Chapter 11. Working With Virtual Machines

The default format of the internal name is i-<user_id>-<vm_id>-<instance.name>, where instance.name is a global parameter. When vm.instancename.flag is set to true, if a display name is provided during the creation of a guest VM, the display name is appended to the internal name of the guest VM on the host. This changes the internal name format to i-<user_id>-<vm_id>-<displayName>.

The following table explains how a VM name is displayed in different scenarios.

User-Provided

vm.instancename

.

Hostname on the

Name on

Internal Name

Display Name

 

 

VM

vCenter

 

 

 

 

 

 

 

Yes

True

Display name

i-<user_id>-

i-<user_id>-

 

 

 

 

<vm_id>-

<vm_id>-

 

 

 

 

displayName

displayName

 

 

 

 

 

No

True

UUID

i-<user_id>-

i-<user_id>-

 

 

 

 

<vm_id>-

<vm_id>-

 

 

 

 

<instance.name>

<instance.name>

 

 

 

 

 

Yes

False

Display name

i-<user_id>-

i-<user_id>-

 

 

 

 

<vm_id>-

<vm_id>-

 

 

 

 

<instance.name>

<instance.name>

 

 

 

 

 

No

False

UUID

i-<user_id>-

i-<user_id>-

 

 

 

 

<vm_id>-

<vm_id>-

 

 

 

 

<instance.name>

<instance.name>

 

 

 

 

 

 

11.7. Stopping and Starting VMs

Once a VM instance is created, you can stop, reset, or delete it as needed. In the CloudPlatform UI, click Instances, select the VM, and use the Stop, Start, Reset, Reboot, and Destroy buttons.

Reseting leads to restarting a VM. You can reset when a VM is either running or stopped.

11.8. Assigning VMs to Hosts

At any point in time, each virtual machine instance is running on a single host. How does CloudPlatform determine which host to place a VM on? There are several ways:

•Automatic default host allocation. CloudPlatform can automatically pick the most appropriate host to run each virtual machine.

•Instance type preferences. CloudPlatform administrators can specify that certain hosts should have a preference for particular types of guest instances. For example, an administrator could state that a host should have a preference to run Windows guests. The default host allocator will attempt to place guests of that OS type on such hosts first. If no such host is available, the allocator will place the instance wherever there is sufficient physical capacity.

•Vertical and horizontal allocation. Vertical allocation consumes all the resources of a given host before allocating any guests on a second host. This reduces power consumption in the cloud. Horizontal allocation places a guest on each host in a round-robin fashion. This may yield better performance to the guests in some cases.

•End user preferences. Users can not control exactly which host will run a given VM instance, but they can specify a zone for the VM. CloudPlatform is then restricted to allocating the VM only to one of the hosts in that zone.

90

Page 99 Page 101
Page 100
Image 100
Citrix Systems 4.2 manual Stopping and Starting VMs, Assigning VMs to Hosts
Page 99 Page 101

4.2 specifications

Citrix Systems, a leading provider of virtualization solutions and cloud computing technologies, released version 4.2 of its popular software, Citrix XenApp, which was previously known as Presentation Server. This version marked a significant evolution in providing users with remote access to applications and desktops, emphasizing simplicity, performance, and security.

One of the standout features of Citrix XenApp 4.2 is its improved application streaming capabilities. This technology allows applications to be delivered to users in real-time, reducing the need for extensive local installations and enhancing the user experience. With application streaming, administrators can efficiently manage applications on a central server while ensuring that users have immediate access to the necessary tools.

Another highlight of this version is the enhanced security measures put in place to protect sensitive data. Citrix XenApp 4.2 includes support for SSL encryption, providing a secure communication channel for data transmitted between the server and clients. This is particularly crucial for businesses that need to comply with strict data protection regulations. Additionally, the integration of endpoint security features ensures that unauthorized access to applications is minimized.

Performance enhancements are also a critical focus in this release. Citrix optimized the delivery of applications over various network conditions, ensuring that users experience minimal latency regardless of their location. This was achieved through the incorporation of SmartAccess and SmartControl technologies, which allow administrators to set policies based on user roles, device types, and network conditions. This level of granularity enables organization-wide security without compromising on usability.

The user experience was further improved with a revamped interface, making it easier for end-users to access their applications and data. Simplified menus, clear navigation paths, and the ability to customize user settings contributed to a more efficient workflow, allowing users to focus on their tasks rather than struggling with the software.

Finally, Citrix XenApp 4.2 was designed to be highly scalable. Organizations of all sizes could deploy this solution to deliver applications efficiently, adapting to their specific needs as their user base grows or changes. This flexibility is crucial for businesses looking to future-proof their IT investments while maintaining optimal performance.

In summary, Citrix XenApp 4.2 stands out with its enhanced application streaming, robust security features, improved performance under varying conditions, user-friendly interface, and scalability, making it an ideal choice for organizations seeking to leverage virtualization for remote access to applications and desktops.
Top Page Image Contents