WEBVTT

00:00:00.000 --> 00:00:07.259
you guys have been telling us for years that our infrastructure the servers and

00:00:05.220 --> 00:00:12.059
the networking gear that our 20 video editors not to mention the other 90

00:00:08.940 --> 00:00:14.040
employees rely on is a little Jake you

00:00:12.059 --> 00:00:17.039
weren't wrong then and realistically you're probably not going to be wrong a

00:00:15.540 --> 00:00:23.699
few years from now but we haven't been standing still and in the last year alone we've effectively replaced or

00:00:21.000 --> 00:00:29.640
rebuilt every single server in this building making them faster better more

00:00:26.160 --> 00:00:31.859
reliable cooler far less power hungry in

00:00:29.640 --> 00:00:36.059
fact we've done so much that most of the servers you've ever seen on camera are

00:00:34.260 --> 00:00:40.440
in this graveyard right in front of me which means it's high time to give you

00:00:38.160 --> 00:00:44.640
guys a full update on all of it including some brand new gear that is

00:00:42.600 --> 00:00:46.879
unlike anything we've ever shown you before

00:00:53.239 --> 00:01:01.079
first up is the main server room at the OG office where you can see there's been

00:00:58.320 --> 00:01:05.400
some serious server shrinkage there was one point during the Vault recovery

00:01:02.699 --> 00:01:11.100
process where we literally only had three rack units left and now this is

00:01:07.920 --> 00:01:13.020
only about half full but the important

00:01:11.100 --> 00:01:19.140
stuff is actually at the back where our old PF sense router has been

00:01:16.340 --> 00:01:23.460
replaced or rather it's pulling Duty as a steam cache now our steam cache used

00:01:21.479 --> 00:01:27.299
to be in a VM but we were having issues with it it'd be like weird performance

00:01:25.080 --> 00:01:30.900
things would be like 10 gig download and be like one gig I mean 10 gig again and

00:01:29.159 --> 00:01:35.340
one gig so we're back on bare metal now which is fine because we upgraded this

00:01:32.939 --> 00:01:41.640
thing anyway only to discover that PF sense didn't run on the new box this

00:01:38.579 --> 00:01:46.140
super micro one you is super cool it's

00:01:41.640 --> 00:01:48.420
got 25 gig networking on board except no

00:01:46.140 --> 00:01:53.820
drivers and PF sense yeah it's running a really old FreeBSD version fortunately

00:01:50.780 --> 00:01:55.560
opensense is a fork of PF sense that

00:01:53.820 --> 00:02:00.079
gets updated way more frequently now that could be a double-edged sword your

00:01:58.020 --> 00:02:05.460
organization might prefer the slow plotting approach to updates but we live

00:02:03.180 --> 00:02:08.759
on the bleeding edge where we love that we've got support for our 25 gig

00:02:06.960 --> 00:02:11.940
networking in here and you update it like a couple weeks after the news yeah

00:02:10.380 --> 00:02:16.379
I usually wait like a month after a big release before updating and it's been

00:02:13.739 --> 00:02:20.760
Rock Solid for us zero issues if we wanted to go back to PF sense though we

00:02:18.120 --> 00:02:24.480
totally could is what I would say except they still don't support this thing no

00:02:22.860 --> 00:02:28.739
they don't the other changes back here are not so much Hardware but rather

00:02:25.860 --> 00:02:34.260
topology we've still got that awesome Dell 100 Gig switch but now we're wired

00:02:32.459 --> 00:02:41.099
directly into all of our editors and ingest stations via fiber running 25 gig

00:02:37.920 --> 00:02:43.920
and we're using the 100 Gig ports to

00:02:41.099 --> 00:02:47.760
connect to each of our Downstream switches where we used to have it going

00:02:45.720 --> 00:02:52.260
from one to the other to the other to the other so that if we had to update

00:02:49.800 --> 00:02:57.120
one or something uh it would knock out everything Downstream of it which to

00:02:54.780 --> 00:03:01.140
their credit these Dell 48 part 10 gig switches other than updates have they

00:02:59.220 --> 00:03:03.959
gone down at all I've never had an issue with any of these three Dell switches

00:03:03.000 --> 00:03:09.360
ever they would have 100 up time if we didn't update them shout out ubiquity as well

00:03:07.800 --> 00:03:13.500
though we've been really happy with their PoE switches this one right here

