Paul Bourke d1673ad173 Allow operators to provision multiple physical networks ... Currently Kolla operators are restricted to configuring one physical network (physnet1). This change along with ml2_conf.ini augmentation can be used to setup multiple physical networks in openvswitch. E.g. To configure two physical networks, physnet1 and physnet2, with ports eth1 and eth2 associated respectively: In /etc/kolla/globals.yml, set neutron_bridge_name: "br-ex,br-ex2" neutron_external_interface: "eth1,eth2" In /etc/kolla/config/neutron/ml2_conf.ini [ovs] bridge_mappings = physnet1:br-ex,physnet2:br-ex2 Co-Authored-By: Mick Thompson <michael.a.thompson@oracle.com> Closes-Bug: #1625700 DocImpact Change-Id: I9454ca98d9b058368129123109ccc56f95519874		2016-09-21 09:14:47 +00:00
..
bootstrap_service.yml	Integrate neutron-vpnaas-agent into the neutron Ansible role	2016-09-15 05:07:46 +00:00
bootstrap.yml	add support for non-default database_port in kolla/ansible	2016-05-13 12:12:25 +00:00
config-neutron-fake.yml	Add vars to the merge_config task in config-neutron-fake.yml	2016-06-03 05:00:41 -04:00
config.yml	Integrate neutron-vpnaas-agent into the neutron Ansible role	2016-09-15 05:07:46 +00:00
deploy.yml	Integrate neutron-vpnaas-agent into the neutron Ansible role	2016-09-15 05:07:46 +00:00
do_reconfigure.yml	Integrate neutron-vpnaas-agent into the neutron Ansible role	2016-09-15 05:07:46 +00:00
ironic-check.yml	Convert Neutron to thin containers	2016-02-06 07:13:47 +00:00
main.yml	Allow neutron role to pull images	2016-01-06 04:23:28 +00:00
pull.yml	Integrate neutron-vpnaas-agent into the neutron Ansible role	2016-09-15 05:07:46 +00:00
reconfigure.yml	Integrate neutron-vpnaas-agent into the neutron Ansible role	2016-09-15 05:07:46 +00:00
register.yml	Fix Keystone v3 and Horizon	2016-03-03 15:44:53 +00:00
start.yml	Allow operators to provision multiple physical networks	2016-09-21 09:14:47 +00:00
upgrade.yml	Integrate neutron-vpnaas-agent into the neutron Ansible role	2016-09-15 05:07:46 +00:00