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

Update marathon app configuration to match Marathon 1.5 syntax

          Details

          • Sprint:
            Networking: RI-8 Sprint 35, Networking: RI-9 Sprint 36
          • Story Points:
            5

            Description

            As per Aleksey Dukhovniy's comment in [1]:

            at least the VIP definition is partially deprecated. ipAddresses is removed, container.docker.network is removed in favour of container.networks, container.docker.portMappings is moved to container.portMappings. See this networking migration guide from 1.4 to 1.5 for more details and update the definitions accordingly.

            Sergey Urbanovich Do you think you could update them, please?

            CC: Deepak Goel Aleksey Dukhovniy Karsten Jeschkies

            [1] https://jira.mesosphere.com/browse/DCOS_OSS-2115?focusedCommentId=161198&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-161198

              Attachments

                Issue Links

                relates to

                Bug - A problem which impairs or prevents the functions of the product. DCOS_OSS-3707 Update to CoreOS v1800.7 leads to networking failure in DC/OS

                • Blocker - This problem will block progress.
                • Resolved

                Bug - A problem which impairs or prevents the functions of the product. DCOS_OSS-2115 test_vip failed with RetryError on MarathonApp.wait

                • High - Serious problem that could block progress.
                • Resolved

                  Activity

                    People

                    • Assignee:
                      sergeyurbanovich Sergey Urbanovich (Inactive)
                      Reporter:
                      prozlach Pawel Rozlach
                      Team:
                      Dev Prod Team
                    • Watchers:
                      4 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved:

                        Zendesk Support