Versions Compared

Old Version 3

changes.mady.by.user Alex Vul

Saved on

compared with

New Version Current

changes.mady.by.user Alex Vul

Saved on

Key

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

Background

Assume that specification of hardware platform capability requirements for R2 will be based on TOSCA templates. TOSCA templates may mayEveryo optionally contain capability clauses defining hardware platform capability requirements. The capability requirements will be specified as comma separated lists of tuples. The ONAP information model specifies the following sets of (optional) hardware capability requirements - CPU, memory, storage and network. The requirement sets are associated with specific VDUs. If  If hardware capability requirements are provided, SDC will need to parse them and internalize them in a format suitable for use during initial instantiation and operation. Tuple parsing tools will be required to parse requirement strings. We can use the same tools as the ones provided for VNFD validation, as part of the VNF SDK, for this purpose.

Questions:

  • What is the SDC-internal VNFD format look like? JSON? YAML?
  • Is the VNFD contained in the catalog, or elsewhere?
    • How does SO extract the VNFD information from the SDC?


    Assumptions & Decisions


    Assumption/Decision

    1Support for HPA assumes a TOSCA based VNF.
    2Support for HPA in HEAT based VNFs is out of scope.
    3HPA information is to be captured per VDU/VNFC. Anatoly to review and come with a proposal for a modeling approach.
    4Michael to schedule a meeting to discuss VID/SO "orchestration type" solution.
    5

    Stretch goals...

    • HEAT/TOSCA and licenses model builder/translator.
    • On-boarding - image upload to Multi-VIM.
    • On-boarding - SDC/VNFSDK integration.
    • Implement SDC model.
    6Michael/Roy to enter relevant epics into SDC and VID.