Recording of introduction

video1075568932.mp4

Phase 1

Used Components

This PoC will use at least the following ONAP components:

• AAI
  • Schema Service
  • Traversal  (data queries)
  • Search Data  (only needed if using the UI)
  • Resources (CRUD interaction)
  • GraphAdmin (needed to set up the backend)
  • others?
• SDC
  • BE
  • FE
  • Onboarding BE
• VID
• SO
  • BPMN infra
  • Catalog DB Adapter
  • Monitoring
  • Openstack Adapter
  • Request DB Adapter
  • SDNC Adapter
  • SDC Controller
  • API Handler (SO "base" c
• DMaaP:
  • Message Router
• SDNC:
  • DMaaP listener
  • SDNC Portal
  • UEB listener

Integrating the other sub components of AAI, DMaaP, SDC, SDNC and SO will be done if possible

client → https → Ingress → http → svc → http → pod

Ingress → http → sidecar → mtls → sidecar pod → http →  pod

Validation Scenarios

The Validation Scenario will be to onboard and then deploy "basicUbuntu" VNF from gating system using GR API.

The validation scenario will be performed at each steps

Phase 2 (if time allows)

If "Step 1" of phase one is validated, we may move in parallel to step 2 → 4 of phase 1 to Phase 2

Used Components

On top of Phase 1 component, we'll add:

• CDS
• Multicloud k8s

Validation Scenario

The validation scenario will be to onboard and then deploy a CNF with values processed thanks to CDS

Flow Matrix

We have two possibilities to perform the Authoritypolicy with service mesh:

Exemple of complex matrix (for simple, remove the 2 last columns):

This flows are an information but due to the complexity and the heterogeneous of configuration, Could be miss some flow.

This information were find into values.yaml or overrides.yml, depend on the component.