Minor fixes (54be3dd8) · Commits · NFV - Network Functions Virtualisation / SOL002-SOL003

src/SOL002/VNFFaultManagement/definitions/SOL002VNFFaultManagement_def.yaml

+3 −3

Original line number	Diff line number	Diff line
		@@ -28,9 +28,9 @@ definitions:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
		vnfcInstanceIds:
		description: >
		Identifiers of the affected VNFC instances.
		Each identifier references the "id" attribute in a "VnfcInfo" structure.
		Shall be present if the alarm affects at least one VNFC instance.
		Identifiers of the affected VNFC instances. Each identifier references the
		"id" attribute in a "VnfcInfo" structure. Shall be present if the alarm affects
		at least one VNFC instance.
		type: array
		items:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/IdentifierInVnf"

src/SOL002/VNFLifecycleManagement/definitions/SOL002VNFLifecycleManagement_def.yaml

+40 −36

Original line number	Diff line number	Diff line
		@@ -234,28 +234,29 @@ definitions:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs"
		extensions:
		description: >
		Additional VNF specific attributes that affect the lifecycle management of this
		VNF instance by the VNFM, or the lifecycle management scripts.
		These attributes represent values that are stored persistently in the VnfInstance
		structure for consumption by the VNFM, or by the lifecycle management scripts
		during the execution of VNF lifecycle management operations.
		Additional VNF specific attributes that affect the lifecycle management of this VNF instance.
		These attributes represent values that are stored persistently in the VnfInstance structure for
		consumption by the VNFM, or by the lifecycle management scripts during the execution of VNF
		lifecycle management operations.

		All extensions that are allowed for the VNF are declared in the VNFD. The declaration of an
		extension in the VNFD contains information on whether its presence is optional or required,
		and optionally can specify an initial value. See note 2 and note 4. The VNFM shall reject
		requests to write extension attributes that are not declared in the VNFD with a "422 Unprocessable
		entity" error response as defined in clause 6.4 of ETSI GS NFV SOL 013.

		Modifying the values of these attributes has no direct effect on the VNF instance;
		however, the modified attribute values can be considered during subsequent VNF
		lifecycle management operations, which means that the modified values can indirectly
		affect the configuration of the VNF instance.
		Modifying the values of these attributes has no direct effect on the VNF instance; however, the
		modified attribute values can be considered during subsequent VNF lifecycle management operations,
		which means that the modified values can indirectly affect the configuration of the VNF instance.

		All extensions that are allowed for the VNF shall be declared in the VNFD.
		This attribute can be be initialized with default values from VNFD and/or
		with values passed in the InstantiateVnfRequest structure (see clause 5.5.2.4).
		These attributes can be initialized with default values from the VNFD (see note 4).

		A value initialised with default values from the VNFD can be updated with values
		passed in the InstantiateVnfRequest structure.
		These attributes can be modified with values passed in the request structures of certain LCM operations,
		such as the InstantiateVnfRequest structure.

		Further, these attributes can be modified with the PATCH method.
		Further, these attributes can be created, modified or deleted with the PATCH method.

		ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on
		TOSCA specifications.
		In addition, the provisions in clause 5.7 shall apply.
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs"
		_links:
		description: >
		@@ -387,7 +388,7 @@ definitions:
		vnfConfigurableProperties:
		description: >
		If present, this attribute provides modifications to the default values, as obtained from the VNFD, of the
		“vnfConfigurableProperties” attribute in the "VnfInstance", as defined in clause 5.5.2.2.
		"vnfConfigurableProperties" attribute in "VnfInstance", as defined in clause 5.5.2.2.
		Provisions for handling configurable properties during the operation are defined in clause 5.4.4.3.1.
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs"

		@@ -573,7 +574,7 @@ definitions:
		description: >
		Additional input parameters for the instantiation process, specific
		to the VNF being instantiated, as declared in the VNFD as part of
		"ChangeExtVnfConnectivityOpConfig".".
		"ChangeExtVnfConnectivityOpConfig".
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs"

		ChangeCurrentVnfPkgRequest:
		@@ -665,7 +666,7 @@ definitions:
		vnfcInfoModifications:
		description: >
		Modifications of certain entries in the "vnfcInfo" attribute array in the
		"instantiatedVnfInfo" attribute of "VnfInstance"." to be used as "newList" as defined below this table.
		"instantiatedVnfInfo" attribute of "VnfInstance" to be used as "newList" as defined below this table.
		type: array
		items:
		$ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfcInfoModifications"
		@@ -1251,6 +1252,11 @@ definitions:
		description: >
		This type provides information about added, deleted, modified and
		temporary VLs, and added or removed VNF link ports.

		NOTE: When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports,
		the "networkResource" attribute refers to the affected virtual link instance, not the link port
		instance. The resource handles of the affected VNF link ports can be found by dereferencing the
		identifiers in the "vnfLinkPortIds" attribute.
		type: object
		required:
		- id
		@@ -1308,16 +1314,14 @@ definitions:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ResourceHandle"
		vnfLinkPortIds:
		description: >
		Identifiers of the link ports of the affected VL (reference to the vnfLinkPortInfo) related to the change.
		Each identifier references a "VnfLinkPortInfo" structure.
		Identifiers of the link ports of the affected VL related to the change. Each identifier references a
		"VnfLinkPortInfo" structure.

		Shall be set when changeType is equal to "LINK_PORT_ADDED" or "LINK_PORT_REMOVED", and the related
		“VnfLinkPortInfo” structures are present (case "added") or have been present (case "removed") in the
		“VnfVirtualLinkResourceInfo” or "ExtManagedVirtualLinkInfo" structures that are represented by the
		"VnfLinkPortInfo" structures are present (case "added") or have been present (case "removed") in the
		"VnfVirtualLinkResourceInfo" or "ExtManagedVirtualLinkInfo" structures that are represented by the
		"vnfVirtualLinkResourceInfo" or "extManagedVirtualLinkInfo" attribute in the "VnfInstance" structure.
		When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, the
		"networkResource" attribute refers to the affected virtual link instance, not the link port instance.
		The resource handles of the affected VNF link ports can be found by dereferencing the identifiers in the
		"vnfLinkPortIds" attribute.
		See note.
		type: array
		items:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/IdentifierInVnfd"

