...
This event is the output of PRH PNF re-registration handling and is used to trigger Policy engine to taking for actions on the associated HSIA service.
DCAE_CL_Event
| Code Block |
|---|
| language | text |
|---|
| firstline | 1 |
|---|
| title | DCAE Control Loop Event |
|---|
| linenumbers | true |
|---|
| collapse | true |
|---|
|
|
A&AI Enrichment
The moving ONT associated (through pnfName) service ID is looked up in A&AI and enriched in the A&AI portion of the above DCAE_CL_Event which trigger the operational policy in the operational policy defined below.
...
Policy
Apex Engine Triggering
PDP-A Configuration (JSON)
| Code Block |
|---|
| language | text |
|---|
| firstline | 1 |
|---|
| title | Nomadic ONT PDP-A Configuration |
|---|
| linenumbers | true |
|---|
| collapse | true |
|---|
|
|
Policy Schema
Logic Artifacts
Pdp-D Option
Operational Policy
| Code Block |
|---|
| language | text |
|---|
| firstline | 1 |
|---|
| title | Nomadic ONT Operation Policy |
|---|
|
...
| | linenumbers | true |
|---|
| collapse | true |
|---|
|
|
SO
...
Recipe
Notes:
Interestingly, this is the first case where DCAE/Policy seem playing roles together in a non-closed/loop or service assurance in sense of usage/solution in ONAP domain, However, this does not really matter in the sense of micro services since service is a service as long as it provides the functionality that meets the requirements in a solution, An argument could be that Policy engine does not have to be introduced in this case, However, the important functionality for policy engine is to decouple action takers from the trigger pullers and ultimately establish robust policy driving on this platform w/o code change.
