When enterprises consider putting business-critical workloads in public clouds, many of them overlook, at least in part, critical issues of economics and over what portion of their cloud software stack the cloud vendor has full control. This leads to a situation where sometimes relatively inexpensive offerings where the vendor has full control of their software stack (like Amazon EC2) are improperly compared to an offering from a vendor like Savvis or Terramark who is building a cloud out of either VMware-provided components or OpenStack components. This gives rise to important issues that drive both the cost of the respective offerings and the degree to which the cloud vendor can both enhance the offerings with rapid agility and quickly address service level issues.
Articles Tagged with OpenStack
Last week’s inaugural board meeting of the new OpenStack Foundation signaled a change in the organization as Rackspace the driving force behind OpenStack handed control to the newly formed board. Allen Clark director of SUSE was appointed chairman, with Lew Tucker Cisco’s VP and CTO of cloud joining the board as Vice Chairman. Members of the OpenStack community who had voiced concerns that OpenStack’s founder Rackspace’s had too much control over the project should be please by these appointments which are seen as key to establishing OpenStack’s bona fides.
In Open Source it’s impossible to keep a secret (and in any case Anti-Trust laws make it very risky). And despite the imminence of VMworld, the governance processes of OpenStack run to their own timetable, so some interesting news about VMWare was made public on Sunday 26th August – the day before VMWorld – that VMware joins OpenStack.
The PaaS market had a major false start in the period 2009 to 2012. The first PaaS vendors came to market with one of two premises
- “we’ve got a really great platform you can use it if you want to”. Good examples are Force.com (A PaaS derived from an IaaS – salesforce.com), Google App Engine and the original version of Azure
- “it’s a great place to run applications in a particular language” – good examples are Heroku (ruby) and PhpFog (PhP)
Since 2011 a second-generation of PaaS infrastructure has emerged which is exemplified by VMware’s CloudFoundry and Red Hat’s OpenShift. The biggest change between first and second generation PaaS is in the mindset. Instead of the first “P” in Platform as a service referring to “a Platform” it now refers to “any Platform”. In other words the job of the PaaS is to support any application in any language and deliver any set of services that any application might reasonably require. Whilst the first-generation PaaS was generally monolithic, the second-generation PaaS is usually capable of being implemented on a broad range of IaaS and/or virtual infrastructure, and the key factor is openness and diversity. Thus CloudFoundry can be implemented on OpenStack.
There has been quite a lot of twitter traffic about the FrankenCloud recently: A cloud with more than one type of hypervisor underneath it. One example, is to build a cloud using Hyper-V three and vSphere, both managed through Microsoft System Center. Another example, is to build a cloud using Hyper-V, KVM, and vSphere all managed through HotLink. But is this a desired cloud topology?
Piston Cloud Computing raised a few eyebrows on Tuesday with the announcement that it was extending its Piston Enterprise OS (PentOS) to provide a platform for hosting virtual desktops (VDI) through an exclusive licensing deal with Toronto-based Gridcentric for its innovative Virtual Memory Streaming (VMS) technology.