Under Construction

This is a page that analyzes the self serve control loops and its possible designs. Some of it might not really fit this feature but might spill over to others.

How to handle (at least) two levels of Policy parameter value filling?

The existing code seems to divide policy definitions to two distinct parts, the type and the instance, as is common for many modeling systems. However, it would seem the "natural" flow of service design and instantiation needs more phases and these would need to be encoded.

Example service with multiple control loops

The following diagrams shows a hypothetical simplified EPC (4G core network) with only some scaling control loops included. This is still only a very small sample of control loops that would be needed for it in reality if all of them would be implemented at ONAP level. Still, this sample tries to be complex enough compared to current demo cases to showcase some issues with the simplest extensions of current approach. 

PGW and SGW can be considered to be VNFs as the basic case but the control loop design and management should be the same if they are implemented using some other supported orchestration instead, like kubernetes. Also PNFs should work similarly, but some actions like scale out are not available. Only scaling control loops are included for simplicity. Each VNF can scale along two dimensions (or aspects): user plane and control plane and the choice between these is encoded in the operational policy action towards SO. All control loops are based on TCA for simplicity.