Skip to content
Snippets Groups Projects
Commit 5bd9a483 authored by mengxuan.zhao's avatar mengxuan.zhao
Browse files

SOL002 VNF Configuration API completed

parent 2bc82978
No related branches found
No related tags found
No related merge requests found
Expand all Hide whitespace changes
Inline Side-by-side
Showing
with 4132 additions and 6 deletions
SOL002/VNFConfiguration-API_egm/Configuration.robot 0 → 100644
+ 91
− 0
View file @ 5bd9a483
*** Settings ***
Resource variables.txt
Library REST ${VNF_SCHEMA}://${VNF_HOST}:${VNF_PORT}
... spec=SOL002-VNFConfiguration-API.yaml
Library JSONLibrary
Library JSONSchemaLibrary schemas/
Library OperatingSystem
Library DependencyLibrary
*** Variables ***
${Etag}= an etag
${Etag_modified}= a modified etag
*** Test cases ***
POST Configuration - Method not implemented
log Trying to perform a POST. This method should not be implemented
Set Headers {"Accept":"${ACCEPT}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
Post ${apiRoot}/${apiName}/${apiVersion}/configuration
Log Validate Status code
Integer response status 405
Get information about a configuration
Log Query VNF The GET method queries information about a configuration.
Set Headers {"Accept":"${ACCEPT}"}
Set Headers {"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
Log Execute Query and validate response
Get ${apiRoot}/${apiName}/${apiVersion}/configuration
${Etag}= Output response headers Etag
Log Validate Status code
Integer response status 200
${contentType}= Output response headers Content-Type
Should Contain ${contentType} ${CONTENT_TYPE}
${result}= Output response body
${json}= evaluate json.loads('''${result}''') json
Validate Json vnfConfiguration.schema.json ${json}
Log Validation OK
PUT Config - Method not implemented
log Trying to perform a PUT. This method should not be implemented
Set Headers {"Accept":"${ACCEPT}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
Put ${apiRoot}/${apiName}/${apiVersion}/configuration
Log Validate Status code
Integer response status 405
PATCH Config
log Trying to perform a PATCH. This method modifies the configuration
Set Headers {"Accept":"${ACCEPT}"}
Set Headers {"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
${body}= Get File json/vnfConfigModifications.json
Patch ${apiRoot}/${apiName}/${apiVersion}/configuration ${body}
Log Validate Status code
${Etag_modified}= Output response headers Etag
Integer response status 200
${contentType}= Output response headers Content-Type
Should Contain ${contentType} ${CONTENT_TYPE}
${result}= Output response body
${json}= evaluate json.loads('''${result}''') json
Validate Json vnfConfigModifications.schema.json ${json}
Log Validation OK
PATCH Config - Precondition failed
[Documentation] Precondition Failed
... Precondition Failed A precondition given in an HTTP request header is not fulfilled.
... Typically, this is due to an ETag mismatch, indicating that the resource was modified by another entity.
... The response body should contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.
Depends On Test PATCH Alarm # If the previous test scceeded, it means that Etag has been modified
log Trying to perform a PATCH. This method modifies an individual alarm resource
Set Headers {"Accept":"${ACCEPT}"}
Set Headers {"Content-Type": "${CONTENT_TYPE}"}
Set Headers {"If-Match": "${Etag}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
${body}= Get File json/vnfConfigModifications.json
Patch ${apiRoot}/${apiName}/${apiVersion}/configuration ${body}
Log Validate Status code
Integer response status 412
${problemDetails}= Output response body
${json}= evaluate json.loads('''${problemDetails}''') json
Validate Json ProblemDetails.schema.json ${json}
Log Validation OK
DELETE Config - Method not implemented
log Trying to perform a DELETE. This method should not be implemented
Set Headers {"Accept":"${ACCEPT}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
Delete ${apiRoot}/${apiName}/${apiVersion}/configuration
Log Validate Status code
Integer response status 405
\ No newline at end of file
SOL002/VNFConfiguration-API_egm/SOL002-VNFConfiguration-API.json 0 → 100644
+ 1398
− 0
View file @ 5bd9a483
This diff is collapsed.
SOL002/VNFConfiguration-API_egm/SOL002-VNFConfiguration-API.yaml 0 → 100644
+ 2202
− 0
View file @ 5bd9a483
This diff is collapsed.
SOL002/VNFConfiguration-API_egm/jsons/vnfConfigModifications.json 0 → 100644
+ 43
− 0
View file @ 5bd9a483
{
"vnfConfigurationData": {
"extCpConfig": {
"cpId": "string",
"cpdId": "string",
"addresses": [
{
"address": {
"macAddress": "string",
"ipAddress": "string"
},
"useDynamicAddress": true,
"port": 0
}
]
},
"dhcpServer": "string",
"vnfSpecificData": {}
},
"vnfcConfigurationData": [
{
"vnfcInstanceId": "string",
"intCpConfig": [
{
"cpId": "string",
"cpdId": "string",
"addresses": [
{
"address": {
"macAddress": "string",
"ipAddress": "string"
},
"useDynamicAddress": true,
"port": 0
}
]
}
],
"dhcpServer": "string",
"vnfcSpecificData": {}
}
]
}
\ No newline at end of file
SOL002/VNFConfiguration-API_egm/schemas/problemDetails.schema.json 0 → 100644
+ 34
− 0
View file @ 5bd9a483
{
"definitions": {},
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
"properties": {
"type": {
"type": "string",
"description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
"format": "URI"
},
"title": {
"type": "string",
"description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
},
"status": {
"type": "integer",
"description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
},
"detail": {
"type": "string",
"description": "A human-readable explanation specific to this occurrence of the problem.\n"
},
"instance": {
"type": "string",
"description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
"format": "URI"
}
},
"required": [
"status",
"detail"
]
}
\ No newline at end of file
SOL002/VNFConfiguration-API_egm/schemas/vnfConfigModifications.schema.json 0 → 100644
+ 157
− 0
View file @ 5bd9a483
{
"description": "This type represents request parameters for the \"Set Configuration\" operation. * NOTE 1: At least one of \"vnfConfigurationData\" and \"vnfcConfigurationData\"\n shall be present.\n * NOTE 2: The VnfcConfiguration data type can only be used to modify the configuration\n of existing VNFC instances.\n",
"type": "object",
"properties": {
"vnfConfigurationData": {
"description": "This type represents configuration parameters of a VNF instance.\n",
"type": "object",
"properties": {
"extCpConfig": {
"description": "This type represents configuration parameters of a CP instance.\n",
"type": "object",
"required": [
"cpId",
"cpdId",
"addresses"
],
"properties": {
"cpId": {
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
},
"cpdId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
"type": "string"
},
"addresses": {
"description": "Network address and port assigned to the CP.\n",
"type": "array",
"items": {
"description": "This type represents configuration parameters of a CP instance address. * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
"type": "object",
"properties": {
"address": {
"description": "Network address that has been configured on the CP. See NOTE 1.\n",
"type": "object",
"properties": {
"macAddress": {
"description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
"type": "string",
"format": "MAC"
},
"ipAddress": {
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
}
}
},
"useDynamicAddress": {
"description": "Set to true if an address shall be assigned dynamically. Otherwise set to false. The default value shall be false. See NOTE 1.\n",
"type": "boolean"
},
"port": {
"description": "The port assigned to the CP instance (e.g. IP port number, Ethernet port number, etc.).\n",
"type": "integer"
}
}
}
}
}
},
"dhcpServer": {
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
},
"vnfSpecificData": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
"type": "object"
}
}
},
"vnfcConfigurationData": {
"description": "Modifications to configuration data for certain VNFC instances. See NOTE 1 and NOTE 2. If present, the modifications of the \"vnfcConfigurationData\" attribute shall follow these provisions: Modifying an attribute that is an array of objects of type \"VnfcConfigurationData\".\n Assumptions:\n 1) \"oldList\" is the \"VnfcConfigurationData\" array to be modified and \"newList\"\n is the \"VnfcConfigurationData\" array that contains the changes.\n 2) \"oldEntry\" is an entry in \"oldList\" and \"newEntry\" is an entry in \"newList\".\n 3) A \"newEntry\" has a \"corresponding entry\" if there exists an \"oldEntry\" that \n has the same content of the \"vnfcInstanceId\" attribute as the \"newEntry\"; \n a \"newEntry\" has no corresponding entry if no such \"oldEntry\" exists.\n 4) In any array of \"VnfcConfigurationData\" structures, the content of \"vnfcInstanceId\"\n is unique (i.e. there shall be no two entries with the same content of \"vnfcInstanceId\").\n Provisions:\n 1) For each \"newEntry\" in \"newList\" that has no corresponding entry in \"oldList\", \n the \"oldList\" array shall be modified by adding that \"newEntry\".\n\n 2) For each \"newEntry\" in \"newList\" that has a corresponding \"oldEntry\" in \"oldList\",\n the value of \"oldEntry\" shall be updated with the value of \"newEntry\" according to\n the rules of JSON Merge PATCH (see IETF RFC 7396 ).\n",
"type": "array",
"items": {
"description": "This type represents configuration parameters of a VNFC instance.\n",
"type": "object",
"required": [
"vnfcInstanceId"
],
"properties": {
"vnfcInstanceId": {
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
},
"intCpConfig": {
"description": "Configuration parameters for the internal CPs of the VNFC instance.\n",
"type": "array",
"items": {
"description": "This type represents configuration parameters of a CP instance.\n",
"type": "object",
"required": [
"cpId",
"cpdId",
"addresses"
],
"properties": {
"cpId": {
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
},
"cpdId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
"type": "string"
},
"addresses": {
"description": "Network address and port assigned to the CP.\n",
"type": "array",
"items": {
"description": "This type represents configuration parameters of a CP instance address. * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
"type": "object",
"properties": {
"address": {
"description": "Network address that has been configured on the CP. See NOTE 1.\n",
"type": "object",
"properties": {
"macAddress": {
"description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
"type": "string",
"format": "MAC"
},
"ipAddress": {
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
}
}
},
"useDynamicAddress": {
"description": "Set to true if an address shall be assigned dynamically. Otherwise set to false. The default value shall be false. See NOTE 1.\n",
"type": "boolean"
},
"port": {
"description": "The port assigned to the CP instance (e.g. IP port number, Ethernet port number, etc.).\n",
"type": "integer"
}
}
}
}
}
}
},
"dhcpServer": {
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
},
"vnfcSpecificData": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
"type": "object"
}
}
}
}
}
}
\ No newline at end of file
SOL002/VNFConfiguration-API_egm/schemas/vnfConfiguration.schema.json 0 → 100644
+ 160
− 0
View file @ 5bd9a483
{
"description": "This type represents configuration parameters of a VNF instance and its VNFC instances.\n",
"type": "object",
"required": [
"vnfConfigurationData"
],
"properties": {
"vnfConfigurationData": {
"description": "This type represents configuration parameters of a VNF instance.\n",
"type": "object",
"properties": {
"extCpConfig": {
"description": "This type represents configuration parameters of a CP instance.\n",
"type": "object",
"required": [
"cpId",
"cpdId",
"addresses"
],
"properties": {
"cpId": {
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
},
"cpdId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
"type": "string"
},
"addresses": {
"description": "Network address and port assigned to the CP.\n",
"type": "array",
"items": {
"description": "This type represents configuration parameters of a CP instance address. * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
"type": "object",
"properties": {
"address": {
"description": "Network address that has been configured on the CP. See NOTE 1.\n",
"type": "object",
"properties": {
"macAddress": {
"description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
"type": "string",
"format": "MAC"
},
"ipAddress": {
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
}
}
},
"useDynamicAddress": {
"description": "Set to true if an address shall be assigned dynamically. Otherwise set to false. The default value shall be false. See NOTE 1.\n",
"type": "boolean"
},
"port": {
"description": "The port assigned to the CP instance (e.g. IP port number, Ethernet port number, etc.).\n",
"type": "integer"
}
}
}
}
}
},
"dhcpServer": {
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
},
"vnfSpecificData": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
"type": "object"
}
}
},
"vnfcConfigurationData": {
"description": "Configuration parameters of the VNFC instances.\n",
"type": "array",
"items": {
"description": "This type represents configuration parameters of a VNFC instance.\n",
"type": "object",
"required": [
"vnfcInstanceId"
],
"properties": {
"vnfcInstanceId": {
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
},
"intCpConfig": {
"description": "Configuration parameters for the internal CPs of the VNFC instance.\n",
"type": "array",
"items": {
"description": "This type represents configuration parameters of a CP instance.\n",
"type": "object",
"required": [
"cpId",
"cpdId",
"addresses"
],
"properties": {
"cpId": {
"description": "An identifier that is unique for the respective type within a VNF instance, but may not be globally unique.\n",
"type": "string"
},
"cpdId": {
"description": "An identifier that is unique within a VNF descriptor.\n",
"type": "string"
},
"addresses": {
"description": "Network address and port assigned to the CP.\n",
"type": "array",
"items": {
"description": "This type represents configuration parameters of a CP instance address. * NOTE 1: Either \"address\" or \"useDynamicAddress\" shall be present.\n * NOTE 2: At least one of \"macAddress\" and \"ipAddress\" shall be present.\n",
"type": "object",
"properties": {
"address": {
"description": "Network address that has been configured on the CP. See NOTE 1.\n",
"type": "object",
"properties": {
"macAddress": {
"description": "A MAC address. Representation: string that consists of groups of two hexadecimal digits, separated by hyphens or colons.\n",
"type": "string",
"format": "MAC"
},
"ipAddress": {
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
}
}
},
"useDynamicAddress": {
"description": "Set to true if an address shall be assigned dynamically. Otherwise set to false. The default value shall be false. See NOTE 1.\n",
"type": "boolean"
},
"port": {
"description": "The port assigned to the CP instance (e.g. IP port number, Ethernet port number, etc.).\n",
"type": "integer"
}
}
}
}
}
}
},
"dhcpServer": {
"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
"type": "string",
"format": "IP"
},
"vnfcSpecificData": {
"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key- value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 7159.\n",
"type": "object"
}
}
}
}
}
}
\ No newline at end of file
SOL002/VNFConfiguration-API_egm/variables.txt 0 → 100644
+ 42
− 0
View file @ 5bd9a483
*** Variables ***
${VNFM_HOST} localhost # Hostname of the VNFM
${VNFM_PORT} 8080 # Listening port of the VNFM
${VNF_HOST} localhost # Hostname of the NFVO
${VNF_PORT} 8081 # Listening port of the NFVO
${VNFM_SCHEMA} https
${VNF_SCHEMA} https
${AUTHORIZATION} Bearer QWxhZGRpbjpvcGVuIHNlc2FtZQ==
${CONTENT_TYPE} application/json
${CONTENT_TYPE_PATCH} application/merge-patch+json
${ACCEPT} application/json
${apiRoot} /
${apiName} vnfconfig
${apiVersion} v1
${AUTH_USAGE} 1
${WRONG_AUTHORIZATION} Bearer XXXXXWRONGXXXXX
${alarm_filter} managedObjectId
${managedObjectId} 007c111c-38a1-42c0-a666-7475ecb1567c
${invalid_alarm_filter} badFilter
${alarmId} 6fc3539c-e602-4afa-8e13-962fb5a7d81d
${vnfInstanceDescription} description vnf
${vnfInstanceDescription_Update} Updated description vnf
${SINGLE_FILE_VNFD} 1 # If VNFD is PLAIN TEXT
${ACCEPT_PLAIN} text/plain
${ACCEPT_ZIP} application/zip
${vnfPkgId_processing} 007c111c-38a1-42c0-a666-7475ecb1567c
${ARTIFACT_TYPE} application/octet-stream
${ARTIFACT_ID} artifactId
${WRONG_ACCEPT} application/json
${vnfLcmOpOccId} 6fc3539c-e602-4afa-8e13-962fb5a7d81d
${CancelMode} GRACEFUL
${LccnSubscriptionRequest} {}
${NVFM_DUPLICATION} 0
${sub_filter} filter
${sub_filter_invalid} filter_invalid
${subscriptionId} 6fc3539c-e602-4afa-8e13-962fb5a7d81f
${notification_ep} /notification
${notification_port} 9091
${AlarmNotification} {}
${AlarmClearedNotification} {}
${AlarmListRebuiltNotification} {}
${PerceivedSeverity} CRITICAL
\ No newline at end of file
SOL002/VNFFaultManagement-API_egm/IndividualAlarm.robot
+ 3
− 5
View file @ 5bd9a483
...@@ -19,11 +19,10 @@ POST Alarm - Method not implemented ...@@ -19,11 +19,10 @@ POST Alarm - Method not implemented
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
Post ${apiRoot}/${apiName}/${apiVersion}/alarms/${alarmId} Post ${apiRoot}/${apiName}/${apiVersion}/alarms/${alarmId}
Log Validate Status code Log Validate Status code
Output response
Integer response status 405 Integer response status 405
Get information about an alarm Get information about a configuration
Log Query VNF The GET method queries information about multiple alarms. Log Query VNF The GET method queries information about an alarm.
Set Headers {"Accept":"${ACCEPT}"} Set Headers {"Accept":"${ACCEPT}"}
Set Headers {"Content-Type": "${CONTENT_TYPE}"} Set Headers {"Content-Type": "${CONTENT_TYPE}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
...@@ -45,7 +44,6 @@ PUT Alarm - Method not implemented ...@@ -45,7 +44,6 @@ PUT Alarm - Method not implemented
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
Put ${apiRoot}/${apiName}/${apiVersion}/alarms/${alarmId} Put ${apiRoot}/${apiName}/${apiVersion}/alarms/${alarmId}
Log Validate Status code Log Validate Status code
Output response
Integer response status 405 Integer response status 405
PATCH Alarm PATCH Alarm
...@@ -111,5 +109,5 @@ DELETE Alarm - Method not implemented ...@@ -111,5 +109,5 @@ DELETE Alarm - Method not implemented
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
Delete ${apiRoot}/${apiName}/${apiVersion}/alarms/${alarmId} Delete ${apiRoot}/${apiName}/${apiVersion}/alarms/${alarmId}
Log Validate Status code Log Validate Status code
Output response
Integer response status 405 Integer response status 405
TrackingStatus.txt
+ 2
− 1
View file @ 5bd9a483
SOL002 SOL002
- VNFConfiguration-API_egm --------------------------------> [NOT STARTED] - VNFConfiguration-API_egm --------------------------------> [DONE]
* Configuration -----------------------------------------> [DONE]
- VNFFaultManagement-API_egm ------------------------------> [DONE] - VNFFaultManagement-API_egm ------------------------------> [DONE]
* Alarms ----------------------------------------------------> [DONE] * Alarms ----------------------------------------------------> [DONE]
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment