OVN-based deployments do not respect Availability Zones
Bug #2002040 reported by
zrsolis
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| openstack-ansible |
In Progress
|
High
|
Unassigned | ||
Bug Description
Currently OVN-based deployments have no mechanism to specify Availability Zones to deploy the ovn-controller or neutron-
| Changed in openstack-ansible: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
| importance: | Critical → High |
Revision history for this message
| Dmitriy Rabotyagov (noonedeadpunk) wrote | #1 |
| Changed in openstack-ansible: | |
| status: | Confirmed → In Progress |
To post a comment you must log in.
Hi,
We already aware about missing this functionality. We have Work in Progress patch already proposed, but it does introduce some more issues.
The main problem in implementation is that in neutron with drivers other then OVN you can provide list of AZs and agents can be distributed across AZs, while ovsctl should be provided with only 1 AZ.
So patch should be smart enough both to allow to configure AZs for all scenarios.
At the moment I can suggest only using OVS, that just relies on neutron config files and can be leveraged with group_vars. But we're going to work on implementing AZ support in the timely manner.