Brief Project Overview (brief as it should be known)
CNFO - Containerized Network Function is orchestrating the network functions deployed in a containers
This functional feature in ONAP would be leveraging the existing functionality of K8s based orchestration to the next level and would be making the helm charts the first class citizen.
The current efforts focus on leveraging the design and runtime functions of ONAP to support the CNFs through helm charts.
New component capabilities for Guilin, i.e. the functional enhancements, if applicable
K8s Adapter - A new adapter (pod) inside SO
New or modified interfaces
New Interfaces around SO - K8s Plugin
Enhanced functions of the SDC, SO, and AAI around the helm chart and CNF resouces
If they are modified, are they backwards compatible?
Yes
Interface naming (point to an example)
Consumed API from other projects
Project | API Dependency | Notes |
|---|---|---|
Published API
Project | API | Notes |
|---|---|---|
Reference to the interfaces.
(Reference to the the swagger.json file(s) whenever possible)
What are the system limits?
.
Involved use cases, architectural capabilities or functional requirements.
Listing of new or impacted models used by the project (for information only).
- Identify any High Level Information Model Requirements. See: ONAP R7 Modeling High Level Requirements
- Models based on information exchanges from Use Cases
- Models documenting existing implementations
- Forward looking models that may be implemented in future releases
- Describe how exposed APIs are mapped to information models
(list all the relevant Jira tickets)