yatinkarel
8989684719
In neutron-multinode jobs where we use ovs/ovn from source, we want to use multi-node-bridge role only for bridge configuration but not for ovs installation. In the job we install ovn and openvswitch before calling this role to configure the bridges. Adding a role var 'install_ovs' to allow skipping ovs installation and service start, it's default to true so no change in current behavior of the role. It's an alternative approach to [1]. [1] https://review.opendev.org/c/zuul/zuul-jobs/+/762650 Related-Bug: #1904117 Change-Id: I64942679520681bdf7f953c0a3c7fc0d13e77856 |
||
|---|---|---|
| .. | ||
| defaults | ||
| files | ||
| tasks | ||
| templates | ||
| vars | ||
| README.rst | ||
Configures a VXLAN virtual network overlay through an openvswitch network bridge between a 'switch' node and 'peer' nodes.
This allows members of the bridge to communicate with each other through the virtual network.
By default, this role will:
- Install and start
openvswitch - Set up a
br-infrabridge on all nodes - Set up the connectivity between the switch and the peer with a virtual port
- Set up an ip address on the bridge interface:
172.24.4.1/23 # switch node
172.41.4.2/23 # first peer
172.41.4.3/23 # second peer
...Role requirements
This role requires and expects two groups to be set up in the Ansible host inventory in order to work:
switch(the node acting as the switch)peers(nodes connected to the virtual switch ports)
Role variables