[
https://issues.apache.org/jira/browse/MESOS-9762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831975#comment-16831975
]
Chun-Hung Hsiao commented on MESOS-9762:
----------------------------------------
Also we might have to chop the framework-specified ID to 99 or 105 bytes to
conform to the CSI spec.
> Encode framework-specified operation ID into CSI volume name.
> -------------------------------------------------------------
>
> Key: MESOS-9762
> URL: https://issues.apache.org/jira/browse/MESOS-9762
> Project: Mesos
> Issue Type: Improvement
> Components: storage
> Reporter: Chun-Hung Hsiao
> Priority: Major
>
> Currently, SLRP uses the internally-generated operation UUID as CSI volume
> creation name, which brings extra difficulty for debugging because users have
> to go through logs to figure out the operation UUID for a given
> {{CREATE_DISK}} call.
> Instead, we could encode the framework-specified operation ID into the volume
> name. To ensure the uniqueness of each volume name, we can use the following
> schema:
> {noformat}
> mesos-<base64-urlsafe-encode(operation-uuid)>.<framework-specified-operation-id>{noformat}
> The prefix before the framework-specified operation ID would be 29 characters
> long.
> We can consider not having the {{mesos-}} prefix to even shorten it, but it
> might not be a bad idea to have that prefix reserved for Mesos.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
