There is now a huge amount of movement in the area of what we have called “Diverse” Platform as a Service i.e. PaaS that delivers a number of different application infrastructure technologies on a mix-and-match basis and where there is no proprietary technology layer at any point in the platform stack. Amongst these we would include OpenShift, Cumulogic and CloudFoundry from our recent set of posts. AppFog sits in this category, and the fact that it has been recently renamed from PHPFog highlights a major trend in the space, the vendors typically start by developing a single technology, build an initial business plan and gain some market traction within that niche, and then move on to supporting a broader range of platforms.
Over the last few months we have identified a trend towards “diversity” in the PaaS provider marketplace. Platform as a Service has become Platforms as a Service, the providers are offering multiple choices at each layer of the platform infrastructure, and seeing their role as automating the provisioning of properly-configured instances as required at each layer of the stack.
On Aug 2nd, there was another entrant to this “diverse” PaaS provider marketplace called Cumulogic, a startup with a PaaS cloud positioned alongside Red Hat OpenShift and VMware CloudFoundry that we identified earlier.
As mentioned in a couple of recent posts, I have been building a prototype application using Open Source technologies that I plan to install on a number of available PaaS cloud platforms. The application is written in Groovy (with some bits in Java) and built on the Grails framework. This article is about my use of RedHat OpenShift PaaS and the controls available.
Over the last few months an additional subproject codenamed Quantum has emerged which deals explicitly with networking and has particpation from networking giants Intel and Cisco as well as from Citrix. It’s a mechanism for defining network topologies aimed at providing Layer-2 network connectivity for VM instances running in clouds based on the OpenStack cloud fabric. It is designed to be extensible to allow higher-level services (VPN, QoS, etc) to be built on top, and to cleanly handle the “edge of network” problem (i.e. the binding of the cloud into the internet).
Red Hat’s Cloud is to play at all levels in the stack, from IaaS and PaaS through to hypervisor and of course operating system. Each layer is comparable to offerings from competitors.except for MRG – Messaging Realtime and Grid, of which version 2.0 has just been released.
One of the most intriguing names that has hitherto been at the periphery of the OpenStack initiative is Citrix. Up until last week, Citrix’s contribution was to ensure OpenStack ran on XenServer. However, this week at it’s Synergy event, Citrix made some more sigificant announcements about Project Olympus, through which it aims to provide (in collaboration with Dell and Rackspace) a route to commercial exploitation of the OpenStack codebase. For some time I have been perplexed as to what Citrix is doing. Are they genuinely intending to enter this space? Is this the real play or is it a spoiler?