WEBVTT

1
00:00.000 --> 00:04.480
So as we check our progress here with the automation wizard, we are still right

2
00:04.480 --> 00:05.360
here at the step of

3
00:05.360 --> 00:11.040
activate TKG, supervisor cluster, and it has been sitting there for 25 minutes.

4
00:11.040 --> 00:12.240
Now it's not

5
00:12.240 --> 00:15.850
stalled here because these messages are changing periodically regarding what's

6
00:15.850 --> 00:17.280
currently going on.

7
00:17.280 --> 00:20.830
So at this point, as long as these messages are changing, we can also go ahead

8
00:20.830 --> 00:21.440
and verify

9
00:21.440 --> 00:24.990
back at the vSphere client, we can go to the hamburger menu here in the vSphere

10
00:24.990 --> 00:25.440
client

11
00:25.440 --> 00:29.280
and go to workload management. And although it hasn't yet created a namespace,

12
00:29.280 --> 00:29.920
we click here on

13
00:29.920 --> 00:35.030
supervisors is currently in the process of deploying our supervisors as part of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.920 --> 00:35.030
supervisors is currently in the process of deploying our supervisors as part of

14
00:35.030 --> 00:36.000
Kubernetes.

15
00:36.000 --> 00:40.270
So that shows right here that is currently configuring says at work. So back at

16
00:40.270 --> 00:41.360
the automation wizard

17
00:41.360 --> 00:46.670
here, we'll continue to let that crank away. And it is done. So this whole

18
00:46.670 --> 00:47.920
process from start

19
00:47.920 --> 00:52.630
to finish here in this last run that we did took about an hour and 10 minutes

20
00:52.630 --> 00:54.000
to complete. So I'm

21
00:54.000 --> 00:57.900
going to go ahead and download the yaml file for this nap three instance. So I

22
00:57.900 --> 00:59.040
have a local copy of

23
00:59.040 --> 01:03.030
it. If I need it, it'll download my downloads folder. And then we'll go ahead
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:59.040 --> 01:03.030
it. If I need it, it'll download my downloads folder. And then we'll go ahead

24
01:03.030 --> 01:04.480
and click on next.

25
01:04.480 --> 01:08.080
So at this point, we're in this stage of the game to deploy the actual NSX

26
01:08.080 --> 01:09.680
application platform

27
01:09.680 --> 01:12.900
itself. So to do that, we're going to click right here on start nap deployment.

28
01:12.900 --> 01:13.360
And actually,

29
01:13.360 --> 01:17.500
before we click on the start here, let's also take a look at vSphere in the v

30
01:17.500 --> 01:18.480
Sphere client

31
01:18.480 --> 01:23.250
and see what it deployed for us as part of this previous step with the Kubernet

32
01:23.250 --> 01:23.680
es.

33
01:23.680 --> 01:27.200
So back here in the vSphere cluster, I currently have in my host and clusters

34
01:27.200 --> 01:27.920
view this new

35
01:28.480 --> 01:32.420
section called namespaces dash and s dash nap three, that was the name of our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:28.480 --> 01:32.420
section called namespaces dash and s dash nap three, that was the name of our

36
01:32.420 --> 01:33.680
instance. And then

37
01:33.680 --> 01:38.420
if we go to the VMs and templates view here, and we expand that namespace, and

38
01:38.420 --> 01:38.960
if we continue

39
01:38.960 --> 01:43.160
opening this up, I've got a worker node and a controller node as part of this

40
01:43.160 --> 01:44.560
nap three instance.

41
01:44.560 --> 01:48.790
And so all that was deployed through the automation wizard. So if we go to the

42
01:48.790 --> 01:49.920
hamburger menu now,

43
01:49.920 --> 01:54.470
on the top, I'm go to workload management. Here, if we click on namespaces, we

44
01:54.470 --> 01:55.440
have our namespace

45
01:55.440 --> 02:00.430
called nap and s nap three right there. If we click on supervisors, and that's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
01:55.440 --> 02:00.430
called nap and s nap three right there. If we click on supervisors, and that's

46
02:00.430 --> 02:01.600
the name of the cluster

47
02:01.600 --> 02:05.210
where it deployed the supervisors here can confirm the details about the

48
02:05.210 --> 02:06.480
version that's being run,

49
02:06.480 --> 02:10.960
and the IP address for the control plane node. And if there are any issues or

50
02:10.960 --> 02:11.760
problems,

51
02:11.760 --> 02:15.450
we could also click here on events, take a look at those details, but

52
02:15.450 --> 02:16.320
everything looks really,

53
02:16.320 --> 02:20.230
really good here. So I go ahead and go back to the inventory view here in the v

54
02:20.230 --> 02:21.040
Sphere client.

55
02:21.040 --> 02:25.480
And let's go back to the NSX manager and continue with the nap deployment. So

56
02:25.480 --> 02:27.200
back at the NSX manager,

57
02:27.200 --> 02:32.450
we're in the final stage here to actually deploy the NSX application platform.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:27.200 --> 02:32.450
we're in the final stage here to actually deploy the NSX application platform.

58
02:32.450 --> 02:32.960
So to do that,

59
02:32.960 --> 02:37.150
we'll simply click down here on start nap deployment right there. And away it

60
02:37.150 --> 02:37.840
goes. And

61
02:37.840 --> 02:42.310
presuming everything is successful here when it's done, we'll have a

62
02:42.310 --> 02:44.160
functioning, working,

63
02:44.160 --> 02:48.810
NSX application platform that we can start using in conjunction with our NSX

64
02:48.810 --> 02:49.920
environment.

