Red Hat OpenShift Red Hat Enterprise Linux Presents | Red Hat Livestreaming, 7 Oct 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Red Hat Enterprise Linux Presents (E22): Storage Primer

Description

It’s hard to believe, but 1 year ago today, RHEL Presents made its first appearance on Red Hat TV! Join Chris and Eric today as they discuss storage concepts under Linux and walk through a couple of demonstrations around managing your storage.

A

A

A

A

A

Good morning, good afternoon, good evening, wherever you're hailing from welcome to another red hat enterprise linux presents today we are tackling storage and we came to this topic uh kind of took some time to get there. I feel like eric, but I still feel like it's very valid to folks that are maybe queueing up to take in our you know a red hat exam, any kind of certification test or oh, my god. I have to do something in an emergency situation with storage.

A

So eric, please introduce yourself uh and- and let's talk about what we're talking about today, yeah.

B

So I am eric. No worries, no worries, it's it's almost friday right, it's we're almost there, uh so I am eric the it guy hendrix. I am a technical marketing manager here in the rel business unit, uh so I spend all of my days thinking about how to make uh systems administrators lives easier and doing so with, hopefully not having a demo environment blow up.

B

On that note, chris, I I did. I did build a brand new vm called it iron man based on previous episode feedback, and you know, I think, we're ready to go.

A

Well, that's good news.

B

We kind of, like you said we kind of came to this topic because it's relevant whether you've been a linux systems administrator for 10 days or 10 years. It's uh it's just one of those things that um it's it's a weird thing, because I don't know about you, but I have to google this about every single time that I go because let's see it's a virtual disk, first right. No, no! You start out in the real world, so it's a physical volume and then then logical or.

A

I'm telling you I I had to find. I had to go into evernote when we were talking about it, because it's been so long since I've mucked with like lvm right.

B

A

I was like dang, that's even in like a different generation of notes, apps right.

B

A

Oh yeah, I need to brush up on that.

B

A

I had that article saved.

B

Evernote back in the day and then and then it's like no, I don't need to reread the whole article. I just need these few commands in the right order, yep. So then that moved to apple notes and then so, I'm on to my third generation, because I'm on joplin now and still to this day, I work on this stuff all day every day and I still have to go in and check actually yeah.

B

Actually we'll do this the hard way first, okay and then I'll show you why I don't need that note anymore. Let's do that.

A

Oh eliminating the note I like this okay cool so.

B

Let me share my screen here.

A

The hardest I mean to be fair, the hardest part for me is lv vg pv. You know right like when to do what create right, like that's always the hardest part for me,.

B

But well and then that's that's really. The hardest part is which order does all this stuff go in and then for fun? Let's throw out fdisk because yeah.

A

Why not add another.

B

Set of commands.

A

In there could you increase the font size on that? Somehow, because, like I could.

B

No, I was afraid that was going to happen. Yeah see, I know you control that we resized it a little bit in the intro. I think it size itself back when uh when I shared it, let me see there, it is.

B

I was right there is a keyboard shortcut.

A

There you go there, we go, how about them. Apples.

B

A

One more got it well, no, it went down. That's weird, it went it like defaulted itself back to the original size. Can you please increase the font size? No, I'm just kidding what are you doing over there? I.

B

Don't know it's like whenever I feel or.

A

Whatever you're doing it's weird interesting, huh it's are you like. Did you do the thing in zoom, where it's like only take this window? Yes, maybe that's the problem. That's probably part of it because you're resizing the window, size and zoom is resizing accordingly as well too. Let's.

B

See got a little zoom and all this technology stuff, it's just great. Let's do, let's just share my whole, desktop we're going to need it all here. Eventually,.

A

Yeah, why not, unless you've got a ultra right monitor, then we don't need all of that.

B

I mean like that: yeah, it's not technically.

A

I mean that's still pretty wide, though so you have to bump up the phone and everything.

A

Come along, that's the terminal, how about them? Apples? uh No! That's unreadable unreadable! Okay! All right!

A

