Skip to main content

VMware's storage independence with Storage Virtualization?



This was an interview with a Datacore Exec on their strategy on Storage Virtualiation and VMware's role in it.

TW: What do think about VMware directly interacting with a storage resource to automate storage provisioning for virtual servers?
PR:

We are having a lot of success with VMware pull-down and thin provisioning. VMware can already use Microsoft's Virtual Disk services (VDS) in Windows to do some of this. Also SMI-S has a generic storage API. It was supposed to be open but suppliers like EMC and HDS have extended it with proprietary extensions so it is no longer absolutely standard.

VDS hasn't taken off for a couple of reasons. Microsoft added complexity which wasn't needed. They came out with VDS and left it to lie. They didn't push it. No-one uses it. There isn't a usable GUI. The end user isn't interested in typing command lines.

We are talking to VMware (about an API-type protocol for storage provisioning). It's a rather complex relationship. They see storage as a hardware entity. We're not hardware. They are a software group too.


It still has a long way to go (as you read on the rest of the interview)

Datacore's site.

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