[ https://issues.apache.org/jira/browse/MESOS-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129288#comment-16129288 ]
Benjamin Mahler commented on MESOS-7513: ---------------------------------------- [~zhitao] that's an option, after discussing with [~anandmazumdar] I updated the ticket to just be about simplifying the path and exposing it consistently in the master and agent APIs. > Expose the container sandbox path to users via the API. > ------------------------------------------------------- > > Key: MESOS-7513 > URL: https://issues.apache.org/jira/browse/MESOS-7513 > Project: Mesos > Issue Type: Task > Reporter: Anand Mazumdar > Labels: mesosphere > > Currently, only the agent exposes the executor sandbox via a {{directory}} > field in the executor JSON for the v0 API. The master's v0 API and all of the > v1 API do not expose the executor sandbox at all. > As a result, users reverse engineer the logic for generating the path and use > it in their scripts. To add to the difficulty, the path currently includes > the agent's work directory which is only obtainable from the agent endpoints > (i.e. {{/<agent_work_directory>/frameworks/<FID>/executors/<EID>}}) rather > than exposing a virtual path (i.e. {{/frameworks/<FID>/executors/<EID>}}), > like we did for {{/slave/log}} and {{/master/log}}. > We should expose the executor sandbox directory to users consistently in both > the master and agent v0/v1 APIs, as well as simplify the path format so that > users don't know about the agent's work directory. > This also needs to work for nested containers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)