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?Hi All,
Here is the summary and actions from today’s call:
