DevOps: Stop The Existential Angst - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
IT Leadership // IT Strategy
Commentary
9/10/2014
09:06 AM
Lori MacVittie
Lori MacVittie
Commentary
50%
50%

DevOps: Stop The Existential Angst

Want to use DevOps to improve time to market, decrease risk, and reduce operating expenses? Then stop with the navel-gazing and start taking advantage of scripting, templates, virtualization, and open APIs.

Twentieth-century philosopher Jean-Paul Sartre embraced existentialism throughout his works -- works I do not recommend unless you have insomnia. To save you the pain of slogging through Being and Nothingness: An Essay on Phenomenological Ontology, I'll sum it up: Words are cheap. Actions are what count.

In short, the meaning -- of life, of mankind, of the universe -- is defined by what we do, not by what we say. Let's apply that to DevOps for a moment, because the industry is currently churning in a sea of turmoil over the definition of DevOps. Is it people? Is it a cultural shift? Is it the tools you use to apply an agile methodology to operations? Is it a role? A group? A title?

I say, forget all that. DevOps is as DevOps does.

[Want more on how to harness DevOps? Attend Lori MacVittie's Interop workshop, Achieving Operational Excellence Through DevOps.]

Rather than asking what DevOps is, ask what it does for you and your organization. What DevOps will do is a far better question than what it is, because by answering what it will do we get a better understanding of what it is. (How's that for existential reasoning?)

DevOps improves time to market. How? By operationalizing the processes that provision apps and their supporting infrastructure. By using scripting, templates, and open APIs, operations can automate and orchestrate the process of provisioning the services necessary to move an app into production.

It decreases risk. How? By promoting the practice of encapsulating infrastructure as code and reducing the number of keystrokes necessary to provision compute, storage, and network services. Human error remains a significant contributor to disruptive data center downtime. Reducing the number of keystrokes means reducing the number of errors and thus decreasing the risk associated with a deployment.  

It reduces operating expenses. How? By automating and orchestrating deployments, the number of hours (and people) needed to provision and run services can be reduced. That means less cost per application and more money available to spend on innovation, new services, and evaluating new technology.

So take action -- explore frameworks and tools such as Puppet, Chef, Vagrant, and Ansible, and evaluate software-defined systems such as OpenStack, VMware NSX, and Cisco ACI.

Through action -- the process of implementation -- DevOps promotes a more collaborative environment because in order to orchestrate the deployment of an application, you have to know all the services and systems that must be provisioned and configured to succeed. That means operations, networking, security, and development must cooperate to define the entire package that makes up an application when it's finally in production. There's the cultural change aspect, but whether it's the chicken or the egg is debatable and, I'd argue, largely irrelevant. That it will happen is inevitable, because the end goal requires it.

So don't worry too much about the definition of DevOps.

DevOps is as DevOps does.  

In its ninth year, Interop New York (Sept. 29 to Oct. 3) is the premier event for the Northeast IT market. Strongly represented vertical industries include financial services, government, and education. Join more than 5,000 attendees to learn about IT leadership, cloud, collaboration, infrastructure, mobility, risk management and security, and SDN, as well as explore 125 exhibitors' offerings. Register with Discount Code MPIWK to save $200 off Total Access & Conference Passes.

Lori MacVittie is the principal technical evangelist for cloud computing, cloud and application security, and application delivery and is responsible for education and evangelism across F5's entire product suite. MacVittie has extensive development and technical architecture ... View Full Bio
We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Mike Fratto, Editor
50%
50%
Mike Fratto, Editor,
User Rank: Apprentice
9/11/2014 | 9:44:06 AM
Re: Sisyphus needed DevOps
But Drew, then Sysiphus would have had to properly handle breaking out a loop gracefully and then all those error conditions to handle. A fate worse than rock pushing. :-)
Drew Conry-Murray
50%
50%
Drew Conry-Murray,
User Rank: Ninja
9/11/2014 | 9:26:15 AM
Sisyphus needed DevOps
Too bad Chef or Puppet weren't around in Sisyphus's day. He could've automated pushing that rock up the hill.
batye
100%
0%
batye,
User Rank: Ninja
9/10/2014 | 1:26:39 PM
interesting
interesting to know, good points and ideas... thank you...
Commentary
Why 2021 May Turn Out to be a Great Year for Tech Startups
John Edwards, Technology Journalist & Author,  2/24/2021
News
How GIS Data Can Help Fix Vaccine Distribution
Jessica Davis, Senior Editor, Enterprise Apps,  2/17/2021
Slideshows
11 Ways DevOps Is Evolving
Lisa Morgan, Freelance Writer,  2/18/2021
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you.
Slideshows
Flash Poll