MESOS-4144 is duplicated by MESOS-3177(Dynamic Roles/Weights), you can refer to the design doc(https://docs.google.com/document/d/1OIgceqpsjV3-_LGF83IMAFnrh1Ea3Zc16w9kWWPpUj4/edit#heading=h.b0rurfixb4wg) for the details.
------------------ Regards! Grady YQ. Wang?????????? ---------------------------------------------------------------------- Software Engineer Of IBM Platform Computing E-mail: [email protected] Mobile: +86-18182636286 WeChat ID: gradyYQwang Address: 3/F,No.42 GAO XIN LIU ROAD,Xian,Shanxi 710075 China If you can control yourself, then you can control everything. ---------------------------------------------------------------------- ------------------ ???????? ------------------ ??????: "John Omernik";<[email protected]>; ????????: 2015??12??14??(??????) ????2:30 ??????: "[email protected]"<[email protected]>; ????: Re: Dynamic Reservations and --roles I filed https://issues.apache.org/jira/browse/MESOS-4143 to address the reserve unreserve endpoints reserving roles for non-explicit rules. I also opened https://issues.apache.org/jira/browse/MESOS-4144 to add the ability to add roles dynamically based on an API request to properly authorized principals. Thanks! John On Sat, Dec 12, 2015 at 1:40 AM, Michael Park <[email protected]> wrote: This seems like a bug to me. Please file a JIRA ticket and I'll sync with Neil regarding what the behavior should be with dynamic/implicit roles in mind. Thanks! MPark. On Fri, Dec 11, 2015 at 1:32 PM Vinod Kone <[email protected]> wrote: 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?
