[
https://issues.apache.org/jira/browse/MESOS-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718325#comment-16718325
]
Chun-Hung Hsiao commented on MESOS-9321:
----------------------------------------
I was considering to make the CSI volume mount point calculation based on
{{vendor}} + {{id}} instead of a relative {{root}} + {{id}}, but now I rethink
about this, it seems to me that the current approach would be more flexible.
With the current approach we may be able to make the SLRP or even SERP
publisher a task using a PV as its work directory and put the CSI volume mount
point in the PV. So I'll keep it as is and make {{vendor}} purely for unique
identification.
> Add an optional `vendor` field in `Resource.DiskInfo.Source`.
> -------------------------------------------------------------
>
> Key: MESOS-9321
> URL: https://issues.apache.org/jira/browse/MESOS-9321
> Project: Mesos
> Issue Type: Task
> Components: resource provider, storage
> Reporter: Chun-Hung Hsiao
> Assignee: Chun-Hung Hsiao
> Priority: Critical
> Labels: mesosphere, storage
>
> This will allow the framework to recover volumes reported by the
> corresponding CSI plugin across agent ID changes.
> When an agent changes its ID, all reservation information related to
> resources coming from a given resource provider will be lost, so frameworks
> needs an unique identifier to identify if a new volume associated with the
> new agent ID is the same volume. Since CSI volume ID are not unique across
> different plugins, we will need to add a new {{vendor}} field, which together
> with the existing {{id}} field can provide the means to globally uniquely
> identify this source.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
