You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Chun-Hung Hsiao (JIRA)" <ji...@apache.org> on 2017/10/16 18:51:00 UTC

[jira] [Updated] (MESOS-8032) Launch CSI plugins in storage local resource providers.

     [ https://issues.apache.org/jira/browse/MESOS-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chun-Hung Hsiao updated MESOS-8032:
-----------------------------------
    Description: 
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.

  was:
Launching a SLRP requires the following steps:
1. Verify the configuration
2. Launch CSI plugins in standalone containers. It needs to use the V1 API to talk to the agent to launch the plugins, which may require authN/authZ.
3. Get the resources from CSI plugins and register to the resource provider manager through the Resource Provider API.

        Summary: Launch CSI plugins in storage local resource providers.  (was: Launching SLRP)

> Launch CSI plugins in storage local resource providers.
> -------------------------------------------------------
>
>                 Key: MESOS-8032
>                 URL: https://issues.apache.org/jira/browse/MESOS-8032
>             Project: Mesos
>          Issue Type: Task
>          Components: agent
>            Reporter: Chun-Hung Hsiao
>            Assignee: Chun-Hung Hsiao
>              Labels: 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)