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

[RFE] Match interface by PCI address identifier

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • nmstate-2.2.48-1.el10
    • None
    • ZStream
    • rhel-net-mgmt
    • ssg_networking
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Regression Exception
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      The acceptance criteria defined below are met.

      Given a system administrator needs to configure network interfaces consistently across systems where NIC names may change and uses Nmstate to manage the network state,

      When they define an interface in the desired state YAML by setting the identifier field to pci-address and providing a valid pci-address value,

      Then Nmstate must correctly match the interface associated with the provided PCI address at runtime and apply the declared configuration or fail gracefully with a clear error message if no matching PCI device is found.


      Integration test case is available upstream


      Code is reviewed and merged upstream


      Preliminary Testing is done


      Upstream documentation is written in the upstream MR if needed


      Release Notes text is written in the RHEL issue if needed


      A demo is recorded

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: The acceptance criteria defined below are met. Given a system administrator needs to configure network interfaces consistently across systems where NIC names may change and uses Nmstate to manage the network state, When they define an interface in the desired state YAML by setting the identifier field to pci-address and providing a valid pci-address value, Then Nmstate must correctly match the interface associated with the provided PCI address at runtime and apply the declared configuration or fail gracefully with a clear error message if no matching PCI device is found. Integration test case is available upstream Code is reviewed and merged upstream Preliminary Testing is done Upstream documentation is written in the upstream MR if needed Release Notes text is written in the RHEL issue if needed A demo is recorded
    • Pass
    • Automated
    • Enhancement
    • Hide
      .Nmstate can assign settings to network interfaces based on PCI addresses

      With this enhancement, you can use Nmstate to set up network interfaces based on their PCI address instead of a device name. Use this feature to ensure consistent configuration across nodes in a cluster. For further details, see link:<tba>[Configuring an Ethernet connection with a dynamic IP address by using nmstatectl with a device path] and link:<tba>[Configuring an Ethernet connection with a static IP address by using nmstatectl with a device path].
      Show
      .Nmstate can assign settings to network interfaces based on PCI addresses With this enhancement, you can use Nmstate to set up network interfaces based on their PCI address instead of a device name. Use this feature to ensure consistent configuration across nodes in a cluster. For further details, see link:<tba>[Configuring an Ethernet connection with a dynamic IP address by using nmstatectl with a device path] and link:<tba>[Configuring an Ethernet connection with a static IP address by using nmstatectl with a device path].
    • Done
    • Done
    • Done
    • Not Required
    • None

      Goal

        • For example: As an OpenShift cluster administrator, I want to set up network interfaces based on a specific PCI address, ensuring consistent configuration across nodes.

      Example with "identifier" and "pci-address" (new) fields:

      ---
      interfaces:
        - name: enp198s0f0np1
          identifier: pci-address
          pci-addresss: 0000:00:14.3
          state: up
          ipv4:
            enabled: true
            dhcp: true
            auto-dns: true
            auto-gateway: true
            auto-routes: true
          ipv6:
            enabled: true
            autoconf: true
            dhcp: true
            auto-dns: true
            auto-gateway: true
            auto-routes: true 

              rh-ee-mshi1 Mingyu Shi
              carlosgoncalves Carlos Goncalves
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Marc Muehlfeld Marc Muehlfeld
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: