Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
NFV - Network Functions Virtualisation
SOL005
Commits
f1449bf5
Commit
f1449bf5
authored
Jul 10, 2019
by
moscatelli
Browse files
SOL005_74: NS LCM occurrences GET method updated
parent
0b57b12e
Pipeline
#1242
passed with stage
in 0 seconds
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
src/SOL005/NSLifecycleManagement/NSLifecycleManagement.yaml
View file @
f1449bf5
...
...
@@ -811,7 +811,7 @@ paths:
required
:
false
type
:
string
description
:
>
Attribute-based filtering expression according to clause
4.3.2
.
Attribute-based filtering expression according to clause
5.2 of ETSI GS NFV SOL 013
.
The NFVO shall support receiving this parameter as part of the URI query string.
The OSS/BSS may supply this parameter.
All attribute names that appear in the NsLcmOpOcc and in data types referenced
...
...
@@ -821,14 +821,14 @@ paths:
required
:
false
type
:
string
description
:
>
Complex attributes to be included into the response. See clause
4
.3
.
3 for details. The
Complex attributes to be included into the response. See clause
5
.3
of ETSI GS NFV SOL 01
3 for details. The
NFVO should support this parameter.
-
name
:
exclude_fields
in
:
query
required
:
false
type
:
string
description
:
>
Complex attributes to be excluded from the response. See clause
4
.3
.
3 for details.
Complex attributes to be excluded from the response. See clause
5
.3
of ETSI GS NFV SOL 01
3 for details.
The NFVO should support this parameter.
-
name
:
exclude_default
in
:
query
...
...
@@ -836,7 +836,7 @@ paths:
type
:
string
description
:
>
Indicates to exclude the following complex attributes from the response. See
clause
4
.3
.
3 for details. The NFVO shall support this parameter.
clause
5
.3
of ETSI GS NFV SOL 01
3 for details. The NFVO shall support this parameter.
The following attributes shall be excluded from the NsLcmOpOcc structure in the
response body if this parameter is provided:
- operationParams
...
...
@@ -847,7 +847,8 @@ paths:
in
:
query
description
:
>
Marker to obtain the next page of a paged response. Shall be supported by the NFVO
if the NFVO supports alternative 2 (paging) according to clause 4.7.2.1 for this resource.
if the NFVO supports alternative 2 (paging) according to clause 5.4.2.1 of
ETSI GS NFV SOL 013 for this resource.
required
:
false
type
:
string
-
name
:
Accept
...
...
@@ -876,12 +877,19 @@ paths:
200 OK
Status information for zero or more NS lifecycle management operation
occurrences
w
as queried successfully.
occurrences
h
as
been
queried successfully.
The response body shall contain in an array the representations of
zero or more NS instances, as defined in clause 5.5.2.13.
zero or more NS instances, as defined in clause 6.5.2.3.
If the "filter" URI parameter or one of the "all_fields", "fields",
"exclude_fields" or "exclude_default" URI parameters was supplied in
the request and is supported, the data in the response body shall have
been transformed according to the rules specified in clauses 5.2.2 and
5.3.2 of ETSI GS NFV SOL 013, respectively.
If the NFVO supports alternative 2 (paging) according to
clause
4.7
.2.1 for this resource, inclusion of the Link HTTP header
in this response shall follow the provisions in clause
4.7.2.
3.
clause
5.4
.2.1
of ETSI GS NFV SOL 013
for this resource, inclusion of the Link HTTP header
in this response shall follow the provisions in clause
5.4.2.3 of ETSI GS NFV SOL 01
3.
headers
:
Content-Type
:
description
:
The MIME type of the body of the response.
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment