Uploaded image for project: 'OpenStack Strategy'
  1. OpenStack Strategy
  2. RHOSSTRAT-902

Support Data plane adoption for BGP control plane - Tech Preview

XMLWordPrintable

    • RHOSSTRAT-904Reach Feature Complete Status for the Red Hat OpenStack Services on OpenShift 18.0 Adoption Process
    • Not Selected
    • False
    • False
    • Hide

      None

      Show
      None
    • 0
    • 0
    • 100% To Do, 0% In Progress, 0% Done
    • rhos-connectivity-bgp
    • Technology Preview
    • Hide
      .Support Data plane adoption for BGP control plane (Technology Preview)

      With this technology preview, you can upgrade in-place an OpenStack deployment from RHOSP 17.1 to RHOSO 18 by deploying a parallel control plane based on RHOSO 18 and then pointing the compute nodes to the new control plane.
      Show
      .Support Data plane adoption for BGP control plane (Technology Preview) With this technology preview, you can upgrade in-place an OpenStack deployment from RHOSP 17.1 to RHOSO 18 by deploying a parallel control plane based on RHOSO 18 and then pointing the compute nodes to the new control plane.
    • Done

      Feature Overview 

      Data plane adoption for RHOSO provides mechanism to upgrade in-place the openstack deployment from RHOSP 17.1 to RHOSO 18 by deploying a parallel control plane based on RHOSO 18 and then pointing the compute nodes to the new control plane. 

      BGP in RHOSP 17.1 supports L3 HA for the OpenStack control plane and enables customers to deploy Openstack control plane across L3 boundaries. This feature is to test the RHOSO adoption process for BGP control plane as the user transitions from RHOSP 17.1 to RHOSO 18 using the adoption process. 

      Goals

      Validate and automate the testing for data plane adoption of BGP control plane.

      Release note for new feature capability

      Requirements (mandatory -_ Complete while in Refinement status):
      A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

      Requirement Notes isMVP?
           
           

       

      Acceptance Criteria

      • Validate and automate the testing for data plane adoption of BGP control plane.
        • Have Routed spine & leaf3  controller nodes using BGP for reachability information (i.e host routes)
        • Perform Adoption from 17.1 to FR3 RHOSO 18.0
        • Verify all controller nodes are able to reach each other using BGP reachbility information
        • Verify FRR config/logs dont report any abnormality 
      • Release note for technology preview capability (no documentation update until full support)

      Team Sign Off (Completion while in Planning status)

      • All required Epics (known at the time) are linked to the this Feature
      • All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
      • Add - Reviewers name, Team Name
      • Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
      • Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone
      Reviewed By Team Name Accepted Notes
             
             
             
             

       

              eolivare Eduardo Olivares Toledo
              rh-ee-gurpsing Gurpreet Singh
              Gurpreet Singh Gurpreet Singh
              Edu Alcaniz Edu Alcaniz
              rhos-dfg-networking-squad-bgp
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: