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: ''

<<<<<<<<

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: ''

<<<<<<<<<