Since around the turn of the century, I have had a motto that goes like this: “Virtualization is a journey, not a project.” It seems now would be a good time to bring that slogan up to date, changing the message to “The cloud is a journey, not a project.” It really amazes me when people bring it up in conversation that their company is going to build a cloud to better meet the needs of its users and customers. The only thing that amazes me more is the number of people I have talked to who believe that because they have a few hypervisors with virtual machines, they have a cloud.
Articles Tagged with Cloud
So, if you don’t know Mike Laverick, do yourself a big favor and listen to the podcast below. He is a VMware vExpert currently working as the Senior Cloud Infrastructure Evangelist for VMware. His focus is vCloud Director, vCloud Automation Center, and pretty much anything else at VMware that has “Cloud” in the title. He has a very realistic sensibility about all technology, probably due to the fact that he has been in the business for twenty years.
I recently spent a fruitless afternoon on the public PaaS version of Cloud Foundry. In this post, I document an equally fruitless afternoon spent on Red Hat’s OpenShift. It think it is fair to say that OpenShift has some advantages over Cloud Foundry for public PaaS. OpenShift feels more comfortable, its integration of a build server introduces a lot of flexibility into its deployment, it makes it easier to know what is going on, and it seems to have more documentation and more discussion on the forums. However, once you veer away from the standard use case, it doesn’t work terribly well. Ultimately, I failed to get it to do what I wanted, but maybe it was just too hard.
I have been building solutions on AWS since 2008, and even though that sounds like a long time, I have still only scratched the surface of what is possible in the cloud. Every few weeks I get another “Aha” moment when I see problems solved with cloud architectures that would be either too hard, not feasible, or too time-consuming to accomplish in a non-cloud environment. Here is my latest “Aha” moment.
Last week I did a post regarding the future in the cloud computing space that focused primarily on the large number of unfilled positions in the modern-day data center. Employment options for this space should be rich and plentiful for the next decade or so, and I think that is a great thing, but there is something else to take away from the post that should make us all take some time to pause and think. Let’s talk about the skills needed for the data center of tomorrow and take another look at this part of my post:
Pivotal’s public cloud version of Cloud Foundry really struggles with the loose integration of third-party services. To appeal to ISVs and others with real-world complexity in their applications, Pivotal needs to identify a coherent product and concentrate on delivering something that works. I tried assiduously to use it and ultimately failed. In case you think I’m being a bit harsh on Pivotal, this system has been in beta for more than two years. By now, it should work.