On 03/28/2017 09:54 PM, J. Bruce Fields wrote:
On Tue, Mar 28, 2017 at 09:15:33PM -0400, Stephen Gallagher wrote:
> After today's Server SIG meeting, I put together a straw-man for what an
> Ansible API for configuring NFS shares might look like. (Apologies for not
> including it inline, but the Markdown formatting is really ugly, so please just
> look at it on the web).
> Feedback on this is highly desirable, but please keep server(a)lists.fp.o in the
> CC when you do so.
>  https://github.com/libre-server/proposals/blob/master/NFS/NFS_ansible.md
I know NFS but not Ansible. Do you also need a way to start and stop
As Major says, I think this is probably handled by the existing "service"
module, though there's an argument to be made about whether we might need to
make some modifications to handle this transparently on OSes still using
sysv/upstart rather than systemd.
I think the thread count is another commonly needed parameter--the
default of 8 threads is a little small.
So, this is a feature like the ID-mapping and stuff that I'm beginning to think
probably should be a separate Ansible module specifically for configuring global
settings of the NFS server. So perhaps we should rename the module described in
this proposal to "nfs_share" rather than just "nfs" and use the name
"remote_path is in there as a future-compatible option; in the
world, we may have the ability to "fake" the mount point to the client,
so I added that as an option here. I'm not sure whether to keep it or
drop it." I'm not sure containers would do that for you. Once upon a
time I had rpc.mountd patches to implement this, but wasn't sure if it
was an interesting feature to anyone.
Well, if nothing else we could always have the module just do a bind mount of
the local_path location into the remote_path location so that it could be
referenced by the latter name; I don't think it would require any changes to the
existing NFS server.