00:03:11.340 --> 00:03:18.480
runs all of our cameras all of our Wi-Fi access points and then this guy up here

00:03:16.200 --> 00:03:22.680
was actually added when we acquired the unit on I guess this runs to both other

00:03:20.760 --> 00:03:26.760
sides right 101 and 105. so that's the shop and like where the WAN Show set is

00:03:24.239 --> 00:03:30.840
and this one's got a 25 gig link to our 100 Gig switch now oh there is one other

00:03:28.739 --> 00:03:35.940
new piece of Hardware we have an NVR back here now yeah we have two actually

00:03:32.760 --> 00:03:37.379
we previously only had one but we had so

00:03:35.940 --> 00:03:41.760
many cameras that it was like starting to like cause weird performance issues

00:03:39.360 --> 00:03:44.760
so we split them out into two ubiquity keeps telling me that they're gonna add

00:03:42.840 --> 00:03:49.019
NVR stacking or you can combine them together but for now I have to like

00:03:46.620 --> 00:03:52.620
click between the we're really happy overall though yeah yeah yeah big

00:03:51.060 --> 00:03:57.060
brother's watching yeah yeah yeah yeah wait I missed something else

00:03:54.780 --> 00:03:59.340
what's this Cloud key doing up here well it used to be on this side let me

00:03:58.260 --> 00:04:05.159
remember don't we have a dream machine here I have one in my house no oh open

00:04:02.099 --> 00:04:08.540
sense right I can't remember why

00:04:05.159 --> 00:04:12.480
I thought you can run this in a VM now

00:04:08.540 --> 00:04:14.159
okay all right it was and then the

00:04:12.480 --> 00:04:20.760
database corrupted so we couldn't adopt anything properly so instead of just

00:04:17.720 --> 00:04:22.320
re-adopting all of the like 40 switches

00:04:20.760 --> 00:04:26.400
we had I was like what if we just transferred to a cloud key and it fixed

00:04:24.240 --> 00:04:30.900
it well it's not a cloud key now again like it was before love doing work twice

00:04:28.979 --> 00:04:35.340
the other thing that particularly the Europeans have tripped us about in here

00:04:32.400 --> 00:04:40.919
is our use of 120 volt power in a server room and while the output on this does

00:04:38.040 --> 00:04:47.820
stay only 110 and 120 volt is the options it's got two 120 volt phases so

00:04:45.419 --> 00:04:52.860
if you pair it with the right pdus or power distribution units you can totally

00:04:50.160 --> 00:04:57.060
do 208 volt which we're now doing thanks to these super cool pdus from triplite

00:04:54.960 --> 00:05:01.440
they're networked so you can not only monitor the total power usage but you

00:04:59.699 --> 00:05:05.520
can actually switch off individual Outlets say if a network device became

00:05:03.840 --> 00:05:09.900
unresponsive you can even create automations for it the main benefit of

00:05:07.620 --> 00:05:13.740
switching to 208 volt is efficiency you've probably seen in power supply

00:05:11.880 --> 00:05:19.020
marketing materials that there will be two lines for the efficiency curve one

00:05:15.960 --> 00:05:20.580
for 120 volt and one for 200 plus and

00:05:19.020 --> 00:05:23.759
the reason for that is the higher voltage allows your power supply to

00:05:22.259 --> 00:05:27.360
operate more efficiently it's exactly the same for servers so we dropped our

00:05:25.740 --> 00:05:32.280
power consumption in here by about 10 percent just from that changeover that

00:05:30.419 --> 00:05:35.400
means that combined with the server consolidation we've done and the

00:05:34.080 --> 00:05:40.680
additional battery units that we've added to our 9pxm this Eaton UPS can run

00:05:38.639 --> 00:05:45.660
for almost an hour with the power out completely which seems to come up around

00:05:43.199 --> 00:05:50.220
here a lot now let's talk about the great consolidation

00:05:47.280 --> 00:05:54.300
after we talk about our sponsor the ridge looking for a stylish and

00:05:52.259 --> 00:05:59.039
practical wallet the ridge wallet has got you covered it's minimalist design

00:05:56.820 --> 00:06:03.780
allows you to carry your essential cards and cash without the bulk check out the

00:06:01.440 --> 00:06:08.880
link below and use code Linus to save 10 off your purchase and get free shipping

00:06:06.060 --> 00:06:14.160
where we used to have five 45 Drive storinators taking up half our rack

