...
Projects that may be impacted
| Project | Possible impact | Workaround | owner | Status |
|---|---|---|---|---|
| SO | Ability to call generic VNF API | Until SO is enhanced to support
SO will be simulated to test the K8S plugin and reference deployment | SO simulation owner: ??? | |
| SDC | May not be any impact, but need to see if there any impact
| Owner : Libo | ||
| A&AI AND ESR | May not be any impact, but need to see whether any schema changes are required
Check whether any existing fields in cloud-region can be used to store this information or introduce new attributes in the schema (under ESR) | Owner : Shashank and Dileep | ||
| MSB/ISTIO | No impact on MSB. But fixes required to do following: Integration with ISTIO CA to have the certificate enrolled for communicating with other ONAP servceis Also to communicate with remote K8S master. |
Activities that are in scope for phase1 (Stretch goals)
| Activity | Owner | Status |
|---|---|---|
| K8S node-feature discovery and population of A&AI DB with the features | ||
| Support for Cloud based CaaS (IBM, GCP to start with) |
FOLLOWING SECTIONS are YET TO BE UPDATED
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.
- 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/work flow with (mostly) zero impact.
- Leverage the existing interfaces and the integration points where possible
Functionality
...
API/Interfaces
Swagger API:
| View file | ||||
|---|---|---|---|---|
|
the following table summarizes the impact on other projects
...
component
...
comment
...
modelling
...
New names of Data model to describe k8s node/COE instead of compute/openstack.
Already modeling for k8s is being discussed.
...
OOF
...
New policy to use COE, to run VNF in container
...
A&AI/ESR
...
Schema extensions to represent k8s data. (kay value pairs)
...
Multicloud
...
New plugin for COE/k8s.
(depending on the community discussion, ARIA and helm support needs to be considered. But this is contained within multicloud project.)
First target for first release
the scope of Beijing is
Scope for Beijing
First baby step to support containers in a Kubernetes cluster via a Multicloud SBI / Plugin
Minimal implementation with zero impact on MVP of Multicloud Beijing work
Use Cases
Sample VNFs(vFW and vDNS)
integration scenario
Register/unregister k8s cluster instance which is already deployed. (dynamic deployment of k8s is out of scope)
onboard VNFD/NSD to use container
Instantiate / de-instantiate containerized VNFs through K8S Plugin in K8S cluster
Vnf configuration with sample VNFs(vFW, vDNS)
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
...
.png?version=1&modificationDate=1526237282000&cacheVersion=1&api=v2)
UseCases
- sample VNF(vFW and vDNS): In Beijing only deploying those VNF over CoE
- other potential usecases(vCPE) are addressed after Beijing release.
the work flow to register k8s instance is depicted as follows
.png?version=1&modificationDate=1526237282000&cacheVersion=1&api=v2)
the work flow to deploy VNF into pod is as follows
.png?version=1&modificationDate=1526237282000&cacheVersion=1&api=v2)
...
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)
...
Scope
- Support for K8S based sites (others such as Dockerswarm, Mesos are not in the scope of Casablanca)
- Support for OVN and flannel based networks in sites
- Support for virtlet to bring up VM based workloads (Others such as Kubevirt is for future)
- Support for bare-metal containers using docker run time (Kata containers support will be taken care later)
- Multiple virtual network support
- Support for multiple interfaces to VMs and containers.
- Proving using VFW VM, Simple router container and EdgeXFoundy containers.
- Support for K8S deployment and other yaml files as artifacts (Helm charts and pure TOSCA based container deployment representation is beyond Casablanca)
- Integration with ISTIO CA (for certificate enrolment)
API/Interfaces
Swagger API:
| View file | ||||
|---|---|---|---|---|
|
Key Project Facts:
This project will be subproject of Multicloud project. Isaku will lead this effort under the umbrella of multicloud project.
...
Role | First Name Last Name | Linux Foundation ID | Email Address | Location | |||
|---|---|---|---|---|---|---|---|
| committer | Isaku Yamahata | yamahata | isaku.yamahata@gmail.com | PT(pacific time zone) | |||
| contributors | Munish Agarwal | Munish.Agarwal@ericsson.com | |||||
| Former user (Deleted) | ritusood | ||||||
| Shashank Kumar Shankar | |||||||
| Ramamani Yeleswarapu (Deactivated) | |||||||
| Kiran | |||||||
| Bin Hu | bh526r | bh526r@att.com | |||||
| libo zhu | |||||||
| Manjeet S. Bhatia | manjeets | ||||||
| Phuoc Hoang | hoangphuocbk | phuoc.hc@dcn.ssu.ac.kr | |||||
| Mohamed ElSerngawy | melserngawy | mohamed.elserngawy@kontron.com | EST | ||||
| Interested (will attend my first on 20180206) - part of oom and logging projects | michaelobrien | frank.obrien@amdocs.com | EST (GMT-5) | ||||
| Victor Morales | electrocucaracha | victor.morale@intel.com | PST |
...