[
https://issues.apache.org/jira/browse/MESOS-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16867536#comment-16867536
]
Tom Quarendon commented on MESOS-7899:
--------------------------------------
I'm reasonably new to mesos, so forgive me if this is a dumb question.
I only seem to have "runs/latest". I don't have "runs/containerId", so I don't
appear to be able to unambiguously get the sandbox for a task? Nothing in the
URL is associated with the task, only the executor, and there can be multiple
tasks per executor can't there?
>From the task update I have the container ID, so I had naively tried to
>construct "runs/containerId" but it doens't work. Indeed the "debug" output
>shows that's not mapped, yet the full path is
>(/var/lib/mesos/agent/slaves/..../runs/containerId)
The user interface manages to work out what the work directory for the agent is
itself and constructs the sandbox path that way, containing the explicit
container ID.
As I say, maybe I'm misunderstanding something, but since there can be multiple
tasks per executor (as I understand it), surely I need to include something
derived from the task ID in the URL?
> Expose sandboxes using virtual paths and hide the agent work directory.
> -----------------------------------------------------------------------
>
> Key: MESOS-7899
> URL: https://issues.apache.org/jira/browse/MESOS-7899
> Project: Mesos
> Issue Type: Task
> Reporter: Zhitao Li
> Assignee: Zhitao Li
> Priority: Major
> Fix For: 1.5.0
>
>
> {{Files}} interface already supports a virtual file system. We should figure
> out a way to enable this in {{ /files/download}} endpoint to hide agent
> sandbox.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
