...
- 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.
- Provide Generic VNF LCM commands for NB consumers (SO , Policy ,CMO, DCAE etc) .
- LCM commands implementation will use the uploaded VNF model for infer the execution protocol and workflow.
- Design time ability for attach recipe to specific VNF LCM command implementation (DG based).
- Provide model driven configuration API composed from Yang based VNF configuration model and set of templates which maps the payload to the VNF configuration protocol.
- Provide configuration repository APIs getLatestConfig , configAudit etc
- Manages the VNF operational state including blocking/Sequencing/throttling and conflict resolution for LCM requests
- Provide flexible deployment options such as HA ,single node or geo distributed deploymentIdentify 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?
- 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
- 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
- Inspierd by ETSI NFV LCM signatures
- Use TOSCA and YANG for its model definition.
- Use Netconf/Chef and Ansible for component SB interface Information/data models
- Are there dependencies with other open source projects?
- APIs/Interfaces
- Integration Testing
- etc.
- Opendaylight (part of ONAP controller framework )
Resources:
- Primary Contact Person
- Names, gerrit IDs, and company affiliations of the committers
- Names and affiliations of any other contributors
- -Reuben Klein AT&T
- Avi Chapnick - Amdocs
- Hector Anapan - AT&T
- Jamil Chawki - Orange
- Vimal Begwani - AT&TProject 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)
...