Jump to content

DevOps: Difference between revisions

Page protected with pending changes
From Wikipedia, the free encyclopedia
Browse history interactively
[accepted revision][accepted revision]
← Previous editNext edit →
Content deleted Content added
VisualWikitext
No edit summary
→About: Spelling
Line 65: Line 65:


[[File:Devops.svg|thumb|widthpx|Illustration showing DevOps as the intersection of development (software engineering), technology operations and quality assurance (QA)]]
[[File:Devops.svg|thumb|widthpx|Illustration showing DevOps as the intersection of development (software engineering), technology operations and quality assurance (QA)]]
Development methodologies (such as [[agile software development]]) that are adopted in a traditional organization with separate departments for Dev, IT operations and [[Quality Assurance|QA]], development and [[Software deployment |deployment]] activities, previously do not have deep cross-departmental integration with IT support or QA. DevOps promotes a set of processes and methods for thinking about [[communication]] and collaboration between departments.<ref>{{Cite web | url = http://www.kartar.net/2010/02/what-devops-means-to-me/ | title = What DevOps means to me... | first = James | last = Turnbull | publisher = Kartar |date=Feb 2010}}</ref>
Development methodologies (such as [[agile software development]]) that are adopted in a traditional organization with separate departments for Development, IT Operations and [[Quality Assurance|QA]], development and [[Software deployment |deployment]] activities, previously do not have deep cross-departmental integration with IT support or QA. DevOps promotes a set of processes and methods for thinking about [[communication]] and collaboration between departments.<ref>{{Cite web | url = http://www.kartar.net/2010/02/what-devops-means-to-me/ | title = What DevOps means to me... | first = James | last = Turnbull | publisher = Kartar |date=Feb 2010}}</ref>


The adoption of DevOps is being driven by factors such as:
The adoption of DevOps is being driven by factors such as:

Revision as of 21:17, 25 September 2014

DevOps (a portmanteau of "development" and "operations") is a concept dealing, among other things with software development, operations and services. It emphasizes communication, collaboration and integration between software developers and information technology (IT) operations personnel.[1][2] DevOps is a response to the interdependence of software development and IT operations. It aims to help an organization rapidly produce software products and services.[3][4][5][6][7]

Simple processes become clearly articulated using a DevOps approach,[citation needed] which aims to maximize the predictability, efficiency, security and maintainability of operational processes. Very often, automation supports this objective.

DevOps integration targets product delivery, quality testing, feature development and maintenance releases in order to improve reliability and security and faster development and deployment cycles. Many of the ideas (and people) involved in DevOps came from the Enterprise Systems Management and Agile software development movements.[8]

DevOps aids in software application release management for an organization by standardizing development environments. Events can be more easily tracked as well as resolving documented process control and granular reporting issues. Companies with release/deployment automation problems usually have existing automation but want to more flexibly manage and drive this automation — without needing to enter everything manually at the command-line. Ideally, this automation can be invoked by non-operations employees in specific non-production environments. The DevOps approach grants developers more control of the environment, giving infrastructure more application-centric understanding.

Companies with very frequent releases may require a DevOps awareness or orientation program. Flickr developed a DevOps approach to support a business requirement of ten deployments per day;[9] this daily deployment cycle would be much higher at organizations producing multi-focus or multi-function applications. This is referred to as continuous deployment[10] or continuous delivery [11] and is frequently associated[by whom?] with the lean startup methodology.[12] Working groups, professional associations and blogs have formed on the topic since 2009.[6][13][14]

About

The term "DevOps" was popularized through a series of "DevOps Days" starting in 2009 in Belgium.[15] Since then, there have been DevOps Days conferences held in India, the US, Brazil, Australia, Germany, and Sweden.[16]

Illustration showing DevOps as the intersection of development (software engineering), technology operations and quality assurance (QA)

Development methodologies (such as agile software development) that are adopted in a traditional organization with separate departments for Development, IT Operations and QA, development and deployment activities, previously do not have deep cross-departmental integration with IT support or QA. DevOps promotes a set of processes and methods for thinking about communication and collaboration between departments.[17]

The adoption of DevOps is being driven by factors such as:

  1. Use of agile and other development processes and methodologies
  2. Demand for an increased rate of production releases from application and business unit stakeholders
  3. Wide availability of virtualized[18] and cloud infrastructure from internal and external providers
  4. Increased usage of data center automation[19] and configuration management tools

References

  1. ^ Pant, Rajiv (2009-03-17). "Organizing a Digital Technology Department of Medium Size in a Media Company".
  2. ^ Loukides, Mike (2012-06-07). "What is DevOps?".
  3. ^ Samovskiy, Dmitriy (2010-03-02). "The Rise of DevOps". Fubaredness Is Contagious.
  4. ^ Edwards, Damon. "What is DevOps?".
  5. ^ Vambenepe, William. "Steve Ballmer gets Cloud".
  6. ^ a b Lyman, Jay. "DevOps mixing dev, ops, agile, cloud, open source and business". 451 CAOS Theory.
  7. ^ Debois, Patrick. "Devops: A Software Revolution in the Making?". Cutter IT Journal.
  8. ^ Nasrat, Paul. "Agile Infrastructure". InfoQ. Retrieved 31 March 2011.
  9. ^ "10+ Deploys Per Day: Dev and Ops Cooperation at Flickr".
  10. ^ "SAM SIG: Applied Lean Startup Ideas: Continuous Deployment at kaChing". SVForum.
  11. ^ Humble, Jez. "Why Enterprises Must Adopt Devops to Enable Continuous Delivery". Cutter IT Journal.
  12. ^ "Applied Lean Startup Ideas: Continuous Deployment at kaChing".
  13. ^ "DevOps Days 2009 Conference".
  14. ^ Edwards, Damon. "DevOps Meetup Recap".
  15. ^ Debois, Patrick (2009). "DevOps Days Ghent". DevopsDays. Retrieved 31 March 2011.
  16. ^ Debois, Patrick. "DevOps Days". DevOps Days. Retrieved 31 March 2011.
  17. ^ Turnbull, James (Feb 2010). "What DevOps means to me..." Kartar.
  18. ^ "Virtual Infrastructure products: features comparison". Welcome to IT 2.0: Next Generation IT infrastructures.
  19. ^ Ellard, Jennifer. "Bringing Order to Chaos through Data Center Automation". Information Management. SourceMedia.

Further reading

Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=DevOps&oldid=627078491"