Hi Eswar,
I don’t know exactly how you performed those actions, but I can
put my test here:
ubuntu@vm0-robot:~$ export
MULTICLOUD_PLUGIN_ENDPOINT=http://10.0.14.1:80/api/multicloud-titanium_cloud/v0/pod25_RegionOne
ubuntu@vm0-robot:~$ curl -v -s -H "Content-Type: application/json" -X POST -d
'{"auth": {"tenantName": "xxx", "passwordCredentials": {"username": "yyy",
"password": "zzz"}}}' $MULTICLOUD_PLUGIN_ENDPOINT/identity/v2.0/tokens
* Trying 10.0.14.1...
* Connected to 10.0.14.1 (10.0.14.1) port 80 (#0)
> POST /api/multicloud-titanium_cloud/v0/pod25_RegionOne/identity/v2.0/tokens
> HTTP/1.1
> Host: 10.0.14.1
> User-Agent: curl/7.47.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 119
>
* upload completely sent off: 119 out of 119 bytes
< HTTP/1.1 200 OK
< Server: openresty
< Date: Tue, 16 Jan 2018 03:22:25 GMT
< Content-Type: application/json
< Transfer-Encoding: chunked
< Connection: keep-alive
< Vary: Cookie
< X-Frame-Options: SAMEORIGIN
< Allow: GET, POST, HEAD, OPTIONS
<
{"access":{"token":{"issued_at":"2018-01-16T03:22:26.000000Z","expires":"2018-01-16T04:22:26.000000Z","id":"7c463130b2ad403ea14c85352243c495","tenant":
ubuntu@vm0-robot:~$ export TOKEN=7c463130b2ad403ea14c85352243c495
ubuntu@vm0-robot:~$ curl -v -s -H "Content-Type: application/json" -H
"X-Auth-Token: $TOKEN" -X GET
$MULTICLOUD_PLUGIN_ENDPOINT/orchestration/v1/c7738ddc4c414303b8960048a16b7fc6/stacks
* Trying 10.0.14.1...
* Connected to 10.0.14.1 (10.0.14.1) port 80 (#0)
> GET
> /api/multicloud-titanium_cloud/v0/pod25_RegionOne/orchestration/v1/c7738ddc4c414303b8960048a16b7fc6/stacks
> HTTP/1.1
> Host: 10.0.14.1
> User-Agent: curl/7.47.0
> Accept: */*
> Content-Type: application/json
> X-Auth-Token: 7c463130b2ad403ea14c85352243c495
>
< HTTP/1.1 200 OK
< Server: openresty
< Date: Tue, 16 Jan 2018 03:23:30 GMT
< Content-Type: application/json
< Transfer-Encoding: chunked
< Connection: keep-alive
< X-Subject-Token: 7c463130b2ad403ea14c85352243c495
< Vary: Cookie
< X-Frame-Options: SAMEORIGIN
< Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
<
* Connection #0 to host 10.0.14.1 left intact
{"stacks":[{"description":"","parent":null,"deletion_time":null,"stack_name":"onap.d","stack_user_project_id":"92d4d1230d254a8185f989a15b459aad","stack_status_reason":"Stack
CREATE completed
successfully","creation_time":"2018-01-16T02:27:25Z","links":[{"href":"http://10.0.14.1:80/api/multicloud-titanium_cloud/v0/pod25_RegionOne/orchestration/v1/c7738ddc4c414303b8960048a16b7fc6/stacks/onap.d/8e50c023-8caf-4c7e-9601-f4821a3fe7d0","rel":"self"}],"updated_time":"2018-01-16T02:27:25Z","stack_owner":null,"stack_status":"CREATE_COMPLETE","id":"8e50c023-8caf-4c7e-9601-f4821a3fe7d0","tags":null}]}
Best Regards,
Bin Yang, Solution Readiness Team, Wind River
Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189
Skype: yangbincs993
From: ESWAR RAO [mailto:[email protected]]
Sent: Tuesday, January 16, 2018 8:26 AM
To: Yang, Bin
Cc: [email protected]
Subject: Re: [onap-discuss] [Multicloud] Heat not getting listed in swagger url
Hi Bin,
Thanks for the help.
I have tried with keystone v2.0 token and issued the below call,
curl -v -s -H "Content-Type: application/json" -H "X-Auth-Token:$TOKEN" -X
GET http://192.168.21.212:80/api/multicloud/v0/radisys_mec/
orchestration/v1/323b4f23d58143d29a81cd4adb6ade3b/stacks<http://192.168.21.212:80/api/multicloud/v0/radisys_mec/%20orchestration/v1/323b4f23d58143d29a81cd4adb6ade3b/stacks>
it gives,
* About to connect() to 192.168.21.212 port 80 (#0)
* Trying 192.168.21.212...
* Connected to 192.168.21.212 (192.168.21.212) port 80 (#0)
> GET
> /api/multicloud/v0/radisys_mec/orchestration/v1/323b4f23d58143d29a81cd4adb6ade3b/stacks
> HTTP/1.1
User-Agent: curl/7.29.0
Host: 192.168.21.212
Accept: */*
Content-Type: application/json
X-Auth-Token:gAAAAABaXKre8_O5Y4TuTLMYxIzr6w9u9VAEX2i8G8WMs_zwQLvQ4_1cYaKUFjBxMuq23DKB0Ps40bmnkqGoi0_QaQJ_bJyksCqJRmw0O6AAiF6okezB9teYZLyt08iscEqMZnbhOv88OZVFnGODf7wfIkHwFN-t7Dwa88KEvGBuSaIoK1WVWA0
HTTP/1.1 403 Unknown Status Code
Server: openresty
Date: Mon, 15 Jan 2018 13:30:12 GMT
Content-Type: application/json
Content-Length: 58
Connection: keep-alive
status: 403
Vary: Cookie
content-encoding: gzip
Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
x-frame-options: SAMEORIGIN
* Connection #0 to host 192.168.21.212 left intact
{"detail":"Authentication credentials were not provided."}
Where TOKEN=
gAAAAABaXKre8_O5Y4TuTLMYxIzr6w9u9VAEX2i8G8WMs_zwQLvQ4_1cYaKUFjBxMuq23DKB0Ps40bmnkqGoi0_QaQJ_bJyksCqJRmw0O6AAiF6okezB9teYZLyt08iscEqMZnbhOv88OZVFnGODf7wfIkHwFN-t7Dwa88KEvGBuSaIoK1WVWA0
FYI, the above call is not even reaching registered VIM heat-api.
Thanks
Eswar Rao
On Mon, Jan 15, 2018 at 3:39 PM, Yang, Bin
<[email protected]<mailto:[email protected]>> wrote:
Hi Eswar,
The heat API was not listed yet, it requires multiple steps.
You can try with following URI prefix for heat APIs:
http://onap-multi-service:80/api/multicloud-ocata/v0/vimid/orchestration/v1/<project-id>
So to list the stack, you can refer to following commands:
export MULTICLOUD_PLUGIN_ENDPOINT=
http://onap-multi-service:80/api/multicloud-ocata/v0/radisys_mec
curl -v -s -H "Content-Type: application/json" -X POST -d '{"auth":
{"tenantName": "<your tenant name>", "passwordCredentials": {"username": "<your
username>", "password": "<your password>"}}}'
$MULTICLOUD_PLUGIN_ENDPOINT/identity/v2.0/tokens
export TOKEN= <TOKEN returned by issuing command above>
export PROJECT_ID = <your project id>
curl -v -s -H "Content-Type: application/json" -H "X-Auth-Token: $TOKEN" -X
GET $MULTICLOUD_PLUGIN_ENDPOINT/orchestration/v1/$PROJECT_ID/stacks
Best Regards,
Bin Yang, Solution Readiness Team, Wind River
Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189
Skype: yangbincs993
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of ESWAR RAO
Sent: Monday, January 15, 2018 4:47 PM
To: [email protected]<mailto:[email protected]>
Subject: [onap-discuss] [Multicloud] Heat not getting listed in swagger url
Hi All,
Can some one please help me in en-listing HEAT with multicloud for a registered
VIM.
I have summarized the issue.
When we issue request as per online documentation,
http://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/Multicloud-Fake_Cloud-Guide.html
http://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-Test-Guide.html#list-instance-of-users-project
http://
onap-multi-service:80/api/multicloud-ocata/v0/vimid/nova/323b4f23d58143d29a81cd4adb6ade3b/servers/
HTTP/1.1 500 Internal Server Error
Server: openresty
Date: Mon, 15 Jan 2018 07:06:14 GMT
Content-Type: application/json
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Cookie
X-Frame-Options: SAMEORIGIN
Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
response
{"error":"invalid cached metadata"}
When we issue request as per swagger gui, it works. (Attached)
Eventhough HEAT is installed on the VIM, it is not listed in the swagger and I
am getting the below error
http://
onap-multi-service:80/api/multicloud-ocata/v0/radisys_mec/323b4f23d58143d29a81cd4adb6ade3b/stacks/
HTTP/1.1 404 Not Found
Server: openresty
…
<p>
Using the URLconf defined in <code>ocata.urls</code>,
Django tried these URL patterns, in this order:
</p>
…..
<p>The current URL,
<code>api/multicloud-ocata/v0/radisys_mec/323b4f23d58143d29a81cd4adb6ade3b/stacks/</code>,
didn't match any of these.</p>
Thanks
Eswar Rao
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
