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
10 lines
413 B
YAML
10 lines
413 B
YAML
resource_registry:
|
|
OS::TripleO::Services::Frr: ../../deployment/frr/frr-container-ansible.yaml
|
|
|
|
parameter_defaults:
|
|
# These need to be disabled by default when using FRR/BGP because
|
|
# the gateways and other controllers are very unlikely to be reachable
|
|
# that early in the deployment (i.e. BGP needs to be up and functional for that to work)
|
|
ValidateControllersIcmp: false
|
|
ValidateGatewaysIcmp: false
|