This is a short description of the metadata fields currently used in the ECOMP SDC product.
The current ECOMP SDC manages metadata for the following constructs:
- a resource or service topology
- a node template
As for now, SDC does not use metadata with TOSCA type definitions (including node types).
Resource topology metadata
Example:
>>>>>>
tosca_definitions_version: tosca_simple_yaml_1_1
metadata:
invariantUUID: 9ff87055-7b97-4b70-8a93-7522555ee59e
UUID: 6287dc96-db94-4982-a693-4abb9a2bc459
name: ak_vf_with_port
description: dddd
type: VF
category: Network L2-3
subcategory: Router
resourceVendor: vvvvv
resourceVendorRelease: '11111111'
resourceVendorModelNumber: ''
<<<<<<
Resource node template metadata
Example:
>>>>>>>>
node_templates:
ak_vf_with_port 0:
metadata:
invariantUUID: 9ff87055-7b97-4b70-8a93-7522555ee59e
UUID: 6287dc96-db94-4982-a693-4abb9a2bc459
customizationUUID: 420fe343-da60-4737-a74c-6d31431c6fe1
version: '0.1'
name: ak_vf_with_port
description: dddd
type: VF
category: Network L2-3
subcategory: Router
resourceVendor: vvvvv
resourceVendorRelease: '11111111'
resourceVendorModelNumber: ''
<<<<<<<<
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
Example:
>>>>>>>>
tosca_definitions_version: tosca_simple_yaml_1_1
metadata:
invariantUUID: ad459a6a-8404-4806-be91-a4a6ac1c79af
UUID: 5f1a4a27-0adc-49ed-8407-0566574147f7
name: ak_service_with_vf_with_port
description: ddddd
type: Service
category: Network L1-3
serviceType: ''
serviceRole: ''
serviceEcompNaming: true
ecompGeneratedNaming: true
namingPolicy: ''
<<<<<<<<<
Resource Metadata Fields
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 types currently in use: VF, VFC, CP, VL, PNF, ServiceProxy, Configuration Ex. “VF” |
category | String | Category of the resource. Ex. “Application L4+” |
subcategory | String | Sub-category of the resource. Ex. “Load Balancer” |
Resource Categories
Category | Sub Category |
---|---|
Network L2-3 | LAN Connectors, WAN Connectors, Router, Gateway, Infrastructure |
Network L4+ | Common Network Resources |
Application L4+ | Border Element, Database, Application Server, Web Server, Call Control, Media Servers, Load Balancer, Firewall |
Generic | Infrastructure, Database, Abstract, Rules, Network Elements |
Network Connectivity | Connection Points, Virtual Links |
DCAE Component | Analytics, Policy, Utility, Collector, Source, Microservice, Database |
Template | Monitoring Template |
Allotted Resource | Tunnel XConnect, IP Mux Demux, Allotted Resource, Security Zone, Contrail Route, Service Admin |
Service Categories
Category |
---|
Mobility |
Network L1-3 |
Network L4+ |
VoIP Call Control |
3 Comments
Priya TG
Hello, It is OK to have metadata per service template. But meta data per node type in the node template section could be too much of information to comprehend and affects readability and clarity of the model.
Anatoly Katzman
Arguable
maopeng zhang
Hi Anatoly
Could we get the ONAP R1 SDC Metadata as input? In R1, Service Categories supports E2E service and network service. Thanks.