One of the primary advantages of a virtualized cloud infrastructure is the ability to maximize resource utilization. In a PNF environment, resource allocation is relatively static and therefore enough capacity needs to be available for peak loads. This leads to many inefficiencies during normal operating times. In the software controlled environment of virtualized resources, ONAP can allocate resources to a VNF as they are needed. Scaling is the process utilized by ONAP to change the amount of resources allocated to a VNF
In priority order:
- Model Driven Control Loop Design
- Further automation Scaling Use Case (Tech Mahindra)
- Eliminate the need to manually enter a Dummy VF_Module
- Fix Naming Policy Issues
- Simplify CLAMP Scale Out Screen.
- Manual Scale In (Manually remove instances of a VNFC)
- Auto Scale In (Automatically remove instances of a VNFC)
- Auto VNF Configuration
- Updates to Manual and Auto Scale Out
- Homing and Capacity Check
- Architecture approved Controller_Type Lookup
- Support TOSCA Based VNFs
Bold projects have been approved for Dublin. Italicized projects have been pushed to a future release
Dynamic scaling gives an operator the tools it needs to maximize efficiency of the resources dedicated to the cloud. ONAP's control environment allows it to assign resources where they are most needed and reallocate them when they are needed by different VNF. This allows the cloud environment to achieve a much higher resource utilization level than the old data centers it is replacing.
Past releases of ONAP have developed the capability of adding additional resources (VMs/VF_Modules) to a VNF as the demand for the VNF grows. In the Dublin release we will add the capability to reduce the number of resources (VMs/VF_Modules) assigned to a VNF so that those resources can be used by other VNFs as needed.
AT&T, Ericsson, Nokia
Past releases of scaling have consistently added a lot of functionality. In the Dublin Release, the Scaling Use Case will focus on hardening the current functionality and make it easier to add future capabilities.
In the Dublin timeframe the Scaling Use Case team will partner with the Closed Loop Subcommittee to focus our resources on Service Assurance and the Closed Loop.
Scaling Use Case Presentations
Closed Loop Design Proposal for R4
Scaling Use Case Team Meetings
For Dublin we will be using both the weekly Scaling call as well as the weekly Closed Loop call to progress the Scaling Use Case.
Weekly Scaling Meeting
Time: UTC 1400 / China 2200 / Eastern 0900 / Pacific 0600
Weekly Closed Loop Subcommittee Meeting
Time: UTC 1500 / China 2300 / Eastern 1000 / Pacific 0700