Allow Cisco ML2 driver to use the upstream ncclient
Bug #1352635 reported by
Juergen Brendel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Juergen Brendel | ||
Icehouse |
New
|
Undecided
|
Unassigned |
Bug Description
Currently, the Cisco ML2 driver relies on a specially patched and maintained custom version of the ncclient 3rd party library for communication with various switches.
Changes have been submitted to the upstream ncclient now so that there is no need to maintain a separate version of the ncclient anymore.
To take advantage of the new ncclient version, a small change needs to be made to the Cisco ML2 driver, so that it can detect whether the old (custom) ncclient is installed, or whether the new upstream ncclient is used.
Installation and maintenance will be simplified by not requiring a custom version of the ncclient.
Changed in neutron: | |
assignee: | nobody → Juergen Brendel (jbrendel) |
Changed in neutron: | |
milestone: | none → juno-3 |
importance: | Undecided → Medium |
tags: | added: cisco |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/112175
Review: https:/