97016b2012
This adds support for BGP via the OS::TripleO::Services::Frr service. Spec: https://review.opendev.org/c/openstack/tripleo-specs/+/758249 We create the frr configuration via the corresponding tripleo_frr ansible role at step0. We start the FRR container at deployment step 1 before pacemaker gets configured as the routing to all the other nodes needs to be functional before setting up the cluster. Co-Authored-By: Carlos Gonçalves <cgoncalves@redhat.com> Change-Id: I7cef73c57e7b69f4d031e220c954803afd5e0b8c
16 lines
553 B
YAML
16 lines
553 B
YAML
---
|
|
features:
|
|
- |
|
|
Added FRR as a new TripleO service. This service allows cloud operators to
|
|
deploy pure L3 control plane via BGP protocol. This has the following
|
|
benefits:
|
|
|
|
* Obtain multiple routes on multiple uplinks
|
|
* BGP used for ECMP load balancing and BFD for resiliency
|
|
* Advertise routes to API endpoints
|
|
* Less L2 traffic
|
|
|
|
Please refer to `Install and Configure FRRouter specification
|
|
<https://specs.openstack.org/openstack/tripleo-specs/specs/wallaby/triplo-bgp-frrouter.html>`_
|
|
for more information.
|