| opendevreview | Ching Kuo proposed openstack/kolla-ansible master: Add ovn_sb_connection to octavia.conf https://review.opendev.org/c/openstack/kolla-ansible/+/822925 | 09:03 |
|---|---|---|
| gueswhat | Is possible to set neutron_external_interface to multiple mixed ( flat and vlan ) interfaces? thanks | 20:44 |
| admin1 | each interface can have a diff name .. | 21:01 |
| admin1 | so you can use multiple interfaces gueswhat | 21:01 |
| gueswhat | admin1: i can not figure out how to set neutron_external_interface for flat network ( interface ens18 ) and for vlan ens19.100 | 21:02 |
| admin1 | you give the raw interface .. ens19 to openstack .. neutron will add the tag itself | 21:03 |
| gueswhat | i dont need to set this https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/neutron/templates/ml2_conf.ini.j2#L16, right? | 21:04 |
| gueswhat | or is it only some ml2 optional vlan constrain? | 21:05 |
| admin1 | i don't know the specifics in kolla :) | 21:07 |
| admin1 | i was talking in a general sense .. | 21:07 |
| admin1 | your /etc/neutron/plugins/ml2/ openvswitch/linuxbridge _agent.ini will have the mappings | 21:08 |
| admin1 | of what physical interface is named what in openstack .. one top of which you add the provider networks | 21:08 |
| gueswhat | oh, so raw interface and mapping will be done directly in neutron? like this openstack network create external --external --provider-physical-network physnet2 --provider-network-type vlan --provider-segment 200 ? with neutron_external_interface: "ens18,ens19", where ens19.200 is my target vlan | 21:15 |
| admin1 | one interface .. not 2 .. if you need 2, bridge/bond them .. | 21:19 |
| admin1 | but yes, neutron will add the 200 vlan on top of it and send tagged packets | 21:19 |
| gueswhat | i have flat one ( ens18 ) and then vlan one ( ens19.100 ), for kolla iam using neutron_bridge_name: "br-ex1,br-ex2" and neutron_external_interface: "ens18,ens19", but openstack network create external --external --provider-physical-network physnet2 --provider-network-type vlan --provider-segment 200 fails to Invalid input for operation: physical_network 'physnet2' unknown for VLAN provider network. | 21:40 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!