Skip to main content

Storage vendors beginning to get unconfortable with VMware

But as VMware adds features to its file system, there's growing suspicion among storage vendors that the company is trying to move storage system value-adds into its Hypervisor. Some storage vendors think that VMware is stepping on their toes, especially when it comes to Storage VMotion, a feature in VMware ESX Server version 3.5 that migrates the back-end storage attached to virtual machines.

It's a matter of virtualisation vendors like VMware "looking for ways to add value" as the virtualisation becomes commoditized, says Bruce McCorkendale, distinguished engineer in the office of the CTO for Symantec Corp.

As more companies virtualize their server environments, users who once struggled with running multiple operating systems will now struggle with running physical and virtual servers, and in some cases, with running multiple hypervisors.

This is where Symantec sees the value proposition for its vendor- and platform-agnostic storage, security and server management software. "We've been helping users do storage management and high availability in heterogeneous environments for a long time," McCorkendale said. "For [another vendor] who hasn't been doing it that long, going from zero to Symantec will take quite a while."

If it sounds like McCorkendale is drawing a line in the sand, it's because he is. VMware may insist it's not trying to compete with storage vendors. But, McCorkendale says, "They are. The question is how well they're going to be able to compete."


Source

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!