• SDC shall support accepting an Onboarding package from the VNF Provider. The On-boarding package will specify:
  • VNFs with one or more incremental modules which:
    • Defines additional resources that can be added to an existing VNF
    • Must be complete Heat templates
    • Should define logical growth-units or sub-components of an overall VNF
    • On creation, receives appropriate Base Module outputs as parameters
      • Provides access to all shared resources (by UUID)
      • Must not be dependent on other Add-On VNF Modules
    • Multiple instances of an incremental Module may be added to the same VNF (e.g. incrementally grow a VNF by a fixed “add-on” growth units)
  • Each VNF Module (base or incremental) may have (optional) and associated Cinder Volume Module
    • Volume modules must correspond 1:1 with a base module or incremental module
    • A Cinder volume may be embedded within the base module or incremental module if persistence is not required
  • Shared resource UUIDs are passed between the base module and incremental modules via Heat Outputs Parameters (i.e., Base Module Output Parameters)
    • The output parameter name in the base must match the parameter name in the add-on module
• SDC will support a TOSCA Service Model view at the VNFC (VF_Module) level. This view must be made available to the VID users
• SDC will validate the initial_count for the VF Modules is equal to or greater than the min_vf_module_instances

Source:

https://wiki.onap.org/display/DW/Scaling+Impacts+to+ONAP+Projects