Bug 1042482

Summary:	[RFE][neutron]: Create a fake netconf client for Cisco nexus unit tests
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/cisco-nexus-fake-ncclient
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_superseded
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:03:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 22:24:51 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/cisco-nexus-fake-ncclient.

Description:

Unit testing of the Cisco plugin currently involves the use of a fake Cisco nexus sub-plugin as a replacement of the real Cisco nexus sub-plugin. Because of this, the real Cisco nexus sub-plugin is not getting exercised as part of unit tests. If the netconf client (the ncclient module) is faked for unit testing instead of the nexus driver, then the nexus driver code can be included in unit tests.

Specification URL (additional information):

None