ONAP Casablanca Release delivers platform capabilities that support scaling up resources. The use case has been designed and implemented to fully take advantage of existing functionalities, using newer APIs and technologies whenever possible. Compared to the previous version delivered for Beijing, which supported only manual trigger and one VNF type, the new use case adds:
- A design phase in which users define and deploy policies and closed-loops from CLAMP;
- Closed-loop- and Policy-based automation;
- Guard policies that allow/deny scale out operations based on frequency limits or max number of instances already scaled;
- New and improved workflow that leverages SO ability to compose building blocks on the fly;
- Use of Generic Resource APIs for VNF instantiation and lifecycle management (as opposed to the old VNF APIs);
- VNF health check;
- Support for multiple VNF types;
- Support for multiple VNF controllers, i.e. APPC (officially supported) and SDNC (experimental);
- Ability to define lifecycle management configuration from CLAMP (automated trigger) or VID (manual trigger).
This is a different kind of Use Case for ONAP that Integrates many of the projects to show how they can work together to perform a complex but essential activity.
Known Issues and Resolutions
- When running closed loop-enabled scale out, the closed loop designed in CLAMP may conflict with the default closed loop defined for the old vLB/vDNS use case.
Resolution