Page Comparison

Table of Contents

PCEI General Architecture

The general PCEI Architecture Document can be found at this link: https://wikilf-akraino.akrainoatlassian.orgnet/wiki/x/CAW6AQ1ojQ

PCEI R4 Architecture and Focus

...

1. Controller Design Studio (CDS) Terraform Executor. Enables automatic and North Bound Interface (NBI) API driven pull from Gihub and execution of Terraform plans, including:
   1. Public Cloud Core orchestration (e.g., AWS, Azure, GCP).
   2. Equinix Interconnect and Infrastructure Orchestration (Fabric l2/L3, Network Edge, Bare Metal).
   3. Openstack orchestration (VM deployments).
2. CDS Helm Chart Processor. Allows automatic and NBI API driven pull from Github of Composite Application Helm charts for:
   1. Onboarding Services and Apps to ONAP (a.k.a., EMCO – Edge Multi-Cluster Orchestrator).
   2. Creation of Service Instances and Deployment of Kubernetes Apps on target Kubernetes clusters.
3. CDS Kubernetes Cluster Registration Processor. Allows NBI API driven automatic target cluster registration with ONAP (EMCO) for:
   1. Kubernetes application deployment on registered target clusters.
4. North Bound Interface APIs for:
   1. Cluster Registration into ONAP
   2. Terraform Plan Execution against target providers (Cloud, Equinix, Openstack).
   3. Helm Chart Onboarding into ONAP for Service and App Registration.
   4. Service Instance creation in ONAP and App deployment onto target Kubernetes clusters.
5. Application and Network Function Deployments. NBI API triggered deployment of Cloud Native Apps and Network Functions on target Kubernetes Edge Clusters:
   1. Azure IoT Edge.
   2. Free 5G Core.