Merge 3.6.1-dev into Release-3 (!257) · Merge requests · NFV - Network Functions Virtualisation / api-tests

SOL002/VNFConfiguration-API/environment/variables.txt

+2 −0

Changes for SOL002/VNFConfiguration-API/environment/variables.txt: 2 added lines, 0 removed lines.
Original line number	Diff line number	Diff line
		@@ -16,3 +16,5 @@ ${CONTENT_TYPE} application/json
		${apiRoot} /
		${apiName} vnfconfig
		${apiMajorVersion} v1

		${etag} enter-etag-value-for-testing-mismatch-condition

SOL002/VNFConfiguration-API/Configuration.robot

+7 −7

Changes for SOL002/VNFConfiguration-API/Configuration.robot: 7 added lines, 7 removed lines.
Original line number	Diff line number	Diff line
		@@ -12,7 +12,7 @@ Set new VNF Configuration
		... Test title: Set a new VNF Configuration
		... Test objective: The objective is to test the creation of a new VNF configuration and perform a JSON schema validation of the returned configuration data structure
		... Pre-conditions: A VNF instance is instantiated
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VE
		... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
		... Post-Conditions: The configuration is successfully set in the VNF and it matches the issued configuration
		@@ -28,7 +28,7 @@ Get information about a VNF configuration
		... Test title: Get information about a VNF configuration
		... Test objective: The objective is to test the retrieval of an existing VNF instance configuration and perform a JSON schema validation of the collected configuration data structure
		... Pre-conditions: A VNF instance is instantiated. The VNF instance is already configured.
		... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VE
		... Applicability: none
		... Post-Conditions: none
		@@ -42,7 +42,7 @@ Get information about a VNF configuration with HTTP Etag
		... Test title: Get information about a VNF configuration with HTTP Etag
		... Test objective: The objective is to test the retrieval of an existing VNF instance configuration, check the generation by the VNF of an HTTP Etag opaque identifier, and perform a JSON schema validation of the collected configuration data structure
		... Pre-conditions: A VNF instance is instantiated. The VNF instance is already configured
		... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VE
		... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
		... Post-Conditions: none
		@@ -57,7 +57,7 @@ Set new VNF Configuration - HTTP Etag precondition unsuccessful
		... Test title: Set a new VNF Configuration - HTTP Etag precondition unsuccessful
		... Test objective: The objective is to test the unsuccess in setting a duplication of VNF configuration identified by an already used HTTP Etag identifier. The test also checks the JSON schema of the unsuccessful operation HTTP response.
		... Pre-conditions: A VNF instance is instantiated. The VNF instance is already configured (Test ID 6.3.1.1.1) with a given HTTP Etag identifier.
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VE
		... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
		... Post-Conditions: The VNF configuration is not modified by the unsuccessful operation and it matches the configuration issued in Test ID 6.3.1.1.1
		@@ -71,7 +71,7 @@ POST VNF Configuration - Method not implemented
		... Test title: POST VNF Configuration - Method not implemented
		... Test objective: The objective is to test that POST method is not allowed to create a new VNF configuration
		... Pre-conditions: none
		... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VE
		... Applicability: none
		... Post-Conditions: none
		@@ -83,7 +83,7 @@ PUT VNF Configuration - Method not implemented
		... Test title: PUT VNF Configuration - Method not implemented
		... Test objective: The objective is to test that PUT method is not allowed to modify an existing VNF configuration
		... Pre-conditions: none
		... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VE
		... Applicability: none
		... Post-Conditions: none
		@@ -95,7 +95,7 @@ DELETE VNF Configuration - Method not implemented
		... Test title: Delete VNF Configuration - Method not implemented
		... Test objective: The objective is to test that DELETE method is not allowed to delete an existing VNF configuration
		... Pre-conditions: none
		... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VE
		... Applicability: none
		... Post-Conditions: none

SOL002/VNFFaultManagement-API/schemas/alarm.schema.json

+27 −18

