Adding allow_automatic_dhcp_failover option or config-flags option for neutron-api charm
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron-api (Juju Charms Collection) |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
OpenStack can define multiple vlan provider networks, and dhcp-agent in one cabinet can be re-scheduled into other vlan cabinet so that dhcp cann't work well when allow_automatic
Maybe setting up external static dhcp server per cabinet or external dhcp proxy can fix such problem but it requires overhead. Availability zone feature is also implemented to fix such problem since Mitaka. But adding the following options can solve this problem more simply when the version is less than Mitaka.
network_
allow_automatic
Does it make sense to expose these options for the general user community? which is better for adding allow_automatic
Thanks,
Joshua
| Changed in neutron-api (Juju Charms Collection): | |
| status: | New → Confirmed |
| milestone: | none → 16.07 |
| importance: | Undecided → Wishlist |
| Hua Zhang (zhhuabj) wrote | #1 |
| Hua Zhang (zhhuabj) wrote | #2 |
| OpenStack Infra (hudson-openstack) wrote Fix merged to charm-neutron-api (master) | #3 |
| Changed in neutron-api (Juju Charms Collection): | |
| status: | Confirmed → Fix Committed |
| Changed in neutron-api (Juju Charms Collection): | |
| status: | Fix Committed → Fix Released |
There are lots of discussion about using a primary config or config-flags started with this link[1]. I personally think it should be done with config-flags. so based on comment #8 in the link[1] I will also provide a config-flags patch first, meantime, you're welcome to contribute to the discussion here. thanks.
[1] https:/