Skip to main content

Real Customer Stories: Rackspace customers suffer for "departmentalization fever"; won't share virtual infra

Well, I didn't hear that from John Engates, who I spoke to a few days back myself. But customers indeed are the ones who are playing really tough. John does have a point about the I/O, security and Performance as well.

I am taking up this initiative myself, within my new employer (AtosOrigin) to have some of these optimization tools as a default design option within our Data Centers.

Anyways here are the stories:

Engates said that in fact security was not a major concern when it came to virtual machines (VMs) - until someone finds a way of tunnelling into the hypervisor. He was clear however to point out that security issues still remain within VMs themselves and that they need to be managed from a security standpoint just like physical boxes.

Rather, his customers were concerned about sharing a physical server because they would not have visibility into what other customers were doing on the hardware.

Since it makes no sense to virtualise an application that hammers the hardware, it's reasonable to assume that most virtualised applications don't generally hog resources. But, if an application in a VM gets hit hard - whether for legitimate reasons or because it's the victim of a DOS attack for example - and then hogs the CPU, storage link or Ethernet ports, all other VMs on that box would be affected. If company A's VM gets hit, company's B's applications slows right down - and there's nothing they can do about it.

The problem is, according to Engates, that there are few if any ways, given the current state of virtualisation technology, to prevent one VM hogging resources, especially I/O or CPU. He said that the tools just aren't there.

Engates acknowledged that the problems Rackspace faces in this regard is similar to that in most organisations, where departments that "own" a server - and are being charged for it - are frequently reluctant to share it with another department in the same company, often for similar reasons. At a recent meeting of IT admins, this issue was voiced as a matter of concern. So it's perhaps hardly surprising that those using managed hosting providers are wary of external organisations.


Link

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

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...