Comment 16 for bug 1490990
Revision history for this message
| Armando Migliaccio (armando-migliaccio) wrote | #16 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
It's my understanding that the issue stems from the different ways options can passed to the CLI.
For instance, --config-dir is relied in distros like RDO, but it is not used in DevStack when loading the neutron server. Furthermore, when loading the server with extension modules (like lbaas, vpnaas, ...), their respective config files are not passed to the CLI at all. For this reason, today we rely on a custom logic to load the option from the *aas config file, but that existing logic is no longer meant to be used for merging the opts.
Bottom line, oslo.config rocks and there's nothing wrong with it. What we'll have to do is revise how Devstack handles the configuration for *-aas modules, and eventually get rid of this extra logic that was introduced when we split the services out of Neutron. Having said that...this is a Neutron matter.
HTH