Skip to content
GitLab
Commit a5755264 authored by Muhammad Hamza's avatar Muhammad Hamza
Browse files

Implement differences between v3.5.1 and v3.6.1 for SOL003

parent b3814751
Pipeline #10233 passed with stage
in 0 seconds
Show whitespace changes
Inline Side-by-side
src/SOL003/APIVersion/APIVersion.yaml
View file @ a5755264
......@@ -20,8 +20,8 @@ info:
version: "1.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf
paths:
/vrqan/api_versions:
......
src/SOL003/VNFFaultManagement/VNFFaultManagement.yaml
View file @ a5755264
......@@ -16,11 +16,11 @@ info:
license:
name: ETSI Forge copyright notice
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
version: "1.4.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf
servers:
- url: http://127.0.0.1/vnffm/v1
......
src/SOL003/VNFFaultManagement/definitions/SOL003VNFFaultManagement_def.yaml
View file @ a5755264
......@@ -2,6 +2,27 @@ definitions:
Alarm:
description: >
The alarm data type encapsulates information about an alarm.
NOTE 1: For an alarm about upcoming impact due to NFVI operation and maintenance (i.e. the attribute
"faultType" has the value "NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE"), the attribute
"rootCauseFaultyResource" indicates a resource to be impacted. Further information on the upcoming
impact (e.g. group of impacted resources, time of impact) is provided in the attribute "faultDetails".
NOTE 2: When alarms are due to upcoming NFVI operation and maintenance (i.e. the attribute "faultType" has the
value "NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE"), the attribute "faultDetails" shall include
information about the anticipated time of the maintenance. See provisions under the present table.
If the attribute "faultType" has the value "NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE", the following provisions
apply for the values of the attribute "faultDetails" related to changes in the state of virtualised resources:
- One of the entries in the array shall provide information about the anticipated time of maintenance in the
following format: "anticipatedTime=$time", wherein "$time" shall be formatted as a "DateTime", as specified
in ETSI GS NFV-SOL 013 [8].
- One of the entries in the array shall provide identification information about the affinity/anti-affinity
group defined in the VNFD that is associated to the affected virtualised resource indicated by
"rootCauseFaultyResource" in the following format: "affinityOrAntiAffinityGroupId=$group", wherein
"$group" shall be equal to the "affinityOrAntiAffinityGroupId" value in the corresponding "VduProfile" (for a
VNFC/COMPUTE affected resource) or "VirtualLinkProfile" for a VL/NETWORK affected resource) in the
VNFD, which is mapped by the VNFM to the virtualised resource group identifier in the virtualised resource
change notification received by the VNFM from the VIM.
type: object
required:
- id
......@@ -26,7 +47,7 @@ definitions:
rootCauseFaultyResource:
description: >
The virtualised resources that are causing the VNF fault.
Shall be present if the alarm affects virtualised resources.
Shall be present if the alarm affects virtualised resources. See note 1.
$ref: "../../../definitions/SOL002SOL003VNFFaultManagement_def.yaml#/definitions/FaultyResourceInfo"
alarmRaisedTime:
description: >
......@@ -64,7 +85,7 @@ definitions:
$ref: "../../../definitions/SOL002SOL003VNFFaultManagement_def.yaml#/definitions/PerceivedSeverityType"
eventTime:
description: >
Time stamp indicating when the fault was observed.
Time stamp indicating when the fault was observed. See note 2.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/DateTime"
eventType:
description: >
......@@ -73,10 +94,20 @@ definitions:
faultType:
description: >
Additional information to clarify the type of the fault.
If the alarm is related to changes in the state of virtualised resources
due to NFVI operation and maintenance, this attribute shall be set to
"NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE".
type: string
probableCause:
description: >
Information about the probable cause of the fault.
If the attribute "faultType" has the value “NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGE”,
the permitted values are:
- "NFVI_COMPONENT_MAINTENANCE": Maintenance of NFVI components, e.g.
physical maintenance/repair, hypervisor software updates, etc.
- "NFVI_COMPONENT_EVACUATION": Evacuation of physical hosts.
- "NFVI_COMPONENT_OPTIMIZATION": Operation and management of NFVI resources, e.g.
to support energy efficiency or resource usage optimization.
type: string
isRootCause:
description: >
......@@ -92,7 +123,7 @@ definitions:
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
faultDetails:
description: >
Provides additional information about the fault.
Provides additional information about the fault. See notes 1 and 2.
type: array
items:
type: string
......
src/SOL003/VNFFaultManagementNotification/VNFFaultManagementNotification.yaml
View file @ a5755264
......@@ -16,11 +16,11 @@ info:
license:
name: ETSI Forge copyright notice
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
version: 1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1
version: 1.4.0-impl:etsi.org:ETSI_NFV_OpenAPI:1
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf
servers:
- url: http://127.0.0.1/callback/v1
......
src/SOL003/VNFIndicator/VNFIndicator.yaml
View file @ a5755264
......@@ -16,11 +16,11 @@ info:
license:
name: ETSI Forge copyright notice
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
version: "1.3.1-impl:etsi.org:ETSI_NFV_OpenAPI:1"
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf
servers:
- url: http://127.0.0.1/vnfind/v1
......
src/SOL003/VNFIndicatorNotification/VNFIndicatorNotification.yaml
View file @ a5755264
......@@ -16,11 +16,11 @@ info:
license:
name: ETSI Forge copyright notice
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
version: "1.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
version: "1.3.1-impl:etsi.org:ETSI_NFV_OpenAPI:1"
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf
servers:
- url: http://127.0.0.1/callback/v1
......
src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml
View file @ a5755264
......@@ -16,11 +16,11 @@ info:
license:
name: ETSI Forge copyright notice
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
version: "2.1.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
version: "2.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf
servers:
- url: http://127.0.0.1/vnflcm/v2
......
src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml
View file @ a5755264
......@@ -34,7 +34,14 @@ definitions:
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/IdentifierInVnfd"
extVirtualLinks:
description: >
Information about external VLs to connect the VNF to.
Information about external VLs to connect the VNF to, including configuration information
for the CPs via which the VNF instance can attach to this VL.
The following applies to the "ExtVirtualLinkData" information provided in this
request, together with the related overriding information provided in the
"Grant" structure (see clause 9.5.2.3): Even if the VNF is not instantiated in
fully scaled-out state, the API consumer shall provide enough CP configuration
records to allow connecting the VNF instance, fully scaled out in all scaling
aspects, to the external VLs
type: array
items:
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ExtVirtualLinkData"
......@@ -164,8 +171,17 @@ definitions:
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/IdentifierInVnfd"
extVirtualLinks:
description: >
Information about external VLs to connect the VNF to.
Entries in the list of external VLs that are unchanged need not be supplied as part of this request.
Information about external VLs to connect the VNF to, including configuration information
for the CPs via which the VNF instance can attach to this VL.
Entries in the list of external VLs that are unchanged need not be supplied as part of
this request.
The following applies to the "ExtVirtualLinkData" information provided in this
request, together with the related "ExtVirtualLinkInfo" information known to the
VNFM represented in the "VnfInstance" structure (see clause 5.5.2.2) and the related
overriding information provided in the "Grant" structure (see clause 9.5.2.3): Even if the VNF
is not in fully scaled-out state after changing the flavour, the API consumer shall provide
enough CP configuration records to allow connecting the VNF instance, fully scaled out in all scaling
aspects, to the external VLs.
type: array
items:
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ExtVirtualLinkData"
......@@ -316,8 +332,17 @@ definitions:
properties:
extVirtualLinks:
description: >
Information about external VLs to change (e.g. connect the VNF to).
Entries in the list of external VLs that are unchanged need not be supplied as part of this request.
Information about external VLs to change (e.g. connect the VNF to) including configuration
information for the CPs via which the VNF instance can attach to this VL.
Entries in the list of external VLs that are unchanged need not be supplied
as part of this request.
The following applies to the "ExtVirtualLinkData" information provided in this request,
together with the related "ExtVirtualLinkInfo" informationknown to the VNFM represented
in the "VnfInstance" structure (see clause 5.5.2.2) and the related overriding
information provided in the "Grant" structure (see clause 9.5.2.3): Even if the VNF
is not in fully scaled-out state, the API consumer shall provide enough CP
configuration records to allow connecting the VNF instance, fully scaled out in
all scaling aspects, to the external VLs.
type: array
items:
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ExtVirtualLinkData"
......@@ -364,8 +389,16 @@ definitions:
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
extVirtualLinks:
description: >
Information about external VLs to connect the VNF to. Entries in the list
that are unchanged need not be supplied as part of this request.
Information about external VLs to connect the VNF to, including configuration information for
the CPs via which the VNF instance can attach to this VL.
Entries in the list that are unchanged need not be supplied as part of this request.
The following applies to the "ExtVirtualLinkData" information provided in this request,
together with the related "ExtVirtualLinkInfo" information known to the VNFM represented
in the "VnfInstance" structure (see clause 5.5.2.2) and the related overriding information
provided in the "Grant" structure (see clause 9.5.2.3): Even if the VNF is not in fully
scaled-out state after the change of the VNF package, the API consumer shall provide enough
CP configuration records to allow connecting the VNF instance, fully scaled
out in all scaling aspects, to the external VLs.
type: array
items:
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ExtVirtualLinkData"
......@@ -839,7 +872,7 @@ definitions:
$ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/ExtVirtualLinkInfo"
extManagedVirtualLinkInfo:
description: >
Information about the externally-managed internal VLs of the VNF instance. See note 5 and note 6.
Information about the externally-managed internal VLs of the VNF instance. See notes 5 and 6.
type: array
items:
$ref: "#/definitions/ExtManagedVirtualLinkInfo"
......@@ -1000,6 +1033,12 @@ definitions:
supported for this VNF instance and is possible based on the current status of
this VNF instance resource (i.e., VNF instance is in INSTANTIATED state).
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Link"
changeCurrentVnfPkg:
description: >
Link to the "Change current VNF package task" resource, if the related
operation is possible based on the current status of this VNF instance resource
(i.e. VNF instance is in INSTANTIATED state).
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Link"
ExtManagedVirtualLinkInfo:
type: object
......@@ -1048,6 +1087,11 @@ definitions:
description: >
This type represents the information that allows addressing a virtualised
resource that is used by a VNF instance.
Note: If only the value or the presence of this attribute is changed in the "VirtualStorageResourceInfo"
structure by an LCM operation occurrence, this does not represent a change that requires
including a related "AffectedVirtualStorage" structure in the VNF LCM operation occurrence
notifications or the "VnfLcmOpOcc" structure related to this LCM operation occurrence.
type: object
required:
- id
......@@ -1102,6 +1146,10 @@ definitions:
CP if it is connected directly to an external VL.
NOTE 3: The information can be omitted because it is already available as part of the
external CP information.
NOTE 4: If only the value or the presence of this attribute is changed in the "VnfcResourceInfo"
structure by an LCM operation occurrence, this does not represent a change that requires
including a related "AffectedVnfc" structure in the VNF LCM operation occurrence notifications
or the "VnfLcmOpOcc" structure related to this LCM operation occurrence.
type: object
required:
- id
......@@ -1120,7 +1168,7 @@ definitions:
description: >
Identifier of the VNFD.
Shall be present in case the value differs from the vnfdId attribute of the VnfInstance (e.g. during a "Change
current VNF package" operation or due to its final failure).
current VNF package" operation or due to its final failure). See note 4.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
computeResource:
description: >
......@@ -1420,6 +1468,11 @@ definitions:
description: >
This type represents the information that allows addressing a virtualised
resource that is used by an internal VL instance in a VNF instance.
Note: If only the value or the presence of this attribute is changed in the "VnfVirtualLinkResourceInfo"
structure by an LCM operation occurrence, this does not represent a change that requires including
a related "AffectedVirtualLink" structure in the VNF LCM operation occurrence notifications or the
"VnfLcmOpOcc" structure related to this LCM operation occurrence.
type: object
required:
- id
......@@ -1438,7 +1491,7 @@ definitions:
description: >
Identifier of the VNFD.
Shall be present in case the value differs from the vnfdId attribute of the VnfInstance (e.g. during a "Change
current VNF package" operation or due to its final failure).
current VNF package" operation or due to its final failure). See note.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier"
networkResource:
description: >
......@@ -1929,6 +1982,7 @@ definitions:
Signals the type of change.
Permitted values:
- ADDED
- MODIFIED
- REMOVED
type: string
enum:
......@@ -2003,6 +2057,7 @@ definitions:
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".
Note 3: Not more than one of changedInfo and modificationsTriggeredByVnfPkgChange shall be present.
type: object
required:
- id
......@@ -2116,7 +2171,7 @@ definitions:
the "operation" attribute is not equal to "CHANGE_VNFPKG", the
"verbosity" attribute is set to "FULL" and the operation has performed
any changes to VNF instance information, including VNF configurable
properties. Shall be absent otherwise.
properties. Shall be absent otherwise. See note 3.
$ref: "#/definitions/VnfInfoModifications"
affectedVipCps:
......@@ -2148,8 +2203,8 @@ definitions:
description: >
Information about performed changes of "VnfInstance" attributes triggered by changing the current VNF package.
Shall be present if the "notificationStatus" is set to "RESULT", the "operation" attribute is equal to
"CHANGE_VNFPKG", the "verbosity" attribute is set to "FULL" and the operation has performed any changes to VNF
instance information, including VNF configurable properties. Shall be absent otherwise.
"CHANGE_VNFPKG", the "verbosity" attribute is set to "FULL" and the operation has performed any changes to
"VnfInstance" attributes. Shall be absent otherwise. See note 3.
$ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/ModificationsTriggeredByVnfPkgChange"
error:
description: >
......
src/SOL003/VNFLifecycleManagementNotification/VNFLifecycleManagementNotification.yaml
View file @ a5755264
......@@ -16,11 +16,11 @@ info:
license:
name: "ETSI Forge copyright notice"
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
version: "2.1.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
version: "2.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf
servers:
- url: http://127.0.0.1/callback/v2
......
src/SOL003/VNFLifecycleOperationGranting/VNFLifecycleOperationGranting.yaml
View file @ a5755264
......@@ -16,11 +16,11 @@ info:
license:
name: ETSI Forge copyright notice
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
version: "1.5.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
version: "1.6.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf
servers:
- url: http://127.0.0.1/grant/v1
......
src/SOL003/VNFLifecycleOperationGranting/definitions/SOL003VNFLifecycleOperationGranting_def.yaml
View file @ a5755264
......@@ -13,17 +13,23 @@ definitions:
during the runtime of the LCM operation. This means, the resource can be allocated and consumed after the
"start" notification for the LCM operation is sent by the VNFM, and the resource will be released before the
"result" notification of the VNF LCM operation is sent by the VNFM.
NOTE 4: The affinity/anti-affinity rules defined in the VNFD and the placement constraints in the GrantVnfLifecycleOperation
as defined in this clause should be conflict-free. In case of conflicts, the placement constraints in the
GrantVnfLifecycleOperation shall take precedence.
NOTE 4: For the affinity/anti-affinity rules defined in the VNFD and the placement constraints in the GrantVnfLifecycleOperation
as defined in this clause, the following applies: Assuming unlimited capacity, the combination of all the
aforementioned rules shall be satisfiable by at least one possible placement of the new resources, with the
exception that some of the rules with fallbackBestEffort may be unsatisfiable due to the actual placement of
existing resources. In this case, rules with fallbackBestEffort are allowed to be violated only in relation
to the placement of existing resources.
NOTE 5: Passing constraints allows the VNFM or the lifecycle management scripts to influence resource placement decisions
by the NFVO to ensure VNF properties such as performance or fault tolerance.
NOTE 6: If fallbackBestEffort is present in placement constraints and set to "true", the NFVO shall process the Affinity/AntiAffinity
constraint in a best effort manner, in which case, if specified resources cannot be allocated based on specified placement
constraint, the NFVO looks for an alternate best effort placement for the specified resources to be granted.
In the best effort anti-affinity case, the resources are expected to be spread optimally over all available instances of scope
(e.g. zones), and in the best effort affinity case, they are expected to be distributed optimally over fewer possible instances
of scope.
NOTE 6: If fallbackBestEffort is present and set to "true" in one or more placement constraints and, the NFVO
cannot find a resource placement that satisfies all of these due to limited capacity, the NFVO shall process
each such affinity/anti-affinity constraint in a best effort manner, in which case, if specified resources
cannot be allocated based on the specified placement constraint, the NFVO shall look for an alternate best
effort placement for the specified resources to be granted. In the best effort anti-affinity case, the
resources are expected to be spread optimally over all available instances of scope (e.g. zones), and in
the best effort affinity case, they are expected to be distributed optimally over as few instances of scope as
possible. Being able to satisfy a "best-effort" constraint in a best effort manner only, as defined above,
shall not lead to rejecting the grant.
type: object
required:
- vnfInstanceId
......@@ -164,39 +170,45 @@ definitions:
description: >
This type represents a grant.
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 1.
NOTE 1: This interface allows to signal the use of multiple VIMs per VNF. The specification
for managing the VNF internal VL requirements across multiple VIMs is supported via
"externally-managed internal VLs" and "multi-site connectivity services".
NOTE 2: Void.
NOTE 3: The Grant response allows the NFVO to pass to the VNFM VIM assets
related to the VNF package that is identified by the vnfdId attribute
in the corresponding Grant request. The NFVO may send in each Grant
response the full set of VIM assets related to the VNF package defined
by the vnfdId in the related Grant request, but shall send this information
if the vnfdId in the related Grant request differs from the vnfdId passed
in the previous Grant request, or if the Grant response is related to an
InstantiateVnf operation. The set of VIM assets shall not change between
subsequent Grant responses if the vnfdId has not changed. During each LCM
operation occurrence, the VIM assets that relate to the VNF package identified
by the current value of the vnfdId attribute in the "VnfInstance" structure
shall be used by the VNFM for newly created resources. If the VNF package
identifier of the VNF instance has been updated, VIM assets that relate to
the previously-used VNF package(s), and that were communicated in previous
Grant responses, apply to existing resources.
NOTE 4: The indication of externally-managed internal VLs is needed in case networks
have been pre-configured for use with certain VNFs, for instance to ensure that
these networks have certain properties such as security or acceleration features,
or to address particular network topologies. The present document assumes that
externally-managed internal VLs are managed by the NFVO and created towards the VIM.
NOTE 5: For any VNF lifecycle management operation request that allows to pass "extVirtualLinks"
and/or "extManagedVirtualLinks" parameters, such as InstantiateVnf, ChangeVnfFlavour,
ChangeExtVnfConnectivity or ChangeCurrentVnfPackage, the NFVO may provide the "extVirtualLinks"
and/or "extManagedVirtualLinks" attributes in the Grant to override the values passed
in these parameters previously in the associated VNF lifecycle management request, if
the lifecycle management request has originated from the NFVO itself. The NFVO shall
not provide the "extVirtualLinks" and/or "extManagedVirtualLinks" attributes in the
Grant otherwise.
NOTE 3: The Grant response allows the NFVO to pass to the VNFM VIM assets related to the VNF
package that is identified in the corresponding Grant request. Because only the operations
InstantiateVnf, ChangeCurrentVnfPkg and the update of the vnfdId by PATCH can imply changes
in the set of VIM assets, the NFVO shall not change this set in any other case. To signal the
set of VIM assets, the following applies:
a) If the current LCM operation is InstantiateVnf, the NFVO shall send in the Grant response
the full set of VIM assets related to the VNF package defined by the vnfdId in the related
Grant request.
b) If the current LCM operation is ChangeCurrentVnfPkg, the NFVO shall send in the
Grant response the full set of VIM assets related to the VNF package defined by the destVnfdId
in the related Grant request.
c) For any other operation: If the set of VIM assets has changed since the end of the previous
granted operation because a PATCH operation has changed the vnfdId between the previous granted
operation and the operation to which the current granting exchange relates, the NFVO shall send
in the Grant response the full set of VIM assets related to the VNF package defined by the vnfdId
in the related Grant request. Otherwise, the NFVO shall either send in the Grant response the full
set of VIM assets related to the VNF package defined by the vnfdId in the related Grant request, or
shall not send any VIM assets at all.
During each LCM operation occurrence other than a "ChangeCurrentVnfPkg" operation,
the VIM assets that relate to the VNF package identified by the current value of
the vnfdId attribute in the "VnfInstance" structure shall be used by the
VNFM for newly created resources and updated resources.
NOTE 4: The indication of externally-managed internal VLs is needed in case networks have been
pre-configured for use with certain VNFs, for instance to ensure that these networks have
certain properties such as security or acceleration features, or to address particular network
topologies (e.g., multi-site connectivity). The present document assumes that externally-managed
internal VLs are managed by the NFVO and created towards the VIM and WIM.
NOTE 5: For any VNF lifecycle management operation request that allows to pass "extVirtualLinks" and/or
"extManagedVirtualLinks" parameters, such as InstantiateVnf, ChangeVnfFlavour, ChangeExtVnfConnectivity or
ChangeCurrentVnfPackage, the NFVO may provide the "extVirtualLinks" and/or "extManagedVirtualLinks" attributes
in the Grant to override the values passed in these parameters previously in the associated VNF lifecycle
management request, if the lifecycle management request has originated from the NFVO itself. The NFVO shall
not provide the "extVirtualLinks" and/or "extManagedVirtualLinks" attributes in the Grant in case the LCM
request did not originate from the NFVO itself or the granted LCM operation request does not allow to pass
these parameters.
NOTE 6: The NFVO shall set the value of the attribute by copying the value from the associated
GrantRequest.
NOTE 7: In case of granting an InstantiateVnf request that has originated from the NFVO and that
......@@ -205,6 +217,10 @@ definitions:
and that did not contain the "extManagedVirtualLinks" attribute, this attribute shall be
set by the NFVO if there is the need to provide information about externally-managed virtual
links.
NOTE 8: The resulting "extVirtualLinks" or "extManagedVirtualLinks" information is calculated as follows:
In a first step, the information passed in the related LCM operation is applied to the baseline
information known from earlier LCM operation executions. In a second step, the information passed
in the Grant is applied to the information resulting from the first step.
type: object
required:
- id
......@@ -326,7 +342,7 @@ definitions:
$ref: "#/definitions/VimSnapshotResource"
extVirtualLinks:
description: >
Information about external VLs to connect the VNF to. See notes 5 and 7. If this attribute
Information about external VLs to connect the VNF to. See notes 5, 7 and 8. If this attribute
is present according to note 5 or note 7, it need not contain those entries that are unchanged
compared to the entries that were passed in the LCM operation which is related to this granting exchange.
type: array
......@@ -334,7 +350,7 @@ definitions:
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/ExtVirtualLinkData"
extManagedVirtualLinks:
description: >
Information about internal VLs that are managed by other entities than the VNFM. See notes 4, 5 and 7.
Information about internal VLs that are managed by other entities than the VNFM. See notes 4, 5, 7 and 8.
type: array
items:
$ref: "../../VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml#/definitions/ExtManagedVirtualLinkData"
......@@ -621,9 +637,10 @@ definitions:
fallbackBestEffort:
description: >
Indication if the constraint is handled with fall back best effort. Default value is “false”.
If set to true, the Affinity/Anti_Affinity placement constraint need not be fully satisfied,
i.e. if the allocation cannot be honoured with the placement constraint, the request is
processed in a best effort manner.
If set to true, the Affinity/Anti_Affinity placement constraint need not be fully satisfied
due to capacity constraints and/or due to the actual placement of existing resources, i.e.
if resource placement cannot honour the placement constraint, the request is processed in a
best effort manner.
$ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Boolean"
VimConstraint:
......
src/SOL003/VNFPackageManagement/VNFPackageManagement.yaml
View file @ a5755264
......@@ -16,11 +16,11 @@ info:
license:
name: ETSI Forge copyright notice
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
version: "2.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
version: "2.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf
servers:
- url: http://127.0.0.1/vnfpkgm/v2
......
src/SOL003/VNFPackageManagementNotification/VNFPackageManagementNotification.yaml
View file @ a5755264
......@@ -16,11 +16,11 @@ info:
license:
name: ETSI Forge copyright notice
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
version: 2.2.0-impl:etsi.org:ETSI_NFV_OpenAPI:1
version: 2.3.0-impl:etsi.org:ETSI_NFV_OpenAPI:1
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf
servers:
- url: http://127.0.0.1/callback/v2
......
src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml
View file @ a5755264
......@@ -19,8 +19,8 @@ info:
version: 2.1.0-impl:etsi.org:ETSI_NFV_OpenAPI:1
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.06.01_60/gs_NFV-SOL003v030601p.pdf
servers:
- url: http://127.0.0.1/vnfpm/v2
......
src/SOL003/VNFPerformanceManagementNotification/VNFPerformanceManagementNotification.yaml
View file @ a5755264
......@@ -19,8 +19,8 @@ info:
version: 2.1.0-impl:etsi.org:ETSI_NFV_OpenAPI:1
externalDocs:
description: ETSI GS NFV-SOL 003 V3.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.05.01_60/gs_NFV-SOL003v030501p.pdf
description: ETSI GS NFV-SOL 003 V3.6.1