| Table of Contents |
|---|
Introduction
...
| Gliffy | ||||
|---|---|---|---|---|
|
VNF Configuration (Ve-Vnfm-em)
...
- SOL002Adapter queries the ESR for external VNFM details.
- SOL002Adapter subscribes in it's startup notifications from external VNFM. Filter used can be wide i.e. all notifications.
- 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.
- When something happens (e.g. VNF instantiated), external VNFM sends notification
- 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)
- 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)
- 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.
- Consume LCM notification
- 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.
- Execute policy action towards actor (through DMaaP or directly)
...