Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-32495

Allow route configuration without interface name specification

XMLWordPrintable

    • sst_network_management
    • ssg_networking
    • 5
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Hide

      User Story:

      As a network administrator, I want to configure routes in OpenShift installations using a MAC address as an identifier so that I can specify routes without needing to know the interface name during image-based installations.

       

      Acceptance criteria:

      Given a system administrator setting up an OpenShift environment with image-based installation and preparing a YAML configuration for network interfaces with MAC addresses specified and the identifier set to `mac-address`,

      When they submit a route configuration where the `next-hop-interface` is specified using a profile-name or directly using a MAC address that matches an earlier specified interface,

       

      Then, Nmstate should match the `next-hop-interface` based on the MAC address or profile name from the corresponding interface section and the route configuration should apply without requiring the explicit name of the network interface.

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Integration tests are written and pass
      • The new feature is part of a downstream build attached to an errata
      • This new feature is documented in RHEL and the nmstate.io official documentation is also updated.
      Show
      User Story: As a network administrator, I want to configure routes in OpenShift installations using a MAC address as an identifier so that I can specify routes without needing to know the interface name during image-based installations.   Acceptance criteria: Given a system administrator setting up an OpenShift environment with image-based installation and preparing a YAML configuration for network interfaces with MAC addresses specified and the identifier set to `mac-address`, When they submit a route configuration where the `next-hop-interface` is specified using a profile-name or directly using a MAC address that matches an earlier specified interface,   Then, Nmstate should match the `next-hop-interface` based on the MAC address or profile name from the corresponding interface section and the route configuration should apply without requiring the explicit name of the network interface. Definition of Done: The implementation meets the acceptance criteria Integration tests are written and pass The new feature is part of a downstream build attached to an errata This new feature is documented in RHEL and the nmstate.io official documentation is also updated.
    • None
    • None
    • Unspecified Release Note Type - Unknown
    • None

      As part of openshift installation we want to use new "identifier:mac" feature as in our installation flow (imaged-based) user will not know interface name.

      Currently user still needs to specify interface name in order to configure route and it makes "identifier:mac" much less generic that it can be.

      Will be very useful to allow route configuration that will not require 

      "next-hop-iface: <iface-name>" and will make it more generic 

            rh-ee-sfaye Stanislas Faye
            itsoiref@redhat.com Igal Tsoiref
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: