Ask Your Question

Jorge88's profile - activity

2018-10-30 10:56:46 -0600 asked a question 3Par: error conect api with cinder volume

Hi all:

I trying to connect a storage 3par 8400 to cinder volume version 11.1.2. But I get the following errors:

  1. Cinder Connects to 3PAR correctly

REQ: curl -i https: // 3parIP: 8080 / api / v1 / credentials -X POST -H "Content-Type: application / json" -H "Accept: application / json" -H "User-Agent: python- 3parclient "

RESP: {'status': '201' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Location': '/ api / v1 / credentials / 0-7e98fea1623c58abba88e85915022806-1f8ebd5b' 'Pragma': 'no-cache' 'Cache-Control': 'no-cache' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT' 'Content-Type': 'application / json'}

 RESP BODY: {"key": "0-7e98fea1623c58abba88e85915022806-1f8ebd5b"}

  1. Cinder tries to validate the "url or API context" / api / v1 / system and gets a 500 error on the side of the 3PAR

REQ: curl -i https: // 3parIP: 8080 / api / v1 / system -X GET -H "X-Hp3Par-Wsapi-Sessionkey: 0-7e98fea1623c58abba88e85915022806-1f8ebd5b" -H "Accept: application / json" -H " User-Agent: python-3parclient "

