Your developers want to deploy a variety of dev and test systems yesterday, and your IT admins don't have time to do all that work so quickly, and they don't want a motley collection of dev environments growing like fungus on IT's resources. That's where devops comes in. The term acknowledges the divide between the software development and IT operations sides of a business, with developers eager to implement their latest creations but stymied by cautious IT personnel focused on keeping systems up and running. Both people- and technology-oriented approaches are emerging to bridge this gap.
To break the logjam, solutions are being pitched that range from better collaboration among parties in a project to implementing automation technologies. Indeed, sensing the opportunity, vendors are starting to jump on the devops bandwagon, with companies ranging from Puppet Labs to Zend Technologies pitching their wares as alleviating the devops burden.
[ InfoWorld columnist Eric Knorr makes the case for devops in "Devops and the great IT convergence." | Get the latest insights on programming issues and trends from InfoWorld's Developer World newsletter. ]
Consultant Patrick Debois, who is credited with coining the term "devops" in 2009, cites the proliferation of agile development, with its more frequent software updates, as a factor leading to the need for devops, as operations staff can't keep up with the number of changes being produced. Cloud and virtualization have also contributed to the need for devops, he says, with IT having to manage more machines and streamline the delivery process.
Web deployments also can cause devops conflicts, says Jesse Robbins, chief community officer at Opscode, which makes the Chef automation tool positioned for use in devops. "Ops has historically been tasked with maintaining website availability, and the challenge with that is the best that you can ever do is 100 percent availability." Avoiding outages prompts the operations team to "become strongly opposed to change," Robbins says.
To protect the infrastructure, IT ops can put in place processes that seem almost draconian, causing developers to complain that these processes slow them down, says Glenn O'Donnell, an analyst at Forrester Research. Indeed, processes such as ITIL (IT Infrastructure Library) that provide a standardized way of doing things, such as handling change management, can become twisted into bureaucracy for its own sake. But sometimes, people "take a good idea too far, and that happens with ITIL, too."
Better collaboration advocated
Debois advocates better collaboration as a way to address the devops challenge, with parties collaborating right from the beginning of a project. "That's a shift in mentality," he acknowledges, to collaboration between silos, says Debois. Small behavioral changes can help, he says. For example, "developers are starting to wear pagers [for] when things go wrong, so they actually feel the pain of people supporting the systems. That will improve how they think about it," he says.
"What devops is about is essentially refocusing operations on business results rather than things like processes or tools," says Luke Kanies, CEO of Puppet Labs, which sells a devops tool.
