[MESOS-6374] CREATE operation shouldn't require the client to specify how the persistent volume should be mounted

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Yan Xu
• Created: 12/Oct/16 00:47
• Updated: 17/Oct/16 20:25

Description

Because CREATE doesn't mount it and there is no container.

Currently in Resource protobuf if 'persistence' is set, 'volume' must be set, 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.

In doing so, the user doesn't have to specify the RW vs. RO mode when creating a persistent volume, it really only matters when the volume is used.

Issue Links

• is related to: MESOS-4324 Allow access to shared persistent volumes as read only or read write by tasks
• is related to: MESOS-4893 Allow setting permissions and access control on persistent volumes