WEBVTT

1
00:00.000 --> 00:03.520
So to begin with, let's take a look at this document from VMware called Deploy

2
00:03.520 --> 00:03.800
ing and

3
00:03.800 --> 00:07.160
managing the VMware NSX application platform.

4
00:07.160 --> 00:10.260
I just want to give you a peek at some of the prerequisites.

5
00:10.260 --> 00:13.550
So if we jump over to prerequisites here, we have versioning issues that we

6
00:13.550 --> 00:13.980
need to

7
00:13.980 --> 00:15.600
be aware of once we get to that point.

8
00:15.600 --> 00:20.100
If we continue to scroll down here, we have licenses that are required and a

9
00:20.100 --> 00:20.480
great way

10
00:20.480 --> 00:24.920
to get the licenses in a lab environment is to simply use VMUG Advantage.

11
00:24.920 --> 00:29.920
If you join that for like $200 a year, they'll give you EVAL license for many

12
00:29.920 --> 00:30.760
of the VMware
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:29.920 --> 00:30.760
of the VMware

13
00:30.760 --> 00:33.240
products including NSX.

14
00:33.240 --> 00:36.200
If we continue to scroll down, we need a Kubernetes cluster.

15
00:36.200 --> 00:39.790
Again, once again, we can use the automation tool to assist us in deploying

16
00:39.790 --> 00:40.280
that.

17
00:40.280 --> 00:43.630
Once we have the network in place, there's a requirement for internet access to

18
00:43.630 --> 00:44.080
download

19
00:44.080 --> 00:48.110
some content from VMware and also as you scroll down some requirements for

20
00:48.110 --> 00:49.120
fully qualified

21
00:49.120 --> 00:50.320
domain names.

22
00:50.320 --> 00:52.890
Specifically two of them that we're going to need, we're also going to need

23
00:52.890 --> 00:53.480
some IP address

24
00:53.480 --> 00:58.130
spaces to play with and ranges of addresses in the IP address spaces that we

25
00:58.130 --> 00:58.800
can use and

26
00:58.800 --> 01:01.910
then making sure from a firewall perspective that we're permitting that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
00:58.800 --> 01:01.910
then making sure from a firewall perspective that we're permitting that

27
01:01.910 --> 01:02.920
protocols and ports

28
01:02.920 --> 01:07.370
needed between all the devices involved as part of the NSX application platform

29
01:07.370 --> 01:07.640
.

30
01:07.640 --> 01:11.220
And as we continue to scroll down, it talks about system requirements and there

31
01:11.220 --> 01:11.600
's also

32
01:11.600 --> 01:16.700
an option to deploy the NSX application appliance using an EVAL mode that is

33
01:16.700 --> 01:17.880
going to not have

34
01:17.880 --> 01:22.010
to require all the individual VMs and resources that you'd want in a production

35
01:22.010 --> 01:23.000
environment.

36
01:23.000 --> 01:25.410
So all of this is going to be applicable at the point where we're going to go

37
01:25.410 --> 01:25.800
ahead and

38
01:25.800 --> 01:31.080
implement the Kubernetes cluster and then the NSX application platform on top
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:25.800 --> 01:31.080
implement the Kubernetes cluster and then the NSX application platform on top

39
01:31.080 --> 01:31.880
of that.

40
01:31.880 --> 01:35.700
So here it's referring to the evaluation form factor which in a lab environment

41
01:35.700 --> 01:36.160
you can

42
01:36.160 --> 01:39.480
get away with but again in a production environment, you'd want to not use that

43
01:39.480 --> 01:39.720
.

44
01:39.720 --> 01:44.170
You'd want to use all the resources required including reserving resources for

45
01:44.170 --> 01:44.640
the VMs

46
01:44.640 --> 01:45.640
involved.

47
01:45.640 --> 01:49.100
Also as part of deploying the NSX application platform, there is a load bal

48
01:49.100 --> 01:49.920
ancer that's going

49
01:49.920 --> 01:53.920
to be deployed in conjunction with the Kubernetes cluster.

50
01:53.920 --> 01:57.530
As we continue to scroll down, we're going to be using the Docker images and

51
01:57.530 --> 01:58.240
Helm charts

52
01:58.240 --> 02:00.840
from a public repository from VMware.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
01:58.240 --> 02:00.840
from a public repository from VMware.

53
02:00.840 --> 02:03.240
So we'll need to make sure we have internet access.

54
02:03.240 --> 02:06.150
And then after all those prereqs we've looked at, it's then getting to the

55
02:06.150 --> 02:06.680
point where

56
02:06.680 --> 02:11.310
we can deploy the NSX application platform on top of our Kubernetes environment

57
02:11.310 --> 02:11.440
.

58
02:11.440 --> 02:14.570
So the reason I'm talking about these prerequisites on the front end is because

59
02:14.570 --> 02:15.440
if we don't have

60
02:15.440 --> 02:19.940
a network on the back end that's prepared to support that environment, it is

61
02:19.940 --> 02:20.680
going to

62
02:20.680 --> 02:21.680
fail.

63
02:21.680 --> 02:23.160
So in the next video, here's what I propose we do.

64
02:23.160 --> 02:27.310
Let's spend a few moments together and lay out a topology and what we plan to

65
02:27.310 --> 02:27.840
use for

66
02:27.840 --> 02:32.210
things like internet access, DNS, which VLANs we're going to be using as part
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
02:27.840 --> 02:32.210
things like internet access, DNS, which VLANs we're going to be using as part

67
02:32.210 --> 02:32.920
of our game

68
02:32.920 --> 02:33.920
plan.

69
02:33.920 --> 02:37.200
And then once we have that in place, we then proceed to implement that with a

70
02:37.200 --> 02:37.800
combination

71
02:37.800 --> 02:42.450
of VLANs on our physical network as well as vSphere with the appropriate poor

72
02:42.450 --> 02:43.000
groups

73
02:43.000 --> 02:45.320
and so forth to support it as well.

74
02:45.320 --> 02:48.980
So also you my friend in the next video as we put a topology together as part

75
02:48.980 --> 02:49.640
of our game

76
02:49.640 --> 02:49.920
plan.