What's the problem with DevOps?

| 2 Comments
| More

There's a small problem with DevOps; for some at least... DevOps is just a bit too much Ops and not quite enough Dev.

It looks good on paper and the "blending" of software application development and systems operations team functions into the spiritual portmanteau that is DevOps should be good news for everybody.

Orchestration, IT automation & release management

But, of course, in reality, software application developers still "throw applications over the wall" to Ops despite the best efforts of those vendors in this space who seek to provide so-called "orchestration", IT automation and release management tools.

Naysaying aside though, DevOps darling Opscode is pointing to what it calls "soaring adoption" for its Enterprise Chef automated configuration management and application delivery product which works across large-scale virtualised infrastructures.

NOTE: Chef is an open-source systems management and cloud infrastructure automation framework created by Opscode -- Enterprise Chef is, unsurprisingly, the paid for enterprise version.

DevOps as a two-department function is able to use Chef to deploy and manage servers and applications (both in-house and in the cloud) -- and what are known as "cookbooks and recipes" exist to tell Chef how each node in an organisation should be configured.
Chef: a primary automation platform?

The firm asserts that European companies are using Enterprise Chef as their "primary information technology automation platform" for both infrastructure and applications.

a picture of a sign.jpg

Mini Case Study

PaddyPower is Ireland's largest bookmaker, serving Ireland and the UK with online, mobile, and physical retail outlets. To squeeze their cycle times from concept to cash, the sports betting company deployed Enterprise Chef combined with Cloudify to automate resource configuration and application delivery for its CloudStack infrastructure. Using Enterprise Chef, PaddyPower created a continuous delivery workflow capable of deploying app updates in minutes instead of days.

So does DevOps have a problem?

Well yes, nothing is perfect.

But as it now becomes physically impossible to manually build, test, and deploy fast Agile cloud-based applications across an heterogeneous infrastructures... perhaps we still need to give DevOps peace a chance.

2 Comments

I think the biggest issue is that developers are pressured to get something, anything really, out the door in as short amount of time as possible. The need for speed means other factors in application security are overlooked or only marginally considered.

Chef is a great tool to supplement the DevOps process. However, DevOps succeeds best with a culture to support it, and technology that supports the entire process. In my experience, cloud-based DevOps can significantly reduce time to market for new applications and services. With a cloud management platform, developers can be provided self-service, on-demand access to not just VMs, but full development platforms incorporating the production Standard Operating Environment, enabling them to find bugs earlier in the software development lifecycle, deliver faster, and iterate more quickly. IT Operations can seamlessly deploy knowing that apps and services were developed and tested with the production SOE... For more: http://www.servicemesh.com/cloud-it-resources/cloud-strategy-transform-it-blog/blog/development-stuck-in-the-middle-of-shadow-it/
- Shawn Douglass, CTO ServiceMesh

Leave a comment

(You will need either to sign in or enter a valid email address to comment.)

About this Entry

This page contains a single entry by Adrian Bridgwater published on November 18, 2013 10:22 AM.

Google: Chrome safer than Acrobat for PDFs was the previous entry in this blog.

Intel Inside... and Underneath and Behind too? is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Categories

Archives

-- Advertisement --