Ask Your Question
0

How the NetApp API works with cinder?

asked 2014-09-24 07:19:27 -0500

Beny gravatar image

updated 2014-10-03 01:50:12 -0500

I have attached a netapp nfs volume to the cinder storage and it is working as expected. I need to know how it actually works whether through API or anything else, to create or delete the volumes.
I have found in the ssc_utils.py file with the below API names.

api_name='net-interface-get-iter'       
api_name='system-user-capability-get-iter'  
api_name='volume-get-iter'          
api_name='aggr-options-list-info'       
api_name='sis-get-iter'             
api_name='snapmirror-get-iter'          
api_name='storage-disk-get-iter'

Not sure whether these api commands are being used.

Any help would be appreciated

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
1

answered 2014-09-25 09:40:24 -0500

lgreg gravatar image

hello, Please refer to the Guide at the following link. http://netapp.github.io/openstack-deploy-ops-guide/icehouse/content/ (http://netapp.github.io/openstack-dep...)

Some of the items you list are used to ensure the user has appropriate RBAC capability and some are used if/when Extra-Specs are provided as requirements for the Cinder Volume creation. The Extra-specs provides ability to define Cinder Volume characteristics, which the Driver will identify the proper backend to meet those Extra-Specs requirements.

Look at the sections in regards to Cinder, as well as CLI in the discussion around Volume Types, and some of the extra specs available within the link provided.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-09-24 07:19:27 -0500

Seen: 203 times

Last updated: Sep 25 '14