Details

    • Sprint:
      RI11/1 DC/OS UI #40, RI11/2 DC/OS UI #41
    • Story Points:
      1

      Description

      When using constraints for placement regarding pods... the UI doesn't allow for it properly AND when provided properly via the CLI... the UI destroys the existing information.

       

      The following is valid pod which fails in the UI

       

      {
      "id": "/ken-test",
      "containers": [
      {
      "name": "container-1",
      "resources": {
      "cpus": 0.1,
      "mem": 128,
      "disk": 0,
      "gpus": 0
      },
      "exec": {
      "command": {
      "shell": "sleep inf"
      }
      }
      }
      ],
      "scaling": {
      "instances": 1,
      "kind": "fixed"
      },
      "scheduling": { "placement": { "acceptedResourceRoles": ["*", "slave_public"] } },
      "executorResources": {
      "cpus": 0.1,
      "mem": 32,
      "disk": 10
      }
      }
      

       

       

      "scheduling": { "placement": { "acceptedResourceRoles": ["*", "slave_public"] } is the failing part.

      If we need a pod placed on a public agent would would do the following

      "scheduling": { "placement": { "acceptedResourceRoles": ["slave_public"] }

      This was tested failing on Soak 1.13

        Attachments

          Activity

            People

            • Assignee:
              rodneynorris Rodney Norris
              Reporter:
              ken Ken Sipe
              Team:
              Frontend Team
              Watchers:
              Automation Bot, Ken Sipe, Mergebot, Rodney Norris
            • Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: