Reservations are used to book capacity on a given Reservation Target type in the future. Reservations enable you to do reservation-aware capacity management that provides more detailed future saturation information with respect to the capacity management based on time forecasting models and trends.
You can manage resource reservation and increase future capacity by onboarding, which enables you to automatically evaluate and predict spare capacity.
List of Supported Platforms
The following tabs allow you to configure various parameters used by reservation-aware capacity management.
|Reservations (Managing)||A Reservation is an event in the future that represents a request to allocate a given resource OR set of resources (based on Service or System templates) for usage by a specific owner (for instance, a Project, User, Department, Tenant, etc) for a specific time period. The date from which the reservation is effective, a reservation is in the realized state. For example, five Virtual Machines from “SmallLinux” template for project “Email” from January 1st 2015 to April 31st 2015.|
|Onboardings||An Onboarding event is an event in the future that represents a known allocation of resources to the infrastructure. For example, additional memory needs to be allocated to a data center in New York. You can add an additional host to a cluster or add a cluster to the Capacity Pool. This incremental change in capacity is taken into consideration for estimating the available resources for future reservation events.|
|Reservation Targets||A Reservation Target is a system that contains resources such as CPU, Memory, and Storage. They can also contain reservation items such as Virtual Machines in a VMware vSphere cluster. You can evaluate the status of Reservation Targets (and its resources), and subsequently plan events to allocate additional resources as required.|
|Capacity Pools||Assign or unassign a capacity pool that was created in the Workspace to be used for Reservations. Capacity Pools are a logical aggregation of Reservation Targets based on business rules. Capacity Pool should never be selected by available capacity, and should be driven by the business purpose of the reservation. For example, you can group Reservation Targets into Capacity Pools based on the location.|
|Tenants||Allocate and manage resource quotas available to individual Tenants, which are shared by Reservation items. You can associate multiple Reservation items to use the resources allocated to a tenant. You can view and manage tenants added to the domain set as the root domain for the Tenants tab.|
Add and manage system and service templates available for Reservations and Onboardings. You can select templates from the workspace tree and make them available for reservation items and onboarding events.
|Placement Rules||Create and manage Placement Rules that enforce user-defined criteria based on tags during placement of Reservation items into the Reservation Target. For example, a template with tag "FastStorage" should be placed on a Reservation Target with tag "Gold".|
|Settings||Configure default behavior of the Reservation system. For example, you can update the default resource comparison method.|