/
APPC Project Proposal (5/12/17)

APPC Project Proposal (5/12/17)

May 17, 2019

Project Name:

  • 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 on ONAP TOSCA and Yang containing 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

Proposed Architecture:

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?

    • Expansion of existing APPC ONAP component to support more complex use cases.

    • Establish dependence on the Common Controller SDK to be used as the base platform for the controller.

    • Depends on 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?

    • Inspired by ETSI NFV LCM signatures

    • Use TOSCA and YANG for all model definitions.

    • Use Netconf/Chef and Ansible for component southbound interface

  • Are there dependencies with other open source projects?

    • Opendaylight (part of ONAP controller framework)

Resources:

Other Information:

  • link to seed code (if applicable)
    https://gerrit.onap.org/r/#/admin/projects/appc

  • Vendor Neutral
    The current seed code has been already scanned and cleanup to remove all proprietary trademarks, logos, etc. except openecomp to be replaced by onap

    Subsequent modification to the existing seed code should continue to follow the same scanning and clean up principles.

  • Meets Board policy (including IPR)

Key Project Facts

Project Name:

Repo name:appc
Lifecycle State:Seed
Primary Contact: Reuben Klein
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
Piyush Garg - Piyush.Garg1@amdocs.com

@Marcus Williams - marcus.williams@intel.com 

Patrick Brady - pb071s@att.com

Skip Wonnell - kw5258@att.com

Randa Maher - rx196w@att.com

 

*Link to TSC approval: 
Link to approval of additional submitters: