tripleo-heat-templates/environments/neutron-ovs-dvr.yaml
Brent Eagles d9fa0ed5b2 Remove External network from DVR related configuration
DVR doesn't imply the "External" networks, simply some type of
connection that is being used for floating IP traffic. This patch
removes the External network from the DVR role and "left overs" from
environment files. It also corrects the multiple-nics version of the
templates so that the ComputeDVR role is attached to the external
bridge with no IP.

Co-Authored-By: Dan Sneddon <dsneddon@redhat.com>

Change-Id: Ia599e01dbefe4e4c752b7d4c1c7e5682963101f7
2018-08-16 16:51:15 -07:00

41 lines
1.9 KiB
YAML

# A Heat environment file that enables DVR in the overcloud.
# This works by configuring L3 and Metadata agents on the
# compute nodes.
resource_registry:
OS::TripleO::Services::ComputeNeutronL3Agent: ../docker/services/neutron-l3.yaml
OS::TripleO::Services::ComputeNeutronMetadataAgent: ../docker/services/neutron-metadata.yaml
# With using default template values, the Compute nodes also need the br-ex
# bridge to be connected to a physical network.
OS::TripleO::Compute::Net::SoftwareConfig: ../net-config-bridge.yaml
parameter_defaults:
# DVR requires that the L2 population feature is enabled
NeutronMechanismDrivers: ['openvswitch', 'l2population']
NeutronEnableL2Pop: 'True'
# Setting NeutronEnableDVR enables distributed routing support in the
# ML2 plugin and agents that support this feature
NeutronEnableDVR: true
# We also need to set the proper agent mode for the L3 agent. This will only
# affect the agent on the controller node.
NeutronL3AgentMode: 'dvr_snat'
# Enabling DVR deploys additional services to the compute nodes that through
# normal operation will consume memory. The amount required is roughly
# proportional to the number of Neutron routers that will be scheduled to
# that host. It is necessary to reserve memory on the compute nodes to avoid
# memory issues when creating instances that are connected to routed
# networks. The current expected consumption is 50 MB per router in addition
# to the base reserved amount. Deployers should refer to existing
# documentation, release notes, etc. for additional information on estimating
# an appropriate value. The provided value here is based on an estimate of 10
# routers and is an example value *only* and should be reviewed and modified
# if necessary before deploying.
NovaReservedHostMemory: 2560
ComputeParameters:
NeutronL3AgentMode: 'dvr'