There’s been an interesting debate on the OpenStack cloud computing project and its API compatibility with Amazon. The discussion and debate over the open source cloud software’s compatibility with cloud leader Amazon’s proprietary APIs was just beginning when the 451 Group released The OpenStack Tipping Point in April. With the advancement of the OpenStack software and community — along with lingering questions about the desired level of compatibility with Amazon’s cloud — the matter is heating up. However, the issue of Amazon cloud compatibility is largely a non-issue.
Enterprise customers are focused on solving their computing and business challenges. They typically center on promptly providing their customers and internal users and divisions with adequate resources and infrastructure; speeding application development and deployment; and avoiding so-called “Shadow IT,” which normally involves use of Amazon’s cloud. Read the full article at LinuxInsider.
I’m not the only one with an opinion around here. My 451 Research colleagues have also weighed in on the matter and 451 Research subscribers can view their argument that Amazon API compatibility may be a fool’s errand.
It’s been some time now that we’ve been talking about devops, the pushing together of application development and application deployment via IT operations, in the enterprise. To keep up to speed on the trend, 451 CAOS attended PuppetConf, a conference for the Puppet Labs community of IT administrators, developers and industry leaders around the open source Puppet server configuration and automation software. One thing that seems clear, given the talk about agile development and operations, cloud computing, business and culture, our definition of devops continues to be accurate.
Another consistent part of devops that also emerged at PuppetConf last week was the way it tends to introduce additional stakeholders beyond software developers and IT administrators. This might be the web or mobile folks, sales and CRM people, security professionals or others, but it is typically about applying business operations methodology to applications and IT, thus bringing in more of the business minds as well. The introduction of additional stakeholders was also a theme we heard from Puppet Labs CEO Luke Kanies in his keynote address. Kanies then discussed how the community was working to make Puppet the ‘language of operations,’ which it basically is along with competitors Chef from Opscode and CFEngine when it comes to devops implementations.
There was another interesting point on the PuppetConf stage from DTO Solutions co-founder and President Damon Edwards, who said devops should not be sold as a way to achieve cost savings, but rather as something that will bring return on investment (ROI). This is similar to the shift of open source software drivers we’ve seen in the enterprise, which are sometimes changing from cost savings and time to factors of performance, reliability and innovation.
Later in the conference during his keynote, Eucalyptus Systems CEO Marten Mickos also had some interesting observations concerning devops, which he described as managing the cloud from both sides. One of his points was that developers have the most to learn about operations. While I would agree to some extent, this statement is interesting when considered alongside my contention that most of the change in devops is happening on the IT administrator and operations side. Later in an interview, Mickos elaborated on his devops thinking, indicating the experts who orchestrate applications in cloud computing — both developers and admins — must understand the entire lifecycle and environment. Continuing our comparison of devops to open source, Mickos indicated the open source MySQL database that he helped usher into the enterprise was disrupting old technology, while devops is innovating new technology.
While it remains early days for devops in the case of many enterprise organizations, we continue to see and hear signs that devops practices, technologies, ideas and culture are making their way into more and more mainstream enterprise IT shops. While we expect devops practices to be implemented by many enterprises based on utility and need to leverage cloud computing, we see a higher level of awareness and engagement from leadership and executives than we did with open source software. This means we expect uptake of devops to happen more quickly and to generate more revenue and opportunity.