Simplify NVP plugin configuration loading
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Armando Migliaccio |
Bug Description
There are several improvements which could be done on the NVP configuration:
- from a user perspective simplify the way in which a connection to a nvp controller is specified.
Currently we use the following format:
<ip>:<port>
However all these parameters with the exception of the first two are common to all controllers (*)
- from a code perspective, there' a a lot of redundancy in the data structures which handle clusters and controller connections; also there's quite a lot of boilerplate code which could be removed if the common cfg infrastructure is properly leveraged.
* Technically, http_timeout, and redirects could different for each controller.
Changed in quantum: | |
milestone: | grizzly-rc1 → havana-1 |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | havana-1 → 2013.2 |
Note: This will be important for properly handling multiple controllers in the devstack patch for nvp as we do not have a way in devstack for specifying multi string options.