...
What is this release trying to address?
Describe the problem being solved by this release
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Minimum Viable Product
Describe the MVP for this release.
Functionalities
...
This project provides a common set of reusable code that can be used across multiple controllers. The code could be used in other components but would not be an end solution for use cases by itself and would not be deployed on its own.
- For example, the SDN-C , APP-C, DCAE, ONAP Operations Manager and ONAP controller can reuse common pieces from this framework.
While controllers are encouraged to use the common controller SDK libraries, usage of this common code is optional. Our goal is to provide code that is sufficiently flexible that there is no need for controllers to implement their own custom solutions, but we recognize that there are valid reasons why specific controllers might need to implement their own solutions and would not prevent them from doing so.
Use Cases
- SDN-C core : core platform needed to execute directed graphs
- SDN-C adaptors : set of adaptors used by directed graphs to talk to other ONAP components or external services, including other controllers
- SDN-C northbound : northbound interfaces to SDN-C
- SDN-C plugins : add-on functionality used by directed graphs
- SDN-C oam : tools for operations, administration and maintenance of controller
- Common microservice / VF lifecycle management capabilities
- Common health checks
- Common APIs
- Common logging
- Common model management (e.g. Yang, TOSCA)
- Common resource management (e.g. IP management, DNS naming, keystore, containers)
Minimum Viable Product
TBD
Functionalities
TBD
Epics
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox and issuetype in (epic) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...