Difference between revisions of "DevOps"

From CNM Wiki
Jump to: navigation, search
(→‎Definitions)
(→‎See also)
 
(2 intermediate revisions by the same user not shown)
Line 4: Line 4:
  
 
Functions of ''DevOps'' can be compared with those of [[project management office]] ([[project management office|PMO]]) in a traditional [[project management]] framework. ''DevOps'' can be considered as an application of [[continuous delivery]].
 
Functions of ''DevOps'' can be compared with those of [[project management office]] ([[project management office|PMO]]) in a traditional [[project management]] framework. ''DevOps'' can be considered as an application of [[continuous delivery]].
 +
 +
A group of ''DevOps'' concepts had been existing for a while before the ''DevOps'' term emerged. Recently, those concepts have catalyzed into a movement and are rapidly spreading throughout the technical community.
  
  
 
==Definitions==
 
==Definitions==
−
According to [[Educaship Alliance LLC]],
 
−
:[[DevOps]]. A term for a group of concepts that, while not all new, have catalyzed into a movement and are rapidly spreading throughout the technical community. Is a new term emerging from the collision of two major related trends.
 
−
 
 
According to the [[ITIL Foundation 4e by Axelos]],
 
According to the [[ITIL Foundation 4e by Axelos]],
 
:[[DevOps]]. An organizational culture that aims to improve the flow of value to customers. DevOps focuses on culture, automation, Lean, measurement, and sharing (CALMS).
 
:[[DevOps]]. An organizational culture that aims to improve the flow of value to customers. DevOps focuses on culture, automation, Lean, measurement, and sharing (CALMS).
−
 
−
[[Category: Information Technology]]
 
−
According to the [[ITIL Foundation 4e by Axelos]],
 
−
:[[Effectiveness]]. A measure of whether the objectives of a practice, service or activity have been achieved.
 
−
 
−
[[Category: Information Technology]]
 
−
According to the [[ITIL Foundation 4e by Axelos]],
 
−
:[[Efficiency]]. A measure of whether the right amount of resources have been used by a practice, service, or activity.
 
−
 
−
[[Category: Information Technology]]
 
−
According to the [[ITIL Foundation 4e by Axelos]],
 
−
:[[Environment]]. A subset of the IT infrastructure that is used for a particular purpose, for example a live environment or test environment. Can also mean the external conditions that influence or affect something.
 
−
 
−
[[Category: Information Technology]]
 
−
According to the [[ITIL Foundation 4e by Axelos]],
 
−
:[[Event]]. Any change of state that has significance for the management of a service or other configuration item.
 
−
 
−
[[Category: Information Technology]]
 
−
According to the [[ITIL Foundation 4e by Axelos]],
 
−
:[[Failure]]. A loss of ability to operate to specification, or to deliver the required output or outcome.
 
−
 
−
[[Category: Information Technology]]
 
−
According to the [[ITIL Foundation 4e by Axelos]],
 
−
:[[Governance]]. The means by which an organization is directed and controlled.
 
−
 
−
[[Category: Information Technology]]
 
−
According to the [[ITIL Foundation 4e by Axelos]],
 
−
:[[Incident]]. An unplanned interruption to a service or reduction in the quality of a service.
 
−
 
−
[[Category: Information Technology]]
 
−
According to the [[ITIL Foundation 4e by Axelos]],
 
−
:[[Integrity]]. A security objective that ensures information is only modified by authorized personnel and activities.
 
−
 
−
[[Category: Information Technology]]
 
−
According to the [[ITIL Foundation 4e by Axelos]],
 
−
:[[Internet of Things]]. The interconnection of devices via the internet that were not traditionally thought of as IT assets, but now include embedded computing capability and network connectivity.
 
−
 
−
[[Category: Information Technology]]
 
−
According to the [[ITIL Foundation 4e by Axelos]],
 
−
:[[Kanban]]. A method for visualizing work, identifying potential blockages and resource conflicts, and managing work in progress.
 
−
 
−
[[Category: Information Technology]]
 
−
According to the [[ITIL Foundation 4e by Axelos]],
 
−
:[[Lean]]. An approach that focuses on improving workflows by maximizing value through the elimination of waste.
 
−
 
−
[[Category: Information Technology]]
 
  
 
==Inspiring quotes==
 
==Inspiring quotes==
Line 66: Line 19:
  
 
==See also==
 
==See also==
 +
*https://www.atlassian.com/devops/devops-tools
  
 
===Related lectures===
 
===Related lectures===
Line 71: Line 25:
 
:*[[What the DevOps Is]].  
 
:*[[What the DevOps Is]].  
  
−
[[Category: Septem Artes Administrativi]][[Category: CNM Cyber Orientation]][[Category: Articles]]
+
[[Category: Septem Artes Administrativi]][[Category: CNM Cyber Orientation]][[Category: Articles]][[Category: Information Technology]]

Latest revision as of 17:54, 5 May 2021

DevOps process

DevOps is an engineering practice and a set of concepts based on that practice that aim at unifying new product development (the Dev part) and operations (the Ops part). The primary feature of DevOps is to strongly advocate automation and monitoring at all steps of the project such as integration, testing, releasing to deployment, and infrastructure management.

DevOps aims at shorter development cycles, increased deployment frequency, more dependable releases, in close alignment with business objectives. DevOps processes refer to a sequence of phases of DevOps; DevOps toolchains refer to a set of tools used in that process.

Functions of DevOps can be compared with those of project management office (PMO) in a traditional project management framework. DevOps can be considered as an application of continuous delivery.

A group of DevOps concepts had been existing for a while before the DevOps term emerged. Recently, those concepts have catalyzed into a movement and are rapidly spreading throughout the technical community.


Definitions

According to the ITIL Foundation 4e by Axelos,

DevOps. An organizational culture that aims to improve the flow of value to customers. DevOps focuses on culture, automation, Lean, measurement, and sharing (CALMS).

Inspiring quotes

  • Simply put, things always had to be in a production-ready state: if you wrote it, you darn well had to be there to get it running!. --Mike Miller
  • The most powerful tool we have as developers is automation. --Scott Hansellman
  • The key in such a transition to continuous delivery is to expect things to get worse before you’ll be able to make them better. --Mattias Marschall
  • Currently, DevOps is more like a philosophical movement, not yet a precise collection of practices, descriptive or prescriptive. --Gene Kim

See also

Related lectures

Retrieved from "https://pravka.bskol.com/w/index.php?title=DevOps&oldid=71021"