The purpose of this test scenario is validate that APP-C successfully triggered the LCM API START via Doc Explorer (REST)

nterface/Method Name:  LCM API START

Test Data: (example)
 sample json request for LCM VNF START api:
{
"input" : {
"common-header" : {
"timestamp" : "2017-07-31T18:16:05.464Z",
"api-ver" : "2.00",
"originator-id" : "SDNGP",
"request-id" : "6c960af0-747a-4a13-98f3-6e105a2c932c",
"sub-request-id" : "6c960af0-747a-4a13-98f3-6e105a2c932c",
"flags" : {
"mode" : "NORMAL",
"force" : "TRUE",
"ttl" : 3600
}
},
"action" : "Start",
"action-identifiers" : {
"vnf-id" : "comx9906v"
},
"payload" : "{\"request-parameters\":{\"vnf-name\":\"comx9906v\",\"vnf-host-ip-address\":\"https://IP_Address:8080/Dispatch/\"},\"configuration-parameters\":{\"vnf_instance\":\"comx9906v\"}}"
}
}

Pre-conditions/Dependencies:
Access to APPC ONAP Doc Explorer (REST API)
VM is in "Stopped" or "shutdown" state

Validation Steps:
1) Access APPC ONAP doc explorer with valid login credential
2) Expand:  
post: /operations/appc-provider-lcm:start
3) Ensure "Response Content Type" = application/json is selected
4) Input the json request for VM START (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.