Unable to change nova.conf via charm
Bug #1648804 reported by
Fairbanks.
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron-gateway (Juju Charms Collection) |
Opinion
|
Wishlist
|
Unassigned | ||
Bug Description
Hello there,
I wonder why it isn't possible to update config files which are templated in several charms.
Sometimes i have to patch the config files my self now because the charm doesn't allow it.
This also means that i have to patch the template file located in on those units, and if i add a new unit i have to patch those again.
For example, the neutron-gateway charm has a /etc/nova/nova.conf file which can't be updated via the charm it self.
Also, if i need to add values to something else then the [DEFAULT] section, this isn't possible.
Can this be fixed somehow, this is a big show-stopper for automation from my point of view.
Thx,
Mathijs van Veluw
Fairbanks.
Revision history for this message
| James Page (james-page) wrote | #1 |
| Changed in neutron-gateway (Juju Charms Collection): | |
| status: | New → Opinion |
| importance: | Undecided → Wishlist |
To post a comment you must log in.
Allowing charm users to arbitrarily change configuration options in charm configuration files has always been something we've avoided if possible - a number of charms have a config-flags option which allows (to an extent) for values to be injected, but that comes with a big disclaimer that its designed to full functional gaps, which should be translated into charm requirements and configuration options when observed.
The rationale being that we want to provide fully tested configurations for OpenStack deployments, and allowing full customisation of any part of a config file will break that contract with charm users.