Gitiles
Code Review Sign In
gerrit.nordix.org / onap / appc / 881d21c2a04c195ad57e7fb14f1fe5cd1b1be413 / . / docs / APPC API Guide / APPC API Guide.rst
blob: 63ebd2731beb2fa1e2ebee17a51109d9aa03b58a [file] [log] [blame]
Scott Seabolt59153e92017-09-08 15:08:33 -0400[diff] [blame]1ONAP Application Controller (APPC) API Guide
2============================================
3
4Revision History
5----------------
6
7+--------------+------------+---------------+--------------------------------------------------------+
8| Date | Revision | Author | Changes |
9+--------------+------------+---------------+--------------------------------------------------------+
10| 2017-08-25 | 2.0.0 | Paul Miller | Updates for software contribution in Amsterdam Release |
11| | | | |
12| | | | **Commands Removed** |
13| | | | - LiveUpgrade |
14| | | | - ModifyConfig (replaced by ConfigModify) |
15| | | | - Rollback |
16| | | | - SoftwareUpload |
17| | | | - Terminate |
18| | | | - Test |
19+--------------+------------+---------------+--------------------------------------------------------+
20| 2017-02-06 | 1.0.0 | mjf | copyright updated |
21+--------------+------------+---------------+--------------------------------------------------------+
22
23|
24
25Introduction
26============
27
28This guide describes the APPC API that allows you to manage and control the life cycle of controlled virtual network functions (VNFs).
29
30
31Target Audience
32---------------
33This document is intended for an advanced technical audience, such as the engineers or architects who need to use this guide to develop an interfacing application. The guide assumes a knowledge of the Open Network Automation Platform (ONAP) components and features, and familiarity with JSON notation.
34
35
36Conventions
37-----------
38
39+--------------+------------------------------------------------------------------------------------------+
40| Convention | Description |
41| | |
42+==============+==========================================================================================+
43|``Monospace`` | This font indicates sample codes, screenshots, or elements. For example:: |
44| | |
45| | "contact": { |
46| | "contactType": "USER", |
47| | "source": "app1", |
48| | } |
49| | |
50+--------------+------------------------------------------------------------------------------------------+
51|*Italics* | Emphasizes a point or denotes new terms at the place where they are defined in the text. |
52| | Indicates an external book title reference. |
53| | |
54+--------------+------------------------------------------------------------------------------------------+
55
56
57
58Life Cycle Management Commands
59==============================
60
61APPC receives commands from external ECOMP components, such as SO, Policy, DCAE, or the Portal, to manage the life cycle of virtual applications and their components.
62
63A virtual application is composed of the following layers of network technology:
64
65- Virtual Network Function (VNF)
66- Virtual Network Function Component (VNFC)
67- Virtual Machine (VM)
68
69A Life Cycle Management (LCM) command may affect one or more of these layers.
70
71An LCM command is sent as a request to the APPC using an HTTP POST request or in a message on a message bus (DMaaP or UEB). A request may result in either a single synchronous response or multiple asynchronous responses:
72
73- An **asynchronous** command, which is sent as an authorized and valid request, results in at least two discrete response events:
74 - an accept response, to indicate that the request is accepted for processing
75 - a final response to indicate the status and outcome of the request processing
76 - An unauthorized or invalid request results in a single ERROR response.
77
78- A **synchronous** command, such as Lock or Unlock, results in a single response that is either SUCCESS or ERROR.
79
80**NOTE:** For both asynchronous or synchronous commands, the first response is always returned using the same transport that the initial action used. For example, if the action request was via the message bus (such as when it originates from Policy), then the response is also via the message bus. However, if the request was via a direct HTTP call, the response is similarly a synchronous HTTP response.
81
82
83Message Bus and the LCM API Client Library
84------------------------------------------
85
86The recommended approach for sending/receiving requests to APPC is via the message bus. To support this approach, an APPC client library is available and should be used. The client library aims to provide consumers of APPC capabilities with a strongly-typed Java interface and to encapsulate the actual interaction with APPC component via the message bus.
87
88For more details, see the APPC Client Library Guide at:
89
90 guides/appc_api_client
91
92
93The client library supports both synchronous and asynchronous flows as follows.
94
95Asynchronous Flow
96^^^^^^^^^^^^^^^^^
97
98- The APPC Client Library is called via an asynchronous API using a full command object, which is mapped to a JSON representation.
99- The APPC client calls the UEB/DMaaP client and sends the JSON command to a configured topic.
100- The APPC client pulls response messages from the configured topic.
101- On receiving the response for the command, APPC client runs the relevant callback method of the consumer ResponseHandler.
102
103Synchronous Flow
104^^^^^^^^^^^^^^^^
105
106- The APPC Client Library is called via a synchronous API using a full command object, which is mapped to a JSON representation.
107- The APPC client calls the UEB/DMaaP client and sends the JSON command to a configured topic.
108- The APPC client pulls response messages from the configured topic.
109- On receiving the final response for the command, the APPC client returns the response object with a final status.
110
111The client library adds the following wrapper around request and responses to the LCM API (described below)::
112
113 {
114 "version" : "2.0",
115 "cambria.partition" : "<TOPIC>",
116 "correlation-id" :"<CORRELATION_ID>",
117 "rpc-name" : "<RPC_NME>",
118 "type" : <MESSAGE_TYPE>
119 "body" : <RPC_SPECIFIC_BODY>
120 }
121
122
123
124Table 1 Request / Response Message Fields
125
126+----------------------+----------------------------------------------------------------------------------------------------------------+---------------------+
127| **Field** | **Description** | **Required** |
128+======================+================================================================================================================+=====================+
129| version | Indicates the version of the message bus protocol with APPC. Version 2.0 should be used. | Yes |
130+----------------------+----------------------------------------------------------------------------------------------------------------+---------------------+
131| cambria. partition | Indicates the specific topic partition that the message is intended for. For example: | No |
132| | | |
133| | - For incoming messages, this value should be APP-C. | |
134| | | |
135+----------------------+----------------------------------------------------------------------------------------------------------------+---------------------+
136| correlation- id | Correlation ID used for associating responses in APPC Client Library. Built as: <request-id>-<sub-request-id> | Yes |
137+----------------------+----------------------------------------------------------------------------------------------------------------+---------------------+
138| rpc-name | The target Remote Processing Call (RPC) name which should match the LCM command name. For example: configure | Yes |
139+----------------------+----------------------------------------------------------------------------------------------------------------+---------------------+
140| type | Message type: request, response or error | Yes |
141+----------------------+----------------------------------------------------------------------------------------------------------------+---------------------+
142| body | Contains the input or output LCM command content, which is either the request or response | |
143| | The body field format is identical to the equivalent HTTP Rest API command based on the specific RPC name | Yes |
144| | | |
145+----------------------+----------------------------------------------------------------------------------------------------------------+---------------------+
146
147
148Generic Request Format
149----------------------
150
151The LCM API general request format is applicable for both POST HTTP API and for the message body received via the EUB/DMaaP bus.
152
153LCM Request
154^^^^^^^^^^^
155
156The LCM request comprises a common header and a section containing the details of the LCM action.
157The LCM request conforms to the following structure::
158
159 {
160 "input": {
161 "common-header": {"timestamp": "<TIMESTAMP>",
162 "api-ver": "<API_VERSION>",
163 "originator-id": "<ECOMP_SYSTEM_ID>",
164 "request-id": "<ECOMP_REQUEST_ID>",
165 "sub-request-id": "<ECOMP_SUBREQUEST_ID>",
166 "flags": {
167 "mode": "<EXCLUSIVE|NORMAL>",
168 "force": "<TRUE|FALSE>",
169 "ttl": "<TTL_VALUE>"
170 }
171 },
172 "action": "<COMMAND_ACTION>",
173 "action-identifiers": {
174 "vnf-id": "<ECOMP_VNF_ID>",
175 "vnfc-name": "<ECOMP_VNFC_NAME>",
176 "vserver-id": "VSERVER_ID"
177 },
178 ["payload": "<PAYLOAD>"]
179 }
180 }
181
182
183Table 2 LCM Request Fields
184
185+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
186| **Field** | **Description** | **Required?** |
187+===========================+========================================================================================================================================================================================================================================================================================================================+=====================+
188| input | The block that defines the details of the input to the command processing. Contains the common-header details. | Yes |
189+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
190| common- header | The block that contains the generic details about a request. | Yes |
191+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
192| timestamp | The time of the request, in ISO 8601 format, ZULU offset. For example: 2016-08-03T08:50:18.97Z. | Yes |
193| | | |
194| | APPC will reject the request if timestamp is in the future (due to clock error), or timestamp is too old (compared to TTL flag) | |
195+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
196| api-ver | Identifies the API version, in X.YY format, where X denotes the major version increased with each APPC release, and YY is the minor release version. For example: | Yes |
197| | | |
198| | - 5.00 for this version | |
199+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
200| originator-id | An identifier of the calling system limited to a length of 40 characters. | Yes |
201| | | |
202| | It can be used for addressing purposes, such as to return an asynchronous response to the correct destination, in particular where there are multiple consumers of APPC APIs. | |
203+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
204| request-id | The UUID for the request ID, limited to a length of 40 characters. The unique OSS/BSS identifier for the request ID that triggers the current LCM action. Multiple API calls can be made with the same request-id. | Yes |
205| | | |
206| | The request-id is stored throughout the operations performed during a single request. | |
207+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
208| sub-request-id | Uniquely identifies a specific LCM or control action, limited to a length of 40 characters. Persists throughout the life cycle of a single request. | No |
209+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
210| flags | Generic flags that apply to all LCM actions: | No |
211| | | |
212| | - "MODE" : | |
213| | | |
214| | - "EXCLUSIVE" - accept no queued requests on this VNF while processing, or | |
215| | | |
216| | - "NORMAL" - queue other requests until complete | |
217| | | |
218| | - "FORCE" : "TRUE"\|"FALSE" - run action even if target is in an unstable state (for example, if VNF is busy processing another LCM command or if a previous command failed and VNF was indicated as not STABLE), or not. | |
219| | | |
220| | The specific behavior of forced actions varies, but implies cancellation of the previous action and an override by the new action. The default value is FALSE. | |
221| | | |
222| | Force flag are used to bypass APPC’s working state management for the VNF(VNF working State Management) : | |
223| | | |
224| | APPC maintains working state (in the VNF\_STATE\_MANAGEMENT table present in the APPC-DB) for the VNF depending on the last action performed on it: | |
225| | | |
226| | There are below 3 states appc have for VNF while performing non-read only operation (Read-Only operations are : Lock, Unlock, CheckLock, Sync, Audit etc. ) : | |
227| | | |
228| | 1) Stable – If the last action performed on a VNF is Successful (returning Success). | |
229| | | |
230| | 2) Unstable – This is the intermediate state for any VNF on which operation is being performed. | |
231| | | |
232| | 3) Unknown – This is the status when the last action performed on a VNF is not successful. | |
233| | | |
234| | APPC have validation that it will not allow any operations on VNF which is in Unstable or Unknown state. To skip this check end-user can pass Force-flag=true in the request. | |
235| | | |
236| | - "TTL": <0....N> - The timeout value for the action to run, between action received by APPC and action initiated. | |
237| | | |
238| | If no TTL value provided, the default/configurable TTL value is to be used. | |
239+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
240| action | The action to be taken by APPC, for example: Test, Start, Terminate. | Yes |
241| | | |
242| | ***NOTE:** The specific value for the action parameter is provided for each* command. | |
243+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
244| action- identifiers | A block containing the action arguments. These are used to specify the object upon which APPC LCM command is to operate. At least one action-identifier must be specified (note that vnf-id is mandatory). For actions that are at the VM level, the action-identifiers provided would be vnf-id and vserver-id. | Yes |
245+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
246| vnf-id | Identifies the VNF instance to which this action is to be applied. Required for actions. | Yes |
247+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
248| vnfc-name | Identifies the VNFC instance to which this action is to be applied. Required if the action applied to a specific VNFC. | No |
249+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
250| vserver-id | Identifies a specific VM instance to which this action is to be applied. Required if the action applied to a specific VM. (Populate the vserver-id field with the UUID of the VM) | No |
251+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
252| vf-module-id | Identifies a specific VF module to which this action is to be applied. Required if the action applied to a specific VF module. | No |
253+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
254| payload | An action-specific open-format field. | No |
255| | | |
256| | The payload can be any valid JSON string value. JSON escape characters need to be added when an inner JSON string is included within the payload, for example: "{\\" vnf -host- ip | |
257| | | |
258| | -address\\": \\"<VNF-HOST-IP-ADDRESS>\\"}". | |
259| | | |
260| | The payload is typically used to provide parametric data associated with the command, such as a list of configuration parameters. | |
261| | | |
262| | Note that not all LCM commands need have a payload. | |
263| | | |
264| | ***NOTE:** See discussion below on the use of payloads for self-service actions.* | |
265+---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
266
267
268Generic Response Format
269-----------------------
270
271
272This section describes the generic response format.
273
274The response format is applicable for both POST HTTP API and for the message body received via the EUB/DMaaP bus.
275
276
277LCM Response
278^^^^^^^^^^^^
279
280The LCM response comprises a common header and a section containing the payload and action details.
281
282The LCM response conforms to the following structure::
283
284 {
285 "output": {
286 "common-header": {
287 "api-ver": "<API\_VERSION>",
288 "flags": {
289 "ttl": <TTL\_VALUE>,
290 "force": "<TRUE\|FALSE>",
291 "mode": "<EXCLUSIVE\|NORMAL>"
292 },
293 "originator-id": "<ECOMP\_SYSTEM\_ID>",
294 "request-id": "<ECOMP\_REQUEST\_ID>",
295 "sub-request-id": "<ECOMP\_SUBREQUEST\_ID>",
296 "timestamp": "2016-08-08T23:09:00.11Z",
297 },
298 "payload": "<PAYLOAD>",
299 [Additional fields],
300 "status": {
301 "code": <RESULT\_CODE>,
302 "message": "<RESULT\_MESSAGE>"
303 }
304 }
305 }
306
307
308Table 3 LCM Response Fields
309
310+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
311| **Field** | **Description** | **Required?** |
312+======================+===========================================================================================================================================================================================================================+=====================+
313| output | The block that defines the details of the output of the command processing. Contains the common-header details. | Yes |
314+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
315| common- header | The block that contains the generic details about a request. | Yes |
316+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
317| api-ver | Identifies the API version, in X.YY format, where X denotes the major version increased with each APPC release, and YY is the minor release version. For example: | Yes |
318| | | |
319| | - 5.00 for this version | |
320+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
321| originator-id | An identifier of the calling system limited to a length of 40 characters. | Yes |
322| | | |
323| | It can be used for addressing purposes, such as to return an asynchronous response to the correct destination, in particular where there are multiple consumers of APPC APIs. | |
324+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
325| request-id | The UUID for the request ID, limited to a length of 40 characters. The unique OSS/BSS identifier for the request ID that triggers the current LCM action. Multiple API calls can be made with the same request- id. | Yes |
326| | | |
327| | The request-id is stored throughout the operations performed during a single request. | |
328+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
329| sub-request-id | Uniquely identifies a specific LCM or control action, limited to a length of 40 characters. Persists throughout the life cycle of a single request. | No |
330+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
331| timestamp | The time of the request, in ISO 8601 format, ZULU offset. For example: 2016-08-03T08:50:18.97Z. | Yes |
332+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
333| status | The status describes the outcome of the command processing. Contains a code and a message providing success or failure details. | Yes |
334| | | |
335| | ***NOTE:** See* status *for code values.* | |
336+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
337| payload | An open-format field. | No |
338| | | |
339| | The payload can be any valid JSON string value. JSON escape characters need to be added when an inner JSON string is included within the payload, for example: "{\\"upload\_config\_id\\": \\"<value\\"}". | |
340| | | |
341| | The payload is typically used to provide parametric data associated with the response to the command. | |
342| | | |
343| | Note that not all LCM commands need have a payload. | |
344| | | |
345| | ***NOTE:** The specific value(s) for the response payload, where relevant, is provided for in each* command *description.* | |
346+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
347| [Field name] | Additional fields can be provided in the response, if needed, by specific commands. | No |
348+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
349| code | A unique pre-defined value that identifies the exact nature of the success or failure status. | No |
350+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
351| message | The description of the success or failure status. | No |
352+----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
353
354
355Status Codes
356^^^^^^^^^^^^
357
358The status code is returned in the response message as the code parameter, and the description as the message parameter.
359
360The different responses are categorized as follows:
361
362**ACCEPTED**
363
364 Request is valid and accepted for processing.
365
366**ERROR**
367
368 Request invalid or incomplete.
369
370**REJECT**
371
372 Request rejected during processing due to invalid data, such as an
373 unsupported command or a non-existent service-instance-id.
374
375**SUCCESS**
376
377 Request is valid and completes successfully.
378
379**FAILURE**
380
381 The request processing resulted in failure.
382
383 A FAILURE response is always returned asynchronously via the message
384 bus.
385
386**PARTIAL SUCCESS**
387
388 The request processing resulted in partial success where at least
389 one step in a longer process completed successfully.
390
391 A PARTIAL SUCCESS response is always returned asynchronously via the
392 message bus.
393
394**PARTIAL FAILURE**
395
396 The request processing resulted in partial failure.
397
398 A PARTIAL FAILURE response is always returned asynchronously via the
399 message bus.
400
401+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
402| **Category** | **Code** | **Message / Description** |
403+=======================+================+======================================================================================================================================+
404| ACCEPTED | 100 | ACCEPTED - Request accepted |
405+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
406| ERROR | 200 | UNEXPECTED ERROR - ${detailedErrorMsg} |
407+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
408| REJECT | 300 | REJECTED - ${detailedErrorMsg} |
409+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
410| | 301 | INVALID INPUT PARAMETER -${detailedErrorMsg} |
411+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
412| | 302 | MISSING MANDATORY PARAMETER - Parameter ${paramName} is missing |
413+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
414| | 303 | REQUEST PARSING FAILED - ${detailedErrorMsg} |
415+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
416| | 304 | NO TRANSITION DEFINED - No Transition Defined for ${actionName} action and ${currentState} state |
417+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
418| | 305 | ACTION NOT SUPPORTED - ${actionName} action is not supported |
419+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
420| | 306 | VNF NOT FOUND - VNF with ID ${vnfId} was not found |
421+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
422| | 307 | DG WORKFLOW NOT FOUND - No DG workflow found for the combination of ${dgModule} module ${dgName} name and ${dgVersion} version |
423+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
424| | 308 | WORKFLOW NOT FOUND - No workflow found for VNF type |
425| | | |
426| | | ${vnfTypeVersion} and ${actionName} action |
427+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
428| | 309 | UNSTABLE VNF - VNF ${vnfId} is not stable to accept the command |
429+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
430| | 310 | LOCKING FAILURE -${detailedErrorMsg} |
431+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
432| | 311 | EXPIREDREQUEST. The request processing time exceeded the maximum available time |
433+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
434| | 312 | DUPLICATEREQUEST. The request already exists |
435+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
436| | 313 | MISSING VNF DATA IN A&AI - ${attributeName} not found for VNF ID = |
437| | | |
438| | | ${vnfId} |
439+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
440| SUCCESS | 400 | The request was processed successfully |
441+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
442| FAILURE | 401 | DG FAILURE - ${ detailedErrorMsg } |
443+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
444| | 402 | NO TRANSITION DEFINED - No Transition Defined for ${ actionName} action and ${currentState} state |
445+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
446| | 403 | UPDATE\_AAI\_FAILURE - failed to update AAI. ${errorMsg} |
447+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
448| | 404 | EXPIRED REQUEST FAILURE - failed during processing because TTL expired |
449+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
450| | 405 | UNEXPECTED FAILURE - ${detailedErrorMsg} |
451+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
452| | 406 | UNSTABLE VNF FAILURE - VNF ${vnfId} is not stable to accept the command |
453+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
454| | 450 | Requested action is not supported on the VNF |
455+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
456| PARTIAL SUCCESS | 500 | PARTIAL SUCCESS |
457+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
458| PARTIAL FAILURE | 501 - | PARTIAL FAILURE |
459| | | |
460| | 599 | |
461+-----------------------+----------------+--------------------------------------------------------------------------------------------------------------------------------------+
462
463
464Malformed Message Response
465^^^^^^^^^^^^^^^^^^^^^^^^^^
466
467A malformed message is an invalid request based on the LCM API YANG scheme specification. APPC rejects malformed requests as implemented by ODL infrastructure level.
468
469**Response Format for Malformed Requests**::
470
471 {
472 "errors": {
473 "error": [
474 {
475 "error-type": "protocol",
476 "error-tag": "malformed-message",
477 "error-message": "<ERROR-MESSAGE>",
478 "error-info": "<ERROR-INFO>"
479 }
480 ]
481 }
482 }
483
484
485**Example Response**::
486
487 {
488 "errors": {
489 "error": [
490 {
491 "error-type": "protocol",
492 "error-tag": "malformed-message",
493 "error-message": "Error parsing input: Invalid value 'Stopp' for
494 enum type. Allowed values are: [Sync, Audit, Stop, Terminate]",
495 "error-info": "java.lang.IllegalArgumentException: Invalid value
496 'Stopp' for enum type. Allowed values are: [Sync, Audit, Stop,
497 Terminate]..."
498 }
499 ]
500 }
501 }
502
503
504
505API Scope
506=========
507
508Defines the level at which the LCM command operates for the current release of APPC and the VNF types which are supported for each command.
509
510
511Commands, or actions, can be performed at one or more of the following scope levels:
512
513
514+-----------------+----------------------------------------------------------------------------------------+
515| **VNF** | Commands can be applied at the level of a specific VNF instance using the vnf-id. |
516+-----------------+----------------------------------------------------------------------------------------+
517| **VF-Module** | Commands can be applied at the level of a specific VF-Module using the vf-module-id. |
518+-----------------+----------------------------------------------------------------------------------------+
519| **VNFC** | Commands can be applied at the level of a specific VNFC instance using a vnfc-name. |
520+-----------------+----------------------------------------------------------------------------------------+
521| **VM** | Commands can be applied at the level of a specific VM instance using a vserver-id. |
522+-----------------+----------------------------------------------------------------------------------------+
523
524
525**VNF’s Types Supported**
526
527Commands, or actions, may be currently supported on all VNF types or a limited set of VNF types. Note that the intent in the 1710 release is to support all actions on all VNF types which have been successfully onboarded in a self-service mode.
528
529**Any -** Currently supported on any vnf-type.
530
531**Any (requires self-service onboarding) –** Currently supported on any vnf-type which has been onboarded using the APPC self-service onboarding process. See further discussion on self-service onboarding below.
532
533
534+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
535| **Command** | **VNF** | **VF-Module** | **VNFC** | **VM** | **VNF/VM Types Supported** |
536+========================+===============+=====================+================+==============+================================================================+
537| Audit | Yes | | | | Any (requires self-service onboarding) |
538+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
539| CheckLock | Yes | | | | Any (APPC internal command) |
540+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
541| Configure | Yes | | Yes | | Any (requires self-service onboarding) |
542+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
543| ConfigModify | Yes | | Yes | | Any (requires self-service onboarding) |
544+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
545| ConfigBackup | Yes | | | | Chef and Ansible only (requires self-service onboarding) |
546+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
547| ConfigRestore | Yes | | | | Chef and Ansible only (requires self-service onboarding) |
548+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
549| Evacuate | | | | Yes | Any (uses OpenStack Evacuate command) |
550+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
551| HealthCheck | Yes | | | | Any (requires self-service onboarding) |
552+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
553| Lock | Yes | | | | Any (APPC internal command) |
554+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
555| Migrate | | | | Yes | Any (uses OpenStack Migrate command) |
556+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
557| Rebuild | | | | Yes | Any (uses OpenStack Rebuild command) |
558+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
559| Restart | Yes | | | Yes | Any (uses OpenStack Start and Stop commands) |
560+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
561| Snapshot | | | | Yes | Any (uses OpenStack Snapshot command) |
562+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
563| Start | Yes | Yes | | Yes | Any (uses OpenStack Start command) |
564+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
565| StartApplication | Yes | | | | Chef and Ansible only (requires self-service onboarding) |
566+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
567| Stop | Yes | Yes | | Yes | Any (uses OpenStack Stop command) |
568+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
569| StopApplication | Yes | | | | Chef and Ansible only (requires self-service onboarding) |
570+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
571| Sync | Yes | | | | Any (requires self-service onboarding) |
572+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
573| Unlock | Yes | | | | Any (APPC internal command) |
574+------------------------+---------------+---------------------+----------------+--------------+----------------------------------------------------------------+
575
576
577
578Self-Service VNF Onboarding
579---------------------------
580
581The APPC architecture is designed for VNF self-service onboarding (i.e., a VNF owner or vendor through the use of tools can enable a new VNF to support the LCM API actions that are designate as self-service). The VNF must support one or more of the following interface protocols:
582
583- Netconf with uploadable Yang model (requires a Netconf server running
584 on the VNF)
585
586- Chef (requires a Chef client running on the VNF)
587
588- Ansible (does not require any changes to the VNF software)
589
590The self-service onboarding process is done using an APPC Design GUI which interacts with an APPC instance which is dedicated to self-service onboarding. The steps in the onboarding process using the APPC Design GUI are:
591
592- Define the VNF capabilities (set of actions that the VNF can
593 support).
594
595- Create a template and parameter definitions for actions which use the
596 Netconf, Chef, or Ansible protocols. The template is an xml or JSON
597 block which defines the “payload” which is included in the request
598 that is downloaded the VNF (if Netconf) or Chef/Ansible server.
599
600- Test actions which have templates/parameter definitions.
601
602- Upload the VNF definition, template, and parameter definition
603 artifacts to SDC which distributes them to all APPC instances in the
604 same environment (e.g., production).
605
606For more details, see the APPC Self-Service VNF Onboarding Guide (add link).
607
608
609
610LCM Commands
611============
612
613The LCM commands that are valid for the current release.
614
615
616Audit
617-----
618
619The Audit command compares the configuration of the VNF associated with the current request against the most recent configuration that is stored in APPC's configuration database.
620
621A successful Audit means that the current VNF configuration matches the latest APPC stored configuration.
622
623A failed Audit indicates that the configurations do not match.
624
625This command can be applied to any VNF type. The only restriction is that the VNF has been onboarded in self-service mode (which requires that the VNF supports a request to return the running configuration).
626
627The Audit action does not require any payload parameters.
628
629**NOTE:** Audit does not return a payload containing details of the comparison, only the Success/Failure status.
630
631
632+------------------------------+------------------------------------------------------+
633| **Target URL** | /restconf /operations/ appc-provider-lcm:audit |
634+------------------------------+------------------------------------------------------+
635| **Action** | Audit |
636+------------------------------+------------------------------------------------------+
637| **Action-Identifiers** | vnf-id |
638+------------------------------+------------------------------------------------------+
639| **Payload Parameters** | See below |
640+------------------------------+------------------------------------------------------+
641| **Revision History** | Unchanged in this version. |
642+------------------------------+------------------------------------------------------+
643
644|
645
646+----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+----------------------------------+
647| **Parameter** | **Description** | **Required?** | **Example** |
648+======================+===========================================================================================================================================================+=====================+==================================+
649| publish-config | \* If the publish\_config field is set to Y in the payload, then always send the running configuration from the VNF using the Data Router | Yes | "publish-config": "<Y\|N>" |
650| | | | |
651| | \* If the publish\_config field is set to N in the payload, then: | | |
652| | | | |
653| | - If the result of the audit is ‘match’ (latest APPC config and the running config match), do not send the running configuration in the Data Router | | |
654| | | | |
655| | - If the result of the audit is ‘no match’, then send the running configuration on the Data Router | | |
656+----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+----------------------------------+
657
658Audit Response
659^^^^^^^^^^^^^^
660
661The audit response returns an indication of success or failure of the audit. If a new configuration is uploaded to the APPC database, the payload contains the ‘upload\_config\_id’ and values for any records created. In addition, the configuration is sent to the ECOMP Data Router bus which may be received by an external configuration storage system.
662
663
664CheckLock
665---------
666
667The CheckLock command returns true if the specified VNF is locked; otherwise, false is returned.
668
669A CheckLock command is deemed successful if the processing completes without error, whether the VNF is locked or not. The command returns only a single response with a final status.
670
671Note that APPC locks the target VNF during any VNF command processing, so a VNF can have a locked status even if no Lock command has been explicitly called.
672
673The CheckLock command returns a specific response structure that extends the default LCM response.
674
675The CheckLock action does not require any payload parameters.
676
677+------------------------------+--------------------------------------------------------+
678| **Target URL** | /restconf/operations/appc-provider-lcm:checklock |
679+------------------------------+--------------------------------------------------------+
680| **Action** | CheckLock |
681+------------------------------+--------------------------------------------------------+
682| **Action-Identifiers** | vnf-id |
683+------------------------------+--------------------------------------------------------+
684| **Payload Parameters** | None |
685+------------------------------+--------------------------------------------------------+
686| **Revision History** | Unchanged in this version. |
687+------------------------------+--------------------------------------------------------+
688
689CheckLock Response
690^^^^^^^^^^^^^^^^^^
691
692The CheckLock command returns a customized version of the LCM
693response.
694
695
696+---------------------+---------------------------------------------------------------------------------------+--------------------+---------------------------------+
697| **Parameter** | **Description** | **Required** | **?Example** |
698+=====================+=======================================================================================+====================+=================================+
699| locked | "TRUE"\|"FALSE" - returns TRUE if the specified VNF is locked, otherwise FALSE. | No | "locked": "<TRUE\|FALSE>" |
700+---------------------+---------------------------------------------------------------------------------------+--------------------+---------------------------------+
701
702
703**Example**::
704
705 {
706 "output": {
707 "status": {
708 "code": <RESULT\_CODE>, "message": "<RESULT\_MESSAGE>"
709 },
710 "common-header": {
711 "api-ver": "<API\_VERSION>",
712 "request-id": "<ECOMP\_REQUEST\_ID>", "originator-id":
713 "<ECOMP\_SYSTEM\_ID>",
714 "sub-request-id": "<ECOMP\_SUBREQUEST\_ID>", "timestamp":
715 "2016-08-08T23:09:00.11Z",
716 "flags": {
717 "ttl": <TTL\_VALUE>, "force": "<TRUE\|FALSE>",
718 "mode": "<EXCLUSIVE\|NORMAL>"
719 }
720 },
721 "locked": "<TRUE\|FALSE>"
722 }
723
724
725Configure
726---------
727
728Configure a VNF or a VNFC on the VNF after instantiation.
729
730A set of configuration parameter values specified in the configuration template is included in the request. Other configuration parameter values may be obtained from an external system.
731
732A successful Configure request returns a success response.
733
734A failed Configure action returns a failure response and the specific failure messages in the response block.
735
736+------------------------------+--------------------------------------------------------+
737| **Target URL** | /restconf/operations/appc-provider-lcm:configure |
738+------------------------------+--------------------------------------------------------+
739| **Action** | Configure |
740+------------------------------+--------------------------------------------------------+
741| **Action-Identifiers** | vnf-id |
742+------------------------------+--------------------------------------------------------+
743| **Payload Parameters** | See below |
744+------------------------------+--------------------------------------------------------+
745| **Revision History** | Unchanged in this version. |
746+------------------------------+--------------------------------------------------------+
747
748|
749
750+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
751| **Payload Parameter** | **Description** | **Required?** | **Example** |
752| | | | |
753+=================================+============================================================================================================================================================================================================================================================================================================+=====================+=================================================================+
754| request- parameters | The parameters required to process the request must include the host-ip-address to connect to the VNF, if Netconf. A template-name may also be included in the event that a specific configuration template needs to be identified. If the request is vnfc-specific, the vnfc-type must be included. | Yes | |
755| | | | "payload": |
756| | | | |
757| | | | "{\"request-parameters |
758| | | | |
759| | | | \": { |
760| | | | |
761| | | | \"host-ip-address\": \”value\”, |
762| | | | |
763| | | | \”vnfc-type\”: \”value\”’, |
764| | | | |
765| | | | \”template-name\”: \”name\” |
766| | | | |
767| | | | } |
768| | | | |
769| | | | \"configuration- parameters\": {\"<CONFIG- PARAMS>\"} |
770| | | | |
771+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
772| configuration- parameters | A set of instance specific configuration parameters should be specified. If provided, APPC replaces variables in the configuration template with the values supplied. | No | |
773+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
774
775
776Configure Response
777^^^^^^^^^^^^^^^^^^
778
779The Configure response returns an indication of success or failure of the request. If successful, the return payload contains the ‘upload\_config\_id’ and values for any records created. In addition, the configuration is sent to the ECOMP Data Router bus which may be received by an external configuration storage system.
780
781SO is creating the VNFC records in A&AI. APPC is updating the VNFC status.
782
783ConfigModify
784------------
785
786Modifies the configuration on a VNF or VNFC in service.
787
788A successful ConfigModify request returns a success response.
789
790A failed ConfigModify action returns a failure response code and the specific failure message in the response block.
791
792**NOTE:** See also `Configure <#_bookmark35>`__
793
794+------------------------------+-----------------------------------------------------------+
795| **Target URL** | /restconf/operations/appc-provider-lcm:configmodify |
796+------------------------------+-----------------------------------------------------------+
797| **Action** | ConfigModify |
798+------------------------------+-----------------------------------------------------------+
799| **Action-Identifiers** | Vnf-id |
800+------------------------------+-----------------------------------------------------------+
801| **Payload Parameters** | See below |
802+------------------------------+-----------------------------------------------------------+
803| **Revision History** | Unchanged in this version. |
804+------------------------------+-----------------------------------------------------------+
805
806|
807
808+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
809| **Payload Parameter** | **Description** | **Required?** | **Example** |
810+=================================+============================================================================================================================================================================================================================================================================================================+=====================+=================================================================+
811| request- parameters | The parameters required to process the request must include the host-ip-address to connect to the VNF, if Netconf. A template-name may also be included in the event that a specific configuration template needs to be identified. If the request is vnfc-specific, the vnfc-type must be included. | Yes | "payload": |
812| | | | |
813| | | | "{\"request-parameters |
814| | | | |
815| | | | \": { |
816| | | | |
817| | | | \"host-ip-address\": \”value\”, |
818| | | | |
819| | | | \”vnfc-type\”: \”value\”’ |
820| | | | |
821| | | | \”template-name\”: \”name\”, |
822| | | | |
823| | | | } |
824| | | | |
825| | | | \"configuration- parameters\": {\"<CONFIG- PARAMS>\"} |
826+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
827| configuration- parameters | A set of instance specific configuration parameters should be specified. If provided, APPC replaces variables in the configuration template with the values supplied. | No | |
828+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
829
830If successful, this request returns a success response.
831
832A failed Configure action returns a failure response and the specific failure message in the response block.
833
834ConfigModify Response
835^^^^^^^^^^^^^^^^^^^^^
836
837The ConfigModify response returns an indication of success or failure of the request. If successful, the return payload contains the ‘upload\_config\_id’ and values for any records created. In addition, the configuration is sent to the ECOMP Data Router bus which may be received by an external configuration storage system.
838
839ConfigBackup
840------------
841
842Stores the current VNF configuration on a local file system (not in APPC). This is limited to Ansible and Chef. There can only be one stored configuration (if there is a previously saved configuration, it is replaced with the current VNF configuration).
843
844A successful ConfigBackup request returns a success response.
845
846A failed ConfigBackup action returns a failure response code and the specific failure message in the response block.
847
848+------------------------------+-----------------------------------------------------------+
849| **Target URL** | /restconf/operations/appc-provider-lcm:configbackup |
850+------------------------------+-----------------------------------------------------------+
851| **Action** | ConfigBackup |
852+------------------------------+-----------------------------------------------------------+
853| **Action-Identifiers** | Vnf-id |
854+------------------------------+-----------------------------------------------------------+
855| **Payload Parameters** | See below |
856+------------------------------+-----------------------------------------------------------+
857| **Revision History** | New in this version. |
858+------------------------------+-----------------------------------------------------------+
859
860|
861
862+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
863| **Payload Parameter** | **Description** | **Required?** | **Example** |
864+=================================+====================================================================================================================================================================================+=====================+=================================================================+
865| request- parameters | The parameters required to process the request must include the host-ip-address to connect to the VNF (for Chef and Ansible, this will be the url to connect to the server). | Yes | "payload": |
866| | | | |
867| | | | "{\"request-parameters |
868| | | | |
869| | | | \": { |
870| | | | |
871| | | | \"host-ip-address\": \”value\” |
872| | | | |
873| | | | } |
874| | | | |
875| | | | \"configuration- parameters\": {\"<CONFIG- PARAMS>\"} |
876+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
877| configuration- parameters | A set of instance specific configuration parameters should be specified, as required by the Chef cookbook or Ansible playbook. | No | |
878+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
879
880ConfigBackup Response
881^^^^^^^^^^^^^^^^^^^^^
882
883The ConfigBackup response returns an indication of success or failure of the request.
884
885ConfigRestore
886-------------
887
888Applies a previously saved configuration to the active VNF configuration. This is limited to Ansible and Chef. There can only be one stored configuration.
889
890A successful ConfigRestore request returns a success response.
891
892A failed ConfigRestore action returns a failure response code and the specific failure message in the response block.
893
894+------------------------------+------------------------------------------------------------------------------------------+
895| **Target URL** | /restconf/operations/appc-provider-lcm:configrestore |
896+------------------------------+------------------------------------------------------------------------------------------+
897| **Action** | ConfigRestore |
898+------------------------------+------------------------------------------------------------------------------------------+
899| **Action-Identifiers** | Vnf-id |
900+------------------------------+------------------------------------------------------------------------------------------+
901| **Payload Parameters** | `request-parameters <#_bookmark24>`__, `configuration-parameters <#_bookmark26>`__ |
902+------------------------------+------------------------------------------------------------------------------------------+
903| **Revision History** | New in this version. |
904+------------------------------+------------------------------------------------------------------------------------------+
905
906|
907
908+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
909| **Parameter** | **Description** | **Required?** | **Example** |
910+=================================+====================================================================================================================================================================================+=====================+=================================================================+
911| request- parameters | The parameters required to process the request must include the host-ip-address to connect to the VNF (for Chef and Ansible, this will be the url to connect to the server). | Yes | "payload": |
912| | | | |
913| | | | "{\"request-parameters |
914| | | | |
915| | | | \": { |
916| | | | |
917| | | | \"host-ip-address\\": \”value\” |
918| | | | |
919| | | | } |
920| | | | |
921| | | | \"configuration- parameters\": {\"<CONFIG- PARAMS>\"} |
922+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
923| configuration- parameters | A set of instance specific configuration parameters should be specified, as required by the Chef cookbook or Ansible playbook. | No | |
924+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
925
926ConfigRestore Response
927^^^^^^^^^^^^^^^^^^^^^^
928
929The ConfigRestore response returns an indication of success or failure of the request.
930
931Evacuate
932--------
933
934Evacuates a specified VM from its current host to another. After a successful evacuate, a rebuild VM is performed if a snapshot is available (and the VM boots from a snapshot.
935
936The host on which the VM resides needs to be down.
937
938If the node is not specified in the request, it will be selected by relying on internal rules to evacuate. The Evacuate action will fail if the specified target host is not UP/ENABLED.
939
940After Evacuate, the rebuild VM can be disabled by setting the optional `rebuild-vm <#_bookmark43>`__ parameter to false.
941
942A successful Evacuate action returns a success response. A failed Evacuate action returns a failure.
943
944**NOTE:** The command implementation is based on Openstack functionality. For further details, see http://developer.openstack.org/api-ref/compute/.
945
946+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+
947| **Target URL** | /restconf/operations/appc-provider-lcm:evacuate |
948+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+
949| **Action** | Evacuate |
950+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+
951| **Action-identifiers** | Vnf-id, vserver-id |
952+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+
953| **Payload Parameters** | `vm-id <#_bookmark40>`__, `identity-url <#_bookmark41>`__, `tenant-id <#_bookmark42>`__, `rebuild-vm <#_bookmark43>`__, `targethost-id <#_bookmark44>`__ |
954+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+
955| **Revision History** | Unchanged in this version. |
956+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+
957
958|
959
960+----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+---------------------------------------+
961| **Parameter** | **Description** | **Required?** | **Example** |
962+======================+==================================================================================================================================================================================+=====================+=======================================+
963| vm-id | The unique identifier (UUID) of the resource. For backwards- compatibility, this can be the self- link URL of the VM. | Yes | "payload": |
964| | | | |
965| | | | "{\"vm-id\": \"<VM-ID> |
966| | | | |
967| | | | \", |
968| | | | |
969| | | | \"identity-url\": |
970| | | | |
971| | | | \"<IDENTITY-URL>\", |
972| | | | |
973| | | | \"tenant-id\\": \"<TENANT-ID> |
974| | | | |
975| | | | \", |
976| | | | |
977| | | | \"rebuild-vm\": \"false\", |
978| | | | |
979| | | | \"targethost-id\": |
980| | | | |
981| | | | \"nodeblade7\"}" |
982+----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+---------------------------------------+
983| identity- url | The identity URL used to access the resource | No | |
984+----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+---------------------------------------+
985| tenant-id | The id of the provider tenant that owns the resource | No | |
986+----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+---------------------------------------+
987| rebuild- vm | A boolean flag indicating if a Rebuild is to be performed after an Evacuate. The default action is to do a Rebuild. It can be switched off by setting the flag to "false". | No | |
988+----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+---------------------------------------+
989| targethost- id | A target hostname indicating the host the VM is evacuated to. By default, the cloud determines the target host. | No | |
990+----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+---------------------------------------+
991
992HealthCheck
993-----------
994
995This command runs a VNF health check and returns the result.
996
997A health check is VNF-specific. For a complex VNF, APPC initiates further subordinate health checks.
998
999HealthCheck is a VNF level command which interrogates the VNF in order to determine the health of the VNF and the VNFCs. The HealthCheck will be implemented differently for each VNF.
1000
1001
1002+------------------------------+-----------------------------------------------------------+
1003| **Target URL** | /restconf/operations/appc-provider-lcm:health-check |
1004+------------------------------+-----------------------------------------------------------+
1005| **Action** | HealthCheck |
1006+------------------------------+-----------------------------------------------------------+
1007| **Action-Identifiers** | Vnf-id |
1008+------------------------------+-----------------------------------------------------------+
1009| **Payload Parameters** | `vnf-host-ip-address <#_bookmark46>`__ |
1010+------------------------------+-----------------------------------------------------------+
1011| **Revision History** | Changed in this version. |
1012+------------------------------+-----------------------------------------------------------+
1013
1014|
1015
1016+-----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------+-------------------------------------+
1017| **Paramete** | **Description** | **Required?** | **Example** |
1018+=============================+================================================================================================================================================================+==================+=====================================+
1019| vnf- host-ip- address | The IP address used to connect to the VNF, using a protocol such as SSH. For example, for a vSCP VNF, the floating IP address of the SMP should be used. | Yes | "payload": |
1020| | | | |
1021| | | | "{\"vnf-host-ip-address\": |
1022| | | | |
1023| | | | \"10.222.22.2\"}" |
1024+-----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------+-------------------------------------+
1025
1026Lock
1027----
1028
1029Use the Lock command to ensure exclusive access during a series of critical LCM commands.
1030
1031The Lock action will return a successful result if the VNF is not already locked or if it was locked with the same request-id, otherwise the action returns a response with a reject status code.
1032
1033Lock is a command intended for APPC and does not execute an actual VNF command. Instead, lock will ensure that ONAP is granted exclusive access to the VNF.
1034
1035When a VNF is locked, any subsequent sequential commands with same request-id will be accepted. Commands associated with other request-ids will be rejected.
1036
1037The Lock command returns only one final response with the status of the request processing.
1038
1039APPC locks the target VNF during any VNF command processing. If a lock action is then requested on that VNF, it will be rejected because the VNF was already locked, even though no actual lock command was explicitly invoked.
1040
1041+------------------------------+---------------------------------------------------+
1042| **Target URL** | /restconf/operations/appc-provider-lcm:lock |
1043+------------------------------+---------------------------------------------------+
1044| **Action** | Lock |
1045+------------------------------+---------------------------------------------------+
1046| **Action-Identifier** | Vnf-id |
1047+------------------------------+---------------------------------------------------+
1048| **Payload Parameters** | None |
1049+------------------------------+---------------------------------------------------+
1050| **Revision History** | Unchanged in this version. |
1051+------------------------------+---------------------------------------------------+
1052
1053Migrate
1054-------
1055
1056Migrates a running target VM from its current host to another.
1057
1058A destination node will be selected by relying on internal rules to migrate. Migrate calls a command in order to perform the operation.
1059
1060Migrate suspends the guest virtual machine, and moves an image of the guest virtual machine's disk to the destination host physical machine. The guest virtual machine is then resumed on the destination host physical machine and the disk storage that it used on the source host physical machine is freed.
1061
1062The migrate action will leave the VM in the same Openstack state the VM had been in prior to the migrate action. If a VM was stopped before migration, a separate VM-level restart command would be needed to restart the VM after migration.
1063
1064A successful Migrate action returns a success response and the new node identity in the response payload block.
1065
1066A failed Migrate action returns a failure and the failure messages in the response payload block.
1067
1068**NOTE:** The command implementation is based on Openstack functionality. For further details, see http://developer.openstack.org/api-ref/compute/.
1069
1070+--------------------------------+-----------------------------------------------------------------------------------------------+
1071| **Target URL** | /restconf/operations/appc-provider-lcm:migrate |
1072+--------------------------------+-----------------------------------------------------------------------------------------------+
1073| **Action** | Migrate |
1074+--------------------------------+-----------------------------------------------------------------------------------------------+
1075| **Action-Identifiers** | Vnf-id, vserver-id |
1076+--------------------------------+-----------------------------------------------------------------------------------------------+
1077| \ **Payload Parameters** | `vm-id <#_bookmark52>`__, `identity-url <#_bookmark54>`__, `tenant-id <#_bookmark55>`__ |
1078+--------------------------------+-----------------------------------------------------------------------------------------------+
1079| **Revision History** | Unchanged in this version. |
1080+--------------------------------+-----------------------------------------------------------------------------------------------+
1081
1082Payload Parameters
1083
1084+---------------------+-------------------------------------------------------------------------+---------------------+------------------------------------+
1085| **Parameter** | **Description** | **Required?** | **Example** |
1086+=====================+=========================================================================+=====================+====================================+
1087| vm-id | The unique identifier (UUID) of | Yes | |
1088| | the resource. For backwards- compatibility, this can be the self- | | "payload": |
1089| | link URL of the VM. | | |
1090| | | | "{\\"vm-id\": \\"<VM-ID>\\", |
1091| | | | \\"identity-url\\": |
1092| | | | |
1093| | | | \\"<IDENTITY-URL>\\", |
1094+---------------------+-------------------------------------------------------------------------+---------------------+ +
1095| identity- url | The identity url used to access the resource | No | \\"tenant-id\\": \\"<TENANT- |
1096| | | | ID>\\"}" |
1097+---------------------+-------------------------------------------------------------------------+---------------------+ +
1098| tenant-id | The id of the provider tenant that owns the resource | No | |
1099+---------------------+-------------------------------------------------------------------------+---------------------+------------------------------------+
1100
1101Rebuild
1102-------
1103
1104Recreates a target VM instance to a known, stable state.
1105
1106Rebuild calls an OpenStack command immediately and therefore does not expect any prerequisite operations to be performed, such as shutting off a VM.
1107
1108APPC only supports the rebuild operation for a VM that boots from image (snapshot), i.e., APPC rejects a rebuild request if it determines the VM boots from volume (disk).
1109
1110A successful rebuild returns a success response and the rebuild details in the response payload block. A failed rebuild returns a failure and the failure messages in the response payload block.
1111
1112**NOTE:** The command implementation is based on Openstack functionality. For further details, see http://developer.openstack.org/api-ref/compute/.
1113
1114+------------------------------+-----------------------------------------------------------------------------------------------+
1115| **Target URL** | /restconf/operations/appc-provider-lcm:rebuild |
1116+------------------------------+-----------------------------------------------------------------------------------------------+
1117| **Action** | Rebuild |
1118+------------------------------+-----------------------------------------------------------------------------------------------+
1119| **Action-identifiers** | Vnf-id, vserver-id |
1120+------------------------------+-----------------------------------------------------------------------------------------------+
1121| **Payload Parameters** | `vm-id <#_bookmark52>`__, `identity-url <#_bookmark54>`__, `tenant-id <#_bookmark55>`__ |
1122+------------------------------+-----------------------------------------------------------------------------------------------+
1123| **Revision History** | Unchanged in this version. |
1124+------------------------------+-----------------------------------------------------------------------------------------------+
1125
1126Restart
1127-------
1128
1129Use the Restart command to restart a VNF or a single VM. The generic VNF Restart uses a simple restart logic where all VM’s are stopped and re-started.
1130
1131The generic Restart operation is invoked either for the VM or the VNF level.
1132
1133+------------------------------+-----------------------------------------------------------------------------------------------------------------+
1134| **Input Block** | api-ver must be set to 2.00 for *VNF Restart* |
1135+------------------------------+-----------------------------------------------------------------------------------------------------------------+
1136| **Target URL** | /restconf/operations/appc-provider-lcm:restart |
1137+------------------------------+-----------------------------------------------------------------------------------------------------------------+
1138| **Action** | Restart |
1139+------------------------------+-----------------------------------------------------------------------------------------------------------------+
1140| **Action-identifiers** | Vnf-id is required; if restart is for a single VM, then vserver-id is also required. |
1141+------------------------------+-----------------------------------------------------------------------------------------------------------------+
1142| **Payload Parameters** | For *VNF* Restart: `host Identity <#_bookmark57>`__, `vnf-host-ip-address <#_bookmark58>`__ |
1143| | |
1144| | For *VM* Restart: `vm-id <#_bookmark52>`__, `identity-url <#_bookmark54>`__, `tenant-id <#_bookmark55>`__ |
1145+------------------------------+-----------------------------------------------------------------------------------------------------------------+
1146| **Revision History** | Revised in this version. |
1147+------------------------------+-----------------------------------------------------------------------------------------------------------------+
1148
1149Payload Parameters for **VNF Restart**
1150
1151+-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+---------------------------------------+
1152| **Parameter** | **Description** | **Required?** | **Example** |
1153+=============================+===================================================================================================================================================================+=====================+=======================================+
1154| Cloud Identity | The identity URL of the OpenStack host on which the VNF resource was created. If not provided, this information will be retrieved from the properties file. | No | "payload": |
1155| | | | "{\\" vnf-host-ip-address \\": |
1156| | | | |
1157| | | | \\"<VNF\_FLOATING\_IP\_ADDRESS> |
1158| | | | \\", |
1159| | | | \\" hostIdentity \\": |
1160| | | | \\"<OpenStack IP Address>\\" |
1161| | | | }" |
1162+-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+---------------------------------------+
1163| vnf- host-ip- address | The IP address used to connect to the VNF, using a protocol such as SSH. For example, for a vSCP VNF, the floating IP address of the SMP should be used. | Yes | |
1164+-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+---------------------------------------+
1165
1166Payload Parameters for **VM Restart**
1167
1168+---------------------+-------------------------------------------------------------------------+---------------------+------------------------------------+
1169| **Parameter** | **Description** | **Required?** | **Example** |
1170+=====================+=========================================================================+=====================+====================================+
1171| vm-id | The unique identifier (UUID) of | Yes | |
1172| | the resource. For backwards- compatibility, this can be the self- | | "payload": |
1173| | link URL of the VM. | | |
1174| | | | "{\\"vm-id\\": \\"<VM-ID>\\", |
1175| | | | \\"identity-url\\": |
1176| | | | |
1177+---------------------+-------------------------------------------------------------------------+---------------------+ \\"<IDENTITY-URL>\\", |
1178| identity- url | The identity url used to access the resource | No | \"tenant-id\": \"<TENANT- |
1179| | | | ID>\"}" |
1180+---------------------+-------------------------------------------------------------------------+---------------------+ +
1181| tenant-id | The id of the provider tenant that owns the resource | No | |
1182+---------------------+-------------------------------------------------------------------------+---------------------+------------------------------------+
1183
1184Snapshot
1185--------
1186
1187Creates a snapshot of a VM.
1188
1189The Snapshot command returns a customized response containing a reference to the newly created snapshot instance if the action is successful.
1190
1191This command can be applied to any VNF type. The only restriction is that the particular VNF should be built based on the generic heat stack.
1192
1193**NOTE:** The command implementation is based on Openstack functionality. For further details, see http://developer.openstack.org/api-ref/compute/.
1194
1195+------------------------------+-----------------------------------------------------------------------------------------------------+
1196| **Target URL** | /restconf/operations/appc-provider-lcm:snapshot |
1197+------------------------------+-----------------------------------------------------------------------------------------------------+
1198| **Action** | Snapshot |
1199+------------------------------+-----------------------------------------------------------------------------------------------------+
1200| **Action-identifiers** | Vnf-id is required. If the snapshot is for a single VM, then the vserver-id is also required. |
1201+------------------------------+-----------------------------------------------------------------------------------------------------+
1202| **Payload Parameters** | `vm-id <#_bookmark52>`__, `identity-url <#_bookmark54>`__, `tenant-id <#_bookmark55>`__ |
1203+------------------------------+-----------------------------------------------------------------------------------------------------+
1204| **Revision History** | Unchanged in this version. |
1205+------------------------------+-----------------------------------------------------------------------------------------------------+
1206
1207Payload Parameters
1208
1209+---------------------+-------------------------------------------------------------------------+---------------------+------------------------------------+
1210| **Parameter** | **Description** | **Required?** | **Example** |
1211+=====================+=========================================================================+=====================+====================================+
1212| vm-id | The unique identifier (UUID) of | Yes | |
1213+---------------------+-------------------------------------------------------------------------+---------------------+------------------------------------+
1214| | the resource. For backwards- compatibility, this can be the self- | | "payload": |
1215| | link URL of the VM. | | |
1216| | | | "{\\"vm-id\": \\"<VM-ID> |
1217| | | | |
1218| | | | \\", |
1219| | link URL of the VM. | | \\"identity-url\\": |
1220| | | | |
1221| | | | \\"<IDENTITY-URL>\\", |
1222+---------------------+-------------------------------------------------------------------------+---------------------+ +
1223| identity- url | The identity url used to access the resource | No | \\"tenant-id\\": \\"<TENANT- |
1224| | | | ID>\\"}" |
1225+---------------------+-------------------------------------------------------------------------+---------------------+------------------------------------+
1226| tenant-id | The id of the provider tenant that owns the resource | No | |
1227+---------------------+-------------------------------------------------------------------------+---------------------+------------------------------------+
1228
1229Snapshot Response
1230^^^^^^^^^^^^^^^^^
1231
1232The Snapshot command returns an extended version of the LCM response.
1233
1234The Snapshot response conforms to the `standard response format <#_bookmark5>`__, but has the following additional field.
1235
1236Additional Parameters
1237
1238+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+---------------------------------------+
1239| **Parameter** | **Description** | **Required** | **?Example** |
1240+=====================+========================================================================================================================================================+====================+=======================================+
1241| snapshot-id | The snapshot identifier created by cloud host. This identifier will be returned only in the final success response returned via the message bus. | No | "snapshot-id": "<SNAPSHOT\_ID>" |
1242+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+---------------------------------------+
1243
1244Start
1245-----
1246
1247Use the Start command to start a VNF, VF-Module, or VM that is stopped or not running.
1248
1249**NOTE:** The command implementation is based on Openstack functionality. For further details, see http://developer.openstack.org/api-ref/compute/.
1250
1251+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1252| **Target URL** | /restconf/operations/appc-provider-lcm:start |
1253+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1254| **Action** | Start |
1255+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1256| **Action-identifiers** | Vnf-id is required; vf-module-id or vserver-id is also required if the action is at vf-module or vm level, respectively. |
1257+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1258| **Payload Parameters** | None |
1259+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1260| **Revision History** | Revised in this version. |
1261+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1262
1263StartApplication
1264----------------
1265
1266Starts the VNF application, if needed, after a VM is instantiated/configured or after VM start or restart. Supported using Chef cookbook or Ansible playbook only.
1267
1268A successful StartApplication request returns a success response.
1269
1270A failed StartApplication action returns a failure response code and the specific failure message in the response block.
1271
1272+------------------------------+---------------------------------------------------------------+
1273| **Target URL** | /restconf/operations/appc-provider-lcm:startapplication |
1274+------------------------------+---------------------------------------------------------------+
1275| **Action** | StartApplication |
1276+------------------------------+---------------------------------------------------------------+
1277| **Action-Identifiers** | Vnf-id |
1278+------------------------------+---------------------------------------------------------------+
1279| **Payload Parameters** | See below |
1280+------------------------------+---------------------------------------------------------------+
1281| **Revision History** | New in this version. |
1282+------------------------------+---------------------------------------------------------------+
1283
1284|
1285
1286+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
1287| **Payload Parameter** | **Description** | **Required?** | **Example** |
1288+=================================+====================================================================================================================================================================================+=====================+=================================================================+
1289| request- parameters | The parameters required to process the request must include the host-ip-address to connect to the VNF (for Chef and Ansible, this will be the url to connect to the server). | Yes | "payload": |
1290| | | | |
1291| | | | "{\\"request-parameters |
1292| | | | \\": { |
1293| | | | \\"host-ip-address\\": \\”value\\” |
1294| | | | } |
1295| | | | \\"configuration- parameters\\": {\\"<CONFIG- PARAMS>\\"} |
1296+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
1297| configuration- parameters | A set of instance specific configuration parameters should be specified, as required by the Chef cookbook or Ansible playbook. | No | |
1298+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
1299
1300StartApplication Response
1301^^^^^^^^^^^^^^^^^^^^^^^^^
1302
1303The StartApplication response returns an indication of success or failure of the request.
1304
1305Stop
1306----
1307
1308Use the Stop command to start a VNF, VF-Module, or VM that is stopped or not running.
1309
1310**NOTE:** The command implementation is based on Openstack functionality. For further details, see http://developer.openstack.org/api-ref/compute/.
1311
1312+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1313| **Target URL** | /restconf/operations/appc-provider-lcm:stop |
1314+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1315| **Action** | Stop |
1316+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1317| **Action-identifiers** | Vnf-id is required; vf-module-id or vserver-id is also required if the action is at vf-module or vm level, respectively. |
1318+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1319| **Payload Parameters** | None |
1320+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1321| **Revision History** | Revised in this version. |
1322+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
1323
1324StopApplication
1325---------------
1326
1327Stops the VNF application gracefully (not lost traffic), if needed, prior to a Stop command. Supported using Chef cookbook or Ansible playbook only.
1328
1329A successful StopApplication request returns a success response.
1330
1331A failed StopApplication action returns a failure response code and the specific failure message in the response block.
1332
1333+------------------------------+--------------------------------------------------------------+
1334| **Target URL** | /restconf/operations/appc-provider-lcm:stopapplication |
1335+------------------------------+--------------------------------------------------------------+
1336| **Action** | StopApplication |
1337+------------------------------+--------------------------------------------------------------+
1338| **Action-Identifiers** | Vnf-id |
1339+------------------------------+--------------------------------------------------------------+
1340| **Payload Parameters** | See below |
1341+------------------------------+--------------------------------------------------------------+
1342| **Revision History** | New in this version. |
1343+------------------------------+--------------------------------------------------------------+
1344
1345|
1346
1347+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
1348| **Payload Parameter** | **Description** | **Required?** | **Example** |
1349+=================================+====================================================================================================================================================================================+=====================+=================================================================+
1350| request- parameters | The parameters required to process the request must include the host-ip-address to connect to the VNF (for Chef and Ansible, this will be the url to connect to the server). | Yes | "payload": |
1351| | | | "{\\"request-parameters |
1352| | | | \\": { |
1353| | | | \\"host-ip-address\\": \\”va lue\\” |
1354| | | | } |
1355| | | | \\"configuration- parameters\\": {\\"<CONFIG- PARAMS>\\"} |
1356+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
1357| configuration- parameters | A set of instance specific configuration parameters should be specified, as required by the Chef cookbook or Ansible playbook. | No | |
1358+---------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+-----------------------------------------------------------------+
1359
1360StopApplication Response
1361^^^^^^^^^^^^^^^^^^^^^^^^
1362
1363The StopApplication response returns an indication of success or failure of the request.
1364
1365Sync
1366----
1367
1368The Sync action updates the current configuration in the APPC store with the running configuration from the device.
1369
1370A successful Sync returns a success status.
1371
1372A failed Sync returns a failure response status and failure messages in the response payload block.
1373
1374This command can be applied to any VNF type. The only restriction is that the VNF has been onboarded in self-service mode (which requires that the VNF supports a request to return the running configuration).
1375
1376+------------------------------+---------------------------------------------------+
1377| **Target URL** | /restconf/operations/appc-provider-lcm:sync |
1378+------------------------------+---------------------------------------------------+
1379| **Action** | Sync |
1380+------------------------------+---------------------------------------------------+
1381| **Action-identifiers** | Vnf-id |
1382+------------------------------+---------------------------------------------------+
1383| **Payload Parameters** | None |
1384+------------------------------+---------------------------------------------------+
1385| **Revision History** | Unchanged in this version. |
1386+------------------------------+---------------------------------------------------+
1387
1388Unlock
1389------
1390
1391Run the Unlock command to release the lock on a VNF and allow other clients to perform LCM commands on that VNF.
1392
1393Unlock is a command intended for APPC and does not execute an actual VNF command. Instead, unlock will release the VNF from the exclusive access held by the specific request-id allowing other requests for the VNF to be accepted.
1394
1395The Unlock command will result in success if the VNF successfully unlocked or if it was already unlocked, otherwise commands will be rejected.
1396
1397The Unlock command will only return success if the VNF was locked with same `request-id <#_bookmark4>`__.
1398
1399The Unlock command returns only one final response with the status of the request processing.
1400
1401Note: APPC locks the target VNF during any command processing. If an Unlock action is then requested on that VNF with a different request-id, it will be rejected because the VNF is already locked for another process, even though no actual lock command was explicitly invoked.
1402
1403+------------------------------+-----------------------------------------------------+
1404| **Target URL** | /restconf/operations/appc-provider-lcm:unlock |
1405+------------------------------+-----------------------------------------------------+
1406| **Action** | Unlock |
1407+------------------------------+-----------------------------------------------------+
1408| **Action-identifiers** | Vnf-id |
1409+------------------------------+-----------------------------------------------------+
1410| **Payload Parameters** | None |
1411+------------------------------+-----------------------------------------------------+
1412| **Revision History** | Unchanged in this version. |
1413+------------------------------+-----------------------------------------------------+
1414