I mean like even with glasses, on my game.

A

We've never had this problem before. Why is this new.

B

I don't know sure enough.

B

Zoom just just work, that's that's all. I need you to do.

A

Well, if not in a windowed state, if you just you're on a mac, so command plus, plus a bunch that should, in theory, make it bigger at the same time what but every time you move it it resizes it that's weird.

B

And everything's updated as of this morning, so I mean we could blame twitch.

A

Okay, that's working keep increasing the size, it's not twitch, because technically it's just soon. Okay, there you go. I can read that all right. If you go up one more, I'm curious if that would help, but probably.

B

Break the entire world yeah all right cool, all right, troubleshooting on air- hopefully that's the worst of it today, all right, so I've got iron man here he is a virtual machine running in my home lab just a generic rel 8.5 installed right off of image builder, and uh so, if, if you look, I've got dev, vda, okay, so let's, let's back up.

A

B

A

To say, let's: let's talk about the device yeah, let's.

B

Let's back up here all right, so I'm logged in as root. Don't do this at home, but so to start with, we've got uh dev vda, it's a 64, gig uh disk. It is technically a qcao 2 file sitting on my uh on my hypervisor server, it's 64 gigs, but in reality it's like 2.5 gigs in an actual size, but it's it's then provisioned, that's actually. That would be a great conversation for for another episode. That was uh virtual machines, qca qc2 files.

B

uh We we saw me working on my my hypervisor here at home, live on the air a couple weeks ago. So uh I might so. I might jot that down.

A

I got a great story I'll, send you a link to it.

B

Perfect yeah because I think that'd be a good conversation. um I would be lost both in this job and every other job. I've had without my home lab. So we'll talk about that in the future. But for all intents and purposes today, just assume dev vda is a disc. That's 64, gigs in size, we've got our bio system, we've got our efi and then uh then about 60, just shy of 64 gigs worth of actual linux file system. That's the storage we actually have available, and then we've got vdb and vdc.

B

So we've got two disks here and I intentionally change put them at different sizes, just for ease of use, because there's no uh there's no greater problem than oh look. I've got like six discs and they're all a terabyte which one's which so vdb is 32. Gigs and vdc is 16 gigs, so just just for the sake of making it easy because live demos are hard. We'll we'll uh make this easy, and so the first thing we want to do is yeah yeah. I love it rap scouting uh yeah, I'm not even gonna.

A

Go down that rabbit trail today, stay here stay here, stay with.

B

Me all right, physical volumes, virtual disks and then uh lvms, so we we've got. We we look at our disk layout. We've got our three different disks, they're 64, 32 and 16, just for the for the ease of uh just for the ease of demonstration.

B

So we don't want to touch our system disk that that one's working it we don't. We don't want to touch it, so we're going to leave vda alone, mostly because I don't want to break my live machine.

B

So vdb is 32 gigs, let's work with that one. So we know that it's it's mounted, because everything in linux is a file. So it's it's actually that disk is actually present at slash dev vdb. So what we want to do is we want to create a virtual disk or a physical volume uh off of see. I'm already messing up. This is this. Is why we're talking about this today right exactly.

B

So the first thing we want to do is use p uh pv, create.

A

Okay, physical.

B

Volume, that's what it stands for: that's a physical volume create. So what we're going to do is we're just going to tell our operating system that hey vdb is a disk. We want to treat it as such that way when we eventually get to our linux, uh our our logical volume that that's we've got everything layered correctly, so we're going to do a pv, create.

A

B

Can we say that it was sick, fantastic.

A

B

No wonder autocomplete wasn't working.

A

ah That's the best all.

B

Right so before you do anything, you did a bunch of prep for this.

A

B

A

I needed a lot of reading. I did a lot.

B

Of reading I didn't run through this, so um this tells you how many times I've had this problem as a systems administrator. So the first thing we need to do is actually install the packages to support logical volumes, so we're we're going to do a dnf, install or yum, install whichever the case may be, and because I've done this before.

B

