Skip to main content

Webhosting provider choose XenSource over VMware



Alex Barrett from TechTarget reporting...

Why not VMware?

Why did Putegnat choose XenSource over more established options like VMware or Microsoft Virtual Server?

The answer to why not Microsoft Virtual Server was simple. "I'm not a big Microsoft fan," Putegnat said. Plus, since the applications in Joots' software stack are virtually all open source, he was more comfortable with a Linux-focused virtualization suite.

VMware, however, also runs on Linux quite well, and Putegnat did in fact consider it. But the more he looked, the less he thought it was necessary. "We could have shelled out for VMware, but it didn't seem that important," he said. Joots paid $350 for its initial XenSource license. In comparison, list price for a two-processor VMware Infrastructure 3 Starter edition is $1,000, and it ramps up to $5,750 for Enterprise Edition.

Putegnat doesn't regret his choice. He currently runs 25 dedicated Red Hat 4.5 virtual machines on the first XenSource node and has since added a second server on which he hosts about 40 Debian 3.1 VMs. Each Joots client receives its own dedicated VM that runs a basic LAMP stack plus Joots' proprietary content management system.


Read the rest 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