On 07/07/16 10:28, Robin Winslow wrote:
> Thanks everyone, some really helpful suggestions there.
>
> > On the storage roadmap we have shared filesystems, so your underlying
> > cloud could provide these and Juju would organise them to be in the
> > right place for each unit.
>
> Is there any information online that you could link me to about these
> ideas, so I can get an idea of what this offering would look like?
It would look like a new storage type declaration in the charm, saying
it wants a shared filesystem mounted at a particular place, and the
matching deployment parameter for the operator.
Something like this in the charm:
storage:
output-dir:
mount: /var/lib/app/output
shared
And something like this in the deployment:
juju add-pool aws-efs=elastic-fs
juju deploy app --storage output-dir=aws-efs
I'm guessing from memory, details are in the Juju storage spec:
https://docs.google.com/document/d/1OhaLiHMoGNFEmDJTiNGMluIlkFtzcYjezC8Yq4nAX3Q/edit#heading=h.fcmwvp6x272u
> > I should also have mentioned that there are IIRC a few bundles
> which> actually setup an NFS server and clients in the bundle in order to
> > provide this entirely internally to the bundle (i.e. without any cloud
> > or juju mediated storage management).
>
> If anyone could link me to any specific bundles which implement this
> sort of solution with NFS, that would be very interesting to look at.
>
https://jujucharms.com/transcode-cloud/
What a nice URL that is, thank you everybody who made that possible :)
Mark
--
Juju mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
