Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
SOL002-SOL003
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
NFV - Network Functions Virtualisation
SOL002-SOL003
Commits
8c7d8792
Commit
8c7d8792
authored
5 years ago
by
Samir Medjiah
Browse files
Options
Downloads
Patches
Plain Diff
SOL002_51 GET method (on VNF LCM operation occurrences) request and response updated
parent
c7a70114
Branches
2.4.1-maintenance
Tags
v2.4.1
1 merge request
!6
Merge 2.6.1-dev branch
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml
+17
-12
17 additions, 12 deletions
...SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml
with
17 additions
and
12 deletions
src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml
+
17
−
12
View file @
8c7d8792
...
...
@@ -1444,7 +1444,7 @@ paths:
parameters
:
-
name
:
filter
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 VNFM shall support receiving this parameter as part of the URI query string.
The EM/VNF may supply this parameter. All attribute names that appear in the VnfLcmOpOcc
and in data types referenced from it shall be supported by the VNFM in the filter expression.
...
...
@@ -1477,28 +1477,28 @@ paths:
-
name
:
all_fields
description
:
>
Include all complex attributes in the response.
See clause
4
.3
.
3 for details. The VNFM shall support this parameter.
See clause
5
.3
of ETSI GS NFV-SOL 01
3 for details. The VNFM shall support this parameter.
in
:
query
required
:
false
type
:
string
-
name
:
fields
description
:
>
Complex attributes to be included into the response.
See clause
4
.3
.
3 for details. The VNFM should support this parameter.
See clause
5
.3
of ETSI GS NFV-SOL 01
3 for details. The VNFM should support this parameter.
in
:
query
required
:
false
type
:
string
-
name
:
exclude_fields
description
:
>
Complex attributes to be excluded from the response.
See clause
4
.3
.
3 for details. The VNFM should support this parameter.
See clause
5
.3
of ETSI GS NFV-SOL 01
3 for details. The VNFM should support this parameter.
in
:
query
required
:
false
type
:
string
-
name
:
exclude_default
description
:
>
Indicates to exclude the following complex attributes from the response.
See clause
4
.3
.
3 for details. The VNFM shall support this parameter.
See clause
5
.3
of ETSI GS NFV-SOL 01
3 for details. The VNFM shall support this parameter.
The following attributes shall be excluded from the VnfLcmOpOcc structure
in the response body if this parameter is provided, or none of the parameters
"all_fields", "fields", "exclude_fields", "exclude_default" are provided:
...
...
@@ -1513,8 +1513,9 @@ paths:
-
name
:
nextpage_opaque_marker
description
:
>
Marker to obtain the next page of a paged response.
Shall be supported by the VNFM if the VNFM supports alternative 2
(paging) according to clause 4.7.2.1 for this resource.
Shall be supported by the VNFM if the VNFM supports
alternative 2 (paging) according to clause 5.4.2.1
of ETSI GS NFV-SOL 013 for this resource.
in
:
query
required
:
false
type
:
string
...
...
@@ -1523,11 +1524,15 @@ paths:
description
:
>
200 OK
Status information for zero or more VNF lifecycle management operation occurrences was queried successfully.
The response body shall contain in an array the status information about zero or more VNF lifecycle
operation occurrences, as defined in clause 5.5.2.13.
If the VNFM 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.
Status information for zero or more VNF lifecycle management operation
occurrences has been queried successfully.
The response body shall contain in an array the status information
about zero or more VNF lifecycle operation occurrences, as defined in
clause 5.5.2.13.
If the VNFM supports alternative 2 (paging) according to 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 013.
headers
:
Content-Type
:
description
:
The MIME type of the body of the response.
...
...
This diff is collapsed.
Click to expand it.
Samir Medjiah
@medjiah
mentioned in commit
1241de32
·
5 years ago
mentioned in commit
1241de32
mentioned in commit 1241de32e1aef47fe54c6f44bcb3221e52949a9d
Toggle commit list
Preview
0%
Loading
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!
Save comment
Cancel
Please
register
or
sign in
to comment