[
https://issues.apache.org/jira/browse/MESOS-9632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813789#comment-16813789
]
Chun-Hung Hsiao edited comment on MESOS-9632 at 4/9/19 8:38 PM:
----------------------------------------------------------------
{noformat}
commit 0f9f9e7be80af936fdd49d4c9f6e41edba62e87f
Author: Chun-Hung Hsiao <[email protected]>
Date: Sat Apr 6 21:36:54 2019 -0700
Fixed a container ID generation issue in the CSI service manager.
Review: https://reviews.apache.org/r/70427{noformat}
Backported to 1.8.x:
{noformat}
commit 315340f5c287fa72d35011ba7fedabf91a66514d{noformat}
was (Author: chhsia0):
{noformat}
commit 0f9f9e7be80af936fdd49d4c9f6e41edba62e87f
Author: Chun-Hung Hsiao <[email protected]>
Date: Sat Apr 6 21:36:54 2019 -0700
Fixed a container ID generation issue in the CSI service manager.
Review: https://reviews.apache.org/r/70427{noformat}
> Refactor SLRP with a CSI service manager.
> -----------------------------------------
>
> Key: MESOS-9632
> URL: https://issues.apache.org/jira/browse/MESOS-9632
> Project: Mesos
> Issue Type: Task
> Components: storage
> Reporter: Chun-Hung Hsiao
> Assignee: Chun-Hung Hsiao
> Priority: Critical
> Labels: mesosphere, storage
> Fix For: 1.8.0
>
>
> The CSI volume manager relies on service containers, which should be agnostic
> to CSI versions. As the first step of MESOS-9622, we should first refactor
> SLRP with a CSI service manager that manages service container lifecycles
> before refactoring it with a CSI volume manager.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
