ONAP Dublin Deployment Components necessary for the vFW &
...
VLB use case with CDS:
In order to run the vDNS VLB with CDS use case, we need an ONAP Dublin Release instance that includes the following components::
| ONAP Component Name | Description | |
|---|---|---|
| A&AI | Required for Inventory Cloud Owner, Customer, Owning Entity, Service, Generic VNF, VF Module | |
SDC | VSP , VF, and Service Modeling of the vDNSVLB | |
| DMAAP | Distribution of the CSAR to all ONAP components | |
| SO | Requires for Macro Orchestration using the generic building blocks. | |
SDNC needs to include:
| Used for ONAP E2E Zero Touch Declarative Provisioning & Configuration Management for VNF/CNF/PNF. | |
| Policy | Used to Store Naming Policy | |
| VID | Used for User Interface for Run Time Execution of the Marco Instantiation flow. | |
| AAF | Used for Authentication and Authorization of requests | |
| Portal | Used for accessing the ONAP Components GUI like SDC, VID, etc ... | |
| Robot | Used for running automated tasks, like provisioning cloud customer, cloud region, service subscription, etc ... | |
| Shared Cassandra DB | Used as a shared storage for ONAP components that rely on Cassandra DB, like AAI | |
| Shared Maria DB | Used as a shared storage for ONAP components that rely on Maria DB, like SDNC, and SO |
...
As we can see in the override.yaml file above, we can enable or disable the deployment of a specific ONAP component, and in our case, we enabled only the necessary components to run the vDNS VLB demo.
We can also see that we can configure the parameters needed for the use case to run, like OpenStack Username, Passowrd, Region, Tenant, Image Names, and Flavors.
...
We will need to apply a few modifications to the deployed ONAP Dublin instance in order to run the vDNS VLB use case:
Initialize cloud account:
...
In case the policy is missing, we can manually create and push the SDNC Naming policy. El Alto E2E Automation vLB w/ CDS Use Case - ONAP-02-Design Time (El Alto)#1091812835
Network Naming mS: Remove data from EXTERNAL_INTERFACE database
...