[MESOS-3066] Replicated registry needs a representation of maintenance schedules

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.25.0
• Component/s: master, replicated log
• Labels: mesosphere
• Target Version/s: 0.25.0
• Epic Link: Maintenance
• Sprint: Mesosphere Sprint 15, Mesosphere Sprint 16, Mesosphere Sprint 17
• Story Points: 3
• Assignee: Joseph Wu
• Reporter: Joseph Wu
• Shepherd: Benjamin Hindman
• Created: 16/Jul/15 18:05
• Updated: 26/Nov/18 12:21
• Resolved: 26/Nov/18 12:21

Description

In order to persist maintenance schedules across failovers of the master, the schedule information must be kept in the replicated registry.

This means adding an additional message in the Registry protobuf in src/master/registry.proto. The status of each individual slave's maintenance will also be persisted in this way.

message Maintenance {
  message HostStatus {
    required string hostname = 1;

    // True if the slave is deactivated for maintenance.
    // False if the slave is draining in preparation for maintenance.
    required bool is_down = 2;  // Or an enum
  }

  message Schedule {
    // The set of affected slave(s).
    repeated HostStatus hosts = 1;

    // Interval in which this set of slaves is expected to be down for.
    optional Unavailability interval = 2;
  }

  message Schedules {
    repeated Schedule schedules;
  }

  optional Schedules schedules = 1;
}

Note: There can be multiple SlaveID's attached to a single hostname.

Issue Links

• Is contained by: MESOS-2075 Add maintenance information to the replicated registry.