So we introduced everything and as far as infrastructure as they serve is in
the basic concepts of what is all involved.
In this particular video, I kind of want to dive more into the actual
responsibilities that we mentioned previously
and make sure that we have a firm understanding the split between our
responsibility as a customer and the provider's responsibilities is maintaining
the actual infrastructure.
So as we take a look at our actual handy-dandy responsibility chart, we can see
a lot of the cloud infrastructure as a service is split up more in our favor WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
a lot of the cloud infrastructure as a service is split up more in our favor
this time.
But this gives us an actual advantage over software as a service and platform
as a service.
As organizational admins, we can monitor usage to identify resource utilization
.
And this may be for things like cost to the actual organization itself, but
less to do with cost in this particular skill, we're more focused on actual
resources.
If we look at the provider's responsibility, they cover the hypervisor, server, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
If we look at the provider's responsibility, they cover the hypervisor, server,
storage, and physical network.
And this covers the CPUs, the RAM, the storage, etc.
Whether it be physical network being expanded or even decreased in some cases
based on a site shutting down or whatnot.
We can actually go through and monitor everything in more detail than we can if
we were in a platform or software as a service.
Because in our responsibility, let's just use virtual network and operating WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Because in our responsibility, let's just use virtual network and operating
system as an example. We can identify if we need additional nodes to be able to
support the load balancing for some of the servers we have in that virtual
network or operating system portion of our responsibility.
And specifically with the actual virtual network, we can identify if we need
more ingress and egress points for that load balancing connection for the
actual clients utilizing our services.
As a solid example, we may have a server that's in charge of processing
financial information and doing all the purchasing for services. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
financial information and doing all the purchasing for services.
And if that server for whatever reason is being tapped out because it doesn't
have enough storage to store all the records or there's not enough RAM on it to
be able to make it as quickly as possible within reason.
We can make that request to the actual fighter to say add more physical
components to make sure that we are getting the biggest bang for our buck.
Now this also goes into understanding that because of this, the responsibility WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now this also goes into understanding that because of this, the responsibility
on us to be able to maintain different aspects of our responsibility portion
increases.
Because just as an example inside of operating system in platform or software
as a service, the license scenes for actual operating systems is held to the
actual provider.
Now yes, that cost is set to us as the actual client and for us utilizing those
different components.
But when we get into infrastructure as a service and we're putting more servers
out there, we're adding more clients, that directly falls on us and is a budget WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
out there, we're adding more clients, that directly falls on us and is a budget
ary measure that we have to keep a firm eye on.
We'll see more of this inside of a couple of videos later on in the skill as we
start diving into the different components and comparing from the last skill.
Hopefully this looks a little bit familiar to you because this was in the last
skill where we did our catalyst center connection and modeling out the platform
as a service.
I bring this up because in the platform as a service, these servers that you WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I bring this up because in the platform as a service, these servers that you
see here that we connected to were maintained by the actual infrastructure and
the provider's responsibility.
Now that we've taken on more responsibility in our role, these servers are
going to be maintained by us, even though the physical hardware is still hosted
by the provider.
Now this means that as we're working throughout our network and providing those
services in the Cisco environment, we have to monitor these and make sure that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
services in the Cisco environment, we have to monitor these and make sure that
their resources are within spec or if we need to request more or reutilize them
somewhere else or how that agreement is with the actual infrastructure provider
.
So we maintain the licensee on these actual servers from an operating system
standpoint instead of just an actual application or how many users and how much
data that we're going to be stored within our actual environment.
If in this infrastructure right here, we said we wanted to add let's say WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
If in this infrastructure right here, we said we wanted to add let's say
another modeling lab server to be able to represent the different network
devices and throw up a different site somewhere else.
We would actually have to go through and purchase that license and stand up
that actual server from the operating system level within the actual virtual
ization modeling, whether it be type one or type two.
Now it's probably going to be type one because if we look in the actual
providers responsibilities, we can see hypervisor. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
providers responsibilities, we can see hypervisor.
And again, if you follow that link above where we go into the intro to virtual
ization here on CBT nuggets, that'll bring you more of a clearer picture of how
that's actually modeled out and provided to actual clients for use.