the SDC CSAR structure is separated into 3 phases:
CSAR provided by the vendor to the SDC for onboarding:
this is the currently expected structure supported by SDC
ROOT\
MainServiceTemplate.mf [a map representing the different parts of the CSAR structure.]
MainServiceTemplate.yaml [copy of the main service template located under Defanitions]
\TOSCA-Metadata\
TOSCA.meta [ metadata regarding the CSAR structure]
\Artifacts\ [includes all artifacts.]
Images are not supported.
Artifact type will be identified by an additional folder under “Informational”/“Deployment” that will define the artifact type SDC supported artifact types can be found here: SDC supported artifact types.
Artifacts at the root directory or unrecognized folder(s) will be classified as type “Other”
\Informational\ [will hold all informative artifacts in the direct asset level]
\Deployment\ [Sub-folder directly under “Artifacts”– Deployment artifacts in the direct asset level]
\<VFC TOSCA name>\
\Informational\ [will hold all informative artifacts on VFC level ]
\Deployment\ [will hold all deployment artifacts on VFC level ]
\Definitions\ [includes all TOSCA yaml files ]
CSAR created by SDC for VF:
ROOT\
\TOSCA-Metadata\
TOSCA.meta [ metadata regarding the CSAR structure]
\Artifacts\ [includes all artifacts.]
Artifact type will be identified by an additional folder under “Informational”/“Deployment” that will define the artifact type SDC supported artifact types can be found here: SDC supported artifact types.
Artifacts at the root directory or unrecognized folder(s) will be classified as type “Other”
\Informational\ [will hold all informative artifacts in the direct asset level]
\Deployment\ [Sub-folder directly under “Artifacts”– Deployment artifacts in the direct asset level]
\<VFC TOSCA name>\
\Informational\ [will hold all informative artifacts on VFC level ]
\Deployment\ [will hold all deployment artifacts on VFC level ]
\Resources\
\<node_template name>\ [per each node_template that has specific artifacts (artifacts that were added to the instance / customized for the instance or generated for the instance).
This folder should NOT include artifacts of the type of the instance (e.g. HEAT should be in the folder of the VF and not in the folder of the VF instance, HEAT_ENV will be in the folder of the instance)]
\Definitions\ [includes all TOSCA yaml files ]
CSAR created by SDC for SERVICE:
ROOT\
\TOSCA-Metadata\
TOSCA.meta [ metadata regarding the CSAR structure]
\Artifacts\ [includes all artifacts.]
Artifact type will be identified by an additional folder under “Informational”/“Deployment” that will define the artifact type SDC supported artifact types can be found here: SDC supported artifact types.
Artifacts at the root directory or unrecognized folder(s) will be classified as type “Other”
\Informational\ [will hold all informative artifacts in the direct asset level]
\Deployment\ [Sub-folder directly under “Artifacts”– Deployment artifacts in the direct asset level]
\<VF TOSCA name>\
\Informational\ [will hold all informative artifacts on VF level ]
\Deployment\ [will hold all deployment artifacts on VF level ]
\Resources\
\<node_template name>\ [per each node_template that has specific artifacts (artifacts that were added to the instance / customized for the instance or generated for the instance).
This folder should NOT include artifacts of the type of the instance (e.g. HEAT should be in the folder of the VF and not in the folder of the VF instance, HEAT_ENV will be in the folder of the instance)]
\Deployment\
\BPMN\ [Includes all workflow BPMN artifact files]
\Definitions\ [includes all TOSCA yaml files ]
CSAR examples:
vendor CSAR:
VF CSAR:
SERVICE CSAR: