Re: Launching tasks with reserved resources

to the whole task termination. By requiring two different objects in the task launch message we motivate the framework ? i.e. framework writer ? to be aware of different policies that may be attached to different roles. Does it make sense? ?Alex On Thu, Aug 13, 2015 at 2:23 PM, Gidon Gershinsky gi

Re: Launching tasks with reserved resources

, 2015 at 3:46 PM, Gidon Gershinsky gi...@il.ibm.com wrote: Hi Alex, Yep, this setup is using static reservations in agents. I haven't tried running a big task with two or more resources (reserved and unreserved), but guess it is quite intuitive for a developer - a framework is offered two

Launching tasks with reserved resources

I have a simple setup where a framework runs with a role, and some resources are reserved in cluster for that role. The resource offers arrive at the framework as a list of two resource sets: one general (cpus(*)), etc) and one specific for the role (cpus(role1), etc). So far so good. If two

Resource allocation module

We need to develop a new resource allocation module, replacing the off-the-shelf DRF. As I understand, the current mechanism http://mesos.apache.org/documentation/latest/allocation-module/ is being replaced with a less intrusive module architecture,