Page Comparison

...

• 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,
• GVNFM Component
  
  There is no scope and architecture changes for VF-C in Dublin release.  For a more detailed overview - https://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=324713016223923

New component capabilities for Dublin, i.e. the functional enhancements

...

1. OOF Integration Optimization
   Optimize the methodology for VNF(vdu) placement, add the process for placement with selected candidates(VIM)
   
2. SOL005 Interface alignment
   a. existing APIs alignment
   b. add the APIs which supported in SOL005, such as package subscription and notification
3. Upgrade Mutlicloud API invocation to support Centralized Representation and Consistent Identification of Cloud Region functional requirement

 Platform enhancements

...

Reference to the interfaces

VF-C R4 API UpdateSwagger yaml

What are the system limits

...

Involved use cases, architectural capabilities or functional requirements

1. Use case support

   1. CCVPN Use Case (Dublin)
   2. Use Case: Residential Broadband vCPE (Approved)
   3. Use Case: vFW/vDNS (Approved)

2. Functional Requirements support 

      a. Centralized Representation and Consistent Identification of Cloud Regions In ONAP

      b. Hardware Platform Enablement In ONAP

Platform Maturity Targets

...