00:06:10.979 --> 00:06:16.620
holding about 60 drives each we now have

00:06:14.160 --> 00:06:21.600
three of these super micro J bods and what we call the mother Vault each of

00:06:19.080 --> 00:06:27.180
these holds up to 90 drives and then we've got this single AMD epic Milan

00:06:24.240 --> 00:06:32.819
head unit that uses two epic Milan 32 core CPUs and then it uses external SAS

00:06:30.000 --> 00:06:37.259
connectors to attach to the j-bods right now we've only got a single j-bot

00:06:34.919 --> 00:06:41.699
attached to each of the SAS hpas in here but theoretically nothing would prevent

00:06:39.240 --> 00:06:46.740
us from adding another I don't know like three of these once we clear out Clover

00:06:44.280 --> 00:06:52.080
server this is running ancient Hardware it says Xeon

00:06:48.680 --> 00:06:53.819
2699v4 I mean that's 28 cores but they

00:06:52.080 --> 00:06:57.720
are flipping slow and we're using this for all of our virtual machines which do

00:06:56.400 --> 00:07:01.139
we even have that many virtual machines what else we got going on in here not

00:06:59.400 --> 00:07:06.060
really this one's being deprecated soon in place of Clayton's server up here

00:07:03.720 --> 00:07:09.720
which is running proxmox instead that will be where all of our VMS move in the

00:07:08.160 --> 00:07:14.940
long term does that mean I can take this CPU from my home server

00:07:12.300 --> 00:07:19.020
sure our Clayton proxmox Server doesn't really run a lot of VMS to be honest we

00:07:17.160 --> 00:07:22.560
have a parsec relay which makes Park SEC run a little bit faster when you have a

00:07:20.340 --> 00:07:27.000
bunch of different users we have a couple VMS for the Labs team and then

00:07:25.020 --> 00:07:33.900
the scene cache was on it but then like I said it kind of had issues so yeah 64

00:07:30.419 --> 00:07:35.460
core epic 24 Bays for four drives in

00:07:33.900 --> 00:07:38.400
like three VMS wait we didn't mention the mother vault

00:07:36.960 --> 00:07:43.139
is running true Nas yeah I mean basically all of our servers run true

00:07:40.020 --> 00:07:44.819
now shout out trunas shout out ZFS and

00:07:43.139 --> 00:07:48.960
Shout Out Wendell from level one text hey it's not like the Vault data is

00:07:46.979 --> 00:07:54.720
essential that's why it wasn't redundant then and it's still not redundant now

00:07:51.479 --> 00:07:56.460
but it's a super nice to have and thanks

00:07:54.720 --> 00:08:00.840
to Wendell we managed to get back what like 98 and a half percent of what we

00:07:58.800 --> 00:08:04.080
lost most of it and to be fair I haven't run into a situation yet where someone's

00:08:02.520 --> 00:08:09.539
been like hey I need this file and I can't find it but I think it's freaking

00:08:06.360 --> 00:08:12.300
awesome and it's wild being in Windows

00:08:09.539 --> 00:08:17.460
Explorer seeing this single folder this single machine that now has everything

00:08:14.180 --> 00:08:20.520
2.4 petabytes or whatever unbelievable

00:08:17.460 --> 00:08:23.160
speaking of unbelievable we got hated on

00:08:20.520 --> 00:08:27.000
a fair bit for this thing and you were right

00:08:24.080 --> 00:08:32.940
but not about the performance yeah this thing has been crazy reliable crazy fast

00:08:30.419 --> 00:08:35.880
it's basically the bee's knees I've only really went into one issue and this was

00:08:35.039 --> 00:08:40.320
recent the day of the heckoning

00:08:38.640 --> 00:08:45.600
one of the drives decided to shut off and if you want to change out an m.2

00:08:42.839 --> 00:08:50.760
drive that's loaded onto a carrier card that's loaded into a module thing that's

00:08:48.240 --> 00:08:54.000
loaded into a server it's a bit of a pain in the butt especially because we

00:08:52.500 --> 00:08:59.160
didn't have the foresight to write down the serials and which carrier card they

00:08:56.820 --> 00:09:04.019
were installed in absolutely zero idea which drive it is oh my God that's what

00:09:01.380 --> 00:09:10.260
you did so what we ended up doing to restore the array's Integrity is putting

00:09:06.959 --> 00:09:13.080
a mismatched seven terabyte kyocsia

