diff options
Diffstat (limited to 'docs')
-rw-r--r-- | docs/testing/user/testspecification/vnf/index.rst | 83 |
1 files changed, 80 insertions, 3 deletions
diff --git a/docs/testing/user/testspecification/vnf/index.rst b/docs/testing/user/testspecification/vnf/index.rst index 43f6cd0c..4b43e7d3 100644 --- a/docs/testing/user/testspecification/vnf/index.rst +++ b/docs/testing/user/testspecification/vnf/index.rst @@ -23,9 +23,13 @@ References This test area references the following specifications and guides: -- Functest repo for detailed description of the below testcases +- Functest repo for detailed description of the vEPC testcase - - https://github.com/opnfv/functest/blob/master/docs/testing/user/userguide/test_details.rst + - https://github.com/opnfv/functest/blob/master/docs/testing/user/userguide/test_details.rst#juju_epc + +- Functest repo for detailed description of the vIMS testcase + + - https://github.com/opnfv/functest/blob/master/docs/testing/user/userguide/test_details.rst#cloudify_ims - 3GPP LTE @@ -39,6 +43,10 @@ This test area references the following specifications and guides: - https://www.rebaca.com/abot-test-orchestration-tool/ +- Cloudify clearwater: opnfv-cloudify-clearwater [1] + + - https://github.com/Orange-OpenSource/opnfv-cloudify-clearwater + Definitions and abbreviations ============================= @@ -49,6 +57,7 @@ area - 3GPP - 3rd Generation Partnership Project - EPC - Evolved Packet Core - ETSI - European Telecommunications Standards Institute +- IMS - IP Multimedia Core Network Subsystem - LTE - Long Term Evolution - NFV - Network functions virtualization - OAI - Open Air Interface @@ -128,7 +137,7 @@ Test execution * Test action 3: Execution of ABot feature files triggered by Juju actions. This executes a suite of LTE signalling tests on the OAI EPC. * Test action 4: ABot test results are parsed accordingly. -* Test action 5: The deployed VMS are deleted. +* Test action 5: The deployed VMs are deleted. Pass / fail criteria @@ -147,3 +156,71 @@ Post conditions --------------- The clean-up operations are run. + +---------------------------------------------------------------- +Test Case 2 - vIMS +---------------------------------------------------------------- + +Short name +---------- + +dovetail.vnf.vims + +Use case specification +---------------------- + +The IP Multimedia Subsystem or IP Multimedia Core Network Subsystem (IMS) is +an architectural framework for delivering IP multimedia services. + +vIMS test case is integrated to demonstrate the capability to deploy a +relatively complex NFV scenario on top of the OPNFV infrastructure. + +Example of a real VNF deployment to show the NFV capabilities of the platform. +The IP Multimedia Subsytem is a typical Telco test case, referenced by ETSI. +It provides a fully functional VoIP System. + +Test preconditions +------------------ + +Certain ubuntu server and cloudify images version refer to dovetail testing user guide. + +At least 30G RAMs and 50 vcpu cores required. + +Basic test flow execution description and pass/fail criteria +------------------------------------------------------------ + +vIMS has been integrated in Functest to demonstrate the capability to deploy +a relatively complex NFV scenario on the OPNFV platform. The deployment of a +complete functional VNF allows the test of most of the essential functions +needed for a NFV platform. + + +Test execution +'''''''''''''' +* Test action 1: Deploy a VNF orchestrator (Cloudify). +* Test action 2: Deploy a Clearwater vIMS (IP Multimedia Subsystem) VNF from + this orchestrator based on a TOSCA blueprint defined in repository of + opnfv-cloudify-clearwater [1]. +* Test action 3: Run suite of signaling tests on top of this VNF +* Test action 4: Collect test results. +* Test action 5: The deployed VMs are deleted. + + +Pass / fail criteria +'''''''''''''''''''' + +The VNF orchestrator (Cloudify) should be deployed successfully. + +The Clearwater vIMS (IP Multimedia Subsystem) VNF from this orchestrator +should be deployed successfully. + +The suite of signaling tests on top of vIMS should be run successfully. + +The test scenarios on the NFV platform should be executed successfully following +the ETSI standards accordingly. + + +Post conditions +--------------- + +All resources created during the test run have been cleaned-up |