WEBVTT 00:01.330 --> 00:07.580 In this demo, we're going to install a basic Cabernets cluster using the mini cube utility as part 00:07.580 --> 00:11.210 of this beginner's course to keep things simple and easy. 00:11.270 --> 00:14.000 We will stick to Minie Cube as our lab solution. 00:14.750 --> 00:20.900 We explore additional options of provisioning equipment and this cluster using the cube admin tool in 00:20.930 --> 00:21.980 DC a course. 00:22.610 --> 00:28.490 As for this course, we just want to stick to the very basics and all the basic operations can be performed 00:28.970 --> 00:30.350 on emeny cube cluster. 00:31.010 --> 00:35.500 So we will start at the Cuban ATSDR IO page within this Web site. 00:35.540 --> 00:41.980 Click on the documentation section and navigate two tasks and install tools section. 00:42.770 --> 00:48.470 Now, before installing Mini Cube, we must install the Cube Cuttle utility. 00:48.830 --> 00:54.770 It will be called a Cube Control Cube Cuddle or cube CDL, whatever you prefer. 00:55.570 --> 01:00.050 Now you might hear me mix it up at times, so bear at me on that. 01:00.830 --> 01:07.490 So the cube coro command line tool is what we will use to manage our coordinate its resources and our 01:07.490 --> 01:10.490 cluster after it is set up using mini cube. 01:11.240 --> 01:18.260 Installing the Cube Cuttle utility before installing mini cube will allow Mini Cube to configure the 01:18.350 --> 01:23.000 local utility to work with the cluster when it provisions it. 01:23.480 --> 01:29.390 So the cube coral utility can work with multiple clusters, local or remote clusters. 01:29.570 --> 01:36.170 At the same time, there's a small configuration for it and Mini Q will automatically take care of that 01:36.860 --> 01:37.880 when it starts. 01:38.090 --> 01:43.520 We need provisions, a comprehensive cluster, but that is if you already have the Cape Coral utility 01:43.950 --> 01:44.330 installed. 01:44.390 --> 01:45.260 So that's important. 01:45.920 --> 01:50.240 Now our goal is to set up a cluster on our local machine. 01:50.540 --> 01:53.150 AM on Linux Open two system. 01:53.450 --> 01:58.460 But the same procedure will also work on Windows or Mac operating systems as well. 01:59.050 --> 02:06.890 Now, all the demos and tools that we have throughout this course will work on all operating systems 02:06.920 --> 02:09.030 Linux, Windows or Mac K. 02:09.080 --> 02:15.260 You just need to follow the respective installation procedure for your OS and to start with. 02:15.380 --> 02:22.430 I'm going to install the CUCHILLO utility on my Linux system and we're going to go ahead with the latest 02:22.430 --> 02:22.880 version. 02:22.910 --> 02:29.000 So just copy and paste the command and provided here for downloading the Cube Cuttle Binary. 02:35.350 --> 02:37.900 The binary has now been downloaded. 02:38.080 --> 02:40.740 The next step is to make this command executables. 02:40.740 --> 02:46.630 So I'm going to use the command S.H. Mod plus X to make it executable. 02:47.020 --> 02:52.120 And finally, we're going to move this to a location within the path using a local bin. 03:04.430 --> 03:04.580 OK. 03:04.680 --> 03:10.140 So this way, I'll be able to run this cute cuddle command from anywhere within my system. 03:14.750 --> 03:22.310 So let's run the cardioversion command and you can see that it has installed the one Dort 18 version. 03:25.670 --> 03:30.530 Now, what we just saw was a one way of installing KUB Cuttle utility. 03:30.590 --> 03:32.150 There are other ways to do it. 03:32.630 --> 03:38.870 You can install it using a package managers depending upon the type of distribution or waste distribution 03:38.870 --> 03:39.590 that you are on. 03:40.220 --> 03:45.140 And the documentation associated with these are available here. 03:45.590 --> 03:51.530 So if you scroll down, you will see that there are instructions for installation on Mac OS and there 03:51.530 --> 03:53.000 should be one for Windows as well. 03:53.030 --> 03:59.510 So make sure that you use the appropriate link and setup up cuddle based on the documentation provided. 04:00.590 --> 04:06.560 Now that we have completed the installation of Cube Gödel utility, we can proceed with the installation 04:06.620 --> 04:07.460 of Mini Cube. 04:08.540 --> 04:10.640 Now the first thing that we have to check. 04:11.270 --> 04:17.090 And this goes for all operating systems, Linux, Windows or Mac is to make sure that virtualization 04:17.150 --> 04:22.000 is enabled for your laptop or desktop wherever you're setting up this lab. 04:22.700 --> 04:31.100 So one of the easy ways to make sure that virtualization is enabled on Linux is to grep for the Remax 04:31.190 --> 04:32.690 or the S u. 04:32.710 --> 04:36.470 M keyword under the proc c.p.u info file. 04:37.370 --> 04:38.750 So that's what I'm going to do now. 04:38.780 --> 04:44.240 So as long as this command shows an output such as the switches listed here. 04:44.830 --> 04:46.610 Now, virtualization has been enabled. 04:46.820 --> 04:51.780 And you don't have to enable it specifically from the BIOS if it's not enabled. 04:51.800 --> 04:55.430 Then you have to check your laptop's BIOS settings. 04:55.910 --> 04:58.070 So you have to restart your laptop, go into the BIOS. 04:58.100 --> 05:00.650 And there should be an option to enable virtualization. 05:01.040 --> 05:01.910 And you have to do that. 05:02.690 --> 05:08.270 You might have to check your laptops, a manual in order to know how that's done. 05:08.300 --> 05:15.920 Or just check online with your laptops model and search how to enable virtualization on your laptop. 05:16.580 --> 05:21.860 And again, make sure that you check the documentation here for the respective operating system that 05:21.860 --> 05:29.210 you are on for each of these are specific commands that can be used to run a test to see whether virtualization 05:29.300 --> 05:30.140 has been enabled. 05:31.160 --> 05:31.360 Okay. 05:31.490 --> 05:33.590 So next, we are going to install mini KUB. 05:33.890 --> 05:36.860 And again, we will go ahead with the option for Linux. 05:37.280 --> 05:42.470 And the first prerequisite is to install Kupe cattle, which we have already done. 05:42.830 --> 05:45.350 The next one is to install a hypervisor. 05:45.860 --> 05:49.440 So for Linux, we can either use Cavey M or Witchel Box. 05:50.150 --> 05:56.480 We will go with virtual box has that is our preferred virtualization solution. 05:56.900 --> 06:01.840 You can also run many KUB without a hypervisor and directly on your host using Docker. 06:01.910 --> 06:06.730 So if you already have Docker installed, you could leverage that and have many KUB. 06:07.700 --> 06:09.410 No provision Echobrain in this cluster. 06:10.700 --> 06:11.930 Using a docker container. 06:12.560 --> 06:18.890 However, note that as you can see here in the documentation page, there is a warning that says it 06:18.890 --> 06:21.530 can result in security or data loss issues. 06:21.560 --> 06:25.310 So we will just stick with a virtual machine based approach for now. 06:25.910 --> 06:32.600 I just prefer virtual box because it can in case you mess up something on your system and you need to 06:32.600 --> 06:33.170 restart. 06:33.710 --> 06:37.030 It's easy to get rid of the VM and restart again, right. 06:37.100 --> 06:43.520 It won't really mess up your laptop and you can take snapshots before you make a major change and then 06:43.520 --> 06:47.000 you can restore that snapshot in case that changed. 06:47.290 --> 06:49.940 You know, it doesn't really well work well for you. 06:50.970 --> 06:57.190 Now, your box is supported on all variety of operating systems, including Linux, Windows and OSX, 06:57.210 --> 07:01.830 so I'm going to open this in a new window and it takes me to the download section. 07:02.190 --> 07:07.830 And here I am going to select Linux distribution and the one that is most appropriate for my system. 07:08.550 --> 07:11.220 You may choose one that is appropriate for yours. 07:12.150 --> 07:17.340 So wait for it to complete the download and then we will install virtual box. 07:19.260 --> 07:23.860 It has downloaded the Debian package, so I'm just going to install it directly. 07:33.070 --> 07:34.630 Wait for the installation to complete. 07:34.840 --> 07:39.280 And while it installs, let's go back to the documentation section. 07:44.960 --> 07:51.050 So now the installation has been completed and I'm just going to close this and I am going to launch 07:51.260 --> 07:52.030 watchbox. 07:54.710 --> 07:58.800 So as you can see here, this is what the virtual box interface looks like. 07:59.310 --> 08:05.250 And you will have a similar interface for Windows or Mac with minor differences, but that should not 08:05.250 --> 08:05.700 matter. 08:06.690 --> 08:10.860 So right now, we don't have any virtual machines running. 08:11.010 --> 08:17.340 So when we provision a cluster using mini cube, it will automatically create a virtual machine as required. 08:18.030 --> 08:23.040 So apart from just installing washer box, you don't really have to do anything directly with it. 08:24.370 --> 08:26.010 Now, let's proceed with the installation. 08:26.040 --> 08:30.680 So the next step is to install the mini cube utility. 08:31.110 --> 08:33.210 Again, there are different ways to do this. 08:33.240 --> 08:39.420 Either use the package manager and install it as a package, or we can do it using a direct download 08:39.630 --> 08:40.140 approach. 08:40.830 --> 08:42.690 So we're going to download the latest version. 08:42.900 --> 08:48.390 And just like we did with the Cube Carol utility, I'm going to call the package and then install it 08:48.390 --> 08:49.110 on my machine. 08:50.240 --> 08:56.200 So I'm just going to copy the whole thing, and this will download, make binaries and assign and execute 08:56.250 --> 08:58.970 bid so that we can run it as a command. 09:01.610 --> 09:05.900 And once that has been done, let us add many KUB to our path. 09:06.410 --> 09:12.710 The user local bin directory has already been created, so we don't have to do that first step. 09:21.930 --> 09:23.040 We were on this command. 09:23.970 --> 09:29.170 Do install mini Kube at these locations like user slash, local slash bin. 09:40.050 --> 09:44.370 Next, we will provision Aquaman and his cluster using the mini cube utility. 09:45.790 --> 09:47.980 So we're going to run the Mini Cooper start command. 09:48.340 --> 09:52.150 But we also have to specify the driver name to be used with this command. 09:52.960 --> 09:55.990 Now, many cube can work with different virtualization tools. 09:56.050 --> 09:59.110 And that's where you must specify what driver to use. 09:59.380 --> 10:01.120 In our case, we use virtual box. 10:01.240 --> 10:07.300 So let's open this link and make sure that you are using the correct driver name. 10:07.750 --> 10:10.510 So the name of a virtual box driver is Virtual Box. 10:10.870 --> 10:12.280 So we will make use of that name. 10:13.100 --> 10:18.970 So I'm going to copy and paste this command until the driver name, and then I'm just going to copy 10:18.970 --> 10:21.940 the driver name from this page and paste it here. 10:24.300 --> 10:27.690 We will now execute the command when it starts. 10:27.750 --> 10:31.620 You'll notice that it follows a process. 10:31.650 --> 10:40.890 So it is, in fact, if downloading the ISO image for many KUB and then this is the image that will 10:40.890 --> 10:44.190 be used to provision a VM on virtual box. 10:45.240 --> 10:51.780 We now see that it's downloading coronets abortion one day or 18 or three and any other required binaries. 11:01.280 --> 11:07.460 Let me switch to the virtual box UI and we will see that a virtual machine by the name Minnie Cube has 11:07.460 --> 11:09.650 been created and it is in their running state. 11:10.370 --> 11:14.180 And you can see that the VM uses to C.P.E. use and to gibi of ram. 11:14.930 --> 11:17.600 So let's wait for this setup to complete. 11:19.680 --> 11:27.760 OK, so now this has been installed and Cucuta's utility is now configured to use the components cluster 11:27.960 --> 11:29.900 provisioned using mini KUB. 11:30.600 --> 11:32.740 So let's head back to the documentation page. 11:32.820 --> 11:39.300 And the next thing that we are going to do is run the mini Kupe status command to ensure that everything 11:39.300 --> 11:40.470 has been set up correctly. 11:41.280 --> 11:46.010 So I'm going to clear the screen here and then run the mini cube status command. 11:46.590 --> 11:55.320 We can see that the mini Cuban control plane, cube led API server and cube config are all in and running 11:55.350 --> 11:56.340 and configured state. 11:56.760 --> 11:57.450 So that's good. 11:58.600 --> 12:04.090 If you run into issues with the insulation in time, feel free to run this command and check the status. 12:04.990 --> 12:06.610 So our cluster is now set up. 12:06.850 --> 12:10.840 We will deploy some applications on the cluster and make sure it's working as expected. 12:11.620 --> 12:17.530 Now, we will get in to talking about the different concepts on deploying an application in the upcoming 12:17.530 --> 12:18.100 lectures. 12:18.550 --> 12:23.560 Right now, we just want to make sure that the cluster we set up is working as expected. 12:23.590 --> 12:27.220 So we will simply follow the tutorial given in this page. 12:27.670 --> 12:33.010 Although it may not make total sense now, but I assure you that we will get to that in a bit. 12:33.820 --> 12:36.130 So click on this link under what's next. 12:36.310 --> 12:42.790 And here we have some examples that could be used to test our setup in the new page. 12:42.820 --> 12:46.360 You can skip the first step of starting a mini cube cluster. 12:46.380 --> 12:48.400 So we have already done that. 12:49.030 --> 12:53.350 So the next thing that we need to check is if Google commands are working. 12:53.640 --> 13:00.420 So I'm going to run the acquittal, get notes command and you can see that it is a single node cluster. 13:00.820 --> 13:04.120 And the node name is Minnie Cube and it is in a ready state. 13:05.440 --> 13:07.810 And it was spun up about eight seconds ago. 13:07.840 --> 13:13.490 And it's running the latest release of Cuban errors, which is one dot 18. 13:13.600 --> 13:14.570 As of this recording. 13:15.560 --> 13:19.240 So next, let us try to create some deployments using this cluster. 13:19.330 --> 13:21.340 So here we have an example on this page. 13:22.060 --> 13:26.070 I'm going to run Cucuta's Create Deployment Command to create the deployment. 13:36.620 --> 13:38.650 Once that is done, we will run the. 13:38.780 --> 13:41.780 You've got to get DEPLOYMENT'S command and you can see that. 13:42.290 --> 13:46.220 Hello, Mini cube deployment has been running for 22 seconds. 13:47.210 --> 13:53.920 Next, we will expose this deployment as a service for that make use of this command here and Kubica 13:53.950 --> 13:55.840 to expose deployment. 13:56.930 --> 13:58.190 Hello, Mini Cooper Command. 13:59.980 --> 14:01.730 Now, don't worry about the command for now. 14:01.940 --> 14:05.210 We'll talk about these in much detail later in this course. 14:05.540 --> 14:07.100 For now, we'll just copy and paste. 14:10.800 --> 14:11.160 OK. 14:11.260 --> 14:16.390 And then we will skip to step five, where we will get the you are all off the exposed service. 14:16.630 --> 14:18.430 So by running this command. 14:23.550 --> 14:24.210 Copy that you are. 14:24.630 --> 14:26.900 And pasted into our browser on your laptop. 14:29.230 --> 14:32.530 And it should list the details about the application like this. 14:33.670 --> 14:39.600 OK, so that's not the most exciting application, but this is proof that your setup is working and 14:39.600 --> 14:40.980 that's all we need for now. 14:41.400 --> 14:47.630 Now follow the remaining instructions to clean up your system, delete the services and delete the deployment. 15:08.050 --> 15:11.650 Now, the deployment will be in a terminating state for a few seconds. 15:17.900 --> 15:21.750 And after it's done, the application will no longer be accessible on the Web page. 15:22.910 --> 15:24.350 Well, that's it for now. 15:24.980 --> 15:26.810 We'll see you in the next lecture.