...
What is this release trying to address?
Continue The Amsterdam release will continue evolving the design driven architecture of and functionality for APPC. APPC aims to be completely agnostic and make no assumption about the network.
Amsterdam release will also add Ansible support, enhancement enhancements for Chef, new Data Graphs (DG) and nodes in support of Ansible, enhancements to existing APIs in support of ONAP Operations Manager, plus capabilities that address operations efficiency.
We will continue to elaborate this section as the release progresses.
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
- APPC will contribute to the vCPE use case closed loop scenario, assuming that Restart action is on the VM, not the VNF.
- APPC will support vFW use case from a regression perspective; i..e, they need to work the same with the new code base.
Minimum Viable Product
Describe the MVP for this release.
- Northbound REST Layer - This layer is responsible for interfacing with APPC clients such as SO, SDC, etc... via YANG-based API vis REST HTTP, message bus (UEB/DMaaP) and exposes APPC OAM APIs enabling performance of lifecycle operations.
- APPC Provider - responsible for validating the YANG Remote Processing Call (RPC) input and for rejected when malformed. Upon successful validation, the APPC Provider call the Dispatcher to continue the request processing.
- APPC Dispatcher - responsible for processing requests received by the Request Handler and, if valid, selects the correct Directed Graph (DG) workflow for execution. Upon DG execution completion, the Dispatcher informs the initiator of results of the execution and updated data in AAI.
- Service Logic Interpreter (SLI) - responsible for executing the DGs. The Dispatcher invokes the SLI framework to execute a specific DG based on the input action. The SLI executes the DG and the sub-DG and returns a success or failure response to the Dispatcher.
- AAI Interface - APPC uses AAI as a source of VNF data, including status, topology, and operational data. It also makes updates to AAI as a result of a lifecycle operation.
- Southbound Layer - plugin architecture, uses several adapters to communicate to VNFs
- Restcont adaptor
- Netconf
- SSH (XML/CLI)
- IaaS - Interface as a Service, which is part of the OpenDaylight platform, which provides the framework for APPC
- Chef (with Release 1)
- Ansible (with Release 1)
- Components that operate across all the APPC modules, including Logging, Security, KPI Service, data access service for access to internal DB (MySQL)
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.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
The long term road map is to achieve all the goals outlined in the approved project proposal; to be fully model and standards driven, be agnostics and make no assumptions about the network. Support configuration and lifecyle management of VNF/VNFC in a generic fashion so that onboarding on-boarding any new VNF/VNFC is just a matter of configuration and data. The diagram below will evolve as discussions around APPC and VF-C take place.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | Deliverable Location |
|---|---|---|
| "App-c Image" Docker Container | Executable | Docker images available on nexus3 |
| Java Source Code | The Java code for the main App-c components. | appc Git repository |
| Deployment Scripts | Linux shell scripts and Maven pom files used to generate the Docker containers. |
| appc/deployment Git repository |
| Directed Graph Xml Files (DGs) |
| Xml files define the directed graphs which are installed to database during startup and are used to determine actions taken by app-c | appc/deployment Git repository | |
| Yang Model Files | Yang files are used to define the... | appc Git repository |
| Property Files | Property files are used to define values that may need to be changed depending on the environment app-c is run in. | appc Git repository |
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.
...
List the other ONAP projects your you depends on.
- SDC: Rest based interface exposed by SDC. APPC receives notifications from SDC on VNF information. SDC team provides an SDC Listener, which is used by APPC.
- AAI: APPC retrieves and updates VNF data from/to AAI.
- OOM ?
Architecture
High level architecture diagram
- DMaaP/UEB: Message bus for communication with other components in the solution (SDC, DCAE, MSO, Portal, OOM)
- MultiVIM: TBD - currently under architecture discussions. Today, AAPC interfaces to OpenStack via CDP-PAL, which is open source software available via Github.
- SDNC/CCSDK - APPC currently gets ODL package from SDNC; SDNC and AAPC currently must align on ODL version. SDNC has indicated plans to upgrade to Carbon as part of R1. This creates a dependency on SNDC for R1.
Architecture
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
...
Anyone reading this section should have a good understanding of all the interacting modules.
High level architecture diagram
What is currently available is documented in the APPC User Guide. This document will be updated as part of the project.
API Incoming Dependencies
List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |||
|---|---|---|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill outSDC | REST API | TBD | TBD | Link toward the detailed API description |
| AAI | REST API | 8/23/17 | 8/23/17 | ||||
| MultiVIM | REST API | 8/23/17 | 8/23/17 | ||||
| CCSDK | OpenDayLight, SLI, and AAI Client | 8/23/17 | 8/23/17 | ||||
| DMaaP | API ti publish/subscribe to events sent for VNF/VM action requests. | 8/23/17 | 8/23/17 | DMaaP API |
API Outgoing Dependencies
API this release is delivering to other releases.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|
| NB Interface | REST API | TBD | TBD | Link toward the detailed API description |
Third Party Products Dependencies
...
| Name | Description | Version |
|---|---|---|
| ODL | OpenDaylight | 4.0.1 |
| Docker | Docker container host | |
| MySql | mysql-server Docker container | 5.6 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
- Unit tests are run automatically as part of every code merge.
- Once the final Docker image is compiled, it will be installed onto a Docker host and will be checked to ensure no errors occur during start-up.
- Functional testing will occur to ensure that the use cases are functioning correctly.
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
ODL upgrade to Carbon - depends on SDNC, SDNC will not have ODL Docker available until end of July. If Carbon docker is delayed, could impact APPC timeline. | Accept risk - need ODL from SDNC |
Resources
Fill out and provide a link toward the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
...
Each project must edit its table within the [[Free_and_Open_Source_Software#Project_Licenses| Master Project License Table]].
Board policy (including IPR)
Indicate if the release meets the Board policy.
...
project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.
Release Key Facts
Fill out and provide a link toward the centralized Release Artifacts.