[
https://issues.apache.org/jira/browse/MESOS-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-2489:
-----------------------------------
Story Points: 12
Assigning story points as the sum of the points of the sub-tasks - if we
promote the sub-tasks to be full-fledged tasks (as we are removing them from
Jira) this should be deleted
[~marco-mesos] to figure out (a) why are the points of subs not added and (b)
does this mean points are double-counted if we do this? (probably yes!)
> Enable a framework to perform reservation operations.
> -----------------------------------------------------
>
> Key: MESOS-2489
> URL: https://issues.apache.org/jira/browse/MESOS-2489
> Project: Mesos
> Issue Type: Task
> Components: master
> Reporter: Michael Park
> Assignee: Michael Park
> Labels: mesosphere
>
> h3. Goal
> This is the first step to supporting dynamic reservations. The goal of this
> task is to enable a framework to reply to a resource offer with *Reserve* and
> *Unreserve* offer operations as defined by {{Offer::Operation}} in
> {{mesos.proto}}.
> h3. Overview
> It's divided into a few subtasks so that it's clear what the small chunks to
> be addressed are. In summary, we need to introduce the
> {{Resource::ReservationInfo}} protobuf message to encapsulate the reservation
> information, enable the C++ {{Resources}} class to handle it then enable the
> master to handle reservation operations.
> h3. Expected Outcome
> * The framework will be able to send back reservation operations to
> (un)reserve resources.
> * The reservations are kept only in the master since we don't send the
> {{CheckpointResources}} message to checkpoint the reservations on the slave
> yet.
> * The reservations are considered to be reserved for the framework's role.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
