...

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

doodle poll to determine timeslot.

TBD: weekly meeting time slot needs to be determined.

Meeting Minutes

• 2017-11-14 architecture subcommittee
  • slide
• 2017-09-26 Meeting notes: Enhancing ONAP to orchestrate container VNFs using container orchestration as VIMs
  • slide

...

Project name: ONAP container support: OCS(TBD)
container support:Repository name: OCS(TBD)

Project Description:

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

...

Some of architecture/design are under discussion. subject to change depending on the outcome of discussion.

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

• 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

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

Multi cloud project

General/cross projects:

• Registry logic to reigster container instances. E.g. k8s instances and its API endpoint with its features.

• At first new TOSCA node definition will be introduced to express container requirement. In long term, contributing to TOSCA specification would be in scope side project.
  
• Network Service(NS) and/or VNF will be described in NSD or VNFD in TOSCA format. one of ONAP component need to generate necessary API requests to continer/COE
• representation in TOSCA to be defined. In longer term, we may want to give feedback to TOSCA spec.

SO and Controllers(SDN-C, APP-C, VF-C etc...)

• Enhancements in SO and controllers to take advantage of enhanced Multi-Cloud model driven API that may be enhanced for container orchestrators. This will be done as a part of multi-cloud project.

• This implies sort of converters from NS/VNF models(VNF descriptors, more higher level, it can be TOSCA ) to  enhanced Multi-Cloud API or directly to k8s API.

Multi cloud project

• Registry logic to reigster container instances. E.g. k8s instances and its API endpoint with its features.

• API enhancements in enhancements   in Multi-Cloud project to enable container orchestration technologies through planned model driver API.(currently TOSCA): First target is Kubenetes plugin - converting the input from northbound API to kubernetes API.

• Southbound plugin in Multi-cloud project to talk to container/COE. The first target will be kubernetes API.

• Plugins to FCAPS/data management to report statistics(e.g. Cpu usage, memory usage) from underlying containers to upper ONAP component

• API enhancements (if needed) in Multi-Cloud project to realize uniform network across VMs and containers instantiated by VIMs TBD : container orchestration api or CNCF using flannel with Multus

SO and Controllers(SDN-C, APP-C, VF-C etc...)

• Enhancements in SO and controllers to take advantage of enhanced Multi-Cloud model driven API that may be enhanced for container orchestrators. This will be done as a part of multi-cloud project.

• This implies sort of converters from VNF models(VNF descriptors, more higher level, it can be TOSCA ) to  enhanced Multi-Cloud API

AAI

• If necessary, enhance AAI schema to describe feature/capability of managed environment. This can be generic among VM-based VIM and container-based VIM.

• multi-VIM project to report container orchestration features/capacity to AAI

...

• Allow container image with TOSCA
  
  

First target for first release

• Container orchestration technology: First target of container orchestration is kubernetes. But support for other container orchestrations can/will be addressed later.
• SO and multicloud
• Sample VNF running within container: sample VNFs as vFW/vDNS
• test

Target for later release

• Installer/test/integration
• VNF SDK
• Policy
• Feedback to modeling project
• More container orchestration technology
• More than sample VNFs

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.

...