[jira] [Commented] (MESOS-6467) Build a Container I/O Switchboard

["Jie Yu (JIRA)" <ji...@apache.org>]

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

Jie Yu commented on MESOS-6467:
-------------------------------

commit 18845afb7f02b0ec92d106e445827f92d3b02329
Author: Kevin Klues <kl...@gmail.com>
Date:   Thu Dec 1 11:21:47 2016 -0800

    Updated IOSwitchboard to block IO until connected for DEBUG containers.

    Review: https://reviews.apache.org/r/54241/

> Build a Container I/O Switchboard
> ---------------------------------
>
>                 Key: MESOS-6467
>                 URL: https://issues.apache.org/jira/browse/MESOS-6467
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Kevin Klues
>            Assignee: Kevin Klues
>              Labels: debugging, mesosphere
>             Fix For: 1.2.0
>
>
> In order to facilitate attach operations for a running container, we plan to introduce a new component into Mesos known as an “I/O switchboard”. The goal of this switchboard is to allow external components to *dynamically* interpose on the {{stdin}}, {{stdout}} and {{stderr}} of the init process of a running Mesos container. It will be implemented as a per-container, stand-alone process launched by the mesos containerizer at the time a container is first launched.
> Each per-container switchboard will be responsible for the following:
>  * Accepting a single dynamic request to register an fd for streaming data to the {{stdin}} of a container’s init process.
>  * Accepting *multiple* dynamic requests to register fds for streaming data from the {{stdout}} and {{stderr}} of a container’s init process to those fds.
>  * Allocating a pty for the new process (if requested), and directing data through the master fd of the pty as necessary.
>  * Passing the *actual* set of file descriptors that should be dup’d onto the {{stdin}}, {{stdout}} and {{stderr}} of a container’s init process back to the containerizer. 
> The idea being that the switchboard will maintain three asynchronous loops (one each for {{stdin}}, {{stdout}} and {{stderr}}) that constantly pipe data to/from a container’s init process to/from all of the file descriptors that have been dynamically registered with it.



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