Unable to inject config values into neutron-api charm outside of [DEFAULT] section

[Pen Gale]

The current neutron-api charm can pass exactly two instances of the --config-file flag when invoking the daemon. The first is always the NEUTRON_CONF file, and the second is the path to the config file for a plugin.

Unfortunately, some plugins, such as the Arista plugin, require two configuration files. And there are some deployments where someone may wish to connect multiple plugins to neutron.

This bug is fixed when the neutron-api charm has been refactored to be more flexible, and accommodate Arista deploys, as well as deploys in which multiple plugins are used.

[Pen Gale (pengale)]

I am grabbing this bug, as I am working on a fix right now.

[Pen Gale (pengale)]

After a conversation with @jamespage, we agreed that it was better practice to simply inject values into the neutron.conf file, rather than adding complexity to the charm by proliferating configuration files.

Unfortunately, it does not appear that the neutron template is currently setup to accept config injection outside of the DEFAULT category. This bug will be fixed once that issue is addressed, I think.

[Pen Gale (pengale)]

Renamed bug to match my current understanding of the issue.