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 |
||
|---|---|---|
| .. | ||
| roles | ||
| templates | ||
| main.yml | ||
| README.rst | ||
Infrared plugin to carry out migration from ML2/OVS to OVN
This is an infrared plugin which can be used to carry out the migration from ML2/OVS to OVN if the tripleo was deployed using infrared. See http://infrared.readthedocs.io/en/stable/index.html for more information.
Before using this plugin, first deploy an ML2/OVS overcloud and then:
- On your undercloud, install python-neutron-ovn-migration-tool package (https://trunk.rdoproject.org/centos7-master/current/) You also need to install python-neutron and python3-openvswitch packages.
- Run :: $infrared plugin add "https://github.com/openstack/neutron.git"
3. Start migration by running:
$infrared tripleo-ovn-migration --version 13|14 \--registry-namespace <REGISTRY_NAMESPACE> --registry-tag <TAG> --registry-prefix <PREFIX>
Using this as a standalone playbook for tripleo deployments
It is also possible to use the playbook main.yml with tripleo deployments. In order to use this:
1. Create hosts inventory file like below [undercloud] undercloud_ip ansible_ssh_user=stack
2. Run the playbook as: ansible-playbook main.yml -i hosts -e install_from_package=True -e registry_prefix=centos-binary -e registry_namespace=docker.io/tripleomaster -e registry_localnamespace=192.168.24.1:8787/tripleomaster -e registry_tag=current-tripleo-rdo