mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Mann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-4178) Add persistent volume support to the Authorizer
Date Tue, 15 Dec 2015 21:09:46 GMT

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

Greg Mann updated MESOS-4178:
-----------------------------
    Description: 
This ticket is the first in a series that adds authorization support for persistent volume
creation and destruction.

Persistent volumes should be authorized with the {{principal}} of the reserving entity (framework
or master). The idea is to introduce {{Create}} and {{Destroy}} into the ACL.

{code}
  message Create {
    // Subjects.
    required Entity principals = 1;

    // Objects? Perhaps the kind of volume? allowed permissions?
  }

  message Destroy {
    // Subjects.
    required Entity principals = 1;

    // Objects.
    required Entity creator_principals = 2;
  }
{code}

ACLs for volume creation and destruction must be added to {{authorizer.proto}}, and the appropriate
function overloads must be added to the Authorizer.

  was:
This ticket is the first in a series that adds authorization support for persistent volume
creation and destruction.

ACLs for volume creation and destruction must be added to {{authorizer.proto}}, and the appropriate
function overloads must be added to the Authorizer.


> Add persistent volume support to the Authorizer
> -----------------------------------------------
>
>                 Key: MESOS-4178
>                 URL: https://issues.apache.org/jira/browse/MESOS-4178
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Greg Mann
>            Assignee: Greg Mann
>              Labels: mesosphere, persistent-volumes
>
> This ticket is the first in a series that adds authorization support for persistent volume
creation and destruction.
> Persistent volumes should be authorized with the {{principal}} of the reserving entity
(framework or master). The idea is to introduce {{Create}} and {{Destroy}} into the ACL.
> {code}
>   message Create {
>     // Subjects.
>     required Entity principals = 1;
>     // Objects? Perhaps the kind of volume? allowed permissions?
>   }
>   message Destroy {
>     // Subjects.
>     required Entity principals = 1;
>     // Objects.
>     required Entity creator_principals = 2;
>   }
> {code}
> ACLs for volume creation and destruction must be added to {{authorizer.proto}}, and the
appropriate function overloads must be added to the Authorizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message