Proposal for Updating End-to-End Test Smoketests Using Python SDK

Slide Note
Embed
Share

Addressing the current scenario and problems encountered in running E2E tests for VNF. Proposals for a 3-stage E2E test setup, including test preparation, vendor and LCM creation, runtime complexities, and cloud region configurations. Suggestions for utilizing SO Openstack and MultiCloud VIM adapters, along with examples of E2E test topics and testcases involving various components.


Uploaded on Aug 07, 2024 | 1 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. Proposal E2E Test Update Smoketests using PythonSDK

  2. Current Scenario and problems vnf_* tests are started in parallel Each testcase creates pre-design and pre-runtime entries (e.g. vendor , cloudregion , Problems: Sometimes conflicts in vendor creation (same vendor exists twice) -> tests fail Tests, which would need changes in Component configuration (e.g. ONAP SO VNF Adapter Rest API endpoint version + CatalogDB entry) cannot be changed in between

  3. Proposal (a) 3 Stage-E2E tests 1. Test-Preparation Design -> Test- Vendor creation -> Test- LCM creation? Runtime -> Complex -> CloudRegion creation (Openstack+ K8S) A) via MultiCloudAAI incl. registration B) via AAI API (incl. esr, tenant, availability zone) -> Organisation in VID: OwningEntity , Project , Platform , LineOfBusiness in AAI: OwningEntity 2. E2E-tests using SO Openstack Adapters (ONAP SO VNF Adapter Rest API endpoint version v1 ) E.g. vnf_basic_vm Service including Openstack Neutron Network and other Openstack Objects (?) 3. E2E-tests using MultiCloud VIM Adapters (Change ONAP SO VNF Adapter Rest API endpoint to v2 and CatalogDB entry) Various Services -> using NBI (e.g. vnf_freeradius_nbi) -> incl. Multiple VSPs and VFs inside a Service (e.g. vnf_clearwater_ims) -> using CDS -> incl. CLAMP -> incl. K8S deployment

  4. Proposal (b) 2 Stage-E2E test (to be checked if possible) Preparation: in ONAP Installation (SO-override) create 2 cloud_site entries RegionOne (as today -> creates CatalogDB entry for usage of so-openstack-adapter) RegionTwo (same values as RegionOne, but ORCHESTRATOR = multicloud ) Set ONAP SO VNF Adapter Rest API endpoint to v2 1. Test-Preparation (as above), but Runtime -> CloudRegion -> RegionTwo 2. E2E-Tests (as in 2. and 3.), but Using RegionOne for so-openstack-adapter Using RegionTwo for multicloud openstack adapter

  5. E2E-Test-Topic Examples Stage Testcase Component Prepare Create Vendor, LCM SDC, AAI Prepare Create Complex, CloudRegion (via MultiCloudregistry) AAI, MultiCloud, MultiCloud Adapter,(ESR Server) Prepare Create Complex, CloudRegion (Manual) AAI Prepare Create Organisation VID, AAI E2E-SO Adapter (v1) vnf_basic_vm SDC (VSP Import, VF, Service Create, Distribute), SO, SO Adapter, SDNC (preload), DMAAP E2E-SO Adapter (v1) basic_network SDC (Service Create, Distribute), SO, SO Adapter (withoutHeatfile), DMAAP E2E-SO MultiCloudAdapter (v2) vnf_freeradius_nbi SDC (multiple VFs in Service), NBI SO, Multicloud, SDNC (preload), DMAAP E2E-SO MultiCloudAdapter (v2) vnf_xxx_cds SDC, CDS CBA Enrichment, SO, Multicloud, CDS Execution, SDNC, DMAAP E2E-SO MultiCloudAdapter (v2) vnf_xxx_cl SDC, SO, Multicloud, SDNC, DMAAP, DCAE, Policy, CLAMP

More Related Content