@startuml
participant SOL002_Adapter
participant External_VNFM
participant AAI
participant DMaaP
participant Policy
participant "APPC/CDS"
participant Policy
hnote over AAI : Precondition: VNF is instantiated (e.g. through SOL003 and with external VNFM) and VNFM is manually 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 VnfIdentifierCreationNotificationVnfLcmOperationOccurrenceNotification
External_VNFM -> SOL002_Adapter : POST ../notifyEndpoint
SOL002_Adapter -> AAI External_VNFM: GET ../vnflcm/v1/vnf_instances/{vnfInstanceId}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 AAI: createPOST Notification
Policy generic-vnf record
SOL002_Adapter-> DMaaP: Consume notifications targeted to Policy
Policy -> Policy: create policies (if needed)
end
...
alt Receive VnfLcmOperationOccurrenceNotification Instantiation Complete
External_VNFM -> SOL002_Adapter : POST ../notifyEndpoint
SOL002_Adapter -> AAI: get generic-vnf information
SOL002_Adapter -> "APPC/CDS": configure VNF
end
...
alt Receive VnfIdentifierDeletionNotification
External_VNFM -> SOL002_Adapter : POST ../notifyEndpoint
SOL002_Adapter -> AAI: delete generic-vnf record
SOL002_Adapter -> Policy: delete related policies
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
...end
@enduml
| 