...

Where are we on the CNCF Trail Journey?

Meeting Notes

APS  (2/13) 

#1 Start to work on our ONAP response to Dan (CNCF)

#2 Try to identify where we are on the CNCF Trail Journey

#3 Fill in the table - how we complement each other

#4 Consolidation our message about ONAP Role - should be linked to #1?

...

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://www.cisco.com/c/en/us/solutions/service-provider/industry/cable/cloud-native-network-functions.html#~introduction

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

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

...

Action Items

Pre-requisite(s):
#Is there any available CNF that we could use to prototype/test with "ONAP Lite"?
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 lite 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 lite" will look like to support CNFs

Link: 
https://github.com/kubernetes-sigs/kubefed -- K8S across multiple clusters

Other links:
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://www.cisco.com/c/en/us/solutions/service-provider/industry/cable/cloud-native-network-functions.html#~introduction

• 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 13 Feb 2020 
•  

  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)