Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
SOL002-SOL003
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
NFV - Network Functions Virtualisation
SOL002-SOL003
Commits
59e7c05a
Commit
59e7c05a
authored
3 years ago
by
Sana Zulfiqar
Browse files
Options
Downloads
Patches
Plain Diff
Added notes for SOL002 resources
parent
2fcc1d74
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!17
Merge 3.5.1-dev into master
Pipeline
#6896
passed
3 years ago
Stage: external
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml
+30
-14
30 additions, 14 deletions
src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml
with
30 additions
and
14 deletions
src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml
+
30
−
14
View file @
59e7c05a
...
...
@@ -150,6 +150,23 @@ definitions:
description
:
>
List of identifiers entries to be deleted from the 'vnfcInfoModifications" attribute array
to be used as "deleteIdList" as defined below this table.
The following provisions shall apply when modifying an attribute that is an array of objects of type
"VnfcInfo" by supplying an array of objects of type "VnfcInfoModifications".
Assumptions:
1) "oldList" is the "VnfcInfo" array to be modified and "newList" is the "VnfcInfoModifications"
array that contains the changes.
2) "oldEntry" is an entry in "oldList" and "newEntry" is an entry in "newList".
3) A "newEntry" has a "corresponding entry" if there exists an "oldEntry" that has the same content
of the "id" attribute as the "newEntry"; a "newEntry" has no corresponding entry if no such
"oldEntry" exists.
4) In any array of "VnfcInfo" resp. "VnfcInfoModifications" structures, the content of "id" is unique
(i.e. there are no two entries with the same content of "id").
Provisions:
1) For each "newEntry" in "newList" that has no corresponding entry in "oldList", the "oldList" array
shall be modified by adding that "newEntry".
2) For each "newEntry" in "newList" that has a corresponding "oldEntry" in "oldList",
the value of "oldEntry" shall be updated with the content of "newEntry" as specified
for the data type of "newEntry (refer to clause 5.5.3.24 for the data type "VnfcInfoModifications").
type
:
array
items
:
$ref
:
"
SOL002SOL003_def.yaml#/definitions/Identifier"
...
...
@@ -310,14 +327,14 @@ definitions:
This type represents a link port of an internal VL of a VNF. It shall comply with the provisions
defined in table 5.5.3.8 1.
NOTE 1:
Either cpInstanceId with cpInstanceType set to "EXT_CP" or any combination of cpInstanceId
NOTE 1:
Either cpInstanceId with cpInstanceType set to "EXT_CP" or any combination of cpInstanceId
with cpInstanceType set to "VNFC_CP" and vipCpInstanceId (i.e. one or both of them) shall be
present for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to "VNFC_CP"
and vipCpInstanceId are present, the two different CP instances share the linkport.
NOTE 2:
Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId
NOTE 2:
Annex A.4 of ETSI GS NFV-IFA 007 provides examples for configurations where both vipCpInstanceId
and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or
only vipCpInstanceId is present (UC6 and UC#6-b).
NOTE 3:
The value of "trunkResourceId" is scoped by the value of "vimConnectionId" in the "resourceHandle"
NOTE 3:
The value of "trunkResourceId" is scoped by the value of "vimConnectionId" in the "resourceHandle"
attribute.
type
:
object
required
:
...
...
@@ -869,7 +886,9 @@ definitions:
VnfcInfoModifications
:
description
:
>
This type represents modifications of an entry in an array of "VnfcInfo" objects.
It shall comply with the provisions defined in table 5.5.3.24-1.
* NOTE: The attribute "id" in this data type represents the same identifier as the attribute
"vnfcInstanceId" in other related data types in the present document. For reasons of backward
compatibility, this misalignment is not corrected.
type
:
object
required
:
-
id
...
...
@@ -878,22 +897,20 @@ definitions:
id
:
description
:
>
Identifier of the VNFC instance of which the information is to be modified.
The identifier references the "id" attribute in a "VnfcInfo" structure.
The attribute "id" in this data type represents the same identifier as the attribute
"vnfcInstanceId" in other related data types in the present document. For reasons of
backward compatibility, this misalignment is not corrected.
The identifier references the "id" attribute in a "VnfcInfo" structure. See note.
$ref
:
"
SOL002SOL003_def.yaml#/definitions/IdentifierInVnf"
vnfcConfigurableProperties
:
description
:
>
Changes of the configurable properties of the VNFC instance.
When this structure is part of a request, the modifications signalled in this attribute
shall be applied according to the rules of JSON Merge Patch (see IETF RFC 7396).
In addition, the provisions in clause 5.7 shall apply.
$ref
:
"
SOL002SOL003_def.yaml#/definitions/KeyValuePairs"
VnfcInfo
:
description
:
>
This type represents the information about a VNFC instance that is part of a VNF instance.
It shall comply with the
provisions defined in table 5.5.3.23-1
.
This type represents the information about a VNFC instance that is part of a VNF instance.
* NOTE: This allows to represent the error condition that a VNFC instance has lost its resources
.
type
:
object
required
:
-
id
...
...
@@ -912,9 +929,7 @@ definitions:
vnfcResourceInfoId
:
description
:
>
Identifier of the VnfcResourceInfo instance representing
the virtualised resources used by this VNFC instance.
Shall be present in case a corresponding VnfcResourceInfo instance exists.
This allows to represent the error condition that a VNFC instance has lost its resources.
the virtualised resources used by this VNFC instance. See note.
$ref
:
"
SOL002SOL003_def.yaml#/definitions/IdentifierInVnf"
vnfcState
:
description
:
>
...
...
@@ -936,7 +951,8 @@ definitions:
VNFC instance.
Configurable properties referred in this attribute are
declared in the VNFD.
This attribute can be modified with the PATCH method
This attribute can be modified with the PATCH method.
In addition, the provisions in clause 5.7 shall apply.
$ref
:
"
SOL002SOL003_def.yaml#/definitions/KeyValuePairs"
ModificationsTriggeredByVnfPkgChange
:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment