Page Comparison

• Target is common LCM API in CCSDK usable by different controller personas to simplify for both clients and controller implementations
• Support PNFs for applicable LCM operations in a consistent way
• Enable use of CDS blueprint processor to customize behavior of LCM operations in the 'self-service' category
  
  • In ONAP R4, CDS can be used for pre/post-instantiation configuration. Generic and model-driven design should allow CDS usage to be extended for additional operations and use cases.
• Evolution steps that preserve backwards compatibility for clients

https://wiki.onap.org/download/attachments/50202249/2019-04-09%20ONAP_LCM_API_Evolution_El_Alto.pptx?api=v2

Visualizer for A&AI Model Layout

Use Case Realization Call: May 1, 2019

A&AI developer Model Browser to navigate and viewing attributes, object types & edge view

Recording & Slides: Use Case Realization Call: May 8, 2019

Analytics focus. 5G place RAN CU in specific locations. Low-latency application. Specific Edge Data Center. Management portion. Task for distributed Management components. Onboarding. Distributed Management. Instantiation. Cloud Native Eco system. Central Management system. K8S Based. Leverage same W/F. Distributed Edge with different capabilities & capacities. Different categories. An "umbrella/Core" ONAP consolidate view component Micro-service in all Edge locations. Analytics application distributed across all location, want consolidated view.

Onboarding/Instantiation Resources - Design Flow integration. Config Sync Mechanism (Cloud K8S operator framework). Offloading process: dimensioning exercise. Topology defined. Application delivery. Instantiation association bind to an existing offload application on the edge. Management components are dynamic. Deploy dynamically.

Edge Orchestrator. Heirarchical orchestration. Edge Cache. Edge offload component. Central repository = primary source of truth. SYNC.

A&AI - dependent on the U/C. e.g. analytics off-load on edge. CLAMP may need edge A&AI. Craft persona. K8S design.

URLLC - Closed Loop on the Edge. 5G.

ARCHITECTURE: converging on multiple proposal. Day1 backward compatible. staring Cloud native w/ backward compatible.

W/F - Multicloud Effort. Cloud native deployment of management workloads. central & edge coordination.

Multi-Tenancy - Automatically factored in. Not driving new multi-tenancy req hold true for Edge.

Edge Automation through ONAP Arch. Task Force - Distributed Management (ONAP etc.) components