I know that the package that I need to give us all the commands is lvm2 um so that that takes care of device mapper that gives us our pv commands our vg commands and our and our lv uh commands as well. So can we just say that I did that on purpose? You did that on purpose.

B

So now autocomplete works. So I know the package is installed, so we're going to do vdb and that's going to create a physical volume. What that does is that basically takes our hardware disk and our and tells the operating system hey. This is hardware disk. I want you to treat it as such, and so we just give it the disk that we want to use, and then so that's pv create so you've got the hardware.

B

You've got physical volume, then the next level up is a is a volume group and so we're going to do a vg create much the same as we did before, and if my brain remembers correctly we're going to do it dash in to give it a name and so we're just going to we're going to be super creative because we're engineers and that's what we do and we're just going to call it a data. Vault data volume, um different organizations have different naming schemes for for volume groups a lot of times.

B

It's the host name other times. It's something super super detailed like data volume.

B

Sometimes if it's like a database disk or something it'll, be uh vg, db or vgdb01, if you've got multiples, so just different naming schemes, so we're going to give it a name and then we're going to reference and technically we're referencing that physical volume now because we've created that, but we give it the same location. So it's slash, dev, slash, vdp and of course I was wrong.

A

Wait, what did you.

B

Say is it oh? uh No argument? Okay, um so it's I'm thinking lvm, okay, so v2 create the name of our volume group and then the uh than the location of the physical volume, so no dash app cool.

A

Two exit zeros, I like it all right, yep,.

B

And, uh as is typical with linux commands, no no feedback is, is good, and so now this is where things get a little bit interesting, uh so logical volumes. This gives you a lot of this. Gives you a lot of flexibility when it comes to creating file systems in in a perfect world, you'd have a different, a separate file system for every every aspect of your system, whether that's slash temp, because you don't want someone coming in and doing some kind of uh some kind of a data dump into slash temp.

B

That brings your system down. So you in a perfect world you'd want to separate that out. um Slash var log is another uh one. That's pretty that I've seen very often can take down my servers because you'll you'll get that one you'll get that one administrator or developer or somebody who's doing some work on the box, changes their application or the networking service or something to debug and then just walk away.

B

You come back a couple hours later and your system's unresponsive and then, when you, when you actually get logged in you realize, oh, my my disk is full. So you start drilling down you. Do uh you? Do some du commands to see um what uh what directories are yeah.

A

B

A

B

Might it be the logs slash var, slash log is taking up 200 gigs worth of space.

A

B

Probably a problem and think about it. Those are those are text files right, like sadly, sadly, I've seen that huge disks completely full yeah.

A

B

Gigs 200 gigs worth of worth of uh debug logs, it's great and all of a sudden. Your multi-thousand dollar server is brought to its knees, because the disks are full go figure, um slash home is another one. That's uh that's pretty good to um that's pretty good to to kind of cordon off yeah, um and in fact, when you uh I, I can't look at the chat anymore.

A

Just turn it off just turn it off I'll keep an eye on it. That's that's awesome, though, and that's fantastic.

A

That's becoming itchy, I'm sorry.

B

No, that's! Okay! That's that's where my brain's at today and context. Switching it's it's fun! um So in a perfect world, you'd want to try and separate some of these things out and if your application lives in slash, opt or slash, serve. You you'd want a separate file system for each of those and in fact, there's certain uh certain certifications.

B

Security, uh certifications like like hipaa or fips uh or pci, is another big one that require those file systems to exist. Otherwise they say nope. You can't take credit card transactions across the server because it's not separated correctly so a lot of times when you look at a certification like a fips or like a hipaa and you've got all these different file systems requirements, then you're looking at something like lvm.

B

um So if we do a man, lv m2, I believe nope just a lamp there we go. So if you do a man on lvm man stands for manual. So, what's great is before the internet and google became a systems administrator's best friend, you could get all the manual all the docs. All the instructions command examples using the man command, and uh not only does it give you information on specific commands, but it also gives you high level stuff, like this. Lvm file tells you different.

