[jira] [Updated] (MESOS-2063) Add InverseOffer to C++ Scheduler API.

["Benjamin Mahler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Mahler updated MESOS-2063:
-----------------------------------
    Description: 
The initial use case for InverseOffer in the framework API will be the maintenance primitives in mesos: MESOS-1474.

One way to add these to the C++ Scheduler API is to add a new callback:

{code}
  virtual void inverseResourceOffers(
      SchedulerDriver* driver,
      const std::vector<InverseOffer>& inverseOffers) = 0;
{code}

libmesos compatibility will need to be figured out here.

We may want to leave the C++ binding untouched in favor of Event/Call, in order to not break API compatibility for schedulers.

  was:
The initial use case for InverseOffer in the framework API will be the maintenance primitives in mesos: MESOS-1474.

One way to add these to the C++ Scheduler API is to add a new callback:

{code}
  virtual void inverseResourceOffers(
      SchedulerDriver* driver,
      const std::vector<InverseOffer>& inverseOffers) = 0;
{code}

libmesos compatibility will need to be figured out here.


> Add InverseOffer to C++ Scheduler API.
> --------------------------------------
>
>                 Key: MESOS-2063
>                 URL: https://issues.apache.org/jira/browse/MESOS-2063
>             Project: Mesos
>          Issue Type: Task
>          Components: c++ api
>            Reporter: Benjamin Mahler
>
> The initial use case for InverseOffer in the framework API will be the maintenance primitives in mesos: MESOS-1474.
> One way to add these to the C++ Scheduler API is to add a new callback:
> {code}
>   virtual void inverseResourceOffers(
>       SchedulerDriver* driver,
>       const std::vector<InverseOffer>& inverseOffers) = 0;
> {code}
> libmesos compatibility will need to be figured out here.
> We may want to leave the C++ binding untouched in favor of Event/Call, in order to not break API compatibility for schedulers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)