[datamodel-upd][SOL003][VNF-OP-GRANT][ v5.2.1][7.3.2.x.x Test-IDs] Change...

      "description": "Information about external VLs to connect the VNF to. See notes 5, 7 and 8. If this attribute  is present according to note 5 or note 7, it need not contain those entries that are unchanged  compared to the entries that were passed in the LCM operation which is related to this granting exchange.\n",

      "type": "array",

      "items": {

        "description": "This type represents an external VL.\n* NOTE 1:\tA link port is not needed for an external CP instance that exposes a  CP in the following cases:\n          1)  For a VIP CP directly exposed as an external CP:\n              1.1)  No dedicated IP address is allocated as VIP address, as indicated in the VNFD.\n              1.2)  A dedicated IP address is allocated as VIP address, but the NFVO indicates that no port is needed\n                    (createExtLinkPort in VnfExtCpConfig set to false).\n          2)  For a VIP CP exposed as an external CP via a floating IP address:\n              2.1)  No dedicated IP address is allocated as VIP address, as indicated in the VNFD, and the VNFC CP\n                    associated to the VIP CP is also exposed via a floating IP address.\n          3)  For a VIRTUAL CP exposed as an external CP.\n          4)  For a VNFC CP exposed as an external CP in a secondary container cluster external network or a\n              secondary container cluster internal network.\n\n* NOTE 2: An example of the network attachment definition resource when the container infrastructure service\n          management is a Kubernetes® instance is a network attachment definition (NAD).\n* NOTE 3: Either \"extCps\" or “extCpsDeletion\" shall be present, but not both.\n",

        "description": "This type represents an external VL.\n* NOTE 1:\tA link port is not needed for an external CP instance that exposes a  CP in the following cases:\n          1)  For a VIP CP directly exposed as an external CP:\n              1.1)  No dedicated IP address is allocated as VIP address, as indicated in the VNFD.\n              1.2)  A dedicated IP address is allocated as VIP address, but the NFVO indicates that no port is needed\n                    (createExtLinkPort in VnfExtCpConfig set to false).\n          2)  For a VIP CP exposed as an external CP via a floating IP address:\n              2.1)  No dedicated IP address is allocated as VIP address, as indicated in the VNFD, and the VNFC CP\n                    associated with the VIP CP is also exposed via a floating IP address.\n          3)  For a VIRTUAL CP exposed as an external CP.\n          4)  For a VNFC CP exposed as an external CP in a secondary container cluster external network or a\n              secondary container cluster internal network.\n\n* NOTE 2: An example of the network attachment definition resource when the container infrastructure service\n          management is a Kubernetes® instance is a network attachment definition (NAD).\n* NOTE 3: Either \"extCps\" or “extCpsDeletion\" shall be present, but not both.\n",

        "type": "object",

        "required": [

          "id",