From 624a161b39f456a2f15f2278d2d7e41fdc34281a Mon Sep 17 00:00:00 2001 From: Ikram Ul Haq Date: Tue, 6 Feb 2024 19:06:55 +0500 Subject: [PATCH] fix issue #17 - [v4.5.1] fix definition of ExtVirtualLinkData Note2 in SOL002_def.yaml --- .../General_Definitions/SOL002_def.yaml | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/src/SOL002/General_Definitions/SOL002_def.yaml b/src/SOL002/General_Definitions/SOL002_def.yaml index cc85e2c5..ea4e80c0 100644 --- a/src/SOL002/General_Definitions/SOL002_def.yaml +++ b/src/SOL002/General_Definitions/SOL002_def.yaml @@ -722,16 +722,16 @@ definitions: * NOTE 1: The information about the VIM connection referenced by the VIM connection id is known to the VNFM. Moreover, the identifier of the VIM connection provides scope to the resourceId. - * NOTE 2: A link port is not needed for an external CP instance that exposes a CP in the following cases: - 1) For a VIP CP directly exposed as an external CP: - 1.1) No dedicated IP address is allocated as VIP address, as indicated in the VNFD. - 1.2) A dedicated IP address is allocated as VIP address, but the NFVO indicates that no port is needed - (createExtLinkPort in VnfExtCpConfig set to false). - 2) For a VIP CP exposed as an external CP via a floating IP address: - 2.1) No dedicated IP address is allocated as VIP address, as indicated in the VNFD, and the VNFC CP - associated to the VIP CP is also exposed via a floating IP address. - 3) For a VIRTUAL CP exposed as an external CP. - 4) For a VNFC CP exposed as an external CP in a secondary container cluster external network. + * NOTE 2: A link port is not needed for an external CP instance that exposes a CP in the following cases: + 1) For a virtual IP CP directly exposed as an external CP: + 1.1) No dedicated IP address is allocated as virtual IP address, as indicated in the VNFD. + 1.2) A dedicated IP address is allocated as virtual IP address, but the NFVO indicates that no port is + needed (createExtLinkPort in VnfExtCpconfig set to false). + 2) For a virtual IP CP exposed as an external CP via a floating IP address: + 2.1) No dedicated IP address is allocated as virtual IP address, as indicated in the VNFD, and the VNFC + CP associated to the virtual IP CP is also exposed via a floating IP address. + 3) For a VIRTUAL CP exposed as an external CP. + 4) For a VNFC CP exposed as an external CP in a secondary container cluster external network. * NOTE 3: An example of the network attachment definition resource when the container infrastructure service management is a Kubernetes® instance is a network attachment definition (NAD). -- GitLab