Over the last few weeks, VMware (as we indicated in an earlier post) and Red Hat have initiated two very similar initiatives known respectively as CloudFoundry and OpenShift. These are Platform as a Service (PaaS) plays, being developed for the longer term, primarily looking to encourage the development of (and thereafter to provide infrastructure for) applications specificallysuited to the the cloud. In this article we compare and contrast the two offerings and discuss their significance for the PaaS market as a whole.
Articles Tagged with Red Hat
Traditionally, internet companies like Google consider their custom server and data center designs as proprietary knowledge that creates significant value, but last week Facebook (which had previously bought commodity servers and rented data center space) has opened up a whole new area of Open Source technology by publishing the full specification of both its new custom server and its new data center as “Open Source” at OpenCompute.org.
Facebook’s designs aim to reduce capital costs by removing unnecessary components from the server and the data center, and by simplifying manufacture and construction. They also seek to reduce running costs by increasing the efficiency of power usage. Although the initiative has been “Greenwashed”, reductions in power consumption seems primarily motivated by saving cost, not saving the planet.
Red Hat announced on November 30, 2010, for an undisclosed sum, the acquisition of startup PaaS vendor, Makara, which provides a deployment platform for most of the Open Source application stacks (Apache, MySQL, PHP, Java, Tomcat and JBoss) onto most of the IaaS cloud infrastructures (Amazon EC2, Amazon VPC, Rackspace Cloud, VMware vCloud, Terremark, Cloud.com and Eucalyptus). Makara is not open source, although the company was committed to open sourcing in due course, and Red Hat is aiming to accelerate that process.
VMworld is clearly the largest dedicated virtualization conference, and yet from an Open Source perspective it is slightly disappointing because the VMware ecosystem naturally attracts proprietary software vendors, and also some of the more interesting activities in Open Source are through multi-vendor foundations which do not have the same marketing budgets as vendors themselves.
Nevertheless, there are a number of key Open Source players, and some interesting smaller players, represented at VMworld.
As of Service Pack 1, SUSE Linux Enterprise Server 11 (SLES) supports KVM. The bald facts are as follows. SLES 11 SP1 is based on a 2.6.32 kernel and is now full supported on x86_64 processors which support hardware virtualization, for the following guest operating systems:
- SUSE Linux Enterprise Server 11 SP1
- SUSE Linux Enterprise Server 10 SP3
- SUSE Linux Enterprise Server 9 SP4
We note there is no mention of other Linux guests or Windows guests. This post follows on from our previous post regarding the demise of Xen in Red Hat Enterprise Linux, and perhaps suggests the beginning of the end for Xen-based virtualization in Linux, but the story is far from clear.
The Red Hat 6 Beta is out, and there is no Xen in it, only KVM. It can operate as a guest in an existing Xen environment, but it cannot act as a Xen host. This isn’t new news, it was widely trailed, but with the emergence of the Beta, there now appears no way back. Xen and RHEL are divorced.
For much of The Virtualization Practice audience, this may seem peculiar. Why (and even how) could Red Hat turn its back on a world-class Type 1 Hypervisor and run with this peculiar Type 2 thing, that nobody has really heard of, and that has such a low profile that people even confuse it with a monitor/keyboard switch also called a KVM?