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

[RFE] Refer altname in bond/VLAN/bridge/route

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

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • nmstate
    • None
    • None
    • rhel-net-mgmt
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Hide

      Definition of Done:

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

      ( ) The acceptance criteria defined below are met.

      Given interface eth0 has alt-name 'uplink-wan' and IP 192.0.2.1/24 with alt-name 'gateway-nic', 

      When a sysadmin applies Nmstate config with:

      • VLAN vlan.101 using base-iface: 'uplink-wan'
      • Static route to 10.0.0.0/8 using next-hop-iface: 'gateway-nic'

      Then, Nmstate resolves alt-names to eth0, creates vlan.101 on eth0 (verified by ip -d link show vlan.101 showing parent eth0), creates the route with eth0 as output interface (verified by ip route show 10.0.0.0/8), and exits with code 0

      Given no interface has alt-name 'nonexistent-link', and both eth0 and eth1 have alt-name 'ambiguous-name' (misconfiguration),

      When sysadmin applies Nmstate config referencing:

      • 'nonexistent-link' as a bond port
      • 'ambiguous-name' as a VLAN base-iface

      Then Nmstate exits with code 1 and error messages indicate:

      • For 'nonexistent-link': interface with name or alt-name not found
      • For 'ambiguous-name': alt-name matches multiple interfaces (eth0, eth1)

      ( ) Integration test case is available upstream.


      ( ) Code is reviewed and merged upstream.


      ( ) Preliminary testing is done.


      ( ) Upstream documentation is written in the upstream MR.


      ( ) Release notes text is written in the RHEL issue.


      ( ) 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 interface eth0 has alt-name 'uplink-wan' and IP 192.0.2.1/24 with alt-name 'gateway-nic',  When a sysadmin applies Nmstate config with: VLAN vlan.101 using base-iface: 'uplink-wan' Static route to 10.0.0.0/8 using next-hop-iface: 'gateway-nic' Then, Nmstate resolves alt-names to eth0, creates vlan.101 on eth0 (verified by ip -d link show vlan.101 showing parent eth0), creates the route with eth0 as output interface (verified by ip route show 10.0.0.0/8), and exits with code 0 — Given no interface has alt-name 'nonexistent-link', and both eth0 and eth1 have alt-name 'ambiguous-name' (misconfiguration), When sysadmin applies Nmstate config referencing: 'nonexistent-link' as a bond port 'ambiguous-name' as a VLAN base-iface Then Nmstate exits with code 1 and error messages indicate: For 'nonexistent-link': interface with name or alt-name not found For 'ambiguous-name': alt-name matches multiple interfaces (eth0, eth1) ( ) Integration test case is available upstream. ( ) Code is reviewed and merged upstream. ( ) Preliminary testing is done. ( ) Upstream documentation is written in the upstream MR. ( ) Release notes text is written in the RHEL issue. ( ) A demo is recorded
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      Goal

      • Support referring altname in bond, VLAN and routes

      For example:

      interfaces:
      - name: bond99
        type: bond
        state: up
        ipv4:
          address:
          - ip: 192.0.2.0
            prefix-length: 24
          enabled: true
        link-aggregation:
          mode: balance-rr
          options:
            miimon: '140'
          port:
          - altname-eth-foo
          - altname-eth-bar
        - alt-names:
          - name: altname-my-bond

              nm-team Network Management Team
              carlosgoncalves Carlos Goncalves
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: