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

Neil Conway updated MESOS-4143:
-------------------------------
            Assignee:     (was: Neil Conway)
              Sprint: Mesosphere Sprint 24, Mesosphere Sprint 25  (was: 
Mesosphere Sprint 24, Mesosphere Sprint 25, Mesosphere Sprint 26)
    Target Version/s:   (was: 0.27.0)
            Priority: Minor  (was: Major)
         Component/s:     (was: general)
                      master

On reflection, I'm probably not going to try to fix this in the near-term.

* Per discussion with [~mcypark], properly fixing it would require some 
refactoring to how we represent the master's role whitelist. We want to 
validate that the role is in the whitelist in 
{{validation::operation::validate}}; to do this without passing a {{Master*}} 
to {{validate}}, the idea would be to refactor the whitelist so it is 
represented as a {{RoleWhitelist}} object, and then pass that to {{validate}}.
* However, I don't think this is a high-priority issue. Also, all of this code 
is going away in ~six months when we remove the role whitelist.

If someone else wants to take a shot at fixing this, go for it!

> Reserve/UnReserve Dynamic Reservation Endpoints allow reservations on 
> non-existing roles
> ----------------------------------------------------------------------------------------
>
>                 Key: MESOS-4143
>                 URL: https://issues.apache.org/jira/browse/MESOS-4143
>             Project: Mesos
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.25.0, 0.26.0
>            Reporter: John Omernik
>            Priority: Minor
>              Labels: mesosphere, reservations
>
> When working with Dynamic reservations via the /reserve and /unreserve 
> endpoints, it is possible to reserve resources for roles that have not been 
> specified via the --roles flag on the master.  However, these roles are not 
> usable because the roles have not been defined, nor are they added to the 
> list of roles available. 
> Per the mailing list, changing roles after the fact is not possible at this 
> time. (That may be another JIRA), more importantly, the /reserve and 
> /unreserve end points should not allow reservation of roles not specified by 
> --roles.  



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

Reply via email to