[
https://issues.apache.org/jira/browse/AURORA-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15483814#comment-15483814
]
Stephan Erb edited comment on AURORA-1768 at 9/12/16 11:08 AM:
---------------------------------------------------------------
That's tough. The PID of the executor is available in
{{/var/lib/mesos/meta/slaves/latest/frameworks/\*/executors/\*/runs/latest/pids/forked.pid}}
but as the executor runs outside of the mount namespace this might not work.
was (Author: stephanerb):
That's tough. The PID of the executor is available in
{{/var/lib/mesos/meta/slaves/latest/frameworks/*/executors/*/runs/latest/pids/forked.pid}}
but as the executor runs outside of the mount namespace this might not work.
> Command `aurora task ssh` is not namespace and taskfs aware
> ------------------------------------------------------------
>
> Key: AURORA-1768
> URL: https://issues.apache.org/jira/browse/AURORA-1768
> Project: Aurora
> Issue Type: Story
> Components: Thermos
> Reporter: Stephan Erb
>
> In order to guarantee isolation among tasks and to simplify debugging in
> production environments, we should make sure commands executed via `aurora
> ssh` have been isolated in the same way as the tasks itself. This implies
> that we have to use the same container filesystem and enter the same
> namespaces.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
