Versions Compared

Old Version 67

changes.mady.by.user Samuli Silvius

Saved on

compared with

New Version 68

changes.mady.by.user Samuli Silvius

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

PlantUML Render Macro
@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 : 1. POST ../vnflcm/v1/subscriptions
External_VNFM -> SOL002_Adapter : 2. 201 Created
end

...
alt  Receive VnfLcmOperationOccurrenceNotification
External_VNFM -> SOL002_Adapter: 3. POST ../notifyEndpoint
SOL002_Adapter -> AAI: 4. 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: 5. transform ETSI data model to ONAP model and create DMaaP message for ONAP
SOL002_Adapter -> DMaaP: 6. POST Notification
Policy -> DMaaP: 7. Consume notifications targeted to Policy
Policy -> Policy: 8. Execute User's policy if exists
Policy -> "APPC/CDS": 9. POST (through DMaaP or directly): Policy action to configure VNF
end


@enduml

...

  1. SOL002Adapter subscribes in it's startup notifications from external VNFM. Filter used can be wide i.e. all notifications.
  2. When adapter get's success for subscription request it starts to listen notifications. If subscription fails, adapter continues to try again forever with suitable interval. 
  3. When something happens (e.g. VNF instantiated), external VNFM send notification
  4. Query AAI for VNF details. GET query to MANO may also be needed if vnfIds in systems are not same.
  5. SOL002Adapter makes necessary translation from ETSI model to ONAP model
  6. Agreed (to be agreed) message format of LCM notification is posted to DMaaP
  7. Consume LCM notification
  8. 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.
  9. Execute policy action towards actoractor (through DMaaP or directly)


Heal