Newer
Older
info:
version: 1.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1
title: SOL009 - NFV-MANO Fault Management Notification interface
description: >
SOL009 - NFV-MANO Fault Management Notification interface
IMPORTANT: Please note that this file might be not aligned to the current version of the ETSI Group Specification it refers to. In case of discrepancies the published ETSI Group Specification takes precedence.
Please report bugs to https://forge.etsi.org/bugzilla/buglist.cgi?component=Nfv-Openapis&list_id=61&product=NFV&resolution=
license:
name: ETSI Forge copyright notice
url: https://forge.etsi.org/etsi-forge-copyright-notice.txt
externalDocs:
description: ETSI GS NFV-SOL 009 V0.8.0
url: https://docbox.etsi.org/ISG/NFV/Open/Drafts/SOL009ed331_MANO_mgmt_stage_3/NFV-SOL009ed331v080.zip
paths:
/URI-is-provided-by-the-client-when-creating-the-subscription-AlarmNotification:
post:
description: >
The POST method notifies an NFV-MANO functional entity alarm or that the
alarm list has been rebuilt. The API consumer shall have previously
created an "Individual subscription" resource with a matching filter.
This method shall follow the provisions specified in the tables
7.5.7.3.1-1 and 7.5.7.3.1-2 for URI query parameters, request and
response data structures, and response codes.
parameters:
- name: Authorization
The authorization token for the request. Reference: IETF RFC 7235
in: header
required: false
schema:
type: string
- name: Content-Type
description: >
The Content-Type header shall be set to
"application/merge-patch+json" according to IETF RFC 7396.
in: header
required: true
schema:
type: string
- name: Version
Version of the API requested to use when responding to this request.
in: header
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
$ref: ../NFVManoFaultManagement/definitions/SOL009NFVManoFaultManagement_def.yaml#/definitions/AlarmNotification
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
Information of a NFV-MANO functional entity alarm.
required: true
responses:
"204":
description: >
204 NO CONTENT
Shall be returned when the notification has been delivered successfully. The response body shall be empty.
headers:
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.
schema:
type: string
minimum: 0
maximum: 1
Version:
description: |
Version of the API used in the response.
schema:
type: string
minimum: 1
maximum: 1
"400":
$ref: ../responses/SOL009_resp.yaml#/responses/400
"401":
$ref: ../responses/SOL009_resp.yaml#/responses/401
"403":
$ref: ../responses/SOL009_resp.yaml#/responses/403
"405":
$ref: ../responses/SOL009_resp.yaml#/responses/405
"406":
$ref: ../responses/SOL009_resp.yaml#/responses/406
"500":
$ref: ../responses/SOL009_resp.yaml#/responses/500
"503":
$ref: ../responses/SOL009_resp.yaml#/responses/503
get:
description: >
The GET method allows the server to test the notification endpoint that
is provided by the client, e.g. during subscription. This method shall
follow the provisions specified in the tables 7.5.7.3.2-1 and
7.5.7.3.2-2 for URI query parameters, request and response data
structures, and response codes.
parameters:
- name: Authorization
description: |
The authorization token for the request. Reference: IETF RFC 7235
in: header
required: false
schema:
type: string
- name: Version
description: |
Version of the API requested to use when responding to this request.
in: header
required: true
schema:
type: string
responses:
"204":
description: >
204 NO CONTENT
Shall be returned to indicate that the notification endpoint has been tested successfully.
The response body shall be empty.
headers:
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.
schema:
type: string
minimum: 0
maximum: 1
Version:
description: |
Version of the API used in the response.
schema:
type: string
minimum: 1
maximum: 1
"400":
$ref: ../responses/SOL009_resp.yaml#/responses/400
"401":
$ref: ../responses/SOL009_resp.yaml#/responses/401
"403":
$ref: ../responses/SOL009_resp.yaml#/responses/403
"405":
$ref: ../responses/SOL009_resp.yaml#/responses/405
"406":
$ref: ../responses/SOL009_resp.yaml#/responses/406
"500":
$ref: ../responses/SOL009_resp.yaml#/responses/500
"503":
$ref: ../responses/SOL009_resp.yaml#/responses/503
/URI-is-provided-by-the-client-when-creating-the-subscription-AlarmClearedNotification:
post:
description: >
The POST method notifies an NFV-MANO functional entity alarm or that the
alarm list has been rebuilt. The API consumer shall have previously
created an "Individual subscription" resource with a matching filter.
This method shall follow the provisions specified in the tables
7.5.7.3.1-1 and 7.5.7.3.1-2 for URI query parameters, request and
response data structures, and response codes.
parameters:
- name: Authorization
description: |
The authorization token for the request. Reference: IETF RFC 7235
in: header
required: false
schema:
type: string
- name: Content-Type
description: >
The Content-Type header shall be set to
"application/merge-patch+json" according to IETF RFC 7396.
in: header
required: true
schema:
type: string
- name: Version
description: |
Version of the API requested to use when responding to this request.
in: header
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
$ref: ../NFVManoFaultManagement/definitions/SOL009NFVManoFaultManagement_def.yaml#/definitions/AlarmClearedNotification
description: |
Information of the clearance of an NFV-MANO functional entity alarm.
required: true
responses:
"204":
description: >
204 NO CONTENT
Shall be returned when the notification has been delivered successfully. The response body shall be empty.
headers:
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.
schema:
type: string
minimum: 0
maximum: 1
Version:
description: |
Version of the API used in the response.
schema:
type: string
minimum: 1
maximum: 1
"400":
$ref: ../responses/SOL009_resp.yaml#/responses/400
"401":
$ref: ../responses/SOL009_resp.yaml#/responses/401
"403":
$ref: ../responses/SOL009_resp.yaml#/responses/403
"405":
$ref: ../responses/SOL009_resp.yaml#/responses/405
"406":
$ref: ../responses/SOL009_resp.yaml#/responses/406
"500":
$ref: ../responses/SOL009_resp.yaml#/responses/500
"503":
$ref: ../responses/SOL009_resp.yaml#/responses/503
get:
description: >
The GET method allows the server to test the notification endpoint that
is provided by the client, e.g. during subscription. This method shall
follow the provisions specified in the tables 7.5.7.3.2-1 and
7.5.7.3.2-2 for URI query parameters, request and response data
structures, and response codes.
parameters:
- name: Authorization
description: |
The authorization token for the request. Reference: IETF RFC 7235
in: header
required: false
schema:
type: string
- name: Version
description: |
Version of the API requested to use when responding to this request.
in: header
required: true
schema:
type: string
responses:
"204":
description: >
204 NO CONTENT
Shall be returned to indicate that the notification endpoint has been tested successfully.
The response body shall be empty.
headers:
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.
schema:
type: string
minimum: 0
maximum: 1
Version:
description: |
Version of the API used in the response.
schema:
type: string
minimum: 1
maximum: 1
"400":
$ref: ../responses/SOL009_resp.yaml#/responses/400
"401":
$ref: ../responses/SOL009_resp.yaml#/responses/401
"403":
$ref: ../responses/SOL009_resp.yaml#/responses/403
"405":
$ref: ../responses/SOL009_resp.yaml#/responses/405
"406":
$ref: ../responses/SOL009_resp.yaml#/responses/406
"500":
$ref: ../responses/SOL009_resp.yaml#/responses/500
"503":
$ref: ../responses/SOL009_resp.yaml#/responses/503
/URI-is-provided-by-the-client-when-creating-the-subscription-AlarmListRebuiltNotification:
post:
description: >
The POST method notifies an NFV-MANO functional entity alarm or that the
alarm list has been rebuilt. The API consumer shall have previously
created an "Individual subscription" resource with a matching filter.
This method shall follow the provisions specified in the tables
7.5.7.3.1-1 and 7.5.7.3.1-2 for URI query parameters, request and
response data structures, and response codes.
parameters:
- name: Authorization
description: |
The authorization token for the request. Reference: IETF RFC 7235
in: header
required: false
schema:
type: string
- name: Content-Type
description: >
The Content-Type header shall be set to
"application/merge-patch+json" according to IETF RFC 7396.
in: header
required: true
schema:
type: string
- name: Version
description: |
Version of the API requested to use when responding to this request.
in: header
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
$ref: ../NFVManoFaultManagement/definitions/SOL009NFVManoFaultManagement_def.yaml#/definitions/AlarmListRebuiltNotification
description: >
Information that the alarm list has been rebuilt by the NFV-MANO
functional entity.
required: true
responses:
"204":
description: >
204 NO CONTENT
Shall be returned when the notification has been delivered successfully. The response body shall be empty.
headers:
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.
schema:
type: string
minimum: 0
maximum: 1
Version:
description: |
Version of the API used in the response.
schema:
type: string
minimum: 1
maximum: 1
"400":
$ref: ../responses/SOL009_resp.yaml#/responses/400
"401":
$ref: ../responses/SOL009_resp.yaml#/responses/401
"403":
$ref: ../responses/SOL009_resp.yaml#/responses/403
"405":
$ref: ../responses/SOL009_resp.yaml#/responses/405
"406":
$ref: ../responses/SOL009_resp.yaml#/responses/406
"500":
$ref: ../responses/SOL009_resp.yaml#/responses/500
"503":
$ref: ../responses/SOL009_resp.yaml#/responses/503
get:
description: >
The GET method allows the server to test the notification endpoint that
is provided by the client, e.g. during subscription. This method shall
follow the provisions specified in the tables 7.5.7.3.2-1 and
7.5.7.3.2-2 for URI query parameters, request and response data
structures, and response codes.
parameters:
- name: Authorization
description: |
The authorization token for the request. Reference: IETF RFC 7235
in: header
required: false
schema:
type: string
- name: Version
description: |
Version of the API requested to use when responding to this request.
in: header
required: true
schema:
type: string
responses:
"204":
description: >
204 NO CONTENT
Shall be returned to indicate that the notification endpoint has been tested successfully. The response body shall be empty.
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
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.
schema:
type: string
minimum: 0
maximum: 1
Version:
description: |
Version of the API used in the response.
schema:
type: string
minimum: 1
maximum: 1
"400":
$ref: ../responses/SOL009_resp.yaml#/responses/400
"401":
$ref: ../responses/SOL009_resp.yaml#/responses/401
"403":
$ref: ../responses/SOL009_resp.yaml#/responses/403
"405":
$ref: ../responses/SOL009_resp.yaml#/responses/405
"406":
$ref: ../responses/SOL009_resp.yaml#/responses/406
"500":
$ref: ../responses/SOL009_resp.yaml#/responses/500
"503":
$ref: ../responses/SOL009_resp.yaml#/responses/503