Skip to main content

Ed Walsh, CEO Virtual Iron: "Don't get into the vendor lock"

Funny, I speak to many IT folks in the past and have heard the same news around the IT manager circles. People are scared to get into to complex locks while the road to freedom and the flight to the Clouds is the shining light at the end of the tunnel. The "transitional vehicle" that virtualization is today, should not be a place where you want to get you ass glued too. But actually the decoupling of the app stack from your hardware layer does make it easier to make that move to the "Query 3.0" architecture which the clouds will try to help you with eventually.

The battle to move on from one vehicle to another is pretty much ,rather primordial, the same. Today we are getting people excited because they spent all their time discussing and talking and now they are willing to budge. Same challenges will be there tomorrow...this is also called the fear of Change.

Anyways, I am sure Ed didn't get too conceptual or philosophical with all this, he simply said:

"Storage design decisions are critical. Don't build out separate islands," he advised, in a tacit swipe at VMware. VMware's popular VMotion product can move running virtual machines around, provided they are using a shared storage file format from VMware. Virtual Iron offers LiveMigration in place of VMotion.

The Lowell, Mass., firm has previous received $8 million in 2003, $12 million in 2004, $11.5 million in 2005, and $13.5 million in July 2007, according to company spokesmen. The same backers have been involved in the previous rounds. Intel is interested in speeding up adoption of virtualization via investment through its venture capital arm because virtualized servers in many cases thrive with the latest versions of its chips. Hooks to the hypervisor have been built into the chips instruction set to speed some forms of virtualization processing requirements.

More 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

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!