Commit 1f887009 authored by rameshnaraya's avatar rameshnaraya

Merge Request Issue. Re committing NSD Files.

parent 7a10c8d8
Pipeline #159 passed with stage
in 0 seconds
This diff is collapsed.
# Copyright (c) ETSI 2017.
# https://forge.etsi.org/etsi-forge-copyright-notice.txt
definitions:
Identifier:
description: >
An identifier with the intention of being globally unique.
type: string
KeyValuePairs:
description: >
This type represents a list of key-value pairs. The order of the pairs in the list is not significant.
......@@ -10,7 +14,35 @@
String:
description: >
This type represents stack of string values
type: string
type: string
Version:
description: >
A Version.
type: string
Uri:
description: >
String formatted according to IETF RFC 3986.
type: string
Link:
description: >
This type represents a link to a resource.
type: object
required:
- href
properties:
href:
description: >
URI of the referenced resource.
type: string
format: url
DateTime:
description: >
Date-time stamp.
Representation: String formatted according to IETF RFC 3339.
type: string
format: "date-time"
ProblemDetails:
#SOL005 location: 4.3.5.3-1
description: >
......
......@@ -56,7 +56,7 @@
description: >
Conflict
The operation cannot be executed currently,
Error: The operation cannot be executed currently,
due to a conflict with the state of the resource.
Typically, this is due to the fact the NS descriptor
resource is in the enabled operational state (i.e.
......@@ -112,7 +112,7 @@
description: >
Conflict
Another request is in progress that prohibits the fulfilment of
Another request is in progress that prohibits the fulfillment of
the current request, or the current resource state is inconsistent
with the request.
headers:
......@@ -207,5 +207,86 @@
type: string
maximum: 1
minimum: 0
schema:
$ref: "../definitions/SOL005_def.yaml#/definitions/ProblemDetails"
409-nsd-onboarding-state-NOT-ONBOARDED:
description: >
Conflict
Error: The operation cannot be executed currently,
due to a conflict with the state of the resource.
Typically, this is due to the fact "nsdOnboardingState"
has a value different from ONBOARDED.
The response body shall contain a ProblemDetails
structure, in which the "detail" attribute shall convey
more information about the error.
headers:
Content-Type:
description: The MIME type of the body of the response.
type: string
maximum: 1
minimum: 1
WWW-Authenticate:
description: >
Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP
request has provided an invalid authorization token.
type: string
maximum: 1
minimum: 0
schema:
$ref: "../definitions/SOL005_def.yaml#/definitions/ProblemDetails"
409-pnfd-onboarding-state-NOT-ONBOARDED:
description: >
Conflict
Error: The operation cannot be executed currently,
due to a conflict with the state of the resource.
Typically, this is due to the fact pnfdOnboardingState
has a value different from ONBOARDED.
The response body shall contain a ProblemDetails
structure, in which the "detail" attribute shall convey
more information about the error.
headers:
Content-Type:
description: The MIME type of the body of the response.
type: string
maximum: 1
minimum: 1
WWW-Authenticate:
description: >
Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP
request has provided an invalid authorization token.
type: string
maximum: 1
minimum: 0
schema:
$ref: "../definitions/SOL005_def.yaml#/definitions/ProblemDetails"
409-pnfd-onboarding-state-NOT-CREATED:
description: >
Conflict.
Error: The operation cannot be executed currently,
due to a conflict with the state of the resource.
Typically, this is due to the fact that the
PnfdOnboardingState has a value other than CREATED.
The response body shall contain a ProblemDetails
structure, in which the "detail" attribute shall convey
more information about the error.
headers:
Content-Type:
description: The MIME type of the body of the response.
type: string
maximum: 1
minimum: 1
WWW-Authenticate:
description: >
Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP
request has provided an invalid authorization token.
type: string
maximum: 1
minimum: 0
schema:
$ref: "../definitions/SOL005_def.yaml#/definitions/ProblemDetails"
\ No newline at end of file
......@@ -49,7 +49,7 @@
minimum: 0
206:
description: >
Partial Content
Partial Content.
On success, if the NFVO supports range requests, a
single consecutive byte range from the content of the
......@@ -332,10 +332,13 @@
$ref: "../definitions/SOL005_def.yaml#/definitions/ProblemDetails"
412:
description: >
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
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.
headers:
......@@ -349,8 +352,7 @@
416:
description: >
The byte range passed in the "Range" header did not
match any available byte range in the NSD file (e.g.
"access after end of file").
match any available byte range in the NSD file (e.g. access after end of file).
The response body may contain a ProblemDetails structure.
headers:
Content-Type:
......
Markdown is supported
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