c2fb0b16b6
setup-mtu-t1 argument name is misleading as it suggest that it will do something with the MTU value, but it really just reduces DHCP agent t1 timer. The fact that this commnad will have a side effect of getting a new MTU value from DHCP should not be part of the argument name. This is based on customer's feedback. I am keeping backward compatibility for setup-mtu-t1 argument in order not to break any existing tools that might depend on it. Change-Id: I939b21fa998c80cf921efeae3e8fa8c2b4ef4f50 |
||
|---|---|---|
| .. | ||
| infrared/tripleo-ovn-migration | ||
| tripleo_environment | ||
| hosts.sample | ||
| migrate-to-ovn.yml | ||
| README.rst | ||
Migration from ML2/OVS to ML2/OVN
Proof-of-concept ansible script for migrating an OpenStack deployment that uses ML2/OVS to OVN.
If you have a tripleo ML2/OVS deployment then please see the folder
tripleo_environment
Prerequisites:
- Ansible 2.2 or greater.
- ML2/OVS must be using the OVS firewall driver.
To use:
Create an ansible inventory with the expected set of groups and variables as indicated by the hosts-sample file.
Run the playbook:
$ ansible-playbook migrate-to-ovn.yml -i hosts
Testing Status:
- Tested on an RDO cloud on CentOS 7.3 based on Ocata.
- The cloud had 3 controller nodes and 6 compute nodes.
- Observed network downtime was 10 seconds.
- The "--forks 10" option was used with ansible-playbook to ensure that commands could be run across the entire environment in parallel.
MTU:
- If migrating an ML2/OVS deployment using VXLAN tenant networks to an OVN deployment using Geneve for tenant networks, we have an unresolved issue around MTU. The VXLAN overhead is 30 bytes. OVN with Geneve has an overhead of 38 bytes. We need the tenant networks MTU adjusted for OVN and then we need all VMs to receive the updated MTU value through DHCP before the migration can take place. For testing purposes, we've just hacked the Neutron code to indicate that the VXLAN overhead was 38 bytes instead of 30, bypassing the issue at migration time.