WARNING! Gitlab maintenance operation scheduled for Monday, 20 April between 12:00 and 14:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.

Commit a9278c20 authored Jan 08, 2019 by Elian Kraja

Fixing typos

parent d693824f

SOL003/VNFLifecycleManagement-API/CancelOperationTask.robot

+4 −4

Original line number	Original line	Diff line number	Diff line
	@@ -6,7 +6,7 @@ Library DependencyLibrary
	Library JSONLibrary		Library JSONLibrary
	Library JSONSchemaLibrary schemas/		Library JSONSchemaLibrary schemas/
	Documentation This task resource represents the "Cancel operation" operation. The client can use this resource to cancel an ongoing VNF lifecycle operation.		Documentation This task resource represents the "Cancel operation" operation. The client can use this resource to cancel an ongoing VNF lifecycle operation.
	Suite setup Check resource existance		Suite Setup Check resource existance

	* Test Cases *		* Test Cases *
	Post Cancel operation task		Post Cancel operation task
	@@ -28,7 +28,7 @@ Post Fail operation task Conflict (Not-FAILED_TEMP)
	... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.		... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
	... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state,		... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state,
	... or another error handling action is starting, such as retry or rollback.		... or another error handling action is starting, such as retry or rollback.
	... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.		... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error.
	Depends on test failure Check resource FAILED_TEMP		Depends on test failure Check resource FAILED_TEMP
	Log Final Fail an operation		Log Final Fail an operation
	Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
	@@ -46,7 +46,7 @@ Post Fail operation task Conflict (parallel LCM operation)
	... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.		... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
	... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state,		... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state,
	... or another error handling action is starting, such as retry or rollback.		... or another error handling action is starting, such as retry or rollback.
	... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.		... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error.
	[Setup] Launch another error handling action		[Setup] Launch another error handling action
	log Final Fail an operation		log Final Fail an operation
	Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
	@@ -66,7 +66,7 @@ Post Fail operation task Not Found
	... Specifically in case of this task resource, the response code 404 shall also be returned		... Specifically in case of this task resource, the response code 404 shall also be returned
	... if the task is not supported for the VNF LCM operation occurrence represented by the parent resource,		... if the task is not supported for the VNF LCM operation occurrence represented by the parent resource,
	... which means that the task resource consequently does not exist.		... which means that the task resource consequently does not exist.
	... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error.		... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error.
	[Setup] Check Fail not supported		[Setup] Check Fail not supported
	log Final fail an operation		log Final fail an operation
	Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}

SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot

+2 −2

Original line number	Original line	Diff line number	Diff line
	@@ -5,7 +5,7 @@ Library REST ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT}
	Library OperatingSystem		Library OperatingSystem
	Library JSONLibrary		Library JSONLibrary
	Library JSONSchemaLibrary schemas/		Library JSONSchemaLibrary schemas/
	Suite setup Check resource existance		Suite Setup Check resource existance

	* Test Cases *		* Test Cases *
	Change external VNF connectivity		Change external VNF connectivity
	@@ -27,7 +27,7 @@ Change external VNF connectivity Conflict (parallel LCM operation)
	[Documentation] Conflict		[Documentation] Conflict
	... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.		... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
	... Typically, this is due to the fact that another LCM operation is ongoing.		... Typically, this is due to the fact that another LCM operation is ongoing.
	... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.		... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error.
	[Setup] Launch another LCM operation		[Setup] Launch another LCM operation
	log Trying to change the deployment flavour of a VNF instance.		log Trying to change the deployment flavour of a VNF instance.
	Set Headers {"Accept":"${ACCEPT}"}		Set Headers {"Accept":"${ACCEPT}"}

SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot

+4 −4

Original line number	Original line	Diff line number	Diff line
	@@ -5,7 +5,7 @@ Library REST ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT}
	Library OperatingSystem		Library OperatingSystem
	Library JSONLibrary		Library JSONLibrary
	Library JSONSchemaLibrary schemas/		Library JSONSchemaLibrary schemas/
	Suite setup Check resource existance		Suite Setup Check resource existance

	* Test Cases *		* Test Cases *
	Change deployment flavour of a vnfInstance		Change deployment flavour of a vnfInstance
	@@ -28,7 +28,7 @@ Change deployment flavour of a vnfInstance Conflict (Not-Instantiated)
	... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.		... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
	... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state,		... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state,
	... or that another lifecycle management operation is ongoing.		... or that another lifecycle management operation is ongoing.
	... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.		... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error.
	[Setup] Check resource not instantiated		[Setup] Check resource not instantiated
	Log Trying to change the deployment flavour of a VNF instance.		Log Trying to change the deployment flavour of a VNF instance.
	Set Headers {"Accept":"${ACCEPT}"}		Set Headers {"Accept":"${ACCEPT}"}
	@@ -49,7 +49,7 @@ Change deployment flavour of a vnfInstance Conflict (parallel LCM operation)
	... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.		... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
	... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state,		... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state,
	... or that another lifecycle management operation is ongoing.		... or that another lifecycle management operation is ongoing.
	... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.		... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error.
	[Setup] Launch another LCM operation		[Setup] Launch another LCM operation
	log Trying to change the deployment flavour of a VNF instance.		log Trying to change the deployment flavour of a VNF instance.
	Set Headers {"Accept":"${ACCEPT}"}		Set Headers {"Accept":"${ACCEPT}"}
	@@ -70,7 +70,7 @@ Change deployment flavour of a vnfInstance Not Found
	[Documentation] Not Found		[Documentation] Not Found
	... Error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists.		... Error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists.
	... Specifically in case of this task resource, the response code 404 shall also returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist.		... Specifically in case of this task resource, the response code 404 shall also returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist.
	... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error.		... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error.
	[Setup] Check change flavour not supported		[Setup] Check change flavour not supported
	Log Trying to change the deployment flavour of a VNF instance, not exist		Log Trying to change the deployment flavour of a VNF instance, not exist
	Set Headers {"Accept":"${ACCEPT}"}		Set Headers {"Accept":"${ACCEPT}"}

