1. VMware view – storage considerations Calin DAMIAN TANASE This presentation does not represent the thoughts, intentions, plans or strategies of nobody. It is solely my opinion. This presentation is provided "AS IS" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. You may distribute this presentation freely as long as you keep it unmodified Copyright Calin DAMIAN TANASE, Temperfield

2. Agenda Why VMware View? What’s driving adoption? Business Drivers VMware View Architecture Design Considerations Challenges in a virtual desktop world Storage – a short introduction Storage – what we plan for? Storage challenges for VMware View Environments How the challenges may be addressed? Resources Storage – a short introduction

4. Device simplification and/or consolidation

5. Faster, rapid deployments

6. New apps

7. New employee

8. Other rovisioning tasks

9. OpEx reductions - Lower Cost of Desktop Management

10. Power savings

11. BYO - “bring-your-own-PC” approaches

12. Reduced IT services cost

13. Reduction of IT staffing costs (or outsourcing costs)

14. Simplified desk-side support

15. Simplified life cycle management.

16. Ease and speed of OS/application deployments

17. Simplify new HW/OS adoption, Windows 7 migration

18. Security - All data is maintained within a central datacenter; no data on clients

19. Asset control outside corporate perimeter (“offshoring”)

20. Physical device security

21. Data security/control

24. Operational requirements

25. Environment may affect the design (latency, bandwidth, DMZ, firewalls)

26. HA for desktops

27. Business continuity/Disaster recovery

28. Portability and flexibility

29. Networking

30. Security

31. Scalability

32. Monitoring

33. Management

34. User experience & user acceptance

35. Output – THE Design

36. Solution/Enterprise/Site – wide Architecture

37. Cluster and Server Sizing (! Configuration Maximums)

38. End-point devices

39. Storage Design & Sizing  that’s ourfocus for this presentation

41. Some won't see any ROI for at least a few years

42. CPU power - 10/12-core CPUs available; 32-core CPU expected H2 2011

43. Lots of memory needed in servers – Cisco EMT 48 DIMM slots for 384GB ; 16GB dimms prices dropping (Moore’s Law)

44. Network Bandwidth – PCoIP improvements; 10G switches price/port dropping bellow 2k eur; accelerators; technology improvements to consider & optimize for virtual channel

45. 3D

46. Risks associated to migration

47. Apps/desktop HW not candidates for VDI; maybe costly migration

48. App-virtualization

49. Licensing

50. Roaming profiles vs. Persona management (personal settings?)

51. Shared centralized infrastructure vs. dedicated hardware

52. And of course STORAGE

53. Don’t forget to consider Subjective challenges

54. changing the culture and perception that users have developed around “their PCs” ; user resistance to be considered 

55. find ways to get prospective users to actually desire new VDI driven systems

58. PCI & SCSI

59. Shared storage – consolidation trends since the 80th

60. Shared storage as technology enabler for clusters, DR, etc

61. FC – we got the best from channel and network comm. types

62. SANs

63. What a storage system is doing basically?

64. Virtualize “local” storage capacity  we get LUNs (logical vols)

65. Serving data to clients (servers) from logical constructs (LUNs)

66. Why is the traditional DDM the “retard child” of IT infrastructures

67. How the IT infrastructure “society members” are contributing to integrate the DDMs?

68. For digital cameras we compare by Mp, optical zoom, digital zoom; what’s used for storage systems?

69. How to read a storage subsystem datasheet (iops, SAS/SATA/FC/iSCSI)

71. How do you characterize the workload to be accommodated?

72. Sequential/random

73. Cache friendly

74. R/W ratio (i.e. 20% write / 80% read)

75. Block size/io length

76. Iops

77. Io bandwidth/throughput

78. Latency tolerance

79. How do you define what’s good or bad with performance? Is there a good enough threshold?

80. What happens when you’re not providing enough to consumers?

81. Impact of HW configuration and logical configuration

82. RAID5 Write penalty scenario

83. How do you benchmark?

84. What may negatively influence your results?

85. Performance management/optimization - One time job or a process to integrate in the business model?

86. Methodology

88. Large scale View projects  huge influx of data that was stored on local machines now needs to be stored and administered centrally

89. Shared storage infrastructure vs. dedicated to the desktop’s user

90. Internal bus transport vs. the storage fabric

91. “Storms” (boot, AV, login) impact for all users?

92. Peaks accommodated into large averages?

94. Performance: iops usually the issue - not capacity nor transport

95. Assess - Measure & Analyze what you need to accommodate as storage needs

96. Well performed assessments will provide good inputs for design

97. Stateless /Statefull?

98. How many different golden images do I need?

99. Apps installed or Thinapped?

100. How many unique linked clone VMs are required?

101. Persistent disks or persona management?

102. What are the average and peak IOPS of the desktops?

103. What are the most IO intensive applications?

104. Any unauthorized apps? – undesired impact on sizing 

106. LSI disk drive for XP; SAS forWindows 7

107. Turn off drive indexing

108. Defrag the drive – both the image and the VMDK

109. Clean out all system temp files

110. No P2V

111. Keep the image as clean as is possible

113. Storage systems architecture

114. Tools you use to assess performance

115. VMware View specifics

116. Linked Clones

117. Tiered storage support & storage overcommitment

118. Master VM image on SSD for stateless

119. Redirect disposables

120. Refresh, Rebalance

121. In a new architecture old solutions may not be ideal; be open to consider change

122. Remember: with flexibility/features comes complexity; storage space consumption was easy to determine. We have now Linked Cloning vs. Linked Cloning Thin Provisioned(even Hw Thin Provisioning @storage layer)vs. Full Cloning Thin Provisioned

123. For a Linked Clones setup you will maybe consider consumption for:

124. master replica & replica

125. delta footprint (refresh @ 50%?)

126. User data disk (if not using roaming profiles/persona management)

127. max log size

128. disposables

129. Overhead

130. .vswp (configured mem, reservations? All VMs powered-on at the same time?)

131. With tiered storage you need to profile workloads per storage tier

132. i.e. 100% read for replica

133. 40% read; 60% write for LinkedClones disks

135. VMware View Architecture Planning

136. VMware View Reference ArchitectureA guide to large-scale Enterprise VMware View deployments

137. VMware View WAN Reference ArchitectureThis View WAN reference architecture focuses on the WAN link, its attributes, such as bandwidth and latency, and the WAN optimization aspect of the architecture.

138. VMware ThinApp Reference ArchitectureThis VMware ThinApp reference architecture specifically focuses on integration with Active Directory, the use of Distributed File System technology for file shares, and View Composer considerations.

139. Server and Storage Sizing for VMware VDI: A Prescriptive Approach

140. Storage Basics -- http://vmtoday.com/2009/12/storage-basics-part-i-intro/

141. Jim Moyle’s paper – Windows 7 IOPS for VDI: Deep DiveView 4.5 Stateless Desktop reference architecture Windows 7 Optimization Guide Windows XP Optimization Guide View VDI calculator http://myvirtualcloud.net/?page_id=1076 The biggest Linked Clone “IO” Split Study

142. Questions?

143. Thank you!