WEBVTT 1 00:00.000 --> 00:04.500 So friends in the previous videos, we learned how we could create partitions 2 00:04.500 --> 00:05.480 using Ansible 3 00:05.480 --> 00:08.920 as well as how to set up logical volume management. 4 00:08.920 --> 00:12.800 Now one thing I just want to highlight to you before we close this particular 5 00:12.800 --> 00:13.360 skill is 6 00:13.360 --> 00:18.140 that we also do have an option to perform these particular tasks by making use 7 00:18.140 --> 00:18.560 of our 8 00:18.560 --> 00:19.560 Ansible roles. 9 00:19.560 --> 00:23.450 Now by now you should remember that roles allow us to make playbooks that are a 10 00:23.450 --> 00:23.920 little 11 00:23.920 --> 00:27.450 bit simpler, a little bit more modular, a little bit more portable, that type 12 00:27.450 --> 00:28.080 of thing. 13 00:28.080 --> 00:32.650 So it is worthwhile to understand that we do have this option available to us, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:28.080 --> 00:32.650 So it is worthwhile to understand that we do have this option available to us, 14 00:32.650 --> 00:33.200 but in 15 00:33.200 --> 00:37.370 this particular case, this is one of the rare events where I really don't like 16 00:37.370 --> 00:37.880 to use the 17 00:37.880 --> 00:42.940 role for this particular task, simply because in my opinion, the role as it is 18 00:42.940 --> 00:43.640 right now 19 00:43.640 --> 00:49.080 upon recording this video in March 2024, well it's a little bit limited and 20 00:49.080 --> 00:50.880 underdeveloped. 21 00:50.880 --> 00:54.760 Nevertheless I do just want to make you aware that the role does exist and 22 00:54.760 --> 00:55.560 where you can 23 00:55.560 --> 00:58.000 find information relating to that particular role. 24 00:58.000 --> 01:03.040 So by now you will have installed the rail system roles and as such within our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 00:58.000 --> 01:03.040 So by now you will have installed the rail system roles and as such within our 25 01:03.040 --> 01:03.720 system, 26 01:03.720 --> 01:06.360 we should have a particular documentation relating to those roles. 27 01:06.360 --> 01:11.150 So if you do CD share doc and then go into rail system roles right here and do 28 01:11.150 --> 01:12.000 an LS, 29 01:12.000 --> 01:15.520 notice we have a particular folder for storage. 30 01:15.520 --> 01:19.240 Now if you go into the storage folder and do an LS, notice we actually don't 31 01:19.240 --> 01:19.680 have any 32 01:19.680 --> 01:23.870 example playbooks, unlike say for example, if I went into let's say maybe the 33 01:23.870 --> 01:24.400 network 34 01:24.400 --> 01:27.000 directory, tons and tons of examples. 35 01:27.000 --> 01:30.900 Now maybe that's an indication that the storage role is not yet quite ready for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 01:27.000 --> 01:30.900 Now maybe that's an indication that the storage role is not yet quite ready for 36 01:30.900 --> 01:31.760 consumption. 37 01:31.760 --> 01:34.410 I don't want to speculate too much, but nevertheless what I do want to 38 01:34.410 --> 01:35.480 highlight to you is that 39 01:35.480 --> 01:39.590 within the readme file here, the marketing one that is, we actually can see how 40 01:39.590 --> 01:40.000 we can 41 01:40.000 --> 01:41.640 use this particular utility. 42 01:41.640 --> 01:45.160 Now one thing to note here and this really is the limitation in my view. 43 01:45.160 --> 01:49.670 Since here this role allows users to configure local storage with minimal input 44 01:49.670 --> 01:49.920 . 45 01:49.920 --> 01:51.320 That sounds really really good. 46 01:51.320 --> 01:56.640 The type of thing we would like to do, however, it says as of now, so hopefully 47 01:56.640 --> 01:57.360 this changes, 48 01:57.360 --> 02:03.070 but right now it says the role supports managing file system and mount entries WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 01:57.360 --> 02:03.070 but right now it says the role supports managing file system and mount entries 49 02:03.070 --> 02:03.880 on and the two 50 02:03.880 --> 02:10.540 options are on partition disks and LVM, unpartitioned whole disk physical 51 02:10.540 --> 02:11.320 volumes. 52 02:11.320 --> 02:15.630 So pretty much if you want to use this particular role, you're going to have to 53 02:15.630 --> 02:16.440 only have one 54 02:16.440 --> 02:19.440 file system on the entire disk. 55 02:19.440 --> 02:23.710 This is very, very limiting and in my opinion, not exactly applicable in the 56 02:23.710 --> 02:24.760 real world of 57 02:24.760 --> 02:26.760 modern Linux administration. 58 02:26.760 --> 02:30.130 Much much more likely you're going to be dealing with disks that have multiple WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 58 02:26.760 --> 02:30.130 Much much more likely you're going to be dealing with disks that have multiple 59 02:30.130 --> 02:31.160 partitions and 60 02:31.160 --> 02:35.640 in that case, this particular role is not going to be able to be used. 61 02:35.640 --> 02:40.040 So you know, that is a little bit of a bummer, but nevertheless, if you want to 62 02:40.040 --> 02:41.240 use this particular 63 02:41.240 --> 02:44.720 role, you can see here we have particular things that we have to specify. 64 02:44.720 --> 02:49.860 So we can see here you would have to define a variable known as storage_pools 65 02:49.860 --> 02:50.200 and you 66 02:50.200 --> 02:53.700 could supply some values to that particular variable, such as the name whereby 67 02:53.700 --> 02:54.200 you would 68 02:54.200 --> 02:58.080 specify the logical volume group you wanted to be manipulating. 69 02:58.080 --> 03:01.590 You could specify the disks that you wanted to be a part of that particular WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 69 02:58.080 --> 03:01.590 You could specify the disks that you wanted to be a part of that particular 70 03:01.590 --> 03:02.520 storage pool, 71 03:02.520 --> 03:06.520 as well as specify the volume that you want to belong to the current pool. 72 03:06.520 --> 03:09.920 So if you scroll down to the very bottom of this particular documentation, you 73 03:09.920 --> 03:10.360 're going 74 03:10.360 --> 03:14.520 to get to see an example playbook with this particular role in use. 75 03:14.520 --> 03:17.550 So as per the example right here, they are targeting the all group and they are 76 03:17.550 --> 03:17.960 calling 77 03:17.960 --> 03:23.670 the role known as rel-system-rolls.storage that invokes this particular role 78 03:23.670 --> 03:24.120 here. 79 03:24.120 --> 03:27.840 And now we're defining that storage pool variable that we just talked about 80 03:27.840 --> 03:28.480 above and then we 81 03:28.480 --> 03:33.410 supply things like the name, the disks involved in this case here, SDB, SDC, as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 81 03:28.480 --> 03:33.410 supply things like the name, the disks involved in this case here, SDB, SDC, as 82 03:33.410 --> 03:34.160 well as the 83 03:34.160 --> 03:36.440 volumes that we target within the particular pool. 84 03:36.440 --> 03:39.740 So we can see the size of the volume, the mount point for the volume, as well 85 03:39.740 --> 03:40.080 as the 86 03:40.080 --> 03:44.050 file system on that particular volume, and the example here they're using the 87 03:44.050 --> 03:44.680 file system 88 03:44.680 --> 03:46.400 of XFS. 89 03:46.400 --> 03:50.230 And scrolling on down a little bit further, we can see more examples of this 90 03:50.230 --> 03:50.960 particular 91 03:50.960 --> 03:51.960 role. 92 03:51.960 --> 03:55.040 So I just want you to be aware of this particular role's existence. 93 03:55.040 --> 03:58.780 Feel free to read the documentation, try it out if you so wish, but just really 94 03:58.780 --> 03:59.280 be aware 95 03:59.280 --> 04:01.080 of its current limitations. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 95 03:59.280 --> 04:01.080 of its current limitations. 96 04:01.080 --> 04:05.060 And for me personally, when I want to manage my logical volumes or my 97 04:05.060 --> 04:06.000 partitions, then 98 04:06.000 --> 04:10.290 I'm going to be using what I see as the much more graceful and elegant solution 99 04:10.290 --> 04:10.840 , and that 100 04:10.840 --> 04:14.650 is just to use the community general collection, which comprises of the modules 101 04:14.650 --> 04:15.280 that we just 102 04:15.280 --> 04:20.680 saw before the part and module, the LVG module, and the LVL module.