> 1. If the role specified in the reserve/unreserve operation doesn't exist > in --roles on the master, it should reject the reservation on the /reserve > endpoint. Why allow the reservation of roles if you can't use them if they > are specified > > 2. If the role doesn't exist in --roles, and a reservation comes through, > it should be added dynamically. This seems to make more sense to me. I.e. > adding roles doesn't require a master restart. >
There is currently work in progress to add support for implicit roles (roles not specified via --roles). But, I agree that until we add that feature the /reserve endpoint should reject reservations for unknown roles. Not sure what the rationale was to allow this. @mpark?
