You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2017/04/14 08:54:42 UTC
[jira] [Updated] (MESOS-7047) Update agent for hierarchical roles.
[ https://issues.apache.org/jira/browse/MESOS-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam B updated MESOS-7047:
--------------------------
Sprint: Mesosphere Sprint 52, Mesosphere Sprint 53, Mesosphere Sprint 54, Mesosphere Sprint 55 (was: Mesosphere Sprint 52, Mesosphere Sprint 53, Mesosphere Sprint 54)
> Update agent for hierarchical roles.
> ------------------------------------
>
> Key: MESOS-7047
> URL: https://issues.apache.org/jira/browse/MESOS-7047
> Project: Mesos
> Issue Type: Task
> Components: agent
> Reporter: Neil Conway
> Assignee: Benjamin Bannier
> Labels: mesosphere
>
> Agents use the role name in the file system path for persistent volumes: a persistent volume is written to {{work_dir/volumes/roles/<role-name>/<persistence-id>}}. When using hierarchical roles, {{role-name}} might contain slashes. It seems like there are three options here:
> # When converting the role name into the file system path, escape any slashes that appear.
> # Hash the role name before using it in the file system path.
> # Create a directory hierarchy that corresponds to the nesting in the role name. So a volume for role {{a/b/c/d}} would be stored in {{roles/a/b/c/d/<persistence-id>}}.
> If we adopt #3, we'd probably also want to cleanup the filesystem when a volume is removed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)