Artifact Type

Description

Valid on Component Types

HEAT

HEAT  Base template (yaml format). Provided by vendor during on-boarding

VF

HEAT_VOL

HEAT  template defining required volumes (yaml format). Provided by vendor during on-boarding

VF

HEAT_NET

HEAT  template defining required networks (yaml format). Provided by vendor during on-boarding (deprecated)

VF

HEAT_ENV

HEAT Environment artifact (yaml format, extension “.env”). This artifact is accompanied to HEAT template and containing values to subset of the template’s parameters. First version is provided by vendor, then SDC generates new content according to designer changes

VF / VF instance

HEAT_ARTIFACT

Supplementary artifact referenced in HEAT* template (“get_file”). Provided by vendor during on-boarding

VF

HEAT_NESTED

HEAT file referenced from another HEAT file (yaml format). Provided by vendor during on-boarding

VF

YANG_XML

YANG asset based XML

Service / VF / VFC

VNF_CATALOG

YANG asset based XML

Service / VF / VFC

MODEL_INVENTORY_PROFILE

Inventory Asset (XML format). As from 1610 it is generated by SDC during service certification

Service / VF / VFC

MODEL_INVENTORY_PROFILE

Inventory Asset Named  Query Specification (XML format)

Service / VF / VFC

VF_LICENSE

VF License Artifact (XML format). Created during on-boarding of the VF

VF

VENDOR_LICENSE

Vendor License Artifact (XML format). Created during on-boarding of the VF

VF

APPC_CONFIG

configuration artifact

VF

VF_MODULES_METADATA

Json artifact that describes the vfModules of the resource. SDC generates this artifact for every VF instance during the service certification.

Component instance (e.g. VF in Service)

DCAE_TOSCA

TOSCA template used by DCAE (yaml format)

VF / VFCMT (= monitoring template)

DCAE_JSON

JSON description of the DCAE component / template

VF / VFCMT (= monitoring template)

PLANWorkflow artifact typeService / VF / VFC
  • No labels

1 Comment

  1. Hi Micheal, This list of artifact folders appear out-of-date. Is it possible to update it? For instance, Ansible is missing. Also, where do I store the YANG modules for a PNF package when it is supported in Dublin? In a new folder called PNF_YANG_MODULES?