[
https://issues.apache.org/jira/browse/MESOS-9275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692439#comment-16692439
]
Chun-Hung Hsiao commented on MESOS-9275:
----------------------------------------
Reviews for barkporting updated and reordered:
https://reviews.apache.org/r/69036/
https://reviews.apache.org/r/69357/
https://reviews.apache.org/r/69359/
https://reviews.apache.org/r/69360/
https://reviews.apache.org/r/69361/
https://reviews.apache.org/r/69356/
https://reviews.apache.org/r/69363/ (w/ a ship-it)
https://reviews.apache.org/r/69362/
Reviews not for backporting:
https://reviews.apache.org/r/69400/
https://reviews.apache.org/r/69402/
https://reviews.apache.org/r/69364/
https://reviews.apache.org/r/69365/
> 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, storage
> Reporter: Jie Yu
> Assignee: Chun-Hung Hsiao
> Priority: Blocker
> Labels: mesosphere, storage
>
> This will allow 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)
