First time here? Check out the FAQ!
![]() | 1 | initial version |
Hello,
First you dont need to reconfigure all for this modification . In your deployement node where you have kolla-ansible intalled under the directory /etc/kolla You can create the directory : /etc/kolla/config/neutron create the ml2_conf.ini with these parameters : This configuration assume you have a trunk on your external interface Bond0 (no tag under linux) with vlans 10->200
[ml2_type_vlan] network_vlan_ranges = physnet1:10:200 [ml2_type_flat] flat_networks =
Kolla-ansible use all files under config directory for specific configuration. Then you can have a centralised configuration . Juste run (choose the right path for multinode files) kolla-ansible/tools/kolla-ansible -i multinode -t neutron reconfigure
You should have your /etc/kolla/neutron-openvswitch-agent/ml2_conf.ini updated with the new configure
![]() | 2 | No.2 Revision |
Hello,
First you dont need to reconfigure all for this modification . In your deployement node where you have kolla-ansible intalled under the directory /etc/kolla You can create the directory : /etc/kolla/config/neutron create the ml2_conf.ini with these parameters : This configuration assume you have a trunk on your external interface Bond0 (no tag under linux) with vlans 10->200
[ml2_type_vlan]
[ml2_type_vlan]
network_vlan_ranges = physnet1:10:200
[ml2_type_flat]
physnet1:10:200
[ml2_type_flat]
flat_networks =
Kolla-ansible use all files under config directory for specific configuration. Then you can have a centralised configuration . Juste run (choose the right path for multinode files) kolla-ansible/tools/kolla-ansible -i multinode -t neutron reconfigure
You should have your /etc/kolla/neutron-openvswitch-agent/ml2_conf.ini updated with the new configure