...

• 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 /vDNS use cases case from a regression perspective; i..e, they need to work the same with the new code base.

...

• 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)

...

...

...

Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

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

...

What is currently available is documented in the APPC User Guide. This document will be updated as part of the project.

...

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 Outgoing Dependencies

...

...

Resources

Fill out and provide a link toward the Resources Committed to the Release centralized page.

Resource Page Link

Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

...

The project team comply with the ONAP Charter.

Release Key Facts

Fill out and provide a link toward the centralized Release Artifacts.