Anda di halaman 1dari 11

VMware Virtual SAN PSO Quick Guide

Prepared by

David Hill

VMware Professional Services Engineering dhill@vmware.com

VMware Internal only - Confidential

Contents
. !oc"ment #verview.............................................................................$ %. #verview of Virt"al S&'.......................................................................$ $. (ecommended reading........................................................................)
$. VMware *i+i Internal ,in+s...............................................................................................) $.% VMware My,ean ,in+........................................................................................................)

-. !esign Considerations.........................................................................) ). Scalability ,imits.................................................................................... .. VS&' !is+ /ro"ps................................................................................ 0. Config"ring dis+ red"ndancy for VS&'...............................................1 1. &dding e2tra comp"te reso"rces witho"t providing e2tra storage.... 3. Prod"ct S"pport Statement................................................................ 4. Credits............................................................................................... % . !isclaimer......................................................................................... %
!isclaimer

1.

Document Overview
5his doc"ment contains information for Professional Services to begin testing and deploying VMware6s new prod"ct Virt"al S&'7 which is incorporated in VMware vSphere ).) with Enterprise Pl"s licensing. 5his doc"ment ass"mes that the person reading this doc"ment has a basic "nderstanding of VMware vSphere8 and is familiar with b"ilding vSphere environments. 5his doc"ment is not intended for administrators or testers who have no prior +nowledge of vSphere concepts and terminology.

Overview o! Virtual SAN


VMware Virt"al S&' 9VS&': aims at providing highly scalable7 available7 reliable storage "sing ;cheap; hardware7 specifically !irect &ttached Storage 9!&S:. !&S storage is typically a lot cheaper to p"rchase than e2ternal storage systems. VMware VS&' is a software system that "ses distrib"ted algorithms to spread ch"n+s of ob<ects across a cl"ster of vSphere hosts and assign appropriate reso"rces 9dis+ and SS!: to them. VMware VS&' adheres to a new storage management paradigm 9inherent to software defined storage:7 which will a"tomate many of the comple2 management wor+flows that e2ist in storage system today with respect to config"ration and cl"stering. 5he p"rpose is to allow policies to be specified and enforced on a per ob<ect basis7 which provides the ability for g"aranteed ="ality of service for individ"al virt"al dis+s. 5his will provide administrators the ability to virt"ali>e and manage storage the same way that they do for CP? and memory today. 5he re="irements for the development of VMware VS&' were@ Converged platform 9comp"te A storage "sing commodity hardware: Simple to manage <"st li+e CP? and memory &bility to scale on demand7 in loc+-step with application needs7 b"t also in a fle2ible way Provide per-VM a"tomated S,& management

#ne of the great feat"res of VMware VS&' is that the prod"ct r"ns as a +ernel mod"le7 rather than r"nning as a virt"al appliance in a cl"ster. 5his allows for greater performance and better interaction with the hypervisor. 5he diagram below shows how the mod"les interact together.

VMware VS&' "tili>es Virt"al Machine Storage Policies within VMware vSphere ).). VM storage policies are similar in some respects to the vSphere ).4 B ). Profile !riven Storage feat"re. 5here are a few specific "se cases for when c"stomers are e2pected to "se VMware VS&'7 these are@ Virt"al des+tops Scale o"t model7 "sing predictive 9performance etc.: repeatable infrastr"ct"re bloc+s lowers costs and simplifies operations &voids ac="isition of e2pensive storage 9lowers 5C#:7 fast time to provision Scale o"t model with high bandwidth capabilities Cheap !( sol"tion7 enabled thro"gh a feat"re li+e vSphere (eplication that allows to replicate to any storage platform

5est B !evelopment Cig !ata !isaster recovery target

".

#ecommended readin$
5o better "nderstand how VMware VS&' wor+s7 and the re="irements needed to implement the sol"tion7 it wo"ld be beneficial to watch the following videos7 and read some of the blog articles and wi+i pages listed. 5he first is Cormac Dogan from VMware 5echnical Mar+eting presenting at the Italian VM?/. In this video he disc"ssed !istrib"ted Storage7 which is7 Virt"al S&' is a part of the overall sol"tion. -

