-
Sub-task
-
Resolution: Done
-
Medium
-
None
-
None
-
None
- [Script] Manual (scripts outside ONAP) Creation of dedicated K8s cluster for vFW service instantiation - The cluster is KUD instance with ovn4nfv, multus and virtlet plugins required fir vFW helm charts
- [AAI] Creation of configuration in AAI with (python script):
- Create Customer
- Create Owning-entity
- Create Platform
- Create Project
- Create Line Of Business
- [AAI] Registration of cloud region in AAI & k8s Plugin (python script):
- Create Complex
- Create Cloud Region
- Create Complex-Cloud Region Relationship
- Create Service
- Create Service Subscription
- Create Cloud Tenant
- Create Availability Zone
- [K8s Plugin] Upload Connectivity Info with kube-config generated in 1 (python script).
- [SO] Modify cloud-sites table in catalogdb (python script)
- [SDC] Create vFW Service Model (python script - python-onapsdk)
- Create VSP in SDC including helm packages (tar.gz) + CBA (zip). The helm packages should be visible as HELM type. VSP cannot have any HEAT templates associated
- [SDC] Create VF (Macro) by the import of VSP with HELM artifact type inside.
- [SDC] Edit VF properties by the inclusion of sdnc_artifact_name, sdnc_model_name, and sdnc_model_version parameters.
- [SDC] Set skip_post_instantiation_configuration flag to False
- [SDC] Create Service including VF with HELM artifact type
- [SDC] Distribute the service - Helm artifact should be uploaded into k8s plugin as new RB Definition, the service should be also visible in SO catalogdb
- [SO] Send first service instantiation request with Default RB Profile. (python script - python-onapsdk)
The- CDS creates configuration template with extra ssh service
- SO request must be completed successfully.
- SO should return successful result status only when all k8s resources are instantiated properly
- Verification of k8s resources with kubectl shows resources are instantiated properly. Status API is used in Config-Deploy operation to monitor the status of instantiated resources. Service creation is completed only when all resources are up and running
- Config-Deploy after verification of the status deploys extra ssh service over instantiation of the configuration template
- Service creation request must allow specifying parameter that will skip verification of the status of the creation of extra ssh-service
- [SO] Delete first service instance properly - all resources created must be deleted (python script - python-onapsdk)
- [SO] Send a second Service instantiation request with RB Profile that will create extra ssh service for vPGN.
- CDS uplods profile with extra ssh service
- SO request must be completed successfully.
- SO should return successful result status only when all k8s resources are instantiated properly
- Verification of k8s resources with kubectl shows resources are instantiated properly. Status API is used in Config-Deploy operation to monitor the status of instantiated resources. Service creation is completed only when all resources are up and running
- Service creation request must allow specifying parameter that will skip verification of the status of the creation of extra ssh-service
- [SO] Delete second service instance properly - all resources created must be deleted (python script - python-onapsdk)
- blocks
-
REQ-628 CNFO Integration Tests Honolulu
- Done