No, we'll possibly look at it down the road, but couldn't afford the infrastructure required to support vmotion. (Have to have hugely expensive SAN hardware underneath.) When ESX adds support for iSCSI devices, we'll likely look more into vMotion.
We're also not using it for fileservers, just db servers and other stuff. Our standard AFS server platform is a PIII or P4, with three 185G drives on a 4port 3ware card set up as mirror and hot spare. Our environment is split between two buildings, and most of our vmware space is set up with paired services where we have a server in each building, using linux virtual server w/ keepalived for load balancing and failover between the two vm's. -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-6679 UMR Information Technology Fax: (573) 341-4216 > -----Original Message----- > From: Matthew Cocker [mailto:[EMAIL PROTECTED] > Sent: Friday, November 19, 2004 2:40 PM > To: Neulinger, Nathan > Cc: openafs-info > Subject: Re: [OpenAFS] Running OpenAFS in Vmware ESX host > > Neulinger, Nathan wrote: > > > It only obliterates it if you have ONE vmware system. > > > > We are doing this for our afs database servers and have 10 > DELL 2650's > > virtualizing approximately 100 linux and windows servers, > with plenty of > > room to spare. > > > > -- Nathan > > > Are you using vmotion. ESX (if the vm images are stored on > sans) has the > ability to migrate vms from one vm server to another with out > taking the > vm down. Also if any esx server goes down the other can > instantly bring > up all the vms it was running. Lastly on one modern box our > afs servers > are using hardly using any cpu or memory, but when the FS crashes it > takes out a lot of users and takes ages to come up. > > Also fibre channel switches are real expensive, so with ESX > we can slipt > the modern server into several virtual afs fs instance with > less users > each (better slavage times), better use the hardware and SANs > connections (of which we need less). All very promising. It > also allows > us to have identical dev/test/production environments and > means that the > dependence on a particular version of linux to run X hba on > X hardware > is removed. > > If only it did not cost so much. > > > Nathan, did you put vicepX on raw disk or on a vmfs shared lun? > > Cheers > > Matt > > > _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info