RESP: {'status': '500' 'content-location': u'https: // 3parIP: 8080 / api / v1 / system ' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT' 'Content-Type': 'application / json'}

 RESP BODY: {"code": 1, "desc": "internal server error"}

  1. Cinder disconnects

REQ: curl -i https: // 3parIP: 8080 / api / v1 / credentials / 0-7e98fea1623c58abba88e85915022806-1f8ebd5b DELETE -H "X-Hp3Par-Wsapi-Sessionkey: 0-7e98fea1623c58abba88e85915022806-1f8ebd5b" -H "Accept: application / json "-H" User-Agent: python-3parclient "

RESP: {'status': '200' 'content-location': u'https: // 3parname: 8080 / api / v1 / credentials / 0-7e98fea1623c58abba88e85915022806-1f8ebd5b ' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Pragma': 'no-cache' 'Cache-Control': 'no-cache' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT'}

  1. Cinder reconnects to 3PAR correctly to validate CPG

REQ: curl -i https: // 3parIP: 8080 / api / v1 / credentials -X POST -H "Content-Type: application / json" -H "Accept: application / json" -H "User-Agent: python- 3parclient "

RESP: {'status': '201' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Location': '/ api / v1 / credentials / 0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b' 'Pragma': 'no-cache' 'Cache-Control': 'no-cache' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT' 'Content-Type': 'application / json'}

  1. Cinder makes the call to CPG and 3PAR API says again error 500

REQ: curl -i https: // 3parIP: 8080 / api / v1 / cpgs / FC_r5_OS -X GET -H "X-Hp3Par-Wsapi-Sessionkey: 0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b" -H "Accept: application / json" - H "User-Agent: python-3parclient" RESP: {'status': '500' 'content-location': u'https: // 3parIP: 8080 / api / v1 / cpgs / FC_r5_OS ' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT' 'Content-Type': 'application / json'}

RESP BODY: {"code": 1, "desc": "internal server error"}

  1. Cinder eliminates the session

REQ: curl -i https: // 3parIP: 8080 / api / v1 / credentials / 0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b DELETE -H "X-Hp3Par-Wsapi-Sessionkey: 0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b" -H "Accept: application / json "-H" User-Agent: python-3parclient " _http_log_req /usr/lib/python2.7/site-packages/hpe3parclient/http.py:169

RESP: {'status': '200' 'content-location': u'https: // 3parIP: 8080 / api / v1 / credentials / 0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b ' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Pragma': 'no-cache' 'Cache-Control': 'no-cache' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT'}

The parameters that we are using in cinder.conf:

volume_driver = cinder.volume.drivers.hpe.hpe_3par_fc.HPE3PARFCDriver hpe3par_api_url = https: // 3parIP: 8080 / api / v1 hpe3par_username = 3paruser hpe3par_password = 3parpassword hpe3par_debug = true san_ip = 3parIP san_login = 3paruser san_password = 3parpassword volume_backend_name = 3parfcrep hpe3par_cpg = CPGname

Where 3paruser is a user with the "edit" role.

Any ideas?

2018-10-30 10:56:39 -0600 answered a question Volume creation error for 3PAR and LHN using Volume TYPE

Hello: What is the difference between the parameters hp3par_username and san_login to integrate with an HPE 3PAR storage ?. I reviewed for the hpe3par_username parameter is a 3par user with the role of "edit" is needed. But for the other parameter that user and permissions need ?. In the documentation the user indicates 3paradm of 3Par, but does not mention what type of permissions they need to be able to generate an alternate user with the permissions that are needed.

https://docs.openstack.org/ocata/config-reference/block-storage/drivers/hpe-3par-driver.html (https://docs.openstack.org/ocata/conf...)

2018-10-29 18:16:37 -0600 asked a question 3PAR_It can't be integrated with StoreServ 8400

Hello:

We are having problems with integrating the HPE 3Par StoreServ 8400 storage with Openstack/Cinder (Cinder version 11.1.2). The messages are the following:

  1. Cinder connects to 3PAR correctly

REQ: curl -i https://3parIP:8080/api/v1/credentials -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-3parclient"

RESP:{'status': '201' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Location': '/api/v1/credentials/0-7e98fea1623c58abba88e85915022806-1f8ebd5b' 'Pragma': 'no-cache' 'Cache-Control': 'no-cache' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT' 'Content-Type': 'application/json'}

RESP BODY:{"key":"0-7e98fea1623c58abba88e85915022806-1f8ebd5b"}

  1. Cinder tries to validate the "url or API context" /api/v1/system and gets a error 500 on the side of the 3PAR.

REQ: curl -i https://3ParIP:8080/api/v1/system -X GET -H "X-Hp3Par-Wsapi-Sessionkey: 0-7e98fea1623c58abba88e85915022806-1f8ebd5b" -H "Accept: application/json" -H "User-Agent: python-3parclient"

RESP:{'status': '500' 'content-location': u'https://hp_3par_mxn6202k4s:8080/api/v1/system' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT' 'Content-Type': 'application/json'}

RESP BODY:{"code":1,"desc":"internal server error"}

  1. Cinder disconnects

REQ: curl -i https://3ParIP:8080/api/v1/credentials/0-7e98fea1623c58abba88e85915022806-1f8ebd5b (https://3ParIP:8080/api/v1/credential...) DELETE -H "X-Hp3Par-Wsapi-Sessionkey: 0-7e98fea1623c58abba88e85915022806-1f8ebd5b" -H "Accept: application/json" -H "User-Agent: python-3parclient"

RESP:{'status': '200' 'content-location': u'https://hp_3par_mxn6202k4s:8080/api/v1/credentials/0-7e98fea1623c58abba88e85915022806-1f8ebd5b' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Pragma': 'no-cache' 'Cache-Control': 'no-cache' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT'}

  1. Cinder reconnects to 3PAR correctly to validate the CPG

REQ: curl -i https://3ParIP:8080/api/v1/credentials -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-3parclient"

RESP:{'status': '201' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Location': '/api/v1/credentials/0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b' 'Pragma': 'no-cache' 'Cache-Control': 'no-cache' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT' 'Content-Type': 'application/json'}

  1. Cinder makes the call to the CPG and 3PAR API says again error 500.

REQ: curl -i https://3ParIP:8080/api/v1/cpgs/CPG1 -X GET -H "X-Hp3Par-Wsapi-Sessionkey: 0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b" -H "Accept: application/json" -H "User-Agent: python-3parclient" RESP:{'status': '500' 'content-location': u'https://3ParIP:8080/api/v1/cpgs/CPG1' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT' 'Content-Type': 'application/json'}

RESP BODY:{"code":1,"desc":"internal server error"}

  1. Cinder delete the session.

REQ: curl -i https://3ParIP:8080/api/v1/credentials/0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b (https://3ParIP:8080/api/v1/credential...) DELETE -H "X-Hp3Par-Wsapi-Sessionkey: 0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b" -H "Accept: application/json" -H "User-Agent: python-3parclient" _http_log_req /usr/lib/python2.7/site-packages/hpe3parclient/http.py:169

RESP:{'status': '200' 'content-location': u'https://3ParIP:8080/api/v1/credentials/0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b' 'Server': 'hp3par-wsapi' 'Connection': 'close' 'Pragma': 'no-cache' 'Cache-Control': 'no-cache' 'Date': 'Wed, 10 Oct 2018 05:29:03 GMT'}

We are using the following parameters in cinder:

Driver: cinder.volume.drivers.hpe.hpe_3par_fc.HPE3PARFCDriver

Options: hpe3par_api_url=https://3parIP:8080/api/v1 hpe3par_username=3parusername hpe3par_password=3parpassword hpe3par_cpg=CPG1 san_ip=3ParIP san_login=3parusername san_password=3parpassword max_over_subscription_ratio=10.0 reserved_percentage=15 image_volume_cache_enabled = True hpe3par_debug = true

3parusername is a user with the "edit" role. The OS version of the 3par is 3.3.1 (MU2).

Also, I tried to configure with a HPE 3Par StoreServ 7400 (OS version: 3.2 ... (more)