Add support for customising Neutron physical network names
Previously Kolla Ansible hard-coded Neutron physical networks starting at physnet1 up to physnetN, matching the number of interfaces in neutron_external_interface and bridges in neutron_bridge_name. Sometimes we may want to customise the physical network names used. This may be to allow for not all hosts having access to all physical networks, or to use more descriptive names. For example, in an environment with a separate physical network for Ironic provisioning, controllers might have access to two physical networks, while compute nodes have access to one. This change adds a neutron_physical_networks variable, making it possible to customise the Neutron physical network names used for the OVS, OVN, Linux bridge and OVS DPDK plugins. The default behaviour is unchanged. Change-Id: Ib5b8ea727014964919c6b3bd2352bac4a4ac1787
Showing
- ansible/group_vars/all.yml 1 addition, 0 deletionsansible/group_vars/all.yml
- ansible/roles/neutron/templates/linuxbridge_agent.ini.j2 2 additions, 1 deletionansible/roles/neutron/templates/linuxbridge_agent.ini.j2
- ansible/roles/neutron/templates/ml2_conf.ini.j2 2 additions, 2 deletionsansible/roles/neutron/templates/ml2_conf.ini.j2
- ansible/roles/neutron/templates/openvswitch_agent.ini.j2 2 additions, 1 deletionansible/roles/neutron/templates/openvswitch_agent.ini.j2
- ansible/roles/ovn-controller/tasks/setup-ovs.yml 4 additions, 2 deletionsansible/roles/ovn-controller/tasks/setup-ovs.yml
- ansible/roles/ovs-dpdk/defaults/main.yml 4 additions, 2 deletionsansible/roles/ovs-dpdk/defaults/main.yml
- doc/source/reference/networking/neutron.rst 36 additions, 5 deletionsdoc/source/reference/networking/neutron.rst
- releasenotes/notes/neutron-physical-networks-5b908bed9809c3b4.yaml 6 additions, 0 deletions...tes/notes/neutron-physical-networks-5b908bed9809c3b4.yaml
Loading
Please register or sign in to comment