...
| Features/Capabilities | K8S Environment | CNTT/Arch Ref.2 | ONAP (Today) | ONAP CNCF | Comments |
|---|---|---|---|---|---|
CNF Scalability | From an Orchestration perspective: Cluster Autoscaler, HPA and VPA Handling within its own cluster From an Automation, Control Loop (CL) perspective | OOF, SO, Multi-Cloud CL (DCAE, Policy, CLAMP + Triggered Action) | Adding value: Handling multiple K8S, Clusters | Not ONAP Scalability itself otherwise MUSIC, OOM (Container Orchestration) | |
CNF Resiliency | From an Orchestration perspective: K8S Services From an Automation, Control Loop (CL) perspective | OOF, MSO, Multi-Cloud CL (DCAE, Policy, CLAMP + Triggered Action) | Not ONAP Resiliency itself otherwise MUSIC, OOM (Container Orchestration) | ||
| CNF Availability | Public Cloud is currently offering <99.999 | Opportunity for ONAP | Not ONAP availability itself otherwise 99.9999+ built inside ONAP | ||
Secured service-to-service communication | Additional SW to be uploaded on top of K8S: Linkerd, ISTIO | AAF (VNFs only) | Integrate our ONAP Apps to Service Mesh  while keeping AAF as optional | Do we provide any certificate or shall we rely on a Certification Manager? | |
Logging | Stackdriver Logging Elasticsearch Fluentd | Logging/Pomba EELF/ELK | Centralization of Logging - ONAP feature or external system to ONAP? | ||
Dashboard |
| OOM - Consul | |||
Observability Events, Alarms, Analytics | Prometheus - https://prometheus.io/ Open-source systems monitoring and alerting toolkit Jaeger - https://www.jaegertracing.io/ As on-the-ground microservice practitioners are quickly realizing, the majority of operational problems that arise when moving to a distributed architecture are ultimately grounded in two areas: networking and observability. It is simply an orders of magnitude larger problem to network and debug a set of intertwined distributed services versus a single monolithic application. based on grafana technologies ?(UI part) | DCAE | Specific VES Integration with Promotheus and Grafana technologies (UI) as POC by AT&T | -Check the CNF Conformance to understand what are the requirements -Shall we integrate one of the open sources to DCAE (like we did with PNDA) or shall we create DCAE CNCF version? | |
| Inventory | AAI | Under investigation | |||
| Security | SECCOM | CNF Security Requirements | How to address Networking back to provider network network | ||
| Tracing | OpenTelemetry provides a single set of APIs, libraries, agents, and collector services to capture distributed traces and metrics from your application. You can analyze them using Prometheus, Jaeger, and other observability tools. - https://opentelemetry.io/ | DCAE | DCAE - Telemetry under assessment | CNF Compliance: The CNF supports OpenTelemetry-compatible tracing | |
| Performance |
Where are we on the CNCF Trail Journey?
...