So we got all the feedback that's out of the way and understanding the
difference between software platform and infrastructure as a service.
And that brings us to this portion of the skill where I actually given some
examples of infrastructure as a service inside of that Cisco world.
And I wanted to show you a couple of things, but also showing you the
difference between software platform and infrastructure.
And for that example, we're going to be walking back over to our sandbox
environment on the actual Cisco sandbox devnet.
And I'm showing you here that this should look familiar because in last skill, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And I'm showing you here that this should look familiar because in last skill,
we went through and selected our catalyst center and launched launched it for
our actual test environment.
The many different options that you have in here to be able to go through and
crank up and do testing on to be able to see if you can actually go through and
get familiar, get some better practice.
And all sorts of different things you can do in here shows us that we can
utilize this right here as platform as a service because everything is being WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
utilize this right here as platform as a service because everything is being
hosted from beyond the application.
See, we have the application where I'm able to access it and actually control
the people in data that's within that environment.
But when we fire this up and look inside of our actual catalyst center
environment that we have in practice,
the infrastructure as a service portion would be that we have control over the
actual virtual machines by way of operating system and going into the actual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
actual virtual machines by way of operating system and going into the actual
operating system itself and making configuration changes.
Now, yes, all the hardware still belongs to the actual provider, but in this
example right here, this would be a classic infrastructure as a service for
that Cisco environment.
We only have one site for this because we're in DevNet sandbox mode, but in
real world, we would actually have multiple different sites that would be divv
ied up in here that we would actually have access into.
And the reason I brought up the whole any connect and making sure that we can WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And the reason I brought up the whole any connect and making sure that we can
log into our Cisco DevNet is because in infrastructure as a service for Cisco
or any infrastructure as a service for that matter, we would actually have to
use that VPN connection to be able to get inside the actual infrastructure
itself.
To the actual hardware that's hosting our virtualization.
We can't just go in and make changes to the operating system over the network
unless it's configured like that and you shouldn't for reasons. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
unless it's configured like that and you shouldn't for reasons.
We actually will cover security here just to manage, but we want to go in and
be able to access this in the most secure way possible and not have this opened
up to the general public.
See, when the public interfaces with this, there want to be looking at it from
a user end. So think like your basic operating system and different Cisco
components that like we can access as a user.
Sometimes it's actually good to go out and sit with the user and see what they
're looking at because it's completely different from our perspective. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
're looking at because it's completely different from our perspective.
Now in this environment that we have as an example right here, we have an iSer
ver, DevBox, DNA Center and our Cisco modeling labs.
Now do keep in mind that the modeling labs is the representation of the actual
infrastructure because if we go into it and we would actually have to crank
this up on the actual website itself.
So you go into the actual information itself, you go to the modeling labs. Well
, you can actually just click on the IP address.
Open up another tab and just paste that in there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Open up another tab and just paste that in there.
And you will come across this because you don't have the SSL certificates for
it or TLS stored as a root certificate on your system.
If you trust it, you trust it. If you don't, you don't.
And we will log into our modeling lab using the correct credentials that I
totally didn't mess up in front of you.
We're going to make sure that we see our admin go lab. That's the one in there
by default.
And this is where we actually cross into that infrastructure as a service
environment for representation. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
environment for representation.
See, we would actually look at this, go inside of it.
There we go.
And this is all the physical hardware that's controlled by the actual provider
to include the actual sandbox switch, which we can go in and look at all the
settings and configurations on.
Now, this doesn't mean that we can actually go in and make changes to it. But
what it does mean is that we can see it and have more.
Scan access to be able to look for vulnerabilities, do risk assessments and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Scan access to be able to look for vulnerabilities, do risk assessments and
also see if there's anything that we need to make changes to as far as
configurations go that we can send back to the actual provider.
When we take a look at our map overall in a live environment, we're going to be
adding in actual workstations and that can be done here in our sandbox
environment, where we can just simply click add nodes.
And we can see what different options we have in here. Now, if you go and add a
desktop, it's not going to let you go in and say what operating system and, you WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
desktop, it's not going to let you go in and say what operating system and, you
know, how, how you want to be able to configure that.
What it does do is give you the real world visualization of information that's
provided by this actual desktop.
And I'm having to zoom in for you real quick and just make sure you can see
this. You'll see a little bit of inception as well. And I apologize, but you
see that this is alpine linux 512 megs and RAM, one CPU and 16 gig route disk WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
see that this is alpine linux 512 megs and RAM, one CPU and 16 gig route disk
size.
The reason I bring that up is because an infrastructure is a service. We have
the ability to maintain oversight on that operating system and maintain the
license for it and deploy them.
But we actually have to get with the actual provider to expand those resources
if we need more. And that's why I wanted to point that out at the beginning of
this because in platform as a service.
This is all handled and maintained by the provider. We get into more
administrative tasks and responsibilities when we cross over an infrastructure WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
administrative tasks and responsibilities when we cross over an infrastructure
because we have to maintain oversight on resource utilization.