Changes for SOL002/VNFFaultManagement-API/schemas/alarm.schema.json: 27 added lines, 18 removed lines.
Original line number	Diff line number	Diff line
		{
		"description": "The alarm data type encapsulates information about an alarm.\n",
		"description": "The alarm data type encapsulates information about an alarm. It shall comply with the provisions defined in table 7.5.2.4-1.\nIf the attribute \"faultType\" has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\", the following provisions apply for the values of the attribute \"faultDetails\" related to changes in the state of virtualised resources:\n - One of the entries in the array shall provide information about the anticipated time of maintenance in the\n following format: \"anticipatedTime=$time\", wherein \"$time\" shall be formatted as a \"DateTime\", as specified\n in ETSI GS NFV-SOL 013 [6].\n - One of the entries in the array shall provide identification information about the affinity/anti-affinity group\n defined in the VNFD that is associated to the affected virtualised resource indicated by \"rootCauseFaultyResource\" \n in the following format: \"affinityOrAntiAffinityGroupId=$group\", wherein \"$group\" shall be equal to the \n \"affinityOrAntiAffinityGroupId\" value in the corresponding \"VduProfile\" (for a VNFC/COMPUTE affected resource) \n or \"VirtualLinkProfile\" for a VL/NETWORK affected resource) in the VNFD, which is mapped by the VNFM to the \n virtualised resource group identifier in the virtualised resource change notification received by the VNFM from \n the VIM.\n\nNOTE 1: For an alarm about upcoming impact due to NFVI operation and maintenance (i.e. the attribute \"faultType\" \n has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"rootCauseFaultyResource\" \n indicates a resource to be impacted. Further information on the upcoming impact (e.g. group of impacted \n resources, time of impact) is provided in the attribute \"faultDetails\".\nNOTE 2: When alarms are due to upcoming NFVI operation and maintenance (i.e. the attribute \"faultType\" has the\n value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"faultDetails\" shall include information \n about the anticipated time of the maintenance. See provisions under the present table.\n",
		"type": "object",
		"required": [
		"id",
		"managedObjectId",
		"rootCauseFaultyResource",
		"alarmRaisedTime",
		"ackState",
		"perceivedSeverity",
		@@ -23,6 +22,14 @@
		"description": "An identifier with the intention of being globally unique.\n",
		"type": "string"
		},
		"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.\n",
		"type": "array",
		"items": {
		"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
		"type": "string"
		}
		},
		"rootCauseFaultyResource": {
		"description": "This type represents the faulty virtual resources that have a negative impact on a VNF.\n",
		"type": "object",
		@@ -33,7 +40,6 @@
		"properties": {
		"faultyResource": {
		"required": [
		"vimConnectionId",
		"resourceId"
		],
		"type": "object",
		@@ -52,7 +58,7 @@
		"type": "string"
		},
		"vimLevelResourceType": {
		"description": "Type of the resource in the scope of the VIM or the resource provider.\n",
		"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
		"type": "string"
		}
		}
		@@ -83,6 +89,11 @@
		"type": "string",
		"format": "date-time"
		},
		"alarmAcknowledgedTime": {
		"description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
		"type": "string",
		"format": "date-time"
		},
		"ackState": {
		"description": "Acknowledgement state of the alarm. Permitted values: * UNACKNOWLEDGED * ACKNOWLEDGED.\n",
		"type": "string",
		@@ -92,7 +103,7 @@
		]
		},
		"perceivedSeverity": {
		"description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
		"description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
		"type": "string",
		"enum": [
		"CRITICAL",
		@@ -109,7 +120,7 @@
		"format": "date-time"
		},
		"eventType": {
		"description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment fault (ITU-T Recommendation X.733).\n",
		"description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the\n procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a\n software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a\n condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the\n quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment\n fault (ITU-T Recommendation X.733).\n",
		"type": "string",
		"enum": [
		"COMMUNICATIONS_ALARM",
		@@ -120,15 +131,15 @@
		]
		},
		"faultType": {
		"description": "Additional information to clarify the type of the fault.\n",
		"description": "Additional information to clarify the type of the fault. If the alarm is related to changes in the state of virtualised resources due to NFVI operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE _CHANGE\".\n",
		"type": "string"
		},
		"probableCause": {
		"description": "Information about the probable cause of the fault.\n",
		"description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value “NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE”, the permitted values are: \n - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n hypervisor software updates, etc.\n - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n efficiency or resource usage optimization.\n",
		"type": "string"
		},
		"isRootCause": {
		"description": "Attribute indicating if this fault is the root for other correlated alarms. If TRUE, then the alarms listed in the attribute CorrelatedAlarmId are caused by this fault.\n",
		"description": "The Boolean is a data type having two values (true and false).\n",
		"type": "boolean"
		},
		"correlatedAlarmIds": {
		@@ -140,7 +151,7 @@
		}
		},
		"faultDetails": {
		"description": "Provides additional information about the fault.\n",
		"description": "Provides additional information about the fault. See notes 1 and 2.\n",
		"type": "array",
		"items": {
		"type": "string"
		@@ -154,30 +165,28 @@
		],
		"properties": {
		"self": {
		"description": "This type represents a link to a resource.\n",
		"description": "This type represents a link to a resource using an absolute URI.\n",
		"type": "object",
		"required": [
		"href"
		],
		"properties": {
		"href": {
		"description": "URI of the referenced resource.\n",
		"type": "string",
		"format": "url"
		"description": "String formatted according to IETF RFC 3986.\n",
		"type": "string"
		}
		}
		},
		"objectInstance": {
		"description": "This type represents a link to a resource.\n",
		"description": "This type represents a link to a resource using an absolute URI.\n",
		"type": "object",
		"required": [
		"href"
		],
		"properties": {
		"href": {
		"description": "URI of the referenced resource.\n",
		"type": "string",
		"format": "url"
		"description": "String formatted according to IETF RFC 3986.\n",
		"type": "string"
		}
		}
		}

SOL002/VNFFaultManagement-API/schemas/alarms.schema.json

+27 −17

Changes for SOL002/VNFFaultManagement-API/schemas/alarms.schema.json: 27 added lines, 17 removed lines.
Original line number	Diff line number	Diff line
		@@ -3,12 +3,11 @@
		"items": {
		"type": "object",
		"items": {
		"description": "The alarm data type encapsulates information about an alarm.\n",
		"description": "The alarm data type encapsulates information about an alarm. It shall comply with the provisions defined in table 7.5.2.4-1.\nIf the attribute \"faultType\" has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\", the following provisions apply for the values of the attribute \"faultDetails\" related to changes in the state of virtualised resources:\n - One of the entries in the array shall provide information about the anticipated time of maintenance in the\n following format: \"anticipatedTime=$time\", wherein \"$time\" shall be formatted as a \"DateTime\", as specified\n in ETSI GS NFV-SOL 013 [6].\n - One of the entries in the array shall provide identification information about the affinity/anti-affinity group\n defined in the VNFD that is associated to the affected virtualised resource indicated by \"rootCauseFaultyResource\" \n in the following format: \"affinityOrAntiAffinityGroupId=$group\", wherein \"$group\" shall be equal to the \n \"affinityOrAntiAffinityGroupId\" value in the corresponding \"VduProfile\" (for a VNFC/COMPUTE affected resource) \n or \"VirtualLinkProfile\" for a VL/NETWORK affected resource) in the VNFD, which is mapped by the VNFM to the \n virtualised resource group identifier in the virtualised resource change notification received by the VNFM from \n the VIM.\n\nNOTE 1: For an alarm about upcoming impact due to NFVI operation and maintenance (i.e. the attribute \"faultType\" \n has the value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"rootCauseFaultyResource\" \n indicates a resource to be impacted. Further information on the upcoming impact (e.g. group of impacted \n resources, time of impact) is provided in the attribute \"faultDetails\".\nNOTE 2: When alarms are due to upcoming NFVI operation and maintenance (i.e. the attribute \"faultType\" has the\n value \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE\"), the attribute \"faultDetails\" shall include information \n about the anticipated time of the maintenance. See provisions under the present table.\n",
		"type": "object",
		"required": [
		"id",
		"managedObjectId",
		"rootCauseFaultyResource",
		"alarmRaisedTime",
		"ackState",
		"perceivedSeverity",
		@@ -27,6 +26,14 @@
		"description": "An identifier with the intention of being globally unique.\n",
		"type": "string"
		},
		"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.\n",
		"type": "array",
		"items": {
		"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
		"type": "string"
		}
		},
		"rootCauseFaultyResource": {
		"description": "This type represents the faulty virtual resources that have a negative impact on a VNF.\n",
		"type": "object",
		@@ -37,7 +44,6 @@
		"properties": {
		"faultyResource": {
		"required": [
		"vimConnectionId",
		"resourceId"
		],
		"type": "object",
		@@ -56,7 +62,7 @@
		"type": "string"
		},
		"vimLevelResourceType": {
		"description": "Type of the resource in the scope of the VIM or the resource provider.\n",
		"description": "The value set of the \"vimLevelResourceType\" attribute is within the scope of the VIM or the resource provider and can be used as information that complements the ResourceHandle. This value set is different from the value set of the \"type\" attribute in the ResourceDefinition (refer to clause 9.5.3.2 in SOL003).\n",
		"type": "string"
		}
		}
		@@ -87,6 +93,11 @@
		"type": "string",
		"format": "date-time"
		},
		"alarmAcknowledgedTime": {
		"description": "Date-time stamp. Representation: String formatted according to IETF RFC 3339.\n",
		"type": "string",
		"format": "date-time"
		},
		"ackState": {
		"description": "Acknowledgement state of the alarm. Permitted values: * UNACKNOWLEDGED * ACKNOWLEDGED.\n",
		"type": "string",
		@@ -96,6 +107,7 @@
		]
		},
		"perceivedSeverity": {
		"description": "Indicates the relative level of urgency for operator attention. * CRITICAL: The Critical severity level indicates that a service\n affecting condition has occurred and an immediate corrective action\n is required. Such a severity can be reported, for example, when a\n managed object becomes totally out of service and its capability needs\n to be restored (ITU-T Recommendation X.733).\n* MAJOR: The Major severity level indicates that a service affecting\n condition has developed and an urgent corrective action is required.\n Such a severity can be reported, for example, when there is a severe\n degradation in the capability of the managed object and its full\n capability needs to be restored (ITU-T Recommendation X.733).\n* MINOR: The Minor severity level indicates the existence of a\n non-service affecting fault condition and that corrective action\n should be taken in order to prevent a more serious (for example,\n service affecting) fault. Such a severity can be reported, for\n example, when the detected alarm condition is not currently degrading\n the capacity of the managed object (ITU-T Recommendation X.733).\n* WARNING: The Warning severity level indicates the detection of a\n potential or impending service affecting fault, before any significant\n effects have been felt. Action should be taken to further diagnose (if\n necessary) and correct the problem in order to prevent it from\n becoming a more serious service affecting fault (ITU-T Recommendation\n X.733).\n* INDETERMINATE: The Indeterminate severity level indicates that the\n severity level cannot be determined (ITU-T Recommendation X.733).\n* CLEARED: The Cleared severity level indicates the clearing of one or\n more previously reported alarms. This alarm clears all alarms for this\n managed object that have the same Alarm type, Probable cause and\n Specific problems (if given) (ITU-T Recommendation X.733).\n",
		"type": "string",
		"enum": [
		"CRITICAL",
		@@ -112,7 +124,7 @@
		"format": "date-time"
		},
		"eventType": {
		"description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment fault (ITU-T Recommendation X.733).\n",
		"description": "The enumeration EventType represents those types of events that trigger an alarm. * COMMUNICATIONS_ALARM: An alarm of this type is associated with the\n procedure and/or process required conveying information from one point\n to another (ITU-T Recommendation X.733).\n* PROCESSING_ERROR_ALARM: An alarm of this type is associated with a\n software or processing fault (ITU-T Recommendation X.733).\n* ENVIRONMENTAL_ALARM: An alarm of this type is associated with a\n condition related to an enclosure in which the equipment resides\n (ITU-T Recommendation X.733).\n* QOS_ALARM: An alarm of this type is associated with degradation in the\n quality of a service (ITU-T Recommendation X.733).\n* EQUIPMENT_ALARM: An alarm of this type is associated with an equipment\n fault (ITU-T Recommendation X.733).\n",
		"type": "string",
		"enum": [
		"COMMUNICATIONS_ALARM",
		@@ -123,15 +135,15 @@
		]
		},
		"faultType": {
		"description": "Additional information to clarify the type of the fault.\n",
		"description": "Additional information to clarify the type of the fault. If the alarm is related to changes in the state of virtualised resources due to NFVI operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE _CHANGE\".\n",
		"type": "string"
		},
		"probableCause": {
		"description": "Information about the probable cause of the fault.\n",
		"description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value “NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE”, the permitted values are: \n - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n hypervisor software updates, etc.\n - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n efficiency or resource usage optimization.\n",
		"type": "string"
		},
		"isRootCause": {
		"description": "Attribute indicating if this fault is the root for other correlated alarms. If TRUE, then the alarms listed in the attribute CorrelatedAlarmId are caused by this fault.\n",
		"description": "The Boolean is a data type having two values (true and false).\n",
		"type": "boolean"
		},
		"correlatedAlarmIds": {
		@@ -143,7 +155,7 @@
		}
		},
		"faultDetails": {
		"description": "Provides additional information about the fault.\n",
		"description": "Provides additional information about the fault. See notes 1 and 2.\n",
		"type": "array",
		"items": {
		"type": "string"
		@@ -157,30 +169,28 @@
		],
		"properties": {
		"self": {
		"description": "This type represents a link to a resource.\n",
		"description": "This type represents a link to a resource using an absolute URI.\n",
		"type": "object",
		"required": [
		"href"
		],
		"properties": {
		"href": {
		"description": "URI of the referenced resource.\n",
		"type": "string",
		"format": "url"
		"description": "String formatted according to IETF RFC 3986.\n",
		"type": "string"
		}
		}
		},
		"objectInstance": {
		"description": "This type represents a link to a resource.\n",
		"description": "This type represents a link to a resource using an absolute URI.\n",
		"type": "object",
		"required": [
		"href"
		],
		"properties": {
		"href": {
		"description": "URI of the referenced resource.\n",
		"type": "string",
		"format": "url"
		"description": "String formatted according to IETF RFC 3986.\n",
		"type": "string"
		}
		}
		}

SOL002/VNFFaultManagement-API/Alarms.robot

+19 −19

Changes for SOL002/VNFFaultManagement-API/Alarms.robot: 19 added lines, 19 removed lines.
Original line number	Diff line number	Diff line
		@@ -13,7 +13,7 @@ POST Alarms - Method not implemented
		... Test title: POST Alarms - Method not implemented
		... Test objective: The objective is to test that the method is not implemented
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -25,7 +25,7 @@ GET information about multiple alarms
		... Test title: GET information about multiple alarms
		... Test objective: The objective is to retrieve information about the alarm list
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -38,7 +38,7 @@ GET information about multiple alarms with attribute-based filter
		... Test title: GET information about multiple alarms with attribute-based filter
		... Test objective: The objective is to retrieve information about the alarm list with attribute-based filter
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -51,7 +51,7 @@ GET information about multiple alarms with invalid attribute-based filter
		... Test title: GET information about multiple alarms with invalid attribute-based filter
		... Test objective: The objective is to retrieve information about the alarm list
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -64,7 +64,7 @@ GET information about multiple alarms with "all_fields" attribute selector
		... Test title: GET information about multiple alarms with "all_fields" attribute selector
		... Test objective: The objective is to retrieve information about the alarm list
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -77,7 +77,7 @@ GET information about multiple alarms with exclude_default attribute selector
		... Test title: GET information about multiple alarms with "exclude_default" attribute selector
		... Test objective: The objective is to retrieve information about the alarm list
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -90,7 +90,7 @@ GET information about multiple alarms with fields attribute selector
		... Test title: GET information about multiple alarms with fields attribute selector
		... Test objective: The objective is to retrieve information about the alarm list
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -103,7 +103,7 @@ GET information about multiple alarms with "exclude_fields" attribute selector
		... Test title: GET information about multiple alarms with "exclude_fields" attribute selector
		... Test objective: The objective is to retrieve information about the alarm list
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -116,7 +116,7 @@ PUT Alarms - Method not implemented
		... Test title: PUT Alarms - Method not implemented
		... Test objective: The objective is to test that the method is not implemented
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -128,7 +128,7 @@ PATCH Alarms - Method not implemented
		... Test title: PATCH Alarms - Method not implemented
		... Test objective: The objective is to test that the method is not implemented
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -140,7 +140,7 @@ DELETE Alarms - Method not implemented
		... Test title: DELETE Alarms - Method not implemented
		... Test objective: The objective is to test that the method is not implemented
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -152,7 +152,7 @@ GET information about multiple alarms to get Paged Response
		... Test title: GET information about multiple alarms to get Paged Response
		... Test objective: The objective is to retrieve information about the alarms to get paged response
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -165,7 +165,7 @@ GET information about multiple alarms for Bad Request Response too big
		... Test title: GET information about multiple alarms for Bad Request Response too big
		... Test objective: The objective is to test that GET method fail retrieving status information about Alarms when Response is too big, and perform the JSON schema validation of the failed operation HTTP response
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -178,7 +178,7 @@ GET information about alarms with attribute-based filter "id"
		... Test title: GET information about alarms with attribute-based filter "id"
		... Test objective: The objective is to retrieve information about the alarm list with alarm filter "id"
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -192,7 +192,7 @@ GET information about multiple alarms with attribute-based filter "vnfcInstanceI
		... Test title: GET information about multiple alarms with attribute-based filter "vnfcInstanceIds"
		... Test objective: The objective is to retrieve information about the alarm list with attribute filter "vnfcInstanceIds"
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -206,7 +206,7 @@ GET information about multiple alarms with attribute-based filter "rootCauseFaul
		... Test title: GET information about multiple alarms with attribute-based filter "rootCauseFaultyResource.faultyResourceType"
		... Test objective: The objective is to retrieve information about the alarm list with attribute filter "rootCauseFaultyResource.faultyResourceType"
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -220,7 +220,7 @@ GET information about multiple alarms with attribute-based filter "eventType"
		... Test title: GET information about multiple alarms with attribute-based filter "eventType"
		... Test objective: The objective is to retrieve information about the alarm list with attribute filter "eventType"
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -234,7 +234,7 @@ GET information about multiple alarms with attribute-based filter "perceivedSeve
		... Test title: GET information about multiple alarms with attribute-based filter "perceivedSeverity"
		... Test objective: The objective is to retrieve information about the alarm list with attribute filter "perceivedSeverity"
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -248,7 +248,7 @@ GET information about multiple alarms with attribute-based filter "probableCause
		... Test title: GET information about multiple alarms with attribute-based filter "probableCause"
		... Test objective: The objective is to retrieve information about the alarm list with attribute filter "probableCause"
		... Pre-conditions: none
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.5.1
		... Reference: Clause 7.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v3.6.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none

Merge 3.6.1-dev into Release-3

Merge request reports