up vote 0 down vote favorite
share [g+] share [fb]

Which rules/policy or procedure do you use to maintain your list of VMs?

For ex. Will you assign a VM and keep eyeing on whether it is being utilized or kept idle? (So that you can take it back to pool and give it to some other needy people)

Or Will you assign a VM only for particular period of time and ask the user to request to extend the period?

link|improve this question
36% accept rate
This may be too localized... – Bart Silverstrim Jan 5 at 13:50
Set and Forget. – Tom O'Connor Jan 5 at 13:53
Are you talking about virtualized workstations? We virtualize only servers so shutting them down for appearing idle might not be a good idea... – Bart Silverstrim Jan 5 at 13:54
Depends on the enviroment...so probably too localized. If I created a server and set it up, and then it got "returned to the pool" after a few months I'd be shot. Normally, VM's are, as Tom said above, Set and Forget, unless you're really squeazed on CPU and storage resources. – tombull89 Jan 5 at 13:54
feedback

closed as not constructive by Chopper3, Bart Silverstrim, MikeyB, dyasny, Tom O'Connor Jan 5 at 15:55

This question is not a good fit to our Q&A format. We expect answers to generally involve facts, references, or specific expertise; this question will likely solicit opinion, debate, arguments, polling, or extended discussion. See the FAQ for guidance on how to improve it.

1 Answer

up vote 1 down vote accepted

The only policy that ever worked for me is a fixed deadline for a VM life. I have yet to see a user who ceased to need a system he got hold of...

link|improve this answer
No body give it back and says that it is no more needed. Often i am running short of space and not able to meet their vm needs. That's why i tried to adapt some best practices followed by experts. But all are following their own idea it seems. – Samselvaprabu Jan 5 at 17:19
feedback

Not the answer you're looking for? Browse other questions tagged or ask your own question.