Service Orchestrator Amsterdam Release
- 1 Overview
- 2 Scope
- 3 Release Deliverables
- 4 Sub-Components
- 5 ONAP Dependencies
- 6 Architecture
- 7 Testing and Integration Plans
- 8 Gaps
- 9 Known Defects and Issues
- 10 Risks
- 11 Resources
- 12 Release Milestone
- 13 Team Internal Milestone
- 14 Documentation, Training
- 15 Other Information
Overview
Project Name | Enter the name of the project |
|---|---|
Target Release Name | Amsterdam |
Project Lifecycle State | Incubation |
Participating Company | Huawei, CMCC, AT&T, Orange,Nokia, IBM,Gigaspaces, Ericsson, VMWare, ZTE, BOCO |
Scope
What is this release trying to address?
The SO provides the highest level of service orchestration in the ONAP architecture.
Functionality for Release 1:
Enhance ONAP SO run-time orchestration framework to support orchestration driven from declarative models (TOSCA encoded).
Perform lifecycle operations based on a declarative TOSCA model, including:
Deployment
Undeployment
Scale (Out, In) (Stretch goal)
Heal (Stretch goal)
Software Upgrade (various forms - Stretch goal)
Use Cases
Use Case: Residential Broadband vCPE (Approved).
Minimum Viable Product
Enhance ONAP SO run-time orchestration framework to support orchestration driven from declarative models (TOSCA encoded).
Perform lifecycle operations based on a TOSCA model, including:
Deployment
Undeployment
Functionalities
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 TOSCA model | In | H |
|
Epics
Stories
Longer term roadmap
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 |
|---|---|
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.