WEBVTT - This file was automatically generated by VIMEO

0
00:00:06.900 --> 00:00:09.500
In this video, we will go over common terminologies that

1
00:00:09.500 --> 00:00:11.700
 you will need to know when implementing devops.

2
00:00:12.400 --> 00:00:15.400
There is a ton of technical. Jargon that gets thrown around when talking about

3
00:00:15.400 --> 00:00:18.800
 devops. So I've chosen 10 Concepts that

4
00:00:18.800 --> 00:00:21.200
 are the most impactful for you to get up and

5
00:00:21.200 --> 00:00:21.900
 running fast.

6
00:00:23.900 --> 00:00:26.700
Configuration management is the process of configuring

7
00:00:26.700 --> 00:00:29.900
 resources like servers using code and configuration files

8
00:00:29.900 --> 00:00:32.300
 that lets you define an end

9
00:00:32.300 --> 00:00:35.700
 state of what that resource should look like configuration management

10
00:00:35.700 --> 00:00:37.400
 should be predictable and repeatable.

11
00:00:38.300 --> 00:00:41.400
Infrastructure's code is the process of using code to

12
00:00:41.400 --> 00:00:45.200
 describe and manage infrastructure such as virtual machines virtual

13
00:00:44.200 --> 00:00:47.900
 networks and Cloud resources like

14
00:00:47.900 --> 00:00:50.300
 Amazon's relational database service or

15
00:00:50.300 --> 00:00:52.300
 commonly known as RDS.

16
00:00:53.100 --> 00:00:56.200
Continuous integration allows developers to merge code on

17
00:00:56.200 --> 00:00:59.500
 a regular Cadence where it is built-in tested on every Commit

18
00:00:59.500 --> 00:01:02.200
 This is considered the build and test phase of

19
00:01:02.200 --> 00:01:03.300
 a delivery pipeline.

20
00:01:04.100 --> 00:01:07.300
Continuous delivery is a practice where all code

21
00:01:07.300 --> 00:01:09.800
 changes are automatically staged for production release.

22
00:01:10.400 --> 00:01:13.300
But are usually gated by a manual step to finish

23
00:01:13.300 --> 00:01:14.100
 the release process.

24
00:01:15.800 --> 00:01:18.600
Continuous deployment on the other hand is a practice where all

25
00:01:18.600 --> 00:01:21.200
 the code changes are automatically deployed to a production

26
00:01:21.200 --> 00:01:23.700
 environment without any user intervention.

27
00:01:25.600 --> 00:01:28.300
Continuous monitoring is a process that collects

28
00:01:28.300 --> 00:01:32.300
 information and data points about your system monitoring provides

29
00:01:31.300 --> 00:01:34.400
 continuous feedback about the

30
00:01:34.400 --> 00:01:37.500
 performance and applications in your infrastructure throughout

31
00:01:37.500 --> 00:01:38.500
 their life cycles.

32
00:01:39.200 --> 00:01:43.000
Meantime to recovery or mttr is

33
00:01:42.200 --> 00:01:45.300
 the average time. It takes for an application or

34
00:01:45.300 --> 00:01:47.000
 system to recover from a failure.

35
00:01:47.700 --> 00:01:50.700
Item potent means executing a command or process

36
00:01:50.700 --> 00:01:54.000
 and getting the same results. Every time this

37
00:01:53.400 --> 00:01:56.600
 concept is found in infrastructure's code

38
00:01:56.600 --> 00:01:58.600
 and configuration management software.

39
00:01:59.500 --> 00:02:02.400
Imperative describes the exact steps needed to

40
00:02:02.400 --> 00:02:05.400
 reach an end state for a system. The user is

41
00:02:05.400 --> 00:02:08.200
 expected to understand each step and how they differ.

42
00:02:09.300 --> 00:02:12.800
Declarative, which is kind of the opposite of imperative is

43
00:02:12.800 --> 00:02:15.600
 when the state of a system is defined as the end goal

44
00:02:15.600 --> 00:02:18.500
 not the exact steps to achieve that state.

45
00:02:18.500 --> 00:02:21.700
 The user is not expected to understand the exact

46
00:02:21.700 --> 00:02:23.000
 commands or any differences.

47
00:02:24.800 --> 00:02:27.400
Okay, let's do a quick recap in this

48
00:02:27.400 --> 00:02:30.400
 video. You learned about 10 devops terminologies that

49
00:02:30.400 --> 00:02:33.700
 are commonly used as a devops engineer or

50
00:02:33.700 --> 00:02:36.400
 someone who contributes to the overall system. You will

51
00:02:36.400 --> 00:02:38.600
 need to be familiar with these terms and more.

52
00:02:39.300 --> 00:02:41.500
But if you had to only remember three of them.

53
00:02:42.700 --> 00:02:45.000
These are the three that you will encounter the most.

54
00:02:45.900 --> 00:02:48.800
Cicd or continuous integration

55
00:02:48.800 --> 00:02:51.100
 continuous delivery or deployment.

56
00:02:51.900 --> 00:02:54.600
Is your main Pipeline and mechanism that that enables

57
00:02:54.600 --> 00:02:56.700
 code to flow from planning to deployment?

58
00:02:57.500 --> 00:03:00.600
Infrastructure's code and configuration management have been

59
00:03:00.600 --> 00:03:03.600
 Staples for devops engineers. But now

60
00:03:03.600 --> 00:03:06.900
 that most workloads run in the cloud. They are

61
00:03:06.900 --> 00:03:08.400
 a must know for any engineer.

62
00:03:09.100 --> 00:03:12.100
Continuous monitoring is not an afterthought any longer.

63
00:03:12.800 --> 00:03:15.300
It is a part of a production release and is a

64
00:03:15.300 --> 00:03:17.200
 required piece for a tight feedback loop.

65
00:03:18.600 --> 00:03:22.200
In the next video, we will expand on cicd in

66
00:03:21.200 --> 00:03:24.100
 software development lifecycle Pipelines.
