[
https://issues.apache.org/jira/browse/MESOS-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225761#comment-15225761
]
Tobias Mueller commented on MESOS-5102:
---------------------------------------
I had a look at https://issues.apache.org/jira/browse/MESOS-4355 and I'm not
sure whether it'll be implemented so that a already created Docker volume can
be used, or that it will be possible to actually create a Docker volume from
the Mesos isolator itself.
Ideally, I think it'd be great if a Marathon app could create a volume upon
launch, and reuse a volume if the task is migrated of restarted. What is not
really clear to me is if there isn't a need for some kind of
volume-to-application (instance) registration, because otherwise I can't
imagine how it would be possible to match a pre-existing volume to an
application. Also, I'm not sure how scaling of apps and their instance volumes
can be handled.
The mesos/elasticsearch framework
(http://mesos-elasticsearch.readthedocs.org/en/latest/) already supports an
'--externalVolumeDriver' flag, but I'm not 100% sure how this was implemented.
> Support persistent volumes via Docker volume drivers
> ----------------------------------------------------
>
> Key: MESOS-5102
> URL: https://issues.apache.org/jira/browse/MESOS-5102
> Project: Mesos
> Issue Type: Improvement
> Components: containerization, docker
> Affects Versions: 0.28.0
> Reporter: Tobias Mueller
>
> To my understanding it's currently not possible to create persistent volumes
> via Docker volume drivers/plugins. This limits IMHO the usability of the
> persistent volumes to a large extend if people are using distributed
> filesystems like GlusterFS or Ceph.
> There was a discussion in a GitHub issue
> (https://github.com/mesosphere/marathon/issues/2493#issuecomment-196743212)
> about this, leading to the conclusion that it's currently not possible to use
> Docker volume drivers.
> Looking at http://mesos.apache.org/documentation/latest/persistent-volume/ I
> guess it would make sense to add a property for the Docker volume driver in
> the Offer::Operation::CREATE operation so that the --volume-driver flag can
> be added when the Docker containers are launched, e.g. via Marathon.
> References:
> * https://docs.docker.com/engine/extend/plugins_volume/
> StackOverflow questions:
> *
> http://stackoverflow.com/questions/36361483/example-marathon-json-deployment-file-when-using-glusterfs-volume-driver/36396205
> *
> http://stackoverflow.com/questions/36242383/mesos-slaves-reject-all-marathon-jobs-with-persistent-volumes-claims-no-space-a
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
