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

Allow using VRF name to specify route table

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

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • nmstate
    • None
    • None
    • rhel-net-mgmt
    • 3
    • 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 an OpenShift sysadmin configuring a Cluster User Defined Network (CUDN),

      When they define routes in Nmstate using  VRF name instead of a numeric table-id, 

      Then Nmstate must:
        - Resolve the VRF name to its corresponding table-id
        - Apply the route to the correct routing table
        - Return an error if the VRF name does not exist or is invalid
        - Persist the configuration so it survives node reboots
        - Upon reboot, reapply the route using the same VRF name

      The following must be verifiable:
        - The route appears in the correct routing table (matching the VRF's table-id)
        - The route is accessible from within the VRF context
        - After reboot, the route is present and functional without manual intervention


      ( ) 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 an OpenShift sysadmin configuring a Cluster User Defined Network (CUDN), When they define routes in Nmstate using  VRF name instead of a numeric table-id,  Then Nmstate must:   - Resolve the VRF name to its corresponding table-id   - Apply the route to the correct routing table   - Return an error if the VRF name does not exist or is invalid   - Persist the configuration so it survives node reboots   - Upon reboot, reapply the route using the same VRF name The following must be verifiable:   - The route appears in the correct routing table (matching the VRF's table-id)   - The route is accessible from within the VRF context   - After reboot, the route is present and functional without manual intervention ( ) 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

      • As a user configuring routes associated with VRFs, I want a stable way to reference the VRF table id. Otherwise, on reboots the id can change and then manual updates are needed to reconcile the route definition.

      Acceptance criteria

      Support a route configuration such as the following:

      routes:
            config:
            - destination: b.b.b.b/32
              metric: 150
              next-hop-address: c.c.c.c
              next-hop-interface: bond0.301
              vrf-name: dmz

      For more details, see the linked RFE.

              nm-team Network Management Team
              bnemec@redhat.com Benjamin Nemec
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: