-
Story
-
Resolution: Won't Do
-
Medium
-
None
-
None
-
Dublin SO Sprint 2
As a user of ONAP, I want SO to send an end of orchestration event when a given transaction is completed. This allows for other parts of ONAP, such as POMBA, to trigger activity knowing the orchestration flow is complete. This event should contain the following information
- Mandatory
- Resource identifier
- Resource of top level flow, such as service instance id
- Resource Type
- Resource type of resource identifier, such as service
- Resource identifier
- Optional
- Status of orchestration - success, partial success, error
- State post orchestration - created, deleted, etc.
- model instance id, model invariant id - references to object in SDC.
This event should be sent via DMaaP. As this notification is going to be consumed as a means of triggering audits and other activity that assumes whatever piece of orchestration has reached a meaningful state, then this notification should either
- Only be sent when the orchestration is truly done from a macro perspective. For example, the service is successfully created and is functional
- The orchestration event is sent more frequently for finer grain orchestration but there is enough information in the notification so the consumer can react accordingly - ie tell when we are truly done or at a point that the consumer knows how to act upon.