...
The node template metadata is actually a copy of the metadata from the implementing topology + customizationUUID
Resource metadata parameters definition:
Parameter Name | Parameter Type | Description |
invariantUUID | String | Constant identifier of the resource model. Ex.: AA97B177-9383-4934-8543-0F91A7A02836 |
uuid | String | Versioned identifier of the resource model (this uuid is changed for every major version of the resource) Ex.: b8ff69ca-786d-479e-9f9c-217a90ee0ebc |
customizationUUID | String | Identifier of the resource instance (uuid of the specific use of the resource model in this service). This identifier is regenerated whenever a user makes a change on the resource instance. Ex.: 38e5fb81-5e8c-479b-9140-38786db19967 |
version | String | The resource version in ASDC catalog. Two digit blocks separated by a dot (“.”). Ex. : “2.0” |
name | String | The name of the resource. Ex. “vMME” |
description | String | Description of the resource |
type | String | The type of resource. Resource type can be either VF, VFC, VFCMT, CP or VL. Ex. “VF” |
category | String | Category of the resource. Ex. “Application L4+” |
subcategory | String | Sub-category of the resource. Ex. “Load Balancer” |
Service topology metadata
...