Summary of the content on the page No. 1
Summary of the content on the page No. 2
Contents 1 Introduction to VMware View ........................................................................... 2 2 About This Guide ................................................................................................... 2 3 Hardware and Software Requirements ......................................................... 2 3.1 Terminology ...............................................................................................................................................
Summary of the content on the page No. 3
1 INTRODUCTION TO VMWARE VIEW Built on VMware’s industry-leading virtualization platform, VMware® View is a Universal Client solution that lets you manage operating systems, hardware, applications and users independently of each other, wherever they may reside. VMware® View streamlines desktop and application management, reduces costs and increases data security through centralization, resulting in greater end user flexibility and IT control. VMware View enables customers to extend the
Summary of the content on the page No. 4
NFS Network File System Protocol NIC Network Interface Card RAID Redundant Array of Independent Disks Snapshot Read only copies of an entire file system in Data ONTAP VMware View VMware View Manager manages secure access to virtual desktops, works Manager with VMware vCenter Server to provide advanced management capabilities VC VMware vCenter Server VIF Virtual Interface VLAN Virtual Local Area Network A set of software products that provide services and management VMware View infr
Summary of the content on the page No. 5
Ten Servers (Configured as follows) 128 GB RAM 4 Quad Core Xeon Processors 2 On-board Ethernet NICs 2 Quad port Ethernet NICs Table 2: Hardware Configuration 3.3 SOFTWARE RESOURCES The following software was used in the configuration: Description Minimum Revision Data ONTAP® 7.3.1 NFS License N/A VMware ESX Servers 3.5 Update 3 VMware vCenter Server 2.5 Update 3 Microsoft Windows Server 2003 Enterprise Edition SP 2 Windows Servers for vCenter (32-Bit) Desktops/Virtual
Summary of the content on the page No. 6
Table 3) Software Resources 4 PHYSICAL ARCHITECTURE Figure 1) Physical Architecture Overview. 4.1 NETWORK ARCHITECTURE The networks used for this test were dedicated 1Gb Ethernet. This network was split into three VLANs. One VLAN was for administrative/public traffic and CIFS access, and the other two were non-routable VLANs designed for storage and VMotion traffic. All virtual desktops were assigned an IP address using a DHCP server. The VMware ESX Server’s networking configur
Summary of the content on the page No. 7
Teaming ports and assigned to the public VLAN for access to CIFS shares and other network resource by the desktop virtual machines. The NetApp FAS2050HA has four 1Gb NICs. The four NICs were configured as two multi-mode VIFs. One VIF was specifically for VMkernel NFS traffic and was placed on the private, non-routable VLAN. The other VIF was for CIFS (Home Directories) and management traffic. This configuration allows for an Active/Active state with both failover and a degree of re
Summary of the content on the page No. 8
reboot of the storage controller at a future time. In the event the management/CIFS VIF needs to be created after the initial setup of the FAS2050, please refer to the Data ONTAP® Software Setup Guide for directions in rerunning the setup process for the storage controller. 1. For each NetApp controller, open NetApp FilerView® and click Network->Add Virtual Interfaces. 2. Name the new VIF. 3. Select the two network interfaces that will make-up the NFS VIF. 4. For Trunk Mode press t
Summary of the content on the page No. 9
Figure 4) FAS2050 NFS VIF setup – Modify virtual interface. The ESX hosts will need to be configured as well. For each ESX host, configure NFS connections to the storage controllers using a VMkernel port group. The network ports for this NFS VMkernel port group should be on a non-routable NFS VLAN. For each ESX host, the virtual switch for the NFS VMkernel should have two network ports that each go to different switches in the network. These two switches are stacked together with li
Summary of the content on the page No. 10
ESX Host Virtual Switch: vSwitch0 Remove… Properties... Service Console Port Physical Adapters Service Console vswif0: 10.10.10.10 Virtual Switch: vSwitch1 Remove… Properties... Virtual Machine Port Group Physical Adapters VM Network Virtual Machine 1 Virtual Machine 2 Virtual Machine 3 Virtual Machine 4 Virtual Switch: vSwitch2 Remove… Properties... VMkernel Port Physical Adapters VMkernel NFS 192.168.1.101 Virtual Switch: vSwitch3 Remove… Properties... VMkernel Port Physical Adapter
Summary of the content on the page No. 11
Storage required after deduplication 5GB 1 (Single parent VM will be used for Number of volumes used both PODs) Size of VM 10GB Volumes for Linked Clones OS Data Disks NFS volume storage capacity 400GB Number of volumes used 4 (two per FAS controller) Volume for User Data Disks for Desktops in Persistent Access Mode (500; 250 per FAS controller) 250GB (2GB per user, 50% NFS volume storage capacity deduplication savings) Number of volumes used 2 (one per FAS controller) Volume
Summary of the content on the page No. 12
To configure the volumes that will contain the virtual machines perform the following steps: 1. For each NetApp controller, open NetApp FilerView® and click Volumes->Add to activate the Volume Wizard. 2. Click on Next to go to the Volume Wizard –Volume Type Selection screen. 3. Choose “Flexible” and click Next. 4. Enter the new Volume name and choose the language and click Next. 5. Choose the Aggregate created for the VMs in the previous steps and select None for the Space Guarant
Summary of the content on the page No. 13
You will next need to ensure that three of the volumes created on the storage controller are set as NFS volumes. In order to accomplish this, please perform the following steps: 1. From the FilerView menu, select NFS. 2. Select Manage Exports to open the Manage NFS Exports screen. 3. Click on the virtual machine production volume created in the previous step NFS export. 4. Grant the export Root Access permissions by clicking on Next and placing a green check inside the box. Then cl
Summary of the content on the page No. 14
4.4 INTELLIGENT READ CACHING VDI by nature is a read-intensive technology and is very bursty in nature. This can be exemplified by boot storms, login storms, and virus scan storms which all further increase the read-intensive and bursty nature of a virtual desktop environment. Traditionally, these challenges are addressed by increasing the cache for both ESX servers and storage devices, increasing the spindle count on the storage devices, and adding more storage devices to offset the t
Summary of the content on the page No. 15
4.6 VMWARE ESX CONFIGURATION Each VMware ESX server should be configured to maximize NFS throughput and capability. In order to maximize NFS capabilities please perform the following steps. 1. Open VCenter Server. 2. Select an ESX host. 3. In the right pane, select the Configuration tab. 4. In the Software box, select Advanced Configuration 5. In the pop-up window, left pane, select NFS 6. Change the value of NFS.HeartbeatFrequency to 12. 7. Change the value of NFS.HeartbeatMaxFai
Summary of the content on the page No. 16
Figure 7) ESX Host NFS Network Configuration Figure 8) ESX Host NFS Load Balancing Network Configuration 15
Summary of the content on the page No. 17
The NFS datastores will need to be mounted on each of the ESX hosts. Please follow the below steps to mount NFS datastores on the ESX host server. 1. Open FilerView (http://filer/na_admin). 2. Select Volumes. 3. Select Add to open the Volume Wizard. Complete the Wizard. 4. From the FilerView menu, select NFS. 5. Select Add Export to open the NFS Export Wizard. Complete the wizard for the newly created file system, granting read/write and root access to the VMkernel address of all E
Summary of the content on the page No. 18
Average Application Execution Time (Seconds) WORD_SAVE_1 WORD_OPEN_1 PPT_OPEN PPT_EDIT PPT_APPEND IE_OPEN_2 IE_OPEN_1 FIREFOX_OPEN FIREFOX_CLOSE EXCEL_SAVE_2 EXCEL_SAVE_1 EXCEL_OPEN_2 EXCEL_OPEN_1 ACROBAT_OPEN_1 0.00 0.50 1.00 1.50 2.00 2.50 Figure 9) Average application execution time in seconds. 5.2 STORAGE SYSTEM IO SUMMARY The graphs below show the number of NFS operations for each controller during the duration of the validation. The average number of IOPS for the cluster was 2652
Summary of the content on the page No. 19
Figure 11) NetApp FAS2050 controller B average NFS OP Rate 6 SUMMARY This reference architecture deployment guide details and validates a 1000 seat VMware View building block based architecture on NetApp. This building block based approach can be scaled linearly by adding additional building blocks. Both NetApp and VMware provide consulting services, design, architecture, deployment, and management guidelines to assist in the deployment of the solution based on your requirements. Mo
Summary of the content on the page No. 20
VMware View Composer Deployment Guide VMware View Reference Architecture 19
