Re: Role-related configuration in Mesos

Perhaps we could also support HTTP PATCH so you could just update one small thing vs's PUT's get and set method. On Thursday, December 17, 2015, Adam Bordelon wrote: > First off, if we're going to have a /reservations endpoint, we should > follow the same PUT+DELETE pattern

Re: Role-related configuration in Mesos

Hi, like you write we use roles for a number of pretty loosely coupled concerns (allocation, quota, reservations). While denormalizing the endpoints like you suggest in Proposal (1) simplifies querying information, it limits how that coupling can be evolved in the future (at least if we’d

Re: Role-related configuration in Mesos

First off, if we're going to have a /reservations endpoint, we should follow the same PUT+DELETE pattern for reserve+unreserve, instead of POST+PUT. And we should consider converting /create and /destroy to PUT+DELETE verbs on a /volumes endpoint. Secondly, we're going to have to support the

Role-related configuration in Mesos

Hi guys, Currently, Mesos uses the following ways to configure role-related objects: 1. For dynamic reserve resources for a role, /reserve endpoint is used to reserve, another /unreserve endpoint is used to unreserve, maybe the third endpoint should be added to show resource reservation of a