feature: Pass mechanism_drivers from neutron-api suboridinate charms
Bug #1496993 reported by
Jorge Niedbalski
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron API Charm |
Triaged
|
Wishlist
|
Unassigned | ||
neutron-api (Juju Charms Collection) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Currently the mechanism_drivers option is enforced to openvswitch,
but we have others to be supported as well, so this should be configurable even
if this is being handled by a subordinate charm.
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = openvswitch,
# Example: mechanism_drivers = openvswitch,brocade
# Example: mechanism_drivers = linuxbridge,brocade
This bug tracks that implementation.
description: | updated |
tags: | added: sts |
tags: | added: openstack |
Changed in charm-neutron-api: | |
status: | New → Confirmed |
Changed in neutron-api (Juju Charms Collection): | |
status: | Confirmed → Invalid |
To post a comment you must log in.
In general subordinates should be able to manipulate ml2_config.ini, SubordinateConf igContext helps to inject new parameters, but existing one cannot be modified.