ONAP Cloud Native Evolution
Plan and Next Steps
- Align ONAP Community on its role and relationship to the Cloud Native ecosystem
- TSC Task force initiated to define on ONAP’s CNF strategy including
#1 What benefits ONAP itself gained by going cloud native
#2 How we want ONAP to enable CNFs (hybrid, ONAP Lite)
#3 What ONAP's value proposition is in the overall LFN family (ONAP/CNTT/OPNFV etc.
- Include “ONAP-CNCF” to the CNCF Cloud Native Interactive Landscape.
- Discussion being kick-off with LF (Arpit Joshipura)
- Promote ONAP’s CNF strategy through LF Events (ONES, DDF etc.) and press release(s)
- CFP submitted for ONES NA
- First implementation of ONAP CNCF as part of the Guilin Release (Nov 2020?)
OVP / Cloud Native Journey
2/12 (presented by Arpit): VNF-CNF OVP - 2 key slides.pptx
2/27 (updated deck with Ciaran, Ranny, Seshu, Timo, Alla): VNF-CNF OVP - 2 key slides_V3.pptx
2/28: (updated deck - orange box is now generic - was previously missing SDC 
): VNF-CNF OVP - 2 key slides_V4
3/3: (updated with CNF Task Force): VNF-CNF OVP - 2 key slides_V5
Role of ONAP
Role of ONAP (which is a central automation platform) across multiple Clouds & Edges.
- Distributed Applications: Telco world is known to have requirement to support ‘network services’ whose components (VNFs today) spread across multiple computing regions (Openstack based regions). Hence, the need for central orchestrator that orchestrates various VNFs of the network service in multiple openstack based computing regions. With edge-computing, even normal applications are becoming distributed, where a few microservices of the application are deployed across multiple edges & a few in network edges and public clouds. Essentially, applications are becoming more like network services.
- Convergence of applications and network functions due to Edges : Edge world can’t afford to have two computing environments – One for normal applications and another one for network functions. This is due to resource constraints. Since many edge-computing efforts in Industry adopted K8s, it is natural to think about supporting network functions and use same K8s cluster for both. It appears that a few MEC applications even require some network functions to be deployed along with them (Example include MEC applications with network security functions).
- Network function deployments and life cycle management are more complex than the applications due to need for supporting multiple interfaces, provider networks, service function chaining. ONAP is solving many of these challenges.
- Support for Multiple Cloud technologies : Supporting legacy Openstack deployments with greenfield K8s deployments are needed. ONAP solves these multi-cloud challenges.
- Support for Telco infrastructure such as OSS/BSS – ONAP is already in the path to support various MEF standards on its north side to support standardization between OSS/BSS and Orchestrators.
- Support for monitoring of distributed applications and closed loops : Monitoring distributed applications that are deployed across multiple edges/clouds is complex. There is need for showing the comprehensive status at the application level instead of at each resource level. ONAP monitors the services/distributed-apps and not only provides simpler view of the status, but also can run through various analytics engines and even act on the actionable insights.
Note: ONAP4K8s is a profile of ONAP for Enterprise/IOT (Including Private-5G/LTE) market that have requirement of deploying CNFs/VNFs along with normal applications in multiple K8s based clusters.
In addition, we believe that ONAP can provide additional values as follows:
#1 NF Control Loop
#2 NF Common Inventory
#3 NF Data collection and analytics
#4 Support of PNFs
#5 Cover the design of services as well as the orchestration of services, design of control loops
#6 Play a role in terms of standardizations (TMForum, ETSI ZSM, MEC etc.) through our ONAP Technical Coordinators
To recap, we can provide significant automation values to handle applications on top of the K8S environment.
Areas of Focus
#1 ONAP 'Light" Weight - Review our current ONAP projects (see Lifecycle review led by Jason/Chaker)
#2 ONAP4K8S, Containerization
#3 Identify ONAP Requirements + to support CNFs for Guilin
#4 E2E Integration (OVP)
#5 VNFREQS => CNFSREQS - Certification CNF requirements - need to align with the ONAP Architcture + ONAP SECCOM regarding Cloud Native.
Features/Capabilities - How We complement each other?
| Features/Capabilities | K8S Environment | CNTT/Arch Ref.2 | ONAP | Comments |
|---|---|---|---|---|
Scalability | Cluster Autoscaler, HPA and VPA | MUSIC | ||
Resiliency | K8S Services | MUSIC | ||
Secured service-to-service communication | - | AAF | Apps Integrated with Service Mesh | |
Logging | Stackdriver Logging Elasticsearch Fluentd | EELF/ELK | ||
Container Orchestration | Role of K8S | OOM | ||
Dashboard |
| Consul | ||
| Observability | Prometheus, Jaeger | DCAE | ||
Where are we on the CNCF Trail Journey?
| Features/Capabilities | ONAP | Comments |
|---|---|---|
| Step #1 Containerization | ||
| Step #2 CI/CD | ||
Pre-requisite(s)
- Is there any available CNF that we could use to prototype/test with "ONAP CNCF"?
- Check this link about CNF Testbed-https://github.com/cncf/cnf-testbed
- Check with OPNFV - if any investigation in this area
Requirements
We need to identify non functional reqs for ONAP Itself and for ONAP to orchestrate CNFS
(Rework the below reqs into these two categories)
#1 Need to deploy ONAP/ONAP CNCF on component basis not as a whole
#2 Move to Service Mesh
#3 Optimization of DB - leverage some storage, DB capabilities offered by existing Cloud solution
#4 Scalability, Reliability based on K8S services (?).
Not replacing K8S but built on top of K8S.
#5 API between components
Later on, how our "ONAP CNCF" will look like to support CNFs
Links
https://github.com/kubernetes-sigs/kubefed -- K8S across multiple clusters
https://pivotal.io/cloud-native
https://techbeacon.com/app-dev-testing/5-critical-elements-building-next-generation-cloud-native-apps
https://medium.com/faun/15-best-practices-to-design-cloud-native-modern-applications-a2aa9f19cda0
https://hackernoon.com/writing-sky-high-applications-a-guide-to-cloud-native-development-9f3c1c020471
https://codilime.com/vnfs-in-cnfs/
https://wiki.lfnetworking.org/display/LN/OVP+2.0+Boot+Strap
Meeting Notes
Previous Meeting Notes
Srinivasa Addepalli
As part of ONAP4K8s, we have done some work in R4 and we are working ìDistributed Application Orchestrationî in R6.
In R4, we showcased deploying CNFs & VNFs (firewall use case) and normal applications on the same cluster from ONAP.
Also, Akraino ICN project is bundling ONAP4K8s.
Glad to see wider interest in deploying CNFs from ONAP in remote K8s clusters.
Linked to the edge computing, K8S deployment/containerization, 5G - discussion under architecture team is ongoing
Prototype under Multicloud project- develop some plug-ins to prove network functions/containerization
What type of orchestrator changes do we need?
Links:
https://wiki.onap.org/display/DW/Multi+Cluster+Application+Scheduler
https://wiki.onap.org/display/DW/ONAP4K8S+profile
Ranny Haiby
#1 Define benefits of ONAP for CNFs - what are we trying to solve with CNFs?
i.e. Control Loops, Provisioning/Modeling, etc
#2 Scalability/Reliability - deep dive to be truly K8S oriented
Ciaran Johnston
Do we want to be truly Cloud Native? yes but it requires baby steps stating with Cloud native development principles
How can we enable as part of our development practices
i.e. DevOps approach - mS
The second approach is the preference
Strategy is to demonstrate how ONAP could be "complementary" to other open source initiatives.
Seshu Kumar Mudiganti
#1 Discussion of two steps
1∞ Identify ONAP components (MVP) to support CNFs
2∞ Transform other components (still maintained) to support also K8S deployment
#2 Is there any other solution than K8S (i.e. Red Hat Openshift?)
https://blog.openshift.com/whats-the-difference-between-openshift-and-kubernetes/
https://hackernoon.com/kubernetes-vs-openshift-a-detailed-comparison-7r3z53zlv
Clarify the term CNF across the community and standardise it addressing the below ONAPARC-552 - Getting issue details... STATUS
Timo Perala
#1 Understand the K8S Roadmap to understand what are the incoming features in the future
so we can identify where ONAP can play a role and then define 'ONAP Lite'
#2 Follow-up with Sylvain (CNCF TCC Lead)
Alla Goldner
Suggestion to create 3 blueprints
#1 ONAP lite (just CNFs)
#2 ONAP hybrid (supporting all - as a transition period or will remain later to support PNFs at least)
#3 ONAP All (VNFs, PNFs, CNFs)
=> Key word: we should be able to deploy the ONAP/ONAP lite components that carrier/vendor just need
March 3rd, 2020
- Presentation made by user-67d6f about VTP <Add deck>
- Review link provided by Ciaran - https://github.com/cntt-n/CNTT/tree/master/doc/ref_arch
- Sylvain/CNCF - Confirmed he will follow-up with CNCF guy (Dan)
- Share additional links presented during OVP PH2 meeting (Feb 28th, 2020) - https://etherpad.opnfv.org/p/OVPp2_Kickoff
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 Respçonse to Dan (CNCF)