[jira] [Comment Edited] (MESOS-5102) Support persistent volumes via Docker volume drivers

["Guangya Liu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225856#comment-15225856 ] 

Guangya Liu edited comment on MESOS-5102 at 4/5/16 8:14 AM:
------------------------------------------------------------

I checked the code of mesos/elasticsearch, it was using the module of dvd isolator plugin from https://github.com/emccode/mesos-module-dvdi and depend on dvdcli to manage mount point for container.

MESOS-4355 also planning same design and the difference is that MESOS-4355 wants to create a docker volume isolator but not a module and it will be more easy to be used by end user.

Once MESOS-4355 finished, the mesos/elasticsearch can drop the dependency with https://github.com/emccode/mesos-module-dvdi and use mesos dvd isolator directly.


was (Author: gyliu):
I checked the code of mesos/elasticsearch, it was using the module of dvd isolator plugin from https://github.com/emccode/mesos-module-dvdi and depend on dvdcli to manage mount point for container.

MESOS-4355 also planning same design and the difference is that MESOS-4355 wants to create a docker volume isolator but not a volume and it will be more easy to use by end user.

Once MESOS-4355 finished, the mesos/elasticsearch can drop the dependency with https://github.com/emccode/mesos-module-dvdi and use mesos dvd isolator directly.

> 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)