From 218f5f31a93d5650da6a219cbff52ab282c8d03c Mon Sep 17 00:00:00 2001 From: Emilien Macchi Date: Mon, 31 May 2021 14:15:49 -0400 Subject: [PATCH] Add environment for external network VIP This environment allows us to control the external VIP for Undercloud or Standalone SSL. When used, a network data has to be provided (e.g. network_data_undercloud.yaml) and `openstack tripleo deploy` must be called with --public-virtual-ip. It's not really needed for Undercloud because environments/undercloud.yaml already sets the resource right, but for Standalone users this file will be useful when they want public endpoints to be listening on another network. Change-Id: I461e0fdc8fc717beed3aea7a66e41de1e11116da (cherry picked from commit d297c822c4177b98028e1a3b2838737b58eb3be1) --- environments/external-network-vip.yaml | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 environments/external-network-vip.yaml diff --git a/environments/external-network-vip.yaml b/environments/external-network-vip.yaml new file mode 100644 index 0000000000..f7808753f5 --- /dev/null +++ b/environments/external-network-vip.yaml @@ -0,0 +1,5 @@ +# This environment allows us to control the external VIP for Undercloud or Standalone SSL. +# When used, a network data has to be provided (e.g. network_data_undercloud.yaml) and +# `openstack tripleo deploy` must be called with --public-virtual-ip. +resource_registry: + OS::TripleO::Network::Ports::ExternalVipPort: ../network/ports/external_from_pool.yaml