...
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 | 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 , Jaeger | DCAE | 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 ? | DCAE | Specific VES Integration with Promotheus and Grafana technologies 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 | |||||||||
Networking back to provider network | |||||||||||
Tracing | CNF Compliance: The CNF supports OpenTelemetry-compatible tracing | Inventory | AAI | Security | SECCOM | CNF Security Requirements | Networking back to provider network |
Where are we on the CNCF Trail Journey?
...
- Feedback from OVP PH2 meeting: https://wiki.lfnetworking.org/display/LN/2020-03-09+OVP+2.0+Meeting+notes
- Review of our previous feedback concerning Compliance & Verification Program - https://wiki.lfnetworking.org/display/LN/OVP+2.0+Boot+Strap
- 2 presentations:
- CNCF Compliance (Bill Mulligan) (PDF version)
- OVP Workstream (Rabi Abdel)
- Do we need to extend our ONAP VNFReqs to consider CNF Reqs or shall we suggest a "LFN CNF Reqs" Board or will it be driven by CNCF?
- Need to connect with CNCF to avoid duplicated effort, divergent effort
- Architecture, Modeling, Security reqs will feed VNFReqs+ to define what it is requested to onboard CNFs on ONAP — Shall we draft a Diagram flow?
- Need also to consider CNF Security reqs from SECCOM
- Need to consider the Architecture, Requirement Subcommittees' perspectives
- ETSI Activities to define packages - candidate for the Guilin Release ETSI CNF Support
- ESTI reqs/packages availability - End of Q4
- Need to define an intermediate (Helm v3.0, TOSCA, HEAT) then try to push back our findings to ESTI
- Hydrid approach (supporting all together - CNFs, VNFs, PNFs) - need to address the network part ONAP SO ETSI-Aligned Hierarchical Orchestration
- Migration Strategy from Openstack (VNFs) to K8S (CNFs)
- New artifacts for containers
- New packages while offering the same functionality than formerly VNFs
- Define the mapping (Helm v3.0, TOSCA, HEAT)
- Review "Features/Capabilities - How We complement each other?"
March 12th, 2020
Action Items
- ONES CFP - Srinivasa Addepalli will work with Alla Goldner on the abstract - Key item - "the value that ONAP can bring"
- Kenny Paulset up doodle pole for meeting cadence and 2 or 3 per week
-
Sylvain Desbureaux - Start to work on our ONAP response to Dan (CNCF)
-
Try to identify where we are on the CNCF Trail Journey
-
Fill in the table - how we complement each other
-
Consolidation our message about ONAP Role - should be linked to our ONAP Response to Dan (CNCF)
- Check with Kenny, David - how to record our upcomign discussions?
- Attend the next VNFReQs meeting and to discuss the extension of the team's scope - Trevor Lovett - was discussed during 3/12 - CNF Part 2
- Follow-up with SECCOM about CNF Security reqs
- Kenny Paul , create a recording section and add the recordings (2x 3/12)
- Define our first Use case and identify CNF
- Check with the DCAE project regarding any study about Prometheus, Jaeger + specific VES to support CNFs