Skip to content
GitLab
Commit fb1e27cf authored by piscione's avatar piscione
Browse files

SOL005_71 to SOL005_80

parent 34421873
Hide whitespace changes
Inline Side-by-side
src/SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml
View file @ fb1e27cf
......@@ -41,8 +41,10 @@ definitions:
HealNsData:
description: >
This type represents the information used to heal a NS.
This type represents the information used to heal a NS.
It shall comply with the provisions defined in Table 6.5.3.43-1.
NOTE: Either the actionsHealing or healScript attribute shall be present, not both attributes.
type: object
required:
- degreeHealing
......@@ -76,7 +78,7 @@ definitions:
particular order (e.g. as a script). The actionsHealing
attribute can be used to provide a specific script whose
content and actions might only be possible to be
derived during runtime.
derived during runtime. See note.
type: array
items:
$ref: "../../definitions/SOL005_def.yaml#/definitions/String"
......@@ -86,7 +88,7 @@ definitions:
to execute dedicated healing actions in a particular
order. The healScript, since it refers to a script in the
NSD, can be used to execute healing actions which
are defined during NS design time.
are defined during NS design time. See note.
$ref: "#/definitions/IdentifierInNsd"
additionalParamsforNs:
description: >
......@@ -756,8 +758,16 @@ definitions:
NsVirtualLinkInfo:
description: >
This type specifies the information about an NS VL instance.
It shall comply with the provisions defined in
Table 6.5.3.53-1
It shall comply with the provisions defined in Table 6.5.3.53-1.
NOTE: As an NS can include NFs deployed in NFVI PoPs under the control
of several different VIMs, therefore deploying an NS VL can involve
several VIMs, each allocating different virtualised network resources,
as well as WIMs handling the connectivity in between the NFVI-PoPs in
the form of multi-site connectivity services.
When this NsVirtualLink is provided as an ExtVirtualLink as input
of a VNF LCM operation, the id of the ExtVirtualLink shall be the same
as the corresponding NsVirtualLink.
type: object
required:
- id
......@@ -780,11 +790,7 @@ definitions:
description: >
Identifier(s) of the virtualised network resource(s) and/or multi-site connectivity service(s)
realizing the VL instance.
As an NS can include NFs deployed in NFVI PoPs under the control of several different VIMs, therefore deploying
an NS VL can involve several VIMs, each allocating different virtualised network resources, as well as WIMs
handling the connectivity in between the NFVI-PoPs in the form of multi-site connectivity services. When this
NsVirtualLink is provided as an ExtVirtualLink as input of a VNF LCM operation, the id of the ExtVirtualLink
shall be the same as the corresponding NsVirtualLink.
See note.
type: array
items:
$ref: "../../definitions/SOL005_def.yaml#/definitions/ResourceHandle"
......@@ -3048,28 +3054,30 @@ definitions:
This type contains information used to create or modify NFP instance parameters
for the update of an existing VNFFG instance.
It shall comply with the provisions defined in Table 6.5.3.38-1.
NOTE 1: It shall be present for modified NFPs and shall be absent for the new NFP.
NOTE 2: It shall be present for the new NFP, and it may be present otherwise.
NOTE 3: At least a CP or an nfpRule shall be present.
NOTE 4: When multiple identifiers are included, the position of the identifier
in the cpGroup value specifies the position of the group in the path.
type: object
properties:
nfpInfoId:
description: >
Identifier of the NFP to be modified. It shall be present
for modified NFPs and shall be absent for the new NFP.
It shall be present for modified NFPs and shall be absent
for the new NFP.
See note 1.
$ref: "#/definitions/IdentifierInNs"
nfpName:
description: >
Human readable name for the NFP. It shall be present
for the new NFP, and it may be present otherwise.
It shall be present for the new NFP, and it may be
present otherwise.
See note 2.
type: string
description:
description: >
Human readable description for the NFP. It shall be
present for the new NFP, and it may be present otherwise.
It shall be present for the new NFP, and it may be
present otherwise.
See note 2.
type: string
cpGroup:
description: >
......@@ -3077,10 +3085,7 @@ definitions:
Cardinality can be 0 if only updated or newly created
NFP classification and selection rule which applied to an
existing NFP is provided.
At least a CP or an nfpRule shall be present.
When multiple identifiers are included, the position of
the identifier in the cpGroup value specifies the position
of the group in the path.
See note 3 and 4.
type: array
items:
$ref: "#/definitions/CpGroupInfo"
......@@ -3147,18 +3152,18 @@ definitions:
vlanTag:
description: >
Indicates a VLAN identifier in an IEEE 802.1Q-2018
tag [6] Multiple tags can be included for QinQ stacking. See note.
tag Multiple tags can be included for QinQ stacking. See note.
type: array
items:
$ref: "../../definitions/SOL005_def.yaml#/definitions/String"
protocol:
description: >
Indicates the L4 protocol, For IPv4 [7] this
Indicates the L4 protocol, For IPv4 this
corresponds to the field called "Protocol" to identify
the next level protocol. For IPv6 [28] this
the next level protocol. For IPv6 this
corresponds to the field is called the "Next Header" field.
Permitted values: Any keyword defined in the IANA
protocol registry [1], e.g.:
protocol registry, e.g.:
TCP
UDP
ICMP
......@@ -3171,10 +3176,10 @@ definitions:
- ICMP
dscp:
description: >
For IPv4 [7] a string of "0" and "1" digits that
For IPv4 a string of "0" and "1" digits that
corresponds to the 6-bit Differentiated Services
Code Point (DSCP) field of the IP header.
For IPv6 [28] a string of "0" and "1" digits that
For IPv6 a string of "0" and "1" digits that
corresponds to the 6 differentiated services bits of
the traffic class header field.
......@@ -4053,6 +4058,15 @@ definitions:
ScaleNsData:
description: >
This type represents the information to scale a NS.
NOTE 1: No more than two attributes between vnfInstanceToBeAdded,
vnfInstanceToBeRemoved, scaleNsByStepsData and scaleNsToLevelData shall be present.
In case of two, the attributes shall be vnfInstanceToBeAdded and vnfInstanceToBeRemoved.
NOTE 2: The DF of the VNF instance shall match the VNF DF present in the associated VNF
Profile of the new NS flavour.
NOTE 3: This functionality is the same as the one provided by the Update NS operation when
the AddVnf update type is selected (see clause 7.3.5).
NOTE 4: This functionality is the same as the one provided by the Update NS operation when
the RemoveVnf update type is selected (see clause 7.3.5).
type: object
properties:
vnfInstanceToBeAdded:
......@@ -4061,6 +4075,7 @@ definitions:
instance as part of the scaling operation. If
needed, the VNF Profile to be used for this VNF
instance may also be provided.
See note 1, note 2 and note 3.
type: array
items:
$ref: "#/definitions/VnfInstanceData"
......@@ -4068,6 +4083,7 @@ definitions:
description: >
The VNF instance to be removed from the NS
instance as part of the scaling operation.
See note 1 and note 4.
type: array
items:
$ref: "../../definitions/SOL005_def.yaml#/definitions/Identifier"
......@@ -4075,10 +4091,12 @@ definitions:
description: >
The information used to scale an NS instance by
one or more scaling steps.
See note 1.
$ref: "#/definitions/ScaleNsByStepsData"
scaleNsToLevelData:
description: >
The information used to scale an NS instance to a target size.
See note 1.
$ref: "#/definitions/ScaleNsToLevelData"
additionalParamsForNs:
description: >
......@@ -4120,6 +4138,14 @@ definitions:
description: >
This type represents defines the information to scale a VNF instance
to a given level, or to scale a VNF instance by steps.
NOTE 1: ETSI GS NFV-IFA 010 (available at https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/010/03.02.01_60/gs_NFV-IFA010v030201p.pdf)
specifies that the lifecycle management operations that expandor contract a VNF instance
include scale in, scale out, scale up and scale down. Vertical scaling (scale up, scale down)
is not supported in the present document.
NOTE 2: Either scaletoLevelData or scaleByStepData but not both shall be present. The scaleByStepData
is used for scale out/in type of scaling, and the scaleToLevelData is used for scale to instantiation/scale
level type of scaling.
type: object
required:
- vnfInstanceId
......@@ -4143,7 +4169,7 @@ definitions:
- SCALE_TO_INSTANTIATION_LEVEL
- SCALE_TO_SCALE_LEVEL(S)
The set of types actually supported depends on the
capabilities of the VNF being managed.
capabilities of the VNF being managed. See note 1.
type: string
enum:
- SCALE_OUT
......@@ -4156,7 +4182,7 @@ definitions:
$ref: "#/definitions/ScaleToLevelData"
scaleByStepData:
description: >
The information used for scaling by steps.
The information used for scaling by steps. See note 2.
$ref: "#/definitions/ScaleByStepData"
ScaleNsByStepsData:
......@@ -4196,6 +4222,7 @@ definitions:
an NS instantiation level or as a list of NS scale levels, one per NS scaling aspect, of the current DF. The NS
instantiation levels, the NS scaling aspects and their corresponding NS scale levels applicable to the NS instance are
declared in the NSD.
NOTE: Either nsInstantiationLevel or nsScaleInfo, but not both, shall be present.
type: object
oneOf:
- required:
......@@ -4206,12 +4233,12 @@ definitions:
nsInstantiationLevel:
description: >
Identifier of the target NS instantiation level of the
current DF to which the NS instance is requested to be scaled.
current DF to which the NS instance is requested to be scaled. See note.
$ref: "#/definitions/IdentifierInNsd"
nsScaleInfo:
description: >
For each NS scaling aspect of the current DF, defines
the target NS scale level to which the NS instance is to be scaled.
the target NS scale level to which the NS instance is to be scaled. See note.
type: array
items:
$ref: "#/definitions/NsScaleInfo"
......@@ -4221,7 +4248,8 @@ definitions:
This type describes the information used to scale a VNF instance to a target size. The target size is either expressed as
an instantiation level of that DF as defined in the VNFD, or given as a list of scale levels, one per scaling aspect of that
DF. Instantiation levels and scaling aspects are declared in the VNFD. The NFVO shall then invoke the
ScaleVnfToLevel operation towards the appropriate VNFM..
ScaleVnfToLevel operation towards the appropriate VNFM.
NOTE: Either the instantiationLevelId attribute or the scaleInfo attribute shall be included.
type: object
anyOf:
- required:
......@@ -4232,13 +4260,13 @@ definitions:
vnfInstantiationLevelId:
description: >
Identifier of the target instantiation level of the current
deployment flavor to which the VNF is requested to be scaled.
deployment flavor to which the VNF is requested to be scaled. See note.
$ref: "../../definitions/SOL005_def.yaml#/definitions/IdentifierInVnfd"
vnfScaleInfo:
description: >
For each scaling aspect of the current deployment
flavor, indicates the target scale level to which the VNF
is to be scaled.
is to be scaled. See note.
type: array
items:
$ref: "#/definitions/VnfScaleInfo"
......@@ -4253,6 +4281,7 @@ definitions:
This type describes the information to scale a VNF instance by steps.
The NFVO shall then invoke the Scale VNF
operation towards the appropriate VNFM.
NOTE: A scaling step is the smallest unit by which a VNF instance can be scaled w.r.t a particular scaling aspect.
type: object
required:
- aspectId
......@@ -4269,7 +4298,7 @@ definitions:
The VNF provider defines in the VNFD whether or not a
particular VNF supports performing more than one step
at a time. Such a property in the VNFD applies for all
instances of a particular VNF.
instances of a particular VNF. See note.
type: integer
default: 1
additionalParams:
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment