-
Story
-
Resolution: Done
-
Medium
-
None
-
None
The purpose of this test scenario is validate that APP-C successfully triggered the LCM API REBUILD via Doc Explorer (REST)
Interface/Method Name: LCM API REBUILD
Test Data: (example)
sample json request for LCM VM RESTART api:
{
"input" : {
"common-header" : {
"timestamp" : "2017-07-05T13:46:00.00Z",
"api-ver" : "2.01",
"originator-id" : "c09ac7d1-de62-0016-2000-e63702155502",
"request-id" : "c09ac7d1-de62-0016-2000-e63702155502",
"sub-request-id" : "150",
"flags" : {
"force" : "TRUE",
"ttl" : 60000
}
},
"action" : "Rebuild",
"action-identifiers" : {
"vnf-id" : "ibcx8888v"
},
"payload" : "{
\"vm-id\":\"http://IP_Address:8774/v2/1ce8eabeb0d3440995815a6d7e8e5934/servers/f890258c-543a-41bd-9c99-902d6dc48e62\",
\"identity-url\":\"http://IP_Address:5000/v2.0\",\"tenant-id\":\"1ce8eabeb0d3440995815a6d7e8e5934\"
}"
}
}
Pre-conditions/Dependencies:
Access to APPC ONAP Doc Explorer (REST API)
Validation Steps:
1) Access APPC ONAP doc explorer with valid login credential
2) Expand:
post: /operations/appc-provider-lcm:rebuild
3) Ensure "Response Content Type" = application/json is selected
4) Input the json request for VM REBUILD (see sample in Test Data into the "Value" field
Note: Ensure the "Timestamp" is current with server's time; data for the requested vnf-id existed in A&AI db
5) Click the "Try it out!" button
6) Check the "Response Body" section for results. Inspect the logs (karaf.log, appc-debug.log)
Validation Notes:
Testers might want to check the "Action Log" in openstack dashboard for the actual result.
- mentioned in
-
Page Loading...