[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
]
Michael Park updated MESOS-7047:
Shepherd: Neil Conway (was: Michael Park)
> 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//}}. 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/}}.
> 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)
[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//}}. 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/}}.
> 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)
[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
]
Artem Harutyunyan updated MESOS-7047:
-
Sprint: Mesosphere Sprint 52, Mesosphere Sprint 53 (was: Mesosphere Sprint
52)
> 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//}}. 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/}}.
> 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)
[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
]
Michael Park updated MESOS-7047:
Description:
Agents use the role name in the file system path for persistent volumes: a
persistent volume is written to
{{work_dir/volumes/roles//}}. 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/}}.
If we adopt #3, we'd probably also want to cleanup the filesystem when a volume
is removed.
was:
Agents use the role name in the file system path for persistent volumes: a
persistent volume is written to
{{work_dir/meta/volumes/roles//}}. 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/}}.
If we adopt #3, we'd probably also want to cleanup the filesystem when a volume
is removed.
> 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
> 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//}}. 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/}}.
> 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)
[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
]
Neil Conway updated MESOS-7047:
---
Issue Type: Task (was: Bug)
> 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
> Labels: mesosphere
>
> Agents use the role name in the file system path for persistent volumes: a
> persistent volume is written to
> {{work_dir/meta/volumes/roles//}}. 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/}}.
> 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)
[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
]
Neil Conway updated MESOS-7047:
---
Summary: Update agent for hierarchical roles. (was: Update agent for
hierarchical roles)
> Update agent for hierarchical roles.
>
>
> Key: MESOS-7047
> URL: https://issues.apache.org/jira/browse/MESOS-7047
> Project: Mesos
> Issue Type: Bug
> Components: agent
>Reporter: Neil Conway
> Labels: mesosphere
>
> Agents use the role name in the file system path for persistent volumes: a
> persistent volume is written to
> {{work_dir/meta/volumes/roles//}}. 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/}}.
> 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)
[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
]
Neil Conway updated MESOS-7047:
---
Description:
Agents use the role name in the file system path for persistent volumes: a
persistent volume is written to
{{work_dir/meta/volumes/roles//}}. 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/}}.
If we adopt #3, we'd probably also want to cleanup the filesystem when a volume
is removed.
was:
Agents use the role name in the file system path for persistent volumes: a
persistent volume is written to
{{work_dir/meta/volumes/roles//}}. 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 or otherwise encode 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/}}.
If we adopt #3, we'd probably also want to cleanup the filesystem when a volume
is removed.
> Update agent for hierarchical roles
> ---
>
> Key: MESOS-7047
> URL: https://issues.apache.org/jira/browse/MESOS-7047
> Project: Mesos
> Issue Type: Bug
> Components: agent
>Reporter: Neil Conway
> Labels: mesosphere
>
> Agents use the role name in the file system path for persistent volumes: a
> persistent volume is written to
> {{work_dir/meta/volumes/roles//}}. 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/}}.
> 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)
