-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. Copyright (c) 2017-2018 VMware, Inc.
+..
+ This work is licensed under a Creative Commons Attribution 4.0
+ International License.
==========================
ONAP MultiCloud Test Guide
Test Examples
~~~~~~~~~~~~~
-The env HOST_IP is msb-iag service cluster-ip value is "10.43.188.78"(see it above).
+The env HOST_IP is msb-iag service cluster-ip value is "10.43.188.78"(see it
+above).
The vimid is "vmware_vio" the registered name in aai.
Get V2 auth token
-----------------
-# VIO openstack support keystone V2 version, vio proxy-plugin will check the request body format, if request body format
-# is keystone V2 format will access keystone V2 service, if not it will access keystone V3 service.
+# VIO openstack support keystone V2 version, vio proxy-plugin will check the
+request body format, if request body format
+# is keystone V2 format will access keystone V2 service, if not it will access
+keystone V3 service.
# this example show how to access keystone V2 service.
+
.. code-block:: console
$ curl -X POST -d @testV2.json -H 'Content-Type:application/json' http://$msb_address/api/multicloud/v0/<vimid>/identity/v2.0/tokens
Response:
-There are a large amounts of data including service endpoint, user information, etc.
-For our testing We take nova and identity service endpoint address and auth token which is in response header named “X-Subject-Token”.
+There are a large amounts of data including service endpoint, user information,
+etc.
+For our testing We take nova and identity service endpoint address and auth
+token which is in response header named “X-Subject-Token”.
-# you can find the endpoint url namespace is "api/multicloiud-vio/v0", it represent the multicloud-vio service, So
+# you can find the endpoint url namespace is "api/multicloiud-vio/v0", it
+represent the multicloud-vio service, So
requests sending to mulitcloud-vio will be forwarded to backend VIO openstack.
-Identity endpoint:
- http://$msb_address/api/multicloud-vio/v0/<vimid>/identity
+Identity endpoint::
+
+ http://$msb_address/api/multicloud-vio/v0/<vimid>/identity
+
+Nova endpoint::
-Nova endpoint:
- http://$msb_address/api/multicloud-vio/v0/<vimid>/nova/<user-tenantid>
+ http://$msb_address/api/multicloud-vio/v0/<vimid>/nova/<user-tenantid>
Get V3 auth token
"auth": sudo pip install virtualenv{
"scope": {"project": {"id": “<project-id>”}},
"identity":
- {
- "password": {"user": {"domain": {"name": “<doman-name>”}, "password": “<user-password>”, "name": “<user-name>”}}, "methods": ["password"]
- }
+ {
+ "password": {"user": {"domain": {"name": “<doman-name>”}, "password": “<user-password>”, "name": “<user-name>”}}, "methods": ["password"]
+ }
}
}
Response:
-There are a large amounts of data including service endpoint, user information, etc.
-For our testing We take nova and identity service endpoint address and auth token which is in response header named “X-Subject-Token”.
+There are a large amounts of data including service endpoint, user information,
+etc.
+For our testing We take nova and identity service endpoint address and auth
+token which is in response header named “X-Subject-Token”.
-# you can find the endpoint url namespace is "api/multicloiud-vio/v0", it represent the multicloud-vio service, So
+# you can find the endpoint url namespace is "api/multicloiud-vio/v0", it
+represent the multicloud-vio service, So
requests sending to mulitcloud-vio will be forwarded to backend VIO openstack.
-Identity endpoint:
- http://$msb_address/api/multicloud-vio/v0/<vimid>/identity
+Identity endpoint::
+
+ http://$msb_address/api/multicloud-vio/v0/<vimid>/identity
+
+Nova endpoint::
-Nova endpoint:
- http://$msb_address/api/multicloud-vio/v0/<vimid>/nova/<user-tenantid>
+ http://$msb_address/api/multicloud-vio/v0/<vimid>/nova/<user-tenantid>
List projects
$ curl -X GET -H 'X-Auth-Token:<token>' http://$msb_address/api/multicloud-vio/v0/<vimid>/glance/v2/tasks/<taskid>
-You can see the description and properties of task in response body,if 'status' is success, it will show image_id in
-result block.
+You can see the description and properties of task in response body,if 'status'
+is success, it will show image_id in result block.
query the image status by image_id