Versions Compared

Key

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


Table of Contents

Introduction

...

  1. LCM Notification Subscribing/Consuming
    • At startup SOL002 Adapter can subscribe LCM notifications from VNFM
    • When receiving notifications SOL002 Adapter can perform actions e.g.:
      • Clean up VNF related Close Loop when receiving VNF terminated notification
      • Configure VNF (Similar as in VNF Configuration use case.) VNF  when receiving VNF Instantiated/Healed/Scaled notification.
  2. LCM Action execution (NOT FOR GUILIN)
    • ONAP Close Loop gets triggered from VES event or by other means and can trigger SOL002 Adapter to perform action using VNF LCM interface

...

External VNFM can subscribe to SOL002 VNF Indicator notifications.

SOL002 Adapter reads VNF spesific specific VES events from DMaaP according to subscriptions and converts events to SOL002 interface format and sends as Notify events to external VNFM.

...

  1. SOL002Adapter queries the ESR for external VNFM details.
  2. SOL002Adapter subscribes in it's startup notifications from external VNFM. Filter used can be wide i.e. all notifications.
  3. 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. 
  4. When something happens (e.g. VNF instantiated), external VNFM sends notification
  5. Query AAI for VNF details. GET query to MANO may also be needed if vnfIds in systems are not same. (Optional step, needed if model translation needed)
  6. SOL002Adapter makes necessary translation from ETSI model to ONAP model. (To be checked: details of translation or if translation even needed - it depends on SOL003 integration)
  7. Agreed VES event (to be agreed message format and fields) message format of LCM notification is posted to DCAE
  8. Consume LCM notification
  9. 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.
  10. Execute policy action towards actor (through DMaaP or directly)

...