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

For a more detailed overview - https://wiki.onap.org/pages/viewpage.action?pageId=3247130

Architecture  changes from E release:

VF-C catalog migrate to modeling etsicatalog repo which has reported in Architecture meeting 2019-10-15

...

  • VF-C catalog migrates to modeling etsicatalog repo and merges with modeling existing etsicatalog parser service and package management service.
  • To ensure compatibility, the APIs provided keep the same after migration , VF-C promises to update their interfaces call if needed.
  •  In F release, new requirements will be implemented in modeling etsicatalog , VF-C catalog is no longer maintained.

For more component description -  ARC VFC Component Description – Frankfurt

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

...

Reference to the interfaces

VF-C R5 Frankfurt API Swagger yamlUpdate

What are the system limits

...