So friends in the previous videos, we learned how we could create partitions
using Ansible
as well as how to set up logical volume management.
Now one thing I just want to highlight to you before we close this particular
skill is
that we also do have an option to perform these particular tasks by making use
of our
Ansible roles.
Now by now you should remember that roles allow us to make playbooks that are a
little
bit simpler, a little bit more modular, a little bit more portable, that type
of thing.
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
So it is worthwhile to understand that we do have this option available to us,
but in
this particular case, this is one of the rare events where I really don't like
to use the
role for this particular task, simply because in my opinion, the role as it is
right now
upon recording this video in March 2024, well it's a little bit limited and
underdeveloped.
Nevertheless I do just want to make you aware that the role does exist and
where you can
find information relating to that particular role.
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
So by now you will have installed the rail system roles and as such within our
system,
we should have a particular documentation relating to those roles.
So if you do CD share doc and then go into rail system roles right here and do
an LS,
notice we have a particular folder for storage.
Now if you go into the storage folder and do an LS, notice we actually don't
have any
example playbooks, unlike say for example, if I went into let's say maybe the
network
directory, tons and tons of examples.
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
Now maybe that's an indication that the storage role is not yet quite ready for
consumption.
I don't want to speculate too much, but nevertheless what I do want to
highlight to you is that
within the readme file here, the marketing one that is, we actually can see how
we can
use this particular utility.
Now one thing to note here and this really is the limitation in my view.
Since here this role allows users to configure local storage with minimal input
.
That sounds really really good.
The type of thing we would like to do, however, it says as of now, so hopefully
this changes,
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
but right now it says the role supports managing file system and mount entries
on and the two
options are on partition disks and LVM, unpartitioned whole disk physical
volumes.
So pretty much if you want to use this particular role, you're going to have to
only have one
file system on the entire disk.
This is very, very limiting and in my opinion, not exactly applicable in the
real world of
modern Linux administration.
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
Much much more likely you're going to be dealing with disks that have multiple
partitions and
in that case, this particular role is not going to be able to be used.
So you know, that is a little bit of a bummer, but nevertheless, if you want to
use this particular
role, you can see here we have particular things that we have to specify.
So we can see here you would have to define a variable known as storage_pools
and you
could supply some values to that particular variable, such as the name whereby
you would
specify the logical volume group you wanted to be manipulating.
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
You could specify the disks that you wanted to be a part of that particular
storage pool,
as well as specify the volume that you want to belong to the current pool.
So if you scroll down to the very bottom of this particular documentation, you
're going
to get to see an example playbook with this particular role in use.
So as per the example right here, they are targeting the all group and they are
calling
the role known as rel-system-rolls.storage that invokes this particular role
here.
And now we're defining that storage pool variable that we just talked about
above and then we
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
supply things like the name, the disks involved in this case here, SDB, SDC, as
well as the
volumes that we target within the particular pool.
So we can see the size of the volume, the mount point for the volume, as well
as the
file system on that particular volume, and the example here they're using the
file system
of XFS.
And scrolling on down a little bit further, we can see more examples of this
particular
role.
So I just want you to be aware of this particular role's existence.
Feel free to read the documentation, try it out if you so wish, but just really
be aware
of its current limitations. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of its current limitations.
And for me personally, when I want to manage my logical volumes or my
partitions, then
I'm going to be using what I see as the much more graceful and elegant solution
, and that
is just to use the community general collection, which comprises of the modules
that we just
saw before the part and module, the LVG module, and the LVL module.