SOL003_104: VnfLcmOperationOccurrenceNotification datatype updated

src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml

@@ -621,7 +621,7 @@ definitions:
       lifecycle caused by a VNF LCM operation occurrence. The support of the
       notification is mandatory.
       This notification shall be triggered by the VNFM when there is a change
-      in the VNF lifecycle caused by a VNF LCM operation occurrence,
+      in the state of a VNF LCM operation occurrence that changes the VNF lifecycle,
       including:
       * Instantiation of the VNF
       * Scaling of the VNF instance (including auto-scaling)
@@ -633,18 +633,20 @@ definitions:
       * Modification of VNF instance information and/or VNF configurable
         properties through the "PATCH" method on the "Individual VNF instance"
         resource.
-      If this is the initial notification about the start of a VNF LCM
-      operation occurrence, it is assumed that the notification is sent by the
-      VNFM before any action (including sending the grant request) is taken as
-      part of the LCM operation. Due to possible race conditions, the "start"
-      notification, the grant request and the LCM operation acknowledgment can
-      arrive in any order at the NFVO, and the NFVO shall be able to handle
-      such a situation.
-      If this is a notification about a final or intermediate result state of
-      a VNF LCM operation occurrence, the notification shall be sent after
-      all related actions of the LCM operation that led to this state have
-      been executed. The new state shall be set in the VnfLcmOpOcc resource
-      before the notification about the state change is sent.
+      Clause 5.6.2 defines the states and state transition of a VNF LCM operation occurrence,
+      and also specifies details of the notifications to be emitted at each state transition.
+      If this is the initial notification about the start of a VNF LCM operation occurrence,
+      it is assumed that the notification is sent by the VNFM before any action (including sending the grant request)
+      is taken as part of the LCM operation. Due to possible race conditions, the "start" notification,
+      the grant request and the LCM operation acknowledgment (i.e. the "202 Accepted" response)
+      can arrive in any order at the NFVO, and the NFVO shall be able to handle such a situation.
+      If this is a notification about a final or intermediate result state of a VNF LCM operation occurrence,
+      the notification shall be sent after all related actions of the LCM operation that led
+      to this state have been executed.
+      The new state shall be set in the "Individual VNF LCM operation occurrence" resource before
+      the notification about the state change is sent.
+      See clause 5.6.2.2 for further provisions regarding sending this notification, including
+      in cases of handling LCM operation errors.
     type: object
     required:
       - id
@@ -768,20 +770,20 @@ definitions:
         $ref: "#/definitions/VnfInfoModifications"
       changedExtConnectivity:
         description: >
-          Information about changed external connectivity, if this
-          notification represents the result of a lifecycle operation
-          occurrence. Shall be present if the "notificationStatus" is set to
-          "RESULT" and the "operation" is set to "CHANGE_EXT_CONN".
-          Shall be absent otherwise.
+          Information about changed external connectivity, if this notification
+          represents the result of a lifecycle operation occurrence.
+          Shall be present if the "notificationStatus" is set to "RESULT" and
+          the "operation" has made any changes to the external connectivity of
+          the VNF instance. Shall be absent otherwise.
         type: array
         items:
           $ref: "#/definitions/ExtVirtualLinkInfo"
       error:
         description: >
           Details of the latest error, if one has occurred during executing
-          the LCM operation. Shall be present if the "operationState"
-          attribute is "FAILED_TEMP" or "FAILED", and shall be absent
-          otherwise.
+          the LCM operation (see clause 6.3 of ETSI GS NFV-SOL 013).
+          Shall be present if the "operationState" attribute is "FAILED_TEMP" or "FAILED",
+          and shall be absent otherwise.
         $ref: "SOL002SOL003_def.yaml#/definitions/ProblemDetails"
       _links:
         description: >