SOL003/VNFLifecycleManagement-API/FailOperationTask.robot

+4 −4

Original line number	Original line	Diff line number	Diff line
	@@ -9,7 +9,7 @@ Documentation This task resource represents the "Fail operation" operation.
	... The client can use this resource to mark a VNF lifecycle management operation occurrence as "finally failed",		... The client can use this resource to mark a VNF lifecycle management operation occurrence as "finally failed",
	... i.e. change the state of the related VNF LCM operation occurrence resource to "FAILED", if it is not assumed that a subsequent retry or rollback will succeed.		... i.e. change the state of the related VNF LCM operation occurrence resource to "FAILED", if it is not assumed that a subsequent retry or rollback will succeed.
	... Once the operation is marked as "finally failed", it cannot be retried or rolled back anymore.		... Once the operation is marked as "finally failed", it cannot be retried or rolled back anymore.
	Suite setup Check resource existance		Suite Setup Check resource existance

	* Test Cases *		* Test Cases *
	Post Fail operation task		Post Fail operation task
	@@ -31,7 +31,7 @@ Post Fail operation task Conflict (Not-FAILED_TEMP)
	... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.		... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
	... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state,		... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state,
	... or another error handling action is starting, such as retry or rollback.		... or another error handling action is starting, such as retry or rollback.
	... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.		... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error.
	Depends on test failure Check resource FAILED_TEMP		Depends on test failure Check resource FAILED_TEMP
	Log Final Fail an operation		Log Final Fail an operation
	Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
	@@ -49,7 +49,7 @@ Post Fail operation task Conflict (parallel LCM operation)
	... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.		... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
	... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state,		... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state,
	... or another error handling action is starting, such as retry or rollback.		... or another error handling action is starting, such as retry or rollback.
	... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.		... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error.
	[Setup] Launch another error handling action		[Setup] Launch another error handling action
	log Final Fail an operation		log Final Fail an operation
	Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
	@@ -69,7 +69,7 @@ Post Fail operation task Not Found
	... Specifically in case of this task resource, the response code 404 shall also be returned		... Specifically in case of this task resource, the response code 404 shall also be returned
	... if the task is not supported for the VNF LCM operation occurrence represented by the parent resource,		... if the task is not supported for the VNF LCM operation occurrence represented by the parent resource,
	... which means that the task resource consequently does not exist.		... which means that the task resource consequently does not exist.
	... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error.		... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error.
	[Setup] Check Fail not supported		[Setup] Check Fail not supported
	log Final fail an operation		log Final fail an operation
	Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}

SOL003/VNFLifecycleManagement-API/HealVNFTask.robot

+4 −4

Original line number	Original line	Diff line number	Diff line
	@@ -5,7 +5,7 @@ Library REST ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT}
	Library OperatingSystem		Library OperatingSystem
	Library JSONLibrary		Library JSONLibrary
	Library JSONSchemaLibrary schemas/		Library JSONSchemaLibrary schemas/
	Suite setup Check resource existance		Suite Setup Check resource existance

	* Test Cases *		* Test Cases *
	Heal a vnfInstance		Heal a vnfInstance
	@@ -28,7 +28,7 @@ Heal a vnfInstance Conflict (Not-Instantiated)
	... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.		... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
	... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state,		... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state,
	... or that another lifecycle management operation is ongoing.		... or that another lifecycle management operation is ongoing.
	... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.		... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error.
	[Setup] Check resource not instantiated		[Setup] Check resource not instantiated
	Log Trying to heal a VNF instance.		Log Trying to heal a VNF instance.
	Set Headers {"Accept":"${ACCEPT}"}		Set Headers {"Accept":"${ACCEPT}"}
	@@ -49,7 +49,7 @@ Heal a vnfInstance Conflict (parallel LCM operation)
	... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.		... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource.
	... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state,		... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state,
	... or that another lifecycle management operation is ongoing.		... or that another lifecycle management operation is ongoing.
	... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.		... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error.
	[Setup] Launch another LCM operation		[Setup] Launch another LCM operation
	log Trying to heal a VNF instance.		log Trying to heal a VNF instance.
	Set Headers {"Accept":"${ACCEPT}"}		Set Headers {"Accept":"${ACCEPT}"}
	@@ -70,7 +70,7 @@ Heal a vnfInstance Not Found
	[Documentation] Not Found		[Documentation] Not Found
	... Error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists.		... Error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists.
	... Specifically in case of this task resource, the response code 404 shall also returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist.		... Specifically in case of this task resource, the response code 404 shall also returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist.
	... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error.		... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error.
	[Setup] Check heal not supported		[Setup] Check heal not supported
	Log Trying to heal a VNF instance, not exist		Log Trying to heal a VNF instance, not exist
	Set Headers {"Accept":"${ACCEPT}"}		Set Headers {"Accept":"${ACCEPT}"}