1 00:00:00,180 --> 00:00:02,009 In this lesson we're going to discuss 2 00:00:02,009 --> 00:00:05,370 how orchestration processes and concepts can be used 3 00:00:05,370 --> 00:00:08,940 to do work more effectively than using simple automation. 4 00:00:08,940 --> 00:00:12,150 So at this point, you're able to do some simple automation 5 00:00:12,150 --> 00:00:15,030 on a small scale, using some basic scripts, 6 00:00:15,030 --> 00:00:18,240 using the at service or the cron service. 7 00:00:18,240 --> 00:00:21,630 But automation alone is not enough to manage the deployment 8 00:00:21,630 --> 00:00:24,390 and maintenance of hundreds or thousands of systems 9 00:00:24,390 --> 00:00:26,370 in large corporate infrastructures 10 00:00:26,370 --> 00:00:30,000 that you may work for as a system administrator one day. 11 00:00:30,000 --> 00:00:31,500 Now, orchestration is known 12 00:00:31,500 --> 00:00:34,020 as the automated configuration management 13 00:00:34,020 --> 00:00:37,020 and coordination of computer systems, applications 14 00:00:37,020 --> 00:00:38,280 and services. 15 00:00:38,280 --> 00:00:41,340 Orchestration helps IT and system administrators 16 00:00:41,340 --> 00:00:44,670 to more easily manage complex tasks and workflows. 17 00:00:44,670 --> 00:00:47,580 Our information technology teams have to manage a lot 18 00:00:47,580 --> 00:00:50,430 of servers and applications every single day 19 00:00:50,430 --> 00:00:54,270 but doing all of that manually just is not scalable at all. 20 00:00:54,270 --> 00:00:57,540 The more complex an IT system becomes, the more complex 21 00:00:57,540 --> 00:01:00,300 managing all the moving parts is going to be. 22 00:01:00,300 --> 00:01:02,520 The need to combine multiple automated tasks 23 00:01:02,520 --> 00:01:05,250 and their configurations across large groups of systems 24 00:01:05,250 --> 00:01:07,620 or machines is going to increase very quickly 25 00:01:07,620 --> 00:01:09,270 in large organizations. 26 00:01:09,270 --> 00:01:12,030 And that's where orchestration can really help us. 27 00:01:12,030 --> 00:01:14,940 So in this lesson, we're going to discuss how 28 00:01:14,940 --> 00:01:17,970 orchestration does the work much more efficiently 29 00:01:17,970 --> 00:01:19,920 than just using automation. 30 00:01:19,920 --> 00:01:21,930 Now, when I talk about automation, 31 00:01:21,930 --> 00:01:25,110 this is the process of accomplishing a configuration task 32 00:01:25,110 --> 00:01:26,910 without human intervention. 33 00:01:26,910 --> 00:01:29,460 This is different than orchestration though. 34 00:01:29,460 --> 00:01:32,130 Automation refers to a single task. 35 00:01:32,130 --> 00:01:35,310 Orchestration refers to managing a larger scale 36 00:01:35,310 --> 00:01:36,810 of series of tasks. 37 00:01:36,810 --> 00:01:39,780 So instead of a single task, we have lots of tasks. 38 00:01:39,780 --> 00:01:43,050 For example, one system administrator might automate 39 00:01:43,050 --> 00:01:44,850 the installation of the Python package 40 00:01:44,850 --> 00:01:46,290 in a Linux deployment. 41 00:01:46,290 --> 00:01:49,170 While another administrator might orchestrate the setup 42 00:01:49,170 --> 00:01:51,300 of a combined web and database server 43 00:01:51,300 --> 00:01:53,160 with all the necessary configurations 44 00:01:53,160 --> 00:01:55,410 on a brand new Linux server. 45 00:01:55,410 --> 00:01:57,360 Orchestration can be thought of as a series 46 00:01:57,360 --> 00:02:00,270 of automation tasks to accomplish a large skilled deployment 47 00:02:00,270 --> 00:02:02,370 of applications, virtual machines 48 00:02:02,370 --> 00:02:05,160 or entire interrelated infrastructures. 49 00:02:05,160 --> 00:02:08,550 Both terms automation and orchestration do imply 50 00:02:08,550 --> 00:02:11,310 that things are happening without your direct intervention 51 00:02:11,310 --> 00:02:14,340 but the way you get those results and the amount of things 52 00:02:14,340 --> 00:02:16,200 that are going to happen are really different 53 00:02:16,200 --> 00:02:19,620 between these two processes, including the tools you use. 54 00:02:19,620 --> 00:02:21,330 Now, when you take a process 55 00:02:21,330 --> 00:02:23,880 you have to first break it down into its component parts. 56 00:02:23,880 --> 00:02:26,520 You need to understand what that workflow looks like. 57 00:02:26,520 --> 00:02:28,350 So if I start at the green dot and I want to get 58 00:02:28,350 --> 00:02:31,170 to the red dot, what things do I do to get there? 59 00:02:31,170 --> 00:02:33,720 What are those, if, and then, and L statements 60 00:02:33,720 --> 00:02:35,670 what are the different actions that go through? 61 00:02:35,670 --> 00:02:36,810 Let's take an example. 62 00:02:36,810 --> 00:02:38,550 Let's say you wanted to orchestrate adding a 63 00:02:38,550 --> 00:02:41,310 new virtual machine to a load balance cluster. 64 00:02:41,310 --> 00:02:44,040 Now this process might include lots of different things. 65 00:02:44,040 --> 00:02:45,660 You're going to have to provision the VM. 66 00:02:45,660 --> 00:02:47,070 You have to configure the VM. 67 00:02:47,070 --> 00:02:48,900 You have to add it to the load balance cluster 68 00:02:48,900 --> 00:02:51,000 and you need to configure that load balance cluster 69 00:02:51,000 --> 00:02:52,920 weight distribution, to consider the fact 70 00:02:52,920 --> 00:02:54,420 that you added this new virtual machine 71 00:02:54,420 --> 00:02:55,950 as part of that cluster. 72 00:02:55,950 --> 00:02:59,417 When you do all these things there might be 4, 5, 10, 73 00:02:59,417 --> 00:03:01,920 15, 20 steps maybe a hundred steps, 74 00:03:01,920 --> 00:03:04,110 but you can do all of this through orchestration 75 00:03:04,110 --> 00:03:05,700 and then you can automate it. 76 00:03:05,700 --> 00:03:06,900 So you can run those things 77 00:03:06,900 --> 00:03:09,540 without having to do each of those steps yourself. 78 00:03:09,540 --> 00:03:11,190 Now, when you talk about orchestration, 79 00:03:11,190 --> 00:03:12,840 I want you to think about it this way. 80 00:03:12,840 --> 00:03:16,380 Orchestration is the automation of automations. 81 00:03:16,380 --> 00:03:17,850 Now, what does that mean? 82 00:03:17,850 --> 00:03:19,740 Well each of those blocks in that flow chart 83 00:03:19,740 --> 00:03:22,350 I just showed you, could be its own step. 84 00:03:22,350 --> 00:03:26,490 And that step may be one action, or it could be 50 actions. 85 00:03:26,490 --> 00:03:29,190 For instance, I have a flow chart and a path 86 00:03:29,190 --> 00:03:31,260 that talks about when you buy a course, 87 00:03:31,260 --> 00:03:33,690 everything that happens from the time you buy the course, 88 00:03:33,690 --> 00:03:35,340 to the time you start taking the course. 89 00:03:35,340 --> 00:03:37,140 And there's a lot of things that happen 90 00:03:37,140 --> 00:03:38,880 because we have to create an account for you, 91 00:03:38,880 --> 00:03:40,260 we have to reset your password, 92 00:03:40,260 --> 00:03:42,060 we need to add the course to your account. 93 00:03:42,060 --> 00:03:43,590 There's all these different steps. 94 00:03:43,590 --> 00:03:45,900 And so each of those, isn't just one step either. 95 00:03:45,900 --> 00:03:48,480 Some of those have multiple actions inside of it. 96 00:03:48,480 --> 00:03:49,830 For instance, when you buy the course, 97 00:03:49,830 --> 00:03:51,240 we have to send your receipt. 98 00:03:51,240 --> 00:03:53,760 We have to log that inside of our purchase system, 99 00:03:53,760 --> 00:03:55,470 we have to make sure we account it for the taxes 100 00:03:55,470 --> 00:03:56,610 that we have to pay on that, 101 00:03:56,610 --> 00:03:58,276 we have to account for the fact that we need 102 00:03:58,276 --> 00:03:59,109 to create an account for that 103 00:03:59,109 --> 00:04:00,030 and all those different things. 104 00:04:00,030 --> 00:04:03,480 And so if we can think logically about what is the sequence, 105 00:04:03,480 --> 00:04:05,310 then we can automate that sequence. 106 00:04:05,310 --> 00:04:06,990 And then if we take lots of different sequences 107 00:04:06,990 --> 00:04:09,300 and put 'em all together in one big automation 108 00:04:09,300 --> 00:04:11,430 that is the orchestration piece. 109 00:04:11,430 --> 00:04:13,470 Now, when we talk about cloud computing, 110 00:04:13,470 --> 00:04:15,360 one of the biggest benefits in cloud computing, 111 00:04:15,360 --> 00:04:17,040 is rapid elasticity. 112 00:04:17,040 --> 00:04:18,930 When you go to my website, if there's one person 113 00:04:18,930 --> 00:04:21,450 going to my website, we have one cloud server up. 114 00:04:21,450 --> 00:04:23,850 If we have 10 people, we might have two cloud servers up. 115 00:04:23,850 --> 00:04:24,990 If we have a hundred people, 116 00:04:24,990 --> 00:04:27,060 we might have five cloud servers up. 117 00:04:27,060 --> 00:04:29,400 If we have a hundred thousand people, we might have 118 00:04:29,400 --> 00:04:31,860 I don't know, a thousand or 2000 servers up. 119 00:04:31,860 --> 00:04:34,050 And what happens is this rapid elasticity, 120 00:04:34,050 --> 00:04:35,640 it does this all on its own. 121 00:04:35,640 --> 00:04:38,640 It rapidly adds new servers, adds the configurations, 122 00:04:38,640 --> 00:04:40,230 configures them, copies the data 123 00:04:40,230 --> 00:04:42,480 and then puts them into the cloud as well as 124 00:04:42,480 --> 00:04:44,400 part of our load balance cluster. 125 00:04:44,400 --> 00:04:47,700 All of that happens with automation and this all happens 126 00:04:47,700 --> 00:04:49,890 because of the orchestration we've created. 127 00:04:49,890 --> 00:04:51,870 Now, when you start talking about orchestration 128 00:04:51,870 --> 00:04:54,330 there's really three types of orchestration. 129 00:04:54,330 --> 00:04:56,730 The first one is resource orchestration. 130 00:04:56,730 --> 00:04:59,040 This is to provision and allocate resources 131 00:04:59,040 --> 00:05:01,470 within a cloud environment or other solution. 132 00:05:01,470 --> 00:05:03,630 When you talk about workload orchestration, 133 00:05:03,630 --> 00:05:05,430 this is for the management of applications 134 00:05:05,430 --> 00:05:08,070 and other cloud workloads that need to be performed. 135 00:05:08,070 --> 00:05:09,960 And basically looking at the components to create 136 00:05:09,960 --> 00:05:11,580 the product you need. 137 00:05:11,580 --> 00:05:13,230 The third one that we have is what's known 138 00:05:13,230 --> 00:05:14,790 as service orchestration. 139 00:05:14,790 --> 00:05:16,800 This is going to be used to deploy services 140 00:05:16,800 --> 00:05:18,270 into cloud environments. 141 00:05:18,270 --> 00:05:19,830 Notice the differences here. 142 00:05:19,830 --> 00:05:23,310 Resources, is like an ec2 instance in Amazon. 143 00:05:23,310 --> 00:05:25,920 You're going to start up a new server, new VM. 144 00:05:25,920 --> 00:05:27,900 If you're dealing with workload orchestration, 145 00:05:27,900 --> 00:05:29,130 this is about managing apps 146 00:05:29,130 --> 00:05:30,840 and other things that are working together. 147 00:05:30,840 --> 00:05:32,760 And then we talk about service orchestration. 148 00:05:32,760 --> 00:05:35,490 This is working on those services themselves. 149 00:05:35,490 --> 00:05:37,710 Now, when it comes to orchestration, I want you to remember, 150 00:05:37,710 --> 00:05:40,110 you don't have to be locked into one vendor. 151 00:05:40,110 --> 00:05:42,390 Everything you do, doesn't have to sit there on Amazon 152 00:05:42,390 --> 00:05:44,580 or on Azure or on Google cloud. 153 00:05:44,580 --> 00:05:47,490 You can pick 1, 2, 3, or multiple. 154 00:05:47,490 --> 00:05:49,170 It really depends on you. 155 00:05:49,170 --> 00:05:51,750 And if you do this, there is some platforms out there 156 00:05:51,750 --> 00:05:54,570 that are known as third party orchestration platforms. 157 00:05:54,570 --> 00:05:56,760 These allow you to work on your product 158 00:05:56,760 --> 00:05:58,980 and your orchestration across multiple vendors 159 00:05:58,980 --> 00:06:01,830 and allows you to prevent this vendor lock in. 160 00:06:01,830 --> 00:06:03,360 Now, as we talk about orchestration 161 00:06:03,360 --> 00:06:06,150 there is a handful of tools that you need to be aware of. 162 00:06:06,150 --> 00:06:08,730 Now, for the exam, the tools I'm going to mention 163 00:06:08,730 --> 00:06:11,280 in this lesson, you don't have to memorize them all. 164 00:06:11,280 --> 00:06:13,590 You should just be able to associate what the tool is 165 00:06:13,590 --> 00:06:15,060 and basically what it does 166 00:06:15,060 --> 00:06:16,980 but nobody's asking you to actually know how to use 167 00:06:16,980 --> 00:06:19,380 these tools, at least not for this exam. 168 00:06:19,380 --> 00:06:20,790 So let's talk about some of these. 169 00:06:20,790 --> 00:06:23,370 The first one we have is what's known as Chef. 170 00:06:23,370 --> 00:06:26,580 Now, Chef is a way to automate configuration deployments 171 00:06:26,580 --> 00:06:28,230 and the management of applications 172 00:06:28,230 --> 00:06:30,360 and it does this using what they call cookbooks. 173 00:06:30,360 --> 00:06:32,220 And this basically tells you how everything 174 00:06:32,220 --> 00:06:33,600 should be configured. 175 00:06:33,600 --> 00:06:35,520 There's lots of different recipes you can create 176 00:06:35,520 --> 00:06:37,680 and you can basically take these different services 177 00:06:37,680 --> 00:06:39,870 that are written inside of Ruby and put them together, 178 00:06:39,870 --> 00:06:41,070 using Chef. 179 00:06:41,070 --> 00:06:43,620 Chef has the ability to work with lots of virtual machines, 180 00:06:43,620 --> 00:06:45,420 as well as physical machines, containers 181 00:06:45,420 --> 00:06:47,340 and other cloud instances. 182 00:06:47,340 --> 00:06:48,780 When we talk about Puppet, 183 00:06:48,780 --> 00:06:50,670 Puppet is very similar to Chef. 184 00:06:50,670 --> 00:06:53,310 But it requires the installation of a master server 185 00:06:53,310 --> 00:06:56,041 and then client agents in the different targeted nodes 186 00:06:56,041 --> 00:06:57,420 to be able to do it's orchestration. 187 00:06:57,420 --> 00:06:59,550 Puppet, unlike Chef doesn't really rely on 188 00:06:59,550 --> 00:07:00,510 as much programming. 189 00:07:00,510 --> 00:07:02,040 So you really don't have to know Ruby, 190 00:07:02,040 --> 00:07:03,210 but you do need to understand some more 191 00:07:03,210 --> 00:07:04,470 traditional operations. 192 00:07:04,470 --> 00:07:06,180 So Puppet is pretty popular, 193 00:07:06,180 --> 00:07:08,730 especially with some of the older school folks. 194 00:07:08,730 --> 00:07:10,620 The next one we have is Ansible. 195 00:07:10,620 --> 00:07:14,070 Ansible, unlike Chef or Puppet, doesn't use user agents. 196 00:07:14,070 --> 00:07:16,770 Instead, everything is done using what's called, 197 00:07:16,770 --> 00:07:19,470 YAML, yet another markup language. 198 00:07:19,470 --> 00:07:21,900 These are different configuration files or playbooks 199 00:07:21,900 --> 00:07:24,390 and it allows the master to connect to the client machines 200 00:07:24,390 --> 00:07:26,580 over SSH to configure them. 201 00:07:26,580 --> 00:07:28,470 The next one we have is, Docker and you've probably heard 202 00:07:28,470 --> 00:07:29,490 of this one before. 203 00:07:29,490 --> 00:07:32,490 It's an open platform for developing, shipping, running 204 00:07:32,490 --> 00:07:33,870 and deploying applications 205 00:07:33,870 --> 00:07:36,180 using container based virtualization. 206 00:07:36,180 --> 00:07:38,700 When we talked earlier about virtualization and containers 207 00:07:38,700 --> 00:07:41,850 Docker is a good example of that container based system. 208 00:07:41,850 --> 00:07:44,340 Now, another one we have is what's known as Kubernetes. 209 00:07:44,340 --> 00:07:46,890 Now Kubernetes, provides an abstraction layer 210 00:07:46,890 --> 00:07:48,540 for managing these containers. 211 00:07:48,540 --> 00:07:50,580 So if you take Docker and you have all those containers 212 00:07:50,580 --> 00:07:52,830 and you need to be able to manage them, using scripts 213 00:07:52,830 --> 00:07:54,240 or other task reliably, 214 00:07:54,240 --> 00:07:56,790 you can use something like Kubernetes to do that. 215 00:07:56,790 --> 00:07:59,160 Another one we have is known as OpenStack. 216 00:07:59,160 --> 00:08:02,243 Now, OpenStack was originally created as a joint rackspace 217 00:08:02,243 --> 00:08:05,190 and NSA project, and it was actually deployed as an 218 00:08:05,190 --> 00:08:08,820 IaaS or infrastructure as a service solution 219 00:08:08,820 --> 00:08:10,620 to manage cloud resources. 220 00:08:10,620 --> 00:08:13,320 OpenStack can orchestrate the deployment of Linux, 221 00:08:13,320 --> 00:08:17,370 Apache, MySQL and PHP services known as lamp. 222 00:08:17,370 --> 00:08:19,350 And then the last one we have is GitHub. 223 00:08:19,350 --> 00:08:21,510 Now, GitHub is basically just a service that a lot 224 00:08:21,510 --> 00:08:23,370 of developers use to share their code. 225 00:08:23,370 --> 00:08:25,230 If you're programming and creating scripts, 226 00:08:25,230 --> 00:08:27,090 you can actually put those on GitHub. 227 00:08:27,090 --> 00:08:29,070 And if you're looking for some kind of an automation 228 00:08:29,070 --> 00:08:31,110 chances are somebody's already built it. 229 00:08:31,110 --> 00:08:32,669 So if you're thinking about how to orchestrate 230 00:08:32,669 --> 00:08:34,950 some kind of a new cloud service, you should first check 231 00:08:34,950 --> 00:08:36,539 on GitHub and see if other people 232 00:08:36,539 --> 00:08:39,330 in their public repositories have made that code available. 233 00:08:39,330 --> 00:08:41,370 If they have, you could take that as your starting point 234 00:08:41,370 --> 00:08:44,159 and then modify it for your own use case. 235 00:08:44,159 --> 00:08:45,930 Now all of these are different tools 236 00:08:45,930 --> 00:08:48,000 and you don't have to be an expert in any of them 237 00:08:48,000 --> 00:08:49,680 for the Linux plus exam. 238 00:08:49,680 --> 00:08:51,420 But the idea here is for you to understand 239 00:08:51,420 --> 00:08:52,740 when you hear these tools, 240 00:08:52,740 --> 00:08:55,200 you should be thinking about orchestration. 241 00:08:55,200 --> 00:08:58,620 Let's talk a little bit about agent versus agentless. 242 00:08:58,620 --> 00:09:00,840 Agent-based orchestration tools require 243 00:09:00,840 --> 00:09:04,110 that a software component resides on the managed device. 244 00:09:04,110 --> 00:09:06,090 When you have an agentless tool, on the other hand, 245 00:09:06,090 --> 00:09:08,340 it doesn't require additional software to exist 246 00:09:08,340 --> 00:09:10,770 ahead of time on that managed system. 247 00:09:10,770 --> 00:09:12,120 This is a big difference. 248 00:09:12,120 --> 00:09:15,060 And agent systems usually have more in depth control 249 00:09:15,060 --> 00:09:17,250 but you do have to preset them up, 250 00:09:17,250 --> 00:09:19,830 where agentless you can take control afterwards, 251 00:09:19,830 --> 00:09:21,840 without having installed tools. 252 00:09:21,840 --> 00:09:24,180 Now, orchestration procedures are going to vary, 253 00:09:24,180 --> 00:09:26,820 depending on which tool or solution you're going to use. 254 00:09:26,820 --> 00:09:29,340 But in general, orchestration steps are going to 255 00:09:29,340 --> 00:09:31,500 involve defining a desired configuration 256 00:09:31,500 --> 00:09:33,450 and then delivering that configuration file 257 00:09:33,450 --> 00:09:35,097 to the destination system. 258 00:09:35,097 --> 00:09:38,010 The configuration definition will then be processed 259 00:09:38,010 --> 00:09:40,050 and this will set up the system's configuration 260 00:09:40,050 --> 00:09:42,060 to match the definition file. 261 00:09:42,060 --> 00:09:44,640 For example, let's say your administrators configure 262 00:09:44,640 --> 00:09:48,120 and test a Chef cookbook with all your configurations in it. 263 00:09:48,120 --> 00:09:50,550 That cookbook will then be delivered to a specified 264 00:09:50,550 --> 00:09:52,110 destination client system. 265 00:09:52,110 --> 00:09:55,320 And then the chef client will process that cookbook 266 00:09:55,320 --> 00:09:57,630 and configure that node appropriately based 267 00:09:57,630 --> 00:09:59,460 on those configurations. 268 00:09:59,460 --> 00:10:01,050 When you're doing orchestration, 269 00:10:01,050 --> 00:10:02,970 the attributes are going to define tasks 270 00:10:02,970 --> 00:10:05,940 that need to be managed by the orchestration process. 271 00:10:05,940 --> 00:10:09,120 Administrators can use these attributes to identify specific 272 00:10:09,120 --> 00:10:11,220 configurations that need to be set through 273 00:10:11,220 --> 00:10:13,170 that orchestration process. 274 00:10:13,170 --> 00:10:16,170 When you're using OpenStack, for example, it's going to rely 275 00:10:16,170 --> 00:10:19,380 on attributes as you're doing all its processes. 276 00:10:19,380 --> 00:10:20,640 Another thing you need to think about, 277 00:10:20,640 --> 00:10:22,410 is inventory management. 278 00:10:22,410 --> 00:10:25,290 Inventory management of hardware, virtual machines, 279 00:10:25,290 --> 00:10:28,350 operating systems, applications and configurations 280 00:10:28,350 --> 00:10:30,930 can all be managed through orchestration tools. 281 00:10:30,930 --> 00:10:32,820 Different tools offer different features 282 00:10:32,820 --> 00:10:35,670 for inventory management, including reporting. 283 00:10:35,670 --> 00:10:37,620 Inventory management is crucial 284 00:10:37,620 --> 00:10:39,540 because administrators cannot manage 285 00:10:39,540 --> 00:10:41,760 what they don't know exists on the network. 286 00:10:41,760 --> 00:10:43,320 And when you're doing orchestration, 287 00:10:43,320 --> 00:10:45,270 the systems can be creating new systems 288 00:10:45,270 --> 00:10:46,620 without you even knowing it 289 00:10:46,620 --> 00:10:49,170 because we're using infrastructure as code. 290 00:10:49,170 --> 00:10:51,540 Now, the benefits of configuration management 291 00:10:51,540 --> 00:10:54,300 are also going to consistently use configured systems 292 00:10:54,300 --> 00:10:57,090 and a more efficient build process by maintaining 293 00:10:57,090 --> 00:10:59,910 a good solid configuration baseline for us. 294 00:10:59,910 --> 00:11:01,650 Ensuring that all of our systems meet 295 00:11:01,650 --> 00:11:03,930 a configuration baseline, will help enforce our 296 00:11:03,930 --> 00:11:06,810 security requirements and our service-level agreements, 297 00:11:06,810 --> 00:11:09,300 as well as making our change management much more efficient 298 00:11:09,300 --> 00:11:10,380 in the long run. 299 00:11:10,380 --> 00:11:12,870 So, when you think of orchestration, 300 00:11:12,870 --> 00:11:15,360 think about a system that can apply the changes 301 00:11:15,360 --> 00:11:18,060 and the baseline for you and build things 302 00:11:18,060 --> 00:11:21,570 using infrastructure as code or infrastructure as a service. 303 00:11:21,570 --> 00:11:24,810 When you think of automation, think about a single task 304 00:11:24,810 --> 00:11:26,790 that is taking the hands off work from 305 00:11:26,790 --> 00:11:29,700 the system administrator and doing it using a basic script. 306 00:11:29,700 --> 00:11:32,373 So you can get more things done in less time.