 Good morning. Good afternoon. Good evening. Wherever you're hailing from, welcome to another episode of Real Presents, Red Hat Enterprise Linux Presents. I am Chris Short, host of the most of Red Hat Live Streaming today. We're talking about Convert to Real, right, Eric? And we're going to start this demo pretty quick and then kind of work our way back, if that makes sense. Yeah, I figure out of a, out of an hour long live stream, we don't want to spend 15 minutes sitting there watching the terminal scroll by. So Hey, what a great idea. I mean, I think it'd be fun, but some some folks watching may not. So I figured we'd we'd start off just kind of talking about what is Convert to Real, dive into the demo and then we can kind of do some Q&A and talk a little bit more about why you'd want to even embark on on doing a Convert to Real on your systems while the while the demo is kind of running. So the the objective is we're going to start with the CentOS Linux 8.4 virtual machine. And by the end of it, we're going to magically have a Real 8.4 machine. Nice. So with that being said, let's dive in. So if you're not sure what we're doing, bear with me for just a few minutes here as as we kind of talk through things. Nice. Helps if you log in first. Logging in is always good. Look at you with your fancy shamancy root password. And and and I learned from our last episode. So you'll notice that my virtual machine today is not called Real 8 or something generic. It's called Iron Man by by popular demand. Okay, cool. There were two votes and it was you and me and we said Iron Man. So there we go. That's how we make decisions around these parts. All right, pretty much. So do do a cat on the release files and we'll see that that I have nothing up my sleeves. I do have sleeves, but there's nothing up them. No trickery here. It's it's a rel fedora like system. We're running CentOS Linux 8. And then and then if if you were we're so inclined, we're running 4.18. That's a whole bunch of stuff for the kernel version. So as you can see, no no trickery. And and since we're starting with CentOS Linux 8, there's no need to make sure that we're registered because we're not registered yet. So we won't run into a problem like we did last time where we won't run into a problem like last time where where we have to unregister and re-register register a system on air. So we're we're learning here. Yes. We can learn. We can be taught. We can be taught. So the first thing we need to do is Eric needs to learn how to talk and type at the same time. So the the first step that we need to do is convert to rel is a supported operation for as as a Red Hat customer. So there is a convert to rel repository where you can go and get the official packages to where you can check the GPG keys, make sure that you're getting what you think you're getting instead of instead of just Joe, Joe and Jack's GitHub repository at some random URL that may or may not be the official package. So to avoid all that bash with sudo to all of down to yeah. Yeah. Yeah. Yeah. Always check what you copy and paste. So I just pulled down the GPG key using curl and then our next command will actually pull down the repo config file. The fact you have this memorize is kind of impressive. I would love to let you think about that. No, you don't. But I can't let you do that. Okay. I've got I've got my notes just off screen here. I mean, yes, I totally have all the memories. Totally just have this all the memories. Although truth be told, I've given this demo enough times. I could probably do it from I could probably do it from memory or at least pretty close. Now here's your chance next time. Next time you get to it. All right. So so in well in two weeks. Oh, so I should I should probably admit. Oh yeah, that's a good point. We we talked about doing a day in the life interview, but the the guests that we we'd asked to to come on the show weren't available this week. So we're we actually punted that topic. And we we pulled this one out of reserve by popular request. Last I think two weeks ago, we had someone asked for a convert to rel a conversation. So we're doing that one today. And then in two weeks, we'll do a day in the life of an operating system engineer. But there's one other caveat. It won't be on Wednesday. It'll be at the same time, but it'll be on Thursday. The next couple of episodes will be on Thursdays. The next two episodes specifically. Yes. Yes. Next two episodes will will be on Thursdays due to some scheduling conflicts on my part. Anyway, back to this. Yes. Thank you for the programming note. I appreciate that. Yeah. More so you remember than than our audience. So if we if we can out the convert to rel repository file, we we see it's pulling straight from the Red Hat CDN. We're doing a GPG check. So we pulled down the repo file and the GPG key. So we should be good to go there. And if you don't do this, this is like rebooting a system for packages. I pretty much anytime I do some kind of an operation, I do a YUM clean all ahead of it, just to clear out any any temporary files, anything that's partially downloaded. And if nothing else, it just makes me feel better just knowing that I'm starting fresh. It's it's probably good practice, especially when you've added or and or removed repositories to just go ahead and clean out that cache. Yeah. Yeah. I mean, I I'm one of those people that YUM clean alls or YUM cleans all quite often just because I don't like having that cruffed around. Right. Like I'll do a YUM clean all when I need like five megs of space. All right. So then because I'm lazy and don't want to tap why later in the command, just do a YUM install dash Y convert to rel, that'll pull down the utility, all the dependencies. So it's the downside to YUM clean all is it does have to pull down its its index of all the packages from each of the registered repositories. But I cannot tell you after a decade of being the patch guy at just about every job I was a systems administrator for it became a running joke. Really. I'd started a new job and it's like, Hey, we've we've been trying to we've been trying to nail down our patch cycle. Can can you help us with that? Well, funny enough, that's what I did in my last job. And just over and over, I ended to be coming to patch guy. So I don't know how many times I've been sitting on on patch night and trying to get updates to run and just won't work and go figure YUM clean all it fixes it. So it just it became kind of my my tradition to just YUM clean all before I do anything with packages. Yeah, good call. Managing chat here a little bit folks are asking about syntax. Call it ask what about the episode about session recording using T log and cockpit? We talked about that. That's on the list, right? It is indeed on the list. Yeah. I'm looking forward to that one because it's really cool. I've actually started using T log for some of the some of the screen recordings I'm doing for for content. Nice. So it really comes in handy for a lot of things. That is a long ETA. Oh, yeah, that's and up. That's weird. You got kids at home. And not at the moment. Not at the moment. Okay. Most of them are in school. One one should be sleeping. So right. That's okay. Five. Sorry. 1.5 meg and it's that's why 25 case. Yeah. Like I said, the downside to doing a YUM clean all what is your well never mind. So if any of you work for Google Fiber, if you could up my my pipe for the next hour, that'd be great. Oh, that's Google Fiber. Yeah. So I'm I'm thinking that may be on CentOS aside. That's can always reboot. That's like when you push the elevator elevator button over and over and over again. So the car comes there faster. So you in my mind it makes things go faster. You're not one of those people that flashes your light at a red light at night, aren't you? I've actually not not heard that one. Of course, it comes from I was I was bragging about the fact that we'd we'd overcome some of our previous issues and we're going to have a smooth demo today because that's that's what happens when when you anger the demo gods. Yeah, you might want to kill this because it's not getting any faster. Try again. I don't know. That's weird. Yeah. For a second that bar loaded all the way. I was like, no, you're you're kidding, right? Right. Okay, that's fun. What is your height or connected to? This is this is my very nice workstation running a virtual machine right here locally. And I have I'm the only one in this house. My workstation and my server are connected to connected via cable. Everyone else connects via Wi-Fi. That is a good point. I did have to split up my Wi-Fi and wired networks a couple months ago because y'all on your Wi-Fis over there. Yeah, like this is a two gig connection here, ladies and gentlemen. This is this is embarrassing. Maybe you should. Worst, worst case, I can restore my backup QCOW two file. And you did this before? Uh huh. Well, interesting. Even even speed test says I'm getting 84 meg down. 94. Yeah, I wouldn't can imagine 15 kilobytes a second. This is this is wonderful. Yeah, this is truly odd to be honest with you. Okay, that ain't gonna fly folks. Let's just for trends. Okay. So I've got a new goal for the quarter, Chris. What's that? Just just now I just wrote it. Oh, yeah? To have a live stream that actually goes smoothly. Oh, okay. Um, so you know, that happens around your fifth or sixth episode. Just to let you know, hopefully that lines up with your quarter. Oh, let's see if a reboot fixed anything. Probably not. Yep. Wow. Awesome. Okay. So, um, when all else fails, just blow it up and try again. So while I'm doing this, I don't know if you all noticed, but, uh, we had gentlemen by the name of Jared, who was an intern on our team over the summer, created some new, some new images for the show, as well as created a new bumper. So we're we're flying high now with yeah, you've got your well presents bumper and you got your own scene and OBS now full ground program. I feel, uh, I feel special. Love. I do. I feel a lot of love. Copy that QCAT two file. This time we will run the risk of not doing a, uh, how are this guy back up and reshare that? I literally ran through this, uh, do this very exercise not two hours ago and, uh, had no such issue. Right. Well, just to remind folks, uh, drop a link and chat for you. You can get your own copies of rel for free fully subscribed up to 16, I think is the, uh, number, with a free developer account from red hat. So go to that link register. You'll have an account on developers at red hat.com or console.redhat.com and you can then download your free copies of rel for development use. Don't go to prod with them though. You'll be violating the license. That's all I ask. I'm not connected to the internet on this one. Oh, no way. It's saying this is failed to download metadata repo for eight RPMs. Cannot download. That's weird problem with, well, the key is bad. I don't think that's the case. Just try it again. Sorry for the dog folks. Mine got kicked out, uh, just few minutes before we went live. Okay. And we'll check my spelling here. Interesting. This is awesome. This is great. The funny thing is, do a dash K dash O just ignore the cert thing. Well, no, I guess you can't the young command. You have to do like a dash dash ignore SSL or something like that. And that's just dangerous. So, right. Willing to bet. I made a typo somewhere and I just didn't see it. Funny thing is we're having trouble with something as simple as a repository instead of the actual conversion process. Yeah. Needless to say the conversion process actually runs very smooth. We hope. Do we dare do it? Oh, for crying out loud. Well, this is fun. So you're having internet connectivity issues. You know, what's funny is, now we had some bad storms roll through here last night. We were thinking, you know, and preparing for the worst as usual. And like we had like the lights dim and then, you know, the power went out for like a few seconds and it came back on the internet went out for like a total of three minutes. No big deal. So we were like, okay, we got off unscathed and turns out everything else around us got like hammered and like max's school is on generator power this morning. First thing and just all kinds like, you know, every stoplight between here and there was, you know, flashing yellow and red. It was just like, wow, okay, everything. But this one neighborhood, even like the back half of our neighborhood doesn't have power. It's like, wow, that's one little part of the neighborhood. Okay. All right. Well, whatever I did on those trouble tickets, they fixed it good. So yeah, I actually have a status page for my house, because Comcast was so bad at one point, I had to prove to them, fix something. It's not between the house and the curb. I promise you, right? Well, let's see. I could always, you could find the file and then move it around locally, but you're still reliant upon your internet connection. Yeah. Hey, are you doing anything to take the entire internet? Right. There's apparently one iPad in use in this house and I can't imagine that would produce the results we're seeing here. Let's see. Just for grins, I'll share what I'm working with here. Yeah. Okay. So I've got SSH keys set up. I don't have Tmux on that box. I don't have Speedtest on there either. What kind of a lousy systems administrator have I become? I have no idea. Oh, geez. Make me a sandwich. No. Pseudo make me a sandwich. Seems pretty fast. I mean, okay. Okay. So what we're going to do is we're going to blame Zoom for that. Okay. Is that what we're going to do? Well, I mean, 24 Megdown versus 640 Megdown for my server. It's just one switchboard away, literally. Okay. Well, that'll do it. Okay. So let me think here. Never thought a 1080p connection would bring fiber to its knees on just one box. It's because it's technology, Chris. Of course. Technology. Of course. Oh, well, here's the thing. I just have Speedtest and got my max pipe. I'm on the same Zoom. Okay. So quickly behind the scenes here, I want to switch to my other cockpits. This is why I don't do things on my local workstation. That's why I do everything in the server lab. I should learn from my own lessons here. Yeah, if I were doing this, it'd be on my local machine. And we were talking pre-show. I had a tab running like 200%. Come on. Let's see. I think it's under images. It is indeed. Awesome. Okay. Cool. You with me? Maybe Eric's internet went down. This is just loads of fun. Yeah. What just happened? Zoom crashed. How? We're just having all kinds of fun today. Well, you know what you should do? Just for like disconnect from Zoom, install what you need to install, and then reconnect. Because apparently that is the problem. Well, we're actually going to do like I suggested in the first place. I'm going to just do this from my server. Why not? So this is cockpit here. And so we're going to do ascent rail 8. So I keep the naming. You put six megs of RAM on its rail box. It's going to be its problems. Isn't system administration fun? It is. That's why I don't do it anymore. It's just too much fun. So much fun. All right. That is odd, though. I will say, like, very odd. Okay. I'm clean all. You know, you want to do that. I do. Now, here's the real test. Is it really Zoom? Yep. Nope. Oh, wait. Okay. Okay. No, that's just about the wrong image. Yeah. This got the right image, but I didn't reset my lab environment here. So, so I'm going to, instead of switching back to my terminal here, I'm going to move that file. I'm going to pseudo remove that file. Once you get all the environmental issues figured out, it's pretty easy. Promise. Right. Promise. Trust us. Yeah. We're experts, I suppose. We heard the professionals here. Right. From the government, we're here to help. Okay. So, restore my backup. I at least did that much. Yeah. Okay. So, you know, your backups are good. First thing. If I type in my username correctly, then we're good. So, what should we be seeing right now? Because we're seeing cockpit. Yeah. I just restored the backup. I guess I could let you see what's going on here. I'm trying to spare everyone from any further confusion. Yeah. Mostly myself. I'll shut up now. I'm no worries. Did I do that backwards? I thought you said your backups were good. They are if you put them in the right directory. Yeah. It's my workstation because that's going just fine. Okay. So, I want to stop my share and see if that helps my speed any. All right. So, if this doesn't work, what are we sacrificing? Let's see. Anyone have any animals that they don't want? I think the demo guides are required. There you go. That helps a little bit. I'm going to kill my video too. I'm still here though, but I'm just watching my backup copy from my workstation. Is it backing up or restoring faster? Yeah. The ETA just dropped by about 50%. So, we're about a quarter of the way there. That's really weird. I'm starting to wonder if it may be the cable I have going between my desk and the switch in the basement. Oh. That is fun to troubleshoot. You need a couple thousand dollars of test gear for that, or just re-terminate it. Yeah. That's probably the first guess. Although, Kourtney, in the chat suggests... That is a good question. Yeah. Yeah. It may be time for a fluid change. Yeah. I've got to get that router juice going right. Of course, I think Kourtney just decided to join us to troll me. I mean, you know, the fact that Zoom can take down your home internet connection. Supposedly, I'm the one with bad internet on the channel. I'm just going to throw that out there. Is it my desktop? I think my desktop even has a 2.5 gigabit nick in it. If you don't have a 2.5 gigabit switch fabric throughout your house. Yeah. Switch is only one gig for now, but I've got my eyes set on a 10 gig switch for the basements. This is ridiculous. I do this for a living and I have not had this problem. Oh, this is why we say, you know, one of our tips, you know, pre-show, before we go live, I typically tell people three things. One of them is, you know, failure is great. We all have to see failure because failure teaches people how to troubleshoot. Just didn't realize it was going to be this kind of troubleshooting. Two weeks in a row or two episodes in a row. But like, you know, like teaching people troubleshooting is hard. Like you have to actually break something usually to teach people how to troubleshoot something. So yeah, this is like on par on brand, I guess. Just not quite how we expect it. Yeah. I mean, maybe we rebrand, REL presents to be a live coding activity instead of, well, we have two seconds left. Okay, you can do it. I believe in you. All right. It might be misguided faith, but I believe in it. Normally, I would argue, but your faith may actually be misplaced today. Oh, goodness. Okay, so the backup is there now. Can I cap it over? Yeah. All right. I'll be back on video here in a second. I've No, I believe you. Time to beat my head against the desk a few times, which I think helps. Okay, just as long as you don't give yourself a concussion, you're going to hit your head as much as you want. All right. Let's try this again. Let's look at cockpit here. Okay. All right. Hey, it did stuff. Okay, that's sent to us. We're making progress. We're getting there. I are smart. And what I'm doing? I are smart. I think I can. I think I can. I thought I could. I thought I could. All right. So this is the backup from my workstation that I tested this out on. So let's pretend this was 34 minutes ago, folks. Right. Yeah. I apologize, folks. This is ridiculous. Hey, same problem. No. Yes. Yes. Oh, good Lord. Wow. How could it be a problem with my image? Oh, geez. Now what? Did you launch the wrong? I was in the wrong cockpit. Okay. That one goes away. Yeah. Okay. Cool. Okay. Sent to us. Linux 8. Okay. All right. So you work at Redhead, right? I did until this live stream. No. All right. I believe I don't want to come up and see what happens. Oh, hey, that can be real quick. All right. Let's tempt fate now. 13 makes a difference. All right. We are in business 36 minutes into this. We are in business here. Don't use local machine. Yeah. Note to self. Don't use local machine. Okay. Grab my notes and we'll be, because I don't remember what that URL was. Okay. There it is. All right. Okay. Well, I know you need to install convertor that I know. Yes. So once again, if you're following along at home and haven't, although give me a second here, because I can't read my notes with the way I had all of this planned out. Yeah. Networking. Okay. Never mind. I won't say that. Don't jinx it, Chris. No, I'm trying not to. Everybody needs to start believing right now. This doesn't work. I'm blaming Courtney. Fair enough. Courtney will have to come on the stream next and explain themselves. Same thing is when you're connected into the terminal like that, copy, paste doesn't always work. I thought, oh, that's no big deal. I'll just share the terminal. Won't be a problem because I only need to type both these commands in once, right? Right. Yeah. Six tries later. Convert to rail. Pseudo. No at your root. Oh my God. Path or access rights. So which is access rights though? Do just a straight up curl, no out on the CDM on that little, you know, your repo that you're trying to actually hit. Yeah. Does that like actually work? Okay. Okay. Yeah, that should. All right. Okay. And then you have this file. Let's make sure that that's not broken. Mm-hmm. I probably broke it with all these attempts. That looks good to me. Wait, check that you have that SSLCA CERC file. Because that is looking at local host. I don't know if you would have that. Okay. So we don't even have that directory. But that's a problem. I haven't needed that before. Comment that out. I bet it works. Repos, convert to rail. Don't try that at home, folks. Not typically suggested. Nope. I was wrong. Okay. Can you curl the repo and defile? Because that would be a red flag. Interesting. Okay. It's a self signed CERC. That's weird. Okay. Crazy idea. Just struck me here. Go to a mirror. What? I don't know. Actually, better. Give me a second. Give me a second. Okay. At this point, I'm just going to cheat. Aw. I should have thought of this sooner. But coming soon to a Red Hat YouTube channel near you is a series that we're calling rail tech tips. So it'll kind of coincide with this show. So there are CDN about redhat.com is rocking a bad shirt. Oh, lovely. So coming soon to a Red Hat YouTube channel near you is rail tech tips. And it's going to be short five to 10 minute videos that hosted by yours truly that walks you through how to do a particular operation, whether that's a convert to rail or an in place upgrade or we've got some changes to image builder that are coming out here soon. And those I'm going to have very well edited videos coming out walking you through very specific operations. So what you're seeing now is VLC pulling up the screen capture from that tech tip video. I should have thought of this sooner. This one I can guarantee will work because And in a lot of time. Yeah. Yeah. Exactly. Actually much quicker. So I've counted out the Etsy release file. I've curled the GPG key. And then as we hit play on this video, I do have a trick up my sleeve apparently. We pull down the, we curl down the convert to rail repo file. We install convert to rail and the dependencies. And look how fast that worked. So I'm going to pause it right here so we can talk about the command itself as soon as the little thing goes away. Come on, VLC. Cal is asking how to convert from Ubuntu to rail. So currently Ubuntu, Suse and some others aren't supported because they are just too far different. Right. This only works on Oracle Enterprise and CentOS at the present. Because they're both rail clones. They're both very rail like. So there's a lot of similarities between the two. You see if I can back up here and grab the top of that command before it just blows away. You are correct, Khaled. Convert to rail does not support Debian based districts. Just because there's so much difference between them, including the package manager, which is kind of important. Hope there it went. So at the very, very bottom of the screen, I apologize for the size. But we run the convert to rail command. You can do this with an access key or with the username and password. So I put in my red hat access ID and then I added the argument for dash dash auto attach, which will pull down a valid subscription and the appropriate repositories. So I don't have to run that as a separate command later. It asks you to read the Yula, which I'm sure we all do. And then it starts to go through and backs up all of our repository files for CentOS. It archives the CentOS. It's actually going faster than I could talk. That's impressive. It's a few seconds ago, it's backed up all of the the GPG keys for CentOS repositories. And so now what it's doing is it's going through and it's replacing some Python libraries. What convert to rail does from a high level, sorry, I'll get back into my talk here now that we've subverted all of the issues we've seen today. What convert to rail does is it takes all the CentOS built packages and replaces them with rail specific packages. So if you have a kernel package or a Python library that was built by CentOS, it pulls that package out and replaces it with something that was built and signed. That's the key built and signed by Red Hat. So when you download the GPG key, that's what that GPG check is during a YUM install because it's verifying that the signature on the package and the signature on the key match so that you know where it came from. Nowadays, one of the biggest security concerns we see in the industry is this whole insecure supply chain. So whether it's and it's usually not the application itself. It's usually some upstream library that someone just did a get clone on and started building off of that had been either. Either a lot of times you'll see something that's spelled very closely to the official library. So if you mistype it, you get the compromise package as opposed to the official package or someone has actually compromised the official repository for one of those upstream libraries. So that is one of the biggest reasons why you'd want to do a convert to RHEL is so that you get that support. If something goes wrong, Red Hat is there to make sure that things are fixed. You've got Red Hat's security team that's constantly running scans, checking packages, verifying key integrities. So having Red Hat manage your operating system versus say CentOS just ensures that extra layer of protection. So that's what it's doing here is it's installing the subscription manager package and some of the Python libraries. We'll go ahead and hit play. Check in the chat. So here towards the bottom, it auto populated my username and so I typed in my password all without touching the keyboard. You're so fancy. You've gone from can't function at all to now like somewhere in the ether. Yeah, exactly. So now it is going out to the Red Hat's subscription service and registering my system, which is sent to RHEL 8. Very creative name here. It's enabling the repositories that we need. So that's the RHEL 8 base OS and RHEL 8 AppStream repositories. See, it just verified all of the available repositories. So if we were doing, if this system required, say, the Bluster, for instance, repository, it would make sure that we've got that repository available, although it's not enabled now, so it's not going to be enabled after the fact. So there's several checks within the Convert to RHEL process that it asks, hey, are you sure this is what we're doing? You can still walk away. So right now it's just told us that it's backed up several of the repo files and now it's getting ready to replace the repos package and the CentOS Linux release package, which are the core components that give an operating system its personality, whether that's Oracle, CentOS, or RHEL, for instance. So we'll go ahead and say yes to that. And then the Convert to RHEL process goes in and grabs the core kernel packages, any modules that we have, and it says, hey, I'm getting ready to replace these things that are starting to get kind of real here, because I love the error message. It says, basically, there's no turning back unless you reboot and restore from a snapshot. So here Convert to RHEL successfully imported its GPG keys, unlike whatever was going on with my demonstration. It's installing the Red Hat kernel and so, of course, kernel 4-18 took a few seconds. Now it's replacing the CentOS signed kernel package, core package, tools, modules with RHEL. Let's see what else is going on here. I'm just going to touch G-Lib C at some point. G-Lib C is in the next batch before it does that. It's actually just created a bootloader entry on our grub screen. Nice. This all makes sense so far. Kernel modules, it has to do this in layers if you were to go through and replace all of the packages at once. It would break. Yeah, something would stop. The equivalent of crossing the streams and very good point. Things like that. Staypuff Marshmallow Man would come out to Marshmallow City. We don't want that. That's still one of the funniest lines. What did you think of? What did you do, Ray? I only had one thought. Like a ball thing. Now it's going through and it's replacing a lot of the core libraries. Saw OpenSSH go by. Some of the core Utils, SSSD. Then there's the Red Hat Release Package. Let's see what other goodies were in there. There's your G-Lib C. Just got installed. And so here's one of those points where we can kind of fast forward because there's 766 steps. And through the magic of video having already done this, I'm going to go ahead and skip through. Yeah, this part takes a bit. Well, you know, it's just reinstalling 700 packages. Yeah, no big deal. So while that's kind of picked up a little bit, it's in the cleanup phase now. So one of the questions that I get asked and you can't really tell today because of issues, this process usually, and this was a smaller VM than what I was going to use today. So it's got a few less cores and a little bit less RAMs than kind of your standard server would have. The question I commonly get asked is how long does this process take? And it usually depends on what it's writing. It depends on so much. Clearly, it depends on your connection to the Internet. Or your use of Zoom. Yeah, or using Zoom on the same system. But under like this particular demonstration took about, the video itself is about eight minutes long. So right around eight minutes to do a conversion. This is a very vanilla system, a very small system. So that time is going to fluctuate based on how many resources you have available. Right, how many packages you have installed. How many packages you have installed. So this doesn't have anything, not even like a web browser. So it's a very, very small from a package perspective. But on average, we've seen about 10 to 15 minutes. And what's great is if you're a satellite customer or if you're heavily using Ansible, you can actually, especially satellite, has either has now or will with 6.10 have one click support for doing convert to rel. So if you have a bunch of CentOS systems, say you want to convert your dev environment over and see how that process goes, you can do a couple of tests manually like this. And then after that, you can select groups of packages, or groups of servers to do this. And it's, as you can see, after basically after the initial command, it was all hands off up until this point where it says, hey, it was successful. It's gone through and replaced all of our packages. There's an archive of all these logs under var log convert to rel. Now to actually use our new system, we need to do a reboot. So if we go ahead and play the video, by now the server should be back up and we can reconnect, type in our handy dandy password, and then get ready for the fanfare and the to does because we are now officially running Red Hat Enterprise Linux 8.4, which means that our system is fully supported. We get all of the support, all the sign packages, all of the benefit of having a full blown rel system. You can pick up the phone and call for help when you can't connect to the repo. Yeah, although I don't know that Red Hat can help you if Zoom isn't cooperating. Yeah, I still don't get that. I still really don't put that at all. I don't know why that happened. Very weird. But yeah, I mean, it's despite all my issues, it's actually a very easy process. It's very straightforward. There's a lot of posts out on access.redhat.com that talk about common issues that folks have seen and have answered. So we may even, in the description of this video, put a timestamp for when things actually started working. So if you come back to this video. But I mean, we could do it again sometime, you know. Yeah, well, we'll probably revisit this. I know coming up soon, there's not so much changes, but new features coming to Convert to Rel. So maybe once 8.5 goes live, we could revisit this. And it may be in a maybe not full hour, but at least kind of. Or just check out detective video when it comes out. That works too. It's about seven and a half minutes long. And if you can't tell, I talk fast. So you can fast forward through that fairly quickly and see this process from start to finish. And you'll have already seen the footage. A lot of it anyway. All right. So now that that's done, any questions, anybody? Why it took so long? We don't really know or understand. Yeah, I'm going to try replacing the cable first, which means I get through the floor, through my garage, into the basement. It'll be fun, but y'all are worth it. So. Well, you're worth it because not just us. I mean, the bra mirror. That's weird though, man. Like that's kind of. I've been on meetings all day. And I know, right? Like you shared my screen. Others have shared their screen. You would think you would have noticed something by now, but I wonder if like a crosstalk problem, maybe, or just like interference from like a power cable. Maybe I don't know. That's weird. It's very odd. Yeah. All right. Like that's that's an unusual thing. I just I blame live live demos. I mean, that's yeah. I mean, that's got to be the thing, right? Like I forgot to do the sacrifices this morning to the demo right here we are. Sadly, when when I was in sales for GitLab, I thought I was set. It was one of my first demos live to a customer right out of right out of right out of onboarding and bootcamp and all that kind of stuff. I was I was ready to go. I had I had my my my demo in my home lab. And if that one didn't work, I had GitLab.com and I actually had I'd pre run a pipeline. So I was like, here, this is how you make this change. And if something should go wrong with with the with the pipeline, I've got I had a second one, you know, kind of like kind of like a cooking show. Yeah, second cake in the oven kind of thing. Makes sense. And so I had I had three layers of redundancy, which my operations rather than out there can say that, you know, three, three is good, four is better, but three is good. Yeah. I thought I was set. Get into we go through the sales part of the conversation. The guy hands it off to me. He's he's a new account essay. He's he's going to be on your on your account moving forward. And he just kind of wants to talk you through what, you know, this new pipeline feature, whatever it was. Yeah. And started my demo off and pipeline wouldn't wouldn't kick off. It wouldn't start a new process. Okay. But it's okay because I prepared for this went to the other project. Couldn't couldn't kick off the couldn't kick off the pipeline couldn't figure it out like, okay. So you've seen the process up to the point of of kicking off the pipeline. Now I can go to to my to my other other backup, where I've already run this process. And I as as much as I'm sitting here in front of you right now, virtually get labs, get lab CDN went down. So get lab.com was unavailable for like 10 minutes. That's like, I swear, of your thing. Of course. Yep. Well, folks, this has been another wonderful episode of Red Hat Enterprise Linux presents. I'm for short. You can find Eric on Twitter and tweeted him, not me. Send all your hate mail to Scott McBrion at redhat.com. There you go. That's his fault. So yeah, thank you all for tuning in. Really appreciate you sticking with us through this. In two weeks, no live demo, just live conversation. Just conversation. Bring your bring your bring your questions. We're definitely hoping to do some live Q&A. Absolutely. So awesome. All right. Folks, stay safe out there. We will see y'all in two weeks on Thursday. Remember on Thursday, two weeks on Thursday.