Skip to content
GitLab
Commit 193ad4a8 authored by Giacomo Bernini's avatar Giacomo Bernini
Browse files

addressed comments from SOL WG review

parent 8199a708
Pipeline #13388 passed with stage
in 0 seconds
Hide whitespace changes
Inline Side-by-side
src/SOL005/NFVICapacityInformation/NFVICapacityInformation.yaml
View file @ 193ad4a8
......@@ -20,7 +20,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/nfvici/v1
......
src/SOL005/NFVICapacityInformationNotification/NFVICapacityInformationNotification.yaml
View file @ 193ad4a8
......@@ -20,7 +20,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/callback/v1
......
src/SOL005/NSDManagement/NSDManagement.yaml
View file @ 193ad4a8
......@@ -20,7 +20,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/nsd/v2
......@@ -1208,7 +1208,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1250,7 +1250,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1296,7 +1296,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1331,7 +1331,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1404,7 +1404,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1491,7 +1491,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1526,7 +1526,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1560,7 +1560,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1599,7 +1599,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1634,7 +1634,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1676,7 +1676,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1782,7 +1782,7 @@ components:
type: string
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1805,7 +1805,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1877,7 +1877,7 @@ components:
type: string
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1906,7 +1906,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1939,7 +1939,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1986,7 +1986,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2027,7 +2027,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2060,7 +2060,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2096,7 +2096,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2156,7 +2156,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2195,7 +2195,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2246,7 +2246,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2282,7 +2282,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2401,7 +2401,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2435,7 +2435,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2474,7 +2474,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2638,7 +2638,7 @@ components:
type: string
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2661,7 +2661,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2719,7 +2719,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2765,7 +2765,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2801,7 +2801,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2888,11 +2888,11 @@ components:
If the content type cannot be determined, the header shall be set to the value
"application/octet-stream".
The "Content-Range" HTTP header shall be provided according to IETF RFC 7233.
The "Content-Range" HTTP header shall be provided according to IETF RFC 9110.
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2924,7 +2924,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2957,7 +2957,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -2992,7 +2992,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -3025,7 +3025,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -3068,7 +3068,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -3110,7 +3110,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -3152,7 +3152,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -3202,7 +3202,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......
src/SOL005/NSDManagementNotification/NSDManagementNotification.yaml
View file @ 193ad4a8
......@@ -20,7 +20,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/callback/v2
......
src/SOL005/NSFaultManagement/NSFaultManagement.yaml
View file @ 193ad4a8
......@@ -20,7 +20,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/nsfm/v1
......@@ -689,7 +689,7 @@ components:
type: string
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......
src/SOL005/NSFaultManagementNotification/NSFaultManagementNotification.yaml
View file @ 193ad4a8
......@@ -20,7 +20,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/callback/v1
......
src/SOL005/NSLCMCoordination/NSLCMCoordination.yaml
View file @ 193ad4a8
......@@ -20,7 +20,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/lcmcoord/v1
......
src/SOL005/NSLifecycleManagement/NSLifecycleManagement.yaml
View file @ 193ad4a8
......@@ -20,7 +20,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/nslcm/v2
......
src/SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml
View file @ 193ad4a8
......@@ -402,7 +402,7 @@ definitions:
This type represents a VNF instance. It shall comply with the provisions defined in table 6.5.3.57-1.
NOTE: Clause B.3.2 of ETSI GS NFV-SOL 003 provides examples illustrating the relationship among the
different run-time idata types (CP, VL and link ports) used to represent the connectivity
different run-time data types (CP, VL and link ports) used to represent the connectivity
of a VNF.
NOTE 1: Modifying the value of this attribute shall not be performed when conflicts exist between the
......@@ -2646,10 +2646,10 @@ definitions:
InstantiateVnfData:
description: >
This type represents the information related to a SAP of a NS. The InstantiateVnfData data type specifies the
parameters that are needed for VNF instantiation. This information element is used for the bottom-up NS creation when
the OSS/BSS explicitly requests VNF instantiation for a given NS. When the NFVO invokes the Instantiate VNF
update operation, a set of these parameters are then passed by the NFVO to the VNFM.
This type represents the information that are needed for VNF instantiation. This data type is used for the
bottom-up NS creation when the OSS/BSS explicitly requests VNF instantiation for a given NS. When the NFVO
invokes the Instantiate VNF update operation, a set of these parameters are then passed by the NFVO to the VNFM.
It shall comply with the provisions defined in table 6.5.3.24-1
NOTE 1: It is possible to have several ExtManagedVirtualLinkData for the same VNF internal
VL in case of a multi-site VNF spanning several VIMs. The set of ExtManagedVirtualLinkData
......@@ -2662,6 +2662,7 @@ definitions:
may select a matching vnfProfile based on other information, such as external VL.
NOTE 3: Either the attribute triple "vnfdId, vnfFlavourId and vnfInstantiationLevelId
(if provided)" or the attribute "vnProfileId" shall be present, but not both.
type: object
properties:
vnfdId:
......
src/SOL005/NSLifecycleManagementNotification/NSLifecycleManagementNotification.yaml
View file @ 193ad4a8
......@@ -18,7 +18,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/callback/v2
......
src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml
View file @ 193ad4a8
......@@ -20,7 +20,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/nspm/v2
......@@ -423,7 +423,7 @@ paths:
# - name: Authorization
# description: |
# The authorization token for the request.
# Reference: IETF RFC 7235.
# Reference: IETF RFC 9110.
# in: header
# required: false
# type: string
......@@ -452,14 +452,14 @@ paths:
# - name: Accept
# description: |
# Content-Types that are acceptable for the response.
# Reference: IETF RFC 7231.
# Reference: IETF RFC 9110.
# in: header
# required: true
# type: string
# - name: Content-Type
# description: |
# The MIME type of the body of the request.
# Reference: IETF RFC 7231.
# Reference: IETF RFC 9110.
# in: header
# required: true
# type: string
......@@ -553,7 +553,7 @@ paths:
# - name: Accept
# description: |
# Content-Types that are acceptable for the response.
# Reference: IETF RFC 7231.
# Reference: IETF RFC 9110.
# in: header
# required: true
# type: string
......@@ -635,14 +635,14 @@ paths:
# Identifier of the subscription.
# This identifier can be retrieved from the resource referenced by the "Location" HTTP header in the response
# to a POST request creating a new subscription resource. It can also be retrieved from the "id" attribute in the
# payload body of that response.
# message content of that response.
# in: path
# type: string
# required: true
# - name: Authorization
# description: |
# The authorization token for the request.
# Reference: IETF RFC 7235
# Reference: IETF RFC 9110
# in: header
# required: true
# type: string
......@@ -664,7 +664,7 @@ paths:
# - name: Accept
# description: |
# Content-Types that are acceptable for the response.
# Reference: IETF RFC 7231
# Reference: IETF RFC 9110
# in: header
# required: true
# type: string
......@@ -734,7 +734,7 @@ paths:
# - name: Accept
# description: |
# Content-Types that are acceptable for the response.
# Reference: IETF RFC 7231.
# Reference: IETF RFC 9110.
# in: header
# required: true
# type: string
......@@ -784,7 +784,7 @@ components:
name: Content-Type
in: header
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
required: true
schema:
type: string
......@@ -965,7 +965,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......@@ -1312,7 +1312,7 @@ components:
headers:
Content-Type:
description: |
The MIME type of the body of the request. Reference: IETF RFC 7231
The MIME type of the body of the request. Reference: IETF RFC 9110
style: simple
explode: false
schema:
......
src/SOL005/NSPerformanceManagementNotification/NSPerformanceManagementNotification.yaml
View file @ 193ad4a8
......@@ -20,7 +20,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/callback/v2
......
src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml
View file @ 193ad4a8
......@@ -20,7 +20,7 @@ info:
externalDocs:
description: ETSI GS NFV-SOL 005 V3.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_nfv-sol005v030701p.pdf
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/03.07.01_60/gs_NFV-SOL005v030701p.pdf
servers:
- url: http://127.0.0.1/vnfpkgm/v2
......
src/SOL005/VNFPackageManagement/definitions/SOL005VNFPackageManagement_def.yaml
View file @ 193ad4a8
......@@ -16,7 +16,6 @@ definitions:
- onboardingState
- operationalState
- usageState
- vnfmInfo
- _links
properties:
id:
......@@ -129,9 +128,9 @@ definitions:
$ref: "#/definitions/PackageUsageStateType"
vnfmInfo:
description: >
Specifies VNFMs compatible with the VNF.