Given a schedule, defined elsewhere, any resource offers to affected slaves must include an Unavailability field.
The maintenance schedule for a single slave should be held in
persistent storage and locally by the master. i.e. In src/master/master.hpp:
The new field should be populated via an API call (see
The Unavailability field can be added to Master::offer (src/master/master.cpp).
- Start master, slave.
- Check unavailability of offer == none.
- Set unavailability to the future.
- Check offer has unavailability.