...
- Support for ONAP use cases V-VOLTE and VCPE
- 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 deployment
Proposed Architecture:
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
- 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 )
...