...
- How does this project fit into the rest of the ONAP Architecture?
- Expansion of existing ONAP component and expanding it for more complex use cases.
- Depends on SDNC framework which is used as the base platform for the controller.
- Depends on SDC for generating the model 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 by ETSI NFV LCM signatures
- Use TOSCA and YANG for its model definition.
- Use Netconf/Chef and Ansible for component SB interface
- Are there dependencies with other open source projects?
- Opendaylight (part of ONAP controller framework )
...
- link to seed code (if applicable)
- Vendor Neutralif 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:appc
Lifecycle State:Seed
Primary Contact: Reuben Klein
Project Lead: Hector Anapan-Lavalle
mailing list tag [Should match Jira Project Prefix]
Committers:
foo@baravich@amdocs.com
baz@quxha076r@att.com
*Link to TSC approval:
Link to approval of additional submitters: