1 00:00:00,420 --> 00:00:05,580 Alone will come back with another interesting topic which is inebriates artworks of sorts will help 2 00:00:05,580 --> 00:00:10,040 you deploy and manage your applications on instances. 3 00:00:10,110 --> 00:00:13,120 So let's dive in and find out what works is all about. 4 00:00:13,230 --> 00:00:18,430 Generally speaking any cloud based computing will involve group of resources and if you are talking 5 00:00:18,430 --> 00:00:23,320 about it as a group of resources could include Is it two instances containers. 6 00:00:23,340 --> 00:00:26,960 It could include databases such as RDX or dynamic D-B. 7 00:00:27,270 --> 00:00:34,420 And also as you scale you might want to include features like or services like yes Elby or classical 8 00:00:34,420 --> 00:00:36,000 or balancers to be more specific. 9 00:00:36,010 --> 00:00:38,570 Now as the environment grows how can you manage it. 10 00:00:38,580 --> 00:00:41,000 How can you automate the roll out of application. 11 00:00:41,010 --> 00:00:47,550 How can you do it to meet the roll out the deployment monitoring the unemployment or decommissioning 12 00:00:47,580 --> 00:00:48,680 of applications. 13 00:00:48,690 --> 00:00:54,090 How can you stage an application before you roll it out to ensure that is going to work out perfectly 14 00:00:54,090 --> 00:00:55,120 as you want to be. 15 00:00:55,140 --> 00:01:01,500 How can you get most of the burden of installing and running applications on us off your back so basically 16 00:01:01,500 --> 00:01:03,600 automating that absorbs helps you do that. 17 00:01:03,600 --> 00:01:08,790 And one very important question that might evolve in your on your mind or maybe you would face it in 18 00:01:08,790 --> 00:01:14,400 exam questions and you will be confused between upswings and cloud formation as we know cloud formation 19 00:01:14,490 --> 00:01:17,640 is about automating your whole infrastructure. 20 00:01:17,760 --> 00:01:24,180 So all the services or almost all of them that are included in your infrastructure so that could be 21 00:01:24,240 --> 00:01:30,060 anything could be S-3 could be done and could be RLDS launching is it to instance is launching many 22 00:01:30,060 --> 00:01:32,570 things you could imagine in your infrastructure. 23 00:01:32,870 --> 00:01:37,030 So cloud formation is broad and it's about managing infrastructure as. 24 00:01:37,070 --> 00:01:41,820 But cloud formation is not about focusing on your application monitoring your application deploying 25 00:01:41,820 --> 00:01:46,110 your application giving your statistics out what's going on with your application works. 26 00:01:46,350 --> 00:01:50,620 So absorbance deals with a narrow or a smaller number of services. 27 00:01:50,640 --> 00:01:57,450 We mentioned some or most of them load balancing easy to our D.S. plastic container services but that's 28 00:01:57,450 --> 00:02:02,970 it that's that's the range that it would work with because the focus of Officeworks is not about the 29 00:02:02,970 --> 00:02:04,790 infrastructure or the underlaid. 30 00:02:05,040 --> 00:02:09,510 It's about the many infrastructure that has to do with the application and then money deploying and 31 00:02:09,510 --> 00:02:10,530 monitoring the application. 32 00:02:10,530 --> 00:02:16,970 Please distinguish between a specific focus of ops works and a broad focus of elaboration. 33 00:02:16,980 --> 00:02:21,930 So in addition to creating the instances which is the infrastructure for application and its totally 34 00:02:21,990 --> 00:02:27,120 unnecessary packages deploying the application you typically need a way to distribute applications to 35 00:02:27,120 --> 00:02:28,270 the application servers. 36 00:02:28,380 --> 00:02:33,930 When you roll out when you scale monitor the stacks performance so the collection of servers that run 37 00:02:33,930 --> 00:02:38,760 the application also would like to manage its performance manage security permissions and so on. 38 00:02:38,760 --> 00:02:45,000 So who can help you do all of that absorb so absorb stacks provides a simple and flexible way to create 39 00:02:45,000 --> 00:02:49,480 and manage stacks and applications and the stack is the core component of our ports. 40 00:02:49,550 --> 00:02:54,960 So our stack is what is easy to instance is the logical balancers is that Hobbes's that you are using 41 00:02:55,110 --> 00:02:58,010 and the application thats the stack that we are talking about. 42 00:02:58,030 --> 00:03:04,260 So here is a simple stack in terms of obsolete and are going to explain all of that cookbook depositary 43 00:03:04,350 --> 00:03:06,350 application repository users. 44 00:03:06,390 --> 00:03:11,760 And then you have within it up your ass you have custom the last layer Microsoft Internet Information 45 00:03:11,760 --> 00:03:17,220 Server layer you have a Windows instance and you have the application and that is the OPs or Stex. 46 00:03:17,220 --> 00:03:22,290 So that is one layer or a single layer absorbs stack and we're going to talk about layers cookbooks 47 00:03:22,320 --> 00:03:23,610 all that don't work. 48 00:03:23,610 --> 00:03:28,830 So as an example of where the application typically requires application servers the resellers load 49 00:03:28,830 --> 00:03:29,890 balancers and so on. 50 00:03:29,910 --> 00:03:34,920 So if you want to put that in a graphical depiction you have the users or the application that probably 51 00:03:34,920 --> 00:03:36,120 would be coming through the Internet. 52 00:03:36,120 --> 00:03:41,700 You need an internet facing load balance and you have then the application server you can scale. 53 00:03:41,820 --> 00:03:46,390 And if one is unhealthy it can be removed without affecting the application and the user experience 54 00:03:46,810 --> 00:03:51,530 and behind that will be data which is of course security will be available as well. 55 00:03:51,540 --> 00:03:52,500 Have you discussed before. 56 00:03:52,530 --> 00:03:56,370 So this is collectively called a stack in OPS works. 57 00:03:56,400 --> 00:04:02,760 So an optional stack provides average set of customizable components that you can mix and match to create 58 00:04:02,850 --> 00:04:06,170 a stack that satisfies the application requirements. 59 00:04:06,200 --> 00:04:12,270 They see to instance which is an instance you need to do Michael C. is it large is it small is it extra 60 00:04:12,270 --> 00:04:19,200 large It allows its edge and our DP access to stack instances and resources can be managed only in the 61 00:04:19,200 --> 00:04:21,630 region in which they are created. 62 00:04:21,630 --> 00:04:24,940 And here is an important one probably will highlight that later on. 63 00:04:25,170 --> 00:04:30,570 But when you are creating the stack you will specify the region when you specify the region once it 64 00:04:30,570 --> 00:04:31,300 is created. 65 00:04:31,320 --> 00:04:37,610 You cannot you can not an OT change the region of an existing stack. 66 00:04:37,690 --> 00:04:42,420 Ok so you need to build another one in a different region if you want to play with the resources that 67 00:04:42,420 --> 00:04:48,390 are created in one original point are not available nor can they be cloned into another regional endpoint 68 00:04:48,630 --> 00:04:50,360 so that it created in a region. 69 00:04:50,370 --> 00:04:52,170 You're stuck with that one for that stack. 70 00:04:52,170 --> 00:04:54,780 So we talk about artworks and automation. 71 00:04:54,780 --> 00:04:56,500 What is the tool inherent to that. 72 00:04:56,500 --> 00:05:02,450 Chef Chef is the automation tool used or the application moment and management tool that is used for 73 00:05:02,450 --> 00:05:03,190 AAPS works. 74 00:05:03,200 --> 00:05:05,810 Stex why would we use it because we need to automate it. 75 00:05:05,810 --> 00:05:08,650 So as your environment grow you cannot do it manually. 76 00:05:08,660 --> 00:05:14,030 The management and deployment and you would like to have an automation tool for that and chefe will 77 00:05:14,030 --> 00:05:14,960 be our automation too. 78 00:05:14,990 --> 00:05:15,860 What does it provide. 79 00:05:15,860 --> 00:05:20,720 It provides automated configuration management that enables consistent configurations at Cape chaffe 80 00:05:20,720 --> 00:05:23,880 helps in ensuring that configuration policy is flexible. 81 00:05:23,890 --> 00:05:30,320 The configuration policy to your servers to you are it to instance it is very general testable and human 82 00:05:30,410 --> 00:05:35,670 readable servers menaced by chefe are continuously evaluated against their desired state. 83 00:05:35,730 --> 00:05:41,870 So chef knows it because it has the configuration files or a script or recipes as we explain shortly. 84 00:05:41,900 --> 00:05:47,030 It knows the desired state always will compare what is deployed to the desired state ensure ensuring 85 00:05:47,030 --> 00:05:53,500 that configuration is automatically corrected and configuration changes are universally applied. 86 00:05:53,510 --> 00:05:58,930 When you have a new version of code that is the piece then chef will take care of that. 87 00:05:59,030 --> 00:06:04,340 If there are any changes or discrepancies chef is going to also continuously monitor your application 88 00:06:04,370 --> 00:06:07,160 and find out these errors and correct them for you. 89 00:06:07,160 --> 00:06:08,420 Good books and recipes. 90 00:06:08,720 --> 00:06:10,220 We'll hear about that a lot as. 91 00:06:10,320 --> 00:06:16,060 As long as you are talking about automation and absorbs or chef to a cookbook what is a cookbook. 92 00:06:16,100 --> 00:06:20,960 Now we're talking about a chef the chef needs a kitchen and the kitchen needs cookbooks so the cookbook 93 00:06:21,020 --> 00:06:26,720 is a packaged file that contains configuration information instructions that are called recipes because 94 00:06:26,720 --> 00:06:33,080 in a cookbook The chef will use the cookbook for whatfor recipes recipes a set of one or more instructions 95 00:06:33,080 --> 00:06:37,850 to do what it has to do with an application you would like to roll out the application or like to deploy 96 00:06:37,850 --> 00:06:44,450 it configure it in a certain way and the instructions are written in Ruby language syntax and the instructions 97 00:06:44,450 --> 00:06:49,750 will specify the resources to use and the order in which those resources are applied. 98 00:06:49,760 --> 00:06:51,440 What is it that we're talking about here. 99 00:06:51,500 --> 00:06:53,100 Is it to instance. 100 00:06:53,270 --> 00:06:55,220 No I have now taken you out of it. 101 00:06:55,230 --> 00:07:01,040 Yes you are talking about chef chef cook books and recipes abstracted from whether you are using it 102 00:07:01,040 --> 00:07:02,630 on us or somewhere else. 103 00:07:02,630 --> 00:07:07,820 So here when we talking about resources we're not talking about resources we're talking about Chef resource 104 00:07:07,910 --> 00:07:14,540 and the resource in that chef automation too is about one instruction or one statement that you are 105 00:07:14,540 --> 00:07:15,100 going to use. 106 00:07:15,110 --> 00:07:20,420 One thing you need to keep in mind that Opsware we can automatically run them at the appropriate time 107 00:07:20,470 --> 00:07:22,160 around what Aranda recipes. 108 00:07:22,190 --> 00:07:28,370 And also you can run them manually before we leave chefe completely and go back to artworks then resource 109 00:07:28,400 --> 00:07:33,110 in Sheft terms or resource as used in Schaff is a statement of configuration policy. 110 00:07:33,200 --> 00:07:35,960 In the next lecture we're going to talk about stacks and layers. 111 00:07:36,050 --> 00:07:42,590 So as we saw in the one layer I was drawing that we looked at we call that earlier. 112 00:07:42,590 --> 00:07:47,240 So what is a stack and what is clear is what we will discuss in the next lecture. 113 00:07:47,240 --> 00:07:47,870 I'll see you then. 114 00:07:47,900 --> 00:07:48,210 Thank you.