Has virtualization caused any issues in your organization that are not technical?
Change control management, Microsoft virtualization, Virtualization Implementation, Virtualization Integration
Has virtualization caused any issues in your organization that are not technical? How has it affected things like Change Control, Support, and integration with existing staff?
This question is sponsored by Microsoft.
Software/Hardware used:
Software/Hardware used:
ASKED:
April 28, 2009 1:42 PM
UPDATED:
August 24, 2009 1:29 PM
Answer Wiki:
Absolutely.
The first problem is why bother with virtualization.
Then you get to who is going to manage it. In our case, we hired a new guy.
Now we are trying to figure out where does one area of responsibility end, and the other begin. ESX | OS | Storage | Netoworking? Or do all of these now have to be handled by the same sys admins?
To see all answers submitted to the Answer Wiki: View Answer History.
We are not experience any negative issues. Since we’ve purchased a virtualization server, we are focusing less on deployment costs and server provisioning which cuts down our time to production.
The only negative issues I’ve experienced are software licensing and politics.
Software licensing is here, but there’s really two prongs to the issue: Understanding how licensing changes when virtualized (Windows, Oracle, etc.) and software that uses licenses that are tied to physical host hash strings. These can be particularly nasty if doing VMotion/Live Migration.
Politics is a whole other discussion. There will almost always be someone within the adminisphere who has a negative opinion on virtualization, be it for security or reliability reasons, or due to a past negative experience, whether due to inadequately-trained personnel or less-robust versions of the hypervisor. These people are always the hard sell, and in some cases you have to be a little under-handed, and implement virtualization on a small scale to prove the concept. At least, that’s how it’s worked for me.