Details

      Description

      It was expected that DCOS UI already has constraint support for Jobs when we spec'ed out work for the Epic to support regions and zones.   It turns out the UI does NOT support job constraints... and we need them to complete the Epic.

      Attached is a screen shot of Marathon Placement Constraints.  Metronome supports the same.

      Example JSON:

       

      {
        "description": "Remote Sleeper",
        "id": "sleeper-remote",
        "run": {
          ...,
          "placement": {
            "constraints": [
      	{ "attribute": "@region", "operator": "IS", "value": "us-east-1" }
            ]}
         }
      }

       Current a placement like this in the UI will error when the "Create Job" button is pressed with an error that is not intelligent IMO.   Screen Shot attached.

       

      AC:

      • Users can add placement constraints to a job

      Additional Info:

      • This will require a custom UI form widget. Placement constraints are already being used in the FrameworkConfigurationForm via the PlacementConstraintSchemaField component. This can likely be reused here

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ken Ken Sipe
              Team:
              Frontend Team
              Watchers:
              Automation Bot, Dima Rozhkov, GeorgiSTodorov, Julian Gieseke, Ken Sipe, Matthias Eichstedt
            • Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: