Uploaded image for project: 'OpenStack as Infra'
  1. OpenStack as Infra
  2. OSASINFRA-2999

[on-prem] BGP as load-balancer for API & Ingress VIPs (Tech Preview)


    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • onprem-bgp-vips
    • False
    • None
    • False
    • Not Selected
    • Done
    • OCPSTRAT-264 - Compute and control plane nodes on separate subnets for on-prem IPI [ Phase 1]
    • OCPSTRAT-264Compute and control plane nodes on separate subnets for on-prem IPI [ Phase 1]
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • Add tech-preview support to replace HAproxy & Keepalived by FRR, on the control plane, to load-balance the VIP traffic for both API & Ingress services

      Why is this important?

      • Multiple (large) customers are requesting a stretched control plane where the VIPs would have to be able to float between multiple Failure Domains, for high availability
      • Using BGP Anycast to route the VIPs traffic would be more efficient than using Keepalived


      • with Keepalived, the VIP is on one host, so all API & Ingress traffic goes through one host at a time and when a failure happens, the VIP moves to another available node.
      • with BGP Anycast, the VIP is on all control plane nodes and BGP will provide the more efficient route to the client for reaching it.
        • When paths to reach the VIP is equal between the domains, BGP will loadbalance the traffic (configurable at the infrastructure level), so no more bottleneck
        • If a node or service (API, ingress) becomes unavailable, BGP will update the routing table and remove the route instantaneously.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. https://issues.redhat.com/browse/OCPCLOUD-1372 to be finished and delivered in 4.12
      2. https://issues.redhat.com/browse/OSASINFRA-2998 to be delivered as Tech Preview in 4.13

      Open questions::

      none for now.

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Enhancement - <link to Enhancement PR>
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

            Unassigned Unassigned
            emacchi@redhat.com Emilien Macchi
            0 Vote for this issue
            2 Start watching this issue