validate the data-port config before applying it
Bug #1927015 reported by
Andrea Ieri
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Neutron Gateway Charm |
Triaged
|
Wishlist
|
Unassigned | ||
| OpenStack Neutron Open vSwitch Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
The charms don't really validate the proposed data-port settings, but an incorrect config can have disastrous consequences on a live cloud. For example, the following is an accepted change:
juju config neutron-openvswitch data-port=
...even though it will cause a network loop that could potentially take out both the data plane and the control plane.
A basic sanity check built into the charm could prevent human mistakes in a very crucial part of the cloud.
Related bugs:
* bug 1872799
* bug 1915967
Revision history for this message
| Alex Kavanagh (ajkavanagh) wrote | #1 |
Revision history for this message
| Alex Kavanagh (ajkavanagh) wrote | #2 |
| Changed in charm-neutron-openvswitch: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| Changed in charm-neutron-gateway: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
To post a comment you must log in.
This is a very tricky one as the range of values that are 'legal' is wide and the possibility of rejecting valid sets of values is high. It's like static type systems; they describe a class of legal programs but not ALL legal programs and a way to escape the type system is necessary to write some programs that otherwise wouldn't be possible.
However, if a mechanism can be proposed for how to 'override' a data checking system that doesn't just add complexity to how to do configurations, that would be useful.