Skip to main content

Virtualization Strategy : Go Open Source



Some technologies cannot be held back but some technologies cannot be milked forever. This article (Which I found on Ashish's blog) has the same thing to say. freeing the VMware Server, Comparison models etc is making virtualization a hard place to make money on virtualization itself. As the writer notes there is loads of money to be made when you start cashing on the "relatively new technology" matra to your own good. Microsoft did this to stop VMware's mad rush to the clients. VMware can further push its prices down and use the same "its a great new technology, we got our own staff to assist you set the things up" to their very own favor.

Why the big change in strategy? In one word: Xen. This is an open source virtualization product emanating from Cambridge University, with a commercial arm called Xensource. The entrance of an open source product into the market has caused the effective price of virtualization to head toward zero. What’s interesting about this market, though, is how fast commoditization has occurred. Unlike databases, where Oracle has a huge installed base that it can milk at traditional prices, virtualization is a nascent market where user choices are being made today. VMWare faced its own choice: maintain its historical pricing and end up a bit player, or chop prices, attempt to establish a dominant market share, and figure out how to make money from the resulting user base. VMWare cut its prices with gusto.


But with XenSource releasing its performance paper, it will give uses a very strong reason to try out Xensource as well. So look at Virtualization as a mad train rushing towards the Commoditization land.

Read the article here.

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