Tuesday, May 6, 2014

Horizon 6 dos and don'ts

 Lets catch up with Horizon 6 best practice. there are lots of article i have found on VDI best practice but it seems like everyday the era of vdi technology is changing and now vdi is also moving to public cloud infrastructure(desktone, AWS etc.). Many of our existing customers were asking for the best practice for vdi deployment which can give optimal performance.

  I was chatting with some of vmware technical support team guyz regarding current view issues and they have mentioned that most of the customers are facing issues because of wrong sizing or incorrect design in their VDI environment. You may find bellow table generalized for other vdi solutions too. feel free to comment for any specific feature's best practice.
    
Tag
Recommendation
Core, scaling, front-end
acceleration
Do: Consider front-end web acceleration solutions for high-volume
infrastructures supporting large numbers of clients.

Core, vCenter

Do: Implement vCenter according to its requirements; back up the database
regularly and have provisions in place in case of an outage. vCenter is very
important.

Core, Active Directory,
DNS, DHCP, Load
Balancing
Do: Consider front-end web acceleration solutions for high-volume
infrastructures supporting large numbers of clients.

Net, VMkernel 10GbE or 8 Gbps FC for storage, uplinks,
dedicated storage net
Do: Always use dedicated (non-shared) VMkernel ports with redundant
10GbE or 8Gbps FC uplinks for connecting each vSphere server to storage.
(network recommendation changes in each scenario but above recommendation will give best performance in any scenario)
Net, Connection Servers,
Load Balancing

Do: Implement more than one Horizon View Connection Server VM to
provide high availability of the desktop VM logon services

Net, uplink (NIC)
redundancy

Do: Assign multiple physical uplinks (network interfaces) to each VMkernel
port and VM Port Group to avoid an outage related to a network interface
card failure in the server.

Net, VLAN tagging

Do: Consider using VLAN tags for VMkernel and VM Port Groups to reflect
VLANs defined within your network infrastructure.

Net, infrastructure (e.g.
switch, etc.) redundancy
Do: Deploy a fully redundant networking infrastructure to reduce the
likelihood of an outage resulting from a failed networking switch or other
component.

Net, VLANs, management

Do: Consider using VLANs to simplify the management of the physical
network.

Net, utilization and
threshold monitoring

Do: Monitor Ethernet port and switch utilization to help reduce the
possibility that an overloaded switch causes performance problems.

Net, storage network,
Back plane bandwidth of switch
Do: Use high-speed  switches between the ESXi hosts and storage which minimum supports back plane bandwidth equals to no. of populated switch port.

Net, Dedicated VMkernel
ports and uplinks for
storage
Do not: Create VMkernel ports for other purposes (e.g. Fault Tolerance
Logging), or VM Port Groups on the same vSwitch (and its uplinks)
designated for storage.

Net, VLANs, bottlenecks,
proper use/design

Do Not: Use VLANs to simplify the network at the expense of creating
network bottlenecks.

Net, 1 GbE, VMstore,
bottlenecks

Do Not: Use 1GbE Ethernet switches for the connections between the
vSphere hosts and storage if VDI is loaded with IO and latency intensive applications

Server, testing, scaling,
carefully consider last
minute changes

Do not: Make significant last-minute changes or substitutions to the
successfully tested server equipment and desktop VM configurations
without considering the potential impact to performance and user
acceptance.

Server, vSphere Host,
CPU cores

Do: Always ensure that the vSphere hosts have the adequate number of
cores and CPU performance required by the desktop VMs.

Server, vSphere Host,
installed memory (RAM)

Do: Always ensure that the vSphere hosts have the adequate amount of
memory (RAM) to run the desktop VMs and their applications efficiently.

Server, user acceptance
testing, end-to-end
(endpoint) performance
Do: Always perform end-to-end user acceptance testing as early as possible
in a deployment cycle to exercise the servers, as well as the entire
environment from the servers to remote users and their endpoint devices
(e.g. smart phones, PCs, laptops, tablets, etc.).

Server, parent images,
preparation

Do: Test and verify the design of the proposed parent VM(s) to determine
the resources they will need, such as virtual CPUs, memory assignments,
storage IOPS, etc.

Server, parent images,
testing, validation
Do: Test and validate the proposed VM images with users and incorporate
their feedback as much as possible before starting a full pilot process.

storage
best practices

Do: Always start with the latest Best practices for deploying storage in VMware vSphere environments.
 Bandwidth sizing
Do: Alwaws calculate datacenter internet bandwidth requirement if users are accessing VDI remotely here is useful link for protocol required bandwidth calculation link from Andri's blog Protocol bandwidth calculator

    feel free to comment if you guyz knows any other tips too.. till then ADIOS AMIGOS...