B

It tells you different commands that are available, different arguments that go with those commands uh use cases for it. So if you look, uh there's like lv resides there towards the bottom um to where you can resize a logical volume and lvm came into play because, as discs got bigger and bigger and bigger, um I remember my first uh ssd was 128 gigs and it was probably 500 bucks, but now I typically don't buy it actually now I don't buy anything smaller than a terabyte.

B

So as as this got bigger, we need more flexibility with our file systems. So one day you've got uh one day. You might need more space and far log another day you might need to increase your database size. So lvm allows you to create logical partitions between your different disks.

B

So you can you can slice and dice one disc? You can put multiple discs into a group together and you can you can do that using lvm.

B

So, to kind of finish up our example, the hard way we're going to do an lv, create and then we're going to.

B

um On top of the man command, you can actually do a you can do lv, create dash dash help and that'll. Give you an output of just the arguments for uh for that command, so like right here towards the bottom, to create a new lv.

B

um Actually, that's create a cash flow, but we're not going to do that today because I don't want to confuse everyone, mostly myself, but there's different, uh there's different approaches, so uh different cache falls or to add to a certain pool. So you get a bunch of different options.

B

Use cases right there on the command line right in your terminal. But what we're going to do is I'm going to do this from memory, so we want. What we want to do is uh do an lv create. So we've got our hardware. We've got our physical volume. We've got our volume group. Now we're going to create a logical volume that only exists within software.

B

So if you were to take this out and to put added in as a secondary disk on another system, it's not going to understand what you're talking about, because this this exists within software.

B

And so what we're going to do is an lv create and then uh we're going to. Okay, so autocomplete doesn't work just yet. So what we're going to do is a dash v and do 100 percent free. So what that's going to do is we're going to specify our volume group, our data vault, that we uh that we determined earlier and it's going to take up all the anything that hasn't been allocated to another uh logical volume.

B

We're actually going to add in uh we're actually going to include in this logical volume, um and then this is where we do the the dash uh dash in so we'll just call it lv data, logical volume data and then we're going to specify our uh we're going to specify our virtual disk.

B

So what we call a data wall.

A

B

Oops, I think that's a capital. Google give me a second. Let me let me grab my note.

B

This is why we have these. Oh, it's a capital, l!

B

B

Double check my command yeah dash, l, 100, free, actually.

B

So you can do the 100 free or you can specify a logical volume size. So if we, if we've got a 32 gig disk- and we want 28 gigs for this lv data partition and then maybe we've got an lv log partition, then we can do there's several different ways to specify how big you can. Even if you're super hardcore old-school sysadmin, you can actually specify extents, um but uh because I I think very visually I can.

B

I can picture 28 things of 32, so using using gigs or megabytes or 100 percent free uh makes it really easy to to use. So now we've got our hardware, our physical, our uh and then our uh virtual group, and then our logical volume. So now we've just got two more steps see this is. This is definitely the hard way. The second disk I added on on purpose and the thing this is a regular thing.

B

Sys admins have to do all the time and by the way, if you take the certification, like chris uh mentioned earlier, there's a good chance that this is going to be on that exam.

B

So we've got our logical volume. It's ready to go. It's lv data, so what we want to do is we want to do a make. Fs that's make file system and xfs is for better or worse, not trying to start a holy war for better or worse. I tend to use xfs on my assistance here at home, so I'm going to do a make file system, exit, fs and then under dev. Mapper devmapper is a part of the of the lvm2 stack.

B

It basically creates common names that you can point to so, instead of pulling out a 25 26 character, uuid, which is really fun to do when you're on a console- and you don't have copy paste, you can specify it via uuid or or you can use the devmapper, which is kind of a common name shortcut. Think of it almost at almost like uh dns names versus ip addresses. It's kind of the same same idea, give it something human readable, and so we know that it, the volume group dash, uh then the logical volume name.

B

