SOL005_24, to SOL005_29 and SOL005_115 SOL005_v040009 (caa09b43) · Commits · Miguel Angel Reina Ortega / SOL005

src/SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml

+212 −22

Original line number	Diff line number	Diff line
		@@ -2161,6 +2161,15 @@ definitions:
		description: >
		This type specifies additional parameters on a per-nested NS instance basis.
		It shall comply with the provisions defined in Table 6.5.3.21a-1.

		NOTE 1: This attribute allows for a nested NS at instantiation of
		the composite NS the use of an NSD different from the one specified in the
		NSD of the composite NS with nsProfileId, provided they have the same nsdExtInvariantId.
		NOTE 2: A VnfProfile, NsProfile or PnfProfile may contain multiple VersionDependencies
		as it may describe the version dependencies of the descriptor referenced in the
		profile or of other descriptors with the same external invariant identifier.
		NOTE 3: The overridingVersionDependency attribute may only be present if
		the overrridingNsdId attribute is present.
		type: object
		required:
		- nsProfileId
		@@ -2175,12 +2184,46 @@ definitions:
		type: array
		items:
		$ref: "../../definitions/SOL005_def.yaml#/definitions/KeyValuePairs"
		overridingNsdId:
		description: >
		Reference to an NSD.
		If present it replaces the nsdId indicated in the referenced NsProfile
		at the instantiation of the nested NS. The NSD referenced by this
		ttribute shall have the same nsdExtInvariantId as the one indicated
		in the NsProfile. If the NsProfile does not contain an nsdExtInvariantId
		this attribute shall be ignored.
		See notes 1 and 3.
		$ref: "../../definitions/SOL005_def.yaml#/definitions/Identifier"
		overridingVersionDependency:
		description: >
		If present, information in each overridingVersionDependency replaces
		the versionDependency in the runtime information that the NFVO
		keeps about the VnfProfile, NsProfile or PnfProfile indicated in
		the OverridingVersionDependency.
		Only the versionDependency in the VnfProfile, NsProfile or PnfProfile
		with the same dependentConstituentId as in the overridingVersionDependency
		is replaced. See note 2.
		If no versionDependency with the dependentConstituentId indicated in
		the overridingVersionDependency exists in the VnfProfile, NsProfile
		or PnfProfile, the new versionDependency is added to the runtime information
		that the NFVO keeps about the profile.
		See note 3.
		$ref: "#/definitions/OverridingVersionDependency"

		ParamsForVnf:
		description: >
		This type defines the additional parameters for the VNF instance
		to be created associated with an NS instance.
		It shall comply with the provisions defined in Table 6.5.3.22-1.

		NOTE 1: This attribute allows at VNF instantiation the use of a VNFD different
		from the one specified in the NSD with vnfProfileId provided the two VNFDs refer
		to the same vnfdExtInvariantId.
		NOTE 2: A VnfProfile, NsProfile or PnfProfile may contain multiple VersionDependencies
		as it may describe the version dependencies of the descriptor referenced in the profile
		or of other descriptors with the same external invariant identifier.
		NOTE 3: The overridingVersionDependency attribute may only be present if the overrridingVnfdId
		attribute is present.
		type: object
		required:
		- vnfProfileId
		@@ -2190,6 +2233,34 @@ definitions:
		Identifier of (reference to) a vnfProfile to which the
		additional parameters apply.
		$ref: "#/definitions/IdentifierInNsd"

		overridingNsdId:
		description: >
		Reference to a VNFD.
		If present it replaces the vnfdId indicated in the referenced
		VnfProfile at the VNF instantiation. The VNFD referenced by this
		attribute shall have the same vnfdExtInvariantId as the one indicated
		in the VnfProfile. If the VnfProfile does not contain a
		vnfdExtInvariantId this attribute shall be ignored.
		See notes 1 and 3.
		$ref: "../../definitions/SOL005_def.yaml#/definitions/Identifier"
		overridingVersionDependency:
		description: >
		If present, information in each overridingVersionDependency replaces
		the versionDependency in the runtime information that the NFVO keeps
		about the VnfProfile, NsProfile or PnfProfile indicated in the
		OverridingVersionDependency.
		Only the versionDependency in the VnfProfile, NsProfile or PnfProfile
		with the same dependentConstituentId as in the overridingVersionDependency
		is replaced. See note 2.
		If no versionDependency with the dependentConstituentId indicated in the
		overridingVersionDependency exists in the VnfProfile, NsProfile or PnfProfile,
		the new versionDependency is added to the runtime information that the NFVO
		keeps about the profile.
		See note 3.
		$ref: "#/definitions/OverridingVersionDependency"


		vnfInstanceName:
		description: >
		Human-readable name of the VNF instance to be created.
		@@ -2368,6 +2439,8 @@ definitions:
		or PnfProfile, the new versionDependency is added to the runtime
		information that the NFVO keeps about the Profile.
		See note 4.
		type: array
		items:
		$ref: "#/definitions/OverridingVersionDependency"


		@@ -2429,7 +2502,8 @@ definitions:
		or PnfProfile, the new versionDependency is added to the runtime
		information that the NFVO keeps about the profile.
		See note 4.

		type: array
		items:
		$ref: "#/definitions/OverridingVersionDependency"


		@@ -2812,6 +2886,19 @@ definitions:
		may select a matching vnfProfile based on other information, such as external VL.
		NOTE 3: Either the attribute triple "vnfdId, vnfFlavourId and vnfInstantiationLevelId
		(if provided)" or the attribute "vnProfileId" shall be present, but not both.
		NOTE 4: The target size for VNF instantiation may be specified in either vnfInstantiationLevelId or
		targetScaleLevelInfo, but not both. If none of the two attributes (vnfInstantiationLevelId or
		targetScaleLevelInfo) are present, the default instantiation level as declared in the VNFD shall be used.
		NOTE 5: If targetScaleLevelInfo is specified, information provided in targetScaleLevelInfo shall be used for instantiating
		scalable constituents of the VNF (e.g, VDUs/VLs). For scaling aspects not specified in targetScaleLevelInfo
		or for the VNF constituents (e.g., VDUs/VLs) that are not scalable, the default instantiation level as declared
		in the VNFD shall be used for instantiation.
		NOTE 6: If the overridingVnfdId attribute is present the vnfProfileId attribute shall also be present.
		NOTE 7: This attribute allows at VNF instantiation the use of a VNFD different from the one specified
		in the NSD with vnfProfileId provided the two VNFDs have the same vnfdExtInvariantId.
		NOTE 8: A VnfProfile, NsProfile or PnfProfile may contain multiple VersionDependencies as it may describe the version
		dependencies of the descriptor referenced in the profile or of other descriptors with the same external invariant identifier.
		NOTE 9: The overridingVersionDependency attribute may only be present if the overridingVnfdId attribute is present.
		type: object
		properties:
		vnfdId:
		@@ -2836,11 +2923,20 @@ definitions:

		See note 2 and 3.
		$ref: "../../definitions/SOL005_def.yaml#/definitions/IdentifierInVnfd"
		targetScaleLevelInfo:
		description: >
		This attribute is applicable if VNF supports target scale level instantiation.

		For each scaling aspect of the current deployment flavour, the attribute specifies the scale level of VNF constituents (e.g., VDU level) to be instantiated.
		See notes 4 and 5.
		type: array
		items:
		$ref: "#/definitions/VnfScaleInfo"
		vnfProfileId:
		description: >
		Identifier of (Reference to) a vnfProfile defined in the NSD which is used for instantiating the VNF.

		See note 3.
		See notes 3 and 6.
		$ref: "#/definitions/IdentifierInNsd"
		vnfInstanceName:
		description: >
		@@ -2882,7 +2978,10 @@ definitions:
		additionalParams:
		description: >
		Additional input parameters for the instantiation process,
		specific to the VNF being instantiated.
		specific to the VNF being instantiated, as declared in the
		VNFD as part of "InstantiateVnfOpConfig" defined in ETSI
		GS NFV-IFA 011.

		$ref: "../../definitions/SOL005_def.yaml#/definitions/KeyValuePairs"
		metadata:
		description: >
		@@ -2910,6 +3009,42 @@ definitions:
		in a specific geographic location.
		$ref: "#/definitions/VnfLocationConstraint"

		overridingVnfdId:
		description: >
		Reference to a VNFD.
		If present the vnfProfileId shall also be present.
		It replaces the vnfdId indicated in the vnfProfileId.
		The VNFD referenced by this attribute shall have the same
		vnfdExtInvariantId as the one indicated in the VnfProfile.
		If the VnfProfile does not contain a vnfdExtInvariantId this
		attribute shall be ignored.
		See notes 6, 7 and 9.
		$ref: "../../definitions/SOL005_def.yaml#/definitions/Identifier"
		overridingVersionDependency:
		description: >
		If present, information in each overridingVersionDependency
		replaces the versionDependency in the runtime information that
		the NFVO keeps about the VnfProfile, NsProfile or PnfProfile
		indicated in the OverridingVersionDependency.

		Only the versionDependency in the VnfProfile, NsProfile or
		PnfProfile with the same dependentConstituentId as in the
		overridingVersionDependency is replaced. See note 8.

		If no versionDependency with the dependentConstituentId indicated
		in the overridingVersionDependency exists in the VnfProfile, NsProfile
		or PnfProfile, the new version Dependency is added to the runtime
		information that the NFVO keeps about the profile.
		See note 9.

		type: array
		items:
		$ref: "#/definitions/OverridingVersionDependency"





		ChangeVnfFlavourData:
		description: >
		The type represents the information that is requested to be changed
		@@ -2925,6 +3060,16 @@ definitions:
		of ExtManagedVirtualLinkData corresponding to the same VNF internal VL shall
		indicate so by referencing to the same VnfVirtualLinkDesc and externally-managed
		multi-site VL instance (refer to clause 6.5.3.27).
		NOTE 3: The target size for VNF instantiation may be specified in either
		instantiationLevelId or targetScaleLevelInfo, but not both. If none of the
		two attributes (instantiationLevelId or targetScaleLevelInfo) are present,
		the default instantiation level as declared in the VNFD shall be used.
		NOTE 4: If targetScaleLevelInfo is specified, information provided in
		targetScaleLevelInfo shall be used for instantiating scalable constituents
		of the VNF (e.g, VDUs/VLs). For scaling aspects not specified in
		targetScaleLevelInfo or for the VNF constituents (e.g., VDUs/VLs) that
		are not scalable, the default instantiation level as declared in the VNFD
		shall be used for instantiation.
		type: object
		required:
		- vnfInstanceId
		@@ -2941,10 +3086,18 @@ definitions:
		instantiationLevelId:
		description: >
		Identifier of the instantiation level of the deployment
		flavor to be instantiated. If not present, the default
		instantiation level as declared in the VNFD is
		instantiated.
		$ref: "../../definitions/SOL005_def.yaml#/definitions/IdentifierInVnfd"
		flavour to be instantiated.
		See note 3.

		targetScaleLevelInfo:
		description: >
		This attribute is applicable if VNF supports target scale level instantiation.
		For each scaling aspect of the current deployment flavour, the attribute
		specifies the scale level of VNF constituents (e.g., VDU level) to be instantiated.
		See notes 3 and 4.
		type: array
		items:
		$ref: "#/definitions/VnfScaleInfo"
		extVirtualLinks:
		description: >
		Information about external VLs to connect the VNF to.
		@@ -5184,7 +5337,7 @@ definitions:
		description: >
		This type represents an external VL.

		NOTE: A link port is not needed for an external CP instance that exposes a VIP CP in the following cases:
		NOTE 1: 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 extCP:
		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,
		@@ -5192,7 +5345,8 @@ definitions:
		2. For a VIP CP exposed as extCP 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.

		NOTE 2: An example of the network attachment definition resource when the container infrastructure service
		is a Kubernetes® instance is a network attachment definition (NAD).
		type: object
		required:
		- resourceId
		@@ -5234,10 +5388,46 @@ definitions:
		external connection points to this external VL unless
		the extCp exposes a VIP CP and a link port is not needed
		for it based on the conditions defined below.
		See note.
		See note 1.
		type: array
		items:
		$ref: "#/definitions/ExtLinkPortData"
		extNetAttDefResourceData:
		description: >
		Externally provided network attachment definition resource(s) that
		provides the specification of the interface to attach external CPs to
		this external VL. See note 2.

		It is only applicable if the external VL is realized by a secondary
		container cluster network. It shall not be present otherwise.
		type: array
		items:
		$ref: "#/definitions/NetAttDefResourceData"


		NetAttDefResourceData:
		description: >
		This type represents the information related to a network attachment definition
		resource that provides the specification of the interface to be used to connect
		one or multiple connection points to a secondary container cluster network
		realizing a VL.
		type: object
		required:
		- netAttDefResourceId
		- resourceHandle
		properties:
		netAttDefResourceId:
		description: >
		Identifier of this network attachment definition resource as provided by the entity that has created it.
		$ref: "../../definitions/SOL005_def.yaml#/definitions/Identifier"
		resourceHandle:
		description: >
		Resource handle of the resource identifying the network attachment definition resource that provides
		the specification of the interface to attach the connection points to a secondary container cluster network.
		$ref: "../../definitions/SOL005_def.yaml#/definitions/ResourceHandle"




		ExtManagedVirtualLinkData:
		description: >