Networking

10:45 PM
Charles Babcock
Charles Babcock
Commentary
Connect Directly
Twitter
RSS
E-Mail
50%
50%

7 Habits Of Successful DevOps

Forrester outlines seven practices that will bring developers and operations teams into harmony. But will they get your IT organization singing Kumbaya?

Habit number three is automating the build, test and release processes so they contain less human error. For testing to work, it must include scalability testing on the systems with which the application will run, as well as business function tests, the thing that traditional development teams excel at. Puppet and Chef now capture and help automate configurations and deployments; use them. (The authors didn't specifically mention Puppet and Chef).

The whole data center infrastructure must be revamped toward delivery of services from a more standardized environment. The process will be a long one, with both business users and developers losing some of their preferred, best-of-breed systems in favor of good enough Linux and Windows systems. The old way led to ever-increasing complexity, and that complexity was accompanied by an increasing fragility. So habit number four is simplify, standardize the development and production environment. Rigorously enforce that simplification on new applications. Then as much as you can, simplify legacy applications. It's a huge task.

Number five is to instill a culture of systems engineering across both development and operations. "Real engineering works in a disciplined, thoughtful way ... to reduce solutions to be -- as Albert Einstein recommended -- as simple as possible but no simpler." Building up software based on simple modules makes it easier to deploy and maintain, and to reuse.

Number six, the authors said, is implement feedback and feed-forward loops. Software is complex and requires feedback on how it's operating. Oftentimes, developers don't know. Testers and operators are often engaged only at the end of a project. They need to be involved early. Likewise, information that explains how an application is expected to operate, such as its dependency mapping, needs to be fed forward to operations and development teams that may be working on the next similar application.

The last habit is put developers on the frontline of support. They don't want to be there. It takes them away from the creative process of building more code, the place where their reputations are already staked out. But the developers who built the code will have the greatest understanding of why it's running poorly in production and produce the quickest fixes. And needless to say, developers will learn a lot about production as they watch their code run in its target environment.

These seven habits will not come as any surprise to the people who have already struggled with DevOps and moved their organizations closer to a combined-function IT staff. But they will come as education to more traditional staffs that are comfortable in their isolation from each other. That isolation includes some protection from being taken out of one's comfort zone and put in a situation where something more is expected of you.

Facebook automated the configuration and deployment of software to 17,000 servers using one Chef server, point out the authors. That's because it was able to build from scratch a simplified and standardized environment. The DevOps gain in automation is self-evident.

Amazon is constantly updating its production systems without fear of unintentionally torpedoing its operation. It does so through an automated test procedure in an environment that matches the production environment. Jon Jenkins, Amazon's director of platform analysis, stated at the Velocity conference in 2011 that someone is deploying code to production "every 11.6 seconds," usually to 10,000 servers at a time. In the average IT shop, such deployments would be suicidal, considering most outages are due to software updates. The DevOps gain in production reliability is self-evident.

Etsy deploys new features to its online, artisan marketplace with only one IT person on duty, thanks to its DevOps rigor of developing new code. Each addition is carefully tested and pushed when ready, rather than planning for a big team push to update a system once or twice a year.

The point of DevOps is to get both teams to treat their responsibilities as a science and to reduce the amount of science fiction involved when dealing with one another.

Learn more about DevOps by attending the Interop conference track on the Business of IT in New York from Sept. 30 to Oct. 4.

Previous
2 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Drew Conry-Murray
50%
50%
Drew Conry-Murray,
User Rank: Strategist
9/9/2013 | 10:53:43 PM
re: 7 Habits Of Successful DevOps
I like Lorna's comment about "homo technologus." We have seen this fight before (think security and everybody else, for example). But silos are starting to crumble everywhere as virtualization mixes up job responsibilities and operational tasks, so maybe everybody can all learn to get along.
Lorna Garey
50%
50%
Lorna Garey,
User Rank: Ninja
9/9/2013 | 7:26:26 PM
re: 7 Habits Of Successful DevOps
Woe to the ops team whose developers are in Bangalore. Midnight planning calls anyone? Seriously, I must admit to being skeptical about this concept myself. Remember when it was the telco team fighting with the Ethernet guys? Territoriality is a core trait of species homo technologus. However, the security problems in apps and the growing complexity of networks does beg for something to be done.
moarsauce123
50%
50%
moarsauce123,
User Rank: Apprentice
9/7/2013 | 12:47:35 PM
re: 7 Habits Of Successful DevOps
I like the last habit, nothing straightens out a developer more than a complaining customer. It is very important for developers to know their audience as most developers will never use their own program in a production.
cbabcock
50%
50%
cbabcock,
User Rank: Apprentice
9/6/2013 | 7:53:40 PM
re: 7 Habits Of Successful DevOps
I've often heard a background debate over who's really trying to get to DevOps. Isn't it just window dressing? In my opinion, many of the best companies are there or are trying to get engaged in DevOps..
Hot Topics
13
Why Facebook Wedge Is Revolutionary
Tom Hollingsworth 7/16/2014
10
Open Source Vs. Open Enough
Bob Laliberte, ESG senior analyst,  7/18/2014
5
Do We Need 25 GbE & 50 GbE?
Jim O'Reilly, Consultant,  7/18/2014
White Papers
Register for Network Computing Newsletters
Cartoon
Current Issue
2014 Private Cloud Survey
2014 Private Cloud Survey
Respondents are on a roll: 53% brought their private clouds from concept to production in less than one year, and 60% ­extend their clouds across multiple datacenters. But expertise is scarce, with 51% saying acquiring skilled employees is a roadblock.
Video
Slideshows
Twitter Feed