Helen will come back with our second lecture on.
Yes.
And still we're not jumping into easy as we'll introduce darker and darker containers in this lecture.
So Doctor what is it.
Look it is a software platform that allows you to build test and deploy distributed applications quickly.
When we talk about distributed applications we're talking about micro services.
And actually this is container's here.
So this is a way or a software that allows you to build test and deploy containers quickly but the mission
management and orchestration tool if you will look or packages of software into standardized units called
containers that have everything the software needs to run including library.
So what are we talking about software the time of the application here.
So we it will allow the application to run including everything that it needs as such as libraries the
binary file system tools code and runtime
using Daker you can quickly deploy and scale applications into any environment and no your code will
run.
Why.
Because they can containers completely abstract the application and its dependencies from the underlying
OS and infrastructure.
So only use the kernel and the kernel works with the infrastructure.
So what's the benefit of running Dharker on each of us and that's all what the easy to contain or service
or easy task is about running on each of us provides developers the ADA developers on it.
Yes and the administrators are highly reliable low cost way to build chiff and run distributed applications
or micro services at any scale.
I wasn't s.c.s leverages or takes advantage of darker images in Task definition's to launch containers
on easy to instances in your clusters.
OK so here we learn about a dual core image.
We learn about the task definition that are used to launch containers and I see two instances.
So in order for it C-s to run containers on easy to instance or on your PC or on the platform two things
will be used for images and task definitions.
And we're not going to elaborate on that more because we have a lecture where we'll talk about them
it supports both the barker licensing model.
So look it has to licensing mothers.
The first one is the open source docker community edition.
CD and the Enterprise Edition subscription based.
So these are the commercial one that's the open source.
A container is a lightweight a standalone executable package of a piece of software.
So that's your application that includes everything needed to run code runtime system to system libraries
and settings.
I mean you are repeating this again and again.
So hopefully it sticks.
And this is the VM versus the container.
So the VM you have the host operating system and then you have the hypervisor and different guest operating
system for each virtual machine.
So this is your virtual machine.
While here we have only the application binary library so you took this part and that is what you move
into a container.
That's what is going to be installed into a container the equivalent if we are to compare is the dock
or engine.
So basically how you can allow the different applications to use the kernel and be separated from each
other and each one feels that it has all what it needs so basically to reach the kernel.
And from that to the infrastructure available for Bosso looker is available for both Linux and Windows
based application containerized software will always run the same regardless of the environment.
So you take it from one Windows Server and move it into another Windows Server that is supported and
it runs because it does have all it needs containers isolate software from its surroundings.
For example differences between development and staging environments and will help reduce conflicts
between teams running different software on the same infrastructure.
So moving it the software application from test into a staging environment into production environment.
As long as the underlying operating system kernel has all what it needs then you are assured that your
application that you are running into a container will run.
Also it reduces conflict between teams running different software on the same infrastructure.
The container engine is the rough equivalent to hypervisor and VM Ducker being the most famous container
engine today.
There is one more good thing about containers.
We said that the application the container right with it's binary and library files.
This is how it runs right.
So this is containers on a physical host.
So this is a physical host.
Here is the shared operating system.
Here's the ducker engine and then I have a function with its binary and library files and tools and
all that.
A picture can be an application.
See the same thing can run on virtual machine so I can containerized applications on virtual machine
so here we have the infrastructure.
I have the hypervisor So this could be what exactly.
This could be the AWOS virtualise Zen environment right.
And this could be the easy two instances of the virtual machines can be that two instances where I have
against Oist that could be Windows or Linux and then I can containerized up occasion so I have a Linux
server.
So this is Linux on an easy to instance see two instance boundaries from here all the way to here.
Virtualise on as in all else which is the AWOS virtualization hypervisor.
And then I can start containerized applications on an easy to instance and then I have another easy
to instance where I continue as a precaution and so on and so forth.
So containers can run on physical Holst's as well as on virtual machines.
If it runs on virtual machines that means you can run containers in a public cloud like AWOS Microsoft
and Google and you can also run it in private cloud.
If the Enterprise had virtualization in a cloud environment within the on premise environment and that
allows the containers and Voelker to be which is the case now on E.W. us or Microsoft Azure and others
and it can run on virtual machines.
Ok so now we can containerized applications not only on your own premise infrastructure but in the cloud
as well.
On bare metal if that cloud provider provides that which it doesn't IDM does as well.
IBM cloud I've been Lumix or on virtual machines so you can have virtual machines and on top of that
you can containerized application so micro services now basically using Dharker in Sevilla Unternehmens
it's available in the private cloud is available on public clouds and that's what the easy s or Vaizey
do container services and you know it's all about running containerized applications using Dharker on
it.
Yes the containers and their features their containers are lightweight they run on a single machine
sharing their machines operating system kernel they start instantly so very fast to the book to boot
and use less compute and the images are constructed from file system layers and share common files these
minimize disk usage and image nodes are much faster because of the containers application as you said
it's in the order of tens of megabytes it is tender.
There is an effort called OCI where a lot of companies HP IBM Apple Microsoft and others are working
to standardize more and more of the containerization features.
So look at containers are based on open standards and they run on all the major Linux distributions
Microsoft Windows and any infrastructure including virtual machines as we saw in the previous slide
very Mattel and in the cloud.
So anyway you want to containerized applications it's ready because they're And it is secure.
I mean that's debatable but that's the message.
Look at Quentin's containers isolate applications from one another and from the underlying infrastructure
look at provides the strongest default solution to limit issues to a single container instead of the
internal machine.
So if one application in a container is compromised here the message is this is completely isolated
from the others.
But of course the ones who are pro virtual machines they would say no it's not isolated because you
are sharing the same kernel the same operating system.
So how if there is a bug in the operating system it affects all of them.
Right.
What else is required so then we have the containers we talked about the containers.
How can I manage and orchestrate the deployment and monitoring and provisioning of containers.
So the additional software that is needed to support the use of standardized containers and talking
about her here are similar in any enterprise or cloud environment or container orchestration and management
systems.
And of course if you want to add to the security then you need also container security systems.
So this is the missing piece and that's what the doctor provides us container of frustration and management
system.
So what would the container station monitoring system help me achieve that could determine if of that
will help you push those containers out to different machines.
If I have a pool of either virtual machines or two instances a cluster or physical barrier mental said
wooers How can I push the containers to which one.
And based on what what's the available memory what's available.
Hard Disk space or just the volume space that I can push and install the container on all that has to
be orchestrated by a tool.
Right.
So that's what you're talking about here.
Also the container orchestration and management system.
It will it make sure that they run and spin up a few more containers with a specific application and
when demand increase so it lost the city.
How when they demand increase Who is going to spin more containers as we did with other scaling when
we had two instances and wanted to spend more as two instances right.
And also if the containers need to know about each other if they need to communicate with each other
you will also still need some way of setting up networking virtual network between them that can assign
IP addresses to every container Cabernets is the best known widely used free or open source content
management system.
And this is very popular in most of the cloud providers as well.
So when you hear the term Cabernets this is your open are the most widely used open source that was
started by Google for content or management.
It provides a mechanism to deploy maintain and scale control applications which is the function of that
container station management.
The one that is known as a commercial product that needs the very famous or the top is our friend the
broker Enterprise Edition.
And this is what is used on it.
Yes so looking to preservation is the best noncommercial content container management solution.
It provides an integrated tested and certified platform for applications running on Enterprise Linux
or Windows operating system and cloud providers and it runs on AWOS.
And this is what Easy S is all about.
And there are other commercial products as well.
Like the core or as tectonic plate had open shift container platform and non-shared labs venture product
but Ducker as we mentioned is the most famous one and it was I think the first one to come out as one.
Right so let's take a quick break come back and start talking about our business.
The AWOS Yes this lecture and the previous one were important to explain to you and get the information
gradually from traditional to virtual machines to containers and then talk about containers generally
speaking.
And then to introduce darker and how it works and what are the components what is needed and how it
runs on virtual machines like easy to instances or physical servers or into the cloud.
So in the next one we're start digging into easier itself and understanding more about it which is very
key to passing the exam.
Okay I'll see in the next lecture.
Thank you.