Quantum server and agents should use openstack.common.cfg
The Quantum server and agents should use openstack.
Note that introducing dependencies on openstack-common into quantum agents might have implications for running agents in XenServer dom0, where only python 2.4 is available. It may be necessary to investigate whether the openstack-common code can be made to run on python 2.4, or whether there are viable solutions to avoid running quantum agents in dom0.
Blueprint information
- Status:
- Complete
- Approver:
- dan wendlandt
- Priority:
- Medium
- Drafter:
- Robert Kukura
- Direction:
- Needs approval
- Assignee:
- Gary Kotton
- Definition:
- New
- Series goal:
- Accepted for folsom
- Implementation:
- Implemented
- Milestone target:
- 2012.2
- Started by
- dan wendlandt
- Completed by
- Gary Kotton
Related branches
Related bugs
Sprints
Whiteboard
I think this is important. Bob, do we have an assignee to take this in F-2, or should I be shopping around for someone?
Gerrit topic: https:/
Addressed by: https:/
blueprint use-common-cfg Added support for linuxbridge plugin
btw, we probably shouldn't put this as "needs code review" until all code for the bp is in code review. I tend to prefer "Good progress" if some code is under review, but more is coming.
Addressed by: https:/
Implements the blueprint use-common-cfg for the quantum service
Useful information:
1. The plugin.ini file has been merged into quantum.conf
2. The Quantum server now has to following options:-
OVS-server:$>sudo python /usr/bin/
Usage: quantum-server [options]
Options:
-h, --help show this help message and exit
--log-
--config-
-v, --verbose Print more verbose output
--noverbose The inverse of --verbose
--use-syslog Use syslog for logging.
--nouse-syslog The inverse of --use-syslog
--log-
--syslog-
-d, --debug Print debugging output
--nodebug The inverse of --debug
--log-
--log-file=PATH (Optional) Name of log file to output to. If not set,
--config-dir=DIR Path to a config directory to pull *.conf files from.
--log-config=PATH If this option is specified, the logging configuration
3. Agent command line is unchanged
Still need to do the following:
1. Separate the api-paste from the quantum configuration file
2. Add global support for the plugin (currently this uses the non-global cfg)
Open issues:
1. Bug in common config - if --config-
2. With V2 doe we need to address versioned plugins? Not sure that this is in the scope of this BP
Addressed by: https:/
Remove paste configuration details to a seperate file. blueprint use-common-cfg