[MESOS-7492] Introduce a daemon manager in the agent.

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Labels: mesosphere storage
• Epic Link: Resource Provider and CSI
• Sprint: Mesosphere Sprint 60, Mesosphere Sprint 61, Mesosphere Sprint 62, Mesosphere Sprint 63, Mesosphere Sprint 64, Mesosphere Sprint 66
• Story Points: 5
• Assignee: Joseph Wu
• Reporter: Jie Yu
• Shepherd: Jie Yu
• Created: 10/May/17 14:13
• Updated: 12/Oct/17 21:25
• Resolved: 12/Oct/17 21:25

Description

Once we have standalone container support from the containerizer, we should consider adding a daemon manager inside the agent. It'll be like 'monit', 'upstart' or 'systemd', but with very limited functionalities. For instance, as a start, the manager will simply always restart the daemons if the daemon fails. It'll also try to cleanup unknown daemons.

This feature will be used to manage CSI plugin containers on the agent.

The daemon manager should have an interface allowing operators to "register" a daemon with a name and a config of the daemon. The daemon manager is responsible for restarting the daemon if it crashes until some one explicitly "unregister" it. Some simple backoff and health check functionality should be provided.

We probably need a small design doc for this.

message DaemonConfig {
  optional ContainerInfo container;
  optional CommandInfo command;
  optional uint32 poll_interval;
  optional uint32 initial_delay;
  optional CheckInfo check; // For health check.
}

class DaemonManager
{
public:
  Future<Nothing> register(
    const ContainerID& containerId,
    const DaemonConfig& config;

  Future<Nothing> unregister(const ContainerID& containerId);

  Future<hashset<ContainerID>> ps();

  Future<ContainerStatus> status(const ContainerID& containerId);
};

Issue Links

• links to: Design document