Newer
Older
25001
25002
25003
25004
25005
25006
25007
25008
25009
25010
25011
25012
25013
25014
25015
25016
25017
25018
25019
25020
25021
25022
25023
25024
25025
25026
25027
25028
25029
25030
25031
25032
25033
25034
25035
25036
25037
25038
25039
25040
25041
25042
25043
25044
25045
25046
25047
25048
25049
25050
25051
25052
25053
25054
25055
25056
25057
25058
25059
25060
25061
25062
25063
25064
25065
25066
25067
25068
25069
25070
25071
25072
25073
25074
25075
25076
25077
25078
25079
25080
25081
25082
25083
25084
25085
25086
25087
25088
25089
25090
25091
25092
25093
25094
25095
25096
25097
25098
25099
25100
25101
25102
25103
25104
25105
25106
25107
25108
25109
25110
25111
25112
25113
25114
25115
25116
25117
25118
25119
25120
25121
25122
25123
25124
25125
25126
25127
25128
25129
25130
25131
25132
25133
25134
25135
25136
25137
25138
25139
25140
25141
25142
25143
25144
25145
25146
25147
25148
25149
25150
25151
25152
25153
25154
25155
25156
25157
25158
25159
25160
25161
25162
25163
25164
25165
25166
25167
25168
25169
25170
25171
25172
25173
25174
25175
25176
25177
25178
25179
25180
25181
25182
25183
25184
25185
25186
25187
25188
25189
25190
25191
25192
25193
25194
25195
25196
25197
25198
25199
25200
25201
25202
25203
25204
25205
25206
25207
25208
25209
25210
25211
25212
25213
25214
25215
25216
25217
25218
25219
25220
25221
25222
25223
25224
25225
25226
25227
25228
25229
25230
25231
25232
25233
25234
25235
25236
25237
25238
25239
25240
25241
25242
25243
25244
25245
25246
25247
25248
25249
25250
25251
25252
25253
25254
25255
25256
25257
25258
25259
25260
25261
25262
25263
25264
25265
25266
25267
25268
25269
25270
25271
25272
25273
25274
25275
25276
25277
25278
25279
25280
25281
25282
25283
25284
25285
25286
25287
25288
25289
25290
25291
25292
25293
25294
25295
25296
25297
25298
25299
25300
25301
25302
25303
25304
25305
25306
25307
25308
25309
25310
25311
25312
25313
25314
25315
25316
25317
25318
25319
25320
25321
25322
25323
25324
25325
25326
25327
25328
25329
25330
25331
25332
25333
25334
25335
25336
25337
25338
25339
25340
25341
25342
25343
25344
25345
25346
25347
25348
25349
25350
25351
25352
25353
25354
25355
25356
25357
25358
25359
25360
25361
25362
25363
25364
25365
25366
25367
25368
25369
25370
25371
25372
25373
25374
25375
25376
25377
25378
25379
25380
25381
25382
25383
25384
25385
25386
25387
25388
25389
25390
25391
25392
25393
25394
25395
25396
25397
25398
25399
25400
25401
25402
25403
25404
25405
25406
25407
25408
25409
25410
25411
25412
25413
25414
25415
25416
25417
25418
25419
25420
25421
25422
25423
25424
25425
25426
25427
25428
25429
25430
25431
25432
25433
25434
25435
25436
25437
25438
25439
25440
25441
25442
25443
25444
25445
25446
25447
25448
25449
25450
25451
25452
25453
25454
25455
25456
25457
25458
25459
25460
25461
25462
25463
25464
25465
25466
25467
25468
25469
25470
25471
25472
25473
25474
25475
25476
25477
25478
25479
25480
25481
25482
25483
25484
25485
25486
25487
25488
25489
25490
25491
25492
25493
25494
25495
25496
25497
25498
25499
25500
25501
25502
25503
25504
25505
25506
25507
25508
25509
25510
25511
25512
25513
25514
25515
25516
25517
25518
25519
25520
25521
25522
25523
25524
25525
25526
25527
25528
25529
25530
25531
25532
25533
25534
25535
25536
25537
25538
25539
25540
25541
25542
25543
25544
25545
25546
25547
25548
25549
25550
25551
25552
25553
25554
25555
25556
25557
25558
25559
25560
25561
25562
25563
25564
25565
25566
25567
25568
25569
25570
25571
25572
25573
25574
25575
25576
25577
25578
25579
25580
25581
25582
25583
25584
25585
25586
25587
25588
25589
25590
25591
25592
25593
25594
25595
25596
25597
25598
25599
25600
25601
25602
25603
25604
25605
25606
25607
25608
25609
25610
25611
25612
25613
25614
25615
25616
25617
25618
25619
25620
25621
25622
25623
25624
25625
25626
25627
25628
25629
25630
25631
25632
25633
25634
25635
25636
25637
25638
25639
25640
25641
25642
25643
25644
25645
25646
25647
25648
25649
25650
25651
25652
25653
25654
25655
25656
25657
25658
25659
25660
25661
25662
25663
25664
25665
25666
25667
25668
25669
25670
25671
25672
25673
25674
25675
25676
25677
25678
25679
25680
25681
25682
25683
25684
25685
25686
25687
25688
25689
25690
25691
25692
25693
25694
25695
25696
25697
25698
25699
25700
25701
25702
25703
25704
25705
25706
25707
25708
25709
25710
25711
25712
25713
25714
25715
25716
25717
25718
25719
25720
25721
25722
25723
25724
25725
25726
25727
25728
25729
25730
25731
25732
25733
25734
25735
25736
25737
25738
25739
25740
25741
25742
25743
25744
25745
25746
25747
25748
25749
25750
25751
25752
25753
25754
25755
25756
25757
25758
25759
25760
25761
25762
25763
25764
25765
25766
25767
25768
25769
25770
25771
25772
25773
25774
25775
25776
25777
25778
25779
25780
25781
25782
25783
25784
25785
25786
25787
25788
25789
25790
25791
25792
25793
25794
25795
25796
25797
25798
25799
25800
25801
25802
25803
25804
25805
25806
25807
25808
25809
25810
25811
25812
25813
25814
25815
25816
25817
25818
25819
25820
25821
25822
25823
25824
25825
25826
25827
25828
25829
25830
25831
25832
25833
25834
25835
25836
25837
25838
25839
25840
25841
25842
25843
25844
25845
25846
25847
25848
25849
25850
25851
25852
25853
25854
25855
25856
25857
25858
25859
25860
25861
25862
25863
25864
25865
25866
25867
25868
25869
25870
25871
25872
25873
25874
25875
25876
25877
25878
25879
25880
25881
25882
25883
25884
25885
25886
25887
25888
25889
25890
25891
25892
25893
25894
25895
25896
25897
25898
25899
25900
25901
25902
25903
25904
25905
25906
25907
25908
25909
25910
25911
25912
25913
25914
25915
25916
25917
25918
25919
25920
25921
25922
25923
25924
25925
25926
25927
25928
25929
25930
25931
25932
25933
25934
25935
25936
25937
25938
25939
25940
25941
25942
25943
25944
25945
25946
25947
25948
25949
25950
25951
25952
25953
25954
25955
25956
25957
25958
25959
25960
25961
25962
25963
25964
25965
25966
25967
25968
25969
25970
25971
25972
25973
25974
25975
25976
25977
25978
25979
25980
25981
25982
25983
25984
25985
25986
25987
25988
25989
25990
25991
25992
25993
25994
25995
25996
25997
25998
25999
26000
understanding of the design. For a full description, see IETF RFC
7807 [19].
type: object
required:
- status
- detail
properties:
type:
description: >
A URI reference according to IETF RFC 3986 [5] that identifies
the problem type. It is encouraged that the URI provides
human-readable documentation for the problem (e.g. using HTML)
when dereferenced. When this member is not present, its value
is assumed to be "about:blank".
type: string
format: URI
title:
description: >
A short, human-readable summary of the problem type. It should
not change from occurrence to occurrence of the problem,
except for purposes of localization. If type is given and
other than "about:blank", this attribute shall also be
provided. A short, human-readable summary of the problem
type. It SHOULD NOT change from occurrence to occurrence of
the problem, except for purposes of localization (e.g., using
proactive content negotiation; see [RFC7231], Section 3.4).
type: string
status:
description: >
The HTTP status code for this occurrence of the problem. The
HTTP status code ([RFC7231], Section 6) generated by the
origin server for this occurrence of the problem.
type: integer
detail:
description: >
A human-readable explanation specific to this occurrence of
the problem.
type: string
instance:
description: >
A URI reference that identifies the specific occurrence of the
problem. It may yield further information if dereferenced.
type: string
format: URI
'406':
description: >
Not Acceptable
If the "Accept" HTTP header does not contain at least one name of a
content type that is acceptable to the API producer, the API
producer shall respond with this response code. The "ProblemDetails"
structure may be omitted in that case.
headers:
Content-Type:
description: The MIME type of the body of the response.
type: string
maximum: 1
minimum: 1
schema:
description: >
The definition of the general "ProblemDetails" data structure from
IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
general framework defined in IETF RFC 7807 [19], the "status" and
"detail" attributes are mandated to be included by the present
document, to ensure that the response contains additional textual
information about an error. IETF RFC 7807 [19] foresees
extensibility of the "ProblemDetails" type. It is possible that
particular APIs in the present document, or particular
implementations, define extensions to define additional attributes
that provide more information about the error. The description
column only provides some explanation of the meaning to Facilitate
understanding of the design. For a full description, see IETF RFC
7807 [19].
type: object
required:
- status
- detail
properties:
type:
description: >
A URI reference according to IETF RFC 3986 [5] that identifies
the problem type. It is encouraged that the URI provides
human-readable documentation for the problem (e.g. using HTML)
when dereferenced. When this member is not present, its value
is assumed to be "about:blank".
type: string
format: URI
title:
description: >
A short, human-readable summary of the problem type. It should
not change from occurrence to occurrence of the problem,
except for purposes of localization. If type is given and
other than "about:blank", this attribute shall also be
provided. A short, human-readable summary of the problem
type. It SHOULD NOT change from occurrence to occurrence of
the problem, except for purposes of localization (e.g., using
proactive content negotiation; see [RFC7231], Section 3.4).
type: string
status:
description: >
The HTTP status code for this occurrence of the problem. The
HTTP status code ([RFC7231], Section 6) generated by the
origin server for this occurrence of the problem.
type: integer
detail:
description: >
A human-readable explanation specific to this occurrence of
the problem.
type: string
instance:
description: >
A URI reference that identifies the specific occurrence of the
problem. It may yield further information if dereferenced.
type: string
format: URI
'409':
description: >
Conflict
Another request is in progress that prohibits the fulfilment of the
current request, or the current resource state is inconsistent with
the request.
headers:
Content-Type:
description: The MIME type of the body of the response.
type: string
maximum: 1
minimum: 1
WWW-Authenticate:
description: >
Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP
request has provided an invalid authorization token.
type: string
maximum: 1
minimum: 0
schema:
description: >
The definition of the general "ProblemDetails" data structure from
IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
general framework defined in IETF RFC 7807 [19], the "status" and
"detail" attributes are mandated to be included by the present
document, to ensure that the response contains additional textual
information about an error. IETF RFC 7807 [19] foresees
extensibility of the "ProblemDetails" type. It is possible that
particular APIs in the present document, or particular
implementations, define extensions to define additional attributes
that provide more information about the error. The description
column only provides some explanation of the meaning to Facilitate
understanding of the design. For a full description, see IETF RFC
7807 [19].
type: object
required:
- status
- detail
properties:
type:
description: >
A URI reference according to IETF RFC 3986 [5] that identifies
the problem type. It is encouraged that the URI provides
human-readable documentation for the problem (e.g. using HTML)
when dereferenced. When this member is not present, its value
is assumed to be "about:blank".
type: string
format: URI
title:
description: >
A short, human-readable summary of the problem type. It should
not change from occurrence to occurrence of the problem,
except for purposes of localization. If type is given and
other than "about:blank", this attribute shall also be
provided. A short, human-readable summary of the problem
type. It SHOULD NOT change from occurrence to occurrence of
the problem, except for purposes of localization (e.g., using
proactive content negotiation; see [RFC7231], Section 3.4).
type: string
status:
description: >
The HTTP status code for this occurrence of the problem. The
HTTP status code ([RFC7231], Section 6) generated by the
origin server for this occurrence of the problem.
type: integer
detail:
description: >
A human-readable explanation specific to this occurrence of
the problem.
type: string
instance:
description: >
A URI reference that identifies the specific occurrence of the
problem. It may yield further information if dereferenced.
type: string
format: URI
'500':
description: >
Internal Server Error
If there is an application error not related to the client's input
that cannot be easily mapped to any other HTTP response code ("catch
all error"), the API producer shall respond withthis response code.
The "ProblemDetails" structure shall be provided, and shall include
in the "detail" attribute more information about the source of the
problem.
headers:
Content-Type:
description: The MIME type of the body of the response.
type: string
maximum: 1
minimum: 1
schema:
description: >
The definition of the general "ProblemDetails" data structure from
IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
general framework defined in IETF RFC 7807 [19], the "status" and
"detail" attributes are mandated to be included by the present
document, to ensure that the response contains additional textual
information about an error. IETF RFC 7807 [19] foresees
extensibility of the "ProblemDetails" type. It is possible that
particular APIs in the present document, or particular
implementations, define extensions to define additional attributes
that provide more information about the error. The description
column only provides some explanation of the meaning to Facilitate
understanding of the design. For a full description, see IETF RFC
7807 [19].
type: object
required:
- status
- detail
properties:
type:
description: >
A URI reference according to IETF RFC 3986 [5] that identifies
the problem type. It is encouraged that the URI provides
human-readable documentation for the problem (e.g. using HTML)
when dereferenced. When this member is not present, its value
is assumed to be "about:blank".
type: string
format: URI
title:
description: >
A short, human-readable summary of the problem type. It should
not change from occurrence to occurrence of the problem,
except for purposes of localization. If type is given and
other than "about:blank", this attribute shall also be
provided. A short, human-readable summary of the problem
type. It SHOULD NOT change from occurrence to occurrence of
the problem, except for purposes of localization (e.g., using
proactive content negotiation; see [RFC7231], Section 3.4).
type: string
status:
description: >
The HTTP status code for this occurrence of the problem. The
HTTP status code ([RFC7231], Section 6) generated by the
origin server for this occurrence of the problem.
type: integer
detail:
description: >
A human-readable explanation specific to this occurrence of
the problem.
type: string
instance:
description: >
A URI reference that identifies the specific occurrence of the
problem. It may yield further information if dereferenced.
type: string
format: URI
'503':
description: >
Service Unavailable
If the API producer encounters an internal overload situation of
itself or of a system it relies on, it should respond with this
response code, following the provisions in IETF RFC 7231 [13] for
the use of the "Retry-After" HTTP header and for the alternative to
refuse the connection. The "ProblemDetails" structure may be
omitted.
headers:
Content-Type:
description: The MIME type of the body of the response.
type: string
maximum: 1
minimum: 1
schema:
description: >
The definition of the general "ProblemDetails" data structure from
IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
general framework defined in IETF RFC 7807 [19], the "status" and
"detail" attributes are mandated to be included by the present
document, to ensure that the response contains additional textual
information about an error. IETF RFC 7807 [19] foresees
extensibility of the "ProblemDetails" type. It is possible that
particular APIs in the present document, or particular
implementations, define extensions to define additional attributes
that provide more information about the error. The description
column only provides some explanation of the meaning to Facilitate
understanding of the design. For a full description, see IETF RFC
7807 [19].
type: object
required:
- status
- detail
properties:
type:
description: >
A URI reference according to IETF RFC 3986 [5] that identifies
the problem type. It is encouraged that the URI provides
human-readable documentation for the problem (e.g. using HTML)
when dereferenced. When this member is not present, its value
is assumed to be "about:blank".
type: string
format: URI
title:
description: >
A short, human-readable summary of the problem type. It should
not change from occurrence to occurrence of the problem,
except for purposes of localization. If type is given and
other than "about:blank", this attribute shall also be
provided. A short, human-readable summary of the problem
type. It SHOULD NOT change from occurrence to occurrence of
the problem, except for purposes of localization (e.g., using
proactive content negotiation; see [RFC7231], Section 3.4).
type: string
status:
description: >
The HTTP status code for this occurrence of the problem. The
HTTP status code ([RFC7231], Section 6) generated by the
origin server for this occurrence of the problem.
type: integer
detail:
description: >
A human-readable explanation specific to this occurrence of
the problem.
type: string
instance:
description: >
A URI reference that identifies the specific occurrence of the
problem. It may yield further information if dereferenced.
type: string
format: URI
'/vnf_lcm_op_occs/{vnfLcmOpOccId}':
parameters:
- name: vnfLcmOpOccId
description: >
Identifier of a VNF lifecycle management operation occurrence. This
identifier can be retrieved from the resource referenced by the
"Location" HTTP header in the response to a PATCH or POST request
triggering a VNF LCM operation. It can also be retrieved from the
"vnfLcmOpOccId" attribute in the
VnfLcmOperationOccurrenceNotification.
in: path
required: true
type: string
get:
description: >
Get Operation Status
The client can use this method to retrieve status information about a
VNF lifecycle management operation occurrence by reading an individual
"VNF LCM operation occurrence" resource.
parameters:
- name: Accept
description: >
Content-Types that are acceptable for the response. Reference: IETF
RFC 7231
in: header
required: true
type: string
- name: Authorization
description: |
The authorization token for the request. Reference: IETF RFC 7235
in: header
required: false
type: string
responses:
'200':
description: >
OK
Information about an individual VNF instance was queried
successfully. The response body shall contain status information
about a VNF lifecycle management operation occurrence.
headers:
Content-Type:
description: The MIME type of the body of the response.
type: string
maximum: 1
minimum: 1
WWW-Authenticate:
description: >
Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP
request has provided an invalid authorization token.
type: string
maximum: 1
minimum: 0
schema:
description: >
This type represents a VNF lifecycle management operation
occurrence.
type: object
required:
- id
- operationState
- stateEnteredTime
- startTime
- vnfInstanceId
- operation
- isAutomaticInvocation
- operationParams
- isCancelPending
properties:
id:
description: |
An identifier with the intention of being globally unique.
type: string
operationState:
description: >
Value | Description ------|------------ STARTING | The LCM
operation is starting. PROCESSING | The LCM operation is
currently in execution. COMPLETED | he LCM operation has been
completed successfully. FAILED_TEMP | The LCM operation has
failed and execution has stopped, but the execution of the
operation is not considered to be closed. FAILED | The LCM
operation has failed and it cannot be retried or rolled back,
as it is determined that such action won't succeed.
ROLLING_BACK | The LCM operation is currently being rolled
back. ROLLED_BACK | The LCM operation has been successfully
rolled back, i.e. The state of the VNF prior to the original
operation invocation has been restored as closely as possible.
type: string
enum:
- STARTING
- PROCESSING
- COMPLETED
- FAILED_TEMP
- FAILED
- ROLLING_BACK
- ROLLED_BACK
stateEnteredTime:
description: |
Date-time when the current state was entered.
type: string
format: date-time
startTime:
description: |
Date-time of the start of the operation.
type: string
format: date-time
vnfInstanceId:
description: |
An identifier with the intention of being globally unique.
type: string
grantId:
description: |
An identifier with the intention of being globally unique.
type: string
operation:
description: >
Value | Description ------|------------ INSTANTIATE |
Represents the "Instantiate VNF" LCM operation. SCALE |
Represents the "Scale VNF" LCM operation. SCALE_TO_LEVEL |
Represents the "Scale VNF to Level" LCM operation.
CHANGE_FLAVOUR | Represents the "Change VNF Flavour" LCM
operation. TERMINATE | Represents the "Terminate VNF" LCM
operation. HEAL | Represents the "Heal VNF" LCM operation.
OPERATE | Represents the "Operate VNF" LCM operation.
CHANGE_EXT_CONN | Represents the "Change external VNF
connectivity" LCM operation. MODIFY_INFO | Represents the
"Modify VNF Information" LCM operation.
type: string
enum:
- INSTANTIATE
- SCALE
- SCALE_TO_LEVEL
- CHANGE_FLAVOUR
- TERMINATE
- HEAL
- OPERATE
- CHANGE_EXT_CONN
- MODIFY_INFO
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
operationParams:
description: >
This type represents a list of key-value pairs. The order of
the pairs in the list is not significant. In JSON, a set of
key- value pairs is represented as an object. It shall comply
with the provisions defined in clause 4 of IETF RFC 7159.
type: object
isCancelPending:
description: >
If the VNF LCM operation occurrence is in "STARTING",
"PROCESSING" or "ROLLING_BACK" state and the operation is
being cancelled, this attribute shall be set to true.
Otherwise, it shall be set to false.
type: boolean
cancelMode:
description: >
Cancellation mode. GRACEFUL: If the VNF LCM operation
occurrence is in "PROCESSING" or "ROLLING_BACK" state, the
VNFM shall not start any new resource management operation and
shall wait for the ongoing resource management operations in
the underlying system, typically the VIM, to finish execution
or to time out. After that, the VNFM shall put the operation
occurrence into the FAILED_TEMP state. If the VNF LCM
operation occurrence is in "STARTING" state, the VNFM shall
not start any resource management operation and shall wait for
the granting request to finish execution or time out. After
that, the VNFM shall put the operation occurrence into the
ROLLED_BACK state. FORCEFUL: If the VNF LCM operation
occurrence is in "PROCESSING" or "ROLLING_BACK" state, the
VNFM shall not start any new resource management operation,
shall cancel the ongoing resource management operations in the
underlying system, typically the VIM, and shall wait for the
cancellation to finish or to time out. After that, the VNFM
shall put the operation occurrence into the FAILED_TEMP
state. If the VNF LCM operation occurrence is in "STARTING"
state, the VNFM shall not start any resource management
operation and put the operation occurrence into the
ROLLED_BACK state.
type: string
enum:
- GRACEFUL
- FORCEFUL
error:
description: >
The definition of the general "ProblemDetails" data structure
from IETF RFC 7807 [19] is reproduced inthis structure.
Compared to the general framework defined in IETF RFC 7807
[19], the "status" and "detail" attributes are mandated to be
included by the present document, to ensure that the response
contains additional textual information about an error. IETF
RFC 7807 [19] foresees extensibility of the "ProblemDetails"
type. It is possible that particular APIs in the present
document, or particular implementations, define extensions to
define additional attributes that provide more information
about the error. The description column only provides some
explanation of the meaning to Facilitate understanding of the
design. For a full description, see IETF RFC 7807 [19].
type: object
required:
- status
- detail
properties:
type:
description: >
A URI reference according to IETF RFC 3986 [5] that
identifies the problem type. It is encouraged that the URI
provides human-readable documentation for the problem
(e.g. using HTML) when dereferenced. When this member is
not present, its value is assumed to be "about:blank".
type: string
format: URI
title:
description: >
A short, human-readable summary of the problem type. It
should not change from occurrence to occurrence of the
problem, except for purposes of localization. If type is
given and other than "about:blank", this attribute shall
also be provided. A short, human-readable summary of the
problem type. It SHOULD NOT change from occurrence to
occurrence of the problem, except for purposes of
localization (e.g., using proactive content negotiation;
see [RFC7231], Section 3.4).
type: string
status:
description: >
The HTTP status code for this occurrence of the problem.
The HTTP status code ([RFC7231], Section 6) generated by
the origin server for this occurrence of the problem.
type: integer
detail:
description: >
A human-readable explanation specific to this occurrence
of the problem.
type: string
instance:
description: >
A URI reference that identifies the specific occurrence of
the problem. It may yield further information if
dereferenced.
type: string
format: URI
resourceChanges:
description: >
This attribute contains information about the cumulative
changes to virtualised resources that were performed so far by
the LCM operation since its start, if applicable.
type: object
properties:
affectedVnfcs:
description: >
Information about VNFC instances that were affected during
the lifecycle operation. This allows the NFVO to obtain
the information contained in the latest "result"
notification if it has not received it due to an error or
a wrongly configured subscription filter.
type: array
items:
description: >
This type provides information about added, deleted,
modified and temporary VNFCs.
type: object
required:
- id
- vduId
- changeType
- computeResource
properties:
id:
description: >
An identifier that is unique for the respective type
within a VNF instance, but may not be globally
unique.
type: string
vduId:
description: >
An identifier that is unique within a VNF
descriptor.
type: string
changeType:
description: >
Signals the type of change. Permitted values: *
ADDED * REMOVED * MODIFIED * TEMPORARY For a
temporary resource, an AffectedVnfc structure exists
as long as the temporary resource exists.
type: string
enum:
- ADDED
- REMOVED
- MODIFIED
- TEMPORARY
computeResource:
required:
- vimConnectionId
- resourceId
type: object
description: >
This type represents the information that allows
addressing a virtualised resource that is used by a
VNF instance. Information about the resource is
available from the VIM.
properties:
vimConnectionId:
description: >
An identifier with the intention of being
globally unique.
type: string
resourceProviderId:
description: >
An identifier with the intention of being
globally unique.
type: string
resourceId:
description: >
An identifier maintained by the VIM or other
resource provider. It is expected to be unique
within the VIM instance.
type: string
vimLevelResourceType:
description: >
Type of the resource in the scope of the VIM or
the resource provider.
type: string
metadata:
description: >
This type represents a list of key-value pairs. The
order of the pairs in the list is not significant.
In JSON, a set of key- value pairs is represented as
an object. It shall comply with the provisions
defined in clause 4 of IETF RFC 7159.
type: object
affectedVnfcCpIds:
description: >
Identifiers of CP(s) of the VNFC instance that were
affected by the change. Shall be present for those
affected CPs of the VNFC instance that are
associated to an external CP of the VNF instance.
May be present for further affected CPs of the VNFC
instance.
type: array
items:
description: >
An identifier that is unique for the respective
type within a VNF instance, but may not be
globally unique.
type: string
addedStorageResourceIds:
description: >
References to VirtualStorage resources that have
been added. Each value refers to a
VirtualStorageResourceInfo item in the VnfInstance
that was added to the VNFC. It shall be provided if
at least one storage resource was added to the VNFC.
type: array
items:
description: >
An identifier that is unique for the respective
type within a VNF instance, but may not be
globally unique.
type: string
removedStorageResourceIds:
description: >
References to VirtualStorage resources that have
been removed. The value contains the identifier of a
VirtualStorageResourceInfo item that has been
removed from the VNFC, and might no longer exist in
the VnfInstance. It shall be provided if at least
one storage resource was removed from the VNFC.
type: array
items:
description: >
An identifier that is unique for the respective
type within a VNF instance, but may not be
globally unique.
type: string
affectedVirtualLinks:
description: >
Information about VL instances that were affected during
the lifecycle operation. This allows the NFVO to obtain
the information contained in the latest "result"
notification if it has not received it due to an error or
a wrongly configured subscription filter.
type: array
items:
description: >
This type provides information about added, deleted,
modified and temporary VLs.
type: object
required:
- id
- virtualLinkDescId
- changeType
- networkResource
properties:
id:
description: >
An identifier that is unique for the respective type
within a VNF instance, but may not be globally
unique.
type: string
virtualLinkDescId:
description: >
An identifier that is unique within a VNF
descriptor.
type: string
changeType:
description: >
Signals the type of change. Permitted values: *
ADDED * REMOVED * MODIFIED * TEMPORARY *
LINK_PORT_ADDED * LINK_PORT_REMOVED For a temporary
resource, an AffectedVirtualLink structure exists as
long as the temporary resource exists.
type: string
enum:
- ADDED
- REMOVED
- MODIFIED
- TEMPORARY
- LINK_PORT_ADDED
- LINK_PORT_REMOVED
networkResource:
required:
- vimConnectionId
- resourceId
type: object
description: >
This type represents the information that allows
addressing a virtualised resource that is used by a
VNF instance. Information about the resource is
available from the VIM.
properties:
vimConnectionId:
description: >
An identifier with the intention of being
globally unique.
type: string
resourceProviderId:
description: >
An identifier with the intention of being
globally unique.
type: string
resourceId:
description: >
An identifier maintained by the VIM or other
resource provider. It is expected to be unique
within the VIM instance.
type: string
vimLevelResourceType:
description: >
Type of the resource in the scope of the VIM or
the resource provider.
type: string
metadata:
description: >
This type represents a list of key-value pairs. The
order of the pairs in the list is not significant.
In JSON, a set of key- value pairs is represented as
an object. It shall comply with the provisions
defined in clause 4 of IETF RFC 7159.
type: object
affectedVirtualStorages:
description: >
Information about virtualised storage instances that were
affected during the lifecycle operation. This allows the
NFVO to obtain the information contained in the latest
"result" notification if it has not received it due to an
error or a wrongly configured subscription filter.
type: array
items:
description: >
This type provides information about added, deleted,
modified and temporary virtual storage resources.
type: object
required:
- id
- virtualStorageDescId
- changeType
- storageResource
properties:
id:
description: >
An identifier that is unique for the respective type
within a VNF instance, but may not be globally
unique.
type: string
virtualStorageDescId:
description: >
An identifier that is unique within a VNF
descriptor.
type: string
changeType:
description: >
Signals the type of change. Permitted values: *
ADDED * REMOVED * MODIFIED * TEMPORARY For a
temporary resource, an AffectedVirtualStorage
structure exists as long as the temporary resource
exists.
type: string
enum:
- ADDED
- REMOVED
- MODIFIED
- TEMPORARY
storageResource:
required:
- vimConnectionId
- resourceId
type: object
description: >
This type represents the information that allows
addressing a virtualised resource that is used by a
VNF instance. Information about the resource is
available from the VIM.
properties:
vimConnectionId:
description: >
An identifier with the intention of being
globally unique.
type: string
resourceProviderId:
description: >
An identifier with the intention of being
globally unique.
type: string
resourceId:
description: >
An identifier maintained by the VIM or other
resource provider. It is expected to be unique
within the VIM instance.
type: string
vimLevelResourceType:
description: >
Type of the resource in the scope of the VIM or
the resource provider.
type: string
metadata:
description: >
This type represents a list of key-value pairs. The
order of the pairs in the list is not significant.
In JSON, a set of key- value pairs is represented as
an object. It shall comply with the provisions
defined in clause 4 of IETF RFC 7159.
type: object
changedInfo:
description: >
This type represents attribute modifications that were
performed on an "Individual VNF instance" resource. The
attributes that can be included consist of those requested to
be modified explicitly in the "VnfInfoModificationRequest"
data structure, and additional attributes of the "VnfInstance"
data structure that were modified implicitly e.g. when
modifying the referenced VNF package.
type: object
properties:
vnfInstanceName:
description: >
If present, this attribute signals modifications of the
"vnfInstanceName" attribute in "VnfInstance".
type: string
vnfInstanceDescription:
description: >
If present, this attribute signals modifications of the
"vnfInstanceDescription" attribute in "VnfInstance".
type: string
vnfConfigurableProperties:
description: >
This type represents a list of key-value pairs. The order
of the pairs in the list is not significant. In JSON, a
set of key- value pairs is represented as an object. It
shall comply with the provisions defined in clause 4 of
IETF RFC 7159.
type: object
metadata:
description: >
This type represents a list of key-value pairs. The order
of the pairs in the list is not significant. In JSON, a
set of key- value pairs is represented as an object. It
shall comply with the provisions defined in clause 4 of
IETF RFC 7159.
type: object
extensions:
description: >
This type represents a list of key-value pairs. The order
of the pairs in the list is not significant. In JSON, a
set of key- value pairs is represented as an object. It
shall comply with the provisions defined in clause 4 of
IETF RFC 7159.
type: object
vimConnectionInfo:
description: >
If present, this attribute signals modifications of
certain entries in the "vimConnectionInfo" attribute array
in "VnfInstance".
type: array
items:
description: >
This type represents parameters to connect to a VIM for
managing the resources of a VNF instance. This structure
is used to convey VIM-related parameters over the
Or-Vnfm interface. Additional parameters for a VIM may
be configured into the VNFM by means outside the scope
of the present document, and bound to the identifier of
that VIM.
type: object
required:
- id
- vimType
properties:
id:
description: >
An identifier with the intention of being globally
unique.
type: string
vimId:
description: >
An identifier with the intention of being globally
unique.
type: string
vimType:
description: >
Discriminator for the different types of the VIM
information. The value of this attribute determines
the structure of the "interfaceInfo" and
"accessInfo" attributes, based on the type of the
VIM. The set of permitted values is expected to
change over time as new types or versions of VIMs
become available. The ETSI NFV registry of
VIM-related information provides access to
information about VimConnectionInfo definitions for
various VIM types. The structure of the registry is
defined in Annex C of SOL003.
type: string
interfaceInfo:
description: >
This type represents a list of key-value pairs. The
order of the pairs in the list is not significant.
In JSON, a set of key- value pairs is represented as
an object. It shall comply with the provisions
defined in clause 4 of IETF RFC 7159.
type: object
accessInfo:
description: >
This type represents a list of key-value pairs. The
order of the pairs in the list is not significant.
In JSON, a set of key- value pairs is represented as
an object. It shall comply with the provisions
defined in clause 4 of IETF RFC 7159.
type: object
extra:
description: >
This type represents a list of key-value pairs. The
order of the pairs in the list is not significant.
In JSON, a set of key- value pairs is represented as