1 00:00:00,000 --> 00:00:06,480 Previously on LTT, I tasked Elijah with 2 00:00:03,400 --> 00:00:08,360 the impossible. To build an eight V8 3 00:00:06,480 --> 00:00:13,920 gaming setup that can be deployed in just 30 minutes for whale land. And man, 4 00:00:11,360 --> 00:00:17,560 it has been a painful month and a half sourcing parts, fitting it all into the 5 00:00:15,560 --> 00:00:21,440 server rack, validating power, cooling, storage, and even networking, and 6 00:00:19,520 --> 00:00:27,040 deploying it here at Smash Champs kind of sucked. Linus, Ow. 7 00:00:23,600 --> 00:00:27,040 Linus, you can remove your blindfold. 8 00:00:27,120 --> 00:00:33,240 Holy Wow. 9 00:00:31,480 --> 00:00:36,800 We got red versus blue racks. >> Yeah, and there's enough room in them 10 00:00:34,880 --> 00:00:41,440 that we could double this next year. >> Shut up. >> Yeah. 11 00:00:38,840 --> 00:00:45,440 Well, we don't get to game yet, though. Wait. I don't even get to game on it? 12 00:00:43,880 --> 00:00:49,240 Not yet, because first we need to talk about the super cool deployment system 13 00:00:47,240 --> 00:00:53,320 we used, because theoretically, it will allow us to handle the updates and 14 00:00:50,880 --> 00:00:57,640 maintenance of all 16 computers as fast as you could normally do one of them. 15 00:00:55,400 --> 00:01:00,400 Okay, fine. But I bet it can't update as fast as I can do the segway to our 16 00:00:58,720 --> 00:01:05,800 sponsor. I have to be fast because I have a 17 00:01:03,000 --> 00:01:10,440 mission, and no matter how hard they try, they'll never stop me from 18 00:01:07,800 --> 00:01:15,000 spreading the word about how Odoo has all the business apps you need in a 19 00:01:12,320 --> 00:01:20,280 single subscription. I'll carry word of their 15-day free trial until my legs 20 00:01:17,480 --> 00:01:23,400 give out, which they won't, of course, not ever. 21 00:01:30,560 --> 00:01:36,520 When we left off, we had chosen all of the hardware and just needed to figure 22 00:01:33,840 --> 00:01:40,400 out how to pack 16 systems into a quick deploy rack and simplify system 23 00:01:38,760 --> 00:01:43,720 management. My original instructions were to keep everything as dense as 24 00:01:42,040 --> 00:01:47,320 possible, and based on these early mock-ups from Justin, it looked like we 25 00:01:45,720 --> 00:01:52,000 could have gotten away with about eight gaming systems for every 12 uses of rack 26 00:01:49,840 --> 00:01:57,440 space. It's pretty damn good. Too bad it didn't happen. See, the Radeon 970 XT 27 00:01:55,000 --> 00:02:02,520 Prime GPUs we ended up with were just a tiny bit thicker. I'm not complaining 28 00:02:00,080 --> 00:02:05,880 since ASUS sent over all of these cards, and honestly, it forced us to rethink 29 00:02:04,600 --> 00:02:10,720 the design in a way that I think is going to vastly improve the thermals of 30 00:02:08,560 --> 00:02:15,840 our entire setup. And besides, it gives me an excuse to have two racks in the 31 00:02:13,240 --> 00:02:18,560 iconic two colors. We got these server racks sent in from Hammond. They're 32 00:02:17,280 --> 00:02:22,720 actually the same guys who got the orange server rack here at Labs, and 33 00:02:20,880 --> 00:02:27,320 I've heard they've done something very special to them considering this one's 34 00:02:24,760 --> 00:02:31,080 named blue Q assembly, This one says red. 35 00:02:27,800 --> 00:02:32,080 >> red Q assembly. Oh my goodness, this is 36 00:02:31,080 --> 00:02:36,600 so Wow. That's a very deep red. 37 00:02:35,200 --> 00:02:39,840 We probably could have guessed that by red assembly, but this looks That was 38 00:02:38,600 --> 00:02:44,880 gorgeous. >> Okay, I want to see the blue one now. >> yeah, yeah. 39 00:02:43,120 --> 00:02:51,160 Oh, careful with this. What, towards the camera? It's a 3D experience. Ooh. Wow. 40 00:02:48,680 --> 00:02:57,440 Red versus blue, baby. I love this. Oh, would you look at that. Holy cow. That 41 00:02:54,600 --> 00:03:02,160 is gorgeous. Oh, these are sick. These are awesome. 42 00:03:00,760 --> 00:03:06,160 I think it's safe to say we're going to have enough room. Our goal from the 43 00:03:03,960 --> 00:03:10,920 original plan is to have all of the IO of the motherboard and the GPUs on one 44 00:03:08,520 --> 00:03:15,760 side, and then the cables, we might have to remove the doors or cut a hole, but 45 00:03:13,560 --> 00:03:20,520 we want the cables to come out from here along the lines of our gaming stations. 46 00:03:18,120 --> 00:03:22,880 Each rack is for each team. So I guess on one side we'll have it and on the 47 00:03:21,680 --> 00:03:26,000 other side we'll have it. And then at the bottom here, it actually looks like 48 00:03:24,720 --> 00:03:30,600 we're going to have pretty decent ventilation. We want a line of fans 49 00:03:28,720 --> 00:03:34,360 because we want as much air flow as we can. Normally with the server rack, you 50 00:03:32,520 --> 00:03:37,440 have the air coming in the front and blowing through to the back. In this 51 00:03:35,880 --> 00:03:40,400 case, because of how we're going to have our motherboards and our GPUs laid out, 52 00:03:39,240 --> 00:03:44,880 we're going to go for more of a bottom-top design. I'm going to leave 53 00:03:42,840 --> 00:03:48,120 this in your hands now to finish building it, and I'm going to talk to 54 00:03:46,720 --> 00:03:52,720 you guys about how I'm going to deploy the operating system and the games, cuz 55 00:03:50,120 --> 00:03:55,640 the plan has changed just a little bit. I still want to go with diskless 56 00:03:54,000 --> 00:04:00,240 booting, meaning there's actually no drives in our machine to save on both 57 00:03:57,440 --> 00:04:03,920 cost and management complexity. My intention was to run something 58 00:04:01,960 --> 00:04:08,000 similar to Kenton's gaming house since he did document everything, but if 59 00:04:06,120 --> 00:04:12,440 something goes wrong, I don't want to have to rely on calling Kenton or hoping 60 00:04:10,440 --> 00:04:16,200 he updates his GitHub scripts. I'm sure he would, but we needed something that 61 00:04:14,280 --> 00:04:19,959 was hopefully guaranteed to have long-term support. 62 00:04:17,760 --> 00:04:25,080 And that's where GG Rock comes in. These guys make purpose-built software for LAN 63 00:04:22,880 --> 00:04:30,480 centers and e-sports events. That's us. And the best part is that if I fall down 64 00:04:27,640 --> 00:04:33,680 the stairs again, What was that? Totally ate it. They have 65 00:04:32,360 --> 00:04:37,120 a support team that our events coordinator, Chase, can reach out to 66 00:04:35,800 --> 00:04:40,000 anytime he wants. 67 00:04:40,000 --> 00:04:45,160 I mentioned in part one that I would need a high-speed storage server in 68 00:04:43,160 --> 00:04:48,720 order to network boot each rack from, but the problem was I didn't actually 69 00:04:46,800 --> 00:04:53,560 find one yet. Oh, how about this one? 70 00:04:50,760 --> 00:04:58,000 The Minisforum MS-A2 is super power efficient thanks to its mobile 71 00:04:54,800 --> 00:04:59,560 processor. Ooh. And it's small enough 72 00:04:58,000 --> 00:05:03,960 that I could tuck it into either one of the server racks or maybe even upstairs 73 00:05:01,680 --> 00:05:07,480 in the server room. It features dual 10 gigabit network ports on the back, and 74 00:05:05,760 --> 00:05:10,840 it has more than enough RAM and CPU cores that meet GG Rock's 75 00:05:08,880 --> 00:05:14,720 recommendations. They were a little hesitant. Usually they want to use 76 00:05:12,480 --> 00:05:18,880 proper server gear, like ECC memory, for example, but they did note that the 77 00:05:16,640 --> 00:05:23,520 network card, or the NIC in this little guy, is what they recommend. So I say we 78 00:05:21,360 --> 00:05:26,960 go for it. The main reason that GG Rock was concerned about our NIC is that 79 00:05:25,080 --> 00:05:30,960 having a fast, reliable network connection is crucial when you're 80 00:05:29,000 --> 00:05:36,640 booting multiple computers off of a storage server. Also, they are going to 81 00:05:33,160 --> 00:05:39,280 use PXE boot and iSCSI, which can be, 82 00:05:36,640 --> 00:05:42,560 in the industry term, a To minimize our chance of running into 83 00:05:40,720 --> 00:05:46,280 issues, we're going to set up Debian on our Minisforum server exactly like the 84 00:05:45,040 --> 00:05:50,840 guide says. Exactly. Do not ask me how I know that. 85 00:05:49,200 --> 00:05:54,240 Then we're going to wget and install link for the GG Rock server, wait for it 86 00:05:52,760 --> 00:05:57,360 to download, and configure our network interfaces. This is important to help 87 00:05:55,880 --> 00:06:01,840 with routing and making sure that our gaming computers will be able to find 88 00:05:59,480 --> 00:06:04,600 our GG Rock server. We type one last command, and that's the whole setup 89 00:06:03,560 --> 00:06:09,880 process. Now, we're going to add two 8 TB M.2 90 00:06:07,480 --> 00:06:14,360 drives in RAID 1. We probably won't have one of these fail, but since we're 91 00:06:11,280 --> 00:06:16,000 having 16 machines depend on reliable 92 00:06:14,360 --> 00:06:20,240 storage, an extra drive seems like a small price for a small man to pay. 93 00:06:18,400 --> 00:06:24,440 We'll create one disk image for games and a separate one for booting Windows. 94 00:06:22,240 --> 00:06:28,200 Now we need to upload an image to use. We're going to go with Windows 11 for 95 00:06:25,760 --> 00:06:32,640 now, but we chose these Radeon GPUs from ASUS both for their excellent price to 96 00:06:30,160 --> 00:06:36,720 performance and to give ourselves just a little bit of flexibility to run Linux 97 00:06:34,400 --> 00:06:40,200 on these systems once SteamOS becomes an actual thing. Now we just need to head 98 00:06:38,560 --> 00:06:44,760 over to our gaming machines and enable PXE boot. After rebooting, it will 99 00:06:42,520 --> 00:06:47,960 attempt to boot into Windows, but it will not work. That would be too easy, 100 00:06:46,280 --> 00:06:51,200 wouldn't it? Next on our GG Rock machine, we find that computer and 101 00:06:49,640 --> 00:06:55,800 choose the right network driver to inject into the Windows image. Reboot, 102 00:06:53,920 --> 00:06:58,760 and hopefully let it finish up the boot up process. 103 00:06:57,280 --> 00:07:02,000 Hopefully. It took me a while. From there, though, 104 00:07:00,280 --> 00:07:06,320 we can enable write backs. That way when I'm finished updating everything I need 105 00:07:03,880 --> 00:07:11,040 to on this one PC, we can then save everything to the master image. And that 106 00:07:08,440 --> 00:07:16,840 now means that theoretically, every machine can boot off of the same image. 107 00:07:14,200 --> 00:07:21,160 Theoretically. Theoretically? I guess we should build 108 00:07:18,440 --> 00:07:25,120 some actual computers. This here is eight of the 16 systems we're going to 109 00:07:22,960 --> 00:07:30,920 use in one of our server racks, and Justin spent the last couple days 3D 110 00:07:27,400 --> 00:07:32,840 printing a whole variety of mounts that 111 00:07:30,920 --> 00:07:36,320 is going to help us get all of these systems in that server rack. Which one's 112 00:07:35,040 --> 00:07:41,440 that? This one here is for the motherboard. Okay, and then what are these ones that I'm holding? Power 113 00:07:39,040 --> 00:07:45,320 supply, graphics card. Got it. And how are they going to lay out for us to be 114 00:07:43,200 --> 00:07:47,360 able to assemble this nicely? They're not just going to loosely lay in the 115 00:07:46,960 --> 00:07:53,400 rack. >> No, no, they'll bolt here to these shelves I got. Got it. Okay, I see now 116 00:07:51,720 --> 00:07:57,600 the pattern of these holes kind of line up with these holes. Correct. How many 117 00:07:55,200 --> 00:08:02,640 computers per shelf? I modeled for up to three, really tight, but because of the 118 00:08:00,480 --> 00:08:05,400 new server racks that we got, we should be able to just fit two per cuz we have 119 00:08:04,800 --> 00:08:11,960 more height now. >> Cuz we have more height. Got it. Okay, so then let's build one shelf, I guess. 120 00:08:10,600 --> 00:08:15,760 Yeah, let's get one together and let's see how it's going to fit height-wise. 121 00:08:13,600 --> 00:08:19,640 Motherboard mount go there. Power supply will mount somewhere along this back 122 00:08:18,040 --> 00:08:24,120 rail here. And then the graphics card >> And then the graphics card will line up 123 00:08:22,120 --> 00:08:29,360 wherever is comfortable for the PCI extenders. Got it, cuz I ordered very 124 00:08:26,800 --> 00:08:33,240 long ones cuz I wasn't sure at the time where this GPU was going to mount, if it 125 00:08:31,040 --> 00:08:36,640 was going to mount like down or up or To be fair, that was the right call. Okay. 126 00:08:35,520 --> 00:08:41,599 Okay, and then what are we using to mount it? Just these like threaded screws or whatever? Yep, standard M6 127 00:08:39,800 --> 00:08:49,760 bolts and these nuts. Got them. Got them. 128 00:08:49,760 --> 00:08:55,120 Snug fit. Uh apparently the PCBs have 129 00:08:53,080 --> 00:08:59,760 some tolerance to them. You see, it's just a little bit. Ah, it'll be fine. 130 00:08:58,600 --> 00:09:03,280 You know what? No. I'm going to I'm just going to shave that down a little bit. I don't trust it. 131 00:09:01,920 --> 00:09:06,360 >> Don't do this at home, kids. Not with your PCI risers. 132 00:09:07,960 --> 00:09:13,640 Push. Ooh. >> I hated that so 133 00:09:12,360 --> 00:09:17,360 much. There we go. Okay. All right, we got our 134 00:09:15,720 --> 00:09:21,840 fans. Yeah. You want You know, you want to roll on this because Thank you for bringing my 135 00:09:19,720 --> 00:09:26,120 only fans. It's the only fans we'll need. 136 00:09:24,320 --> 00:09:30,600 That was a funny joke. Linus would have made the same joke. That's the problem. 137 00:09:29,600 --> 00:09:34,440 Okay. There you go. >> Cool. Awesome. All right. Now, round 138 00:09:32,880 --> 00:09:41,040 two. Oh, yeah, I guess we do need Oh my god. We got to do this eight times. 139 00:09:41,040 --> 00:09:44,740 Now all I need to do is build eight more and then ship it all to the badminton 140 00:09:44,080 --> 00:09:49,600 center. I'm not going to do that on camera. I'll 141 00:09:47,960 --> 00:09:54,320 see you guys there. Eight more. >> Well, like eight more computers, not 142 00:09:52,520 --> 00:09:58,080 eight more of these. I would die if I had to do eight more of these. It's now 143 00:09:56,200 --> 00:10:01,720 the Friday before Whale LAN. I already threw our Mini Swarm MSA 2 upstairs here 144 00:10:00,280 --> 00:10:06,120 in the server room and I confirmed with the infrastructure team exactly which 145 00:10:03,280 --> 00:10:09,640 port I should plug it into. And as you can see, it's here on our 146 00:10:07,520 --> 00:10:13,160 network. Now, all I have to do is wait for Linus to be free being done setting 147 00:10:11,560 --> 00:10:17,120 up some of the couches and stuff, and then we're going to try to set up all 16 148 00:10:14,920 --> 00:10:19,680 in our 30-minute goal. While I wait, I got to thank ThreatLocker for helping us 149 00:10:18,400 --> 00:10:24,640 out with the Whale LAN event. They're helping provide some of the network security here for the event, so that way 150 00:10:22,640 --> 00:10:27,600 it protects our computers and your guys's. They also provide protection for 151 00:10:26,400 --> 00:10:32,680 us at the office. So, thanks ThreatLocker. We're just finalizing getting the AV8s here set up as if they 152 00:10:31,280 --> 00:10:36,800 were kind of set up by someone else, meaning all the cables were in place, the tables were in place. Then we're 153 00:10:35,520 --> 00:10:42,520 going to call Linus over to do the monitors, the keyboards, the mice, the headsets, and power it on. 154 00:10:40,880 --> 00:10:46,440 And hopefully, everything will work. I just got to route the last cables, the 155 00:10:43,880 --> 00:10:46,440 displays. 156 00:10:48,320 --> 00:10:54,200 Okay, I've got an update. I was going to test boot one of the systems just to make sure it does work, so when Linus 157 00:10:52,560 --> 00:10:57,600 comes over and sets them all up, it's like, "Wow, this is amazing. Look how 158 00:10:55,680 --> 00:11:02,320 good I did." I'm not getting any of them detected now 159 00:11:00,160 --> 00:11:05,640 when I'm trying to network boot them. And Dan's blasting crab rave, and it's 160 00:11:04,120 --> 00:11:09,720 driving me nuts. We're trying to figure out what's going on with the networking, and then it 161 00:11:08,160 --> 00:11:15,000 might also be display cables. I don't know at this point. It's coming down to the wire for Whale LAN. I wanted to test 162 00:11:12,880 --> 00:11:20,680 one computer for you, that way, "Oh man, everything's so magical and beautiful." 163 00:11:17,200 --> 00:11:22,680 I'm struggling to see my PXE server 164 00:11:20,680 --> 00:11:26,920 to boot everything from. So, we have to configure DHCP to be able to network 165 00:11:24,880 --> 00:11:29,560 boot. It's getting there. This is a quick 30-minute setup though, 166 00:11:28,320 --> 00:11:32,760 Linus. It's almost 4:00. When you start, it'll 167 00:11:31,680 --> 00:11:38,280 be a 30-minute setup. >> Are we going to be able to get this down to that? In the future, yes, because we 168 00:11:36,440 --> 00:11:42,800 would have ideally the proper length cables that would be always in a bundle. 169 00:11:40,839 --> 00:11:45,480 And just could they just like be coiled up in the cabinet? 170 00:11:44,040 --> 00:11:49,320 >> 100%. Okay, cool. >> Yeah. This is a first-time deployment. 171 00:11:47,440 --> 00:11:55,400 It's going to have some irons and bugs that need to be Well, no. >> It'll have some irons to bug. Iron 172 00:11:53,800 --> 00:11:59,680 So, we're rebooting one more time. Uh Elijah ran a command to try and refresh 173 00:11:57,680 --> 00:12:02,600 some of the settings on the server, and let's see what happens. 174 00:12:02,720 --> 00:12:07,760 That is also very good. >> Hey! Windows logo. 175 00:12:08,360 --> 00:12:11,200 We can go home. 176 00:12:14,839 --> 00:12:22,040 We got one of 16 done. But, that means the next 15 will be 177 00:12:19,800 --> 00:12:27,960 easy. Theoretically. Now I'm ready to get Linus for our quick 30-minute setup. 178 00:12:26,120 --> 00:12:33,280 It's 4:00 p.m. No, it's uh 4:20 p.m. 179 00:12:30,720 --> 00:12:36,520 Nice. Nice. Nice. Linus, Linus. We're actually ready now if you want to set up 180 00:12:34,960 --> 00:12:42,040 the rest of them. I wanted to do one as a test before we just jumped all 16. 181 00:12:38,880 --> 00:12:44,760 Dude, she's responsive. That's not bad. 182 00:12:42,040 --> 00:12:48,240 >> as our network is, essentially. Dude, she just She just works. She's like a 183 00:12:46,640 --> 00:12:52,960 computer. Okay, well, let's set up the rest. Okay. Do you think we can do it in 184 00:12:50,640 --> 00:12:55,920 30 minutes because I have to leave in 27 minutes for LAN show? Yeah, yeah, yeah. 185 00:12:54,600 --> 00:13:01,320 This only took like four or five to get to here, so the rest should be fine. 186 00:12:58,520 --> 00:13:05,760 I mean, you guys probably saw the Whale LAN setup vlog, so you know that we've 187 00:13:03,320 --> 00:13:10,040 both been here all day, and I know that he's full of sh Yeah. 188 00:13:07,720 --> 00:13:14,360 We went way over the top on the monitors for these. We don't want anybody blaming 189 00:13:12,360 --> 00:13:19,680 our AV8 systems. So, these are from ASRock's Phantom Gaming line. They're 190 00:13:16,480 --> 00:13:22,600 1080p IPS. Okay, that doesn't sound that 191 00:13:19,680 --> 00:13:26,440 impressive yet. 520 hertz. 192 00:13:24,240 --> 00:13:29,600 Are these labeled? Uh yeah, whichever one's the furthest that way is the one 193 00:13:27,920 --> 00:13:32,320 you get. What What are you talking about? No, I just mean are these labeled? 194 00:13:31,320 --> 00:13:37,720 >> No. That's number eight though. Are you sure? How do you know? Wait, what? 195 00:13:35,800 --> 00:13:40,280 Yeah, cuz it was laying there. We did this earlier. We We organized 196 00:13:39,520 --> 00:13:45,240 this earlier. >> even help, dude. And then this is your USB hub that we're going to plug our 197 00:13:43,560 --> 00:13:50,280 keyboard, mice, and headset into. >> Elijah, you're killing me. Yeah. Slowly. 198 00:13:48,400 --> 00:13:53,800 >> This so is this project. Dude, this is sick. I didn't know there 199 00:13:51,720 --> 00:13:57,240 was going to be lighting. Dude, oh, she's warm, 200 00:13:56,240 --> 00:14:03,880 she's warm. >> Yeah, we might want to pop the top off almost. What we might want to do is put 201 00:14:01,560 --> 00:14:08,839 a bunch of cooling fans up here. Then, if we did put the other side in and have 202 00:14:06,680 --> 00:14:14,800 enough to have each of these be an 8 by 8, then we could just kind of 203 00:14:12,480 --> 00:14:19,120 create an air funnel. And the IO is actually surprisingly organized. 204 00:14:17,400 --> 00:14:24,520 Everything is just on the ends here. Motherboards, GPUs, and everything's 205 00:14:21,440 --> 00:14:27,280 labeled. Love it. And each computer only 206 00:14:24,520 --> 00:14:31,040 has three cables, the Ethernet, one USB which goes to a hub, and then the 207 00:14:28,520 --> 00:14:36,040 display. Damn. You have your pog perfectly organized garage, I have my 208 00:14:32,839 --> 00:14:37,440 POS perfectly organized system. 209 00:14:36,040 --> 00:14:41,400 This is not going to be one of those projects where we just get it half-baked 210 00:14:39,560 --> 00:14:44,320 over the line and then just leave it, right? >> Well, I mean, we can make it another 211 00:14:42,720 --> 00:14:48,959 video in a quarter. No, no, no, no, no, no, no. This is final form, right? 212 00:14:47,120 --> 00:14:52,680 Yeah. For our peripherals, HyperX stepped up. They sent us 16 of their 213 00:14:51,040 --> 00:14:55,920 headsets, their keyboard, and their mice. That way, everyone here is on the 214 00:14:54,600 --> 00:15:01,400 same playing field. Nobody gets an advantage with their special little keyboards or their super light mice. 215 00:14:59,680 --> 00:15:05,640 We're all the exact same. Half an hour, he told me. 216 00:15:03,320 --> 00:15:09,680 Unless you want overtime. Have you tested these headsets to make sure that 217 00:15:07,400 --> 00:15:13,079 they handle a hub okay? Sometimes audio on a hub can be not great. 218 00:15:10,880 --> 00:15:15,720 >> Hm. I don't know, every time I've listened 219 00:15:14,120 --> 00:15:19,360 to the hub, it's been fine. That's not what we're talking about. >> Oh, oh, oh. I think we just need to make 220 00:15:18,079 --> 00:15:22,720 sure the monitor's on the right input. I might have to reboot because we're using DisplayPort. 221 00:15:21,280 --> 00:15:24,720 >> Uh-huh. But, theoretically, theoretically, we have 222 00:15:24,320 --> 00:15:30,079 them all. >> Theoretically. Oh, should we shout out Motion Grey who sent over 16 chairs, not 223 00:15:28,680 --> 00:15:33,120 to mention a crew of people to build them for us? Wait, that was That was 224 00:15:32,160 --> 00:15:38,200 actually Motion Grey that That was pretty chill of them. Oh, cool. 225 00:15:35,440 --> 00:15:42,600 Any luck on your networking? No. Shawn right now is making some changes at the 226 00:15:40,240 --> 00:15:47,360 same time we're trying to set this up, and I think we got blocked in some way. 227 00:15:45,240 --> 00:15:50,920 So, AJ's communicating with him. In a couple hours, so theoretically. 228 00:15:49,400 --> 00:15:55,480 Theoretically. I will be halfway through LAN show. 229 00:15:52,640 --> 00:15:58,980 Yeah, and I will be done this setup. Okay. 230 00:15:56,680 --> 00:16:02,720 I'll see you tomorrow, buddy. 231 00:16:02,720 --> 00:16:09,480 I've seen better cable management, but hey, we put a fair bit of lipstick on 232 00:16:07,560 --> 00:16:12,640 that pig. Yeah, looks great, doesn't it? But, you can boot up any of the games 233 00:16:10,720 --> 00:16:16,720 that are on the desktop, Linus. There's no storage in these systems. It's all 234 00:16:14,600 --> 00:16:19,520 booting over iSCSI, and it will work totally fine. 235 00:16:19,560 --> 00:16:25,520 Buddy! That's sick. Dude, this is what 236 00:16:23,240 --> 00:16:30,440 I'm talking about. That took 20 seconds, and I am in game, 237 00:16:28,720 --> 00:16:33,839 ready to go. We had an issue where all these computers weren't able to see the 238 00:16:31,880 --> 00:16:36,480 server that Linus created. So, what we actually have done is we've changed the 239 00:16:35,200 --> 00:16:41,400 Windows setting to make it a private network. Now, what we're going to do is we're going to try the system where we 240 00:16:39,600 --> 00:16:44,800 update one of them, and it should apply to all. So, we just did it to the blue 241 00:16:43,160 --> 00:16:49,400 eight computer there. Now, all I have to do is hit check mark to apply it. 242 00:16:47,920 --> 00:16:54,200 Applied. Change. Okay. Uh-huh. Then we hit apply. 243 00:16:53,320 --> 00:17:00,320 Now, you're going to notice all the systems are out of date. So, theoretically, all we now have to do is 244 00:16:57,959 --> 00:17:04,120 reboot them, and as we reboot them, they will be getting that new network change. 245 00:17:02,160 --> 00:17:10,000 I also set the default refresh rate to 520 hertz. >> Oh, yeah, that as well then. So, it 246 00:17:06,480 --> 00:17:11,400 should should be going to all of them. 247 00:17:10,000 --> 00:17:15,079 Okay, here they go. They're rebooting. The storage is a touch slow when 248 00:17:13,560 --> 00:17:19,280 everything's getting hit at the same time, but realistically, for gaming, 249 00:17:17,839 --> 00:17:23,760 especially some of the older games that we're going to be playing, it shouldn't matter that much. 250 00:17:31,800 --> 00:17:37,400 I want to give a huge thanks to all of the partners that made this possible. We're going to have everything linked 251 00:17:35,520 --> 00:17:40,920 down below, including the ASUS GPUs, the Mini Swarm motherboards, the G.Skill 252 00:17:38,960 --> 00:17:44,160 memory, the Western Digital drives, the Hamon Server Racks. I'm probably 253 00:17:42,760 --> 00:17:48,000 forgetting something, but it'll be down there. Oh, and GG Rock for all of the 254 00:17:46,040 --> 00:17:50,840 software help as well. And of course, our sponsor. 255 00:17:49,600 --> 00:17:55,679 >> That was a really cool video, Elijah. Really great job. >> Thanks. It's time for a song now though, 256 00:17:53,080 --> 00:18:01,320 so But first, a question. How do we explain what Odoo is? That's not a touch 257 00:17:59,000 --> 00:18:06,679 screen. Odoo is a smartphone. Are you referring to how you can use Odoo on 258 00:18:03,760 --> 00:18:11,400 your smartphone? Nah, Odoo is a smartphone. What? Listen. 259 00:18:25,960 --> 00:18:31,720 I don't get it. I thought it was super clear. 260 00:18:29,400 --> 00:18:37,080 Do you mean Odoo is like a smartphone? Well, yes. That's exactly what I meant. 261 00:18:34,480 --> 00:18:41,720 Oh, well, why didn't you say that? I like phrasing it as a metaphor. Well, I 262 00:18:39,520 --> 00:18:46,000 prefer a simile. I like the word onomatopoeia. Us too. Bam! 263 00:19:01,320 --> 00:19:07,280 If you guys enjoyed this video, go check out part one where Linus first gave me 264 00:19:05,480 --> 00:19:10,600 the task to try to build one of these machines. That's where we discovered 265 00:19:09,000 --> 00:19:14,880 what hardware we're going to use, and we tried to brainstorm some ideas about how 266 00:19:12,159 --> 00:19:14,880 to deploy them.