Loading src/definitions/SOL002SOL003_def.yaml +15 −8 Original line number Diff line number Diff line Loading @@ -313,7 +313,8 @@ definitions: The applicable "VimConnectionInfo" structure, which is referenced by vimConnectionId, can be obtained from the "vimConnectionInfo" attribute of the "VnfInstance" structure. structure. (This applies in case of SOL003) See note 1. (This applies in case of SOL002) $ref: "#/definitions/Identifier" resourceProviderId: description: > Loading @@ -325,12 +326,12 @@ definitions: resourceId: description: > Identifier of the resource in the scope of the VIM or the CISM or the resource provider. See note 2. CISM or the resource provider. See note 3. $ref: "#/definitions/IdentifierInVim" vimLevelResourceType: description: > Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 1. or the resource provider. See note 2. type: string vimLevelAdditionalResourceInfo: descriptions: > Loading Loading @@ -629,6 +630,9 @@ definitions: This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 4.4.1.10d-1. This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. It shall comply with the provisions defined in table 5.5.3.6d-1. (This applies in case of SOL002) * NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used, otherwise it will be ignored by the CISM. Loading @@ -655,7 +659,10 @@ definitions: ExtVirtualLinkData: description: > This type represents an external VL. * NOTE 1: A link port is not needed for an external CP instance that exposes a VIP CP in the following cases: * 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. (This applies in case of SOL002) * NOTE 2: A link port is not needed for an external CP instance that exposes a VIP 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 Loading @@ -667,7 +674,7 @@ definitions: 4 For a VNFC CP exposed as an external CP in a secondary container cluster external network or a secondary container cluster internal network. * NOTE 2: An example of the network attachment definition resource when the container infrastructure service * 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). type: object required: Loading @@ -684,7 +691,7 @@ definitions: description: > Identifier of the VIM connection to manage this resource. This attribute shall only be supported and present if VNF-related resource management in direct mode is applicable. resource management in direct mode is applicable. See note 1. $ref: "#/definitions/Identifier" resourceProviderId: description: > Loading Loading @@ -713,7 +720,7 @@ definitions: external connection points to this external VL. If this attribute is not present, the VNFM shall create the link ports on the external VL except in the cases defined below. See note 1. below. See note 2. type: array items: $ref: "#/definitions/ExtLinkPortData" Loading @@ -721,7 +728,7 @@ definitions: description: > Externally provided network attachment definition resource(s) that provide the specification of the interface to attach external CPs to this external VL. See note 2. to attach external CPs to this external VL. See note 3. It is only applicable if the external VL is realized by a secondary container cluster network. It shall not be present otherwise. Loading Loading
src/definitions/SOL002SOL003_def.yaml +15 −8 Original line number Diff line number Diff line Loading @@ -313,7 +313,8 @@ definitions: The applicable "VimConnectionInfo" structure, which is referenced by vimConnectionId, can be obtained from the "vimConnectionInfo" attribute of the "VnfInstance" structure. structure. (This applies in case of SOL003) See note 1. (This applies in case of SOL002) $ref: "#/definitions/Identifier" resourceProviderId: description: > Loading @@ -325,12 +326,12 @@ definitions: resourceId: description: > Identifier of the resource in the scope of the VIM or the CISM or the resource provider. See note 2. CISM or the resource provider. See note 3. $ref: "#/definitions/IdentifierInVim" vimLevelResourceType: description: > Type of the resource in the scope of the VIM or the CISM or the resource provider. See note 1. or the resource provider. See note 2. type: string vimLevelAdditionalResourceInfo: descriptions: > Loading Loading @@ -629,6 +630,9 @@ definitions: This type represents network address data for a virtual CP. It shall comply with the provisions defined in table 4.4.1.10d-1. This type represents information about a link port of an external VL, i.e. a port providing connectivity for the VNF to an NS VL. It shall comply with the provisions defined in table 5.5.3.6d-1. (This applies in case of SOL002) * NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be used, otherwise it will be ignored by the CISM. Loading @@ -655,7 +659,10 @@ definitions: ExtVirtualLinkData: description: > This type represents an external VL. * NOTE 1: A link port is not needed for an external CP instance that exposes a VIP CP in the following cases: * 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. (This applies in case of SOL002) * NOTE 2: A link port is not needed for an external CP instance that exposes a VIP 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 Loading @@ -667,7 +674,7 @@ definitions: 4 For a VNFC CP exposed as an external CP in a secondary container cluster external network or a secondary container cluster internal network. * NOTE 2: An example of the network attachment definition resource when the container infrastructure service * 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). type: object required: Loading @@ -684,7 +691,7 @@ definitions: description: > Identifier of the VIM connection to manage this resource. This attribute shall only be supported and present if VNF-related resource management in direct mode is applicable. resource management in direct mode is applicable. See note 1. $ref: "#/definitions/Identifier" resourceProviderId: description: > Loading Loading @@ -713,7 +720,7 @@ definitions: external connection points to this external VL. If this attribute is not present, the VNFM shall create the link ports on the external VL except in the cases defined below. See note 1. below. See note 2. type: array items: $ref: "#/definitions/ExtLinkPortData" Loading @@ -721,7 +728,7 @@ definitions: description: > Externally provided network attachment definition resource(s) that provide the specification of the interface to attach external CPs to this external VL. See note 2. to attach external CPs to this external VL. See note 3. It is only applicable if the external VL is realized by a secondary container cluster network. It shall not be present otherwise. Loading