[MESOS-2120] Add support for task labels / parameters

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Sprint: Mesosphere Q4 Sprint 3 - 12/7
• Assignee: Niklas Quarfot Nielsen
• Reporter: Niklas Quarfot Nielsen
• Shepherd: Timothy Chen
• Created: 17/Nov/14 22:10
• Updated: 09/Sep/15 23:13
• Resolved: 20/Nov/14 19:39

Description

Add support to hang key value pairs off tasks which follows them through the task life-cycle. This can be made available through the existing HTTP end-points (state, tasks and so on) which the data field cannot do, as we cannot make any assumptions in how to interpret the user data.
A capability like this is a relative small change compared to the leverage it gives with regards to external tooling.

We should consider the implications of the new field just like the data field with respect to avoid requiring excess memory to store the task info's.

We already have a proto message for key value pairs called Parameter: https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L712

So the suggested change is:

message TaskInfo {
  required string name = 1;
  required TaskID task_id = 2;
  required SlaveID slave_id = 3;
  repeated Resource resources = 4;
  optional ExecutorInfo executor = 5;
  optional CommandInfo command = 7;
  // Task provided with a container will launch the container as part
  // of this task paired with the task's CommandInfo.
  optional ContainerInfo container = 9;
  optional bytes data = 6;
  // A health check for the task (currently in *alpha* and initial
  // support will only be for TaskInfo's that have a CommandInfo).
  optional HealthCheck health_check = 8;

  optional Parameters parameters = 9;
}

Alongside the necessary changes to expose the value in master and slave endpoints.

Issue Links

• relates to: MESOS-3401 Add labels to Resources