1
00:00:00,000 --> 00:00:10,320
In this video, we'll identify the main configuration management solutions.

2
00:00:10,320 --> 00:00:13,840
There's a couple of solutions on the market.

3
00:00:13,840 --> 00:00:16,240
First and foremost, there is Ansible.

4
00:00:16,240 --> 00:00:18,959
Ansible is currently the most used tool.

5
00:00:18,959 --> 00:00:24,120
It does not need an agent, because it uses SSH for contact, and it is push-based.

6
00:00:24,120 --> 00:00:29,680
The configuration is defined in YAML, which is easy to understand.

7
00:00:29,680 --> 00:00:35,000
Also very common is Puppet, but it was mainly big in the past, before Ansible became so

8
00:00:35,000 --> 00:00:36,000
popular.

9
00:00:36,000 --> 00:00:41,680
Puppet needs an agent, that's a piece of software that you install on your managed assets.

10
00:00:41,680 --> 00:00:45,759
And it is pool-based, and that means that the agent is going to fetch the configuration

11
00:00:45,759 --> 00:00:50,759
itself to ensure that the managed machine is in the desired state.

12
00:00:50,759 --> 00:00:55,439
It uses a relatively complex configuration language.

13
00:00:55,439 --> 00:01:00,720
A somewhat smaller solution is Chef, which also needs an agent and is pool-based.

14
00:01:00,720 --> 00:01:05,360
It uses a relatively complex configuration language like Puppet, but has never been one

15
00:01:05,360 --> 00:01:07,639
of the big solutions.

16
00:01:07,639 --> 00:01:12,959
Likewise for SaltStack, which is used in the SUSE Manager management solution.

17
00:01:12,959 --> 00:01:18,680
It needs an agent, it is pool-based, and the configuration is in YAML.

18
00:01:18,680 --> 00:01:23,080
Mainly because Ansible is so simple and it doesn't need an agent, but works over default

19
00:01:23,080 --> 00:01:27,199
remote control like Secure Shell, it has become so popular.

20
00:01:27,199 --> 00:01:29,800
And that's also because the configuration is all in YAML.