mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MESOS-9275) Allow optional `profile` to be specified in `CREATE_DISK` offer operation.
Date Thu, 27 Sep 2018 19:18:00 GMT
Jie Yu created MESOS-9275:
-----------------------------

             Summary: Allow optional `profile` to be specified in `CREATE_DISK` offer operation.
                 Key: MESOS-9275
                 URL: https://issues.apache.org/jira/browse/MESOS-9275
             Project: Mesos
          Issue Type: Task
          Components: resource provider
            Reporter: Jie Yu


This will allows the framework to "import" pre-existing volumes reported by the corresponding
CSI plugin.

For instance, the LVM CSI plugin might detect some pre-existing volumes that Dan has created
out of band. Currently, those volumes will be represented as RAW "disk" resource with a volume
ID, but no volume profile by the SLRP. When a framework tries to use the RAW volume as either
MOUNT or BLOCK volume, it'll issue a CREATE_DISK operation. The corresponding SLRP will handles
the operation, and validate against a default profile for MOUNT volumes. However, this prevents
the volume to have a different profile that the framework might want.

Ideally, we should allow the framework to optionally specify a profile that it wants the volume
to have during CREATE_DISK because it might have some expectations on the volume. The SLRP
will validate with the corresponding CSI plugin using the ValidateVolumeCapabilities RPC call
to see if the profile is applicable to the volume.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message