...
- support NS and VNF lifecycle management based on the ONAP tosca data model and workflow
- support integration with multi VNFMs via drivers, which include vendors VNFM and generic VNFM
- support integration with multi VNFs via generic VNFM, which does not provide VNFM function
- support integration with multi VIMS via Multi-VIM, which include the opensource and commercial VIMs
- support microservice architecture and model driven orchestration and management
VF-C has two main components: - NFV-O Component,
- compliant with ETSI NFV MANO architecture,
- providing resource orchestration and full life cycle management and FCAPS for NS,
- providing standard south bound interface to VNFMs,
- providing north bound interface to SO, to take part in fulfilling the orchestraion and operation of end2end service,
- providing interface and work with DCAE and Policy for Close Loop Automation.
- GVNFM Component,
- compliant with ETSI NFV MANO architecture
- providing full life cycle management and FCAPS for VNFs which do not require a vendor VNFM
There is no scope and architecture changes for VF-C in Dublin release. For a more detailed overview - https://wiki.onap.org/pages/viewpage.action?pageId=3247130
New component capabilities for Dublin, i.e. the functional enhancements
Functional enhancements
- OOF Integration Optimization
Optimize the methodology for VNF(vdu) placement, add the process for placement with selected candidates(VIM) - SOL005 Interface alignment
a. existing APIs alignment
b. add the APIs which supported in SOL005, such as package subscription and notification - Upgrade Mutlicloud API invocation to support Centralized Representation and Consistent Identification of Cloud Region functional requirement
Platform enhancements
Mysql DB migrates to OOM shared MariaDB Galera Cluster which can be used to meet S3P HA requirements.
- Update VF-C DB Helm Chart
- Update VF-C component to leverage new MariaDB Galera Cluster
- Docker configuration update
- DB script migrate
- Other work
- SOL005 Interface
- Example: Providing example "Helm" init containers to setup Volumes
- AAF is refactoring existing maintenance processes online for Open Source (meaning non company specific), including
- Analysis of expiring Creds and Roles
- Generation of Approval records
- Notification of Approvals, Creds and Roles in an external company configurable way.
- Configuration Improvement
- Investigate all VF-C configuration could be automatically injected through OOM.
- Data Persistence
Add data persistent storage to avoid data loss due to pod restart
New or modified interfaces
...
Reference to the interfacesxxx
What are the system limits
NoNow the component Redundancy and scaling depends on Kubernetes.
Involved use cases, architectural capabilities or functional requirements
Use case support
Functional Requirements support
a.
...
Centralized Representation and Consistent
...
Identification of Cloud Regions In ONAP
b.
...
Hardware Platform Enablement In ONAP
Platform Maturity Targets
- CII Badge silver is the stretch goal (lack resource)
- 55% code coverage, all repos have already passed
Listing of new or impacted models used by the project (for information only)
...
Support for service/VNF DM and align with the above data model proposed by the modelling subcommittee in Dublin release