http@EEblogs.vmware.comEvsphereE%4 $E4)Evmware-storage-f"t"res-video-co"rtesy-of-vm"g-italia.html VMware Principal &rchitect7 !"ncan Epping6s personal blog7 in which he provides comments on the VMworld !istrib"ted Storage session. De gives an overview of the technology and has a demo video. http@EEblogs.vmware.comEvsphereE%4 $E4)Evmware-storage-f"t"res-video-co"rtesy-of-vm"g-italia.html VMware Staff &rchitect Massimo (e Ferre gives an overview of how !istrib"ted Storage will fit within a Clo"d model. http@EEit%4.infoE%4 %E43Evmware-distrib"ted-storage-this-is-where-the-clo"d-world-collapsesE 5he following lin+ provides a downloadable overview of the capabilities of VS&'7 and how Digh &vailability wor+s with it. https@EEwi+i.eng.vmware.comEwi+iEimagesE0E0cEVS&'-all-in-one-t%.mp/SS 5ech Preview http@EEvmweb.vmware.comEs"pportwebE5rainingEPSEG5rainingGMaterialE#therE5echPreviews).)E5ech H%4PreviewH%4).)H%4-H%4vS&'.pdf 5his lin+ is a *ebe2 recording of Cormac Dogan giving a demonstration of VS&' to /5S-S!!C team. https@EEvmware.webe2.comEvmwareElsr.phpI&5JpbBSPJMCBrI!J.3% -- 0BrKeyJc33)0ad.)d.0d31b

".1VMware %iki &nternal 'inks


https@EEwi+i.eng.vmware.comEVsan https@EEwi+i.eng.vmware.comEVS&'!esign https@EEwi+i.eng.vmware.comEVS&'EvS&'G?ISpec https@EEwi+i.eng.vmware.comESPCM

". VMware M('ean 'ink


http@EEmylearn.vmware.comEmgr(egEplan.cfmIplanJ%%$ %B"iJwwwGfieldBtitleJCIML$ ,a"nch

).

Desi$n Considerations
5here are a n"mber of considerations that are needed7 prior to config"ring a vSphere cl"ster to participate as a VS&'. 5he following list shows the minim"m re="irements to implement a VS&'. Minim"m of three hosts. Each storageM host has a minim"m of one SS! and one spindle hard dis+. Each storageM host has a Pass-thr" (&I! controller as specified in the DC,. 5he (&I! controller m"st be able to present dis+s directly to the host witho"t a (&I! config"ration. 4/C 'etwor+. 9 /C networ+ can be "sed for smaller environments7 however 4/C is recommended:. VS&' VM+ernel port config"red on every host participating in the cl"ster. !edicated VS&' V,&' config"red following similar vMotion best practices. dVswitch or standard vSwitch with Management port gro"p created. Storage profile config"ration for red"ndant dis+ striping 9See Section 0 for g"idance:

Note: * The term storage used here determines hosts that will be used to provide the storage to the VSAN cluster. Hosts without storage can still participate in the cluster, they will only provide compute resources.

*.

Scala+ilit( 'imits
O,tion
Ma2im"m n"mber of dis+ stripes

'imit
% )

Ma2im"m n"mber of fail"res tolerated 'o of VS&' hosts per Cl"ster Ma2 n"mber of I#ps Ma2 n"mber of Parallel vMotion per VS&' cl"ster Ma2 n"mber of Parallel SvMotion per VS&' cl"ster Ma2 n"mber of VMs per host Ma2 n"mber of VMs per 9evenly distr"bted: VS&' cl"ster Ma2 n"mber of dis+ gro"ps per host Ma2 n"mber of hard dis+s per dis+ gro"p

$ 1 %47444 1 % 44 144 . .

Note: These scalability limits are correct at time o writing or the pre!release beta version o vSphere "."

-.

VSAN Disk Grou,s


In this section we will loo+ at how VMware VS&' creates dis+ gro"ps on each host. !is+ gro"ps are a b"nch of dis+s gro"ped together to provide storage to VS&'. No" can create m"ltiple dis+ gro"ps per host7 which wo"ld allow yo" to create m"ltiple data stores. ,oo+ing at the screen shot below7 yo" can see how a host reports standard dis+s. Note: As mentioned in the #esign $onsiderations section, each host providing storage to a VSAN cluster must have at least one SS#.

*hen config"ring a VS&' cl"ster for the first time7 yo" are given the option to either enable &"tomatic or Man"al dis+ addition. It is recommended to leave this in &"tomatic mode7 however7 if yo" were to choose Man"al mode7 yo" wo"ld need to create all the dis+ gro"ps per host yo"rself 9man"ally:.

*hen VS&' is initially t"rned on and in man"al mode7 >ero hosts are allocated as providing dis+s to the VS&' cl"ster. No" can see this in the screen shot below. *e resolve this by creating dis+ gro"ps as previo"sly mentioned.

*hen creating dis+ gro"ps man"ally7 yo" "se a dis+ gro"p creation wi>ard. #nce we create a dis+ gro"p7 a data store is a"tomatically created and mo"nted on all the hosts participating in a cl"ster. 5he screenshot below shows how a dis+ gro"p loo+s when created.

'otice the capacity of this data store in the screenshot7 this only incl"des three -4/C dis+s present in the first host. SS!6s are not incl"ded in the data store capacity. 5hese are "sed for read and write cache only.

!atastore capacity is dynamically e2tended when more dis+ gro"ps are created. 5he screen shot below shows the same datastore as above7 b"t with e2tra capacity.

..

Con!i$urin$ disk redundanc( !or VSAN


*hen config"ring VS&' we do not set"p any hardware based (&I! config"ration 9remember the design consideration7 this was a pre-re="isite to have Pass-5hro"gh (&I! Controllers:. So how do we ens"re data protectionI VMware VS&' "ses Storage policies to do this. 5hese can be fo"nd in vCenter Dome -O ("les and Profiles -O VM Storage Profiles. ?sing VM Storage Profiles yo" can assign capabilities to storage. In a Clo"d environment7 we li+e to "se /old7 Silver and Cron>e to determine o"r storage capabilities. *e can easily create these policies to now match the capabilities of the storage. *e have a n"mber of different config"ration options available to "s when adding capabilities. 5he screenshot below shows these capabilities.

If we select Num+er o! !ailures to tolerate and set this to 7 this specifies that the VMs associated with this policy can tolerate at least one fail"re 9host7 networ+ or dis+:. *e have the option to set the Num+er o! disk stri,es ,er o+/ect7 which specifies the n"mber of hard dis+s the replica of a storage ob<ect is striped across. 5he nice thing abo"t this is immediately I can tell whether or not any datastores are capable of "nderstanding the re="irement in the matc0in$ resources window. 5he vsan!atastore shown below is capable of "nderstanding these re="irements that I have placed in the VM Storage Policy.

Note that this is no guarantee that the datastore can meet the re%uirements in the V& Storage 'olicy. (t simply means that the re%uirements in the V& Storage 'olicy can be understood by the datastores which show up in the matching resouces. #nce Virt"al Machines have been deployed7 yo" can see how the placement has been performed. No" can see this by loo+ing at the VM Storage Policy "nder the manage tab on a VM.

5he (&I! indicates that the VM!K has a replica. 5his is to tolerate a fail"re7 the val"e was set to in the policy. 5his allows the VM to contin"e to r"n if there is a single fail"re in the cl"ster. 5he witness is there to 3

act as a tiebrea+er. If one host fails7 and one component is lost7 then this witness allows a ="or"m of storage ob<ects to still reside in the cl"ster. 'otice that all three components are on different hosts for this e2act reason. 5o recap7 by e2amining the lay o"t of the ob<ect above7 we can see that a (&I! config"ration has been p"t in place by VS&'7 placing each replica on different hosts. 5his means that in the event of a host7 dis+ or networ+ fail"re on one of the hosts7 the virt"al machine will still be available. If the host on which the VM does not reside fails7 then no action is re="ired. If the host on which the VM resides fails7 then vSphere D& can be "sed to a"tomatically bring the VM online on one of the remaining hosts in the cl"ster.

1.

Addin$ e2tra com,ute resources wit0out ,rovidin$ e2tra stora$e


#ne of the great feat"res of VS&' is that hosts can participate in a VS&' Cl"ster witho"t act"ally having to provide any storage. 5his allows for the scalability of comp"te reso"rces in a cl"ster7 witho"t having to p"rchase more dis+s for the hosts. 5his is a great "se case for clo"d environments where comp"te needs to be e2panded ="ic+ly7 even tho"gh no more storage is re="ired. 5he same pre-re="isites apply to the hosts being added to the cl"ster7 with the e2ception that no storage needs to be provided. &dding a host witho"t storage is simply a matter of right clic+ing on the cl"ster and moving a host into that cl"ster. 5he screen shot below shows the reso"rces available prior to adding any more hosts. No" can see we have ="ite a lot of reso"rces available already. 'otice that we have -00/C storage capacity7 and $..1/D> CP? available.

'ow if we add another host 9witho"t providing any e2tra storage: lets see what happens.

*e can see that CP? and Memory have increased7 we now have -%.)$ /D> of CP? available7 however storage capacity has not increased. 5his is one of the really great feat"res of VS&'7 allowing "s to ="ic+ly and simply scale o"t or comp"te reso"rces7 or add more storage to a cl"ster if we need.

3.

Product Su,,ort Statement


It is e2pected that VMware will release VS&' as a p"blic beta7 la"nching at VMworld %4 $ with the /& release of VMware vSphere ).). 5he VS&' feat"re set is to be f"lly s"pported and /& in L of %4 - when

VMware releases vSphere ).) ?pdate . Prior to the /& release7 VMware VS&' will not be s"pported in any prod"ction environments. Fa"lt 5olerance will not be s"pported with any Virt"al Machines r"nning on a VS&' !atastore. VMware View new release in L %4 - will s"pport VMware VS&'

14. Credits
Some of the information contained within this doc"ment7 has been gathered from VMware colleag"es. 5he Section Config"ring !is+ (ed"ndancy has had some information leveraged from a doc"ment written by Cormac Dogan7 5echnical Mar+eting &rchitect. 5he "se cases listed in the overview section have been leveraged from !"ncan Epping7 Principal &rchitect blog article on yellow-bric+s.com

11. Disclaimer
5he information in this doc"ment is correct at the time of writing. 'o g"arantees are given that once the prod"ct is released generally that they will not change. It is recommended to always confirm everything prior to releasing this information to c"stomers.

Anda mungkin juga menyukai