...
- AAI entry creation for a new PNF instance (identified based on correlationID)
- Hibernation of a workflow instance in case an AAI entry is incomplete (missing PNF`s OAM IP addresses)
- Re-Hydration upon reception of a pnfRegistration event from a PNF
- In Beijing release, the VES event is used - domain "other"
ONAP Casablanca work is described here: Casablanca: SO PNF PnP algorithm
Beijing release
Initional version of the PNF PnP flow was contributed in the Beijing release.
This flow is checking, if an AAI entry exists (if not - this entry is created), and then it checks, if there is at least a single IP address available for that entry.
If there is one, the control is passed to higher-level workflow; if not - the workflow is hibernates, and continues, when a pnfReady notification reaches SO.
...
| Gliffy | ||||
|---|---|---|---|---|
|
Casablanca release
Within the Casablanca release, the SO PNF PnP sub-flow is modified.
The modification targets waiting for the pnfReady event in any case (irrespective of the PNF`s AAI entry contents).
PNF PnP algorithm block diagram - Casablanca release
| Gliffy | ||||
|---|---|---|---|---|
|