Extract CommonDBMixin into a separate module
Bug #1340145 reported by
Eugene Nikanorov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
Wishlist
|
Eugene Nikanorov | ||
Bug Description
Several service plugins are inheritig from CommonDBMixin which has a few utulity methods.
Right now CommonDBMixin resides in db_base_
In some cases it is undesirable and can lead to cycles in imports,
so CommonDBMixin needs to be extracted into a different module
| Changed in neutron: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to neutron (master) | #1 |
| Changed in neutron: | |
| status: | In Progress → Fix Committed |
| Changed in neutron: | |
| milestone: | none → juno-2 |
| status: | Fix Committed → Fix Released |
| Changed in neutron: | |
| milestone: | juno-2 → 2014.2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit cbd89e75d34c048
Author: Eugene Nikanorov <email address hidden>
Date: Wed Jul 9 14:47:01 2014 +0400
Extract CommonDBMixin to a separate file
db_
usually, so extract CommonDBMixin in different file.
Plus using db_base_plugin_v2 for some types of modules can lead to
cycles in imports, this refactoring should resolve the issue.
Closes-Bug: #1340145
Change-Id: Idb027d7c5cee2d