Open Stack

Thank you Danny for pointing it out! I somehow missed it when going through doc.
Read it again, test and looked into playbook. It seems that's not what I need.

[1] doesn't add multiple interfaces onto one bridge. It actually adds one interface
onto one bridge, but there could be multiple pairs.
This is also confirmed by playbook [2].

Also, the limitation of [3] is an issue for me. 

Hopefully this can be supported in the future.

Thanks!
Tony
[1] https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutron.html#example-multiple-interfaces
[2] https://opendev.org/openstack/kolla-ansible/src/commit/5dbcbda4751f3ac401693c919e6ad2c94f553d7a/ansible/roles/openvswitch/tasks/post-config.yml#L19
[3] https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutron.html#example-shared-interface

________________________________________
From: Danny Webb <Danny.Webb at thehutgroup.com>
Sent: March 26, 2022 12:05 PM
To: Tony Liu; openstack-discuss
Subject: Re: [kolla-ansible] OVS br-ex configuration for OVN SNAT gateway along with HAProxy

<https://github.com/openstack/kolla-ansible/blob/79a5bf2bbe6d8b3509ace56c887baba4c79e61d5/doc/source/reference/networking/neutron.rst#example-multiple-interfaces>
Hi Tony,

Multiple interfaces can be configured as follows:

https://github.com/openstack/kolla-ansible/blob/master/doc/source/reference/networking/neutron.rst#example-multiple-interfaces

Danny
________________________________
From: Tony Liu <tonyliu0592 at hotmail.com>
Sent: 26 March 2022 05:02
To: openstack-discuss <openstack-discuss at lists.openstack.org>
Subject: [kolla-ansible] OVS br-ex configuration for OVN SNAT gateway along with HAProxy

CAUTION: This email originates from outside THG

Hi,

My goal is to have OVN SNAT gateway (with OVS bridge) and HAProxy co-exist.
Here is the networking configuration (partial) before deployment.
eth1, no address, neutron_external_interface
eth1.40, external address, kolla_external_vip_interface

After deployment, I'd like to see this.
br-ex
  eth1
  eth1.40 tag 40
eth1.40 with external address

But actually, only eth1 is put on br-ex by Kolla Ansible.

Need eth1.40 on br-ex, because the external network is also one of the provider
networks. Need eth1 on br-ex, to support other provider networks (different VLANs).
It works fine when deploy with TripleO with os-net-config.

Is it supported by Kolla Ansible? It seems Kolla Ansible only puts one interface
(neutron_external_interface) on br-ex?

I know a few workarounds in case that's not supported, just want to confirm.

Thanks!
Tony



Danny Webb
Principal OpenStack Engineer
The Hut Group<http://www.thehutgroup.com/>

Tel:
Email: Danny.Webb at thehutgroup.com<mailto:Danny.Webb at thehutgroup.com>

For the purposes of this email, the "company" means The Hut Group Limited, a company registered in England and Wales (company number 6539496) whose registered office is at Fifth Floor, Voyager House, Chicago Avenue, Manchester Airport, M90 3DQ and/or any of its respective subsidiaries.

Confidentiality Notice
This e-mail is confidential and intended for the use of the named recipient only. If you are not the intended recipient please notify us by telephone immediately on +44(0)1606 811888 or return it to us by e-mail. Please then delete it from your system and note that any use, dissemination, forwarding, printing or copying is strictly prohibited. Any views or opinions are solely those of the author and do not necessarily represent those of the company.

Encryptions and Viruses
Please note that this e-mail and any attachments have not been encrypted. They may therefore be liable to be compromised. Please also note that it is your responsibility to scan this e-mail and any attachments for viruses. We do not, to the extent permitted by law, accept any liability (whether in contract, negligence or otherwise) for any virus infection and/or external compromise of security and/or confidentiality in relation to transmissions sent by e-mail.

Monitoring
Activity and use of the company's systems is monitored to secure its effective use and operation and for other lawful business purposes. Communications using these systems will also be monitored and may be recorded to secure effective use and operation and for other lawful business purposes.

hgvyjuv