You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Qian Zhang (Jira)" <ji...@apache.org> on 2020/09/01 00:54:00 UTC
[jira] [Commented] (MESOS-10150) Refactor CSI volume manager to
support pre-provisioned CSI volumes
[ https://issues.apache.org/jira/browse/MESOS-10150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188072#comment-17188072 ]
Qian Zhang commented on MESOS-10150:
------------------------------------
commit ea4099028cfe93e1e2fd80e4d30e03057ec27df1
Author: Qian Zhang
Date: Sun Aug 30 10:23:06 2020 +0800
Relaxed unknown volume check when unpublishing volumes.
Review: https://reviews.apache.org/r/72820
> Refactor CSI volume manager to support pre-provisioned CSI volumes
> ------------------------------------------------------------------
>
> Key: MESOS-10150
> URL: https://issues.apache.org/jira/browse/MESOS-10150
> Project: Mesos
> Issue Type: Task
> Reporter: Qian Zhang
> Assignee: Greg Mann
> Priority: Major
> Fix For: 1.11.0
>
>
> The existing [VolumeManager|https://github.com/apache/mesos/blob/1.10.0/src/csi/volume_manager.hpp#L55:L138] is like a wrapper for various CSI gRPC calls, we could consider leveraging it to call CSI plugins rather than making raw CSI gRPC calls in `volume/csi` isolator. But there is a problem, the lifecycle of the volumes managed by VolumeManager starts from the `[createVolume|https://github.com/apache/mesos/blob/1.10.0/src/csi/v1_volume_manager.cpp#L281:L329]` CSI call, but what we plan to support in MVP is pre-provisioned volumes, so we need to refactor VolumeManager by making it support pre-provisioned volumes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)