Do we still need to add InverseOffer support to Scheduler API?

[Qian AZ Zhang]

Hi,

In the maintenance epic (MESOS-1474), I see there are 3 tasks created to
add InverseOffer support to Scheduler API:
        MESOS-2063      Add InverseOffer to C++ Scheduler API
        MESOS-2064      Add InverseOffer to Java Scheduler API
        MESOS-2065      Add InverseOffer to Python Scheduler API

I think we have already supported Schedule HTTP API, so do we still need to
update the C++ scheduler API (and the Java/Python binding) to support
InverseOffer? If so, I think we may need to update all the example
frameworks as well. Take C++ scheduler API as an example, we may need to
add a new callback inverseResourceOffers() in the Scheduler class, and each
example framework's scheduler needs to implement it.


Regards,
Qian Zhang