Details

    • Type: Task
    • Status: Resolved
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: metronome
    • Labels:
      None

      Description

      Background

      Currently, the API for Metronome only support specification of jobs that use docker containers. Here is an example job specification:

      {
        "description": "Example Application",
        "id": "prod.example.app",
        "run": {
          "artifacts": [],
          "cmd": "nuke --dry --master local",
          "cpus": 1.5,
          "mem": 32,
          "disk": 128,
          "docker": {
            "image": "foo/bla:test",
            "forcePullImage": true,
            "parameters": [],
            "privileged": false
          }
        }
      }
      

      We need to introduce additional fields necessary to launch a UCR container, and specify a docker image, etc.

      Additionally, we have two versions of the Metronome API which are supported: v0 and v1.

      Acceptance criteria

      • Design for v0 and v1 (It is anticipated that they will be the same).
      • We don't introduce a major new convention for v0 and v1 (which would lead us to the normalization madness that happened with Marathon). Design should be as consistent as possible with existing norms, with the end goal of creating a more sensible v2.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ken Ken Sipe
                Reporter:
                ken Ken Sipe
                Team:
                Orchestration Team
                Watchers:
                Ken Sipe
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: