Refactor of the Neutron network adapter
Through accretion, the Network API adapter for Neutron has become prohibitively difficult to maintain, debug and extend. In order to improve interoperability of Nova and Neutron, this code must be refactored to:
* Make it easier to understand.
* Make it easier to test effectively.
* Encourage extension through acceptable coding and design practices and idioms.
Blueprint information
- Status:
- Not started
- Approver:
- John Garbutt
- Priority:
- Undefined
- Drafter:
- Brent Eagles
- Direction:
- Needs approval
- Assignee:
- Brent Eagles
- Definition:
- Pending Approval
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Refactor allocate_
Addressed by: https:/
Refactor of the Neutron network adapter
--
These specs are -2'ed because this blueprint is approved per the 'wrapper spec' but where is that? Should this blueprint be abandoned or at least made dependent on the 'wrapper' blueprint so we're not completely lost on what's going on here for design plans and documentation of the specs in Liberty? I'm specifically interested in how the 'wrapper' is going to work, i.e. wrap neutronclient, use the sdk, or roll our own service layer like tempest? And also wondering about test details.
-- mriedem 2015/05/19
https:/
Wrap Neutron client calls
Amended by: https:/
Given the confusion here, I am removing this from liberty while we understand what the state of all these BPs actually is. --johnthetubaguy 22nd June 2015
Additional refactory stuff:
https:/
https:/
I'm not quite sure how you want to progress this, but they seem to fit in the same shaped hole. -- ijw