00:09:10.260 --> 00:09:18.240
drive into one of the front NVMe Bays Jake yeah and the plan is apparently to

00:09:16.500 --> 00:09:24.420
do something about the serviceability of it soon TM well it hasn't needed any

00:09:21.720 --> 00:09:27.959
servicing right so to be fair when I restarted the server the drive came back

00:09:25.980 --> 00:09:31.620
online it has been online since we do have some ideas for improving the

00:09:29.580 --> 00:09:37.140
serviceability we found out that you can get u.2 to m.2 carrier cards so we could

00:09:35.160 --> 00:09:42.180
actually just take all those internal ssds load them into the u.2 slots in the

00:09:40.500 --> 00:09:45.660
front I guess we'll have to add more modules for that maybe use a different

00:09:43.560 --> 00:09:52.140
server or maybe use a difference oh okay so new new new monik is coming soon then

00:09:49.740 --> 00:09:58.860
wanted four and we could use those new sabrant drives they're sending over 22

00:09:55.800 --> 00:10:00.959
of their wild eight terabyte rocket 4

00:09:58.860 --> 00:10:06.420
plus drives so that we can try them out with that crazy 21 by m.2 carrier card

00:10:04.320 --> 00:10:10.440
that you probably saw in the news so wait no I am not thinking we use those

00:10:08.700 --> 00:10:15.839
carrier cards hey you were the one that brought that up no we're not we just put

00:10:12.600 --> 00:10:18.540
one it's the one one card server it's

00:10:15.839 --> 00:10:21.779
got 160 terabytes on one card yeah entire One X server and an Intel Nook

00:10:20.880 --> 00:10:26.760
yeah no no I mean you made it yeah it's not that

00:10:25.620 --> 00:10:31.500
way I'm the one that's supposed to say your ideas are stupid that's stupid it's

00:10:28.740 --> 00:10:35.519
not that stupid you like it I don't not after that meanwhile in Unit 101 where

00:10:33.959 --> 00:10:40.080
all the inventory and Logistics Department used to be but now you'll

00:10:37.500 --> 00:10:43.920
find only our makeshift ShortCircuit set we've removed the server rack

00:10:42.120 --> 00:10:46.920
outright because we can't have servers sitting here

00:10:45.360 --> 00:10:51.540
next to where we're trying to film instead we've got this simple six rack

00:10:49.740 --> 00:10:55.079
unit wall mount here that's going to hold our two Network switches that

00:10:53.399 --> 00:10:59.820
handle all the network connectivity down here and upstairs we've also got a udm

00:10:58.019 --> 00:11:04.260
pro down here that's the router for our secondary backup internet connection

00:11:01.440 --> 00:11:09.839
it's not nearly as fast it's one gig instead of 10 gig but realistically most

00:11:08.339 --> 00:11:15.480
of what we're doing we don't need most of the time we just use it for like testing a router on ShortCircuit so

00:11:12.959 --> 00:11:19.620
yeah it doesn't really matter now you might have noticed that this

00:11:17.880 --> 00:11:25.440
looks pretty okay this looks extremely not okay this is

00:11:22.860 --> 00:11:28.320
very much a work in progress these patch panels are going to come down here and

00:11:27.000 --> 00:11:32.220
then presumably at some point we're going to shorten these runs oh yeah oh

00:11:30.060 --> 00:11:35.220
yeah yeah because they're long enough to go into a rack well these will get

00:11:33.839 --> 00:11:38.640
replaced with little like those little ultra thin six inch cables from infinite

00:11:37.320 --> 00:11:42.540
cable Shadow infinite cables thanks for the thanks for these things and uh

00:11:40.680 --> 00:11:46.079
speaking of you know shout out shout out ubiquity for this access point yeah

00:11:44.160 --> 00:11:49.260
definitely oh my God is this the actual access point no no it's just like the

00:11:47.760 --> 00:11:53.279
backup connection one the only other noteworthy thing here is our ups this is

00:11:51.300 --> 00:11:57.720
to ensure that not only is our main internet connection battery backed up

00:11:54.839 --> 00:12:01.680
but also our secondary one that way in the event that we lose power to the

00:11:59.279 --> 00:12:06.540
building outright the WAN Show can continue as you guys actually saw not

00:12:04.019 --> 00:12:10.560
that long ago that time we had to run it on jackeries because we actually ran out

00:12:08.220 --> 00:12:13.019
of backup battery so we bought a second battery pack that just needs to get put

00:12:12.000 --> 00:12:20.040
on here it's sitting over there it'll it'll get on there we gotta be able to do WAN Show for like at least two hours

00:12:16.320 --> 00:12:21.959
yeah yeah on battery five

00:12:20.040 --> 00:12:27.540
moving over to the lab the biggest change is probably the complete removal

00:12:24.420 --> 00:12:29.579
of Windows from our infrastructure get

00:12:27.540 --> 00:12:33.480
it there used to be a window here yeah but because of all the sound bleed from

00:12:31.620 --> 00:12:37.680
the servers next door the poor social media team who's moving in here was

00:12:35.160 --> 00:12:41.880
going to develop tinnitus social media theme isn't that who's coming in here I

00:12:39.300 --> 00:12:46.440
hope this is my server room no what it what the server room's over here and now

00:12:44.220 --> 00:12:51.300
it is properly sealed so let's head in this room this is this no Honestly

00:12:49.500 --> 00:12:54.660
though removing the window and finishing up the drywall

00:12:52.860 --> 00:12:57.060
it's not really enough and it's especially not going to be enough with

00:12:55.980 --> 00:13:02.279
some of the gear that we're putting in here so we're doing it again but this

00:13:00.120 --> 00:13:06.300
time better way better hanging insulation on the wall of the server

00:13:04.500 --> 00:13:10.320
room yeah this time we're going to use this cool product called Sona par which

00:13:08.100 --> 00:13:14.579
like is a recycled wood panel they're like 30 bucks for a four by eight sheet

00:13:12.360 --> 00:13:17.459
which is really cheap for sand isolation and then we're gonna put rock wall on

00:13:16.019 --> 00:13:22.079
top of it with these cool adapters that Dan Made In fairness to me the original

00:13:19.500 --> 00:13:25.980
solution was messy but darn it did it ever work yeah it does work really well

00:13:24.000 --> 00:13:31.079
I took so much Flack for that I don't even know if sonopar existed then yeah

00:13:28.980 --> 00:13:35.579
and to be fair Nails is way easier than 3D printing hundreds of little brackets

00:13:32.760 --> 00:13:38.459
yeah yeah I did that in a weekend yeah we're gonna put the duvetine on with

00:13:37.079 --> 00:13:44.700
magnets it probably took like three months off my life with the amount of fibers I inhaled that yeah that's okay

00:13:42.240 --> 00:13:48.660
he got good life insurance man this is where you can see the difference between

00:13:46.500 --> 00:13:54.180
us eight and a half years ago architecting this stuff and then kind of

00:13:50.940 --> 00:13:55.800
upgrading piecemeal as we go and when we

00:13:54.180 --> 00:13:58.980
build something from scratch with all the knowledge we've gained since then

00:13:57.300 --> 00:14:03.360
here's where our internet connection comes in we did end up having to go for

00:14:01.260 --> 00:14:07.620
the expensive link over to the other building but hey now that the whole

00:14:05.639 --> 00:14:12.420
writing team's here and the lab is here we definitely do need it and then we've

00:14:10.260 --> 00:14:19.980
got these 100 Gig links that break out into 425s that go to these 10 gig

00:14:15.480 --> 00:14:22.380
switches one two three four five of them

00:14:19.980 --> 00:14:26.940
we might need one more too what the intention is for every single Connection

00:14:24.300 --> 00:14:30.720
in this building to be 10 gig obviously not cameras and like APS and stuff

00:14:29.220 --> 00:14:34.680
everything else is running off of these Enterprise 48 switches from ubiquity

00:14:32.579 --> 00:14:38.820
these are super cool they're 48 ports two and a half gig and they do PoE so

00:14:37.620 --> 00:14:44.040
these will do all the cameras and access points here which access points in

00:14:41.040 --> 00:14:46.620
particular now actually can use two and

00:14:44.040 --> 00:14:50.639
a half gig uplinks yeah so freaking fast and we put those Wi-Fi 60 Enterprise APS

00:14:49.199 --> 00:14:54.959
everywhere in this building at least with what's done so far we have

00:14:53.040 --> 00:14:58.800
ripping fast Wi-Fi here there's more than just networking over here though

00:14:56.279 --> 00:15:04.620
we've got the NVR Pro from ubiquity this is handling all of the cameras in this

00:15:00.839 --> 00:15:06.899
building and you may recognize this as

