Skip to content

Commit a41e633

Browse files
idmac75idmac75
committed
Updated the A's in glossary page
modified: docs/devops-basics/devops-vs-sre.md modified: docs/devops-basics/glossary.md modified: mkdocs.yml Signed-off-by: Scott McCarthy <scott.mccarthy@opencastsoftware.com>
1 parent 70d6b4b commit a41e633

3 files changed

Lines changed: 52 additions & 17 deletions

File tree

‎docs/devops-basics/devops-vs-sre.md‎

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,7 @@ _This article originated from a blog on [Harness's website](https://harness.io/b
66

77
In a nutshell, DevOps Engineers are ops-focused engineers who solve development pipeline problems. Site Reliability Engineers are development-focused engineers who solve operational/scale/reliability problems.
88

9-
<figure markdown>
109
![devops overview](../img/sre-v-devops-1.png){ width="300" }
11-
<figcaption>Image caption</figcaption>
12-
</figure>
1310

1411
Software is certainly eating the world, and as our dependence on technology increases, disciplines have arisen to ensure that changes are rolled out efficiently and our systems are there when we need them. The rise of DevOps and Site Reliability Engineering cultures and practices has risen to the mainstream over the past years.
1512

@@ -37,7 +34,7 @@ Because we are all still fighting Conway’s Law, having a solid DevOps team doe
3734

3835
## Two Different Problem Sets
3936

40-
Engineering efficiency and reliability are two separate domains, but have some overlap. There is a correlation between agility and more robust systems. A counter-argument might be made that agility brings about a fast velocity of change, and change is a detriment to reliability. Today’s challenges are faced at scale, and as we continue to push the boundaries, adjusting on-the-fly is important. The problems that both teams solve are telling to the culture and skills needed for both to thrive.
37+
Engineering efficiency and reliability are two separate domains, but have some overlap. There is a correlation between agility and more robust systems. A counter-argument might be made that agility brings about a fast velocity of change, and change is a detriment to reliability. Today’s challenges are faced at scale, and as we continue to push the boundaries, adjusting on-the-fly is important. The problems that both teams solve are telling to the culture and skills needed for both to thrive.
4138

4239
## What Problems Do DevOps Teams Solve?
4340

‎docs/devops-basics/glossary.md‎

Lines changed: 44 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,50 @@
11
---
22
title: DevOps Glossary
33
summary: A list of DevOps terms as defined by the DevOps Institute
4+
author: the DevOps Institute - https://devopsinstitute.com
45

56
---
6-
This list of DevOps terms as defined by the DevOps Institute
77

8-
| Term | Definition |
9-
|---------------------------|---------------------------------------------------------------------------------------------------------------------------|
10-
| A/B Testing | Deploy different versions of an EUT to different customers and let the customer feedback determine which is best. |
11-
| Administration Testing | The purpose of the test is to determine if an End User Test (EUT) is able to process administration tasks as expected. |
8+
This list of DevOps terms are as defined by the DevOps Institute:
9+
10+
Click on the follow bookmarks to jump - | [A](#a-terms) | [B](#b-terms) |
11+
12+
## A - Terms
13+
14+
| Term | Definition |
15+
| :------------------------ | :------------------------------------------------------------------------------------------------------------------------------------ |
16+
| A/B Testing | Deploy different versions of an EUT to different customers and let the customer feedback determine which is best. |
17+
| Administration Testing | The purpose of the test is to determine if an End User Test (EUT) is able to process administration tasks as expected. |
18+
| Agile | A project management method for complex projects that divides tasks into smal "sprints" of work with frequent reassessment and adaption of plans |
19+
| Agile Coach | Help teams master Agile development and DevOps practices; enables productive ways of working and collaboration. |
20+
| Agile Manifesto | A formal proclamation of values and principles to guide an iterative and people-centric approach to software development. |
21+
| Agile Portfolio Managment | Involves evaluating in-flight project and proposed future initiatives to shape and govern the ongoing investment in projects and discretionary work. |
22+
| Agile Principles | The tweleve principle that underpin the Agile Manifesto |
23+
| Agile Process Owner | An ITSM or other type of process own that uses Agile and Scurm principles and practices to design, manage and measure individual processes. |
24+
| Agile Service Manager | The operational equivalent to Dev's ScrumMaster. A role within an IT organisation that understand how to leverage Agile and Scurm methods to improve the design speed and agility of ITSM processes. |
25+
| Agile Software Development | Group of software development methods in which requirement and olutions evovle through collaboration between self-organzing, cross-functional teams. Usually applied using the Scrum or Scaled Agile Framework approach. |
26+
| Amazon Web Services (AWS) | AWS is a secure cloud services platform offering comupute power, database storage, content delivery and otehr functionality to help businesses scale and grow. |
27+
| Analytics | Test results processed and presented in an organised manner in accordance with analysis methods and criterion |
28+
| Andon (Cord) | A system that gives an assembly line worker the ability, and moreover the empowerment, to stop production when a defect is found and immediately call for assistance. |
29+
| Ant-pattern | A commonly reinvented bu poor solution to a problem. |
30+
| Anti-fragility | Antifragility is a property of systems that increases it capability to thrive as a result of stressors, shocks, volatility, noise, mistakes, faults, attacks, or failures. |
31+
| Application Programming Interface (API) | A set of protocols used to create applications for a specific OS or as an interface between modules or applications. |
32+
| API Testing | The purpose of the test is to determine if na API for an EUT functions as expected. |
33+
| Application Release | Controlled continuous delivery pipeline capabilities including automation (release upon code commit). |
34+
| Application Testing | The purpose of the test is to determine if an application is performing according to its requirements and expected behaviors. |
35+
| Architecture | The fundamental underlying design of computer hardware, software or both in combination. |
36+
| Artifact | Any element in a software development project inclding documentation, test plans, images, data files and executable modules. |
37+
| Artifact Repository | Store for binaries, reports and metadata. Example tools include: JFog Artifactory, Sonatype Nexus or Azure Artifacts. |
38+
| Audi Managment | The use of automated tools to ensure products and services are auditable, including keeping audit logs of build, test and deplooy activities, auditing configurations and users, as well as log files from production operations. |
39+
| Authentication | The process of verifying an asserted identity. Authentication can be based on what you know 9e.g. password or PIN), kwhat you have (token or one-time code), what you are (biometrics) or contextual information. |
40+
| Authorisation | The process of granting roles to users to have access to resources |
41+
| Auto-DevOps | Auto DevOps brings DevOps best practices to your project by automatically configuring software development lifecycles. It automatically detects, builts, test, deploys and monitors applications. |
42+
| Auto-scaling | The ability to automatically and elastically scale and de-scale infrastructure depending on traffic and capacity variations while maintaining control of costs. |
43+
| Automated Rollback | If a failure is detected during a deployment, an operator (or automated process) will verify the failure and rollback the failing release to the previous known working state. |
44+
| Availability | Availability is the proportion of time a system is in a functioning condition and therefore available (to users) to be used. |
45+
46+
## B - Terms
47+
48+
| Term | Definition |
49+
| :------------------------ | :------------------------------------------------------------------------------------------------------------------------------------ |
50+
| Backlog | |

‎mkdocs.yml‎

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
### SITE BASE CONFIG ###
1+
### --- SITE BASE CONFIG --- ###
22

33
# Default values, taken from mkdocs_theme.yml
44
site_name: Devops Docs
@@ -27,9 +27,7 @@ theme:
2727
# include_search_page: false
2828
# search_index_only: true
2929

30-
### START OF EXTENSIONS & PLUGIN SECTION ###
31-
32-
30+
### --- START OF EXTENSIONS & PLUGIN SECTION --- ###
3331

3432
# Used for glossary page and adding abbrviations
3533
markdown_extensions:
@@ -51,10 +49,12 @@ markdown_extensions:
5149
- pymdownx.tasklist:
5250
custom_checkbox: true
5351

52+
# Used to allow for customisation of tables
53+
markdown_extensions:
54+
- tables
5455

5556

56-
57-
#### START OF NAVIGATION SECTION ###
57+
### --- START OF NAVIGATION SECTION -- ###
5858

5959
nav:
6060
- Home: index.md
@@ -82,5 +82,4 @@ nav:
8282
- About: about.md
8383

8484

85-
86-
#### END OF NAVIGATION SECTION ###
85+
### END OF FILE ###

0 commit comments

Comments
 (0)