So it should be date of all dash lv data and then this, depending on the size of the disk that you're working with it, usually comes through fairly quickly. So now that logical volume actually has a file system on it, so it's not just ones and zeros. Now the operating system can actually make uh can actually write content to that to that logical volume, so the the last step part a see how see how complicated this is.

B

The last step part a is to mount the file system, so we want to mount dev mapper uh data wall dash lp data to say serve now. If I were now, if we do, if we list the file systems down at the bottom, we can see that we have 28 gigs mounted at serve and there's there's our dev mapper.

B

um So if we do a touch um serve, slash hello, world.txt.

B

Now we see that file, but if I do, if I unmount that file system.

B

And then look our file's gone and what happens? Oh, I don't know. That's fine, um so last step. Part b is we want this file system to mount on reboot and, of course, vim is not found just.

A

Bi wow, you just totally fresh boxed. This didn't they I I did.

B

Well, with the amount of trouble we had with with this thing,.

A

Last time I was just.

B

Like blowing it all away, makes.

A

Sense, that's cool.

B

Lv data, so we want to tell it where we'll do mount uh dash serve then xfs for file system just take the defaults and we don't need. uh We don't need to do a disk check. We can talk about that another day, but this is a typical layout for an entry in cfs tab. Fs tab handles the discs and partitions on boot, so the top line handles uh slash, so the the root file system directory the next the next line. There is the efi partition uh part of the boot process.

B

So now the the line that we just added handles the slash, serve and uh points to uh date of all dash lv data. So that's that's the disks that we've been working with so now. If we write that file kind of give us some space here and then do a mount dash, a mount dash, a says dash all basically and what that does. Is it tells your operating system to go in and re-read that scfs tab file?

B

So if we do a mount dash a and then we go check our serve directory, our text file is back.

B

So you can go through all of that and even lots of rigmarole.

A

B

Lots of uh lots of command line, kung, fu and, as you can see even I forget some of the command line, arguments or.

A

B

Know the package.

A

Or whatever yeah.

B

Well, yeah usually helps if uh usually helps if you're uh so yeah.

A

I mean you've shown us stuff. You've shown us how to do. It now show to show us how to do it under diverse.

B

Isn't that what we just did, I think so.

A

um I mean I didn't have vin installed.

B

Didn't have lvm2.

A

B

It will fix this lvm.

A

Go fix this lvm problem. First problem: it's not installed. Well, sadly, that's that's happened. I'm sure it has.

B

So you can run through all of that and it's great fun or see this is this is why I don't like uh how cockpit initially positioned themselves as the uh as the um sort of thing that window yeah. Thank you sort of the new administrator approach to managing things, because.

B

This is a brand new box.

A

B

It's got nothing on it, so so what you're looking at is the red hat enterprise linux, web ui, it's based on cockpit and cockpit, has a bunch of extra uh modules add-ons, and one of those, I believe, is cockpit dash storage, which gives us the ability to manage our storage from a web ui and, of course, there's not so we're going to do a dns search.

A

I can't tell you.

B

How many times I've had.

A

To do a tnf search, cockpit dash, there is storage d, yeah. Sorry I know where is? uh I probably should have caught that one as many times as I've installed it right.

B

Yeah, I'm I'm definitely with you there. um So it's going to install the cockpit dash storage d um and then.

B

Interesting, oh there we go okay, um so the next thing we're going to have to do is we're going to have to do a systemctl, restart, cockpit and log back in yeah.

B

So I wish I could say that all this was on purpose.

B

These are, these are teachable moments, but uh no, I just forget things like and make sure lvm2 is installed: yeah, okay! So now now we log back into the web ui and we've got our storage option yep and truth be told. I had probably forgot about the storage d package because I usually run an ansible playbook against all of my labs. That sets all this up for me right because I am a scatter brain systems administrator so but with the web ui with the storage plug-in, we can see our lv data uh already mounted.

B

We can see that it's using practically nothing of 28 gigs. So with that in mind, why not.

B

