APPC Frankfurt Architecture Review

Brief Project Overview (brief as it should be known)

The Application Controller (APPC) performs functions to manage the lifecycle of VNFs and their components providing model driven configuration, abstracts cloud/VNF interfaces for repeatable actions, uses vendor agnostic mechanisms (NETCONF, Chef via Chef Server and Ansible) and enables automation.

New component capabilities for Frankfurt, i.e. the functional enhancements.

The following  lists the Frankfurt functional requirements which impact APPC.

• APPC-1778 - develop new LCMs to support pre/post actions:

  • LicenseManagement, PreConfigure, GetConfig, PostRebuild, PreRebuild, PreEvacuate, PostEvacuate, PreMigrate, PostMigrate, Provisioning, StartTraffic, StatusTraffic, StopTraffic

  • Documentation: https://gerrit.onap.org/r/c/appc/+/99744

• APPC-1744: move dmaap adapter out of ODL

• APPC-1729: VNFC support for Ansible protocol

• APPC-1732: ODL upgrade to Neon SR1

• APPC-1734: CDS DG Orchestrator

• REQ-42/APPC-1733: Scaling use case support ( New LCM: ConfigScaleIn)

• REQ-53/APPC-1807: Enhancement on PNF S/W Upgrade with EM with Ansible

• REQ-174: Remove dependencies on Python2

New or modified interfaces

modified interface internally (please see the presentation material for details)

If they are modified, are the backwards compatible?

Yes - DMaaP is out of ODL. the change is transparent and backwards compatible for the previous releases.

Interface naming (point to an example)

The APPC R6 Frankfurt API Incoming/Outcoming Independent  - has a list of our incoming and outgoing dependencies.

API from other projects

Involved use cases, architectural capabilities or functional requirements.

vFW, Scale Out, closedloop, vCPE, Change Management

Presentation Material