Remove plugging of internal classes from configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Senhua Huang |
Bug Description
Nova currently has the following options:
cfg.
cfg.
cfg.
These options came from the following commit:
commit c729ba8c0aa4d28
Author: Chris Behrens <email address hidden>
Date: Sun Jan 15 23:29:41 2012 -0800
Core modifications for future zones service.
Makes compute/
Splits some code out in compute/api
Adds some race condition checking on deletes in compute/api
Make instance_delete support UUIDs
Add support to RPC to cast to specific servers
Migrations for future zones
Change-Id: Ibee126cd6d325e
Nova should not expose the ability to replace internal classes in the configuration. These classes are internal implementation details. Exposing it via configuration like this commits us to some level of maintaining these implementation details in case someone has put in their own version. It also seems like a support nightmare.
Based on the commit when these went in, it sounds like we can just remove these options completely and handle what is necessary internally. For example, if these classes need to be swapped out for cells, then when you enable cells, it can be done automatically internally instead of allowing anyone to replace these classes with anything.
Changed in nova: | |
assignee: | nobody → Yaguang Tang (heut2008) |
Changed in nova: | |
assignee: | nobody → Senhua Huang (senhuang) |
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-2 → 2013.2 |
Makes total sense to me - something like enable_zones=True should just automatically hook in the zones code