e4edf35b64
This allows the path-specific registry entries to be static and doesn't impose any requirements on where the environment containing parameters lives. The documentation is also updated, which required a newer version of sphinx to allow automatic references to headings.
19 lines
1.0 KiB
YAML
19 lines
1.0 KiB
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: Enable Routed Networks
|
|
# description: |
|
|
# Enable use of routed networks, where there may be multiple separate
|
|
# networks connected with a router and DHCP relay. Do not pass any other
|
|
# network configuration environments after this one or they may override
|
|
# the changes made by this environment. When this environment is in use,
|
|
# the routed-networks-configuration environment should usually be
|
|
# included as well.
|
|
resource_registry:
|
|
OS::OVB::BaremetalNetworks: ../templates/baremetal-networks-routed.yaml
|
|
OS::OVB::DHCPRelay: ../templates/dhcp-relay.yaml
|
|
OS::OVB::UndercloudNetworks: ../templates/undercloud-networks-routed.yaml
|