Commit faf186ea authored by Eisha Ayaz's avatar Eisha Ayaz Committed by Giacomo Bernini
Browse files

[datamodel-upd][SOL003][VNF-LCM][ v5.2.1][7.3.1.x.x Test-IDs] Change... 

[datamodel-upd][SOL003][VNF-LCM][ v5.2.1][7.3.1.x.x Test-IDs] Change description of attribute for type : vnfInstance
parent fda931ef

SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfo.schema.json

+3 −3
Original line number Diff line number Diff line
@@ -776,7 +776,7 @@ 
                  }

                },

                "extCpInfo": {

                  "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.See note 7.\n",

                  "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated with sub-ports of a trunk.See note 7.\n",

                  "type": "array",

                  "items": {

                    "description": "This type represents information about an external CP of a VNF.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n        \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated with a link port in the cases indicated for the \n        \"extLinkPorts\" attribute in clause 4.4.1.11.\nNOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network \n        attachment definition resource is needed to fulfil the connectivity requirements of the external \n        CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
@@ -1015,7 +1015,7 @@ 
                  }

                },

                "vipCpInfo": {

                  "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",

                  "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated with an external CP of the VNF instance. May be present otherwise.\n",

                  "type": "array",

                  "minItems": 1,

                  "items": {
@@ -1212,7 +1212,7 @@ 
                  }

                },

                "virtualCpInfo": {

                  "description": "Virtual CPs that are part of the VNF instance. Shall be present when a particular Virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",

                  "description": "Virtual CPs that are part of the VNF instance. Shall be present when a particular Virtual CP is associated with an external CP of the VNF instance. May be present otherwise.\n",

                  "type": "array",

                  "items": {

                    "description": "This type provides information related to a virtual CP instance of a VNF.\nNOTE 1: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n        accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n        and filtering by corresponding \"vduIds\" values.\nNOTE 2: The information can be omitted because it is already available as part of the external CP information in the \n        VnfExtCpInfo structure.\n",

SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotInfoModifications.schema.json

+3 −3
Original line number Diff line number Diff line
@@ -768,7 +768,7 @@ 
									}

								},

								"extCpInfo": {

									"description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.See note 7.\n",

									"description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated with sub-ports of a trunk.See note 7.\n",

									"type": "array",

									"items": {

										"description": "This type represents information about an external CP of a VNF.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n        \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated with a link port in the cases indicated for the \n        \"extLinkPorts\" attribute in clause 4.4.1.11.\nNOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network \n        attachment definition resource is needed to fulfil the connectivity requirements of the external \n        CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
@@ -1007,7 +1007,7 @@ 
									}

								},

								"vipCpInfo": {

									"description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",

									"description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated with an external CP of the VNF instance. May be present otherwise.\n",

									"type": "array",

									"minItems": 1,

									"items": {
@@ -1204,7 +1204,7 @@ 
									}

								},

								"virtualCpInfo": {

									"description": "Virtual CPs that are part of the VNF instance. Shall be present when a particular Virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",

									"description": "Virtual CPs that are part of the VNF instance. Shall be present when a particular Virtual CP is associated with an external CP of the VNF instance. May be present otherwise.\n",

									"type": "array",

									"items": {

										"description": "This type provides information related to a virtual CP instance of a VNF.\nNOTE 1: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n        accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n        and filtering by corresponding \"vduIds\" values.\nNOTE 2: The information can be omitted because it is already available as part of the external CP information in the \n        VnfExtCpInfo structure.\n",

SOL003/VNFLifecycleManagement-API/schemas/VnfSnapshotsInfo.schema.json

+3 −3
Original line number Diff line number Diff line
@@ -778,7 +778,7 @@ 
                    }

                  },

                  "extCpInfo": {

                    "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.See note 7.\n",

                    "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated with sub-ports of a trunk.See note 7.\n",

                    "type": "array",

                    "items": {

                      "description": "This type represents information about an external CP of a VNF.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n        \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated with a link port in the cases indicated for the \n        \"extLinkPorts\" attribute in clause 4.4.1.11.\nNOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network \n        attachment definition resource is needed to fulfil the connectivity requirements of the external \n        CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
@@ -1017,7 +1017,7 @@ 
                    }

                  },

                  "vipCpInfo": {

                    "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",

                    "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated with an external CP of the VNF instance. May be present otherwise.\n",

                    "type": "array",

                    "minItems": 1,

                    "items": {
@@ -1214,7 +1214,7 @@ 
                    }

                  },

                  "virtualCpInfo": {

                    "description": "Virtual CPs that are part of the VNF instance. Shall be present when a particular Virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",

                    "description": "Virtual CPs that are part of the VNF instance. Shall be present when a particular Virtual CP is associated with an external CP of the VNF instance. May be present otherwise.\n",

                    "type": "array",

                    "items": {

                      "description": "This type provides information related to a virtual CP instance of a VNF.\nNOTE 1: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n        accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n        and filtering by corresponding \"vduIds\" values.\nNOTE 2: The information can be omitted because it is already available as part of the external CP information in the \n        VnfExtCpInfo structure.\n",

SOL003/VNFLifecycleManagement-API/schemas/vnfInstance.schema.json

+3 −3
Original line number Diff line number Diff line
@@ -726,7 +726,7 @@ 
          }

        },

        "extCpInfo": {

          "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.See note 7.\n",

          "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated with sub-ports of a trunk.See note 7.\n",

          "type": "array",

          "items": {

            "description": "This type represents information about an external CP of a VNF.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n        \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated with a link port in the cases indicated for the \n        \"extLinkPorts\" attribute in clause 4.4.1.11.\nNOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network \n        attachment definition resource is needed to fulfil the connectivity requirements of the external \n        CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
@@ -965,7 +965,7 @@ 
          }

        },

        "vipCpInfo": {

          "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",

          "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated with an external CP of the VNF instance. May be present otherwise.\n",

          "type": "array",

          "minItems": 1,

          "items": {
@@ -1162,7 +1162,7 @@ 
          }

        },

        "virtualCpInfo": {

          "description": "Virtual CPs that are part of the VNF instance. Shall be present when a particular Virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",

          "description": "Virtual CPs that are part of the VNF instance. Shall be present when a particular Virtual CP is associated with an external CP of the VNF instance. May be present otherwise.\n",

          "type": "array",

          "items": {

            "description": "This type provides information related to a virtual CP instance of a VNF.\nNOTE 1: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n        accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n        and filtering by corresponding \"vduIds\" values.\nNOTE 2: The information can be omitted because it is already available as part of the external CP information in the \n        VnfExtCpInfo structure.\n",

SOL003/VNFLifecycleManagement-API/schemas/vnfInstances.schema.json

+3 −3
Original line number Diff line number Diff line
@@ -728,7 +728,7 @@ 
            }

          },

          "extCpInfo": {

            "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated to sub-ports of a trunk.See note 7.\n",

            "description": "Information about the external CPs exposed by the VNF instance. When trunking is enabled, the list of entries includes both, external CPs corresponding to parent ports of a trunk, and external CPs associated with sub-ports of a trunk.See note 7.\n",

            "type": "array",

            "items": {

              "description": "This type represents information about an external CP of a VNF.\nNOTE 1:\tThe attributes \"associatedVnfcCpId\", \"associatedVipCpId\", \"associatedVirtualCpId\" and \n        \"associatedVnfVirtualLinkId\" are mutually exclusive. Exactly one shall be present.\nNOTE 2:\tAn external CP instance is not associated with a link port in the cases indicated for the \n        \"extLinkPorts\" attribute in clause 4.4.1.11.\nNOTE 3: Cardinality greater than 1 is only applicable for specific cases where more than one network \n        attachment definition resource is needed to fulfil the connectivity requirements of the external \n        CP, e.g. to build a link redundant mated pair in SR-IOV cases.\nNOTE 4: When more than one netAttDefResourceId is indicated, all shall belong to the same namespace.\n",
@@ -967,7 +967,7 @@ 
            }

          },

          "vipCpInfo": {

            "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated to an external CP of the VNF instance. May be present otherwise.\n",

            "description": "VIP CPs that are part of the VNF instance. Shall be present when that particular VIP CP of the VNFC instance is associated with an external CP of the VNF instance. May be present otherwise.\n",

            "type": "array",

            "minItems": 1,

            "items": {
@@ -1164,7 +1164,7 @@ 
            }

          },

          "virtualCpInfo": {

            "description": "Virtual CPs that are part of the VNF instance. Shall be present when a particular Virtual CP is associated to an external CP of the VNF instance. May be present otherwise.\n",

            "description": "Virtual CPs that are part of the VNF instance. Shall be present when a particular Virtual CP is associated with an external CP of the VNF instance. May be present otherwise.\n",

            "type": "array",

            "items": {

              "description": "This type provides information related to a virtual CP instance of a VNF.\nNOTE 1: A consumer of the VNF LCM interface can learn the actual VNFC instances implementing the service \n        accessible via the virtual CP instance by querying the \"vnfcResourceInfo\" from the \"InstantiatedVnfInfo\" \n        and filtering by corresponding \"vduIds\" values.\nNOTE 2: The information can be omitted because it is already available as part of the external CP information in the \n        VnfExtCpInfo structure.\n",