What is ETSI?
...
There are three tests currently being run "Distribute Service Template", "Invoke Service Instantiation" and "Invoke VNF Instantiation".
Distribute Service Template
As the name would suggest the aim for the "Distribute Service Template" test is to distribute a service template within the SDC controller pod. Once a http session of the SDC controller is created a post request can be made to it. This post requests sends binary data from "distributeServiceTemplate.json". This json file contains resources and artifacts required to distribute a service. Once this post request is sent, the response status code is checked to see if it is 200. If the code is not equal to 200 then the test is thought to be a failure.
Invoke Service Instantiation
The aim of the "Invoke Service Instantiation" test is to invoke the service distributed to the sdc controller in the previous test. A http session of the api handler pod is created. This session is sent a post request containing "serviceInstantiationRequest.json". Once this request is made the response is checked if it a valid code is returned. A for loop is used to continually make calls to check the orchestration request, to check the status of service instantiation. Only once this orchestration returns either a fail or success, will we break out of the for loop.Once outside the for loop a final statement is used to check if service has been successfully instantiated.
Invoke VNF Instantiation
The aim of "Invoke VNF Instantiation" test is to now instantiate the VNF that relates to service in the previous test. This test requires the ID of the service instance created in the previous test. If this is not provided then the test will fail from the get go. Once again a http session of the api handler pod is created. Similarly a post request using the json data within "vnfInstantiationRequest.json". Once this request is made if it returns a success code then the test moves on to a for loop. Within this for a loop an orchestration request is made each time, when this request signals that either the instantiation request has failed or fully succeeded then the loop is escaped. The test will either be a pass or fail depending on this final orchestration request.
Troubleshooting
There are a number of simple issues which can
Issues relating from Python and its libraries
A correct installation of the robot framework to run our tests requiring python and the following pip libraries.
Configuration
Troubleshooting
- robotframework
- robotframework-extendedselenium2library
- robotframework-httplibrary
- robotframework-onap
- robotframework-requests
- robotframework-selenium2library
To make sure each of the previous libraries is installed run the following command
| Code Block |
|---|
pip -list |