2071dc9a38
Kayobe has fairly coarse-grained default groups - controller, compute, etc, which work well in the majority of cases. Kolla Ansible allows much more fine-grained placement on a per-service basis, e.g. ironic-conductor. If the operator has taken advantage of this fine-grained placement, then it is possible that some of the assumptions in Kayobe may be incorrect. This is one downside of the split between Kayobe and Kolla Ansible. For example, Ironic conductor services may have been moved to a subset of the top level 'controllers' group. In this case, we would not want the Ironic networks to be mapped to all hosts in the controllers group - only those running Ironic conductor services. The same argument can be made if the loadbalancer services (HAProxy & keepalived) or Neutron dataplane services (e.g. L3 & DHCP agents) have been separated from the top level 'network' group. This change abstracts the placement of Ironic conductor Ironic inspector, loadbalancer and network services into separate variables, rather than referencing the top level 'controllers' and 'network' groups directly. These variables may be updated by the operator to match the service placement. Change-Id: Idbf181c795ee98ad653f11ae483f9dab4ef1b599
67 lines
2.5 KiB
Plaintext
67 lines
2.5 KiB
Plaintext
---
|
|
###############################################################################
|
|
# Neutron configuration.
|
|
|
|
# List of Neutron ML2 mechanism drivers to use. If unset the kolla-ansible
|
|
# defaults will be used.
|
|
kolla_neutron_ml2_mechanism_drivers:
|
|
|
|
# List of Neutron ML2 type drivers to use.
|
|
kolla_neutron_ml2_type_drivers:
|
|
- flat
|
|
- vlan
|
|
- vxlan
|
|
|
|
# List of Neutron ML2 tenant network types to use.
|
|
kolla_neutron_ml2_tenant_network_types:
|
|
- flat
|
|
- vlan
|
|
- vxlan
|
|
|
|
# List of Neutron ML2 network VLAN ranges to use. Each item should be a dict
|
|
# containing the following items:
|
|
# physical_network: The physical network
|
|
# range: Range of allowed VLANs on this physical network (min:max, (optional)
|
|
kolla_neutron_ml2_network_vlan_ranges: []
|
|
|
|
# List of Neutron ML2 extention drivers to use.
|
|
kolla_neutron_ml2_extension_drivers: []
|
|
|
|
###############################################################################
|
|
# Neutron ML2 generic switch driver configuration.
|
|
|
|
# List of switches to configure for use by genericswitch ML2 mechanism driver.
|
|
# Each item should be a dict containing the following items:
|
|
# name: Hostname of the switch
|
|
# ip: IP address on which to reach the switch
|
|
# username: SSH username
|
|
# password: SSH password (optional)
|
|
# key_file: SSH key file (optional)
|
|
# secret: SSH secret (optional)
|
|
kolla_neutron_ml2_generic_switches: []
|
|
|
|
# List of Ansible hosts representing switches to configure for use by
|
|
# genericswitch ML2 mechanism driver. These switches will be appended to
|
|
# kolla_neutron_ml2_generic_switches and their configuration will be determined
|
|
# by the following host variables:
|
|
# name: inventory_hostname
|
|
# ip: ansible_host
|
|
# username: ansible_user
|
|
# password: ansible_ssh_pass
|
|
# key_file: not currently supported
|
|
# secret: not currently supported
|
|
kolla_neutron_ml2_generic_switch_hosts: []
|
|
|
|
# List of Ansible hosts whose switch interfaces are to be configured as tagged
|
|
# members of all networks managed by the genericswitch ML2 mechanism driver.
|
|
# These hosts will be matched against the description fields in the
|
|
# switch_interface_config variable for each switch to determine which
|
|
# interfaces should be configured.
|
|
kolla_neutron_ml2_generic_switch_trunk_port_hosts: "{{ groups[controller_network_group] }}"
|
|
|
|
# Dict containing additional configuration for switches managed by the
|
|
# genericswitch ML2 mechanism driver. For per-switch configuration of switches
|
|
# in kolla_neutron_ml2_generic_switch_hosts, this may be set as a group or
|
|
# host variable for the switch host.
|
|
kolla_neutron_ml2_generic_switch_extra: {}
|