93d2f4f56c
Big changes here. This will make it easier to deploy some of the more advanced OVB options like network-isolation. Instead of users having to figure out which lines in the sample env.yaml to uncomment when deploying advanced options, they will simply be able to include one environment file that contains all the appropriate parameters to turn on the option. This _should_ be backwards compatible with existing monolithic env.yaml configurations. If it is not, that is a bug. To create the option environments, a slightly modified copy of the sample environment generator from tripleo-heat-templates has been copied into the project. The sample environments should _not_ be edited directly. Instead, the definition in the sample-env-generator directory should be altered and the tool re-run to update the environment.
23 lines
927 B
YAML
23 lines
927 B
YAML
# *******************************************************************
|
|
# This file was created automatically by the sample environment
|
|
# generator. Developers should use `tox -e genconfig` to update it.
|
|
# Users are recommended to make changes to a copy of the file instead
|
|
# of the original, if any customizations are needed.
|
|
# *******************************************************************
|
|
# title: Assign the Undercloud an Existing Floating IP
|
|
# description: |
|
|
# When deploying the undercloud, assign it an existing floating IP instead
|
|
# of creating a new one.
|
|
parameter_defaults:
|
|
# Address of existing floating ip to use.
|
|
# Type: string
|
|
undercloud_floating_ip: ''
|
|
|
|
# ID of existing floating ip to use.
|
|
# Mandatory. This parameter must be set by the user.
|
|
# Type: string
|
|
undercloud_floating_ip_id: <None>
|
|
|
|
resource_registry:
|
|
OS::OVB::UndercloudFloating: ../templates/undercloud-floating-existing.yaml
|