Versions Compared

Old Version 3

changes.mady.by.user Miroslaw Medrek

Saved on

compared with

New Version 4

changes.mady.by.user Miroslaw Medrek

Saved on

Key

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



Table of Contents

...

Gliffy
nameONAP ETSI Alignment Copy
pagePinpageid1468541021

Feature Descriptions

Feature

Description

SOL002 Adapter executes VNF LCM operations towards VNFM

SOL002 Adapter utilizes VNFM exposed SOL002 VNF LCM interface:

  • ONAP DCAE/Policy executes Close Loop based on VNF or VNFC level events
  • ONAP Controller or SOL002 Adapter directly can react to Policy trigger as Policy actor to perform LCM operation for VNF
  • SOL002 Adapter is used to translate LCM action to SOL002 interface format towards external VNFM
  • External VNFM performs VNF resource changes (VNFC or VNF level)
SOL002 Adapter subscribes and consumes VNF LCM notifications from VNFM

SOL002 Adapter utilizes VNFM exposed SOL002 VNF LCM interface to subscribe LCM Notifications:

  • SOL002 Adapter subscribes LCM notifications at startup (e.g. listen all notifications)
  • SOL002 Adapter receives LCM notification and emits event to DMaaP e.g. for Policy to consume
  • User should model action Policy to react to these events on ONAP side
  • Based on modeled action some operation can be done. E.g. with ONAP Controller to configure VNF. Clean Close loop etc.
SOL002 Adapter receives subscription and sends VNF Indicator notifications to VNFM

SOL002 Adapter exposes VNF Indicator subscription endpoint and sends Indicator notifications to external VNFM:

  • VNFM calls SOL002 Adapter to subscribe VNF Indicator notifications
  • SOL002 Adapter stores subscriptions according to standard
  • SOL002 Adapter starts to listen DMaaP events based on subscription
  • SOL002 Adapter consumes any matching events and translates events to SOL002 Indicator notification and sends to subscriber
SOL002 Adapter receives VNF configuration request from VNFM

SOL002 Adapter exposes VNF configuration endpoint for external VNFM:

  • SOL002 Adapter performs EM role (Ve-Vnfm-em)
  • VNFM calls SOL002 Adapter VNF configuration interface
  • SOL002 Adapter translates the configuration request into APPC/CDS/GNFC - specific API-call
  • APPC/CDS/GNFC configures specific VNF or VNFC accordingly

...

  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 (to be agreed message format and fields) message format of LCM notification is posted to DMaaP. Another (stretch goal and better long term option) solution is to create VES event and feed it to ONAP's DCAE for normal LC processing.
  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)

...