...
- Create new java package for VNF-LCM testing in VNFSDK
- Create new scenario in VTP called "lfn-ovp-vnf"
- Create new testsuite in VTP named "vnf-validation" under scenario "lfn-ovp-vnf"
- Add new test case with name "onap-vnf-lcm" under testsuite "vnf-validation" with following details
- Execution block : use script to run the LCM testing using ONAP CLI
Inputs: Update the script to take following additional parameters as arguments if not available from config file
parameter name description config entry action notes request_id On every testing, to track the progress and results, this parameter is added NA - update all oclip command used in the script with --request-id parameter with value given using this request-id.
vnf_csar_path TOSCA VNF CSAR used for testing.
SDC will upload this file to VTP using execute API and VTP will store it in local file system and use it while invoking the script with this parameter.
vnfs.vgw.path
- comment this property in config file
- update the script to use the value given using this parameter instead from config file
ns_csar_path TOSCA NSCSAR used for testing.
SDC will upload this file to VTP using execute API and VTP will store it in local file system and use it while invoking the script with this parameter.
vnfs.vgw.path
- comment this property in config file
- update the script to use the value given using this parameter instead from config file
Optional.
vnf_csar_iddynamically generated CSAR ID (uuid)ns. csar-idTBDNot required as input. After step-3, CLI will find the csar id and use it step 6. ns_csar_iddynamically generated CSAR ID (uuid)vnfs.vgw.csar-idTBD- Outputs: Update the script to produce following outputs
Output description action notes vnf-id VNF ID update the script to generate the output json with this value ns-id NS ID update the script to generate the output json with this value vnf_status VNF status update the script to report the status of VNF stretch goal ns_status NSstatus update the script to report the status of NS stretch goalTBD NOTE: Once VNF is created, how to test the health of VNF, these outputs would be useful, if VFC provides health check REST API for given VNF
- Errors: Update the script to write the errors in error stream, so that OCLIP will automatically read it. Use the format : <error-code>: <error-message>
...
/v1/vtp/executions?request-id=<uuid>
-- Already supported
Options
Currently every action is available as indivual test cases and to run complete LCM operation including on-boarding and instantiation, this automation script to be modelled as test case, so complete LCM actions could be executed in one shot. so OVP can invoke these test cases either direclty invoking given LCM action or as a whole operation.
...