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 2015/12/07 20:54:11 UTC

[jira] [Commented] (MESOS-2998) Disable Persistent Volumes, Dynamic Reservations via master flags

    [ https://issues.apache.org/jira/browse/MESOS-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045584#comment-15045584 ] 

Adam B commented on MESOS-2998:
-------------------------------

This ticket was intended as a stopgap until we get the ACLs in place. Now that we're landing the ACLs, I think we can close it (duplicate? won't fix?). Objections?

cc: [~jieyu], [~greggomann]

> Disable Persistent Volumes, Dynamic Reservations via master flags
> -----------------------------------------------------------------
>
>                 Key: MESOS-2998
>                 URL: https://issues.apache.org/jira/browse/MESOS-2998
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.23.0
>            Reporter: Adam B
>            Assignee: Michael Park
>              Labels: mesosphere, persistence, reservations, volumes
>
> As an operator, I might not want frameworks using the experimental dynamic reservations/persistent volumes APIs in 0.23, since there are no ACLs or operator endpoints for me to manage them. That means that a rogue framework could start reserving resources and creating volumes with all resources provided, and I would have no way to clean them up.
> Is it possible to disable these features from the master (flags, etc.)?



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