1 00:00:00,540 --> 00:00:08,100 In our next section we will talk about the configuration management mechanisms the tools and processes 2 00:00:08,130 --> 00:00:15,790 network engineers have used to manage networks have not really changed in the last twenty five years. 3 00:00:15,900 --> 00:00:23,970 For example using tools like putty or secure CRT and network engineer will connect to a device using 4 00:00:24,060 --> 00:00:30,030 SSA age and perform some configuration change or check at device status. 5 00:00:30,540 --> 00:00:38,940 However with the scale of networks today it is no longer practical to make these changes on the device 6 00:00:38,940 --> 00:00:40,950 by device basis. 7 00:00:41,040 --> 00:00:44,940 Network automation is fast becoming a. 8 00:00:44,940 --> 00:00:52,980 Network Engineers ought to muster as a result of using developer's tools for many years. 9 00:00:53,100 --> 00:01:02,010 Network engineers are seeing the benefit of these tools for performing network administration and configuration 10 00:01:02,100 --> 00:01:03,360 tasks. 11 00:01:03,360 --> 00:01:14,920 Now we are going to reveal the top three network automation tools used in today and their puppet chef 12 00:01:15,310 --> 00:01:24,790 and the NSL Puppet Chef and assemble are three different tools that represent different paths to achieve 13 00:01:24,850 --> 00:01:35,260 a common goal of managing a large scale infrastructure efficiently with minimal input from the developers 14 00:01:35,290 --> 00:01:39,340 and system and network administrators. 15 00:01:39,340 --> 00:01:47,620 All three configuration management tools are designed to reduce the complexity of configuring distributed 16 00:01:47,680 --> 00:01:56,740 infrastructure resources enabling speed and ensuring reliability and compliance. 17 00:01:57,130 --> 00:02:05,440 Okay let's start with the symbol and symbol deserves its place at the top of the list of network automation 18 00:02:05,440 --> 00:02:14,920 tools in use today and Siebel is written in Python and was previously developed to automate the management 19 00:02:14,950 --> 00:02:22,680 of Linux servers but is now capable of automating most of network tasks. 20 00:02:22,690 --> 00:02:29,320 This software remains open source and as such is free to use. 21 00:02:29,410 --> 00:02:37,690 There is also a strong community providing good support for sensible guys for corporate users who require 22 00:02:37,710 --> 00:02:40,480 a more formal support module. 23 00:02:40,480 --> 00:02:49,630 There is an single engine which is a fully supported version of animal both products are driven from 24 00:02:49,660 --> 00:02:52,270 the command line interface. 25 00:02:52,270 --> 00:02:55,090 Finally there is an Sibal tower. 26 00:02:55,180 --> 00:03:03,580 The companies G you ie management to a license product based on the number of devices being managed 27 00:03:04,630 --> 00:03:13,570 and simple uses the concept of app playbook which in which you define a list of tasks consisting of 28 00:03:13,680 --> 00:03:23,200 as small items of configuration such as the creations of freelance or defining the interfaces and etc.. 29 00:03:23,560 --> 00:03:33,340 The playbook file is written in Yama which is very human readable and also uses ginger too for writing 30 00:03:33,370 --> 00:03:42,910 templates and symbol works on AB push methodology you define what you want to do and push it to the 31 00:03:43,030 --> 00:03:44,580 nuts and that's it. 32 00:03:45,220 --> 00:03:55,500 And Sibal will confirm if changes actually need to be made by verifying if the code is in place already. 33 00:03:55,540 --> 00:03:58,810 If so it will skip that task. 34 00:03:58,810 --> 00:04:07,810 This is referred to as IDM then potency only making change so when they are actually required. 35 00:04:08,560 --> 00:04:16,500 If the playbook that our minds at change does not need to be made it will skip that task. 36 00:04:16,510 --> 00:04:25,090 The main reason and symbol is such a great tool for network automation is that it is Agent plus meaning 37 00:04:25,120 --> 00:04:36,100 that to manage any network device you only require SSA access that this is its main advantage over tools. 38 00:04:36,100 --> 00:04:45,720 We will look at that on our next slides like puppet or chaff which require an agent to be installed. 39 00:04:45,730 --> 00:04:57,180 This is very easy on our Linux server but not as simple as on network devices let's go ahead with Jeff. 40 00:04:57,750 --> 00:05:06,650 Jeff is another popular too for network automation guys and add the set up is a little more involved 41 00:05:06,700 --> 00:05:09,650 than and symbol for one. 42 00:05:09,650 --> 00:05:19,240 There is a master server and agents are installed on managed not at Jeff installation also needs a workstation 43 00:05:19,250 --> 00:05:21,260 to control the master. 44 00:05:21,260 --> 00:05:29,570 Once an agent has been installed on the managed device the notes authenticate the to the master with 45 00:05:29,570 --> 00:05:32,300 the use of certificates. 46 00:05:32,900 --> 00:05:36,590 Additionally chef is written in Ruby. 47 00:05:36,620 --> 00:05:46,110 So you should ideally also come with basic knowledge of Ruby as the name suggests the chef utilizes 48 00:05:46,130 --> 00:05:51,870 a cooking them and receipts instead of tasks. 49 00:05:51,950 --> 00:06:01,550 However to use chaff for network automation you still need to get an agent on to your target device. 50 00:06:01,670 --> 00:06:09,680 Puppet is another open source automation tool that was initially used for managing Linux servers but 51 00:06:09,680 --> 00:06:15,470 is also gaining popularity in the network automation world. 52 00:06:15,470 --> 00:06:22,160 As with chef a it requires an agent to be installed on the target device. 53 00:06:22,400 --> 00:06:30,590 Puppet uses its own configuration language which is completely appropriate or a team making puppet more 54 00:06:30,590 --> 00:06:39,860 complex to learn than any symbol or chef puppet devices periodically pooled their comfort configuration 55 00:06:39,860 --> 00:06:42,740 from the puppet master server. 56 00:06:42,740 --> 00:06:49,640 This differs from and symbol in which it is purely push model. 57 00:06:49,710 --> 00:06:57,330 You can define a standard build and ensure the target device devices maintained that build by checking 58 00:06:57,360 --> 00:07:00,540 in to deal with the puppet master server.