On Tuesday, October 23, 2012 10:14:43 AM Michael Jinks wrote: > On Tue, Oct 23, 2012 at 10:51:51AM -0400, Josh Thompson wrote: > > Michael, > > > > Can you explain the behavior you were expecting a little better? From > > what > > you've said, I thought you wanted the ability to easily change how many > > VMs > > VCL will spin up on a given host. Rather than using the VM Limit field, > > you can assign/unassign VMs to/from a host to change how many are on it. > > So, given that, I'm guessing there was something more you were looking > > for. > That's the obvious alternative, yeah... > > I'll leave out the "why" for now, but what I had hoped was that we could > define all our VM's, assign them across our vhosts, and then use the > limit as a sort of flexible governor to raise and lower the number of > vm's that can actually boot at any given time, independent of what'd > defined or assigned.
So, you were thinking you'd be able to assign all of your VMs to all of your VM hosts, and VCL would control on which host a VM would be deployed? Josh -- ------------------------------- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University [email protected] 919-515-5323 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.
signature.asc
Description: This is a digitally signed message part.