65
02:49.920 --> 02:54.080
So we'll go ahead and give this as long as it takes to go ahead and complete,

66
02:54.080 --> 02:58.420
or if it has issues or problems, we'll troubleshoot that wherever it stops. So

67
02:58.420 --> 02:59.120
at the moment,

68
02:59.120 --> 03:02.010
it looks like it's in pretty good shape. Now what we could also do, let me go
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
02:59.120 --> 03:02.010
it looks like it's in pretty good shape. Now what we could also do, let me go

69
03:02.010 --> 03:03.360
ahead and just duplicate

70
03:03.360 --> 03:07.450
this tab here. So this is back at the NSX manager in a separate tab. If we

71
03:07.450 --> 03:08.880
click here on the NSX

72
03:08.880 --> 03:12.580
application platform, it's also going to show us right here, its current

73
03:12.580 --> 03:13.760
progress in deploying

74
03:13.760 --> 03:17.550
the platform itself. So this is the automation tool in the background that's

75
03:17.550 --> 03:19.120
kicked off this process.

76
03:19.120 --> 03:23.720
So this is the view from the tab for the NSX application platform as it's being

77
03:23.720 --> 03:24.240
deployed.

78
03:24.240 --> 03:29.100
And this is the view from the plugin, the nap automation plugin, which is also

79
03:29.100 --> 03:29.360
showing us

80
03:29.360 --> 03:32.880
right here the status regarding the nap deployment. So currently it's at 10%.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
03:29.360 --> 03:32.880
right here the status regarding the nap deployment. So currently it's at 10%.

81
03:32.880 --> 03:34.480
And either way, whether

82
03:34.480 --> 03:38.690
we watch it complete here, or if we watch it complete here, either way, if it

83
03:38.690 --> 03:39.680
finishes all the way

84
03:39.680 --> 03:44.200
through, once it's done, we'll have a beautiful NSX application platform that

85
03:44.200 --> 03:45.040
we can then go

86
03:45.040 --> 03:48.770
ahead and start using. So once again, I'm going to give this as long as it

87
03:48.770 --> 03:50.080
takes to complete.

88
03:50.080 --> 03:56.160
All right, so it is now at 30%. So that is making good progress. And if we went

89
03:56.160 --> 03:56.960
back over to the

90
03:56.960 --> 04:01.050
wizard over here, back at the other interface, here it shows that similar
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
03:56.960 --> 04:01.050
wizard over here, back at the other interface, here it shows that similar

91
04:01.050 --> 04:02.320
information about where

92
04:02.320 --> 04:06.170
it is in the process of deploying nap. And if it gets stopped by an error, that

93
04:06.170 --> 04:06.800
error will show up

94
04:06.800 --> 04:10.850
here. And the error would also be reflected here as well. Again, if it has a

95
04:10.850 --> 04:12.320
problem or an issue

96
04:12.320 --> 04:16.770
as it's deploying the nap. All right, so now it's at 40%. Again, that

97
04:16.770 --> 04:18.240
information is here

98
04:18.240 --> 04:22.560
at the NSX application platform as it's being deployed. And it's also shown

99
04:22.560 --> 04:23.760
here in the wizard

100
04:23.760 --> 04:27.870
as well as part of the automation. So again, we'll let that continue. So for

101
04:27.870 --> 04:28.240
the actual

102
04:28.240 --> 04:32.450
installing platform part that took about 30 minutes to complete, and it's now
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
04:28.240 --> 04:32.450
installing platform part that took about 30 minutes to complete, and it's now

103
04:32.450 --> 04:33.520
on to registering the

104
04:33.520 --> 04:37.210
platform. So here's look at that same information from the perspective of the

105
04:37.210 --> 04:38.480
automation platform.

106
04:38.480 --> 04:42.160
So once again, it's about 70%. All right, so that's the step about registering

107
04:42.160 --> 04:42.960
the platform took

108
04:42.960 --> 04:47.200
about five to six minutes. And now it's on to installing metrics. All right,

109
04:47.200 --> 04:48.080
and it is done.

110
04:48.080 --> 04:53.000
So here in the wizard, it says nap deployment is completed, fantastic. And if

111
04:53.000 --> 04:53.760
we jump over here

112
04:53.760 --> 04:57.640
to the NSX application platform, looks like I need to refresh this page, so I

113
04:57.640 --> 04:58.800
'll click right here

114
04:58.800 --> 05:04.890
on try again. And indeed, we have the NSX application platform, which is ready
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

114
04:58.800 --> 05:04.890
on try again. And indeed, we have the NSX application platform, which is ready

115
05:04.890 --> 05:05.760
to rock.

116
05:05.760 --> 05:10.640
So now that we have the NSX application platform available to us, if we scroll

117
05:10.640 --> 05:11.680
down, we can then

118
05:11.680 --> 05:16.250
start to enable many of its features, including NSX intelligence, NSX network

119
05:16.250 --> 05:17.600
detection and response,

120
05:17.600 --> 05:22.240
and NSX malware prevention, which will do those in a separate set of videos.

121
05:22.240 --> 05:22.640
But for now, I just

122
05:22.640 --> 05:27.790
want to walk through the deployment using the nap automation. And as a reminder

123
05:27.790 --> 05:28.560
of all the cool

124
05:28.560 --> 05:32.180
stuff it just did for us, it is these two stages that it went completely
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
05:28.560 --> 05:32.180
stuff it just did for us, it is these two stages that it went completely

125
05:32.180 --> 05:33.280
through until finally,

126
05:33.280 --> 05:38.080
we have a functional working NSX application platform that we can now use.

127
05:38.080 --> 05:48.080
[BLANK_AUDIO]