1 00:00:00,540 --> 00:00:08,590 Hello and welcome to the solution video for installing cabinet this cluster using cube A.T.M. and this 2 00:00:08,590 --> 00:00:09,420 practice lap. 3 00:00:09,430 --> 00:00:17,680 We have a total of eight questions and the first question is for us to install cube IDM package on Master 4 00:00:17,770 --> 00:00:25,860 and Node 0 1 So before we begin let's check whether those packages are sold and available 5 00:00:33,050 --> 00:00:39,410 to install Q IDM we will make use of the equipment as documentation so go through the documentation 6 00:00:39,410 --> 00:00:42,920 page and search for cubism idiom install 7 00:00:57,600 --> 00:01:03,820 in our lives make use of ubuntu image so we allow to scroll down and find the installation steps for 8 00:01:03,880 --> 00:01:04,360 open to 9 00:01:10,390 --> 00:01:18,260 and typically you can ignore any ports to be opened because in this case we have everything set up already 10 00:01:18,530 --> 00:01:26,000 so you don't have to worry about opening any firewall ports or any other prerequisites the docker on 11 00:01:26,000 --> 00:01:27,380 time has already installed 12 00:01:31,670 --> 00:01:39,400 so to install QB DRM will go down and look for the instructions for when 2 or Debian so the first thing 13 00:01:39,520 --> 00:01:47,250 to do is to update the repository install the GOP cheeky 14 00:01:50,050 --> 00:01:51,130 pour over notice 15 00:01:57,090 --> 00:02:03,210 once that's done we can do an app get update and install Q bullet QB DMA and cube CTO 16 00:02:16,630 --> 00:02:23,140 using cube IDM vision dash all shot we can check the evolution of Q medium installed on the master node 17 00:02:24,500 --> 00:02:29,430 and now we have to do the same thing on nodes or two so it's installed on the master and lets repeat 18 00:02:29,430 --> 00:02:40,840 the process on nodes that are 1 so it's assessed you know 0 1 and copy the same commands from the documentation 19 00:03:07,020 --> 00:03:17,900 what is the vision of cube it installed so let's go back to node sort of 1 and we can run come on Q 20 00:03:17,930 --> 00:03:18,260 Let 21 00:03:22,240 --> 00:03:28,630 with the dash dash vision fly and you can see that it is also running vision 1 not 1 7 that's the correct 22 00:03:28,630 --> 00:03:37,370 answer how many nodes are part of the cluster currently so we already know that the cluster is not install 23 00:03:37,440 --> 00:03:49,000 cube CTO get n most moderate on anything so we'll click the zero let let's know bootstrap given it cluster 24 00:03:48,990 --> 00:03:57,190 use a Q media the latest version of Governor this will be installed Okay so for the next question we 25 00:03:57,190 --> 00:04:04,120 have to initialize the controller incompetence on the master node and for this will again refer to the 26 00:04:04,120 --> 00:04:15,920 documentation go to Cuba IDM use Q radium to create a cluster and the one that we need to run here is 27 00:04:15,940 --> 00:04:17,030 Cuba radium in it 28 00:04:21,070 --> 00:04:26,350 lies controlled plant one Q radium nitwit additional arguments in this case we don't know how to make 29 00:04:26,350 --> 00:04:33,190 use of any arguments but you can if you want to use a custom service side arrange or any other options. 30 00:04:33,190 --> 00:04:35,320 What this gives you don't have to. 31 00:04:35,690 --> 00:04:38,500 So we'll use it without any additional arguments 32 00:04:43,550 --> 00:04:44,780 when we run cube radium in it. 33 00:04:44,780 --> 00:04:46,770 It will first run some please. 34 00:04:46,790 --> 00:04:51,810 Pre-flight checks to make sure that the system is healthy and ready to install given it is. 35 00:04:51,920 --> 00:04:58,620 And if there are any errors it will show you that in the screen as well so in this case doesn't look 36 00:04:58,620 --> 00:05:04,810 like we have any errors so we'll just wait for the installation to complete the scan. 37 00:05:04,820 --> 00:05:06,830 Typically take two to three minutes 38 00:05:11,240 --> 00:05:11,600 okay. 39 00:05:11,600 --> 00:05:18,650 The installation has completed no but before we move ahead we have to make sure that the cube config 40 00:05:18,650 --> 00:05:24,190 file is completed the default directory so we can just copy these commands here. 41 00:05:31,410 --> 00:05:35,150 And you would also see that uh joined token has been created for you. 42 00:05:35,150 --> 00:05:42,270 This is the command that we have to run on the volcano to add them to the cluster so you can copy this 43 00:05:42,270 --> 00:05:43,190 command as well. 44 00:05:48,970 --> 00:05:54,130 Generate a Q radium token or copy the one that was generated by cube idiom in it. 45 00:05:54,130 --> 00:05:55,050 Come on. 46 00:05:55,090 --> 00:05:56,710 So in case you have lost us. 47 00:05:56,720 --> 00:06:03,450 Come on we can actually regenerate a new token and plant a new joint command using cube IDM token. 48 00:06:03,450 --> 00:06:11,200 Come on. 49 00:06:11,280 --> 00:06:18,450 If you run cube idiom 2 can create with dash dash help in the options you'll see that there is a flag 50 00:06:18,840 --> 00:06:20,490 called Print joint command 51 00:06:31,730 --> 00:06:35,040 so this will give you a new command that you can copy 52 00:06:49,350 --> 00:07:00,450 and you can run that command on Node 0 1 and wait for it to be added to the cluster. 53 00:07:00,560 --> 00:07:06,330 So now that has been added to the cluster we can verify this by running cubes he'll get notes 54 00:07:10,260 --> 00:07:13,960 as you can see no 0 1 is also now part of the cluster. 55 00:07:14,110 --> 00:07:17,160 Don't worry about the status of it not being ready. 56 00:07:17,280 --> 00:07:21,090 This will be fixed as soon as we install our network plugin 57 00:07:25,560 --> 00:07:29,430 so for the last question we are going to install a network plugin as a default. 58 00:07:29,430 --> 00:07:34,060 We'll call it we've which we have been using for other labs as well and for this will again make use 59 00:07:34,060 --> 00:07:35,560 of the official documentation. 60 00:07:37,420 --> 00:07:43,740 So if you scroll down there is a section for installing a port and it took add on 61 00:07:48,270 --> 00:07:54,890 and to do this one of the prerequisites as to said these are slightly old rules here so copy it. 62 00:07:57,460 --> 00:07:59,440 And run it on all the notes 63 00:08:05,840 --> 00:08:10,310 and once that's done we can deploy the V plugin 64 00:08:30,440 --> 00:08:34,320 now let's check the status of the nodes in the cluster. 65 00:08:34,550 --> 00:08:37,970 They should be going to ready status and there you go. 66 00:08:37,970 --> 00:08:41,120 They are now and ready status and you know what to node. 67 00:08:41,120 --> 00:08:43,400 Given this cluster running 1 not 1 7 68 00:08:48,080 --> 00:08:49,970 thank you for joining me in this video. 69 00:08:49,970 --> 00:08:52,120 I hope that you found it useful. 70 00:08:52,160 --> 00:08:53,360 I'll see you in the next one.