You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "haosdent (JIRA)" <ji...@apache.org> on 2015/09/14 17:21:45 UTC
[jira] [Commented] (MESOS-2065) Add InverseOffer to Python
Scheduler API.
[ https://issues.apache.org/jira/browse/MESOS-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743663#comment-14743663 ]
haosdent commented on MESOS-2065:
---------------------------------
In this discussion, we suggest to support InverseOffer through V1 API in python.
[Do we still need to add InverseOffer support to Scheduler API|http://search-hadoop.com/m/0Vlr6EWNESWcZkd1]
> Add InverseOffer to Python Scheduler API.
> -----------------------------------------
>
> Key: MESOS-2065
> URL: https://issues.apache.org/jira/browse/MESOS-2065
> Project: Mesos
> Issue Type: Task
> Components: python api
> Reporter: Benjamin Mahler
> Assignee: Yong Qiao Wang
> 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 Python Scheduler API is to add a new callback:
> {code}
> def inverseResourceOffers(self, driver, inverse_offers):
> {code}
> Egg / libmesos compatibility will need to be figured out here.
> We may want to leave the Python 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)