Uploaded image for project: 'DC/OS'
  1. DC/OS
  2. DCOS_OSS-5059

Attach labels to Marathon/Metronome/SDK tasks to identify its "parent"

    Details

      Description

      The general problem is the following:
      multiple components in DC/OS are fetching Mesos state for specific tasks and then trying to identify task's parent information like:

      • Framework e.g. root Marathon, SDK
      • ServiceId e.g. Marathon AppId/PodId
      • ServiceType e.g. Marathon App or Pod
      • Additional Info e.g. in case of Marathon Pods the containerName
      • ...?

      Recently this has bubbled up in multiple JIRA issues most notably:

      • DCOS-51892 EdgeLB is parsing Marathon taskIds to determine whether it is app/pod and (if it is a pod) the container name
      • DCOS-41313 UI is doing something similar additionally relying on the task.discover part of the Mesos task data which has a name field to distinguish between apps and pods (I'm sure this is accidental and is in no way intentional behavior)

      Proposed solution:
      We set task labels which should help other DC/OS components to identify "tasks parent information". We should also keep it as general between our own frameworks as possible, though certain concepts like e.g. "apps" and "pods" are Marathon specific and will not apply to SDK.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              adukhovniy Aleksey Dukhovniy
              Team:
              Orchestration Team
              Watchers:
              Aleksey Dukhovniy, Dima Rozhkov, Matthias Eichstedt, Pawel Rozlach
            • Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: