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

Support for multiple external GW - Multihoming

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • rhos-19.0.0
    • None
    • Neutron
    • None
    • Moderate
    • Not Selected
    • False
    • False
    • Hide

      None

      Show
      None
    • 0
    • 0
    • Red Hat OpenStack Services on OpenShift (formerly Red Hat OpenStack Platform)
    • Feature

      Feature Overview 

      Customer deployment may want to have multiple external gateway devices for the same neutron router. This may falls under two use cases

      • Redundancy or HA for external gw routes
      • Use of different external network / gw for different type of traffic (storage, inernal API, tenant traffic)

      Goals

      • Ability to configure and deploy a neutron router to multiple external gw mapping, with ECMP or without
      • Provide redundancy for external connectivity
      • Different routing paths for different external network type

       

      Requirements 

       

      Requirement Notes isMVP?
      Ability to deploy/configure neutron router to multiple external GW mappings for multihoming.    yes
      Functional operation and validation   yes

       

      Done - Acceptance Criteria 

      • Functional operation & validation
      • ECMP operation with failure detection and failover
      • Baseline failover and failure detection time
      • Regression and Automation, CI framework support

      Use Cases

      • Failover to functional external gw upon failure
      • Loadbalancing of traffic across the multiple external gw for higher aggregate capacity

      Documentation Considerations 

      • Feature description, configuration workflow, limitations in Users Guide
      • Release notes for new feature

       

      Background and Strategic Fit 

      • Explicit customer request for the feature as tactical
      • Improve customer adoption and increase market share

       

      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
             
             
             
             

       

              bcafarel@redhat.com Bernard Cafarelli
              rh-ee-gurpsing Gurpreet Singh
              Gurpreet Singh Gurpreet Singh
              Edu Alcaniz Edu Alcaniz
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: