...
APPC model will be based ONAP Tosca TOSCA and Yang and contain dependency contains a dependency model, LCM recipes, configuration templates, policies etc.
APPC provide provides multi-protocol south bound plugin southbound plugins, including support for NETCONF, Chef via a Chef Server, and Ansible and and ability to provide operate through vendor specific VNFM/EMS via adaptation through a plugin.
APPC provide provides a VNF configuration repository with the latest working configuration for each of the managed VNF instances instance it is responsible for.
Scope
- Support for complex ONAP use cases V-VOLTE and VCPEincluding vVOLTE (with vEPC) and vCPE
- Provide Generic VNF LCM VNF LCM commands for NB Northbound consumers (SO, Policy, CMO, DCAE, etc.) .
- The implementation of LCM commands implementation will use the an uploaded VNF Yang model for to infer the an execution protocol and workflowdrive workflows.
- Design-time ability for attach recipe to attach recipes (specified by Directed Graphs, aka DGs) to specific VNF LCM command implementation (DG based) commands, or "Actions" received via the Northbound APIs.
- Provide a model driven configuration API composed from a Yang-based VNF configuration model and set and set of templates which maps the payload to map payloads to the VNF configuration protocol.
- Provide configuration repository APIs getLatestConfig, configAudit etc.
- Manages the VNF operational state including blocking/Blocking, Sequencing /throttling and Session Throttling
- Provides conflict resolution for multiple LCM requests requests
- Provide flexible deployment options such as HA, single node or geo-distributed deployment
Proposed Architecture:
...
- How does this project fit into the rest of the ONAP Architecture?
- Expansion of existing APPC ONAP component and expanding it for to support more complex use cases.
- Depends Establish dependence on the SDNC framework which is framework (aka Controller framework) to be used as the base platform for the controller.
- Depends on SDC Service Designer for generating the model(s) and other artifacts necessary for specifying controller runtime behavior
- Depends on Multi VIM project for cloud infrastructure APIs
- How does this align with external standards/specifications?
- Inspierd Inspired by ETSI NFV LCM signatures
- Use TOSCA and YANG for its all model definitiondefinitions.
- Use Netconf/Chef and Ansible for component SB interface southbound interface
- Are there dependencies with other open source projects?
- Opendaylight (part of ONAP controller framework)
...
- Primary Contact Person - Reuben Klein, AT&T
- Avi Chapnick - Amdocs
- Hector Anapan - AT&T
- Jamil Chawki - Orange
- Vimal Begwani - AT&T
- Paul Bartoli - AT&T
- Marcus Williams - Intel
...
Repo name:appc
Lifecycle State:Seed
Primary Contact: Reuben Klein
Project Lead: Hector Anapan-Lavalle
mailing list tag [Should match Jira Project Prefix]
Committers:
Avi Chapnick - avich@amdocs.com
Hector Anapan-Lavalle - ha076r@att.com
Marcus Williams - marcus.williams@intel.com
Patrick Brady - pb071s@att.com
*Link to TSC approval:
Link to approval of additional submitters: