WEBVTT

1
00:00.000 --> 00:02.960
So we got all the feedback that's out of the way and understanding the

2
00:02.960 --> 00:06.600
difference between software platform and infrastructure as a service.

3
00:06.600 --> 00:10.120
And that brings us to this portion of the skill where I actually given some

4
00:10.120 --> 00:14.360
examples of infrastructure as a service inside of that Cisco world.

5
00:14.360 --> 00:17.790
And I wanted to show you a couple of things, but also showing you the

6
00:17.790 --> 00:21.440
difference between software platform and infrastructure.

7
00:21.440 --> 00:25.440
And for that example, we're going to be walking back over to our sandbox

8
00:25.440 --> 00:28.120
environment on the actual Cisco sandbox devnet.

9
00:28.560 --> 00:32.800
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

9
00:28.560 --> 00:32.800
And I'm showing you here that this should look familiar because in last skill,

10
00:32.800 --> 00:38.260
we went through and selected our catalyst center and launched launched it for

11
00:38.260 --> 00:40.720
our actual test environment.

12
00:40.720 --> 00:45.490
The many different options that you have in here to be able to go through and

13
00:45.490 --> 00:50.430
crank up and do testing on to be able to see if you can actually go through and

14
00:50.430 --> 00:54.000
get familiar, get some better practice.

15
00:54.000 --> 00:58.470
And all sorts of different things you can do in here shows us that we can

16
00:58.470 --> 01:03.450
utilize this right here as platform as a service because everything is being
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

16
00:58.470 --> 01:03.450
utilize this right here as platform as a service because everything is being

17
01:03.450 --> 01:06.240
hosted from beyond the application.

18
01:06.240 --> 01:09.810
See, we have the application where I'm able to access it and actually control

19
01:09.810 --> 01:12.400
the people in data that's within that environment.

20
01:12.400 --> 01:17.900
But when we fire this up and look inside of our actual catalyst center

21
01:17.900 --> 01:21.120
environment that we have in practice,

22
01:21.840 --> 01:25.900
the infrastructure as a service portion would be that we have control over the

23
01:25.900 --> 01:31.660
actual virtual machines by way of operating system and going into the actual
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
01:25.900 --> 01:31.660
actual virtual machines by way of operating system and going into the actual

24
01:31.660 --> 01:35.040
operating system itself and making configuration changes.

25
01:35.040 --> 01:39.400
Now, yes, all the hardware still belongs to the actual provider, but in this

26
01:39.400 --> 01:43.960
example right here, this would be a classic infrastructure as a service for

27
01:43.960 --> 01:45.680
that Cisco environment.

28
01:46.400 --> 01:51.310
We only have one site for this because we're in DevNet sandbox mode, but in

29
01:51.310 --> 01:55.450
real world, we would actually have multiple different sites that would be divv

30
01:55.450 --> 01:58.000
ied up in here that we would actually have access into.

31
01:58.000 --> 02:02.110
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

31
01:58.000 --> 02:02.110
And the reason I brought up the whole any connect and making sure that we can

32
02:02.110 --> 02:06.800
log into our Cisco DevNet is because in infrastructure as a service for Cisco

33
02:06.800 --> 02:11.170
or any infrastructure as a service for that matter, we would actually have to

34
02:11.170 --> 02:15.950
use that VPN connection to be able to get inside the actual infrastructure

35
02:15.950 --> 02:16.320
itself.

36
02:16.320 --> 02:22.000
To the actual hardware that's hosting our virtualization.

37
02:22.000 --> 02:26.070
We can't just go in and make changes to the operating system over the network

38
02:26.070 --> 02:30.160
unless it's configured like that and you shouldn't for reasons.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
02:26.070 --> 02:30.160
unless it's configured like that and you shouldn't for reasons.

39
02:30.160 --> 02:35.120
We actually will cover security here just to manage, but we want to go in and

40
02:35.120 --> 02:40.520
be able to access this in the most secure way possible and not have this opened

41
02:40.520 --> 02:41.760
up to the general public.

42
02:42.000 --> 02:45.960
See, when the public interfaces with this, there want to be looking at it from

43
02:45.960 --> 02:50.610
a user end. So think like your basic operating system and different Cisco

44
02:50.610 --> 02:53.920
components that like we can access as a user.

45
02:53.920 --> 02:57.090
Sometimes it's actually good to go out and sit with the user and see what they

46
02:57.090 --> 03:00.400
're looking at because it's completely different from our perspective.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:57.090 --> 03:00.400
're looking at because it's completely different from our perspective.

47
03:00.400 --> 03:04.940
Now in this environment that we have as an example right here, we have an iSer

