Affects Version/s: None
Fix Version/s: 0.17.0
Running tasks on more than one offer (which belong to a single slave) can be useful in situations with multiple out-standing offers. Currently, only one offer can be used per launch.
Offer resources can be aggregated and used for traditional task launch.
- Extending the scheduler API with launchTasks(offers, tasks, filters) with takes a list of offers and opposed to a single offer.
- Extending LaunchTasksMessage to carry offer list.
- Extend the offer to offer list in call-path from scheduler to master.
- Master applies offer visitors to validate and aggregate offers into a single resource, before task validation and launch is carried out.
Java and Python interfaces should support both the new and old launchTasks() for backward compatibility.