We're going to scroll over and we can see the actual drives that are installed on the system, so you can either run 27 different commands, of which each of the command line arguments are just slightly different enough to be painful or we can come into the web. Ui go into the storage plugin and we can come to that. 16 gig drive that we saw earlier and we can get all of the information right here in front of us. So there's it says, is unrecognized data because there's no file system on this device.

B

So what we can do is we can actually create a partition table. We can format the disk and I believe, it's under format that we can determine whether to zero out the entire disk. Xfs is the recommended default. We can do lv logs and we can put that at slash log.

B

We can do a mount now. We can set it to read only so if we don't want to be able to write to the disk, it can mount as read only but of course I say it's easy and then I forgot a step.

B

So we have that option right from the disk, but if we want to add it to our existing, if we want to add it to our existing physical volume group, we can do that fairly easily because we'll come in here to our devices into data vault and.

B

Going to come over here to physical volumes, we're going to add a physical volume to that, and it already says: oh hey, you've got a virtual disk here or you've got a you've got a physical disk here that hasn't been added to a physical volume. Would you like to add it? Just click the check box, click add and now, instead of running that pv create command.

B

We've already got a dev vdc physical volume, just with a couple of clicks.

A

B

Let's see if we go, we didn't want to click on that. Sorry, then we want to create a new logical volume.

B

We can call it lv.

A

Device file systems.

B

Oh, here's something I want to point out was that you can actually thinly provision a file system which means that, even though you're only using even if you create a disk, that's 20 gigs in size, you can actually uh you can. You can specify that a file system is 20 gigs in size, but you'll only be using the actual storage space within the device. So you create a 20 gig thinly provisioned file system and, if you're, only using two gigs of that then you're only using two gigs on the disk.

B

So it gives you some space, especially in a non-production environment, to over provision. um It's not quite recommended for production use unless you know exactly what you're doing, but this allows you to kind of resize volumes on on the fly, but we're just going to do a we're just going to do a block device for now. So we're going to create that logical volume which will add our uh so we didn't we, we have.

B

We created 28 gigs uh on our on our other disk, and so we've got 16. That leaves four left over. That's where the 20 gigs came from we're going to create that lv log.

B

So now, within our within our volume group, we've got two volumes: we've got a 28 gig lv data and we've got a 20 gig lv log.

B

So now, if we come in here, it should still shows unrecognized, but right from right from here, we can go through and we can create a let's call it logs, because we're super original and we'll just put in slash logs for now we're going to mount now and format.

B

So what that's done is it's gone in and just with that one screen that was like three or four of the steps that we did manually.

B

So now, if you come and look at your your file systems here, we can see that we've got our lv data with 28 gigs. We've got our logs file system, that's using 20 gigs of data, and then we've got a root partition, that's using two and a half gigs out of almost 64.. So it's so much easier to use the web ui than it is to jump through uh all the different commands, all the different arguments, um but there there is a.

B

I don't think, I'm I'm uh saying that the command line isn't important, because there could be more advanced use cases uh that would uh benefit from using the command line. There's there's a whole bunch of arguments that are available within the command line and use cases that aren't in the web ui either yet are aren't going to be supported like I, I believe it was just a version or two ago that uh support for raid volumes was added to the web ui so before about a year or so ago.

B

If you wanted to actually do a raid array, you had to do it on the command line, and then, after after you'd established your raid and created the physical volume group, then you could come into uh into cockpit and actually create those actually create those partitions using the web. Ui.

A

A

Where do we go from here? I guess is the question: how do we help people just remember the steps right like because you still have to like remember the order right.

B

um For me, one of the best things to do is just remember you start with the hardware and then because you're talking about physical hardware, that gives you physical hardware, physical volume and then then we're going more into the software side of things so think virtual and then logical because you're nice.

B

So it's it's easiest to remember, you're, going from from concrete to more abstract, so hardware, physical volume, virtual volume and then a logical or a volume group, and then a logical volume. On top of that, of course, then you just need to remember that there's a file system on top of the the logical volume honestly, the the best thing to do is to ensure that that you keep good notes. um My my evernote, my apple notes, my and now my joplin, some of those notes.

