PaaS and open source

Ted Leung has some interesting ideas about Platform As a Service (PaaS) and open source. I agree with Ted that open source software is not becoming any less relevant. Looking at current platform as a service offerings Ted’s view of,

The more interesting question for developers has to do with infrastructure software. In my mind LAMP is really a proxy for “infrastructure software” If you’ve been paying any attention at all to the development of web application software, you know that there is a lot happening with various kinds of infrastructure software.

is understandable. Almost all the current PaaS vendors have developed mechanisms to harvest commons based peer production. Ultimately all of this ends up in some server of a vendor locked away in a data center somewhere. Most of the vendors use open source software heavily for their PaaS offerings and some have open sourced bits and pieces of their platform. While I’m certainly not the overzealous freedom fighter I was, this awfully sounds like writing open source applications for a proprietary platform. Not that it’s necessarily a bad thing. Unlike developing software on a proprietary operating system, developing on a proprietary platform as a service offering is limited in various aspects which are unique to its usecase.

So, IMHO, a more interesting problem to tackle in an environment like this is open source platform as a service. You still have a hosted service where people can just develop applications and forget about underlying technical details of the platform, where your data is residing and so on. At the same time this entire platform is open source! Sounds like a pipe dream but it’s a reality. I hope this will set a trend that other vendors follow, eventually.

The open source platform as a service is Stratos. The hosted platform reside in cloud.wso2.com where anyone can register for free (during the alpha and beta stages) and get an entire middleware platform at your fingertips with a few clicks. Another bold move is that the code base of the downloadable version and the hosted version are exactly the same! So, the platform itself and hosted applications behave in a predictable manner where ever they’re deployed. Also, it should be mentioned here that most of the services provided by Stratos started their life as standalone programs (like Tomcat). This also, provide invaluable repository of information if anyone wants to study how their should architect their applications to make them cloud native. Source code for the entire platform available here.

Posted in open source, paas, soa | Leave a comment

What is AGPL?

Recently bumped into a license called AGPL. If you don’t know what it is, just by looking at the name you can guess that it’s one from FSF. AGPL is designed to close the “ASP loophole”. What does that mean? If you’re using GPL licensed software, you MUST release the source code if you’re redistributing the software. For example, if you use a GPL licensed library or program in your software projects, when you put your product out there (either sell or give it away free) you must release the source code for your program under the same license. So your program will also be GPL licensed automatically. If not it’s a violation of the GPL licensing terms.

Now, if you use a GPL licensed program in the server side (a CMS such as WordPress for example) to provide a service and you’ve done some modifications to the server side software, then even though it’s GPL licensed you don’t have to release your modifications. In this case you’re not really redistributing the software so you’re alright. This has been referred to as the “ASP loophole”.

So, AGPL is designed to close this “loophole”. Meaning, if you’re using an AGPL licensed program on the server side and you have done some modifications, you MUST release the source code with those modifications.

My view about the AGPL, as with anything GPL, don’t bother.

Posted in agpl | 2 Comments

VMware ESXi on Realtek NIC

VMware ESXi 4.0 doesn’t support Realtek RTL8111/8168 network cards by default. When you try to install ESXi on a computer with a Realtek NIC it will say the network card is not supported and will not allow you to proceed with the installation. Luckily you can modify the ESXi ISO to include the Realtek driver so that you’ll be able to install it without a problem. A forum post describes how to do this. I’m echoing the steps below.

  1. Create a folder and copy your VMware ESXi ISO file
  2. Download RTL8111_8168_P55_integr_SATA_Ctrl.(AHCI).oem.tgz and copy it to the folder you just created
  3. Download mkesxiaio_3.9.sh and inetd.conf from here and copy it to the same folder.
  4. Run sudo ./mkesxiaio_3.9.sh
  5. Burn the modified ISO

Realtek network cards are not exactly esoteric hardware. Not sure why the default installation doesn’t have support for this. If you’re trying to install ESXi better check the HCL.

Posted in virtualization, vmware esxi | 30 Comments