Skip to main content

Should VMware open source ESX server?



This blogger has some points to make about open sourcing ESX server.

His arguments are:

  • ESX is already using many open source technologies and components, whether we say it's built on top of Linux OS, using Linux kernel, or is a Linux derivative, it is built on an open source foundation.

  • ESX Server make Linux users feel at home, and Linux community are used to find, evaluate and use open source projects before they recommend it to their employers and use it in the enterprise, imagine a project called OpenESX, and fully open source and free virutualization project where anyone if the world can contribute to the design, development, testing, and documenting of every part of it just like Fedora project and Redhat. VMware will sponsor the project and support the development.

  • It will provide rapid progress, more innovation, closeness to the users, and larger user exposure: open source's advantages.



Good point but in the wake of the apparent legitimization of Linux and Open Source and also the move of open source firms building products with OSS stack and going proprietery (with a OSS arm as well) why should VMware go that way. I am not saying that its a bad move, in fact it is a very good move. but I want to know from experience of other firms (who have gone that way) a couple of things:

  • Did your sales shoot up after the release of your OSS?
  • What is the added value (I know community and all that stuff but )?
  • What about reputational advantage or disadvantage (Think of that prolific developer who walked out of fedora because of poor patching and other issues. This guy was a loyal, not on payroll, but loyal. Then he defected to Ubuntu)
  • Manageability: You'll need a huge and a long arm to manage that OSS initiative, do you have the capacity to do that? Do you pay those project members enough so they can help you out and give you a good report?
  • Cash and Investors: what do the investors think?
I think if that was a good path then Microsoft would have gone that way long long ago.

Now in favor:

  • User community would benefit greatly from it.
  • That will make ESX almost pervasive and a household name
  • Innovation will shoot inall directions: Super computing, mobile devices, provisioning, etc
My advice:

  • Have people on your payroll and not just some amateur or professional contributors because they can step away when jilted. Better get them onboard if you want to go that way!
  • Metrics: Keep the fundings tight and measure the projects regularly. Keep asking questions: does it generate any value? does it generate cash? If not, shelve it!
  • Investors on board. Very crucial!
final advice: Should they? I'd say "not yet, not in 2007 atleast!"

Read this post.
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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...
Post a Comment
Read more