00:15:04.620 --> 00:15:12.180
the storeinator that 45 drives sent over for our vault recovery well now it's

00:15:09.600 --> 00:15:17.100
pulling completely different Duty as our Annie Dale server so this is our footage

00:15:15.000 --> 00:15:21.779
Dumping Ground and is one of the backup targets for our main video editing

00:15:19.199 --> 00:15:25.860
server wanick it's over at the lab now for more physical separation so that way

00:15:24.120 --> 00:15:30.300
if one of the buildings were to burn down in the past they were just two

00:15:28.079 --> 00:15:34.860
separate units of the same building now they are physically separate buildings

00:15:33.060 --> 00:15:40.260
probably the coolest thing over here though is this our first attempt at a

00:15:38.339 --> 00:15:46.380
high availability server that if all goes well is going to be the new wanek

00:15:42.779 --> 00:15:49.079
editing Nas you mean new new new high

00:15:46.380 --> 00:15:53.100
availability wanted yes yes that's the name we're gonna go for J wanted four

00:15:51.360 --> 00:15:55.579
um how do I get these out uh there's like a little

00:15:57.620 --> 00:16:05.940
each of these four units in here has a

00:16:01.680 --> 00:16:08.100
64 core epic melon season these are

00:16:05.940 --> 00:16:14.760
Genoa yeah yeah so it's like 384 gigs of RAM 64 core

00:16:11.880 --> 00:16:19.139
Genoa six UDOT three slots in the front for PCIe Gen 5 storage if you want and

00:16:16.860 --> 00:16:25.260
then there's two little m.2s for boot and there's four of them in this to you

00:16:21.260 --> 00:16:27.120
holy crap so there's 256 cores the idea

00:16:25.260 --> 00:16:31.139
here is that in the same way that you would run multiple hard drives so that

00:16:29.220 --> 00:16:36.779
if one fails the rest of them can just take over you run multiple servers so

00:16:34.920 --> 00:16:41.639
that if one fails for whatever reason the other three will just keep on

00:16:39.480 --> 00:16:45.600
trucking now there's a number of different ways that we can combine the

00:16:43.680 --> 00:16:51.660
storage of these servers whether we use something like Gloucester FS on trunes

00:16:47.519 --> 00:16:53.040
scale or Seth or even weka FS yeah we

00:16:51.660 --> 00:16:59.459
were going to use that weren't we we're working on it okay maybe yeah maybe we might need a

00:16:58.019 --> 00:17:05.100
second one of these because weka apparently needs eight nodes minimum now

00:17:02.639 --> 00:17:08.880
but still then we could have like three of them fail I think and still have

00:17:07.140 --> 00:17:12.000
storage which is crazy the other cool thing is

00:17:10.620 --> 00:17:17.040
you can update it in the middle of the workday like it's nothing oh that's

00:17:14.640 --> 00:17:22.559
super cool yeah BIOS update stay tuned for that yeah shout out Eaton by the way

00:17:19.319 --> 00:17:24.000
for this 9pxm UPS I think

00:17:22.559 --> 00:17:28.439
is the same one that's on the other side yeah did they just send this yeah they

00:17:26.220 --> 00:17:31.919
also sent us another two pdus which is super sick dude the pdus those aren't

00:17:30.419 --> 00:17:36.840
even the final ones they didn't have stock of the ones I wanted that have

00:17:33.660 --> 00:17:38.220
individual per Port energy monitoring no

00:17:36.840 --> 00:17:41.700
way so they were like oh yeah you can just have these ones for now and we'll

00:17:40.020 --> 00:17:45.600
send those ones when you want it and they're also providing full cable tray

00:17:44.160 --> 00:17:49.679
for the entire Warehouse so we can actually run all the Ethernet in like

00:17:47.340 --> 00:17:53.160
those fancy trays so eaten our just complete Bros now yeah man their stuff

00:17:52.140 --> 00:17:57.419
is like aced here that's the that's this is what

00:17:55.500 --> 00:18:01.080
you want speaking of cable tray I guess that's the plan for this yeah the reason

00:17:59.220 --> 00:18:04.620
that that hasn't been cleaned up is we have to run like another 30 or 40 wires

00:18:03.360 --> 00:18:07.860
you might as well just do it all at once got it we didn't mention this on the

00:18:06.419 --> 00:18:12.299
other side but you might have noticed we have these color-coded power cables

