You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2017/11/13 01:04:02 UTC
[jira] [Updated] (MESOS-8032) Launch CSI plugins in storage local
resource provider.
[ https://issues.apache.org/jira/browse/MESOS-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam B updated MESOS-8032:
--------------------------
Sprint: Mesosphere Sprint 64, Mesosphere Sprint 65, Mesosphere Sprint 66, Mesosphere Sprint 67, Mesosphere Sprint 68 (was: Mesosphere Sprint 64, Mesosphere Sprint 65, Mesosphere Sprint 66, Mesosphere Sprint 67)
> Launch CSI plugins in storage local resource provider.
> ------------------------------------------------------
>
> Key: MESOS-8032
> URL: https://issues.apache.org/jira/browse/MESOS-8032
> Project: Mesos
> Issue Type: Task
> Components: storage
> Reporter: Chun-Hung Hsiao
> Assignee: Chun-Hung Hsiao
> Labels: mesosphere, storage
> Fix For: 1.5.0
>
>
> Launching a CSI plugin requires the following steps:
> 1. Verify the configuration.
> 2. Prepare a directory in the work directory of the resource provider where the socket file should be placed, and construct the path of the socket file.
> 3. If the socket file already exists and the plugin is already running, we should not launch another plugin instance.
> 4. Otherwise, launch a standalone container to run the plugin and connect to it through the socket file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)