On 11/01/2016 01:12 PM, Pete Travis wrote:
On Oct 26, 2016 07:44, "Jon Stanley"
> I'd like some feedback on a (very early) draft that I have of the
> document for the NFS role definition (if you'd like edit access, just
> shoot me an email):
> How I thought of this was to go from user stories, to technical
> requirements, and finally to activities to meet those requirements.
> The actor in all of the user stories in an inexperienced admin - are
> there other actors that we need to be concerned with?
> Totally open to feedback here - is this even on the right path?
Could this also include an NFS client role? It would be great if the one
cockpit instance would let me create an export on server A, and present that
export in the cockpit UI as an available mount for server B.
I'm not sure that we specifically need a client *role* for this. It kind of
depends on what we decide belongs in the base offering of Fedora Server.
In my view, storage is kind of a bootstrapping thing. I'm not sure I'd want to
install a special module just to attach to my storage servers; I'd expect to be
able to do that out-of-the-box.
I spoke with the Cockpit developers; they've got plans and a design for adding
NFS client support to Cockpit proper. They haven't prioritized it yet, but we
Aside, I'd love an NFS+gluster role for similar use cases.
Once you start getting into clustered deployments, I'm not sure the model we're
using *quite* fits in. That sort of thing really needs orchestration at a higher
level than per-machine.