-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If this works best for the backend, I'm good with making it happen on the frontend.
Josh On Thursday, January 10, 2013 9:35:50 PM Aaron Coburn wrote: > Hi, > > The VCL currently allows VM Host profiles to identify a single "VM Working > Directory Path", which can be either a dedicated or shared disk. All > running VMs on a given host will use this datastore path for I/O > operations. > > In our system, we are using a clustered VM host (VMware vCenter) > infrastructure connected to a shared network (SAN) storage array. In the VM > host profile, the "Virtual Disk Path" and "VM Working Directory Path" use > separate datastores, each of which use distinct storage processors in the > SAN. But still, all running VMs in the cluster use the same datastore for > their working directories. > > We have recently been encountering some significant I/O congestion on the > host bus adaptors that connect to the VM working directory, resulting in > really high I/O latency. > > My current thinking on this is that I would like to make it possible for a > VM host profile to identify multiple paths for the "Working Directory". > This would mean that the path for a given VM would be determined via round > robin. This would obviously have certain implications for the database and > existing provisioning module code, as well as involve some front-end GUI > work. > > Do any of you have thoughts on this? > > Thanks, > > Aaron Coburn > Systems Administrator and Programmer > Academic Technology Services, Amherst College > [email protected] - -- - ------------------------------- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlDwhb8ACgkQV/LQcNdtPQOS2ACeMSw188W0zNWv9dSuHdoY/JE7 OhEAni0ga32Oawpwwcs4wljl21BadzzI =cyuN -----END PGP SIGNATURE-----
