...
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
| Functionality Name | In or Out | Priority | Stretch |
|---|---|---|---|
| Orchestration driven from declarative models | In | H | TOSCA encoded |
| Perform life cycle operations based on a declarative TOSCA model | In | H |
|
Epics
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=so and issuetype in (epic) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
- Support more life cycle management operations
- Support distributed component Deployment
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | To fill out | To fill out|
|---|---|---|---|
| Source Code | Source Code of Service Orchestration | ||
| API List | The Specification of the Service Orchestration APIs. | ||
| Docker Image | Docker Image(executable) of Service Orchestration |
Sub-Components
List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
ONAP Dependencies
...
SDC (true dependency with SDC SDK)
AAI (using API interface)
SDN-C (using API interface)
APP-C (no existing interface yet)
DMaaP (included as part of SDC SDK)
- MSB (no existing interface yet)
VF-C (no existing interface yet)
- Multi-VIM(no existing interface yet)
Architecture
High level architecture diagram
...