ONAP Container/Container Orchestration Engine(COE) support

Code Name: TBD(invent short fancy name)

This page tracks the related materials/discussions/etc related to Container based network service/function deployment(ONAP container/Container Orchestration Engine(COE)) effort.

As starting point, this effort has started as small subgroup of multicloud as task force.As the efforts evolve, logistics would be revised. Maybe this task force would be promoted to a independent group or an independent project.

Meetings

• [coe] Team ONAP5, China(Wed)2:00am / UTC(Wed) 18:00PM / ET(Tue) 13:00pm / PT(Tue) 10:00am From Nov 30/Dec 1, 2017.
• From Jan 16/17, we'll have new timeslot.  China CST(Wed)2:00am/UTC(Wed) 18:00PM/ET(Tue) 13:00pm/PT(Tue) 10:00am
• draft discussion for second presentation at architecture subcommittee draft slides/discussion will be posted here.
• Meeting Minutes

Items

• determine timeslot for weekly zoom meeting: doodle poll
  • new time slot is China CST(Wed)2:00am/UTC(Wed) 18:00PM/ET(Tue) 13:00pm/PT(Tue) 10:00am
  • start from Jan 16/17
• materials for Usecase subcommittee
• update matrials for architecture subcommittee
• settle down legistics
  • subproject under the umbrella of multicloud project
  • sub PTL for
  • setup repo
    • committers
  • JIRA items
• Beijing planning
  
  • use case
• archtecture/API design
  • collect k8s usage options
    
    • Munish proposal
    • Isaku proposal
    • Bin Hu proposal:
    • Frank proposal
  • impact on modeling
  • impact on policy
  • impact on TOSCA
• use case proposal
  • impacted projects
• architecture proposal
  • discussion points
  • how to register k8s cluster
  • how to deploy vnf
  • life cycle management and others(e.g. auto scaling): generic VNF controllers

timeline

• determine timeslot for oneline meeting
• the week of Nov 30/Dec 1, 2017: first online meeting
• the week of Dec 4: kubecon: will skip
• the week of Dec 11: ONAP developer event. Let's have f2f session there.
• the week of Dec 18:
  
  • zoom meeting? or skip?
• after that, online meeting
• Maybe people will be on vacation around chrismas/new year
• The week of Dec 25: skip
• The week of Jan 1: skip?
• The week of Jan 8: Time slot will be determined by doodle poll
• Jan 9, 2018: ARC subcommitee 2nd review:  slide
• Jan 15, 2018: attending multicloud weekly meeting
• Jan 16, 2018: weekly meeting
• the week of TBD: usecase subcommittee meeting
• The week of TBD: archtecture subcommittee meeting
• The week of TBD: present for TSC for new projects(or taskforce or whatever)

Project template for project proposal

Project Name:

Project name: Container based network service/function deployment(ONAP container support):

code name: TBD

Repository name: TBD

Project Description:

The effort will investigate/drive a way to allow ONAP to deploy/manage Network Services/VNFs over container/COE.

Increasing VNF density on each node and latency requirements are driving container based VNFs.  This project enhances ONAP to support VNFs as containers in addition to VNFs as VMs.

• Support for multiple container orchestration technologies as VIM(Virtualized Infrastructure Manager) technologies - Support container orchestration technology as VIM by ONAP and allow VNFs to run within container technology and also allow closed feedback loop same to VM based VIM. e.g. openstack

• Support for co-existence of VNF VMs and VNF containers - Add container orchestration technology in addition to the traditional VM-based VIM or environment managed by ONAP. So that VNFs can be deployed within container by ONAP.
• Support in various ONAP projects to bring up VNFs as containers by standardized definition of workload as VM or container (e.g TOSCA model)
• Enhance VNF SDK to support container based VNFs.
• Support for uniform network connectivity among VMs and containers.

Goal and scope

the first target of container/COE is k8s. but other container/COE technology, e.g. docker swarm, is not precluded. If volunteers steps up for it, it would be also addressed.

The use of CoE/K8S is optional.

• Have ONAP take advantage of container/COE technology for cloud native era
• Utilizing of industry momentum/direction for container/COE

• Influence/feedback the related technologies(e.g. TOSCA, container/COE)

• Teach ONAP container/COE instead of openstack so that VNFs can be deployed/run over container/COE in cloud native way

At the same time it's important to keep ONAP working, not break them.

• Don’t change the existing components
• Leverage the existing interfaces and the integration points where possible

Functionality

• Allow VNFs within container through container orchestration managed by ONAP same to VM based VIM.
• Allow closed loop feedback and policy
• Allow container based VNFs to be designed
• Allow container based VNFs be configured and monitored.
• Kubernetes VIM as initial container orchestration technology under Multi-Cloud project.
  

API/Interfaces

new API is introduced into multicloud projects shown in the following slide.

the following table summarizes the impact on other projects

First target for first release

the scope of Beijing is

• Pure COE/K8S deployment

• Assume that COE/K8S is already deployed

• Deployment unit is Pod

• Future work

• Hybrid deployment: VM + container (+ PF)

• Dynamic deployment of COE/K8S instances on demand

• Multicloud: basic API

• Lifecycle management: keep compatibility of APP-C

• No (major) change by using bare pod

• Future work

• Delegation in APP-C or VNF controllers is future work

• Sample VNF running within container: sample VNFs as vFW/vDNS
• test

Target for later release

• Installer/test/integration
• More container orchestration technology
• More than sample VNFs
• delegating functionalities to CoE/K8S

Non-Goal/out of scope

The followings are not goal or out-of-scope of this proposal.

• Not installer/deployment. ONAP running over container
  • OOM project ONAP on kubernetes
  • https://wiki.onap.org/pages/viewpage.action?pageId=3247305
  • https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project
  • Self hosting/management might be possible. But it would be further phase.
• container/COE deployment
• On-demand Installing container/coe on public cloud/VMs/baremetal as cloud deployment
  • This is also out of scope for now.
  • For ease of use/deployment, this will be further phase.

Architecture Alignment.

• How does this project fit into the rest of the ONAP Architecture?

• The architecture (will be)is designed to enhancement to some existing project.

• It doesn’t introduce new dependency

• How does this align with external standards/specifications?

• Convert TOSCA model to each container northbound APIs in some ONAP component. To be discussed.

• Are there dependencies with other open source projects?

• Kubernetes pod API or other container northbound AP

• CNCF(Cloud Native Computing Foundation), OCI(Open Container Initiative), CNI(Container Networking interface)

  
  

This above slide depicts the basic workflow there is no workflow change except k8s driver in multicloud.

the work flow to register k8s instance is depicted as follows

the work flow to deploy VNF into pod is as follows

Other Information:

• link to seed code (if applicable) N/A

• Vendor Neutral

• if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?

• Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Key Project Facts:

Release Components Name:

Note: refer to existing project for details on how to fill out this table

Resources committed to the Release:

Note 1: No more than 5 committers per project. Balance the committers list and avoid members representing only one company.

Note 2: It is critical to complete all the information requested, that will help to fast forward the onboarding process.