Bug 1142043

Summary: [RFE][cinder]: NetApp Cinder driver refactoring, phase 1
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: eharney, markmc, scohen, yeylon
Target Milestone: Upstream M1Keywords: CodeChange, FutureFeature, OtherQA
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/cinder/+spec/netapp-cinder-driver-refactoring-phase-1
Whiteboard: upstream_milestone_kilo-1 upstream_definition_approved upstream_status_implemented
Fixed In Version: openstack-cinder-2015.1.0-2.el7ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:13:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-09-16 04:07:35 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/netapp-cinder-driver-refactoring-phase-1.

Description:

NetApp's five Cinder drivers have been in continuous development for nearly 3 years, and it would seem necessary to do some housecleaning.  The first phase will include splitting long files that contain multiple classes, normalizing the class hierarchies to enable subclassing different driver classes (ISCSIDriver, FibreChannelDriver), and renaming classes.  Later phases will move unit test files into a matching hierarchy in the "tests" tree, improve SDK usage, standardize data motion tasks, and generally clean up existing code; separate blueprints will be submitted for those.

Specification URL (additional information):

https://etherpad.openstack.org/p/NetApp_driver_refactoring,_phase_1

Comment 7 errata-xmlrpc 2015-08-05 13:13:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548