What happens downstream?: Scott Mattoon's blog

Ian Kallen over at Technorati wrote a nice post about the cloud computing ontology and the subtleties of Infrastructure as a Service (IaaS).  I'm glad to know he's still working on the hard problems there at the blogsphere search engine after their recent cost cutting measures.  As he has said to me previously, he writes, "What I foresee is that the first vendor to embrace and commoditize a standard interface for infrastructure management changes the game."  I think he's right, particularly in his prediction that these standards will enable a market place in which workloads can be moved from cloud to cloud according to price, capacity, and feature criteria.  A few companies are jockeying for the pole position in the race to provide the arbitrage for this meta cloud that Ian envisions.  Rightscale is perhaps in the best spot for that right now.  But who's going to set the standards for interfacing with clouds.  It's still pretty early in the game, but there's no question that Amazon has a good leg up with the AWS API's, which are further butressed by Eucalytus's emulation of those interfaces in their open source Xen based IaaS stack.  Meanwhile, Ruv over at Enomaly is fostering a Unified Cloud Interface (UCI) standard to be submitted to the IETF next year.  Conspicuously, it appears that Amazon is involved in neither the Eucalyptus nor UCI standards efforts.  Meanwhile, Rightscale is working closely with Rich Wolski's Eucalytus team, and both of these standard bearers are advising on Sun's Network.com model.  It will be interesting to witness the evolution of agreed upon standard interfaces in the presence of the defacto standard that is AWS.  Until there's a cleaner and/or cheaper way to develop on OpenSolaris in the cloud, I'll continue to write to the AWS interfaces to launch and extend instances of OpenSolaris on EC2.