mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam B (JIRA)" <>
Subject [jira] [Commented] (MESOS-6460) Mesos Support for Container Attach and Container Exec
Date Mon, 06 Feb 2017 09:13:41 GMT


Adam B commented on MESOS-6460:

[~klueska] Can we close out this Epic for Mesos 1.2.0 and move all the unresolved tickets
to a new "Container Exec/Attach Improvments" Epic for 1.3.0?

> Mesos Support for Container Attach and Container Exec
> -----------------------------------------------------
>                 Key: MESOS-6460
>                 URL:
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Kevin Klues
>            Assignee: Kevin Klues
>              Labels: debugging, mesosphere
>   Original Estimate: 840h
>  Remaining Estimate: 840h
> This Epic coordinates the design of new Agent APIs for attaching a remote client to the
{{stdin}}, {{stdout}}, and {{stderr}} of a running Mesos task. It also outlines an API for
launching new processes inside the same container as a running Mesos task and attaching to
its {{stdin}}, {{stdout}}, and {{stderr}}. At a high level, these APIs mimic functionality
similar to {{docker attach}} and {{docker exec}}.
> The primary motivation for such functionality is to enable users to debug their running
Mesos tasks more easily. Specifically, these APIs will allow us to prod and probe the container
of a running Mesos task by (for example) navigating its file system using an interactive {{bash}}
shell or attaching {{gdb}} to any processes already running inside the container.

This message was sent by Atlassian JIRA

View raw message