Fix spacing issues in YAML files in tosca/

[demo.git] / tosca / vCPE / Definitions / onap_dm.yaml

diff --git a/tosca/vCPE/Definitions/onap_dm.yaml b/tosca/vCPE/Definitions/onap_dm.yaml
index 80d1153..c2e9395 100644 (file)
--- a/tosca/vCPE/Definitions/onap_dm.yaml
+++ b/tosca/vCPE/Definitions/onap_dm.yaml
@@ -233,7 +233,7 @@ data_types:
         type: tosca.datatypes.nfv.LogicalNodeData
         description: references (couples) the CP with any logical node I/O requirements (for network devices) that may have been created. Linking these attributes is necessary so that so that I/O requirements that need to be articulated at the logical node level can be associated with the network interface requirements associated with the CP.
         required: false
-  
+
   tosca.datatypes.nfv.injectFile: #used for vCPE usecase
     derived_from: tosca.datatypes.Root
     properties:
@@ -477,10 +477,10 @@ data_types:
         required: false
         constraints:
           - greater_than: 0
-      segmentation_id:  #Introduced from Beijing release, only used for vCPE usecase, outside the scope of SOL001 v2.5.1
+      segmentation_id: #Introduced from Beijing release, only used for vCPE usecase, outside the scope of SOL001 v2.5.1
         type: integer
         required: false
-      physical_network:  #Introduced from Beijing release, only used for vCPE usecase, outside the scope of SOL001 v2.5.1
+      physical_network: #Introduced from Beijing release, only used for vCPE usecase, outside the scope of SOL001 v2.5.1
         type: string
         required: false
   tosca.datatypes.nfv.L3ProtocolData:
@@ -539,7 +539,7 @@ data_types:
          type: tosca.datatypes.nfv.L3ProtocolData
          description: Specifies the L3 protocol data for this virtual link.  Shall be present when the associatedLayerProtocol attribute indicates a L3 protocol and shall be absent otherwise.
          required: false
-  
+
   tosca.datatypes.nfv.VlProfile:
     derived_from: tosca.datatypes.Root
     description: Describes additional instantiation data for a given VL used in a specific VNF deployment flavour.
@@ -854,7 +854,7 @@ data_types:
         description: Configuration parameters for the OperateVnf operation
         required: false
       change_ext_connectivity:
-        type:   tosca.datatypes.nfv.VnfChangeExtConnectivityOperationConfiguration
+        type: tosca.datatypes.nfv.VnfChangeExtConnectivityOperationConfiguration
         description: Configuration parameters for the changeExtVnfConnectivityOpConfig operation
         required: false
   tosca.datatypes.nfv.CpProtocolData:
@@ -1006,7 +1006,7 @@ data_types:
         required: true
       checksum:
         type: string
-        description:  Checksum of the software image file
+        description: Checksum of the software image file
         required: true
       container_format:
         type: string
@@ -1022,7 +1022,7 @@ data_types:
           - valid_values: [ aki, ami, ari, iso, qcow2, raw, vdi, vhd, vhdx, vmdk ]
       min_disk:
         type: scalar-unit.size # Number
-        description:  The minimal disk size requirement for this software image
+        description: The minimal disk size requirement for this software image
         required: true
       min_ram:
         type: scalar-unit.size # Number
@@ -1161,7 +1161,7 @@ interface_types:
 node_types:
   tosca.nodes.nfv.Vdu.Compute:
     derived_from: tosca.nodes.Root
-    description:  Describes the virtual compute part of a VDU which is a construct   supporting the description of the deployment and operational behavior of a VNFC
+    description: Describes the virtual compute part of a VDU which is a construct   supporting the description of the deployment and operational behavior of a VNFC
     properties:
       name:
         type: string
@@ -1274,7 +1274,7 @@ node_types:
         description: Defines the capabilities of virtual_storage.
   tosca.nodes.nfv.Cp:
     derived_from: tosca.nodes.Root
-    description:  Provides information regarding the purpose of the connection point
+    description: Provides information regarding the purpose of the connection point
     properties:
       layer_protocols:
         type: list
@@ -1531,7 +1531,7 @@ policy_types:
         required: false # required if multiple entries in levels
   tosca.policies.nfv.VduInstantiationLevels:
     derived_from: tosca.policies.Root
-    description:  The VduInstantiationLevels type is a policy type representing all the instantiation levels of resources to be instantiated within a deployment flavour in term of the number of VNFC instances to be created from each vdu.Compute. as defined in ETSI GS NFV-IFA 011 [1]
+    description: The VduInstantiationLevels type is a policy type representing all the instantiation levels of resources to be instantiated within a deployment flavour in term of the number of VNFC instances to be created from each vdu.Compute. as defined in ETSI GS NFV-IFA 011 [1]
     properties:
       levels:
         type: map # key: levelId
@@ -1542,7 +1542,7 @@ policy_types:
     targets: [ tosca.nodes.nfv.Vdu.Compute ]
   tosca.policies.nfv.VirtualLinkInstantiationLevels:
     derived_from: tosca.policies.Root
-    description:  The VirtualLinkInstantiationLevels type is a policy type representing all the instantiation levels of virtual link resources to be instantiated within a deployment flavour as defined in ETSI GS NFV-IFA 011 [1].
+    description: The VirtualLinkInstantiationLevels type is a policy type representing all the instantiation levels of virtual link resources to be instantiated within a deployment flavour as defined in ETSI GS NFV-IFA 011 [1].
     properties:
       levels:
         type: map # key: levelId
@@ -1680,7 +1680,7 @@ policy_types:
     targets: [ tosca.nodes.nfv.VduCp, tosca.nodes.nfv.VnfExtCp ]
   tosca.policies.nfv.SupportedVnfInterface:
     derived_from: tosca.policies.Root
-    description:  this policy type represents interfaces produced by a VNF, the details to access them and the applicable connection points to use to access these interfaces
+    description: this policy type represents interfaces produced by a VNF, the details to access them and the applicable connection points to use to access these interfaces
     properties:
       interface_name:
         type: string