Skip to main content

5 ways to screw up Virtualization



This is better article than some plain "Virtualization is good" or "Virtualization is bad". How can you mess up Virtualization or any other breakthrough technology for that matter.

Too much , too soon
Ignore security
Failing to utilize it to its full power
Ignoring the departmental politics
Not understanding the license well enough

Not my words but coming from this article from ComputerWorld.

As the number of virtual machines climbs from dozens to hundreds, or thousands, tracking what you have becomes challenging. "It's easy to lose track of what's out there in the virtual world," because there are no physical machines to see or serial numbers to record, says David Rossi, managing partner at Sapien LLC, an application service provider in Morristown, N.J. that runs its operations on virtual servers. "The cataloging and administration of that is one of the ‘gotchas,' he says.


You'll lose the TCO and ROI advantage way too soon. And it really doesn't matter if its the cheaper XenSource or the license trap of VMware. The trap and price are all decided and ignored at your end, not the supplier.

Good read.

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op...