Orchestration Procedures, Attributes and Inventory
Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or
Already have an account? Sign In »
Video Transcription
00:00
>> Hello Cybrarians, and welcome back to
00:00
the Linux Plus course here at Cybrary.
00:00
I'm your instructor Rob Gills,
00:00
and in today's lesson we're going to be discussing
00:00
orchestration procedures and attributes.
00:00
Upon completion of this lesson,
00:00
you're going to be able to understand
00:00
the purpose that procedures,
00:00
attributes, and inventory play in orchestration.
00:00
An orchestration procedure is
00:00
really a set of steps to complete an action,
00:00
and that can be straightforward or it could be
00:00
complex series of actions.
00:00
Now, some examples of
00:00
orchestration procedures
00:00
>> include continuous integration,
00:00
>> which is quickly incorporating
00:00
>> software changes back into
00:00
>> the main software branch using
00:00
something like Git like we saw in the previous lesson,
00:00
and continuous delivery, which
00:00
delivers software on a continuous basis.
00:00
We're making changes to our code,
00:00
we're testing it,
00:00
and then we're pushing it out in production.
00:00
We might also be controlling
00:00
our environment using orchestration procedures,
00:00
ensuring that changes get tested and managed,
00:00
which is known as automated configuration,
00:00
and we might also be deploying or
00:00
defining our environment using code.
00:00
Configuring that with code is
00:00
known as Infrastructure as Code.
00:00
Maybe we can commit changes to our configuration for
00:00
our infrastructure and put that
00:00
into a version control system like Git,
00:00
and then we can deploy that information
00:00
on an ongoing, consistent, repeatable basis.
00:00
We might also be monitoring the environment
00:00
using agent or agentless monitoring,
00:00
like we talked about in the previous lesson as well.
00:00
Now, an attribute is a parameter that's used to
00:00
customize and define orchestration procedures,
00:00
and so this is vague,
00:00
but let's talk about some examples of attributes.
00:00
Well, we might have an environment that it
00:00
specifies specific components and applications.
00:00
We say, oh, we have this environment,
00:00
it needs to have this many machines running.
00:00
The front end, maybe we have
00:00
a couple of back-end servers running the database,
00:00
and these are the various applications and
00:00
packages that we need to
00:00
have installed in this environment.
00:00
We might also have a configuration
00:00
attribute that indicates,
00:00
we need these machines to be this big.
00:00
They need to have this much memory and this many CPUs,
00:00
and they need to be configured with
00:00
these settings in the LS with the application.
00:00
Then we have a version attribute,
00:00
which basically could say, for this version,
00:00
we're going to have the environment
00:00
or the configuration set
00:00
this way and then in
00:00
the next version it might be something else.
00:00
That version attribute can change the environment or
00:00
configuration independently as you
00:00
go through and set up things.
00:00
Also, it's critically important that
00:00
orchestration has an accurate view of the environment,
00:00
and this is known as keeping inventory.
00:00
Orchestration inventory processes can
00:00
be tasked with a lot of different things.
00:00
They're generally storing information on things like
00:00
virtual machines and hypervisors, networks,
00:00
applications and operating systems,
00:00
the hardware itself, as well as software licenses.
00:00
There are a bunch of different products
00:00
that can be used to gather inventories.
00:00
Some of those include, Ansible,
00:00
which is a configuration management tool.
00:00
Another configuration management and
00:00
maintenance tool is known as Chef.
00:00
Puppet, is a configuration management
00:00
and configuration consistency tool
00:00
because it has things in place to make
00:00
sure that your configuration doesn't drift.
00:00
Then Terraform is a provisioning tool for
00:00
infrastructure and all of
00:00
these can do inventory gathering.
00:00
With that, in this lesson,
00:00
we covered the purpose that procedures,
00:00
attributes, and inventory play in orchestration.
00:00
Thanks so much for being here and I look
00:00
forward to seeing you in the next lesson.
Up Next
Instructed By
Similar Content