B

If, if you track their history back, are probably 12 years old, 14 years old, it's it's good to have those those quick hitting. I only do this once every six months kind of thing in order to uh to remember that. Remember those certain specific uh uh procedures so like when, when I was trying to do the lv command, I literally opened up. Joplin did a search for lv create and the only result in all of my notes was.

A

One note you needed.

B

Right yeah. Luckily, it took me right to the part of the note where it said: hey genius, it's it's dash, l, not dash b. um So I mean it is confusing. I I will grant you but.

A

Yeah no like having to do this like on the fly while on call before is not fun because yeah, it's do fill up overnight. Sometimes right yeah, it happens. It's great.

B

It's great when you have your headset on or or back in my day, you're you're doing this with.

A

Your phone yeah yeah.

B

And and your boss is yelling at you and you're trying to remember what the arguments are yeah, it's it's great fun to try and do this under duress I mean even just doing this on a casual live stream was uh was challenging. Apparently uh it helps to install lvm2 by the way.

A

Yeah, that's that's a good start to any lab about lvm um awesome. So a little a little riffraff in in chat get rid of sorry for that folks, um moving along here, any tips or tricks other than that. You know concrete to more virtual thing here or and and hey just install cockpit. You know.

B

If you're really.

A

Really under duress just install cockpit, you can uninstall it when you're done kind of thing. If you know push comes to shove, right, like.

B

Right, it's faster to do that than try.

A

And remember everything and if you screw up something, oh god, you.

B

Know yeah not that I've ever uh not that I've ever had to redeploy a vm or not that.

A

I've actually lost and.

B

Then reinstalled it or uninstalled it when I was done just so, the audit wouldn't come in and go what's this.

A

What is this web server thing here? Yeah? No, I I have. I am smart enough now to know that this is data. Sensitive operations and yeah. Sometimes there's a way to be safe about that, in a very literal sense. So.

B

Yeah to some of the more seasoned administrators out there don't be too proud to use the best tool for the job and, if you're, a very visual person like myself, it's easier for me to look in and see. I have these discs they're mounted here they have the nice blue bar. That tells me exactly how much space is available.

B

Don't don't be too proud to use the easier tool? There's there's the stigma about. Why would I take shortcuts or use automation to do this thing I I have to. I have to beat myself up with these command line arguments no.

A

You don't see in a perfect world, you would have just shown off a playbook that asks you the right argument right like seriously right, like you, can automate this. This.

B

A

You know, and you can you can say oh this is always my disaster scenario is adding more disk from the file. You know the filer that's off in the data center, adding more disks to this lvm group. You could literally just create an ansible playbook to do that when.

B

The alert fires.

A

Add more disks done, you know all right like or you know purge logs whatever you want to be.

B

Yeah but yeah we didn't- and I'm not even set up to to do this at the moment. But we didn't even talk about things like log rotate or just maintenance that.

A

B

Probably be a good topic is what are some of the common maintenance things outside of say. Patching that that assist admin might do longer is a big one.

A

Because yeah, if you deal with databases on your systems or any kind of like high churn kind of thing, log rotates a big deal right and doing that right and doing it. Well is a big deal. So that is a good idea for a show all right. I got no questions here. Just a.

B

Little bit yeah, I got, uh I got no yeah. I got no no questions in the chat. So do we want to move on to a couple of uh housekeeping items, some a couple of announcements that we've got.

A

Yeah sure go ahead, what kind of announcements you got.

B

So uh I wouldn't be much of a technical marketing manager if I didn't say that uh go to lab.redhat.com, because we have a growing list of activities similar to this one. uh There's one on file permissions, there's one on uh using image builder to create a template.

B

So there's there's a bunch of different things to do at lab.redhat.com. It's free! You don't have to pay anything. You don't have to sign up. You just go in kick off a terminal, a lot of times we a lot of times we use lab.redhat.com on this, show yeah for our our live demonstrations and, frankly, those have proven to work better than my home lab.

B

