Operators require to reserve resources for future usages. Such events could be predicted traffic increase due to concert, natural disasters etc. However, at present, OpenStack cannot reserve resources for future usage. OpenStack requires instant instantiation of Virtual Machines (VMs) in order to occupy resources intended to be reserved. Blazar can reserve compute resources for future by keeping the VMs in shelved mode. However, such reserved resources can also be used for scaling out rather than new VM instantiation. Blazar do not support network and storage resource reservation yet.
Fig. 1 shows the Resource Reservation for future usage scenario. Providing a start time to allocate the reserved resources is one approach to solve this problem. VMs won’t be instantiated until the start time arrives. This also provides a resource guarantee for the period expressed by start and end time. In Fig. 1, User/Client represents the requestor and the consequent consumer of the resources who will own the VMs to be instantiated on those resources. In ETSI NFV terminology, User/Client would be the NFV Orchestrator (NFVO) and VNF Manager (VNFM).
Along with Resource Reservation, this Project includes Capacity Management where the VIM performs the resource pool capacity management and interacts with NFVO to exchange capacity information.
StormForgeopen source software will be contributed to OPNFV with complete functional implementation of the N/B API specifications covering Resource Capacity management and Resource Reservation service
Stormifyopen source software will be contributed to OPNFV with complete functional implementation of data model abstractions with dynamic generation of REST/JSON N/B API specifications
pkgcloudopen source software will be integrated to provide library abstraction to OpenStack APIs