[
https://issues.apache.org/jira/browse/MESOS-6384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085953#comment-16085953
]
Craig Maxson commented on MESOS-6384:
-------------------------------------
Thanks [~bosschaert] for the quick response.
We are pre-creating volumes today with the Docker cli. We are growing an
internal Mesos cloud service and would much prefer to get out of the developers
way by letting them create their own volumes. We could build a self-service
provisioning tool but it would be much better to leverage the standard marathon
interface.
HPE has a case open with Mesosphere from their side.
Any suggestions for getting more action on this issue?
> Support for size with create-on-demand volumes with Docker containerizer
> ------------------------------------------------------------------------
>
> Key: MESOS-6384
> URL: https://issues.apache.org/jira/browse/MESOS-6384
> Project: Mesos
> Issue Type: Improvement
> Components: docker
> Reporter: David Bosschaert
>
> This issue was originally worded as marathon issue
> https://github.com/mesosphere/marathon/issues/4583
> When specifying an external volume to be used with a docker container, the
> size of the external volume cannot be specified. External volumes are often
> created on-demand, when first used, but if no size can be specified all
> volumes will have the same, default size.
> In the case if DVDI with REXRay, the default size is 16GB. This default can
> be modified but it is clearly desirable to be able to specify per-volume what
> the size should be.
> When mesos creates the external volume on-demand, which I presume normally
> happens before the docker container is launched, it should allow the
> specification of the size of this volume.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
