mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qian Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-2063) Add InverseOffer to C++ Scheduler API.
Date Tue, 15 Sep 2015 06:17:45 GMT

    [ https://issues.apache.org/jira/browse/MESOS-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744909#comment-14744909
] 

Qian Zhang commented on MESOS-2063:
-----------------------------------

Currently, there is no plan to add this to old scheduler API, see the following mail thread
for detailed discussion:
http://www.mail-archive.com/dev@mesos.apache.org/msg33184.html

> 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
>            Assignee: Qian Zhang
>              Labels: mesosphere, twitter
>
> 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)

Mime
View raw message