Versions Compared

Old Version 10

changes.mady.by.user Miroslaw Medrek

Saved on

compared with

New Version 11

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 SOL002 VNF Indicator interface
pageid68541021


Feature Descriptions

Feature

Description

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 DCAE 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 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 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

Epic and User Story

Epic

User Story

Description

Is Guilin?JIRA
SOL002
Adapter




Epic: SOL002 Adapter will support EM-triggered VNF/VNFC ManagementPartially

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2427

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.
Yes

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2745

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)
No
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
No
Documentation for SOL002 Adapter featuresDocumentation for SOL002 Adapter featuresYes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2431









SOL002 Adapter Architecture

...

  1. SOL002Adapter will be the SO microservice component

  2. SOL002Adapter will be registered in the Microservice Bus (via helm chart)
  3. SOL002Adapter will be registered manually in the External System Register
  4. SOL002Adapter on startup will use ESR to get external VNFM data
  5. SOL002Adapter on startup will register in VNFM for all LCM notifications
  6. BPMN will trigger LCM operation which will go to SOL003Adapter
  7. SOL003Adapter triggers the LCM flow in VNFM
  8. ETSI LCM notification is sent from VNFM and goes to SOL002Adapter
  9. SOL002Adapter will query A&AI to get VNF data
  10. SOL002Adapter will construct and publish ONAP event via DCAE/DMaaP. At the current phase it will be DMaaP event t but later on it will evolve to VES event.
  11. Policy will consume DMaaP event
  12. Policy will call configuration component to configure VNF

  13. For the integration testing, the VNFM Simulator in the CSIT container will be used

...

The following SOL002 operations will be supported:

API ActionActorMethodURIDescription
Subscribe for LCM notificationsSOL002 Adapter → VNFM POST
/vnflcm/v1/subscriptions (LccnSubscriptionRequest)
To create subscription for LCM notification
Notify on VNF lifecycle changesVNFM → SOL002 AdapterPOST
/lcm/v1/vnf/instances/notifications (VnfLcmOperationOccurrenceNotification)
To notify SOL002 adapter on VNF lifecycle changes





SOL002 Operation Sequence Flows

...

  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)

...