You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2017/06/09 18:31:18 UTC

[jira] [Updated] (MESOS-7033) Update documentation for hierarchical roles.

     [ https://issues.apache.org/jira/browse/MESOS-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Mahler updated MESOS-7033:
-----------------------------------
    Description: 
A few things to be sure cover:

* How to ensure that a volume is not shared with other frameworks. Previously, this meant running only 1 framework in the role and using ACLs to prevent other frameworks from running in the role. With hierarchical roles, this now also includes using ACLs to prevent any child roles from being created beneath the role (as these children would be able to obtain the reserved resources). We've been advising frameworks to generate a role (e.g. eng/kafka/<instance-id>) to ensure that they own their reservations (but the dynamic nature of this makes setting up ACLs difficult). Longer term, we may need a more explicit way to bind reservations or volumes to frameworks.

> Update documentation for hierarchical roles.
> --------------------------------------------
>
>                 Key: MESOS-7033
>                 URL: https://issues.apache.org/jira/browse/MESOS-7033
>             Project: Mesos
>          Issue Type: Task
>          Components: documentation
>            Reporter: Neil Conway
>            Assignee: Neil Conway
>              Labels: mesosphere
>
> A few things to be sure cover:
> * How to ensure that a volume is not shared with other frameworks. Previously, this meant running only 1 framework in the role and using ACLs to prevent other frameworks from running in the role. With hierarchical roles, this now also includes using ACLs to prevent any child roles from being created beneath the role (as these children would be able to obtain the reserved resources). We've been advising frameworks to generate a role (e.g. eng/kafka/<instance-id>) to ensure that they own their reservations (but the dynamic nature of this makes setting up ACLs difficult). Longer term, we may need a more explicit way to bind reservations or volumes to frameworks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)