Arguments for and against the cloud are starting to calm down a bit, and most people agree that the cloud is somewhere in your future, if not in your present.
Instead of arguing semantics of application development and delivery, the discussion should really be around how to deal with a mix of on-premise and on-demand, a combination that is unlikely to change in the foreseeable future.
I spent the first half of this week in Las Vegas at a nontech trade show, and missed both VMworld and the Red Hat Summit. However, watching and reading from afar, I noticed two major themes in discussion around both cloud computing and virtualization: cloud interoperability and the lack of application management tools.
Cloud interoperability--the ability to abstract the programmatic differences from one cloud to another--is a key to adoption. If we assume that some percentage of private compute clouds will be based on virtualization, and we know that a large percentage of public clouds already are, then the ability to move among virtual machines is a critical function in this regard.
Red Hat is obviously taking interoperability seriously, with Thursday's launch of Deltacloud, a new open-source project "designed to enable an ecosystem of developers, tools, scripts, and applications that can interoperate across the public and private clouds."
Let's remember that right now, there is a difference between managing applications that are in your own data center and managing those at a cloud provider. Missing here are new management tools that cross borders in a seamless manner and don't discriminate against different hypervisors or application platforms.
Cloud application management isn't so much about workloads as it is the ability to move applications and associated data from cloud to cloud and system to system with no interference. This new realm of internal-external systems management opens up a world of opportunities but faces some significant speed bumps.
I noted last week that Amazon's announcement of virtual private clouds presents a challenge for many cloud-oriented start-ups. The issue is that Amazon calls the shots on the cloud and VMware on virtualization. And while both companies have done fairly well by their users (let's say better than we would expect from Microsoft or Oracle), innovation is stuck within their respective ways of doing things.
Regardless, there is a cloud management opportunity, with open-source projects like Puppet, as well as Red Hat's new release of Network Satellite 5.3. While neither is cloud-specific, applications that support large-scale infrastructure management are perhaps the first step in harnessing the computing power inside and attached to your data center.
Arguments for and against the cloud are starting to calm down a bit--and most agree that the cloud is somewhere in your future. The discussion should really be around how to deal with a mix of on-premise and on-demand, a combination that is unlikely to change in the foreseeable future.
Follow me on Twitter @daveofdoom.
Over the last several months I've changed my opinions on open source any number of times. I like to think I'm not just being fickle and instead it's market dynamics that are shifting focus and opinion.
I was recently quoted in an article about open-source "leeches", and in many situations I stand behind the comments. As it turns out, one of the companies I mentioned is now paying, though many others are still not. Freeloaders will always be part of the open-source game, and I think we all accept that, even if it gets under your skin occasionally. At this point, I don't really care--I'd rather see more unpaid open source than expensive proprietary software in use.
In the past I've had bewildering conversations with CIOs and VPs where they told me that they wouldn't contribute code back because they had "created IP--why would we give it to you for free?" while generating hundreds of millions of dollars on top of open-source software that someone, somewhere had given to them for free. I guess that's the sticking point. Not the freeloading, but the assumption that what they created is somehow more valuable than the product that they built on top of.
This brings up a whole world of issues for those trying to build open source companies. Lately, I'm becoming less convinced that you can build a pure-play open source company if you don't fall into two broad categories: direct replacements or inventions.
... Read more
The Puppet framework provides a means to describe IT infrastructure as policy, execute that policy to build services then audit and enforce ongoing changes to the policy. Basically Puppet makes infrastructure management dramatically easier.
Listen now:
Download today's podcast
You can also download the MP3 or OGG file.
In this episode:
- What is Puppet and who uses it (Digg, Google, lots of others)
- How to explain Puppet to business-jerks like me and Matt
- How does Luke as an engineer think about open source business models
- The big problem of cloud computing without centralized management
- The value of high-quality technology and effective IT management
- How does a guy like Luke figure out the commercial strategy for his open source project
- We find out that our guests don't listen to us
- Your choice of open source license has a huge impact on your business
The opening music this week is 'Fix up, look sharp' from Dizzee Rascal's Boy in da Corner
You can follow us on Twitter @daveofdoom and @mjasay.
- prev
- 1
- next
