Alone will come back with another interesting topic which is inebriates artworks of sorts will help
you deploy and manage your applications on instances.
So let's dive in and find out what works is all about.
Generally speaking any cloud based computing will involve group of resources and if you are talking
about it as a group of resources could include Is it two instances containers.
It could include databases such as RDX or dynamic D-B.
And also as you scale you might want to include features like or services like yes Elby or classical
or balancers to be more specific.
Now as the environment grows how can you manage it.
How can you automate the roll out of application.
How can you do it to meet the roll out the deployment monitoring the unemployment or decommissioning
of applications.
How can you stage an application before you roll it out to ensure that is going to work out perfectly
as you want to be.
How can you get most of the burden of installing and running applications on us off your back so basically
automating that absorbs helps you do that.
And one very important question that might evolve in your on your mind or maybe you would face it in
exam questions and you will be confused between upswings and cloud formation as we know cloud formation
is about automating your whole infrastructure.
So all the services or almost all of them that are included in your infrastructure so that could be
anything could be S-3 could be done and could be RLDS launching is it to instance is launching many
things you could imagine in your infrastructure.
So cloud formation is broad and it's about managing infrastructure as.
But cloud formation is not about focusing on your application monitoring your application deploying
your application giving your statistics out what's going on with your application works.
So absorbance deals with a narrow or a smaller number of services.
We mentioned some or most of them load balancing easy to our D.S. plastic container services but that's
it that's that's the range that it would work with because the focus of Officeworks is not about the
infrastructure or the underlaid.
It's about the many infrastructure that has to do with the application and then money deploying and
monitoring the application.
Please distinguish between a specific focus of ops works and a broad focus of elaboration.
So in addition to creating the instances which is the infrastructure for application and its totally
unnecessary packages deploying the application you typically need a way to distribute applications to
the application servers.
When you roll out when you scale monitor the stacks performance so the collection of servers that run
the application also would like to manage its performance manage security permissions and so on.
So who can help you do all of that absorb so absorb stacks provides a simple and flexible way to create
and manage stacks and applications and the stack is the core component of our ports.
So our stack is what is easy to instance is the logical balancers is that Hobbes's that you are using
and the application thats the stack that we are talking about.
So here is a simple stack in terms of obsolete and are going to explain all of that cookbook depositary
application repository users.
And then you have within it up your ass you have custom the last layer Microsoft Internet Information
Server layer you have a Windows instance and you have the application and that is the OPs or Stex.
So that is one layer or a single layer absorbs stack and we're going to talk about layers cookbooks
all that don't work.
So as an example of where the application typically requires application servers the resellers load
balancers and so on.
So if you want to put that in a graphical depiction you have the users or the application that probably
would be coming through the Internet.
You need an internet facing load balance and you have then the application server you can scale.
And if one is unhealthy it can be removed without affecting the application and the user experience
and behind that will be data which is of course security will be available as well.
Have you discussed before.
So this is collectively called a stack in OPS works.
So an optional stack provides average set of customizable components that you can mix and match to create
a stack that satisfies the application requirements.
They see to instance which is an instance you need to do Michael C. is it large is it small is it extra
large It allows its edge and our DP access to stack instances and resources can be managed only in the
region in which they are created.
And here is an important one probably will highlight that later on.
But when you are creating the stack you will specify the region when you specify the region once it
is created.
You cannot you can not an OT change the region of an existing stack.
Ok so you need to build another one in a different region if you want to play with the resources that
are created in one original point are not available nor can they be cloned into another regional endpoint
so that it created in a region.
You're stuck with that one for that stack.
So we talk about artworks and automation.
What is the tool inherent to that.
Chef Chef is the automation tool used or the application moment and management tool that is used for
AAPS works.
Stex why would we use it because we need to automate it.
So as your environment grow you cannot do it manually.
The management and deployment and you would like to have an automation tool for that and chefe will
be our automation too.
What does it provide.
It provides automated configuration management that enables consistent configurations at Cape chaffe
helps in ensuring that configuration policy is flexible.
The configuration policy to your servers to you are it to instance it is very general testable and human
readable servers menaced by chefe are continuously evaluated against their desired state.
So chef knows it because it has the configuration files or a script or recipes as we explain shortly.
It knows the desired state always will compare what is deployed to the desired state ensure ensuring
that configuration is automatically corrected and configuration changes are universally applied.
When you have a new version of code that is the piece then chef will take care of that.
If there are any changes or discrepancies chef is going to also continuously monitor your application
and find out these errors and correct them for you.
Good books and recipes.
We'll hear about that a lot as.
As long as you are talking about automation and absorbs or chef to a cookbook what is a cookbook.
Now we're talking about a chef the chef needs a kitchen and the kitchen needs cookbooks so the cookbook
is a packaged file that contains configuration information instructions that are called recipes because
in a cookbook The chef will use the cookbook for whatfor recipes recipes a set of one or more instructions
to do what it has to do with an application you would like to roll out the application or like to deploy
it configure it in a certain way and the instructions are written in Ruby language syntax and the instructions
will specify the resources to use and the order in which those resources are applied.
What is it that we're talking about here.
Is it to instance.
No I have now taken you out of it.
Yes you are talking about chef chef cook books and recipes abstracted from whether you are using it
on us or somewhere else.
So here when we talking about resources we're not talking about resources we're talking about Chef resource
and the resource in that chef automation too is about one instruction or one statement that you are
going to use.
One thing you need to keep in mind that Opsware we can automatically run them at the appropriate time
around what Aranda recipes.
And also you can run them manually before we leave chefe completely and go back to artworks then resource
in Sheft terms or resource as used in Schaff is a statement of configuration policy.
In the next lecture we're going to talk about stacks and layers.
So as we saw in the one layer I was drawing that we looked at we call that earlier.
So what is a stack and what is clear is what we will discuss in the next lecture.
I'll see you then.
Thank you.