48
03:04.940 --> 03:08.960
ver, DevBox, DNA Center and our Cisco modeling labs.

49
03:08.960 --> 03:13.480
Now do keep in mind that the modeling labs is the representation of the actual

50
03:13.480 --> 03:17.630
infrastructure because if we go into it and we would actually have to crank

51
03:17.630 --> 03:19.760
this up on the actual website itself.

52
03:19.760 --> 03:27.100
So you go into the actual information itself, you go to the modeling labs. Well

53
03:27.100 --> 03:29.520
, you can actually just click on the IP address.

54
03:29.520 --> 03:32.720
Open up another tab and just paste that in there.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
03:29.520 --> 03:32.720
Open up another tab and just paste that in there.

55
03:33.920 --> 03:38.470
And you will come across this because you don't have the SSL certificates for

56
03:38.470 --> 03:41.680
it or TLS stored as a root certificate on your system.

57
03:41.680 --> 03:44.080
If you trust it, you trust it. If you don't, you don't.

58
03:44.080 --> 03:49.190
And we will log into our modeling lab using the correct credentials that I

59
03:49.190 --> 03:50.880
totally didn't mess up in front of you.

60
03:50.880 --> 03:55.240
We're going to make sure that we see our admin go lab. That's the one in there

61
03:55.240 --> 03:55.760
by default.

62
03:55.760 --> 03:59.520
And this is where we actually cross into that infrastructure as a service

63
03:59.520 --> 04:02.720
environment for representation.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
03:59.520 --> 04:02.720
environment for representation.

64
04:03.040 --> 04:06.160
See, we would actually look at this, go inside of it.

65
04:06.160 --> 04:07.440
There we go.

66
04:07.440 --> 04:12.930
And this is all the physical hardware that's controlled by the actual provider

67
04:12.930 --> 04:19.720
to include the actual sandbox switch, which we can go in and look at all the

68
04:19.720 --> 04:21.120
settings and configurations on.

69
04:21.120 --> 04:24.760
Now, this doesn't mean that we can actually go in and make changes to it. But

70
04:24.760 --> 04:27.520
what it does mean is that we can see it and have more.

71
04:28.240 --> 04:33.740
Scan access to be able to look for vulnerabilities, do risk assessments and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
04:28.240 --> 04:33.740
Scan access to be able to look for vulnerabilities, do risk assessments and

72
04:33.740 --> 04:37.540
also see if there's anything that we need to make changes to as far as

73
04:37.540 --> 04:41.040
configurations go that we can send back to the actual provider.

74
04:41.040 --> 04:47.360
When we take a look at our map overall in a live environment, we're going to be

75
04:47.360 --> 04:51.220
adding in actual workstations and that can be done here in our sandbox

76
04:51.220 --> 04:54.800
environment, where we can just simply click add nodes.

77
04:55.200 --> 04:59.680
And we can see what different options we have in here. Now, if you go and add a

78
04:59.680 --> 05:05.250
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

78
04:59.680 --> 05:05.250
desktop, it's not going to let you go in and say what operating system and, you

79
05:05.250 --> 05:07.840
know, how, how you want to be able to configure that.

80
05:07.840 --> 05:14.770
What it does do is give you the real world visualization of information that's

81
05:14.770 --> 05:17.840
provided by this actual desktop.

82
05:17.840 --> 05:20.390
And I'm having to zoom in for you real quick and just make sure you can see

83
05:20.390 --> 05:23.850
this. You'll see a little bit of inception as well. And I apologize, but you

84
05:23.850 --> 05:30.800
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

84
05:23.850 --> 05:30.800
see that this is alpine linux 512 megs and RAM, one CPU and 16 gig route disk

85
05:30.800 --> 05:31.280
size.

86
05:31.280 --> 05:35.800
The reason I bring that up is because an infrastructure is a service. We have

87
05:35.800 --> 05:41.000
the ability to maintain oversight on that operating system and maintain the

88
05:41.000 --> 05:43.120
license for it and deploy them.

89
05:43.360 --> 05:47.570
But we actually have to get with the actual provider to expand those resources

90
05:47.570 --> 05:51.400
if we need more. And that's why I wanted to point that out at the beginning of

91
05:51.400 --> 05:53.440
this because in platform as a service.

92
05:53.440 --> 05:57.880
This is all handled and maintained by the provider. We get into more

93
05:57.880 --> 06:03.710
administrative tasks and responsibilities when we cross over an infrastructure
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
05:57.880 --> 06:03.710
administrative tasks and responsibilities when we cross over an infrastructure

94
06:03.710 --> 06:08.320
because we have to maintain oversight on resource utilization.