Defining Booking Requests
Defining Booking Requests
#330050
Booking requests have a profile strength that indicates how much information has been captured about the booking request. The more details that you add when you create the booking request, the higher the profile strength. See How the Profile Strength is Calculated for details.
When creating a new booking request, a set amount of mandatory information needs to be entered to enable proper routing, for instance selecting a reference system that is used to populate several values in the booking request, such as the required vCPUs, memory and OS. Other information about the booking request can also be populated to ensure the booking is routed to the ideal hosting venue and to enforce specific policy rules during placement and rebalancing, such as keeping load balancing members and security zones apart based on the load balancing group and security zone specified. This type of information can also be inherited if it has been included with a reference system.
To begin defining your booking request, navigate to the Route and Reserve Demand page to the Route Demand screen. Click Add. The New Guest Booking Request dialog box is displayed and needs to be defined, section by section.
Step 1: Defining Guest's Booking Information
Table: Fields in the Guest's Booking Information Section
Field |
Description |
---|---|
Guest's Booking Information |
|
System Name * |
Add the expected VM name. |
Customer Name |
Add the name of the VM owner. |
Planned Start Date * |
This date is based on the Densify server’s time zone, which is shown in the above figure with a GMT offset "(UTC -4:00)". Enter the expected date that the VM will be needed. The calendar picker shows the date based on the Densify server’s time zone. The Today button allows you to choose today's date for immediate placement. |
Hold Reservation <n> days after Planned Start Date |
Enter the number of days after the Planned Start Date to hold the booking, in case the incoming VM is late. Enter 0 if you do not want a grace period. |
Copies |
Enter the number of copies you need if you want to create multiple copies of booking requests. Note: Although you can create up to 999 booking requests at one time, your system will require significant processing time if you create more than 100 copies. |
Project |
Enter the project name or application that this VM is associated with. After the new booking request is saved, it is grouped and displayed under the project name in both the Booking Requests to be Routed pane and Reservation Details pane. |
Customer Email |
Enter the email for the person who requested the VM. |
Description |
Enter an optional description, to a maximum of 1024 characters. |
Step 2: Defining Guest's Resource Request
Table: Fields in the Guest's Resource Request Section
Field |
Description |
---|---|
Guest's Resource Request |
|
CPUs * |
The Original/From Reference System column shows the values of the reference system and these values can be reused or overridden in the Requested column for the new VM. Selecting a reference system is mandatory. If required, override the CPU value in the Requested column with the number of vCPUs required for the new VM. |
Memory (GB) * |
If required, override the memory value in the Requested column with the memory requirement for the new VM. |
OS * |
Shows the OS from the reference system. If you need to change the operating system, select a different reference system with the OS type that is the same as the new VM. |
Reference System * |
Select a reference system to use its values for the requested system. Selecting a reference system is mandatory but values can be overridden in the Requested column. Note that other requirements and attribute values set on the reference system will be loaded when that reference system is selected. |
Preferred Environment |
Select the preferred environment for this system. Note: This field is not constrained by the global filter. |
Preferred Hosting Venue |
Select the preferred hosting venue for this system. This field is only enabled once a preferred environment has been selected. After selecting a preferred environment and hosting venue, you can route the booking request directly by clicking the Route button. See Routing from the Booking Request Dialog Box. Note: This field is not constrained by the global filter. |
Disk * |
If the reference system has an associated disk, those disk values are populated in the lower section. If you want to change the disk values, you can override them. If the VM is associated with multiple disks, such as when the operating system, the database, and the log files for a VM are each located on a different disk, click Add Disk to add disk information. The VM will only be routed to hosting venues that contain datastores of the appropriate tier (each disk may be required to belong to a different datastore because of security, performance, etc.) and that have enough capacity to host the booking request's disks. |
Provisioned Space (GB) |
If required, you can override the provisioned space value with the amount of space (GB) for the datastore that is required for this disk. This field is ignored during routing if 0 or no value is specified. |
Datastore Preference |
Specify the preferred datastore for this disk. If the datastore preference is specified in the Workload disk definition, Densify will try to respect the preferred placement according to the best candidate environment and hosting venue selected. If the preferred datastore is not available in the selected hosting venue, does not satisfy the tier condition, or does not have enough capacity, then the next suitable datastore available in the venue will be used. Regardless if the preferred datastore is used during routing, the Datastore Preference value is still preserved in the Workload disk definition after placement.
Note: If a preferred datastore is set, then that setting will override the sensor placement strategy (i.e. balanced/fill and spill). |
Tiers |
Select the storage tier required for this disk. |
Used Space (GB) |
If required, you can override the used space value with the amount of used space (GB) for the datastore required for this disk. This field is ignored during routing if 0 or no value is specified. |
Step 3: Defining Guest's Utilization Profile
Table: Fields in the Guest's Utilization Profile Section
Field |
Description |
---|---|
Guest's Utilization Profile |
|
Workload Profile * |
Select a workload profile from the list below that best reflects the new workload. Note: The workload profile is inherited from the reference system when a reference system is selected or changed. This will replace any existing workload profile value. |
Workload Type |
Select a workload type from the list below. After selecting the workload profile and type, the corresponding chart is shown. |
A workload profile is a model used for characterizing the expected utilization levels and patterns for multiple resource types, and a workload type is a resource utilization metric associated with a single system or a group of systems. You need to select a workload profile and type for the booking request that best reflects this new VM so the required resources are accurately calculated for this new workload.
Each profile, such as Memory Intensive, Medium Utilization, etc. has several associated workload types, i.e. CPU utilization and Disk I/O Operations. Review the available profiles in the following table. Review their corresponding workload charts to determine which option to use for your bookings.
Table: Sample Representative Workloads
Workload Profile |
Description |
CPU |
Actual Memory |
Disk I/O Operations |
Network I/O Activity |
---|---|---|---|---|---|
CPU_Intensive_Peak |
Workload with a high level of peak CPU utilization. |
Very High Peak (100%), Nominal Sustained (20%) |
Nominal (70% Actual, 30% Active) |
Nominal |
Nominal |
CPU_Intensive_Sustained |
Workload with a high level of sustained CPU utilization. |
High Sustained (60%), High Peak (80%) |
Nominal (70% Actual, 30% Active) |
Nominal |
Nominal |
Disk_Intensive |
Workload with high level disk I/O activity. |
Nominal (40% Peak, 20% Sustained) |
Nominal (70% Actual, 30% Active) |
High |
Nominal |
Low_Utilization |
Workload with low levels of resource utilization (CPU, memory, disk and network I/O). |
Low (20% Peak, 2% Sustained) |
Low (20% Actual, 2% Active) |
Low |
Low |
Medium_Utilization |
Workload with medium levels of resource utilization. |
Nominal (40% Peak, 20% Sustained) |
Nominal (70% Actual, 30% Active) |
Nominal |
Nominal |
Memory_Intensive |
Workload with high levels of memory utilization. |
Nominal (40% Peak, 20% Sustained) |
High (90% Actual, 50% Active) |
Nominal |
Nominal |
Network_Intensive |
Workload with high level of network I/O activity |
Nominal (40% Peak, 20% Sustained) |
Nominal (70% Actual, 30% Active) |
Nominal |
High |
Zero_Utilization |
Workload with zero resource utilization. |
N/A |
N/A |
N/A |
N/A |
Step 4: Defining Guest's Security Requirements
Table: Fields in the Guest's Security Requirements Section
Field |
Description |
---|---|
Guest's Security Requirements |
|
Data Jurisdiction |
Select the jurisdiction for this workload, such as Canada or US. |
Compliance |
Select the compliance for this workload, such as PCI or HIPAA. |
Encryption and Key Management |
Select the encryption key management for this workload, such as 128-bit based or 256-bit based. |
Identity and Access Management |
Select the identity and access management (IAM) requirements for this workload, such as Active Directory. |
Security Zone |
Select the security zone for the VM if applicable. |
Network Isolation |
Select the network isolation capabilities for this workload, such as Logical or Physical. |
Intel TXT Support |
Select if this workload supports Intel Trusted Execution Technology. |
Step 5: Defining Guest's Business Requirements
Table: Fields in the Guest's Business Requirements Section
Field |
Description |
---|---|
Guest's Business Requirements |
|
Location |
Select the location for this VM. |
Service Level |
Select the service level required by this VM. |
Department |
Select the department for this VM. |
Step 6: Defining Guest's Technical Requirements
Table: Fields in the Guest's Technical Requirements
Field |
Description |
---|---|
Guest's Technical Requirements |
|
Hosting Platform |
Select the hosting platform for the VM, e.g. Amazon Web Services, VMware. |
Context Switches |
Enter the number of context switches per second that the VM will require. |
Disk IO (Ops) |
Enter the Disk IO requirement for the VM in operations per second. |
Network IO (Packets) |
Enter the Network IO requirement for the VM in packets per second. |
Application Tier |
Select the application tier for the VM if applicable. |
High Availability Group |
Select the high availability group for the VM if applicable. |
Allocation Sync Group |
Select the allocation sync group if applicable. |
Software Licenses |
Select the software licenses for the VM, e.g. Windows and MSSQL. |
IP Addresses Assigned |
Enter the number of IP addresses to be assigned to this booking, from your defined IP address pool sensors. Typically this will be set to 1, but can be set to values >1 if there are multiple NICs or if the VM needs multiple IP interfaces for other reasons. |
Hypervisor Type |
Select the hypervisor type for the VM, e.g. Hyper-V, VMware, PowerVM. |
Disk IO (Bytes) |
Enter the Disk IO requirement for the VM in bytes per second. |
Network IO (Bytes) |
Enter the Network IO requirement for the VM in bytes per second. |
Operational Environment |
Select the operational environment for the VM if applicable. |
Load Balancing Group |
Select the load balancing group for the VM if applicable. |
Static Source Placement |
Select whether VMs should not be moved during rebalancing and defragmentation. |
License Group |
Select the license group for this workload, such as database or platform. |
Editing Booking Request Details
After the booking request has been created but is still unrouted, you can select and then Edit all details for the request except for the reference system.
Editing One or More Booking Requests
You can edit multiple booking requests at the same time.
Select the specific projects or the specific booking requests, using the standard SHIFT or CTRL key for multi-select. If different values have been entered previously for different booking requests, the field will show "multiple values". Any value that you enter will overwrite any value previously entered.
Routing from the Booking Request Dialog Box
If you know the environment and hosting venue where you want to place the new booking request, you can route the booking request directly from the New/Edit Guest Booking Request dialog box.
After the Preferred Environment and Preferred Hosting Venue are specified, click the Route button. If the hosting venue is suitable for hosting the booking request, it is routed to that group. The booking is then moved to the Reservation Details pane.
Deleting Booking Requests
You can select and Delete multiple booking requests at the same time.