Missing support for AGENT.availability_zone
Bug #1829537 reported by
Florian Guitton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Open vSwitch Charm |
Fix Released
|
Medium
|
James Page |
Bug Description
Hello everybody,
Currently there does not seem to be a way to control the neutron availability_zone of a compute node. When relying on DVR_SNAT this is an issue because compute nodes do not bring up the necessary routers to perform network communication. Currently all node deployed with this charm have default 'nova' availability zone.
I am missing something ? Is there a way to work around this issue ?
Changed in charm-neutron-openvswitch: | |
assignee: | nobody → James Page (james-page) |
milestone: | none → 19.10 |
importance: | Wishlist → Medium |
status: | Triaged → In Progress |
Changed in charm-neutron-openvswitch: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
TRIAGE:
The [agent] -> availability_zone isn't set in the neutron-api's neutron.conf which is where it would need to be supported.