00:18:09.900 --> 00:18:17.820
coming off of our pdus that's so that we can ensure that each of our servers is

00:18:15.240 --> 00:18:21.660
powered by two separate pdus so that in the event of a pdu failure it'll still

00:18:20.160 --> 00:18:24.840
stay running thanks to the Redundant power supply the last part of the

00:18:23.220 --> 00:18:28.799
infrastructure changes are on the client side specifically for our writers

00:18:26.640 --> 00:18:33.120
ubiquity hooked up each of them with one of these cool I think they're called the

00:18:29.880 --> 00:18:34.799
switchflex XG they're a PoE powered 10

00:18:33.120 --> 00:18:39.660
gig switch but in our case we're just using wall power it gives each of our

00:18:36.840 --> 00:18:43.500
Riders four 10 gig ports and a gigabit Port obviously we have test benches and

00:18:41.700 --> 00:18:46.380
other devices that we're working on so just having one 10 gig connection to

00:18:45.240 --> 00:18:51.419
each workstation was a bit of a bottleneck this way they can plug in a bunch of different devices and still get

00:18:49.559 --> 00:18:54.360
that 10 gig speed which is obviously very important if we need to review

00:18:52.559 --> 00:18:57.240
footage off this server or what have you it's pretty sick and they're not that

00:18:55.559 --> 00:18:59.940
expensive either I think it's 2 99 for one of those we almost forgot about the

00:18:58.559 --> 00:19:04.320
network closet that was here when we moved into the lab the intention for

00:19:01.919 --> 00:19:07.919
this is for all of these cables to get moved over to the new server room the

00:19:06.480 --> 00:19:12.780
reason it's still here is these are all the old Connections in the warehouse that haven't been redone yet because of

00:19:10.980 --> 00:19:17.280
that cable tray so once that's all done these will probably just get cut out of

00:19:14.700 --> 00:19:19.679
the wall and recycled and yeah there won't really be anything in this closet

00:19:18.539 --> 00:19:25.740
we could probably just use it for cleaning products or something like that grammarly is throwing their hat into the

00:19:23.460 --> 00:19:29.880
AI ring with grammarly go which offers generative AI to accelerate your

00:19:27.840 --> 00:19:34.140
productivity while staying true to your personal style what makes grammarly go

00:19:32.039 --> 00:19:38.460
so unique is that you can customize your preferred communication Style by setting

00:19:36.000 --> 00:19:42.299
your voice to personalize your tone the business team uses grammarly go to

00:19:40.320 --> 00:19:48.179
rewrite emails and talking points to be more concise all while keeping it

00:19:44.400 --> 00:19:50.340
authentic to our voice it's me need help

00:19:48.179 --> 00:19:54.720
with a video title just input a prompt and grammarly go will provide innovative

00:19:52.260 --> 00:19:58.919
ideas to unlock your creative potential our favorite part about grammarly go is

00:19:56.940 --> 00:20:02.100
that it's there to help you write not replace you and there's no need to leave

00:20:00.660 --> 00:20:06.000
the platform you're on just download sign up and start typing you'll be

00:20:04.380 --> 00:20:12.000
amazed at what you can do with grammarly go so sign up at grammarly.com LTT and

00:20:09.179 --> 00:20:15.120
get 20 off grammarly premium and that's pretty much it big shout out to you

00:20:13.679 --> 00:20:19.440
ubiquity for all the networking gear micro tick as well super micro for all

00:20:17.460 --> 00:20:24.539
the servers infinite cables for the patch panels the networking they sent us

00:20:22.020 --> 00:20:30.480
like 20 boxes of a thousand feet of cat6a they got really sick patch cables

00:20:26.880 --> 00:20:32.340
45 are you pimping infinite cases again

00:20:30.480 --> 00:20:37.380
yes yes 45 drives also makes awesome servers

00:20:35.640 --> 00:20:41.580
we're just not really using them aside from this one but definitely check them

00:20:38.760 --> 00:20:44.820
out God what's up what else is there oh I guess a video to watch probably the

00:20:43.380 --> 00:20:49.500
one where we put all this in this rack because that was just like pure

00:20:46.799 --> 00:20:52.980
distilled chaos or you could go watch the one on the

00:20:50.940 --> 00:20:58.460
mother Vault yeah that was a big change for us oh my gosh it's so nice though

00:20:55.980 --> 00:20:58.460
bye
