You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Kevin Klues (JIRA)" <ji...@apache.org> on 2016/11/01 20:21:58 UTC

[jira] [Updated] (MESOS-6471) Build support for LAUNCH_NESTED_CONTAINER_SESSION call into the Agent API in Mesos

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

Kevin Klues updated MESOS-6471:
-------------------------------
    Sprint: Mesosphere Sprint 46

> Build support for LAUNCH_NESTED_CONTAINER_SESSION call into the Agent API in Mesos
> ----------------------------------------------------------------------------------
>
>                 Key: MESOS-6471
>                 URL: https://issues.apache.org/jira/browse/MESOS-6471
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Kevin Klues
>            Assignee: Kevin Klues
>              Labels: debugging, mesosphere
>
> This HTTP API call will launch a nested container whose life-cycle is tied to the lifetime of the connection used to make this call. Once the agent receives the request, it will hold onto it until the container runs to completion or there is an error. Upon success, a 200 response will be initiated with an “infinite” chunked response (but no data will ever be sent over this connection). On error, an appropriate 400 error will be returned. If the connection is ever broken by the client, the container will be destroyed. 
> This will likely involve modifications to some existing existing protobuf messages. It will also involve changes to {{launch.cpp}} to satisfy the new namespace requirements.
> We will create subtickets as we figure out the details for this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)