NetApp unified block storage driver

Registered by Navneet on 2013-04-23

The current netapp block storage drivers are divided based on the technology(nfs/iscsi and different storage families) used across multiple classes. This poses a problem or confusion at the end user level about which driver to configure and which one is the recommended one from netapp with recommended options. It also causes documentation mess as multiple driver classes which are growing during the period of time are required to be mentioned as part of the documentation and also configured at cinder backend at the time of usage.

The NetApp unified driver attempts to solve this problem by providing a single entry point driver class for different netapp storage families and storage protocols and can be configured with simple options. It is required to be built in a plug in style architecture to ease registering existing and new drivers without any significant code change. It gives the opportunity to provide recommended/default driver options while configuring a driver backend for cinder using a single netapp driver without the need to remember weird class names.

Blueprint information

Status:
Complete
Approver:
Duncan Thomas
Priority:
Low
Drafter:
Navneet
Direction:
Needs approval
Assignee:
Navneet
Definition:
New
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
Navneet on 2013-04-23
Completed by
Thierry Carrez on 2013-06-25

Related branches

Sprints

Whiteboard

Stalled by NetApp legal according to update from bswartz

Gerrit topic: https://review.openstack.org/#q,topic:bp/netapp-unified-driver,n,z

Addressed by: https://review.openstack.org/32564
    NetApp unified driver implementation.

Addressed by: https://review.openstack.org/33168
    NetApp unified driver implementation.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.