• False
    • False

      What is the business rationale for this exception? Is there a specific customer that needs this RFE?

      Belgacom/Proximus migrate their environments, they complained about having stale DHCP ports after the migration.

      Are there any security concerns?

      No

      What other functions, teams, or DFGs are impacted by this feature?

      None

      What is the estimated time to have the upstream work complete and approved?

      The migration tool is downstream only

      What is the time and resources required to test this issue? On what date will automated tests be written and ready to run and report results in Polarion?

      We have fully automated CI jobs performing end-to-end migration. The only testing aspect would be checking that the DHCP ports are gone after the migration is finished.

      Is there potential doc impact?

      No

      Are there new packages needed that are not packaged in OSP or RHEL? Does it require newer versions of existing dependencies (dependency bumps)?

      No

      What is the support level? Tech Preview or fully supported

      Fully supported

      How invasive is the code? From very invasive, a core change to very isolated, no risk to other components? Example: Minimal impact (only affects the puppet-cinder module).

      Code change is in the migration tool only, separated from all Neutron services.

      What is the impact to deployment/updates/upgrades/FFU; what are the test plans in these areas?

      No impacts.

              Unassigned Unassigned
              jjoyce@redhat.com Jason Joyce
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: