[MESOS-2076] Implement maintenance primitives in the Master.

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: master
• Labels: mesosphere twitter
• Epic Link: Maintenance
• Story Points: 13
• Assignee: Joris Van Remoortere
• Reporter: Benjamin Mahler
• Created: 11/Nov/14 20:42
• Updated: 25/Sep/15 04:33
• Resolved: 25/Sep/15 04:33

Description

The master will need to do a number of things to implement the maintenance primitives:

1. For machines that have a maintenance window:
   • Disambiguate machines to agents.
   • For unused resources, offers must be augmented with an Unavailability.
   • For used resources, inverse offers must be sent.
2. For inverse offers:
   • Filter them before sending them again.
   • For declined inverse offers, do something with the reason (store or log).
3. Recover the maintenance information upon failover.

Note: Some amount of this logic will need to be placed in the allocator.

Issue Links

• contains: MESOS-3038 Resource offers do not contain Unavailability, given a maintenance schedule
• contains: MESOS-3042 Master/Allocator does not send InverseOffers to resources to be maintained
• contains: MESOS-3043 Master does not handle InverseOffers in the Accept call (Event/Call API)
• contains: MESOS-3044 Slaves are not deactivated upon reaching a maintenance window
• contains: MESOS-3045 Maintenance information is not populated in case of failover
• contains: MESOS-3265 Starting maintenance needs to deactivate agents and kill tasks.
• contains: MESOS-3266 Stopping/Completing maintenance needs to reactivate agents.
• contains: MESOS-3041 Decline call does not include an optional "reason", in the Event/Call API