Project Name:
- Proposed name for the project:
APPC - Proposed name for the repository:
appc
Project description:
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 contain dependency model , LCM recipes , configuration templates , policies etc.
APPC provide multi protocol south bound plugin , including NETCONF ,Chef, Ansible and ability to provide vendor specific VNFM/EMS adaptation plugin.
APPC provide VNF configuration repository with latest working configuration for each of the VNF instances it is responsible for.
Scope
- Support for ONAP use cases V-VOLTE and VCPE
- Describe the functionality to be provided by the project. Please provide the full intended scope of the project; not just what is intended for the project's first release.
- Specify any interface/API specification proposed,
- Identity a list of features and functionality will be developed.
- Identify what is in or out of scope. During the development phase, it helps reduce discussion.
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
- Please Include architecture diagram if possible
- What other ONAP projects does this project depend on?
- How does this align with external standards/specifications?
- APIs/Interfaces
- Information/data models
- Are there dependencies with other open source projects?
- APIs/Interfaces
- Integration Testing
- etc.
Resources:
- Primary Contact Person
- Names, gerrit IDs, and company affiliations of the committers
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable)
- Vendor Neutral
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
- Meets Board policy (including IPR)
Use the above information to create a key project facts section on your project page
Key Project Facts
Project Name:
- JIRA project name:
- JIRA project prefix:
Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix]
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval:
Link to approval of additional submitters: