[
https://issues.apache.org/jira/browse/MESOS-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yan Xu updated MESOS-6374:
--------------------------
Summary: CREATE operation shouldn't require the client to specify how the
persistent volume should be mounted (was: CREATE operation shouldn't require
the client to specify how it should be mounted)
> CREATE operation shouldn't require the client to specify how the persistent
> volume should be mounted
> ----------------------------------------------------------------------------------------------------
>
> Key: MESOS-6374
> URL: https://issues.apache.org/jira/browse/MESOS-6374
> Project: Mesos
> Issue Type: Bug
> Reporter: Yan Xu
>
> Because CREATE doesn't mount it and there is no container.
> Currently in {{Resource}} protobuf [if 'persistence' is set, 'volume' must be
> set|https://github.com/apache/mesos/blob/af2d406282d8da0ed93eacf997bf8f94aa77b492/include/mesos/v1/mesos.proto#L831-L832],
> this requires frameworks to specify a {{volume}} field with a dummy
> {{container_path}} because it's a required field.
> The lifecycle management of persistent "volumes" is so different from regular
> volumes that we should use the {{volume}} field only in the context of
> tasks/containers.
> We should put everything related to the management of persistent volumes into
> {{Persistence}} and not require {{volume}} to be set when we are
> creating/destroying a persistent volume.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
