1

00:00:00,350 --> 00:00:05,810

In this demo, we will see how to provision the victims required to set up a single master to worker



2

00:00:05,820 --> 00:00:13,080

node cabernets cluster using virtual box and Vikrant on our local system as a prerequisite.



3

00:00:13,200 --> 00:00:16,470

You must have virtual box and vagrant installed.



4

00:00:17,490 --> 00:00:22,860

We will use a vagrant file to automate the provisioning of the virtual machines required for the master



5

00:00:22,860 --> 00:00:23,720

and worker notes.



6

00:00:24,630 --> 00:00:29,070

The vagrant file is located in the GitHub repository associated with this course.



7

00:00:29,730 --> 00:00:35,940

So we clone this repository first by copying the repository you are all and running the clone command



8

00:00:35,970 --> 00:00:37,020

followed by the.



9

00:00:37,050 --> 00:00:38,430

You are to the repository.



10

00:00:42,870 --> 00:00:45,780

Once cloned c.D into the cloned directory.



11

00:00:48,430 --> 00:00:51,490

Review the vagrant file to make sure it has the right settings.



12

00:00:53,220 --> 00:00:57,870

We see that we have configured the number of Masser nodes to one and worker nodes to two.



13

00:00:58,410 --> 00:01:00,180

And the IP network range is one.



14

00:01:00,180 --> 00:01:02,340

I need to load 168 dot 56.



15

00:01:03,820 --> 00:01:08,500

This means that when the victims are created, they are going to get IP addresses within this range.



16

00:01:09,640 --> 00:01:10,510

So that looks good.



17

00:01:11,050 --> 00:01:16,510

We come out of the file and we run the background status command to check the status of the V.



18

00:01:17,050 --> 00:01:21,720

And since we have not created them yet, they are in a not created state.



19

00:01:22,480 --> 00:01:25,240

But we can see the names of machines that it would create.



20

00:01:25,270 --> 00:01:30,970

Once we provision, they will be named Cube Master Cube, not zero one and Cube notes zero two.



21

00:01:31,750 --> 00:01:34,900

We will now run the vagrant up command to provision the VMC.



22

00:01:37,270 --> 00:01:40,270

It uses the Ubuntu Bionic 64 base images.



23

00:01:40,920 --> 00:01:44,350

The base image is pulled and the beams are being provisioned.



24

00:01:44,770 --> 00:01:50,800

Now, depending on your network bandwidth and your hosts resources, this may take some time.



25

00:01:51,130 --> 00:01:52,150

So let's wait.



26

00:01:53,420 --> 00:01:58,470

Now, first, the acute masteries provisioned and then the cube node zero one is provisioned.



27

00:01:58,830 --> 00:02:01,680

And finally, Cube notes, Rotu gets provisioned.



28

00:02:11,410 --> 00:02:17,740

We now check the status again and see that it's all in our running state to access one of these system,



29

00:02:18,160 --> 00:02:19,960

use the vagrant as a search command.



30

00:02:20,020 --> 00:02:25,930

So we run the vagrant as a sage cube master command to assist into the master node.



31

00:02:26,470 --> 00:02:27,760

So we are in the master node.



32

00:02:28,390 --> 00:02:30,890

We run just any command to make sure it's working.



33

00:02:30,910 --> 00:02:35,740

So we were on the uptime command to check if the commands are working.



34

00:02:36,220 --> 00:02:42,850

And then we will now log out of the system and test SSL connectivity to the other nodes, not zero one.



35

00:02:48,530 --> 00:02:50,850

And followed by No one zero to.



36

00:02:55,370 --> 00:02:56,240

So they look good.



37

00:02:57,300 --> 00:02:58,700

Now we're all set.



38

00:02:58,760 --> 00:03:04,490

And in the next video, we will proceed with bootstrapping a cluster using Cubitt E.M..