Skip to main content

Virtualization: Are you willing to pay the price?



Time for some plain and simple facts. And this discussion I had with a leading education supplier in the Netherlands this morning. Yes this morning!

We were talking about the pricing against the price you're willing to pay. So is ESX really that expensive? Ask yourself these questions and decide yourself:

  • Am I willing to pay the price for a virtualization solution that just about might help me save money in the future?
  • Am I willing to invest in another virtualization vendor and its solutions while ignoring the "screaming message across the wall?"*
  • What about manageability? Are we getting the real win out of the virtualization solution?
  • Benchmarks: Is the cheaper solution the best or should I wait and see and risk my services go from bad (current physical) to worse (unmeasurable choices made due to pressure on costs)

Having said this, I don't want to target any virtualization vendor or solution. All I say is :
  • Do the math
  • Benchmark
  • Ask around
  • Do the math (again)


So this article obviously takes a jab at VMware's pricing and sure some folks might welcome it too. But are we forgetting something here? Its the technology and not a particular vendor. With loads of virtualization solutions springing like mushrooms all over this marshland, what do you do?
In 2006, many enterprise IT groups saw the potential in virtualization, rushed to consolidate servers and subsequently propelled VMware software to a market-leading spot. As 2007 begins, VMware’s prices are under attack, just as more CIOs look to virtualization to control server and storage sprawl and tame data center power costs.


What do you do?

Analysts advise CIOs planning for virtualization in 2007 to think strategically, not just tactically.


Ditto!

Read further...

*PS: And I didn't mention it in the same tone as the famed (or infamous) quote "Writing on the wall"
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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
Post a Comment
Read more

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!
Post a Comment
Read more