I mentioned in another post that there is a big push for the current VMware VCP4’s to prepare to take the VCP5 exam by the end of February when the grace period for not having to take a class is over. I did leave out one other great resource that is worth mentioning. Cody Bunch hosts the BrownBags on Wednesday nights. The sessions have been focusing on the VCP5 exam blueprint and this week’s guest was Jason Boche (VCDX #34) and he did a great job, as always, presenting the information on virtual machines and giving the rest of us extreme home lab envy. After the VCP roadmap is the finished the BrownBags will continue with the VCAP blueprint with the idea of working for the VCDX. If you are interested in another way to study and learn from some well established people in the industry sign up and check things out.
Articles Tagged with Red Hat
In 2012 should you use Virtual Infrastructure, Infrastructure Cloud (IaaS) or Platform Cloud (PaaS). Which one has crossed the Chasm?
Now, of course, this is a simplified version of the question, because in almost all cases Infrastructure Clouds and Platform Clouds are built on a Virtual Environment, and in most cases Platform Cloud is built on an Infrastructure Cloud, so the question is really about how far into the Cloud you should be prepared to go. My perspective here is of a development manager – someone who is charged with building a new application. I’m thinking as a development manager not a developer and I’m making decisions to maximise the productivity of a development team – rather than on the “shininess” of the technology – by developing in the cloud.
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. The choice to go with this set of technologies is documented in Why would a Developer choose VMware? and my experiences leveraging the Open Source ecosystem around Groovy/Grails is outlined in VMware’s SpringSource Ecosystem
We’ve touched on Red Hat’s Cloud strategy in a number of posts. To summarize they’re trying to play at all levels in the stack, from IAAS and PaaS through to hypervisor and of course operating system. All layers are open, and as you get further down the stack towards virtualization they are pushing KVM but they are clear that they have to co-exist with Microsoft and VMware. In the IaaS layer they have DeltaCloud, which is nominally open but is really a Red Hat product with an open veneer. In the PaaS layer they have a stack of really good middleware from JBoss, and an openness to a whole bunch of Java/JVM and non-JVM languages. They’re punting this out to the world as OpenShift.
So far, although there are nuances that differ from other vendors, the main conclusion is that each individual layer is comparable to offerings from competitors. However, there is one layer that sets Red Hat apart from competitive offerings, known as MRG – Messaging Realtime and Grid, pronounced “Merge”. If you’re wondering what this is, it seems also that some of are bits of Red Hat’s marketing department that haven’t got a clue either because the market positioning is a bit vague.
As mentioned in my previous piece I’ve been doing some prototyping using SpringSource’s Grails. Grails can be thought of as the top of the stack. If you pick up Grails you would naturally pull in the other pieces of SpringSource, including vFabric and ultimately CloudFoundry. In a future post I will deal with what happens when you stick Grails onto CloudFoundry, but at this stage I’ve been assessing the health of the SpringSource Ecosystem.
VMware’s CloudFoundry announcement has enormously clarified VMware’s long term strategy regarding its role in the Systems Software business. When VMware acquired SpringSource two years ago, it had application platform strategy that consisted of offering an enhanced version of Tomcat along with some development tools. This put VMware on the Java side of the Java vs. .NET wars, which was interesting, but it did not address the rapid proliferation of other application run time environments like Ruby and PHP that were continuing to drive the envelope of developer productivity.