Skip to main content

Virtualization: Hypervisor portability is key to sustainability!

This is what this news item has to say. Companies are custom-coding too much in the hope of making a quick exit from VMware's VI to another cheaper infrastructure that provides the functionalities of HotMigration and Resource scheduling capabilities. Quoting

As such, Mosso isn't devoting too many resources into developing its environment around VMware. Instead, it will use "the basics like VMotion and DRS" and try not to custom-code too much of the environment. "We've tried not to tie our system too directly to VMware, because we might potentially switch it out for Xen," Bryce said. The company recently finished evaluating Citrix XenServer and will soon evaluate Oracle VM, Bryce said.

With Xen-based virtualization platforms, Bryce said, the philosophy is to provide "the engine and the access, on which you are free to do whatever you want."

The company is also "talking to VMware to help us develop more advanced features, although I don't know how much success we'll have," Bryce said. "VMware is building the tools that 80% of business needs; the problem is, we do things in the remaining 20% that not many people need."

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

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