Public bug reported:
Hello everyone,
I noticed a BUG in the Neutron agent reschedule process when I'm running
the 'BGP dynamic routing agent'.
I tried to found some n-d-r related documentation about the scheduler
process for L3 agents, but I've just saw routers context topics [1].
The main prob
Public bug reported:
Nowadays, the n-d-r service architecture depends of some kind of
messaging between the DRAgent service and Neutron server side. However,
this communications is strongly depent of the messaging service
availability (RabbitMQ by default), and any transient/permanent failures
in
ing
vulnerable to different OVN architectures (using DGP, for example). If Neutron
configured the gateway_port parameter on NAT rule command it would work, but
the issue is that Neutron never configured this before and automatically
gateway port discovery may break the working of FIPs.
My sugge
Public bug reported:
Problem description
--
Regarding the conversation started in March [1] about the use of OVN
interconnect with Neutron, we are testing the use of the OVN-IC to interconnect
workloads in multiple AZs - with different OpenStacks deployments.
4 matches
Mail list logo