[
https://issues.apache.org/jira/browse/MESOS-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-2065:
-----------------------------------
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 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.
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 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.
> 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
>
> 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)