src/SOL002/VNFPerformanceManagement/VNFPerformanceManagement.yaml

+7 −5

Original line number	Diff line number	Diff line
		@@ -32,7 +32,7 @@ paths:
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/Authorization
		get:
		description: \|
		The client can use this method to retrieve information about PM jobs.
		The API consumer can use this method to retrieve information about PM jobs.
		parameters:
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/Accept
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/ContentType
		@@ -114,7 +114,7 @@ paths:
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/Authorization
		get:
		description: \|
		The client can use this method for reading an individual PM job.
		The API consumer can use this method for reading an individual PM job.
		parameters:
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/Accept
		responses:
		@@ -224,7 +224,7 @@ paths:
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/Authorization
		get:
		description: \|
		The client can use this method for reading an individual performance report.
		The API consumer can use this method for reading an individual performance report.
		parameters:
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/Accept
		responses:
		@@ -261,7 +261,7 @@ paths:
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/Authorization
		get:
		description: \|
		The client can use this method to query information about thresholds.
		The API cosumer can use this method to query information about thresholds.
		parameters:
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/Accept
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/filter
		@@ -296,7 +296,9 @@ paths:

		post:
		description: \|
		The POST method can be used by the client to create a threshold. As the result of successfully executing this method, a new "Individual threshold" resource as defined in clause 6.4.6 shall have been created.
		The POST method can be used by API consumer to create a threshold.
		As the result of successfully executing this method, a new
		"Individual threshold" resource as defined in clause 6.4.6 shall have been created.
		parameters:
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/Accept
		- $ref: ../../components/SOL002SOL003_params.yaml#/components/parameters/ContentType

src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml

+32 −41

