...
- Proposed name for the project:
APPC - Proposed name for the repository:
appc
Project description:
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.
- Model and policy driven application controller with intrinsic VNF management capabilities.
- Support of multi vendor system of VNFs with interdependence
...
- between them.
...
- Provide uploading capabilities of standard data model which describe the management, configuration and inter-dependencies of the VNF.
- APPC model will be based ONAP TOSCA and Yang and contains a dependency model, LCM recipes, configuration templates, policies etc.
- APPC provides multi-protocol southbound plugins, including support for NETCONF, Chef via a Chef Server, and Ansible and ability to operate through vendor specific VNFM/EMS via adaptation through a plugin.
- APPC provides a VNF configuration repository with the latest working configuration for each managed VNF instance it is responsible for.
Scope
- Support for complex ONAP use cases including vVOLTE (with vEPC) and vCPE
- Provide Generic VNF LCM commands for Northbound consumers (SO, Policy, CMO, DCAE, etc.)
- The implementation of LCM commands will use an uploaded VNF Yang model to infer an execution protocol and drive workflows.
- Design-time ability to attach recipes (specified by Directed Graphs, aka DGs) to specific VNF LCM commands, or "Actions" received via the Northbound APIs.
- Provide a model driven configuration API composed from a Yang-based VNF configuration model and set of templates to map payloads to the VNF configuration protocol.
- Provide configuration repository APIs getLatestConfig, configAudit etc.
- Manage the VNF operational state including Blocking, Sequencing and Session Throttling
- Provide conflict resolution for multiple LCM requests
- Provide flexible deployment options such as HA, single node or geo-distributed deployment
Adaptation of additional NBI definitions established by ETSI-MANO using NFV-O to leverage existing APPC functions which already exist, including:
Scale VNF
Terminate VNF
Query VNF
Operate VNF
Modify VNF Information
Get Operation Status
Adaptation of NBI definition at the orchestration level by invoking existing orchestrator functions, including:
Create VNF Identifier
- Delete VNF Identifier
Instantiate VNF
Build additional DGs to implement new ETSI defined NB APIs not currently supported by APPC
Scale VNF to Level
Change VNF Flavour
Heal VNF
...