3.3.1 dev sol011 final

Merge request reports

Loading
+58
Changes for SOL011/NSInstanceUsageNotification-API/environment/variables.txt: 58 added lines, 0 removed lines.
Original line number Diff line number Diff line
*** Variables ***
${NFVO_HOST}      localhost    # Hostname of the NFVO
${NFVO_PORT}      8081    # Listening port of the NFVO
${NFVO_SCHEMA}    https
${AUTHORIZATION}    Bearer    QWxhZGRpbjpvcGVuIHNlc2FtZQ==
${CONTENT_TYPE}    application/json
${CONTENT_TYPE_JSON}    application/json
${ACCEPT}         application/json
${AUTH_USAGE}     1
${ACCEPT_JSON}         application/json
${apiRoot}        /
${apiName}        nsiun
${apiVersion}     v1

${SYNC_MODE}    1

${response}    {}

${NFVO_DUPLICATION}    1

${VNFM_HOST}      localhost    # Hostname of the VNFM
${VNFM_PORT}      8080    # Listening port of the VNFM
${VNFM_SCHEMA}    https
${CONTENT_TYPE_PATCH}    application/merge-patch+json
${WRONG_AUTHORIZATION}    Bearer    XXXXXWRONGXXXXX

${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

${sub_filter}    filter
${sub_filter_invalid}    filter_invalid
${fields}         criteria,objectInstanceIds
${subscriptionId}    6fc3539c-e602-4afa-8e13-962fb5a7d81f
${notification_ep}    notification
${VrQuotaAvailNotification}    {}

${callback_uri}    http://localhost
${callback_port}    9091
${callback_endpoint}    /endpoint
${callback_endpoint_fwd}    /endpoint/check
${callback_endpoint_error}    /endpoint_404
${sleep_interval}    20s
${total_polling_time}   2 min
${polling_interval}     10 sec

${notification_request}    []
${notification_response}    []

${callbackResp}		127.0.0.1

${MOCK_SERVER_JAR}    ../../../bin/mockserver-netty-5.5.0-jar-with-dependencies.jar
+9
Changes for SOL011/NSInstanceUsageNotification-API/jsons/NsInstanceUsageNotification.json: 9 added lines, 0 removed lines.
Original line number Diff line number Diff line
{{
  "id": "",
  "notificationType": "NSInstanceUsageNotification",
  "subscriptionId": "{subscriptionId}",
  "timeStamp": "",
  "nsInstanceId": "",
  "status": "START",
  "_links": ""
}}
 No newline at end of file
+10
Changes for SOL011/NSInstanceUsageNotification-API/jsons/NsInstanceUsageSubscriptionRequest.json: 10 added lines, 0 removed lines.
Original line number Diff line number Diff line
{
  "filter": {
    "nsInstanceUsageNotificationFilter": {
      "nsInstanceId": "6fc3539c-e602-4afa-8e13-962fb5a7d81f",
      "status": "START"
    }
  },
  "callbackUri": "http://127.0.0.1/subscribe",
  "authentication": ""
}
 No newline at end of file
+43
Changes for SOL011/NSInstanceUsageNotification-API/schemas/NsInstanceUsageNotification.schema.json: 43 added lines, 0 removed lines.
Original line number Diff line number Diff line
{
  "description": "This type represents an NS instance usage notification, which indicates the start  or end of usage of an NS instance as a part of a composite NS managed by the NFVO-C.  It shall comply with the provisions defined in table 8.6.2.4-1.",
  "type": "object",
  "required": [
    "id",
    "notificationType",
    "subscriptionId",
    "timeStamp",
    "nsInstanceId",
    "status",
    "_links"
  ],
  "properties": {
    "id": {
      "description": "Identifier of this notification. If a notification is sent multiple times due  to multiple subscriptions, the \"id\" attribute of all these notifications shall  have the same value.",
      "$ref": "../components/SOL011_schemas.yaml#/components/schemas/Identifier"
    },
    "notificationType": {
      "description": "Discriminator for the different notification types. Shall be set to  \"NsInstanceUsageNotification\" for this notification type.",
      "type": "string"
    },
    "subscriptionId": {
      "description": "Identifier of the subscription that this notification relates to.",
      "$ref": "../components/SOL011_schemas.yaml#/components/schemas/Identifier"
    },
    "timeStamp": {
      "description": "Date and time of the generation of the notification.",
      "$ref": "../components/SOL011_schemas.yaml#/components/schemas/DateTime"
    },
    "nsInstanceId": {
      "description": "Identifier of the NS instance affected.",
      "$ref": "../components/SOL011_schemas.yaml#/components/schemas/Identifier"
    },
    "status": {
      "description": "Indicates whether this notification reports about the start of the usage of  an NS instance or about the end of the usage of an NS instance.",
      "$ref": "#/components/schemas/NsInstanceUsageStatusType"
    },
    "_links": {
      "description": "Links to resources related to this notification.",
      "$ref": "../components/SOL011_schemas.yaml#/components/schemas/NotificationLink"
    }
  }
}
 No newline at end of file
+34
Changes for SOL011/NSInstanceUsageNotification-API/schemas/ProblemDetails.schema.json: 34 added lines, 0 removed lines.
Original line number Diff line number Diff line
{
  "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
Loading
Loading