Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Mesos epic is here: https://issues.apache.org/jira/browse/MESOS-6460
These APIs will allow aurora task ssh to enter a container's namespaces (both mount and network) greatly improving user's abilities to self-serve problem solving with their tasks when these isolation mechanisms are enabled.
I pinged in Mesos slack about the availability of these APIs and it seems like they'll land with Mesos 1.2.0, though perhaps without documentation:
Joshua Cohen [3:05 PM] @klueska what’s the status on this? https://issues.apache.org/jira/browse/MESOS-6460 is it still slated for 1.2.0? Kevin Klues [3:08 PM] Yes. All of the API support has landed and will be included in the release. The CLI hasn’t been updated to consume these APIs yet though. I don’t think that will make it into 1.2 unfortunately. The DC/OS CLI can be used as an alternative though https://github.com/dcos/dcos-cli. You can configure it to work with standalone mesos by setting `core.mesos_master_url` in its config. GitHub dcos/dcos-cli dcos-cli - The command line for your datacenter! [3:09] @jcohen ^^ Joshua Cohen [3:10 PM] are the APIs documented? [3:10] we’d like to build support for this in to aurora’s task ssh functionality. Kevin Klues [3:14 PM] I’ve started on the documentation but haven’t finished it yet (and may not before the release). It will be coming soon though. If you want to get started right away, the best source of truth about how to consume the APIS is probably in the PRs against the DC/OS CLI: https://github.com/dcos/dcos-cli/pull/838/files and https://github.com/dcos/dcos-cli/pull/856/files GitHub dcos task exec by adam-mesos · Pull Request #838 · dcos/dcos-cli · GitHub This commit adds a new dcos task exec subcommand to the DC/OS CLI. Using dcos task exec, one can launch arbitrary commands inside a task's container in a DC/OS cluster. This includes commands that ... GitHub Updated `dcos task exec` ATTACH_CONTAINER_INPUT semantics. by klueska · Pull Request #856 · dcos/dcos-cli · GitHub With the new semantics, an ATTACH_CONTAINER_INPUT call will be attempted once before committing to a persistent connection where the actual input is streamed to the agent. This change is required t... Joshua Cohen [3:15 PM] thanks @klueska! Kevin Klues [3:17 PM] @jcohen Actually, its probably more easily consumable from the commits themselves: https://github.com/dcos/dcos-cli/commit/e52bc6f058bc161fb2067a179cea44b2b78d3b37 and https://github.com/dcos/dcos-cli/commit/e6bcdc7efb9e630782e40354fc31c9568d98a473 GitHub task: add `dcos task exec` (#838) · dcos/dcos-cli@e52bc6f · GitHub This commit adds a new dcos task exec subcommand to the DC/OS CLI. Using dcos task exec, one can launch arbitrary commands inside a task's container in a DC/OS cluster. This includes commands that... GitHub task: update `dcos task exec` ATTACH_CONTAINER_INPUT semantics. (#856) · dcos/dcos-cli@e6bcdc7 · GitHub With the new semantics, an ATTACH_CONTAINER_INPUT call will be attempted once before committing to a persistent connection where the actual input is streamed to the agent. This change is requi...