Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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://wiki.onap.org/pages/viewpage.action?pageId=3247130

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

      

 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. Update Mutlicloud API invocation to support Centralized Representation and Consistent Identification of Cloud Region functional requirement


 Platform enhancements

  1. Mysql DB migrates to OOM shared MariaDB Galera Cluster which can be used to meet S3P HA requirements.

    1. Update VF-C DB Helm Chart
    2. Update VF-C component to leverage new MariaDB Galera Cluster 
      1. Docker configuration update 
      2. DB script migrate 
      3. Other work 
  2. Configuration Improvement
    1. Investigate all VF-C configuration could be automatically injected through OOM.
  3. Data Persistence
    Add data persistent storage to avoid data loss due to pod restart
  4. OOF Integration Optimization 
    Optimize the methodology for VNF(vdu) placement, add the process for placement with selected candidates(VIM)

...

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

...