Table of Contents
In the Casablanca release, ONAP will support the ability to both manually and automatically scale out a VNF component. Below is the sequence diagram for how scaling will work.
At a high level the way Scale Out will work is:
VF_Modules(VNFC’s) may be scaled out with either one of two methods:
Using VID, the operator will choose to scale out a VNFC by picking a
An operator may define an operating policy (and associated guard policies) to trigger a scaling operation automatically.
As an example, the operating policy may be when the output of an application load balancer crosses a bandwidth threshold, then increase the number of instances of the application.
Examples of a guard policies:
- If a scaling operation has run within the past X minutes, then do not scale.
- If the number of instance is <=
MAX_INSTANCES, then do not scale.
VID or Policy sends the Scale Out Request to SO.
When SO receives the Scaling request it will first send a request to the appropriate controller (APPC or SDNC) to execute a health check on the VNF.
Once the health check has been run, SO executes the Heat Template associated with the VF Module requested by the VID Operator or the operational policy.
After the new component(s) have been instantiated SO calls the responsible controller (via DMaaP) to configure the new instances using Ansible, Chef, or Netconf.
Finally a health check is run to ensure that the entire VNF is Operating as it should.
For VNFs to make use of the Manual Scaling Capabilities of ONAP, they must support the following functionality:
- VNFs must support a Healthcheck as described in: ONAP Management Requirements.
- R-43413 states that a “VNF MUST utilize a modular Heat Orchestration Template design to support scaling”. The description of this design may be found in the ONAP VNF Modularity Overview of the Heat Requirements.
VF_Moduleto be scaled must be built according to the VNF Modularity Rules for Incremental Modules
- Configuration of the VNF must be done via NETCONF, Chef, or Ansible as described in the Configuration Management