Skip to content
GitLab
Commit 5784d120 authored by Francesca Moscatelli's avatar Francesca Moscatelli
Browse files

SOL003_1->SOL003_61: implementation of differences between v2.7.1 and v2.8.1

parent 3202703d
Pipeline #5985 failed with stage
in 0 seconds
Expand all Hide whitespace changes
Inline Side-by-side
src/SOL003/APIVersion/APIVersion.yaml
View file @ 5784d120
......@@ -15,8 +15,8 @@ info:
contact:
name: "NFV-SOL WG"
externalDocs:
description: ETSI GS NFV-SOL 003 V2.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf
description: ETSI GS NFV-SOL 003 V2.8.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.08.01_60/gs_NFV-SOL003v020801p.pdf
schemes:
- http
- https
......
src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml
View file @ 5784d120
......@@ -25,8 +25,8 @@ info:
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
externalDocs:
description: ETSI GS NFV-SOL 003 V2.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf
description: ETSI GS NFV-SOL 003 V2.8.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.08.01_60/gs_NFV-SOL003v020801p.pdf
basePath: "/vnffm/v1"
......@@ -244,7 +244,7 @@ paths:
patch:
description: >
Acknowledge Alarm.
This method modifies an individual alarm resource.
This method modifies an "Individual alarm" resource.
This method shall follow the provisions specified in the tables 7.4.3.3.4-1 and 7.4.3.3.4-2
for URI query parameters, request and response data structures, and response codes.
parameters:
......@@ -354,14 +354,14 @@ paths:
for URI query parameters, request and response data structures, and response codes.
As the result of successfully executing this method, a new "Individual subscription" resource
as defined in clause 7.4.5 shall have been created. This method shall not trigger any notification.
Creation of two "Individual subscription" resources with the same callbackURI and the same filter
Creation of two "Individual subscription" resources with the same callback URI and the same filter
can result in performance degradation and will provide duplicates of notifications to the NFVO,
and might make sense only in very rare use cases. Consequently, the VNFM may either allow creating
a new "Individual subscription" resource if another "Individual subscription" resource with the
same filter and callbackUri already exists (in which case it shall return the "201 Created" response code),
same filter and callback URI already exists (in which case it shall return the "201 Created" response code),
or may decide to not create a duplicate "Individual subscription" resource (in which case it shall return
a "303 See Other" response code referencing the existing "Individual subscription" resource with the
same filter and callbackUri).
same filter and callback URI).
parameters:
- name: FmSubscriptionRequest
description: The VNF creation parameters
......@@ -431,17 +431,6 @@ paths:
schema:
$ref: "../../definitions/SOL002SOL003VNFFaultManagement_def.yaml#/definitions/FmSubscription"
303:
# description: >
# 303 SEE OTHER
#
# Shall be returned when a subscription with the
# same callbackURI and the same filter already exists
# and the policy of the VNFM is to not create
# redundant subscriptions.
# The HTTP response shall include a "Location"
# HTTP header that contains the resource URI of the
# existing "Individual subscription" resource.
# The response body shall be empty.
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303"
400:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400"
......@@ -525,7 +514,7 @@ paths:
description: >
200 OK
The list of subscriptions has been queried successfully.
Shall be returned when the list of subscriptions has been queried successfully.
The response body shall contain in an array the representations of all active subscriptions
of the functional block that invokes the method, i.e. zero or more representations of
FM subscriptions as defined in clause 7.5.2.3.
......
src/SOL003/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml
View file @ 5784d120
......@@ -25,8 +25,8 @@ info:
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
externalDocs:
description: ETSI GS NFV-SOL 003 V2.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf
description: ETSI GS NFV-SOL 003 V2.8.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.08.01_60/gs_NFV-SOL003v020801p.pdf
basePath: "/callback/v1"
......@@ -119,7 +119,7 @@ paths:
get:
description: >
The GET method allows the server to test the notification endpoint that is provided by the API consumer,
The GET method allows the API producer to test the notification endpoint that is provided by the API consumer,
e.g. during subscription.
This method shall follow the provisions specified in the tables 7.4.6.3.2-1 and 7.4.6.3.2-2
for URI query parameters, request and response data structures, and response codes.
......@@ -254,7 +254,7 @@ paths:
get:
description: >
The GET method allows the server to test the notification endpoint that is provided by the API consumer,
The GET method allows the API producer to test the notification endpoint that is provided by the API consumer,
e.g. during subscription.
This method shall follow the provisions specified in the tables 7.4.6.3.2-1 and 7.4.6.3.2-2
for URI query parameters, request and response data structures, and response codes.
......@@ -389,7 +389,7 @@ paths:
get:
description: >
The GET method allows the server to test the notification endpoint that is provided by the API consumer,
The GET method allows the API producer to test the notification endpoint that is provided by the API consumer,
e.g. during subscription.
This method shall follow the provisions specified in the tables 7.4.6.3.2-1 and 7.4.6.3.2-2
for URI query parameters, request and response data structures, and response codes.
......
src/SOL003/VNFIndicator/VNFIndicator.yaml
View file @ 5784d120
......@@ -14,8 +14,8 @@ info:
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
externalDocs:
description: ETSI GS NFV-SOL 003 V2.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf
description: ETSI GS NFV-SOL 003 V2.8.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.08.01_60/gs_NFV-SOL003v020801p.pdf
basePath: "/vnfind/v1"
......@@ -407,14 +407,14 @@ paths:
The POST method creates a new subscription.
As the result of successfully executing this method, a new "Individual subscription" resource
as defined in clause 8.4.6 shall have been created. This method shall not trigger any notification.
Creation of two "Individual subscription" resources with the same callbackURI and the same filter
Creation of two "Individual subscription" resources with the same callback URI and the same filter
can result in performance degradation and will provide duplicates of notifications to the NFVO,
and might make sense only in very rare use cases. Consequently, the VNFM may either allow creating
a new "Individual subscription" resource if another "Individual subscription" resource with the
same filter and callbackUri already exists (in which case it shall return the "201 Created" response code),
same filter and callback URI already exists (in which case it shall return the "201 Created" response code),
or may decide to not create a duplicate "Individual subscription" resource (in which case it shall return
a "303 See Other" response code referencing the existing "Individual subscription" resource with the same
filter and callbackUri).
filter and callback URI).
This method shall follow the provisions specified in the tables 8.4.5.3.1-1 and 8.4.5.3.1-2
for URI query parameters, request and response data structures, and response codes.
parameters:
......
src/SOL003/VNFIndicatorNotification/VNFIndicatorNotification.yaml
View file @ 5784d120
......@@ -25,8 +25,8 @@ info:
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
externalDocs:
description: ETSI GS NFV-SOL 003 V2.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf
description: ETSI GS NFV-SOL 003 V2.8.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.08.01_60/gs_NFV-SOL003v020801p.pdf
basePath: "/callback/v1"
......@@ -111,7 +111,7 @@ paths:
get:
description: >
The GET method allows the server to test the notification endpoint that is provided by the API consumer,
The GET method allows the API producer to test the notification endpoint that is provided by the API consumer,
e.g. during subscription.
This method shall follow the provisions specified in the tables 8.4.7.3.2-1 and 8.4.7.3.2-2
for URI query parameters, request and response data structures, and response codes.
......
src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml
View file @ 5784d120
swagger: "2.0"
info:
version: "1.4.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
version: "1.5.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
title: SOL003 - VNF Lifecycle Management interface
description: >
SOL003 - VNF Lifecycle Management interface definition
......@@ -25,8 +25,8 @@ info:
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
externalDocs:
description: ETSI GS NFV-SOL 003 V2.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf
description: ETSI GS NFV-SOL 003 V2.8.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.08.01_60/gs_NFV-SOL003v020801p.pdf
basePath: "/vnflcm/v1"
......@@ -52,15 +52,8 @@ paths:
#SOL003 location: 5.4.2
post:
description: >
Create VNF Identifier.
The POST method creates a new VNF instance resource.
This method shall follow the provisions specified in the tables 5.4.2.3.1-1 and 5.4.2.3.1-2
for URI query parameters, request and response data structures, and response codes.
As the result of successfully executing this method, a new "Individual VNF instance"
resource as defined in clause 5.4.3 shall have been created, and the value of the
"instantiationState" attribute in the representation of that resource shall be "NOT_INSTANTIATED".
A notification of type VnfIdentifierCreationNotification shall be triggered as part of successfully
executing this method as defined in clause 5.5.2.18.
The POST method creates a new VNF instance resource based on a VNF package
that is onboarded and in "ENABLED" state.
parameters:
- name: createVnfRequest
description: The VNF creation parameters
......@@ -1737,7 +1730,7 @@ paths:
maximum: 1
minimum: 0
schema:
$ref: "../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfLcmOpOcc"
$ref: "./definitions/SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfLcmOpOcc"
400:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400"
401:
......@@ -1831,7 +1824,7 @@ paths:
maximum: 1
minimum: 1
schema:
$ref: "../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfLcmOpOcc"
$ref: "./definitions/SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfLcmOpOcc"
400:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400"
401:
......@@ -2134,7 +2127,7 @@ paths:
maximum: 1
minimum: 1
schema:
$ref: "../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfLcmOpOcc"
$ref: "./definitions/SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfLcmOpOcc"
400:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400"
401:
......@@ -2292,14 +2285,14 @@ paths:
for URI query parameters, request and response data structures, and response codes.
As the result of successfully executing this method, a new "Individual subscription"
resource as defined in clause 5.4.3 shall have been created. This method shall not trigger any notification.
Creation of two "Individual subscription" resources with the same callbackURI and the same filter
Creation of two "Individual subscription" resources with the same callback URI and the same filter
can result in performance degradation and will provide duplicates of notifications to the NFVO,
and might make sense only in very rare use cases. Consequently, the VNFM may either allow creating
an "Individual subscription" resource if another "Individual subscription" resource with the same
filter and callbackUri already exists (in which case it shall return the "201 Created" response code),
filter and callback URI already exists (in which case it shall return the "201 Created" response code),
or may decide to not create a duplicate "Individual subscription" resource (in which case it shall
return a "303 See Other" response code referencing the existing "Individual subscription" resource
with the same filter and callbackUri).
with the same filter and callback URI).
parameters:
- name: LccnSubscriptionRequest
description: >
......@@ -2371,14 +2364,6 @@ paths:
schema:
$ref: "../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/LccnSubscription"
303:
#description: >
#303 SEE OTHER
#Shall be returned if a subscription with the same callbackURI and the same filter already exists
#and the policy of the VNFM is to not create redundant subscriptions.
#The HTTP response shall include a "Location" HTTP header that contains the resource URI of the existing
#"Individual subscription" resource.
#The response body shall be empty.
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/303"
400:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/400"
......
src/SOL003/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml
View file @ 5784d120
......@@ -25,8 +25,8 @@ info:
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
externalDocs:
description: ETSI GS NFV-SOL 003 V2.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf
description: ETSI GS NFV-SOL 003 V2.8.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.08.01_60/gs_NFV-SOL003v020801p.pdf
basePath: "/callback/v1"
......@@ -56,7 +56,7 @@ paths:
in: body
required: true
schema:
$ref: "../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfLcmOperationOccurrenceNotification"
$ref: "./definitions/SOL003VNFLifecycleManagementNotification_def.yaml#/definitions/VnfLcmOperationOccurrenceNotification"
- name: Authorization
description: >
The authorization token for the request.
......@@ -115,7 +115,7 @@ paths:
get:
description: >
The GET method allows the server to test the notification endpoint that is provided by the API consumer,
The GET method allows the API producer to test the notification endpoint that is provided by the API consumer,
e.g. during subscription.
This method shall follow the provisions specified in the tables 5.4.20.3.2-1 and 5.4.20.3.2-2
for URI query parameters, request and response data structures, and response codes.
......
src/SOL003/VNFLifecycleManagementNotification/definitions/SOL003VNFLifecycleManagementNotification_def.yaml 0 → 100644
View file @ 5784d120
# Copyright (c) ETSI 2017.
# https://forge.etsi.org/etsi-forge-copyright-notice.txt
definitions:
VnfLcmOperationOccurrenceNotification:
description: >
This type represents a VNF lifecycle management operation occurrence
notification, which informs the receiver of changes in the VNF
lifecycle caused by a VNF LCM operation occurrence. The support of the
notification is mandatory.
This notification shall be triggered by the VNFM when there is a change
in the state of a VNF LCM operation occurrence that changes the VNF lifecycle,
which represents an occurrence of one the following LCM operations:
* Instantiation of the VNF
* Scaling of the VNF instance (including auto-scaling)
* Healing of the VNF instance (including auto-healing)
* Change of the state of the VNF instance (i.e. Operate VNF)
* Change of the deployment flavour of the VNF instance
* Change of the external connectivity of the VNF instance
* Termination of the VNF instance
* Modification of VNF instance information and/or VNF configurable
properties through the "PATCH" method on the "Individual VNF instance"
resource.
Clause 5.6.2 defines the states and state transition of a VNF LCM operation occurrence,
and also specifies details of the notifications to be emitted at each state transition.
If this is the initial notification about the start of a VNF LCM operation occurrence,
it is assumed that the notification is sent by the VNFM before any action (including sending the grant request)
is taken as part of the LCM operation. Due to possible race conditions, the "start" notification,
the grant request and the LCM operation acknowledgment (i.e. the "202 Accepted" response)
can arrive in any order at the NFVO, and the NFVO shall be able to handle such a situation.
If this is a notification about a final or intermediate result state of a VNF LCM operation occurrence,
the notification shall be sent after all related actions of the LCM operation that led
to this state have been executed.
The new state shall be set in the "Individual VNF LCM operation occurrence" resource before
the notification about the state change is sent.
See clause 5.6.2.2 for further provisions regarding sending this notification, including
in cases of handling LCM operation errors.
type: object
required:
- id
- notificationType
- subscriptionId
- timeStamp
- notificationStatus
- operationState
- vnfInstanceId
- operation
- isAutomaticInvocation
- vnfLcmOpOccId
- _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: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
notificationType:
description: >
Discriminator for the different notification types. Shall be set to
"VnfLcmOperationOccurrenceNotification" for this notification type.
type: string
enum:
- VnfLcmOperationOccurrenceNotification
subscriptionId:
description: >
Identifier of the subscription that this notification relates to.
Shall be set to the value of the "id" attribute of the "LccnSubscription"
representing the associated "Individual subscription" resource.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
timeStamp:
description: >
Date-time of the generation of the notification.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/DateTime"
notificationStatus:
description: >
Indicates whether this notification reports about the start of a
lifecycle operation or the result of a lifecycle operation.
Permitted values:
* START: Informs about the start of the VNF LCM operation
occurrence.
* RESULT: Informs about the final or intermediate result of the VNF
LCM operation occurrence.
type: string
enum:
- START
- RESULT
operationState:
description: >
The state of the VNF LCM operation occurrence.
$ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/LcmOperationStateType"
vnfInstanceId:
description: >
The identifier of the VNF instance affected.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
operation:
description: >
The lifecycle management operation.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/LcmOperationType"
isAutomaticInvocation:
description: >
Set to true if this VNF LCM operation occurrence has been triggered
by an automated procedure inside the VNFM
(i.e. ScaleVnf / ScaleVnfToLevel triggered by auto-scale, or HealVnf
triggered by auto-heal).
Set to false otherwise.
type: boolean
vnfLcmOpOccId:
description: >
The identifier of the VNF lifecycle management operation occurrence
associated to the notification.
Shall be set to the value of the "id" attribute of the "VnfLcmOpOcc"
representing the associated "Individual VNF lifecycle management operation
occurrence" resource.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
affectedVnfcs:
description: >
Information about VNFC instances that were affected during the
lifecycle operation.
Shall be present if the "notificationStatus" is set to "RESULT" and
the operation has performed any resource modification. Shall be
absent otherwise. This attribute contains information about the
cumulative changes to virtualised resources that were performed so
far by the VNF LCM operation occurrence and by any of the error
handling procedures for that operation occurrence.
type: array
items:
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/AffectedVnfc"
affectedVirtualLinks:
description: >
Information about VL instances that were affected during the
lifecycle operation.
NOTE 1: Shall be present if the "notificationStatus" is set to "RESULT"
and the operation has performed any resource modification. Shall be absent
otherwise. This attribute contains information about the cumulative changes
to virtualised resources that were performed so far by the VNF LCM operation
occurrence and by any of the error handling procedures for that operation
occurrence.
NOTE 2: For a particular affected VL, there shall be as many "AffectedVirtualLink"
entries as needed for signalling the different types of changes, i.e., one per
virtual link and change type. For instance, in the case of signaling affected VL
instances involving the addition of a particular VL instance with links ports,
one "AffectedVirtualLink" entry signals the addition of the VL by using the
"changeType" attribute of "AffectedVirtualLink" structure equal to "ADDED",
and another "AffectedVirtualLink" entry signals the addition of externally visible
VNF link ports of the VL by using the "changeType" equal to "LINK_PORT_ADDED".
type: array
items:
$ref: "../../VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml#/definitions/AffectedVirtualLink"
affectedExtLinkPorts:
description: >
Information about external VNF link ports that were affected during the
lifecycle operation. See note 1.
NOTE 1: Shall be present if the "notificationStatus" is set to "RESULT"
and the operation has performed any resource modification. Shall be absent
otherwise. This attribute contains information about the cumulative changes
to virtualised resources that were performed so far by the VNF LCM operation
occurrence and by any of the error handling procedures for that operation
occurrence.
type: array
items:
$ref: "../../VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml#/definitions/AffectedExtLinkPort"
affectedVirtualStorages:
description: >
Information about virtualised storage instances that were affected
during the lifecycle operation.
Shall be present if the "notificationStatus" is set to "RESULT" and
the operation has performed any resource modification. Shall be
absent otherwise. This attribute contains information about the
cumulative changes to virtualised resources that were performed so
far by the VNF LCM operation occurrence and by any of the error
handling procedures for that operation occurrence.
type: array
items:
$ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/AffectedVirtualStorage"
changedInfo:
description: >
Information about the changed VNF instance information, including
changed VNF configurable properties.
Shall be present if the "notificationStatus" is set to "RESULT" and
the operation has performed any changes to VNF instance information,
including VNF configurable properties.
Shall be absent otherwise.
$ref: "../../VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml#/definitions/VnfInfoModifications"
changedExtConnectivity:
description: >
Information about changed external connectivity, if this notification
represents the result of a lifecycle operation occurrence.
Shall be present if the "notificationStatus" is set to "RESULT" and
the "operation" has made any changes to the external connectivity of
the VNF instance. Shall be absent otherwise.
Only information about external VL instances that have been added or
modified shall be provided.
type: array
items:
$ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/ExtVirtualLinkInfo"
error:
description: >
Details of the latest error, if one has occurred during executing
the LCM operation (see clause 6.3 of ETSI GS NFV-SOL 013).
Shall be present if the "operationState" attribute is "FAILED_TEMP", "FAILED"
or "ROLLED_BACK" and shall be absent otherwise.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"
_links:
description: >
Links to resources related to this notification.
The link URIs in this structure shall be set to point to the resources identified
by the corresponding identifier attributes in this notification.
$ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/LccnLinks"
\ No newline at end of file
src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml
View file @ 5784d120
......@@ -25,9 +25,9 @@ info:
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
externalDocs:
description: ETSI GS NFV-SOL 003 V2.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.07.01_60/gs_NFV-SOL003v020701p.pdf
description: ETSI GS NFV-SOL 003 V2.8.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.08.01_60/gs_NFV-SOL003v020801p.pdf
basePath: "/grant/v1"
schemes:
......
src/SOL003/VNFLifecycleOperationGranting/definitions/VNFLifecycleOperationGranting_def.yaml
View file @ 5784d120
......@@ -178,12 +178,18 @@ definitions:
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
vnfInstanceId:
description: >
Identifier of the related VNF instance.
Identifier of the related VNF instance. See note 6.
NOTE 6: The NFVO shall set the value of the attribute by copying the value
from the associated GrantRequest.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
vnfLcmOpOccId:
description: >
Identifier of the related VNF lifecycle management operation
occurrence.
occurrence. See note 6.
NOTE 6: The NFVO shall set the value of the attribute by copying the value
from the associated GrantRequest.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
vimConnections:
description: >
......@@ -199,8 +205,9 @@ definitions:
This attribute shall only be supported when VNF-related Resource
Management in direct mode is applicable. In direct mode, this
parameter shall be absent if the VIM information was configured to
the VNFM in another way, present otherwise.
This interface allows to signal the use of multiple VIMs per VNF.
the VNFM in another way, present otherwise. See note 1.
NOTE 1: This interface allows to signal the use of multiple VIMs per VNF.
However, due to the partial support of this feature in the present
release, it is recommended in the present document that the number
of entries in the "vims" attribute in the Grant is not greater than
......@@ -229,8 +236,9 @@ definitions:
computeReservationId:
description: >
Information that identifies a reservation applicable to the compute
resource requirements of the corresponding grant request.
At least one of (computeReservationId, networkReservationId,
resource requirements of the corresponding grant request. See note 2.
NOTE 2: At least one of (computeReservationId, networkReservationId,
storageReservationId) shall be present when policy is
GRANT_RESERVE_SINGLE and an applicable reservation exists. None of
these shall be present otherwise.
......@@ -238,8 +246,9 @@ definitions:
networkReservationId:
description: >
Information that identifies a reservation applicable to the network
resource requirements of the corresponding grant request.
At least one of (computeReservationId, networkReservationId,
resource requirements of the corresponding grant request. See note 2.
NOTE 2: At least one of (computeReservationId, networkReservationId,
storageReservationId) shall be present when policy is
GRANT_RESERVE_SINGLE and an applicable reservation exists. None of
these shall be present otherwise.
......@@ -247,8 +256,9 @@ definitions:
storageReservationId:
description: >
Information that identifies a reservation applicable to the storage
resource requirements of the corresponding grant request.
At least one of (computeReservationId, networkReservationId,
resource requirements of the corresponding grant request. See note 2.
NOTE 2: At least one of (computeReservationId, networkReservationId,
storageReservationId) shall be present when policy is
GRANT_RESERVE_SINGLE and an applicable reservation exists. None of
these shall be present otherwise.
......@@ -256,7 +266,7 @@ definitions:
addResources:
description: >