Moving on with the 2nd in my series of Enterprise Devops posts.
As I write this, I am listening to this excellent presentation of John Allspaw and Paul Hammond of Flickr, which goes into great detail around the core DevOps problem of writing code and applying continuous integration principles.
However, my intent in this blog has more to do with the problem of "infrastructure as code." As I noted previously, DevOps practices in the enterprise case would need to accomodate a wide variety of tools and middleware beyond Java, RoR, and the LAMP stack.
In general, I view this all as an exercise in element configuration management (discussion of three flavors of configuration management, also element vs. enterprise config). The question for the enterprise is
to what degree is your current infrastructure technology portfolio suitable for DevOps practices?