...

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 add Ansible support, 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).

...

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 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.

...

List the other ONAP projects your you depends on.

• SDC
• AAI
• OOM
• MultiVIM - tbd...

Architecture

High level architecture diagram

Image Removed

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.

Image Added

API Incoming Dependencies

...

...