@startuml
participant SOL002_Adapter
participant External_VNFM
participant AAI
participant DMaaP
participant Policy
participant "APPC/CDS"
hnote over AAI : Precondition: VNF is instantiated (e.g. through SOL003 and with external VNFM) and VNFM is registered in ESR
...
alt Subscribe to LCM Notifications after startup
SOL002_Adapter -> External_VNFM : POST ../vnflcm/v1/subscriptions
External_VNFM -> SOL002_Adapter : 201 Created
end
...
alt Receive VnfLcmOperationOccurrenceNotification
External_VNFM -> SOL002_Adapter: POST ../notifyEndpoint
SOL002_Adapter -> AAI: GET generic-vnf to make mapping. GET query to MANO may also be needed if vnfIds in systems are not same.
SOL002_Adapter -> SOL002_Adapter: transform ETSI data model to ONAP model and create DMaaP message for ONAP
SOL002_Adapter -> DMaaP: POST Notification
Policy -> DMaaP: Consume notifications targeted to Policy
Policy -> Policy: If Operational Policy reacting to LCM notifications is created as part of normal VNF modeling/instantiation,
then user's policy is run.
It's up to user's policy what it does and following steps is an example for configuring a VNF with ONAP controller.
Policy -> "APPC/CDS": POST (through DMaaP or directly): Policy action to configure VNF
end
@enduml
| 