[
https://issues.apache.org/jira/browse/MESOS-9275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703640#comment-16703640
]
Chun-Hung Hsiao commented on MESOS-9275:
----------------------------------------
Backported to 1.7.x:
{noformat}
commit 4140b73f0ac75e9700a3a9260f589d7e064bee97
commit 55ff7377b2062e03c04d2fd84c2935f598877a70
commit 37d6a222ab25c37cc0b5def45825583f65b11c00
commit b704e4946705db732fd216f516df3b0e2e36128a
commit 1c7be01b2b3a5f577b12713ea319c79769e55803
commit 27b400e0266528b08f9da90bd41a5c19514858eb
commit 0ae89dc43872166e9f83e5ab1cd3c63efab4bb4a
commit 9d32259105c4794d7d45060c9fad03954a7e39cb{noformat}
> 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: Improvement
> Components: resource provider, storage
> Reporter: Jie Yu
> Assignee: Chun-Hung Hsiao
> Priority: Blocker
> Labels: mesosphere, storage
> Fix For: 1.7.1, 1.8.0
>
>
> 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)