But but, needless to say, I assign myself a task of creating a disk management uh lab when we started planning for this episode, uh so you'll be able to do kind of what we did today on your own without having to spend any money or spend up any resources. So there's that then the other kind of housekeeping thing I wanted to mention or not housekeeping uh was uh rel. 8.5 is coming uh so ours. Our labs recently have been 8.4, but we've gone to a standard release cadence.

B

So, every six months there's a new minor version every three years, there's a new major version.

B

So as of yesterday, I believe rel 8.5 beta is out, and if you have a red hat subscription or a red hat developer subscription either one you can now get access to the 8.5 beta. One of our episodes, probably in november, will be about what's new in rel 8.5.

B

What are some of the cool new things you can do um so the the beta is out now. uh The actual release date is about mid-november. uh I'd have to double check. uh Everything. I've done is around the beta so far, so.

A

I knew yesterday, I know that feeling. I know that feeling trust me. That's all.

B

It was problems.

A

But I don't know when the actual releases.

B

We probably should have led with this, but we just kind of dove into our topic, um but uh this show, as of today is a year old.

A

Yes, it's pretty cool to have been doing this and it's it's gone through. Two hosts right, like it's name, show I'm not.

B

Not sure if we want to celebrate.

A

Well, no, I mean but like it, it shows you the you know, sustainability of it all right like it just takes somebody that knows rel to run. This show right.

B

A

That's that's really, the the key here.

B

I think the key is more, who doesn't mind when his lab blows up in the middle of a demo. That's.

A

True too, you kind of have to be able to sacrifice your home lab at any given moment.

B

I I distinctly remember an episode with the scott, where uh the the episode's guest actually had to jump in and say: oh, your demo broke no problem. I've I've been playing with this all morning, so here's mine, so I think.

A

There's a certain.

B

Amount of resilience that that's required.

A

Nice all right, so we've got getoff's guide to the galaxy cone up here at the top of the hour. Anything else.

B

uh That's all I had did you uh did you have anything just left to share? I.

A

Mean we announced it yesterday on the channel, but folks, I'm I'm leaving red hat to take an opportunity elsewhere. uh My last day is the 18th of october. um I I can point you to the interview that stu miniman did with me yesterday, where we talked about all things. You know openshift tv, you know more than a year later, right, like we have actual recurring, shows that are turning a year. Old rel presents as perfect example, but you know, ask and open shift admin get up, scotty galaxy, those all turned a year old.

A

B

A

Weeks ago and so yeah, it was kind of a nice episode to talk about the progress and then also to say that, yes, I am leaving the company here on the 18th, so I'll see you at cubecom but uh yeah. That's that's all I got for now um and thank you for dropping that link to the beta appreciate.

B

A

um So you want to rap or you're good.

B

Well, I just wanted to say thank you for uh for getting this uh up and running, because.

A

B

Be our last episode together, but but never fear if, if you're watching this, I intend to keep keep this going. I'm looking for a.

B

I'm I'm going to be looking for a co-host to to help me out and we'll keep this going. In fact, I think we're looking at writing up a listener survey to kind of get your all's feedback and and make this show better. um Obviously, once I'm done rebuilding my lab, we won't have that problem as much, but so never fear rel presents is, uh is going to continue uh we'll just miss uh we'll just miss you, uh chris we'll have to bring you back on as a as a guest or something.

A

B

Or just uh just do a roast of you in a few months that works too, but with that that's uh that's all I have, except for the. uh If, if you're watching on twitch- and you haven't heard, there is a big uh security breach so reset your password yeah, please that's that's!.

A

That's been forced upon you already.

B

Right yeah: that's that's our public service announcement for this episode, but.

A

B

That that's all I got chris.

A

All right well awesome, thanks for a great show, eric and coming up next on the channel getups guide to the galaxy, we're gonna be talking about advanced cluster security or advanced container security.

A

So hang on tight or as james samuel jackson said in uh jurassic park, hold on to your butts, um so stay safe out there and see you soon I'll.

B

Talk to you all later.