...

Main PNF PnP flow steps

1. A user onboards a PNF package, and creates a service which utilizes the PNF based resource (not shown on a figure below)
2. A user instantiates a PNF-enabled service, providing a correlationID parameter
   1. Service instantiation creates a valid AAI entry for a service instance, and an AAI entry for a PNF resource instance.
      CorrelationID parameter is used to fill-in the pnf-name AAI attribute in the PNF instance entry.
   2. Service Orchestration hibernates the service instance creation flow, adding the correlationID as a SO workflow instance search key, within SO event listener
3. When a PNF is installed, it is expected to issue a VES "Registration" event. This event shall be received in the ONAP/DCAE/VES collector, and passed to a dedicated DMaaP topic.
   1. That event shall contain a vendor name and a device serial number, which will be used to create a correlationID
4. The PNF Registration Handler (PRH) reads the events from "registration" DMaaP topic, and processes them
   1. It updates the AAI entry with valid OAM IP addresses of a PNF device
   2. It publishes a PNF_READY event in the dedicated DMaaP topic, this event contains a correlationID generated based on the VES registration event
5. The PNF_READY event is read by the SO event listener, and an appropriate service instantiatio workflow instance is re-hydrated.
6. Service instantiation continues from that step (e.g. SO might send a configuration commande thru a controller to the PNF instance)

Sequence diagram - PNF PnP

...

Development status

Development Status

PNF PnP testing scope

1. WHO IS TESTING - what company, team, and people will be doing the testing & responsibilities for testing.
2. TEST ENVIRONMENT - which does the lab & test environment.
3. RESOURCES NEEDED - what resources are needed.
4. WHO IS CONTRIBUTING RESOURCES - what resources will be provided and by whom/what company.

...