Table of Contents

Background

Each time a new PNF is connected to the network, or reseted to factory settings, a PNF registration process is expected to happen.
Within this process, a VES pnfRegistration event is sent from a PNF instance to the ONAP/DCAE/VES collector.
In order to support Nomadic PNF use-case of a broader BBS use-case, an initial registration of a PNF needs to be distinguished from a re-registration.

...

1. If a registration attempt is executed for a PNF Instance, which has an existing entry in the ONAP/AAI, and when that PNF instance is associated with an active (orchestration-status==active) service instance
   → Re-Registration

Service/Resource instance state machine

SO project defined the State Machines, related to the service and resource (PNF/VNF) instances life-cycle.
The state machines are defined here.

For PNFs, the state machine (simplified is stated as follows):

Register (when a PNF instance is created) → Registered (after initial pnfRegistration) → Assign → Assigned → ConfigAssign → ConfigAssigned → Configure → Configured → Active

Note:

At this moment (ONAP/Casablanca release), the orchestration states are not managed by teh PNF PnP building block (states were not defined before).
Setting proper states within the PNF PnP BB according to this StateMachine will probably be added at the beginning of ONAP/El Alto release.

→