Original line number	Diff line number	Diff line
		@@ -2150,6 +2150,15 @@ definitions:
		description: >
		This type provides information about added, deleted, modified and
		temporary VLs, and added or removed VNF link ports.

		NOTE 1: When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports,
		the "networkResource" and "resourceDefinitionId" attributes refer to the affected virtual link
		instance, not the link port instance. The resource handles of the affected VNF link ports can be
		found by dereferencing the identifiers in the "vnfLinkPortIds" attribute.
		NOTE 2: The "resourceDefinitionId" attribute provides information to the API consumer (i.e. the NFVO) to
		assist in correlating the resource changes performed during the LCM operation with the granted
		resources in a specific Grant exchange, which is identified by the "grantId" available in the
		"Individual VNF lifecycle management operation occurrence" and the "id" in the "Individual Grant".
		type: object
		required:
		- id
		@@ -2174,19 +2183,17 @@ definitions:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
		changeType:
		description: >
		Signals the type of change. Permitted values:
		* ADDED
		* REMOVED
		* MODIFIED
		* TEMPORARY
		* LINK_PORT_ADDED
		* LINK_PORT_REMOVED
		For a temporary resource, an AffectedVirtualLink structure exists as
		long as the temporary resource exists.
		When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, the
		"networkResource" attribute refers to the affected virtual link instance, not the link port instance.
		The resource handles of the affected VNF link ports can be found by dereferencing the identifiers in the
		"vnfLinkPortIds" attribute.
		Signals the type of change.

		Permitted values:
		- ADDED
		- REMOVED
		- MODIFIED
		- TEMPORARY
		- LINK_PORT_ADDED
		- LINK_PORT_REMOVED
		For a temporary resource, an AffectedVirtualLink structure exists as long as the temporary resource exists.
		See note 1.
		type: string
		enum:
		- ADDED
		@@ -2197,42 +2204,26 @@ definitions:
		- LINK_PORT_REMOVED
		networkResource:
		description: >
		Reference to the VirtualNetwork resource. Detailed information is
		(for new and modified resources) or has been (for removed
		resources) available from the VIM.
		When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, the
		"networkResource" attribute refers to the affected virtual link instance, not the link port instance.
		The resource handles of the affected VNF link ports can be found by dereferencing the identifiers in
		the "vnfLinkPortIds" attribute.
		Reference to the VirtualNetwork resource.
		Detailed information is (for new and modified resources) or has been (for removed resources) available from the VIM.
		See note 1.
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ResourceHandle"
		vnfLinkPortIds:
		description: >
		Identifiers of the link ports of the affected VL (reference to the vnfLinkPortInfo) related to the change.
		Each identifier references a "VnfLinkPortInfo" structure.
		Shall be set when changeType is equal to "LINK_PORT_ADDED" or "LINK_PORT_REMOVED", and the related
		“VnfLinkPortInfo” structures are present (case "added") or have been present (case "removed") in the
		“VnfVirtualLinkResourceInfo” or "ExtManagedVirtualLinkInfo" structures that are represented by the
		"vnfVirtualLinkResourceInfo" or "extManagedVirtualLinkInfo" attribute in the "VnfInstance" structure.
		When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, the
		"networkResource" attribute refers to the affected virtual link instance, not the link port instance.
		The resource handles of the affected VNF link ports can be found by dereferencing the identifiers in the
		"vnfLinkPortIds" attribute.
		Identifiers of the link ports of the affected VL related to the change. Each identifier references a "VnfLinkPortInfo"
		structure.

		Shall be set when changeType is equal to "LINK_PORT_ADDED" or "LINK_PORT_REMOVED", and the related "VnfLinkPortInfo"
		structures are present (case "added") or have been present (case "removed") in the "VnfVirtualLinkResourceInfo" or
		"ExtManagedVirtualLinkInfo" structures that are represented by the "vnfVirtualLinkResource¬Info" or "extManagedVirtualLinkInfo"
		attribute in the "VnfInstance" structure. See note 1.
		type: array
		items:
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/IdentifierInVnfd"
		resourceDefinitionId:
		description: >
		The identifier of the "ResourceDefinition" in the granting exchange
		related to the LCM operation occurrence. It shall be present when an
		applicable GrantInfo for the granted resource exists.
		When signalling the addition (LINK_PORT_ADDED) or removal (LINK_PORT_REMOVED) of VNF link ports, the
		"networkResource" attribute refers to the affected virtual link instance, not the link port instance.
		The resource handles of the affected VNF link ports can be found by dereferencing the identifiers in the
		"vnfLinkPortIds" attribute.
		The "resourceDefinitionId" attribute provides information to the API consumer (i.e. the NFVO) to assist
		in correlating the resource changes performed during the LCM operation with the granted resources in a
		specific Grant exchange, which is identified by the "grantId" available in the "Individual VNF lifecycle
		management operation occurrence" and the "id" in the "Individual Grant".
		The identifier of the "ResourceDefinition" in the granting exchange related to the LCM operation occurrence.
		It shall be present when an applicable GrantInfo for the granted resource exists. See note 1 and note 2.
		$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/IdentifierLocal"
		zoneId:
		description: >

src/SOL003/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml

+2 −2

Original line number	Diff line number	Diff line
		@@ -120,7 +120,7 @@ paths:

		get:
		description: \|
		The GET method allows the server to test the notification endpoint that is provided by the API consumer,
		The GET method allows the API producer to test the notification endpoint that is provided by the API consumer,
		e.g. during subscription.
		This method shall follow the provisions specified in the tables 5.4.20.3.2-1 and 5.4.20.3.2-2
		for URI query parameters, request and response data structures, and response codes.
		@@ -178,7 +178,7 @@ paths:

		get:
		description: \|
		The GET method allows the server to test the notification endpoint that is provided by the API consumer,
		The GET method allows the API producer to test the notification endpoint that is provided by the API consumer,
		e.g. during subscription.
		This method shall follow the provisions specified in the tables 5.4.20.3.2-1 and 5.4.20.3.2-2
		for URI query parameters, request and response data structures, and response codes.

Admin message