Hi Felix,
Thanks for your feedback.
The ovn-bgp-agent is a very powerful application to interconnect multi-tenancy networks using BGP evpn type 5. This application integrates the br-ext with FRR and provides the interconnect using the BGP session. That would be one way to do it, but the problem is that bgpvpn service plugin is only integrated with Neutron. Imagine in the future that we need to integrate the tenant network between different cloud solutions (e.g using OpenStack, Kubernetes, LXD, etc.)... this could be possible if everyone uses OVN as a network backend and ovn-ic to interconnect the LRPs between AZs.
Maybe I'm missing some point and there's no community interest in something like that. But back to the OpenStack/Neutron case, it might be interesting to continue the work on Neutron interconnect (or something like that), but maybe this time with the service plugin for ovn-ic.
Regards, Roberto
Em qui., 9 de mar. de 2023 às 05:24, Felix Hüttner felix.huettner@mail.schwarz escreveu:
Hi Roberto,
We will face a similar issue in the future and have also looked at ovn-interconnect (but not yet tested it).
There is also ovn-bgp-agent [1] which has an evpn mode that might be relevant.
Whatever you find I would definitely be interested in your results
[1] https://opendev.org/x/ovn-bgp-agent
--
Felix Huettner
*From:* Roberto Bartzen Acosta roberto.acosta@luizalabs.com *Sent:* Wednesday, March 8, 2023 9:49 PM *To:* openstack-discuss@lists.openstack.org *Cc:* Tiago Pires tiago.pires@luizalabs.com *Subject:* [neutron] Openstack Network Interconnection
Hey folks.
Does anyone have ideas on how to interconnect different Openstack deployments? Consider that we have multiple Datacenters and need to interconnect tenant networks. How could this be done in the context of OpenStack (without using VPN) ?
We have some ideas about the usage of OVN-IC (OVN Interconnect). It looks like a great solution to create a network layer between DCs/AZs with the help of the OVN driver. However, Neutron does not support the Transit Switches (OVN-IC design) that are required for this application.
We've seen references to abandoned projects like [1] [2] [3].
Does anyone use something similar in production or have an idea about how to do it? Imagine that we need to put workloads on two different AZs that run different Openstack installations, and we want to communicate with the local networks without using a FIP.
I believe that the most coherent way to maintain databases consistent in each Openstack would be an integration with Neutron, but I haven't seen any movement on that.
Regards, Roberto
[1] https://www.youtube.com/watch?v=GizLmSiH1Q0 https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DGizLmSiH1Q0&data=05%7C01%7C%7C7c899166e1ec438b1f7908db20182331%7Cd04f47175a6e4b98b3f96918e0385f4c%7C0%7C0%7C638139060268571269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NdmjPTTQd9HisMRNF8yim%2BjOeXZrlqVY6Q4tKTpb%2FPo%3D&reserved=0 [2] https://specs.openstack.org/openstack/neutron-specs/specs/stein/neutron-inte... https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fspecs.openstack.org%2Fopenstack%2Fneutron-specs%2Fspecs%2Fstein%2Fneutron-interconnection.html&data=05%7C01%7C%7C7c899166e1ec438b1f7908db20182331%7Cd04f47175a6e4b98b3f96918e0385f4c%7C0%7C0%7C638139060268571269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MSh%2BPpWY6L1UoA5kE21cn5khtFWgq%2F8J00kWdOLmHCI%3D&reserved=0 [3] https://opendev.org/x/neutron-interconnection https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopendev.org%2Fx%2Fneutron-interconnection&data=05%7C01%7C%7C7c899166e1ec438b1f7908db20182331%7Cd04f47175a6e4b98b3f96918e0385f4c%7C0%7C0%7C638139060268571269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pb%2B85Y2eobtcu7HbcZpdN68qNjmd2WuedSLteQ3cli8%3D&reserved=0
*‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’.*
- ‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para
assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*
Diese E Mail enthält möglicherweise vertrauliche Inhalte und ist nur für die Verwertung durch den vorgesehenen Empfänger bestimmt. Sollten Sie nicht der vorgesehene Empfänger sein, setzen Sie den Absender bitte unverzüglich in Kenntnis und löschen diese E Mail. Hinweise zum Datenschutz finden Sie hier https://www.datenschutz.schwarz.