1 00:00:00,510 --> 00:00:03,790 Helen will come back with our second lecture on. 2 00:00:03,860 --> 00:00:04,390 Yes. 3 00:00:04,410 --> 00:00:10,760 And still we're not jumping into easy as we'll introduce darker and darker containers in this lecture. 4 00:00:13,980 --> 00:00:15,990 So Doctor what is it. 5 00:00:16,010 --> 00:00:22,870 Look it is a software platform that allows you to build test and deploy distributed applications quickly. 6 00:00:22,980 --> 00:00:26,230 When we talk about distributed applications we're talking about micro services. 7 00:00:26,550 --> 00:00:30,060 And actually this is container's here. 8 00:00:30,060 --> 00:00:38,100 So this is a way or a software that allows you to build test and deploy containers quickly but the mission 9 00:00:38,160 --> 00:00:46,760 management and orchestration tool if you will look or packages of software into standardized units called 10 00:00:47,000 --> 00:00:51,190 containers that have everything the software needs to run including library. 11 00:00:51,180 --> 00:00:54,250 So what are we talking about software the time of the application here. 12 00:00:54,270 --> 00:01:00,290 So we it will allow the application to run including everything that it needs as such as libraries the 13 00:01:00,290 --> 00:01:03,320 binary file system tools code and runtime 14 00:01:06,010 --> 00:01:12,760 using Daker you can quickly deploy and scale applications into any environment and no your code will 15 00:01:12,760 --> 00:01:13,180 run. 16 00:01:13,180 --> 00:01:13,570 Why. 17 00:01:13,570 --> 00:01:20,140 Because they can containers completely abstract the application and its dependencies from the underlying 18 00:01:20,230 --> 00:01:21,670 OS and infrastructure. 19 00:01:21,670 --> 00:01:27,990 So only use the kernel and the kernel works with the infrastructure. 20 00:01:28,940 --> 00:01:33,800 So what's the benefit of running Dharker on each of us and that's all what the easy to contain or service 21 00:01:33,800 --> 00:01:39,090 or easy task is about running on each of us provides developers the ADA developers on it. 22 00:01:39,150 --> 00:01:47,810 Yes and the administrators are highly reliable low cost way to build chiff and run distributed applications 23 00:01:47,810 --> 00:01:49,650 or micro services at any scale. 24 00:01:51,260 --> 00:01:58,330 I wasn't s.c.s leverages or takes advantage of darker images in Task definition's to launch containers 25 00:01:58,330 --> 00:02:00,980 on easy to instances in your clusters. 26 00:02:01,310 --> 00:02:04,660 OK so here we learn about a dual core image. 27 00:02:04,660 --> 00:02:10,360 We learn about the task definition that are used to launch containers and I see two instances. 28 00:02:10,370 --> 00:02:21,090 So in order for it C-s to run containers on easy to instance or on your PC or on the platform two things 29 00:02:21,090 --> 00:02:24,030 will be used for images and task definitions. 30 00:02:24,120 --> 00:02:28,280 And we're not going to elaborate on that more because we have a lecture where we'll talk about them 31 00:02:30,750 --> 00:02:34,210 it supports both the barker licensing model. 32 00:02:34,220 --> 00:02:35,840 So look it has to licensing mothers. 33 00:02:35,870 --> 00:02:38,690 The first one is the open source docker community edition. 34 00:02:38,690 --> 00:02:43,990 CD and the Enterprise Edition subscription based. 35 00:02:44,010 --> 00:02:46,220 So these are the commercial one that's the open source. 36 00:02:49,930 --> 00:02:56,910 A container is a lightweight a standalone executable package of a piece of software. 37 00:02:56,940 --> 00:03:02,070 So that's your application that includes everything needed to run code runtime system to system libraries 38 00:03:02,100 --> 00:03:02,730 and settings. 39 00:03:02,730 --> 00:03:04,950 I mean you are repeating this again and again. 40 00:03:05,160 --> 00:03:06,910 So hopefully it sticks. 41 00:03:07,080 --> 00:03:09,770 And this is the VM versus the container. 42 00:03:09,780 --> 00:03:15,330 So the VM you have the host operating system and then you have the hypervisor and different guest operating 43 00:03:15,330 --> 00:03:16,800 system for each virtual machine. 44 00:03:16,800 --> 00:03:18,750 So this is your virtual machine. 45 00:03:18,750 --> 00:03:27,150 While here we have only the application binary library so you took this part and that is what you move 46 00:03:27,360 --> 00:03:28,400 into a container. 47 00:03:28,420 --> 00:03:35,060 That's what is going to be installed into a container the equivalent if we are to compare is the dock 48 00:03:35,060 --> 00:03:35,680 or engine. 49 00:03:35,730 --> 00:03:43,530 So basically how you can allow the different applications to use the kernel and be separated from each 50 00:03:43,530 --> 00:03:49,300 other and each one feels that it has all what it needs so basically to reach the kernel. 51 00:03:49,310 --> 00:03:56,070 And from that to the infrastructure available for Bosso looker is available for both Linux and Windows 52 00:03:56,070 --> 00:04:00,420 based application containerized software will always run the same regardless of the environment. 53 00:04:00,420 --> 00:04:04,920 So you take it from one Windows Server and move it into another Windows Server that is supported and 54 00:04:04,920 --> 00:04:11,760 it runs because it does have all it needs containers isolate software from its surroundings. 55 00:04:11,760 --> 00:04:18,210 For example differences between development and staging environments and will help reduce conflicts 56 00:04:18,210 --> 00:04:21,600 between teams running different software on the same infrastructure. 57 00:04:21,630 --> 00:04:26,920 So moving it the software application from test into a staging environment into production environment. 58 00:04:27,120 --> 00:04:34,590 As long as the underlying operating system kernel has all what it needs then you are assured that your 59 00:04:34,590 --> 00:04:38,450 application that you are running into a container will run. 60 00:04:38,520 --> 00:04:44,080 Also it reduces conflict between teams running different software on the same infrastructure. 61 00:04:44,080 --> 00:04:51,630 The container engine is the rough equivalent to hypervisor and VM Ducker being the most famous container 62 00:04:51,690 --> 00:04:52,780 engine today. 63 00:04:53,370 --> 00:04:56,430 There is one more good thing about containers. 64 00:04:56,460 --> 00:05:01,720 We said that the application the container right with it's binary and library files. 65 00:05:01,740 --> 00:05:03,290 This is how it runs right. 66 00:05:03,360 --> 00:05:08,140 So this is containers on a physical host. 67 00:05:08,190 --> 00:05:10,400 So this is a physical host. 68 00:05:10,400 --> 00:05:12,430 Here is the shared operating system. 69 00:05:12,480 --> 00:05:17,010 Here's the ducker engine and then I have a function with its binary and library files and tools and 70 00:05:17,010 --> 00:05:17,490 all that. 71 00:05:17,490 --> 00:05:18,720 A picture can be an application. 72 00:05:18,720 --> 00:05:26,920 See the same thing can run on virtual machine so I can containerized applications on virtual machine 73 00:05:26,930 --> 00:05:29,770 so here we have the infrastructure. 74 00:05:30,010 --> 00:05:34,440 I have the hypervisor So this could be what exactly. 75 00:05:34,460 --> 00:05:40,280 This could be the AWOS virtualise Zen environment right. 76 00:05:40,650 --> 00:05:45,840 And this could be the easy two instances of the virtual machines can be that two instances where I have 77 00:05:45,850 --> 00:05:52,380 against Oist that could be Windows or Linux and then I can containerized up occasion so I have a Linux 78 00:05:52,560 --> 00:05:53,870 server. 79 00:05:54,150 --> 00:06:02,410 So this is Linux on an easy to instance see two instance boundaries from here all the way to here. 80 00:06:02,730 --> 00:06:09,050 Virtualise on as in all else which is the AWOS virtualization hypervisor. 81 00:06:09,270 --> 00:06:17,280 And then I can start containerized applications on an easy to instance and then I have another easy 82 00:06:17,310 --> 00:06:21,520 to instance where I continue as a precaution and so on and so forth. 83 00:06:21,560 --> 00:06:27,760 So containers can run on physical Holst's as well as on virtual machines. 84 00:06:27,760 --> 00:06:34,180 If it runs on virtual machines that means you can run containers in a public cloud like AWOS Microsoft 85 00:06:34,660 --> 00:06:39,120 and Google and you can also run it in private cloud. 86 00:06:39,180 --> 00:06:49,360 If the Enterprise had virtualization in a cloud environment within the on premise environment and that 87 00:06:49,360 --> 00:06:55,240 allows the containers and Voelker to be which is the case now on E.W. us or Microsoft Azure and others 88 00:06:55,360 --> 00:06:58,100 and it can run on virtual machines. 89 00:06:58,100 --> 00:07:04,300 Ok so now we can containerized applications not only on your own premise infrastructure but in the cloud 90 00:07:04,330 --> 00:07:05,230 as well. 91 00:07:05,230 --> 00:07:10,180 On bare metal if that cloud provider provides that which it doesn't IDM does as well. 92 00:07:10,180 --> 00:07:16,810 IBM cloud I've been Lumix or on virtual machines so you can have virtual machines and on top of that 93 00:07:17,080 --> 00:07:24,060 you can containerized application so micro services now basically using Dharker in Sevilla Unternehmens 94 00:07:24,100 --> 00:07:29,950 it's available in the private cloud is available on public clouds and that's what the easy s or Vaizey 95 00:07:29,950 --> 00:07:35,350 do container services and you know it's all about running containerized applications using Dharker on 96 00:07:35,370 --> 00:07:35,590 it. 97 00:07:35,600 --> 00:07:45,960 Yes the containers and their features their containers are lightweight they run on a single machine 98 00:07:46,770 --> 00:07:53,540 sharing their machines operating system kernel they start instantly so very fast to the book to boot 99 00:07:53,630 --> 00:08:01,250 and use less compute and the images are constructed from file system layers and share common files these 100 00:08:01,250 --> 00:08:06,830 minimize disk usage and image nodes are much faster because of the containers application as you said 101 00:08:06,830 --> 00:08:10,170 it's in the order of tens of megabytes it is tender. 102 00:08:10,190 --> 00:08:20,540 There is an effort called OCI where a lot of companies HP IBM Apple Microsoft and others are working 103 00:08:20,540 --> 00:08:23,790 to standardize more and more of the containerization features. 104 00:08:23,810 --> 00:08:29,150 So look at containers are based on open standards and they run on all the major Linux distributions 105 00:08:29,480 --> 00:08:36,410 Microsoft Windows and any infrastructure including virtual machines as we saw in the previous slide 106 00:08:36,740 --> 00:08:38,680 very Mattel and in the cloud. 107 00:08:38,840 --> 00:08:44,950 So anyway you want to containerized applications it's ready because they're And it is secure. 108 00:08:44,950 --> 00:08:49,140 I mean that's debatable but that's the message. 109 00:08:49,360 --> 00:08:55,030 Look at Quentin's containers isolate applications from one another and from the underlying infrastructure 110 00:08:55,150 --> 00:09:01,690 look at provides the strongest default solution to limit issues to a single container instead of the 111 00:09:01,690 --> 00:09:02,320 internal machine. 112 00:09:02,320 --> 00:09:07,630 So if one application in a container is compromised here the message is this is completely isolated 113 00:09:07,630 --> 00:09:08,340 from the others. 114 00:09:08,350 --> 00:09:13,480 But of course the ones who are pro virtual machines they would say no it's not isolated because you 115 00:09:13,480 --> 00:09:16,140 are sharing the same kernel the same operating system. 116 00:09:16,180 --> 00:09:19,340 So how if there is a bug in the operating system it affects all of them. 117 00:09:19,360 --> 00:09:19,740 Right. 118 00:09:19,840 --> 00:09:23,110 What else is required so then we have the containers we talked about the containers. 119 00:09:23,110 --> 00:09:29,940 How can I manage and orchestrate the deployment and monitoring and provisioning of containers. 120 00:09:31,160 --> 00:09:36,140 So the additional software that is needed to support the use of standardized containers and talking 121 00:09:36,140 --> 00:09:42,080 about her here are similar in any enterprise or cloud environment or container orchestration and management 122 00:09:42,080 --> 00:09:43,280 systems. 123 00:09:43,280 --> 00:09:47,530 And of course if you want to add to the security then you need also container security systems. 124 00:09:47,570 --> 00:09:54,050 So this is the missing piece and that's what the doctor provides us container of frustration and management 125 00:09:54,170 --> 00:09:57,270 system. 126 00:09:57,290 --> 00:10:03,770 So what would the container station monitoring system help me achieve that could determine if of that 127 00:10:03,770 --> 00:10:07,960 will help you push those containers out to different machines. 128 00:10:08,120 --> 00:10:14,470 If I have a pool of either virtual machines or two instances a cluster or physical barrier mental said 129 00:10:14,470 --> 00:10:20,380 wooers How can I push the containers to which one. 130 00:10:20,520 --> 00:10:23,180 And based on what what's the available memory what's available. 131 00:10:23,190 --> 00:10:31,170 Hard Disk space or just the volume space that I can push and install the container on all that has to 132 00:10:31,170 --> 00:10:32,680 be orchestrated by a tool. 133 00:10:32,700 --> 00:10:33,050 Right. 134 00:10:33,090 --> 00:10:34,530 So that's what you're talking about here. 135 00:10:37,030 --> 00:10:40,560 Also the container orchestration and management system. 136 00:10:40,650 --> 00:10:46,270 It will it make sure that they run and spin up a few more containers with a specific application and 137 00:10:46,270 --> 00:10:48,580 when demand increase so it lost the city. 138 00:10:48,610 --> 00:10:55,350 How when they demand increase Who is going to spin more containers as we did with other scaling when 139 00:10:55,350 --> 00:10:58,860 we had two instances and wanted to spend more as two instances right. 140 00:10:58,890 --> 00:11:03,360 And also if the containers need to know about each other if they need to communicate with each other 141 00:11:03,360 --> 00:11:09,180 you will also still need some way of setting up networking virtual network between them that can assign 142 00:11:09,210 --> 00:11:17,280 IP addresses to every container Cabernets is the best known widely used free or open source content 143 00:11:17,340 --> 00:11:18,390 management system. 144 00:11:18,390 --> 00:11:22,610 And this is very popular in most of the cloud providers as well. 145 00:11:22,710 --> 00:11:29,880 So when you hear the term Cabernets this is your open are the most widely used open source that was 146 00:11:29,880 --> 00:11:32,900 started by Google for content or management. 147 00:11:32,940 --> 00:11:39,300 It provides a mechanism to deploy maintain and scale control applications which is the function of that 148 00:11:39,430 --> 00:11:42,960 container station management. 149 00:11:43,150 --> 00:11:49,630 The one that is known as a commercial product that needs the very famous or the top is our friend the 150 00:11:49,660 --> 00:11:52,150 broker Enterprise Edition. 151 00:11:52,220 --> 00:11:54,010 And this is what is used on it. 152 00:11:54,080 --> 00:12:00,940 Yes so looking to preservation is the best noncommercial content container management solution. 153 00:12:01,100 --> 00:12:07,160 It provides an integrated tested and certified platform for applications running on Enterprise Linux 154 00:12:07,250 --> 00:12:12,410 or Windows operating system and cloud providers and it runs on AWOS. 155 00:12:12,440 --> 00:12:14,710 And this is what Easy S is all about. 156 00:12:15,730 --> 00:12:18,310 And there are other commercial products as well. 157 00:12:18,520 --> 00:12:26,290 Like the core or as tectonic plate had open shift container platform and non-shared labs venture product 158 00:12:27,000 --> 00:12:34,510 but Ducker as we mentioned is the most famous one and it was I think the first one to come out as one. 159 00:12:34,660 --> 00:12:39,480 Right so let's take a quick break come back and start talking about our business. 160 00:12:39,490 --> 00:12:48,100 The AWOS Yes this lecture and the previous one were important to explain to you and get the information 161 00:12:48,130 --> 00:12:54,400 gradually from traditional to virtual machines to containers and then talk about containers generally 162 00:12:54,400 --> 00:12:55,350 speaking. 163 00:12:55,660 --> 00:13:01,900 And then to introduce darker and how it works and what are the components what is needed and how it 164 00:13:01,900 --> 00:13:08,430 runs on virtual machines like easy to instances or physical servers or into the cloud. 165 00:13:08,890 --> 00:13:15,340 So in the next one we're start digging into easier itself and understanding more about it which is very 166 00:13:15,340 --> 00:13:17,760 key to passing the exam. 167 00:13:17,890 --> 00:13:19,220 Okay I'll see in the next lecture. 168 00:13:19,300 --> 00:13:19,690 Thank you.