[
https://issues.apache.org/jira/browse/MESOS-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226058#comment-15226058
]
Tobias Mueller commented on MESOS-5102:
---------------------------------------
I had a look at dvdcli, and it says it mimics what the Docker daemon does for
its volumes. That seems fine so far. Still, I not sure about the following:
- dvdcli is an additional component which has to be installed (I guess it won't
be integrated with Mesos directly with the isolator, if I understand the
"Comments from EMC Team for item 3)" in the design docs correctly), at least
for some time. For example, we're running Mesos on CoreOS clusters and try to
avoid installing additional/custom software on the agents as far as we can. We
run everything via Docker images, so installing dvdcli is not ideal for us (if
Docker itself already has the same functionality). In a second step, dvdcli
will be replaced in a second step by a reimplementation in C++, so the
dependency will probably be removed. Is this correct?
- I saw the protobuf definition and I think it's fine. What I don't understand
from the design docs is how the volumes will be usable via the Offers/Tasks,
and how this will fit in the currently used resource offers. Can you please
give a little insight on that?
Thank you very much!
> 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)
