[jira] [Commented] (MESOS-6241) Add agent::Call / agent::Response API for managing nested containers.

["Benjamin Mahler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15524876#comment-15524876 ] 

Benjamin Mahler commented on MESOS-6241:
----------------------------------------

{noformat}
commit 398dd5603a6666d98b340a437e89190e9f479767
Author: Benjamin Mahler <bm...@apache.org>
Date:   Mon Sep 26 11:39:24 2016 -0700

    Removed resources field from LaunchNestedContainer agent::Call.

    This field is currently not used, in that nested containers will
    share the resources allocated to the parent container, regardless
    of whether resources are specified.

    In the future when we introduce the ability to provide nested
    container resource allocation and isolation, we can re-introduce
    the field as necessary.

    Review: https://reviews.apache.org/r/52290
{noformat}

{noformat}
commit 9faf6a0916a1c0b4b47ea68620eeb92f3bf6d111
Author: Benjamin Mahler <bm...@apache.org>
Date:   Mon Sep 26 17:03:29 2016 -0700

    Updated nested container agent API to allow custom ContainerIDs.

    Previously, we required that ContainerID.value is a UUID. The
    intention here was that each container has the same format, and
    we could remove the need for ContainerID.parent since all
    ContainerIDs would be unique globally.

    With this change, we intend to keep ContainerID.parent and allow
    users to specify custom IDs (e.g. <executor uuid>.redis.backup).
    This makes for more readable IDs, and we maintain globally unique
    ContainerIDs since the executor container has a UUID generated by
    the agent.

    With this change, we now validate that the user supplied IDs are
    setting the parent component of the ID correctly, and that the
    value does not contain problematic characters.

    Review: https://reviews.apache.org/r/52292
{noformat}

> Add agent::Call / agent::Response API for managing nested containers.
> ---------------------------------------------------------------------
>
>                 Key: MESOS-6241
>                 URL: https://issues.apache.org/jira/browse/MESOS-6241
>             Project: Mesos
>          Issue Type: Task
>          Components: HTTP API, slave
>            Reporter: Benjamin Mahler
>            Assignee: Benjamin Mahler
>             Fix For: 1.1.0
>
>
> In order to manage nested containers from executors or from tooling, we'll need to have an API for managing nested containers.
> Per the [design doc|https://docs.google.com/document/d/1FtcyQkDfGp-bPHTW4pUoqQCgVlPde936bo-IIENO_ho/] we will start with the following:
> * Launch: create a new nested container underneath the parent container.
> * Wait: wait for the nested container to terminate.
> * Kill: kill a non-terminal nested container.



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