WEBVTT Kind: captions Language: en 00:00:00.080 --> 00:00:02.149 align:start position:0% Welcome<00:00:00.400> to<00:00:00.480> True<00:00:01.040> Tech<00:00:01.280> Talk,<00:00:01.600> the<00:00:01.920> last 00:00:02.149 --> 00:00:02.159 align:start position:0% Welcome to True Tech Talk, the last 00:00:02.159 --> 00:00:04.950 align:start position:0% Welcome to True Tech Talk, the last episode<00:00:02.560> at<00:00:02.800> the<00:00:02.960> end<00:00:03.040> of<00:00:03.280> February<00:00:03.840> 2026. 00:00:04.950 --> 00:00:04.960 align:start position:0% episode at the end of February 2026. 00:00:04.960 --> 00:00:06.789 align:start position:0% episode at the end of February 2026. We've<00:00:05.120> got<00:00:05.279> a<00:00:05.440> few<00:00:05.600> high-profile<00:00:06.319> items<00:00:06.640> to 00:00:06.789 --> 00:00:06.799 align:start position:0% We've got a few high-profile items to 00:00:06.799 --> 00:00:08.710 align:start position:0% We've got a few high-profile items to cover<00:00:07.120> today.<00:00:07.440> We<00:00:07.600> got<00:00:07.680> a<00:00:07.839> new<00:00:07.919> hot<00:00:08.160> fix.<00:00:08.559> We 00:00:08.710 --> 00:00:08.720 align:start position:0% cover today. We got a new hot fix. We 00:00:08.720 --> 00:00:10.950 align:start position:0% cover today. We got a new hot fix. We got<00:00:08.880> some<00:00:09.040> changes<00:00:09.440> coming<00:00:09.760> to<00:00:10.240> smart<00:00:10.639> support 00:00:10.950 --> 00:00:10.960 align:start position:0% got some changes coming to smart support 00:00:10.960 --> 00:00:13.190 align:start position:0% got some changes coming to smart support to<00:00:11.200> announce.<00:00:11.599> Oo,<00:00:11.920> stay<00:00:12.160> tuned<00:00:12.320> for<00:00:12.480> that. 00:00:13.190 --> 00:00:13.200 align:start position:0% to announce. Oo, stay tuned for that. 00:00:13.200 --> 00:00:15.749 align:start position:0% to announce. Oo, stay tuned for that. Debut<00:00:13.519> of<00:00:13.759> an<00:00:13.920> official<00:00:14.320> Proxmox<00:00:15.120> plugin<00:00:15.519> and 00:00:15.749 --> 00:00:15.759 align:start position:0% Debut of an official Proxmox plugin and 00:00:15.759 --> 00:00:17.750 align:start position:0% Debut of an official Proxmox plugin and some<00:00:16.000> much<00:00:16.240> soughtafter<00:00:17.119> application 00:00:17.750 --> 00:00:17.760 align:start position:0% some much soughtafter application 00:00:17.760 --> 00:00:20.550 align:start position:0% some much soughtafter application updates.<00:00:18.640> An<00:00:18.880> action-packed<00:00:19.680> episode<00:00:20.000> ahead. 00:00:20.550 --> 00:00:20.560 align:start position:0% updates. An action-packed episode ahead. 00:00:20.560 --> 00:00:22.790 align:start position:0% updates. An action-packed episode ahead. Let's<00:00:20.800> dive<00:00:21.039> right<00:00:21.279> in.<00:00:22.000> Welcome<00:00:22.240> back<00:00:22.560> this 00:00:22.790 --> 00:00:22.800 align:start position:0% Let's dive right in. Welcome back this 00:00:22.800 --> 00:00:24.790 align:start position:0% Let's dive right in. Welcome back this week<00:00:23.119> everybody.<00:00:23.760> Be<00:00:23.920> sure<00:00:24.160> of<00:00:24.400> course<00:00:24.560> to 00:00:24.790 --> 00:00:24.800 align:start position:0% week everybody. Be sure of course to 00:00:24.800 --> 00:00:26.950 align:start position:0% week everybody. Be sure of course to like<00:00:25.039> and<00:00:25.279> subscribe.<00:00:26.080> do<00:00:26.320> all<00:00:26.400> the<00:00:26.640> usual 00:00:26.950 --> 00:00:26.960 align:start position:0% like and subscribe. do all the usual 00:00:26.960 --> 00:00:28.870 align:start position:0% like and subscribe. do all the usual YouTube<00:00:27.359> things.<00:00:27.840> Otherwise,<00:00:28.320> I<00:00:28.560> might<00:00:28.720> need 00:00:28.870 --> 00:00:28.880 align:start position:0% YouTube things. Otherwise, I might need 00:00:28.880 --> 00:00:30.790 align:start position:0% YouTube things. Otherwise, I might need to<00:00:28.960> make<00:00:29.119> Chris<00:00:29.439> daily<00:00:29.840> drive<00:00:30.000> a<00:00:30.240> Mac<00:00:30.480> for<00:00:30.640> a 00:00:30.790 --> 00:00:30.800 align:start position:0% to make Chris daily drive a Mac for a 00:00:30.800 --> 00:00:32.870 align:start position:0% to make Chris daily drive a Mac for a week,<00:00:31.039> which<00:00:31.760> actually<00:00:32.160> that<00:00:32.320> may<00:00:32.480> not<00:00:32.640> be<00:00:32.719> a 00:00:32.870 --> 00:00:32.880 align:start position:0% week, which actually that may not be a 00:00:32.880 --> 00:00:35.110 align:start position:0% week, which actually that may not be a bad<00:00:33.040> idea,<00:00:33.440> Chris.<00:00:34.079> You<00:00:34.160> know,<00:00:34.399> I'm<00:00:34.559> I'm<00:00:34.960> kind 00:00:35.110 --> 00:00:35.120 align:start position:0% bad idea, Chris. You know, I'm I'm kind 00:00:35.120 --> 00:00:36.549 align:start position:0% bad idea, Chris. You know, I'm I'm kind of<00:00:35.280> liking<00:00:35.600> this<00:00:35.840> one. 00:00:36.549 --> 00:00:36.559 align:start position:0% of liking this one. 00:00:36.559 --> 00:00:37.830 align:start position:0% of liking this one. >> I<00:00:36.640> was<00:00:36.719> going<00:00:36.800> to<00:00:36.880> say<00:00:37.120> enjoy<00:00:37.360> that. 00:00:37.830 --> 00:00:37.840 align:start position:0% >> I was going to say enjoy that. 00:00:37.840 --> 00:00:39.350 align:start position:0% >> I was going to say enjoy that. >> You've<00:00:38.160> been<00:00:38.239> trying<00:00:38.399> to<00:00:38.559> get<00:00:38.640> me<00:00:38.800> onto<00:00:39.040> Linux 00:00:39.350 --> 00:00:39.360 align:start position:0% >> You've been trying to get me onto Linux 00:00:39.360 --> 00:00:40.709 align:start position:0% >> You've been trying to get me onto Linux for<00:00:39.520> a<00:00:39.600> while<00:00:39.760> now.<00:00:40.000> You<00:00:40.160> want<00:00:40.239> to<00:00:40.320> make<00:00:40.399> me<00:00:40.559> try 00:00:40.709 --> 00:00:40.719 align:start position:0% for a while now. You want to make me try 00:00:40.719 --> 00:00:42.069 align:start position:0% for a while now. You want to make me try a<00:00:40.879> Mac? 00:00:42.069 --> 00:00:42.079 align:start position:0% a Mac? 00:00:42.079 --> 00:00:44.869 align:start position:0% a Mac? >> Well,<00:00:42.399> you<00:00:42.559> know,<00:00:43.280> I<00:00:43.520> I'm<00:00:43.840> using<00:00:44.079> my<00:00:44.320> daily<00:00:44.559> Mac 00:00:44.869 --> 00:00:44.879 align:start position:0% >> Well, you know, I I'm using my daily Mac 00:00:44.879 --> 00:00:46.549 align:start position:0% >> Well, you know, I I'm using my daily Mac as<00:00:45.040> my<00:00:45.280> daily<00:00:45.520> driver,<00:00:45.760> but<00:00:45.920> I<00:00:46.000> have<00:00:46.079> my<00:00:46.239> Linux 00:00:46.549 --> 00:00:46.559 align:start position:0% as my daily driver, but I have my Linux 00:00:46.559 --> 00:00:48.150 align:start position:0% as my daily driver, but I have my Linux gaming<00:00:46.960> system.<00:00:47.360> So,<00:00:47.520> again,<00:00:47.840> different 00:00:48.150 --> 00:00:48.160 align:start position:0% gaming system. So, again, different 00:00:48.160 --> 00:00:50.310 align:start position:0% gaming system. So, again, different purposes<00:00:48.559> and<00:00:48.719> all<00:00:48.879> that.<00:00:49.120> You<00:00:49.280> need<00:00:49.440> both.<00:00:50.079> I 00:00:50.310 --> 00:00:50.320 align:start position:0% purposes and all that. You need both. I 00:00:50.320 --> 00:00:51.910 align:start position:0% purposes and all that. You need both. I think<00:00:50.480> you<00:00:50.640> need<00:00:50.719> one<00:00:50.960> of<00:00:51.039> each. 00:00:51.910 --> 00:00:51.920 align:start position:0% think you need one of each. 00:00:51.920 --> 00:00:53.990 align:start position:0% think you need one of each. >> Okay.<00:00:53.039> We'll<00:00:53.280> get<00:00:53.360> there.<00:00:53.600> We'll<00:00:53.760> get<00:00:53.840> there. 00:00:53.990 --> 00:00:54.000 align:start position:0% >> Okay. We'll get there. We'll get there. 00:00:54.000 --> 00:00:55.830 align:start position:0% >> Okay. We'll get there. We'll get there. We'll<00:00:54.239> work<00:00:54.320> on<00:00:54.559> Chris.<00:00:55.199> We'll<00:00:55.360> get<00:00:55.520> that.<00:00:55.760> I 00:00:55.830 --> 00:00:55.840 align:start position:0% We'll work on Chris. We'll get that. I 00:00:55.840 --> 00:00:57.830 align:start position:0% We'll work on Chris. We'll get that. I hear<00:00:56.000> the<00:00:56.160> dark<00:00:56.399> side<00:00:56.640> has<00:00:56.879> cookies. 00:00:57.830 --> 00:00:57.840 align:start position:0% hear the dark side has cookies. 00:00:57.840 --> 00:00:59.110 align:start position:0% hear the dark side has cookies. >> It<00:00:58.079> does<00:00:58.239> have<00:00:58.399> cookies.<00:00:58.719> They're<00:00:58.960> pretty 00:00:59.110 --> 00:00:59.120 align:start position:0% >> It does have cookies. They're pretty 00:00:59.120 --> 00:01:00.150 align:start position:0% >> It does have cookies. They're pretty tasty,<00:00:59.440> too.<00:00:59.680> It's<00:00:59.840> nice. 00:01:00.150 --> 00:01:00.160 align:start position:0% tasty, too. It's nice. 00:01:00.160 --> 00:01:02.790 align:start position:0% tasty, too. It's nice. >> All<00:01:00.239> right.<00:01:00.640> Well,<00:01:01.680> okay.<00:01:02.079> Well,<00:01:02.320> hey,<00:01:02.480> we<00:01:02.719> had 00:01:02.790 --> 00:01:02.800 align:start position:0% >> All right. Well, okay. Well, hey, we had 00:01:02.800 --> 00:01:04.469 align:start position:0% >> All right. Well, okay. Well, hey, we had some<00:01:03.039> exciting<00:01:03.440> news<00:01:03.600> this<00:01:03.840> week.<00:01:04.080> I<00:01:04.239> think<00:01:04.320> we 00:01:04.469 --> 00:01:04.479 align:start position:0% some exciting news this week. I think we 00:01:04.479 --> 00:01:06.390 align:start position:0% some exciting news this week. I think we just<00:01:04.640> did<00:01:04.720> a<00:01:04.879> big<00:01:05.040> release<00:01:05.360> last<00:01:05.600> week<00:01:05.840> and<00:01:06.159> you 00:01:06.390 --> 00:01:06.400 align:start position:0% just did a big release last week and you 00:01:06.400 --> 00:01:07.910 align:start position:0% just did a big release last week and you challenged<00:01:06.880> folks<00:01:07.119> to<00:01:07.280> find<00:01:07.439> those<00:01:07.600> edge 00:01:07.910 --> 00:01:07.920 align:start position:0% challenged folks to find those edge 00:01:07.920 --> 00:01:09.910 align:start position:0% challenged folks to find those edge cases<00:01:08.240> and<00:01:08.479> so<00:01:08.880> sure<00:01:09.040> enough,<00:01:09.360> we<00:01:09.520> put<00:01:09.680> out<00:01:09.760> a 00:01:09.910 --> 00:01:09.920 align:start position:0% cases and so sure enough, we put out a 00:01:09.920 --> 00:01:11.590 align:start position:0% cases and so sure enough, we put out a hot<00:01:10.159> fix.<00:01:10.479> Tell<00:01:10.560> us<00:01:10.720> about<00:01:10.880> that,<00:01:11.119> Chris.<00:01:11.439> What 00:01:11.590 --> 00:01:11.600 align:start position:0% hot fix. Tell us about that, Chris. What 00:01:11.600 --> 00:01:12.310 align:start position:0% hot fix. Tell us about that, Chris. What happened? 00:01:12.310 --> 00:01:12.320 align:start position:0% happened? 00:01:12.320 --> 00:01:14.070 align:start position:0% happened? >> Yeah,<00:01:12.560> we<00:01:12.720> we<00:01:13.040> made<00:01:13.200> that<00:01:13.439> little<00:01:13.600> comment.<00:01:13.920> We 00:01:14.070 --> 00:01:14.080 align:start position:0% >> Yeah, we we made that little comment. We 00:01:14.080 --> 00:01:15.910 align:start position:0% >> Yeah, we we made that little comment. We said,<00:01:14.400> let's<00:01:14.720> take<00:01:14.799> a<00:01:14.960> little<00:01:15.119> overunder<00:01:15.760> here 00:01:15.910 --> 00:01:15.920 align:start position:0% said, let's take a little overunder here 00:01:15.920 --> 00:01:17.510 align:start position:0% said, let's take a little overunder here on<00:01:16.240> how<00:01:16.479> long<00:01:16.640> it<00:01:16.799> is<00:01:16.960> until<00:01:17.200> somebody 00:01:17.510 --> 00:01:17.520 align:start position:0% on how long it is until somebody 00:01:17.520 --> 00:01:19.590 align:start position:0% on how long it is until somebody surfaces<00:01:18.000> a<00:01:18.159> new<00:01:18.320> bug.<00:01:18.720> How<00:01:18.880> long<00:01:19.119> is<00:01:19.280> it<00:01:19.439> going 00:01:19.590 --> 00:01:19.600 align:start position:0% surfaces a new bug. How long is it going 00:01:19.600 --> 00:01:21.749 align:start position:0% surfaces a new bug. How long is it going to<00:01:19.680> be?<00:01:20.080> Right.<00:01:20.560> And<00:01:20.960> uh<00:01:21.119> well,<00:01:21.439> I<00:01:21.680> don't 00:01:21.749 --> 00:01:21.759 align:start position:0% to be? Right. And uh well, I don't 00:01:21.759 --> 00:01:23.510 align:start position:0% to be? Right. And uh well, I don't recall<00:01:22.000> if<00:01:22.159> we<00:01:22.320> ever<00:01:22.479> put<00:01:22.640> any<00:01:22.880> money<00:01:23.119> down<00:01:23.360> on 00:01:23.510 --> 00:01:23.520 align:start position:0% recall if we ever put any money down on 00:01:23.520 --> 00:01:24.950 align:start position:0% recall if we ever put any money down on that,<00:01:23.759> but<00:01:24.000> we'll<00:01:24.240> have<00:01:24.320> to<00:01:24.479> see<00:01:24.560> who's<00:01:24.880> going 00:01:24.950 --> 00:01:24.960 align:start position:0% that, but we'll have to see who's going 00:01:24.960 --> 00:01:27.270 align:start position:0% that, but we'll have to see who's going to<00:01:25.040> collect.<00:01:25.600> But<00:01:25.920> we<00:01:26.159> did<00:01:26.400> do<00:01:26.560> a<00:01:26.799> quick<00:01:27.040> little 00:01:27.270 --> 00:01:27.280 align:start position:0% to collect. But we did do a quick little 00:01:27.280 --> 00:01:30.950 align:start position:0% to collect. But we did do a quick little hot<00:01:27.520> fix<00:01:27.759> there.<00:01:28.080> So<00:01:28.400> 2510.2.1, 00:01:30.950 --> 00:01:30.960 align:start position:0% hot fix there. So 2510.2.1, 00:01:30.960 --> 00:01:32.950 align:start position:0% hot fix there. So 2510.2.1, the<00:01:31.200> first<00:01:31.360> little<00:01:31.520> hot<00:01:31.759> fix<00:01:32.000> there.<00:01:32.479> Uh<00:01:32.720> it's 00:01:32.950 --> 00:01:32.960 align:start position:0% the first little hot fix there. Uh it's 00:01:32.960 --> 00:01:34.710 align:start position:0% the first little hot fix there. Uh it's just<00:01:33.119> a<00:01:33.280> handful<00:01:33.600> of<00:01:33.759> little<00:01:34.000> fixes<00:01:34.320> in<00:01:34.479> there. 00:01:34.710 --> 00:01:34.720 align:start position:0% just a handful of little fixes in there. 00:01:34.720 --> 00:01:36.710 align:start position:0% just a handful of little fixes in there. One<00:01:34.880> of<00:01:35.040> them<00:01:35.200> is<00:01:35.439> a<00:01:35.680> fix<00:01:35.920> for<00:01:36.079> some<00:01:36.320> nick 00:01:36.710 --> 00:01:36.720 align:start position:0% One of them is a fix for some nick 00:01:36.720 --> 00:01:38.710 align:start position:0% One of them is a fix for some nick bonding<00:01:37.119> issues,<00:01:37.759> uh<00:01:37.840> which<00:01:38.079> was<00:01:38.159> pointed<00:01:38.479> out 00:01:38.710 --> 00:01:38.720 align:start position:0% bonding issues, uh which was pointed out 00:01:38.720 --> 00:01:40.230 align:start position:0% bonding issues, uh which was pointed out by<00:01:38.960> somebody<00:01:39.119> on<00:01:39.360> upgrade<00:01:39.759> that<00:01:40.000> they<00:01:40.159> said, 00:01:40.230 --> 00:01:40.240 align:start position:0% by somebody on upgrade that they said, 00:01:40.240 --> 00:01:42.950 align:start position:0% by somebody on upgrade that they said, "Hey,<00:01:40.640> it<00:01:40.960> uh<00:01:41.280> it<00:01:41.600> broke<00:01:41.840> my<00:01:42.000> nick<00:01:42.320> team<00:01:42.720> pretty 00:01:42.950 --> 00:01:42.960 align:start position:0% "Hey, it uh it broke my nick team pretty 00:01:42.960 --> 00:01:44.149 align:start position:0% "Hey, it uh it broke my nick team pretty much<00:01:43.119> immediately<00:01:43.520> and<00:01:43.680> they<00:01:43.840> had<00:01:44.000> to 00:01:44.149 --> 00:01:44.159 align:start position:0% much immediately and they had to 00:01:44.159 --> 00:01:45.990 align:start position:0% much immediately and they had to revert."<00:01:44.560> So<00:01:45.119> uh<00:01:45.280> that<00:01:45.439> one<00:01:45.600> should<00:01:45.840> be 00:01:45.990 --> 00:01:46.000 align:start position:0% revert." So uh that one should be 00:01:46.000 --> 00:01:48.149 align:start position:0% revert." So uh that one should be corrected.<00:01:46.399> We<00:01:46.640> apologize<00:01:47.119> for<00:01:47.280> that.<00:01:47.920> There 00:01:48.149 --> 00:01:48.159 align:start position:0% corrected. We apologize for that. There 00:01:48.159 --> 00:01:49.830 align:start position:0% corrected. We apologize for that. There were<00:01:48.320> also<00:01:48.640> some<00:01:48.880> of<00:01:48.960> those<00:01:49.200> wonderful<00:01:49.520> edge 00:01:49.830 --> 00:01:49.840 align:start position:0% were also some of those wonderful edge 00:01:49.840 --> 00:01:52.069 align:start position:0% were also some of those wonderful edge cases<00:01:50.240> that<00:01:50.399> were<00:01:50.560> found<00:01:50.799> around<00:01:51.200> those<00:01:51.600> SMB 00:01:52.069 --> 00:01:52.079 align:start position:0% cases that were found around those SMB 00:01:52.079 --> 00:01:55.030 align:start position:0% cases that were found around those SMB validation<00:01:52.880> errors<00:01:53.119> for<00:01:53.520> legacy<00:01:54.000> shares<00:01:54.880> and 00:01:55.030 --> 00:01:55.040 align:start position:0% validation errors for legacy shares and 00:01:55.040 --> 00:01:57.190 align:start position:0% validation errors for legacy shares and a<00:01:55.280> couple<00:01:55.439> of<00:01:55.600> cosmetic<00:01:56.159> things.<00:01:56.799> But<00:01:56.960> then 00:01:57.190 --> 00:01:57.200 align:start position:0% a couple of cosmetic things. But then 00:01:57.200 --> 00:01:59.510 align:start position:0% a couple of cosmetic things. But then one<00:01:57.520> piece<00:01:57.840> that<00:01:58.320> uh<00:01:58.479> was<00:01:58.719> supposed<00:01:58.960> to<00:01:59.119> be<00:01:59.280> in 00:01:59.510 --> 00:01:59.520 align:start position:0% one piece that uh was supposed to be in 00:01:59.520 --> 00:02:02.389 align:start position:0% one piece that uh was supposed to be in the<00:01:59.920> hot<00:02:00.240> fix<00:02:00.479> or<00:02:00.719> the<00:02:01.040> original<00:02:01.439> bundle<00:02:02.159> in 00:02:02.389 --> 00:02:02.399 align:start position:0% the hot fix or the original bundle in 00:02:02.399 --> 00:02:04.149 align:start position:0% the hot fix or the original bundle in the<00:02:02.640> 2510.2 00:02:04.149 --> 00:02:04.159 align:start position:0% the 2510.2 00:02:04.159 --> 00:02:05.910 align:start position:0% the 2510.2 and<00:02:04.560> didn't<00:02:04.880> make<00:02:05.040> it<00:02:05.119> in<00:02:05.360> because<00:02:05.520> of<00:02:05.680> some 00:02:05.910 --> 00:02:05.920 align:start position:0% and didn't make it in because of some 00:02:05.920 --> 00:02:08.389 align:start position:0% and didn't make it in because of some strange<00:02:06.240> Jira<00:02:06.719> build<00:02:06.960> issues.<00:02:07.360> I<00:02:07.600> believe<00:02:08.319> uh 00:02:08.389 --> 00:02:08.399 align:start position:0% strange Jira build issues. I believe uh 00:02:08.399 --> 00:02:11.589 align:start position:0% strange Jira build issues. I believe uh is<00:02:08.640> there<00:02:08.800> is<00:02:08.959> a<00:02:09.119> fix<00:02:09.360> for<00:02:09.599> NFS<00:02:10.239> version<00:02:10.640> 4<00:02:11.280> that 00:02:11.589 --> 00:02:11.599 align:start position:0% is there is a fix for NFS version 4 that 00:02:11.599 --> 00:02:13.430 align:start position:0% is there is a fix for NFS version 4 that has<00:02:11.760> to<00:02:11.920> do<00:02:12.080> with<00:02:12.239> how<00:02:12.480> it's<00:02:12.720> counting<00:02:13.200> sort<00:02:13.360> of 00:02:13.430 --> 00:02:13.440 align:start position:0% has to do with how it's counting sort of 00:02:13.440 --> 00:02:17.110 align:start position:0% has to do with how it's counting sort of those<00:02:13.760> change<00:02:14.239> ID<00:02:14.640> values<00:02:15.120> for<00:02:15.360> NFS<00:02:16.000> v4.<00:02:16.879> This 00:02:17.110 --> 00:02:17.120 align:start position:0% those change ID values for NFS v4. This 00:02:17.120 --> 00:02:18.630 align:start position:0% those change ID values for NFS v4. This is<00:02:17.280> really<00:02:17.520> important<00:02:17.840> for<00:02:18.080> those<00:02:18.160> of<00:02:18.319> you<00:02:18.480> who 00:02:18.630 --> 00:02:18.640 align:start position:0% is really important for those of you who 00:02:18.640 --> 00:02:22.309 align:start position:0% is really important for those of you who are<00:02:18.879> using<00:02:19.200> VMware<00:02:19.840> ESX<00:02:20.480> or<00:02:20.720> VMware<00:02:21.200> vSphere 00:02:22.309 --> 00:02:22.319 align:start position:0% are using VMware ESX or VMware vSphere 00:02:22.319 --> 00:02:24.630 align:start position:0% are using VMware ESX or VMware vSphere because<00:02:22.879> that<00:02:23.200> lets<00:02:23.520> it<00:02:23.760> actually<00:02:24.160> understand 00:02:24.630 --> 00:02:24.640 align:start position:0% because that lets it actually understand 00:02:24.640 --> 00:02:26.150 align:start position:0% because that lets it actually understand when<00:02:24.879> it's<00:02:25.120> doing<00:02:25.280> these<00:02:25.599> tiny<00:02:26.000> little 00:02:26.150 --> 00:02:26.160 align:start position:0% when it's doing these tiny little 00:02:26.160 --> 00:02:28.710 align:start position:0% when it's doing these tiny little incremental<00:02:26.800> changes.<00:02:27.920> This<00:02:28.319> sort<00:02:28.560> of 00:02:28.710 --> 00:02:28.720 align:start position:0% incremental changes. This sort of 00:02:28.720 --> 00:02:29.990 align:start position:0% incremental changes. This sort of surfaced<00:02:29.120> when<00:02:29.360> you<00:02:29.520> had<00:02:29.599> a<00:02:29.840> really 00:02:29.990 --> 00:02:30.000 align:start position:0% surfaced when you had a really 00:02:30.000 --> 00:02:31.670 align:start position:0% surfaced when you had a really high-speed<00:02:30.560> network.<00:02:30.959> Now,<00:02:31.200> back<00:02:31.360> in<00:02:31.520> the 00:02:31.670 --> 00:02:31.680 align:start position:0% high-speed network. Now, back in the 00:02:31.680 --> 00:02:33.509 align:start position:0% high-speed network. Now, back in the day,<00:02:31.920> this<00:02:32.080> would<00:02:32.239> have<00:02:32.400> been<00:02:32.959> kind<00:02:33.200> of<00:02:33.280> hard 00:02:33.509 --> 00:02:33.519 align:start position:0% day, this would have been kind of hard 00:02:33.519 --> 00:02:35.030 align:start position:0% day, this would have been kind of hard to<00:02:33.680> get<00:02:33.840> past<00:02:34.160> because<00:02:34.400> you'd<00:02:34.640> have<00:02:34.720> to<00:02:34.879> be 00:02:35.030 --> 00:02:35.040 align:start position:0% to get past because you'd have to be 00:02:35.040 --> 00:02:36.470 align:start position:0% to get past because you'd have to be running,<00:02:35.280> you<00:02:35.440> know,<00:02:35.599> something<00:02:35.920> faster<00:02:36.239> than 00:02:36.470 --> 00:02:36.480 align:start position:0% running, you know, something faster than 00:02:36.480 --> 00:02:39.030 align:start position:0% running, you know, something faster than 10<00:02:36.800> gig<00:02:37.120> or<00:02:37.599> maybe<00:02:37.760> you'd<00:02:38.080> see<00:02:38.160> it<00:02:38.319> on<00:02:38.480> 10<00:02:38.720> gig 00:02:39.030 --> 00:02:39.040 align:start position:0% 10 gig or maybe you'd see it on 10 gig 00:02:39.040 --> 00:02:41.430 align:start position:0% 10 gig or maybe you'd see it on 10 gig during<00:02:39.280> a<00:02:39.440> period<00:02:39.680> of<00:02:39.840> really<00:02:40.400> uh<00:02:40.720> low<00:02:41.040> network 00:02:41.430 --> 00:02:41.440 align:start position:0% during a period of really uh low network 00:02:41.440 --> 00:02:44.070 align:start position:0% during a period of really uh low network congestion.<00:02:42.560> But<00:02:42.959> this<00:02:43.200> would<00:02:43.360> be<00:02:43.440> a<00:02:43.599> sporadic 00:02:44.070 --> 00:02:44.080 align:start position:0% congestion. But this would be a sporadic 00:02:44.080 --> 00:02:45.430 align:start position:0% congestion. But this would be a sporadic issue.<00:02:44.319> you'd<00:02:44.560> see<00:02:44.640> it<00:02:44.800> after<00:02:45.120> trying<00:02:45.280> to 00:02:45.430 --> 00:02:45.440 align:start position:0% issue. you'd see it after trying to 00:02:45.440 --> 00:02:48.229 align:start position:0% issue. you'd see it after trying to clone<00:02:45.680> a<00:02:45.920> VM<00:02:46.560> uh<00:02:46.640> when<00:02:46.879> you<00:02:47.040> would<00:02:47.200> use<00:02:47.360> a<00:02:48.160> you 00:02:48.229 --> 00:02:48.239 align:start position:0% clone a VM uh when you would use a you 00:02:48.239 --> 00:02:49.990 align:start position:0% clone a VM uh when you would use a you know<00:02:48.400> one<00:02:48.480> of<00:02:48.560> the<00:02:48.800> fast<00:02:49.120> ZFS<00:02:49.599> cloning 00:02:49.990 --> 00:02:50.000 align:start position:0% know one of the fast ZFS cloning 00:02:50.000 --> 00:02:51.830 align:start position:0% know one of the fast ZFS cloning primitives<00:02:50.400> or<00:02:50.640> something<00:02:50.879> like<00:02:51.040> that.<00:02:51.680> But 00:02:51.830 --> 00:02:51.840 align:start position:0% primitives or something like that. But 00:02:51.840 --> 00:02:54.070 align:start position:0% primitives or something like that. But now<00:02:52.080> with<00:02:52.400> 25<00:02:52.720> gig<00:02:53.120> 40<00:02:53.360> gig<00:02:53.680> people<00:02:53.840> would<00:02:54.000> see 00:02:54.070 --> 00:02:54.080 align:start position:0% now with 25 gig 40 gig people would see 00:02:54.080 --> 00:02:55.990 align:start position:0% now with 25 gig 40 gig people would see it<00:02:54.319> more<00:02:54.480> commonly.<00:02:55.360> We've<00:02:55.680> actually 00:02:55.990 --> 00:02:56.000 align:start position:0% it more commonly. We've actually 00:02:56.000 --> 00:02:57.509 align:start position:0% it more commonly. We've actually corrected<00:02:56.400> this.<00:02:56.720> This<00:02:56.879> required<00:02:57.200> a<00:02:57.440> little 00:02:57.509 --> 00:02:57.519 align:start position:0% corrected this. This required a little 00:02:57.519 --> 00:03:00.470 align:start position:0% corrected this. This required a little bit<00:02:57.599> of<00:02:57.760> upstream<00:02:58.239> work<00:02:58.560> in<00:02:58.879> ZFS<00:02:59.440> to<00:02:59.760> expose<00:03:00.160> an 00:03:00.470 --> 00:03:00.480 align:start position:0% bit of upstream work in ZFS to expose an 00:03:00.480 --> 00:03:02.949 align:start position:0% bit of upstream work in ZFS to expose an underlying<00:03:01.040> ZFS<00:03:01.599> counter<00:03:02.000> in<00:03:02.239> there.<00:03:02.720> Uh 00:03:02.949 --> 00:03:02.959 align:start position:0% underlying ZFS counter in there. Uh 00:03:02.959 --> 00:03:05.509 align:start position:0% underlying ZFS counter in there. Uh because<00:03:03.200> again<00:03:03.519> ZFS<00:03:04.080> being<00:03:04.400> atomic,<00:03:04.959> it<00:03:05.200> knows 00:03:05.509 --> 00:03:05.519 align:start position:0% because again ZFS being atomic, it knows 00:03:05.519 --> 00:03:07.350 align:start position:0% because again ZFS being atomic, it knows it's<00:03:05.760> got<00:03:05.920> a<00:03:06.239> iteration<00:03:06.640> in<00:03:06.800> there.<00:03:07.040> It<00:03:07.200> says 00:03:07.350 --> 00:03:07.360 align:start position:0% it's got a iteration in there. It says 00:03:07.360 --> 00:03:09.270 align:start position:0% it's got a iteration in there. It says hey<00:03:08.000> um<00:03:08.239> I<00:03:08.400> don't<00:03:08.560> care<00:03:08.720> how<00:03:08.879> many<00:03:09.040> times 00:03:09.270 --> 00:03:09.280 align:start position:0% hey um I don't care how many times 00:03:09.280 --> 00:03:10.869 align:start position:0% hey um I don't care how many times you've<00:03:09.519> changed<00:03:09.840> this<00:03:10.080> file<00:03:10.319> in<00:03:10.560> the<00:03:10.640> last 00:03:10.869 --> 00:03:10.879 align:start position:0% you've changed this file in the last 00:03:10.879 --> 00:03:13.350 align:start position:0% you've changed this file in the last millisecond.<00:03:12.159> uh<00:03:12.319> I'm<00:03:12.480> I'm<00:03:12.800> tracking<00:03:13.040> each<00:03:13.280> of 00:03:13.350 --> 00:03:13.360 align:start position:0% millisecond. uh I'm I'm tracking each of 00:03:13.360 --> 00:03:16.070 align:start position:0% millisecond. uh I'm I'm tracking each of those<00:03:13.599> changes<00:03:13.920> separately.<00:03:14.879> So<00:03:15.519> it<00:03:15.760> can<00:03:15.920> now 00:03:16.070 --> 00:03:16.080 align:start position:0% those changes separately. So it can now 00:03:16.080 --> 00:03:18.309 align:start position:0% those changes separately. So it can now get<00:03:16.319> all<00:03:16.480> of<00:03:16.640> the<00:03:16.800> precision<00:03:17.280> that<00:03:18.000> is 00:03:18.309 --> 00:03:18.319 align:start position:0% get all of the precision that is 00:03:18.319 --> 00:03:20.229 align:start position:0% get all of the precision that is required<00:03:18.879> no<00:03:18.959> matter<00:03:19.280> how<00:03:19.519> fast<00:03:19.760> your<00:03:19.920> network 00:03:20.229 --> 00:03:20.239 align:start position:0% required no matter how fast your network 00:03:20.239 --> 00:03:22.630 align:start position:0% required no matter how fast your network interlink<00:03:20.800> is.<00:03:21.360> So<00:03:21.599> if<00:03:21.760> we've<00:03:22.080> got<00:03:22.239> some<00:03:22.480> of 00:03:22.630 --> 00:03:22.640 align:start position:0% interlink is. So if we've got some of 00:03:22.640 --> 00:03:24.390 align:start position:0% interlink is. So if we've got some of the<00:03:22.959> uh<00:03:23.200> community<00:03:23.599> out<00:03:23.760> there<00:03:24.000> that's 00:03:24.390 --> 00:03:24.400 align:start position:0% the uh community out there that's 00:03:24.400 --> 00:03:27.430 align:start position:0% the uh community out there that's running<00:03:24.959> uh<00:03:25.120> VMware<00:03:25.680> ESX<00:03:26.640> and<00:03:26.959> you're<00:03:27.200> using 00:03:27.430 --> 00:03:27.440 align:start position:0% running uh VMware ESX and you're using 00:03:27.440 --> 00:03:29.750 align:start position:0% running uh VMware ESX and you're using NFSV4<00:03:28.319> and<00:03:28.560> you've<00:03:28.879> noticed<00:03:29.120> these<00:03:29.440> kind<00:03:29.599> of 00:03:29.750 --> 00:03:29.760 align:start position:0% NFSV4 and you've noticed these kind of 00:03:29.760 --> 00:03:32.149 align:start position:0% NFSV4 and you've noticed these kind of strange<00:03:30.319> intermittent<00:03:30.959> issues,<00:03:31.840> uh<00:03:32.000> those 00:03:32.149 --> 00:03:32.159 align:start position:0% strange intermittent issues, uh those 00:03:32.159 --> 00:03:34.149 align:start position:0% strange intermittent issues, uh those are<00:03:32.319> always<00:03:32.560> the<00:03:32.799> most<00:03:33.040> fun<00:03:33.200> to<00:03:33.440> track<00:03:33.760> down. 00:03:34.149 --> 00:03:34.159 align:start position:0% are always the most fun to track down. 00:03:34.159 --> 00:03:34.550 align:start position:0% are always the most fun to track down. Mhm. 00:03:34.550 --> 00:03:34.560 align:start position:0% Mhm. 00:03:34.560 --> 00:03:37.670 align:start position:0% Mhm. >> Uh<00:03:34.799> do<00:03:34.959> us<00:03:35.120> a<00:03:35.280> favor,<00:03:35.519> give<00:03:35.840> 25102.1, 00:03:37.670 --> 00:03:37.680 align:start position:0% >> Uh do us a favor, give 25102.1, 00:03:37.680 --> 00:03:40.789 align:start position:0% >> Uh do us a favor, give 25102.1, give<00:03:37.840> this<00:03:38.000> hot<00:03:38.239> fix<00:03:38.480> a<00:03:38.720> shot<00:03:39.280> and<00:03:39.680> see<00:03:39.920> if<00:03:40.239> this 00:03:40.789 --> 00:03:40.799 align:start position:0% give this hot fix a shot and see if this 00:03:40.799 --> 00:03:42.390 align:start position:0% give this hot fix a shot and see if this corrects<00:03:41.200> that<00:03:41.360> issue.<00:03:41.760> See<00:03:41.920> if<00:03:42.000> you<00:03:42.159> can<00:03:42.239> try 00:03:42.390 --> 00:03:42.400 align:start position:0% corrects that issue. See if you can try 00:03:42.400 --> 00:03:44.710 align:start position:0% corrects that issue. See if you can try to<00:03:42.560> force<00:03:42.799> it<00:03:42.959> to<00:03:43.120> surface<00:03:44.000> because<00:03:44.400> we 00:03:44.710 --> 00:03:44.720 align:start position:0% to force it to surface because we 00:03:44.720 --> 00:03:46.149 align:start position:0% to force it to surface because we believe<00:03:44.879> we've<00:03:45.200> actually<00:03:45.440> got<00:03:45.599> it<00:03:45.760> sorted 00:03:46.149 --> 00:03:46.159 align:start position:0% believe we've actually got it sorted 00:03:46.159 --> 00:03:48.550 align:start position:0% believe we've actually got it sorted this<00:03:46.400> time.<00:03:46.720> Um<00:03:47.280> I<00:03:47.519> I'm<00:03:47.920> pretty<00:03:48.080> big<00:03:48.319> fan<00:03:48.400> of 00:03:48.550 --> 00:03:48.560 align:start position:0% this time. Um I I'm pretty big fan of 00:03:48.560 --> 00:03:50.149 align:start position:0% this time. Um I I'm pretty big fan of this.<00:03:48.879> I'm<00:03:49.120> really<00:03:49.360> happy<00:03:49.519> with<00:03:49.680> the<00:03:49.840> work<00:03:49.920> the 00:03:50.149 --> 00:03:50.159 align:start position:0% this. I'm really happy with the work the 00:03:50.159 --> 00:03:52.309 align:start position:0% this. I'm really happy with the work the engineering<00:03:50.640> team<00:03:50.879> did<00:03:51.360> and<00:03:51.760> uh<00:03:51.840> shout<00:03:52.080> out<00:03:52.239> to 00:03:52.309 --> 00:03:52.319 align:start position:0% engineering team did and uh shout out to 00:03:52.319 --> 00:03:53.990 align:start position:0% engineering team did and uh shout out to the<00:03:52.480> member<00:03:52.640> of<00:03:52.720> our<00:03:52.959> community<00:03:53.200> who<00:03:53.519> sort<00:03:53.680> of 00:03:53.990 --> 00:03:54.000 align:start position:0% the member of our community who sort of 00:03:54.000 --> 00:03:56.470 align:start position:0% the member of our community who sort of uh<00:03:54.319> gave<00:03:54.560> us<00:03:54.720> some<00:03:54.879> assistance<00:03:55.360> and<00:03:56.000> helped<00:03:56.319> by 00:03:56.470 --> 00:03:56.480 align:start position:0% uh gave us some assistance and helped by 00:03:56.480 --> 00:03:58.710 align:start position:0% uh gave us some assistance and helped by dumping<00:03:56.879> some<00:03:57.040> logs<00:03:57.439> to<00:03:57.599> us<00:03:58.080> to<00:03:58.319> track<00:03:58.560> down 00:03:58.710 --> 00:03:58.720 align:start position:0% dumping some logs to us to track down 00:03:58.720 --> 00:04:00.869 align:start position:0% dumping some logs to us to track down that<00:03:58.959> root<00:03:59.280> cause.<00:03:59.920> Um,<00:04:00.239> you<00:04:00.319> know,<00:04:00.480> we<00:04:00.640> really 00:04:00.869 --> 00:04:00.879 align:start position:0% that root cause. Um, you know, we really 00:04:00.879 --> 00:04:02.309 align:start position:0% that root cause. Um, you know, we really appreciate<00:04:01.200> that<00:04:01.360> and<00:04:01.599> it's<00:04:01.840> great<00:04:02.000> to<00:04:02.159> see 00:04:02.309 --> 00:04:02.319 align:start position:0% appreciate that and it's great to see 00:04:02.319 --> 00:04:03.990 align:start position:0% appreciate that and it's great to see that<00:04:02.560> sort<00:04:02.720> of<00:04:02.799> community<00:04:03.200> teamwork<00:04:03.680> going<00:04:03.840> on 00:04:03.990 --> 00:04:04.000 align:start position:0% that sort of community teamwork going on 00:04:04.000 --> 00:04:05.030 align:start position:0% that sort of community teamwork going on here,<00:04:04.319> Chris. 00:04:05.030 --> 00:04:05.040 align:start position:0% here, Chris. 00:04:05.040 --> 00:04:06.390 align:start position:0% here, Chris. >> Yeah.<00:04:05.280> No,<00:04:05.439> that's<00:04:05.680> awesome.<00:04:05.920> And<00:04:06.080> those<00:04:06.239> are 00:04:06.390 --> 00:04:06.400 align:start position:0% >> Yeah. No, that's awesome. And those are 00:04:06.400 --> 00:04:07.910 align:start position:0% >> Yeah. No, that's awesome. And those are the<00:04:06.560> hardest<00:04:06.799> things<00:04:06.959> to<00:04:07.200> solve<00:04:07.519> again<00:04:07.760> where 00:04:07.910 --> 00:04:07.920 align:start position:0% the hardest things to solve again where 00:04:07.920 --> 00:04:09.670 align:start position:0% the hardest things to solve again where it's<00:04:08.159> intermittent<00:04:08.720> at<00:04:08.879> best<00:04:09.120> and<00:04:09.360> you<00:04:09.519> can't 00:04:09.670 --> 00:04:09.680 align:start position:0% it's intermittent at best and you can't 00:04:09.680 --> 00:04:12.229 align:start position:0% it's intermittent at best and you can't quite<00:04:09.920> find<00:04:10.239> ways<00:04:10.480> to<00:04:10.640> surface<00:04:11.040> it<00:04:11.280> reliably. 00:04:12.229 --> 00:04:12.239 align:start position:0% quite find ways to surface it reliably. 00:04:12.239 --> 00:04:13.670 align:start position:0% quite find ways to surface it reliably. It's<00:04:12.400> such<00:04:12.560> a<00:04:12.720> pain<00:04:12.799> in<00:04:12.959> the<00:04:13.040> rear<00:04:13.280> to<00:04:13.439> an 00:04:13.670 --> 00:04:13.680 align:start position:0% It's such a pain in the rear to an 00:04:13.680 --> 00:04:14.309 align:start position:0% It's such a pain in the rear to an engineer. 00:04:14.309 --> 00:04:14.319 align:start position:0% engineer. 00:04:14.319 --> 00:04:16.469 align:start position:0% engineer. >> Exactly.<00:04:14.799> It's<00:04:15.360> the<00:04:15.599> hardest<00:04:15.920> part<00:04:16.079> is<00:04:16.320> when 00:04:16.469 --> 00:04:16.479 align:start position:0% >> Exactly. It's the hardest part is when 00:04:16.479 --> 00:04:18.069 align:start position:0% >> Exactly. It's the hardest part is when it's<00:04:16.639> like<00:04:16.880> you<00:04:17.040> have<00:04:17.199> to<00:04:17.280> beat<00:04:17.600> on<00:04:17.759> something 00:04:18.069 --> 00:04:18.079 align:start position:0% it's like you have to beat on something 00:04:18.079 --> 00:04:20.150 align:start position:0% it's like you have to beat on something for<00:04:18.320> 2<00:04:18.560> hours<00:04:18.799> just<00:04:19.040> to<00:04:19.199> get<00:04:19.280> the<00:04:19.519> chance<00:04:19.759> of<00:04:19.919> a 00:04:20.150 --> 00:04:20.160 align:start position:0% for 2 hours just to get the chance of a 00:04:20.160 --> 00:04:22.550 align:start position:0% for 2 hours just to get the chance of a failure.<00:04:20.959> It<00:04:21.280> makes<00:04:21.440> those<00:04:21.680> test<00:04:22.000> cycles<00:04:22.320> so 00:04:22.550 --> 00:04:22.560 align:start position:0% failure. It makes those test cycles so 00:04:22.560 --> 00:04:24.230 align:start position:0% failure. It makes those test cycles so much<00:04:22.720> longer<00:04:23.120> and<00:04:23.440> so<00:04:23.680> much<00:04:23.840> harder<00:04:24.080> to 00:04:24.230 --> 00:04:24.240 align:start position:0% much longer and so much harder to 00:04:24.240 --> 00:04:26.310 align:start position:0% much longer and so much harder to surface.<00:04:24.720> So<00:04:24.880> again,<00:04:25.600> uh<00:04:25.759> thank<00:04:25.919> you<00:04:26.080> very 00:04:26.310 --> 00:04:26.320 align:start position:0% surface. So again, uh thank you very 00:04:26.320 --> 00:04:28.390 align:start position:0% surface. So again, uh thank you very much<00:04:26.479> to<00:04:26.720> the<00:04:26.960> community<00:04:27.280> member<00:04:27.600> who<00:04:28.000> uh<00:04:28.160> gave 00:04:28.390 --> 00:04:28.400 align:start position:0% much to the community member who uh gave 00:04:28.400 --> 00:04:29.909 align:start position:0% much to the community member who uh gave us<00:04:28.479> the<00:04:28.720> assist<00:04:29.040> on<00:04:29.199> that<00:04:29.360> one<00:04:29.440> and<00:04:29.680> was 00:04:29.909 --> 00:04:29.919 align:start position:0% us the assist on that one and was 00:04:29.919 --> 00:04:31.510 align:start position:0% us the assist on that one and was willing<00:04:30.160> to<00:04:30.320> share<00:04:30.479> their<00:04:30.720> logs<00:04:31.120> and<00:04:31.360> some 00:04:31.510 --> 00:04:31.520 align:start position:0% willing to share their logs and some 00:04:31.520 --> 00:04:33.990 align:start position:0% willing to share their logs and some debugs<00:04:32.080> from<00:04:32.560> not<00:04:32.800> just<00:04:32.880> the<00:04:33.120> trunaz<00:04:33.680> machine 00:04:33.990 --> 00:04:34.000 align:start position:0% debugs from not just the trunaz machine 00:04:34.000 --> 00:04:36.390 align:start position:0% debugs from not just the trunaz machine but<00:04:34.400> uh<00:04:34.720> did<00:04:34.960> some<00:04:35.199> redacting<00:04:35.759> and<00:04:36.000> shared<00:04:36.240> it 00:04:36.390 --> 00:04:36.400 align:start position:0% but uh did some redacting and shared it 00:04:36.400 --> 00:04:38.469 align:start position:0% but uh did some redacting and shared it from<00:04:36.560> one<00:04:36.639> of<00:04:36.720> their<00:04:36.880> clients<00:04:37.280> as<00:04:37.520> well. 00:04:38.469 --> 00:04:38.479 align:start position:0% from one of their clients as well. 00:04:38.479 --> 00:04:41.189 align:start position:0% from one of their clients as well. >> So<00:04:39.360> uh<00:04:39.520> we<00:04:39.680> got<00:04:39.840> another<00:04:40.320> big<00:04:40.639> bit<00:04:40.800> of<00:04:41.040> news 00:04:41.189 --> 00:04:41.199 align:start position:0% >> So uh we got another big bit of news 00:04:41.199 --> 00:04:42.950 align:start position:0% >> So uh we got another big bit of news here<00:04:41.520> Chris<00:04:41.840> that<00:04:42.240> uh<00:04:42.400> maybe<00:04:42.560> we<00:04:42.800> want<00:04:42.880> to 00:04:42.950 --> 00:04:42.960 align:start position:0% here Chris that uh maybe we want to 00:04:42.960 --> 00:04:44.790 align:start position:0% here Chris that uh maybe we want to share<00:04:43.199> with<00:04:43.280> the<00:04:43.520> community.<00:04:44.000> So<00:04:44.240> I<00:04:44.479> will<00:04:44.639> let 00:04:44.790 --> 00:04:44.800 align:start position:0% share with the community. So I will let 00:04:44.800 --> 00:04:46.550 align:start position:0% share with the community. So I will let you<00:04:45.280> uh<00:04:45.440> handle<00:04:45.840> this<00:04:46.080> one. 00:04:46.550 --> 00:04:46.560 align:start position:0% you uh handle this one. 00:04:46.560 --> 00:04:48.710 align:start position:0% you uh handle this one. >> Sure.<00:04:47.120> So<00:04:47.520> regarding<00:04:48.000> smart<00:04:48.479> you<00:04:48.560> know 00:04:48.710 --> 00:04:48.720 align:start position:0% >> Sure. So regarding smart you know 00:04:48.720 --> 00:04:50.230 align:start position:0% >> Sure. So regarding smart you know obviously<00:04:49.120> that's<00:04:49.440> been<00:04:49.520> a<00:04:49.759> controversial 00:04:50.230 --> 00:04:50.240 align:start position:0% obviously that's been a controversial 00:04:50.240 --> 00:04:51.909 align:start position:0% obviously that's been a controversial topic<00:04:50.560> in<00:04:50.720> the<00:04:50.880> community<00:04:51.199> for<00:04:51.360> a<00:04:51.520> while<00:04:51.759> some 00:04:51.909 --> 00:04:51.919 align:start position:0% topic in the community for a while some 00:04:51.919 --> 00:04:54.310 align:start position:0% topic in the community for a while some of<00:04:52.000> the<00:04:52.160> changes<00:04:52.400> we<00:04:52.560> made<00:04:52.720> in<00:04:52.960> 2510.<00:04:53.919> We<00:04:54.160> just 00:04:54.310 --> 00:04:54.320 align:start position:0% of the changes we made in 2510. We just 00:04:54.320 --> 00:04:55.350 align:start position:0% of the changes we made in 2510. We just want<00:04:54.400> to<00:04:54.479> let<00:04:54.639> you<00:04:54.720> know<00:04:54.880> we're<00:04:55.040> not<00:04:55.199> going<00:04:55.280> to 00:04:55.350 --> 00:04:55.360 align:start position:0% want to let you know we're not going to 00:04:55.360 --> 00:04:57.110 align:start position:0% want to let you know we're not going to go<00:04:55.440> into<00:04:55.600> all<00:04:55.759> the<00:04:56.000> details<00:04:56.320> today,<00:04:56.639> but<00:04:56.880> we<00:04:56.960> do 00:04:57.110 --> 00:04:57.120 align:start position:0% go into all the details today, but we do 00:04:57.120 --> 00:04:58.790 align:start position:0% go into all the details today, but we do have<00:04:57.280> some<00:04:57.440> plans<00:04:57.759> pending<00:04:58.160> for<00:04:58.320> how<00:04:58.479> to<00:04:58.639> add 00:04:58.790 --> 00:04:58.800 align:start position:0% have some plans pending for how to add 00:04:58.800 --> 00:05:00.710 align:start position:0% have some plans pending for how to add some<00:04:59.040> better<00:04:59.360> visibility<00:04:59.840> and<00:05:00.160> light<00:05:00.400> command 00:05:00.710 --> 00:05:00.720 align:start position:0% some better visibility and light command 00:05:00.720 --> 00:05:03.430 align:start position:0% some better visibility and light command and<00:05:00.960> control<00:05:01.600> of<00:05:01.919> smart<00:05:02.320> into<00:05:02.639> the<00:05:02.880> 26 00:05:03.430 --> 00:05:03.440 align:start position:0% and control of smart into the 26 00:05:03.440 --> 00:05:05.430 align:start position:0% and control of smart into the 26 release.<00:05:04.080> Now,<00:05:04.320> we'll<00:05:04.560> have<00:05:04.720> more<00:05:04.880> details<00:05:05.280> on 00:05:05.430 --> 00:05:05.440 align:start position:0% release. Now, we'll have more details on 00:05:05.440 --> 00:05:07.430 align:start position:0% release. Now, we'll have more details on that<00:05:05.600> as<00:05:05.759> we<00:05:05.919> get<00:05:06.000> a<00:05:06.240> little<00:05:06.320> closer<00:05:06.560> to<00:05:06.720> the<00:05:06.960> 26 00:05:07.430 --> 00:05:07.440 align:start position:0% that as we get a little closer to the 26 00:05:07.440 --> 00:05:09.350 align:start position:0% that as we get a little closer to the 26 beta,<00:05:07.919> but<00:05:08.240> we're<00:05:08.560> expecting<00:05:08.880> it'll<00:05:09.199> give 00:05:09.350 --> 00:05:09.360 align:start position:0% beta, but we're expecting it'll give 00:05:09.360 --> 00:05:11.670 align:start position:0% beta, but we're expecting it'll give enough<00:05:09.600> back<00:05:09.840> in<00:05:10.080> regards<00:05:10.720> for<00:05:10.960> our<00:05:11.120> home<00:05:11.360> lab 00:05:11.670 --> 00:05:11.680 align:start position:0% enough back in regards for our home lab 00:05:11.680 --> 00:05:13.270 align:start position:0% enough back in regards for our home lab community<00:05:12.080> who<00:05:12.320> gets<00:05:12.479> the<00:05:12.639> comfort<00:05:12.960> out<00:05:13.120> of 00:05:13.270 --> 00:05:13.280 align:start position:0% community who gets the comfort out of 00:05:13.280 --> 00:05:14.790 align:start position:0% community who gets the comfort out of being<00:05:13.440> able<00:05:13.600> to<00:05:13.759> run<00:05:13.919> those<00:05:14.160> short<00:05:14.400> and<00:05:14.560> long 00:05:14.790 --> 00:05:14.800 align:start position:0% being able to run those short and long 00:05:14.800 --> 00:05:17.110 align:start position:0% being able to run those short and long tests,<00:05:15.120> parse<00:05:15.440> the<00:05:15.680> results,<00:05:16.479> all<00:05:16.639> that<00:05:16.880> good 00:05:17.110 --> 00:05:17.120 align:start position:0% tests, parse the results, all that good 00:05:17.120 --> 00:05:19.350 align:start position:0% tests, parse the results, all that good stuff.<00:05:17.440> So,<00:05:18.080> hoping<00:05:18.400> to<00:05:18.639> see<00:05:18.720> those<00:05:18.960> changes 00:05:19.350 --> 00:05:19.360 align:start position:0% stuff. So, hoping to see those changes 00:05:19.360 --> 00:05:20.950 align:start position:0% stuff. So, hoping to see those changes go<00:05:19.600> live<00:05:19.759> here<00:05:20.000> soon.<00:05:20.479> Those<00:05:20.639> will<00:05:20.880> get 00:05:20.950 --> 00:05:20.960 align:start position:0% go live here soon. Those will get 00:05:20.960 --> 00:05:22.150 align:start position:0% go live here soon. Those will get announced<00:05:21.280> once<00:05:21.520> they<00:05:21.680> land<00:05:21.919> in<00:05:22.080> the 00:05:22.150 --> 00:05:22.160 align:start position:0% announced once they land in the 00:05:22.160 --> 00:05:24.310 align:start position:0% announced once they land in the nightlys.<00:05:22.960> I'd<00:05:23.199> probably<00:05:23.440> be<00:05:23.600> adding<00:05:23.840> some<00:05:24.160> uh 00:05:24.310 --> 00:05:24.320 align:start position:0% nightlys. I'd probably be adding some uh 00:05:24.320 --> 00:05:26.390 align:start position:0% nightlys. I'd probably be adding some uh capability<00:05:24.800> to<00:05:25.039> the<00:05:25.199> experimental<00:05:25.759> MCP 00:05:26.390 --> 00:05:26.400 align:start position:0% capability to the experimental MCP 00:05:26.400 --> 00:05:27.990 align:start position:0% capability to the experimental MCP connector<00:05:26.720> we<00:05:26.960> talked<00:05:27.199> about<00:05:27.360> last<00:05:27.600> week<00:05:27.840> as 00:05:27.990 --> 00:05:28.000 align:start position:0% connector we talked about last week as 00:05:28.000 --> 00:05:30.230 align:start position:0% connector we talked about last week as well.<00:05:28.479> So<00:05:28.639> you<00:05:28.800> could<00:05:28.960> point<00:05:29.199> your<00:05:29.360> LLM<00:05:29.840> at<00:05:30.000> it 00:05:30.230 --> 00:05:30.240 align:start position:0% well. So you could point your LLM at it 00:05:30.240 --> 00:05:31.990 align:start position:0% well. So you could point your LLM at it and<00:05:30.400> then<00:05:30.560> do<00:05:30.720> some<00:05:30.880> analysis<00:05:31.360> of<00:05:31.600> the<00:05:31.759> more 00:05:31.990 --> 00:05:32.000 align:start position:0% and then do some analysis of the more 00:05:32.000 --> 00:05:34.629 align:start position:0% and then do some analysis of the more gory<00:05:32.400> smart<00:05:32.720> logs<00:05:33.039> and<00:05:33.199> details<00:05:33.520> as<00:05:33.840> well<00:05:34.400> as 00:05:34.629 --> 00:05:34.639 align:start position:0% gory smart logs and details as well as 00:05:34.639 --> 00:05:36.230 align:start position:0% gory smart logs and details as well as you<00:05:34.800> wish.<00:05:35.039> Actually<00:05:35.280> I<00:05:35.440> think<00:05:35.600> LLMs<00:05:36.080> might 00:05:36.230 --> 00:05:36.240 align:start position:0% you wish. Actually I think LLMs might 00:05:36.240 --> 00:05:37.670 align:start position:0% you wish. Actually I think LLMs might actually<00:05:36.479> be<00:05:36.639> pretty<00:05:36.880> useful<00:05:37.120> for<00:05:37.280> that<00:05:37.520> use 00:05:37.670 --> 00:05:37.680 align:start position:0% actually be pretty useful for that use 00:05:37.680 --> 00:05:39.110 align:start position:0% actually be pretty useful for that use case<00:05:37.919> too<00:05:38.080> where<00:05:38.320> it<00:05:38.479> can<00:05:38.560> go<00:05:38.720> and<00:05:38.880> kind<00:05:39.039> of 00:05:39.110 --> 00:05:39.120 align:start position:0% case too where it can go and kind of 00:05:39.120 --> 00:05:40.790 align:start position:0% case too where it can go and kind of make<00:05:39.280> sense<00:05:39.520> of<00:05:39.680> some<00:05:39.840> of<00:05:39.919> the<00:05:40.080> jargon<00:05:40.560> and 00:05:40.790 --> 00:05:40.800 align:start position:0% make sense of some of the jargon and 00:05:40.800 --> 00:05:42.390 align:start position:0% make sense of some of the jargon and sift<00:05:41.120> through<00:05:41.280> some<00:05:41.440> of<00:05:41.520> the<00:05:41.680> quirks<00:05:42.080> and<00:05:42.240> all 00:05:42.390 --> 00:05:42.400 align:start position:0% sift through some of the quirks and all 00:05:42.400 --> 00:05:44.390 align:start position:0% sift through some of the quirks and all that<00:05:42.560> good<00:05:42.800> stuff<00:05:43.360> and<00:05:43.680> hopefully<00:05:44.000> give<00:05:44.160> you 00:05:44.390 --> 00:05:44.400 align:start position:0% that good stuff and hopefully give you 00:05:44.400 --> 00:05:46.790 align:start position:0% that good stuff and hopefully give you more<00:05:44.960> meaningful<00:05:45.440> telemetry.<00:05:46.240> But<00:05:46.400> anyway, 00:05:46.790 --> 00:05:46.800 align:start position:0% more meaningful telemetry. But anyway, 00:05:46.800 --> 00:05:48.950 align:start position:0% more meaningful telemetry. But anyway, more<00:05:46.960> to<00:05:47.120> come<00:05:47.280> on<00:05:47.520> that.<00:05:48.000> You<00:05:48.160> know,<00:05:48.560> again, 00:05:48.950 --> 00:05:48.960 align:start position:0% more to come on that. You know, again, 00:05:48.960 --> 00:05:50.150 align:start position:0% more to come on that. You know, again, stay<00:05:49.199> tuned.<00:05:49.440> We're<00:05:49.600> not<00:05:49.759> going<00:05:49.840> to<00:05:49.919> get<00:05:50.000> into 00:05:50.150 --> 00:05:50.160 align:start position:0% stay tuned. We're not going to get into 00:05:50.160 --> 00:05:51.430 align:start position:0% stay tuned. We're not going to get into all<00:05:50.240> the<00:05:50.400> details<00:05:50.639> yet<00:05:50.880> until<00:05:51.039> we<00:05:51.199> can<00:05:51.360> show 00:05:51.430 --> 00:05:51.440 align:start position:0% all the details yet until we can show 00:05:51.440 --> 00:05:53.270 align:start position:0% all the details yet until we can show you<00:05:51.600> exactly<00:05:51.919> what<00:05:52.160> landed 00:05:53.270 --> 00:05:53.280 align:start position:0% you exactly what landed 00:05:53.280 --> 00:05:54.870 align:start position:0% you exactly what landed >> exactly.<00:05:53.840> That's<00:05:54.160> that's<00:05:54.560> going<00:05:54.639> to<00:05:54.720> be 00:05:54.870 --> 00:05:54.880 align:start position:0% >> exactly. That's that's going to be 00:05:54.880 --> 00:05:56.950 align:start position:0% >> exactly. That's that's going to be something<00:05:55.120> that<00:05:55.440> I<00:05:55.680> imagine<00:05:56.080> is<00:05:56.320> going<00:05:56.479> to<00:05:56.560> be 00:05:56.950 --> 00:05:56.960 align:start position:0% something that I imagine is going to be 00:05:56.960 --> 00:05:59.990 align:start position:0% something that I imagine is going to be discussed<00:05:57.440> fairly<00:05:58.479> to<00:05:58.880> no<00:05:59.280> extent<00:05:59.600> in<00:05:59.840> the 00:05:59.990 --> 00:06:00.000 align:start position:0% discussed fairly to no extent in the 00:06:00.000 --> 00:06:02.310 align:start position:0% discussed fairly to no extent in the comments.<00:06:00.800> Um,<00:06:01.280> you<00:06:01.440> know,<00:06:01.600> we<00:06:01.840> will<00:06:02.000> put<00:06:02.160> a 00:06:02.310 --> 00:06:02.320 align:start position:0% comments. Um, you know, we will put a 00:06:02.320 --> 00:06:04.070 align:start position:0% comments. Um, you know, we will put a thread<00:06:02.560> up<00:06:02.720> in<00:06:02.880> the<00:06:02.960> forums<00:06:03.360> as<00:06:03.600> well<00:06:03.759> for<00:06:03.919> you 00:06:04.070 --> 00:06:04.080 align:start position:0% thread up in the forums as well for you 00:06:04.080 --> 00:06:05.909 align:start position:0% thread up in the forums as well for you to<00:06:04.240> share<00:06:04.479> your<00:06:05.039> uh<00:06:05.199> comments<00:06:05.520> and<00:06:05.759> your 00:06:05.909 --> 00:06:05.919 align:start position:0% to share your uh comments and your 00:06:05.919 --> 00:06:08.230 align:start position:0% to share your uh comments and your opinions<00:06:06.240> on<00:06:06.479> this<00:06:06.639> one.<00:06:07.199> But<00:06:07.360> again,<00:06:07.919> uh, 00:06:08.230 --> 00:06:08.240 align:start position:0% opinions on this one. But again, uh, 00:06:08.240 --> 00:06:10.390 align:start position:0% opinions on this one. But again, uh, give<00:06:08.479> us<00:06:08.639> a<00:06:08.800> little<00:06:08.960> bit<00:06:09.120> here<00:06:09.759> while<00:06:10.000> we<00:06:10.240> sort 00:06:10.390 --> 00:06:10.400 align:start position:0% give us a little bit here while we sort 00:06:10.400 --> 00:06:11.830 align:start position:0% give us a little bit here while we sort of<00:06:10.560> structure<00:06:10.960> out<00:06:11.120> and<00:06:11.280> then<00:06:11.440> we're<00:06:11.600> going<00:06:11.680> to 00:06:11.830 --> 00:06:11.840 align:start position:0% of structure out and then we're going to 00:06:11.840 --> 00:06:13.670 align:start position:0% of structure out and then we're going to share<00:06:12.080> you<00:06:12.319> some<00:06:12.560> more<00:06:12.720> details<00:06:13.120> as<00:06:13.360> Chris 00:06:13.670 --> 00:06:13.680 align:start position:0% share you some more details as Chris 00:06:13.680 --> 00:06:16.390 align:start position:0% share you some more details as Chris said<00:06:14.080> as<00:06:14.319> we<00:06:14.560> get<00:06:14.720> closer<00:06:14.960> to<00:06:15.120> Trunaz<00:06:15.680> 26,<00:06:16.080> the 00:06:16.390 --> 00:06:16.400 align:start position:0% said as we get closer to Trunaz 26, the 00:06:16.400 --> 00:06:17.590 align:start position:0% said as we get closer to Trunaz 26, the first<00:06:16.560> beta. 00:06:17.590 --> 00:06:17.600 align:start position:0% first beta. 00:06:17.600 --> 00:06:20.710 align:start position:0% first beta. >> Absolutely.<00:06:18.960> Okay.<00:06:19.520> And<00:06:19.759> then<00:06:20.160> some<00:06:20.400> other 00:06:20.710 --> 00:06:20.720 align:start position:0% >> Absolutely. Okay. And then some other 00:06:20.720 --> 00:06:22.390 align:start position:0% >> Absolutely. Okay. And then some other exciting<00:06:21.120> news<00:06:21.280> this<00:06:21.600> week.<00:06:21.840> Let's<00:06:22.080> get<00:06:22.240> into 00:06:22.390 --> 00:06:22.400 align:start position:0% exciting news this week. Let's get into 00:06:22.400 --> 00:06:24.710 align:start position:0% exciting news this week. Let's get into the<00:06:22.560> Proxmox<00:06:23.280> Trunaz<00:06:23.840> side<00:06:24.080> as<00:06:24.240> well.<00:06:24.400> I<00:06:24.560> think 00:06:24.710 --> 00:06:24.720 align:start position:0% the Proxmox Trunaz side as well. I think 00:06:24.720 --> 00:06:26.550 align:start position:0% the Proxmox Trunaz side as well. I think we<00:06:24.880> did<00:06:25.039> some<00:06:25.199> new<00:06:25.440> things<00:06:25.680> and<00:06:26.080> uh<00:06:26.160> a<00:06:26.400> few<00:06:26.479> of 00:06:26.550 --> 00:06:26.560 align:start position:0% we did some new things and uh a few of 00:06:26.560 --> 00:06:27.909 align:start position:0% we did some new things and uh a few of you<00:06:26.720> have<00:06:26.800> already<00:06:27.039> noticed<00:06:27.360> because<00:06:27.600> we<00:06:27.759> see 00:06:27.909 --> 00:06:27.919 align:start position:0% you have already noticed because we see 00:06:27.919 --> 00:06:29.990 align:start position:0% you have already noticed because we see people<00:06:28.160> starting<00:06:28.479> to<00:06:28.639> look<00:06:28.720> at<00:06:28.880> GitHub.<00:06:29.759> But 00:06:29.990 --> 00:06:30.000 align:start position:0% people starting to look at GitHub. But 00:06:30.000 --> 00:06:31.510 align:start position:0% people starting to look at GitHub. But uh<00:06:30.160> tell<00:06:30.319> us<00:06:30.479> about<00:06:30.560> that<00:06:30.880> Chris.<00:06:31.199> What's<00:06:31.360> this 00:06:31.510 --> 00:06:31.520 align:start position:0% uh tell us about that Chris. What's this 00:06:31.520 --> 00:06:32.710 align:start position:0% uh tell us about that Chris. What's this new<00:06:31.680> plugin<00:06:32.000> we<00:06:32.240> have? 00:06:32.710 --> 00:06:32.720 align:start position:0% new plugin we have? 00:06:32.720 --> 00:06:34.710 align:start position:0% new plugin we have? >> Absolutely.<00:06:33.360> So<00:06:33.520> what<00:06:33.759> we<00:06:33.919> have<00:06:34.080> done<00:06:34.240> is<00:06:34.479> we 00:06:34.710 --> 00:06:34.720 align:start position:0% >> Absolutely. So what we have done is we 00:06:34.720 --> 00:06:36.469 align:start position:0% >> Absolutely. So what we have done is we actually<00:06:35.039> reached<00:06:35.360> out<00:06:35.600> to<00:06:35.759> a<00:06:36.080> community 00:06:36.469 --> 00:06:36.479 align:start position:0% actually reached out to a community 00:06:36.479 --> 00:06:38.629 align:start position:0% actually reached out to a community member<00:06:36.800> who<00:06:36.960> had<00:06:37.199> been<00:06:37.360> creating<00:06:37.759> an<00:06:38.080> official 00:06:38.629 --> 00:06:38.639 align:start position:0% member who had been creating an official 00:06:38.639 --> 00:06:41.990 align:start position:0% member who had been creating an official plugin<00:06:39.199> for<00:06:39.600> Proxmox<00:06:40.880> uh<00:06:41.039> under<00:06:41.360> the<00:06:41.520> name<00:06:41.680> of 00:06:41.990 --> 00:06:42.000 align:start position:0% plugin for Proxmox uh under the name of 00:06:42.000 --> 00:06:44.870 align:start position:0% plugin for Proxmox uh under the name of Warlock<00:06:42.560> Sino.<00:06:43.199> So<00:06:43.440> we<00:06:43.680> reached<00:06:44.000> out<00:06:44.160> to<00:06:44.720> uh 00:06:44.870 --> 00:06:44.880 align:start position:0% Warlock Sino. So we reached out to uh 00:06:44.880 --> 00:06:47.510 align:start position:0% Warlock Sino. So we reached out to uh Mr.<00:06:45.280> Warlock<00:06:45.840> there<00:06:46.319> and<00:06:46.560> we<00:06:46.800> asked<00:06:46.960> him<00:06:47.120> if<00:06:47.360> he 00:06:47.510 --> 00:06:47.520 align:start position:0% Mr. Warlock there and we asked him if he 00:06:47.520 --> 00:06:49.590 align:start position:0% Mr. Warlock there and we asked him if he would<00:06:47.680> be<00:06:47.840> interested<00:06:48.240> in<00:06:48.720> you<00:06:48.960> know<00:06:49.199> bringing 00:06:49.590 --> 00:06:49.600 align:start position:0% would be interested in you know bringing 00:06:49.600 --> 00:06:52.469 align:start position:0% would be interested in you know bringing this<00:06:50.400> uh<00:06:50.639> property<00:06:51.039> sort<00:06:51.280> of<00:06:51.360> on<00:06:51.680> board<00:06:51.919> as<00:06:52.240> the 00:06:52.469 --> 00:06:52.479 align:start position:0% this uh property sort of on board as the 00:06:52.479 --> 00:06:56.230 align:start position:0% this uh property sort of on board as the official<00:06:53.360> Trunaz<00:06:54.000> Proxmox<00:06:54.639> plugin.<00:06:55.440> So<00:06:55.759> it<00:06:56.080> is 00:06:56.230 --> 00:06:56.240 align:start position:0% official Trunaz Proxmox plugin. So it is 00:06:56.240 --> 00:06:58.469 align:start position:0% official Trunaz Proxmox plugin. So it is now<00:06:56.479> under<00:06:56.800> our<00:06:56.960> GitHub<00:06:57.600> umbrella<00:06:58.000> there<00:06:58.400> uh 00:06:58.469 --> 00:06:58.479 align:start position:0% now under our GitHub umbrella there uh 00:06:58.479 --> 00:06:59.510 align:start position:0% now under our GitHub umbrella there uh which<00:06:58.639> you<00:06:58.800> can<00:06:58.960> see<00:06:59.120> under 00:06:59.510 --> 00:06:59.520 align:start position:0% which you can see under 00:06:59.520 --> 00:07:03.110 align:start position:0% which you can see under github.com/trunaz/trunazroxmox 00:07:03.110 --> 00:07:03.120 align:start position:0% 00:07:03.120 --> 00:07:05.270 align:start position:0% plugin.<00:07:03.759> It's<00:07:04.000> an<00:07:04.240> official<00:07:04.479> plugin.<00:07:04.960> It<00:07:05.120> is 00:07:05.270 --> 00:07:05.280 align:start position:0% plugin. It's an official plugin. It is 00:07:05.280 --> 00:07:07.670 align:start position:0% plugin. It's an official plugin. It is ready<00:07:05.520> for<00:07:05.759> community<00:07:06.240> testing<00:07:07.039> and<00:07:07.280> we<00:07:07.520> are 00:07:07.670 --> 00:07:07.680 align:start position:0% ready for community testing and we are 00:07:07.680 --> 00:07:09.110 align:start position:0% ready for community testing and we are currently<00:07:08.000> going<00:07:08.160> through<00:07:08.400> the<00:07:08.560> process<00:07:08.880> with 00:07:09.110 --> 00:07:09.120 align:start position:0% currently going through the process with 00:07:09.120 --> 00:07:11.029 align:start position:0% currently going through the process with Proxmox<00:07:09.759> to<00:07:09.840> get<00:07:09.919> it<00:07:10.160> validated<00:07:10.639> for 00:07:11.029 --> 00:07:11.039 align:start position:0% Proxmox to get it validated for 00:07:11.039 --> 00:07:13.029 align:start position:0% Proxmox to get it validated for enterprise<00:07:11.680> use.<00:07:12.240> test<00:07:12.479> out<00:07:12.720> things<00:07:12.880> like 00:07:13.029 --> 00:07:13.039 align:start position:0% enterprise use. test out things like 00:07:13.039 --> 00:07:15.350 align:start position:0% enterprise use. test out things like RDMA<00:07:13.759> functionality<00:07:14.319> and<00:07:14.560> our<00:07:14.800> use<00:07:14.960> with<00:07:15.120> our 00:07:15.350 --> 00:07:15.360 align:start position:0% RDMA functionality and our use with our 00:07:15.360 --> 00:07:18.390 align:start position:0% RDMA functionality and our use with our HA<00:07:15.759> systems<00:07:16.000> and<00:07:16.240> failover.<00:07:17.280> What<00:07:17.599> this<00:07:17.759> is<00:07:18.000> is 00:07:18.390 --> 00:07:18.400 align:start position:0% HA systems and failover. What this is is 00:07:18.400 --> 00:07:21.749 align:start position:0% HA systems and failover. What this is is a<00:07:18.639> way<00:07:18.800> to<00:07:19.039> extend<00:07:19.520> Proxmox's<00:07:20.479> ZFS<00:07:21.199> over<00:07:21.520> ice 00:07:21.749 --> 00:07:21.759 align:start position:0% a way to extend Proxmox's ZFS over ice 00:07:21.759 --> 00:07:24.390 align:start position:0% a way to extend Proxmox's ZFS over ice scuzzi<00:07:22.240> functionality<00:07:23.199> that<00:07:23.680> previously<00:07:24.160> did 00:07:24.390 --> 00:07:24.400 align:start position:0% scuzzi functionality that previously did 00:07:24.400 --> 00:07:26.950 align:start position:0% scuzzi functionality that previously did not<00:07:24.639> work<00:07:24.800> very<00:07:25.120> well<00:07:25.280> with<00:07:25.520> Trunaz<00:07:26.160> scale 00:07:26.950 --> 00:07:26.960 align:start position:0% not work very well with Trunaz scale 00:07:26.960 --> 00:07:29.270 align:start position:0% not work very well with Trunaz scale because<00:07:27.440> it<00:07:27.840> required<00:07:28.240> the<00:07:28.479> use<00:07:28.639> of<00:07:28.800> an<00:07:29.120> ice 00:07:29.270 --> 00:07:29.280 align:start position:0% because it required the use of an ice 00:07:29.280 --> 00:07:31.589 align:start position:0% because it required the use of an ice scuzzy<00:07:29.680> target<00:07:30.080> that<00:07:30.479> we<00:07:30.800> didn't<00:07:31.039> use. 00:07:31.589 --> 00:07:31.599 align:start position:0% scuzzy target that we didn't use. 00:07:31.599 --> 00:07:33.350 align:start position:0% scuzzy target that we didn't use. Proxmox<00:07:32.319> didn't<00:07:32.479> know<00:07:32.639> how<00:07:32.800> to<00:07:32.880> communicate 00:07:33.350 --> 00:07:33.360 align:start position:0% Proxmox didn't know how to communicate 00:07:33.360 --> 00:07:35.990 align:start position:0% Proxmox didn't know how to communicate with<00:07:33.680> SCST.<00:07:34.560> It<00:07:34.720> didn't<00:07:34.960> know<00:07:35.120> how<00:07:35.280> to<00:07:35.599> do<00:07:35.759> our 00:07:35.990 --> 00:07:36.000 align:start position:0% with SCST. It didn't know how to do our 00:07:36.000 --> 00:07:38.710 align:start position:0% with SCST. It didn't know how to do our provisioning<00:07:36.560> through<00:07:36.800> our<00:07:37.120> API.<00:07:38.160> So<00:07:38.479> this 00:07:38.710 --> 00:07:38.720 align:start position:0% provisioning through our API. So this 00:07:38.720 --> 00:07:41.110 align:start position:0% provisioning through our API. So this plugin<00:07:39.199> is<00:07:39.440> basically<00:07:39.759> a<00:07:40.000> nice<00:07:40.240> API<00:07:40.720> wrapper 00:07:41.110 --> 00:07:41.120 align:start position:0% plugin is basically a nice API wrapper 00:07:41.120 --> 00:07:43.830 align:start position:0% plugin is basically a nice API wrapper that<00:07:41.440> translates<00:07:41.919> Proxmox's<00:07:42.800> calls<00:07:43.120> for,<00:07:43.680> you 00:07:43.830 --> 00:07:43.840 align:start position:0% that translates Proxmox's calls for, you 00:07:43.840 --> 00:07:45.670 align:start position:0% that translates Proxmox's calls for, you know,<00:07:44.000> please<00:07:44.319> create<00:07:44.639> me<00:07:44.800> a<00:07:45.039> new<00:07:45.199> disk<00:07:45.520> to 00:07:45.670 --> 00:07:45.680 align:start position:0% know, please create me a new disk to 00:07:45.680 --> 00:07:49.670 align:start position:0% know, please create me a new disk to back<00:07:45.919> this<00:07:46.240> VM<00:07:47.039> into<00:07:47.440> trunaz<00:07:48.000> API<00:07:48.400> calls.<00:07:49.360> It's 00:07:49.670 --> 00:07:49.680 align:start position:0% back this VM into trunaz API calls. It's 00:07:49.680 --> 00:07:51.430 align:start position:0% back this VM into trunaz API calls. It's extending<00:07:50.080> all<00:07:50.240> that<00:07:50.479> functionality.<00:07:51.039> So<00:07:51.199> it 00:07:51.430 --> 00:07:51.440 align:start position:0% extending all that functionality. So it 00:07:51.440 --> 00:07:53.110 align:start position:0% extending all that functionality. So it allows<00:07:51.680> you<00:07:51.919> to<00:07:52.080> do<00:07:52.400> all<00:07:52.639> of<00:07:52.720> the<00:07:52.880> native 00:07:53.110 --> 00:07:53.120 align:start position:0% allows you to do all of the native 00:07:53.120 --> 00:07:54.710 align:start position:0% allows you to do all of the native Proxmox<00:07:53.840> behaviors.<00:07:54.240> You've<00:07:54.400> got<00:07:54.560> your 00:07:54.710 --> 00:07:54.720 align:start position:0% Proxmox behaviors. You've got your 00:07:54.720 --> 00:07:57.110 align:start position:0% Proxmox behaviors. You've got your snapshots,<00:07:55.599> you've<00:07:55.840> got<00:07:55.919> thin<00:07:56.319> provisioning, 00:07:57.110 --> 00:07:57.120 align:start position:0% snapshots, you've got thin provisioning, 00:07:57.120 --> 00:07:59.749 align:start position:0% snapshots, you've got thin provisioning, you've<00:07:57.360> got<00:07:57.599> automated<00:07:58.160> disc<00:07:58.479> resizing,<00:07:59.520> you 00:07:59.749 --> 00:07:59.759 align:start position:0% you've got automated disc resizing, you 00:07:59.759 --> 00:08:02.230 align:start position:0% you've got automated disc resizing, you can<00:07:59.840> handle<00:08:00.479> ice<00:08:00.639> scuzzi<00:08:01.199> and<00:08:01.440> NVME<00:08:02.000> over 00:08:02.230 --> 00:08:02.240 align:start position:0% can handle ice scuzzi and NVME over 00:08:02.240 --> 00:08:04.869 align:start position:0% can handle ice scuzzi and NVME over fabric<00:08:02.639> in<00:08:02.800> this<00:08:02.960> one.<00:08:03.599> It's<00:08:03.840> got<00:08:04.080> multipath 00:08:04.869 --> 00:08:04.879 align:start position:0% fabric in this one. It's got multipath 00:08:04.879 --> 00:08:07.029 align:start position:0% fabric in this one. It's got multipath support,<00:08:05.280> integrated<00:08:05.759> health<00:08:06.080> checks.<00:08:06.720> It's 00:08:07.029 --> 00:08:07.039 align:start position:0% support, integrated health checks. It's 00:08:07.039 --> 00:08:09.589 align:start position:0% support, integrated health checks. It's a<00:08:07.199> very<00:08:07.520> very<00:08:07.840> robust<00:08:08.319> way<00:08:08.560> to<00:08:08.879> expose<00:08:09.360> all 00:08:09.589 --> 00:08:09.599 align:start position:0% a very very robust way to expose all 00:08:09.599 --> 00:08:12.230 align:start position:0% a very very robust way to expose all those<00:08:09.840> functionalities<00:08:10.479> of<00:08:10.720> Trunaz<00:08:11.759> into 00:08:12.230 --> 00:08:12.240 align:start position:0% those functionalities of Trunaz into 00:08:12.240 --> 00:08:15.350 align:start position:0% those functionalities of Trunaz into your<00:08:12.560> Proxmox<00:08:13.280> system.<00:08:14.000> Um<00:08:14.639> it's<00:08:14.879> it's<00:08:15.199> been 00:08:15.350 --> 00:08:15.360 align:start position:0% your Proxmox system. Um it's it's been 00:08:15.360 --> 00:08:16.869 align:start position:0% your Proxmox system. Um it's it's been very<00:08:15.599> beneficial.<00:08:16.080> I've<00:08:16.319> been<00:08:16.400> testing<00:08:16.720> this 00:08:16.869 --> 00:08:16.879 align:start position:0% very beneficial. I've been testing this 00:08:16.879 --> 00:08:19.350 align:start position:0% very beneficial. I've been testing this out<00:08:17.120> for<00:08:17.440> quite<00:08:17.680> some<00:08:17.919> time.<00:08:18.479> Uh<00:08:18.800> even<00:08:19.039> before 00:08:19.350 --> 00:08:19.360 align:start position:0% out for quite some time. Uh even before 00:08:19.360 --> 00:08:20.950 align:start position:0% out for quite some time. Uh even before we<00:08:19.599> brought<00:08:19.840> it<00:08:19.919> on,<00:08:20.319> it<00:08:20.479> was<00:08:20.639> one<00:08:20.720> of<00:08:20.800> the 00:08:20.950 --> 00:08:20.960 align:start position:0% we brought it on, it was one of the 00:08:20.960 --> 00:08:22.950 align:start position:0% we brought it on, it was one of the things<00:08:21.039> that<00:08:21.199> sort<00:08:21.440> of<00:08:21.520> piqued<00:08:21.840> my<00:08:22.080> interest. 00:08:22.950 --> 00:08:22.960 align:start position:0% things that sort of piqued my interest. 00:08:22.960 --> 00:08:25.189 align:start position:0% things that sort of piqued my interest. Uh<00:08:23.280> especially<00:08:23.759> in<00:08:24.080> you<00:08:24.240> know<00:08:24.720> reaching<00:08:25.039> out 00:08:25.189 --> 00:08:25.199 align:start position:0% Uh especially in you know reaching out 00:08:25.199 --> 00:08:27.029 align:start position:0% Uh especially in you know reaching out and<00:08:25.360> saying<00:08:25.599> hey<00:08:25.840> this<00:08:26.000> is<00:08:26.080> a<00:08:26.319> this<00:08:26.560> is<00:08:26.639> a<00:08:26.879> good 00:08:27.029 --> 00:08:27.039 align:start position:0% and saying hey this is a this is a good 00:08:27.039 --> 00:08:29.110 align:start position:0% and saying hey this is a this is a good piece<00:08:27.199> of<00:08:27.360> software.<00:08:28.400> uh<00:08:28.560> we<00:08:28.800> think<00:08:28.879> it's 00:08:29.110 --> 00:08:29.120 align:start position:0% piece of software. uh we think it's 00:08:29.120 --> 00:08:30.710 align:start position:0% piece of software. uh we think it's going<00:08:29.199> to<00:08:29.280> be<00:08:29.360> really<00:08:29.680> beneficial<00:08:30.240> especially 00:08:30.710 --> 00:08:30.720 align:start position:0% going to be really beneficial especially 00:08:30.720 --> 00:08:33.909 align:start position:0% going to be really beneficial especially for<00:08:30.960> those<00:08:31.199> of<00:08:31.360> you<00:08:31.520> who<00:08:32.159> as<00:08:32.399> a<00:08:32.640> juosition<00:08:33.440> who 00:08:33.909 --> 00:08:33.919 align:start position:0% for those of you who as a juosition who 00:08:33.919 --> 00:08:36.149 align:start position:0% for those of you who as a juosition who like<00:08:34.080> I<00:08:34.240> said<00:08:34.560> are<00:08:34.800> customers<00:08:35.200> or<00:08:35.519> our<00:08:36.000> you 00:08:36.149 --> 00:08:36.159 align:start position:0% like I said are customers or our you 00:08:36.159 --> 00:08:38.389 align:start position:0% like I said are customers or our you know<00:08:36.320> community<00:08:36.640> members<00:08:37.120> running<00:08:37.599> VMware<00:08:38.240> at 00:08:38.389 --> 00:08:38.399 align:start position:0% know community members running VMware at 00:08:38.399 --> 00:08:40.310 align:start position:0% know community members running VMware at the<00:08:38.560> start<00:08:38.640> of<00:08:38.800> the<00:08:38.959> episode.<00:08:39.760> This<00:08:40.000> is<00:08:40.080> now 00:08:40.310 --> 00:08:40.320 align:start position:0% the start of the episode. This is now 00:08:40.320 --> 00:08:42.949 align:start position:0% the start of the episode. This is now for<00:08:40.479> those<00:08:40.640> of<00:08:40.719> you<00:08:41.200> who<00:08:41.519> have<00:08:41.839> left<00:08:42.159> VMware 00:08:42.949 --> 00:08:42.959 align:start position:0% for those of you who have left VMware 00:08:42.959 --> 00:08:44.790 align:start position:0% for those of you who have left VMware and<00:08:43.279> said<00:08:43.599> hey<00:08:43.839> maybe<00:08:44.080> I'd<00:08:44.320> like<00:08:44.560> something 00:08:44.790 --> 00:08:44.800 align:start position:0% and said hey maybe I'd like something 00:08:44.800 --> 00:08:46.389 align:start position:0% and said hey maybe I'd like something that's<00:08:45.120> a<00:08:45.279> little<00:08:45.360> bit<00:08:45.519> easier<00:08:45.839> to<00:08:46.000> provision 00:08:46.389 --> 00:08:46.399 align:start position:0% that's a little bit easier to provision 00:08:46.399 --> 00:08:48.870 align:start position:0% that's a little bit easier to provision my<00:08:46.640> storage.<00:08:47.360> So<00:08:48.000> this<00:08:48.240> this<00:08:48.560> is<00:08:48.720> something 00:08:48.870 --> 00:08:48.880 align:start position:0% my storage. So this this is something 00:08:48.880 --> 00:08:50.230 align:start position:0% my storage. So this this is something that's<00:08:49.120> been<00:08:49.279> going<00:08:49.440> pretty<00:08:49.680> well<00:08:49.920> Chris. 00:08:50.230 --> 00:08:50.240 align:start position:0% that's been going pretty well Chris. 00:08:50.240 --> 00:08:51.670 align:start position:0% that's been going pretty well Chris. We've<00:08:50.399> got<00:08:50.560> some<00:08:50.720> of<00:08:50.800> our<00:08:51.200> internal 00:08:51.670 --> 00:08:51.680 align:start position:0% We've got some of our internal 00:08:51.680 --> 00:08:53.190 align:start position:0% We've got some of our internal developers<00:08:52.160> working<00:08:52.399> on<00:08:52.560> this.<00:08:52.880> There's<00:08:53.040> been 00:08:53.190 --> 00:08:53.200 align:start position:0% developers working on this. There's been 00:08:53.200 --> 00:08:55.269 align:start position:0% developers working on this. There's been a<00:08:53.440> quite<00:08:53.600> a<00:08:53.760> flurry<00:08:54.080> of<00:08:54.240> activity<00:08:54.560> of<00:08:54.800> late<00:08:55.040> on 00:08:55.269 --> 00:08:55.279 align:start position:0% a quite a flurry of activity of late on 00:08:55.279 --> 00:08:57.750 align:start position:0% a quite a flurry of activity of late on that<00:08:55.680> uh<00:08:55.839> GitHub<00:08:56.320> repo<00:08:56.640> even.<00:08:57.279> Yeah,<00:08:57.519> we<00:08:57.760> have 00:08:57.750 --> 00:08:57.760 align:start position:0% that uh GitHub repo even. Yeah, we have 00:08:57.760 --> 00:08:59.750 align:start position:0% that uh GitHub repo even. Yeah, we have a<00:08:57.920> handful<00:08:58.160> of<00:08:58.320> internal<00:08:58.800> developers<00:08:59.279> who<00:08:59.519> use 00:08:59.750 --> 00:08:59.760 align:start position:0% a handful of internal developers who use 00:08:59.760 --> 00:09:01.750 align:start position:0% a handful of internal developers who use this<00:08:59.920> as<00:09:00.080> well<00:09:00.240> and<00:09:00.480> they<00:09:00.640> use<00:09:00.720> Proxmox<00:09:01.519> in 00:09:01.750 --> 00:09:01.760 align:start position:0% this as well and they use Proxmox in 00:09:01.760 --> 00:09:03.269 align:start position:0% this as well and they use Proxmox in conjunction<00:09:02.160> with<00:09:02.320> their<00:09:02.480> Trunz.<00:09:03.040> So,<00:09:03.120> it's 00:09:03.269 --> 00:09:03.279 align:start position:0% conjunction with their Trunz. So, it's 00:09:03.279 --> 00:09:04.790 align:start position:0% conjunction with their Trunz. So, it's it's<00:09:03.519> good<00:09:03.680> to<00:09:03.839> see<00:09:03.920> this<00:09:04.240> kind<00:09:04.399> of<00:09:04.480> come<00:09:04.640> to 00:09:04.790 --> 00:09:04.800 align:start position:0% it's good to see this kind of come to 00:09:04.800 --> 00:09:06.790 align:start position:0% it's good to see this kind of come to maturity<00:09:05.279> and<00:09:05.600> happen<00:09:05.839> and<00:09:06.160> have<00:09:06.480> something 00:09:06.790 --> 00:09:06.800 align:start position:0% maturity and happen and have something 00:09:06.800 --> 00:09:08.790 align:start position:0% maturity and happen and have something officially<00:09:07.279> under<00:09:07.519> the<00:09:07.600> Trune<00:09:08.320> umbrella 00:09:08.790 --> 00:09:08.800 align:start position:0% officially under the Trune umbrella 00:09:08.800 --> 00:09:10.790 align:start position:0% officially under the Trune umbrella which<00:09:08.959> is<00:09:09.200> great<00:09:09.360> to<00:09:09.519> see<00:09:09.680> and<00:09:10.080> uh<00:09:10.240> we'll<00:09:10.560> talk 00:09:10.790 --> 00:09:10.800 align:start position:0% which is great to see and uh we'll talk 00:09:10.800 --> 00:09:12.630 align:start position:0% which is great to see and uh we'll talk about<00:09:11.040> about<00:09:11.360> it<00:09:11.519> more<00:09:11.680> in<00:09:11.839> the<00:09:12.000> future<00:09:12.240> as<00:09:12.480> it 00:09:12.630 --> 00:09:12.640 align:start position:0% about about it more in the future as it 00:09:12.640 --> 00:09:14.710 align:start position:0% about about it more in the future as it goes<00:09:12.800> through<00:09:13.040> kind<00:09:13.200> of<00:09:13.279> its<00:09:13.680> uh<00:09:14.160> maturing 00:09:14.710 --> 00:09:14.720 align:start position:0% goes through kind of its uh maturing 00:09:14.720 --> 00:09:16.230 align:start position:0% goes through kind of its uh maturing phase<00:09:15.040> and<00:09:15.279> gets<00:09:15.519> that<00:09:15.680> enterprise 00:09:16.230 --> 00:09:16.240 align:start position:0% phase and gets that enterprise 00:09:16.240 --> 00:09:18.150 align:start position:0% phase and gets that enterprise acceptability,<00:09:17.120> gets<00:09:17.360> through<00:09:17.519> Proxmox 00:09:18.150 --> 00:09:18.160 align:start position:0% acceptability, gets through Proxmox 00:09:18.160 --> 00:09:19.750 align:start position:0% acceptability, gets through Proxmox testing,<00:09:18.560> all<00:09:18.720> that<00:09:18.880> good<00:09:19.040> stuff.<00:09:19.360> But<00:09:19.519> yeah, 00:09:19.750 --> 00:09:19.760 align:start position:0% testing, all that good stuff. But yeah, 00:09:19.760 --> 00:09:21.910 align:start position:0% testing, all that good stuff. But yeah, good<00:09:19.920> first<00:09:20.160> steps.<00:09:20.560> Excited.<00:09:21.600> Thank<00:09:21.760> you. 00:09:21.910 --> 00:09:21.920 align:start position:0% good first steps. Excited. Thank you. 00:09:21.920 --> 00:09:23.430 align:start position:0% good first steps. Excited. Thank you. This<00:09:22.080> is<00:09:22.160> a<00:09:22.320> good<00:09:22.480> collaboration<00:09:22.959> with<00:09:23.279> the 00:09:23.430 --> 00:09:23.440 align:start position:0% This is a good collaboration with the 00:09:23.440 --> 00:09:24.949 align:start position:0% This is a good collaboration with the community<00:09:23.760> member.<00:09:24.160> We<00:09:24.399> really<00:09:24.560> appreciate 00:09:24.949 --> 00:09:24.959 align:start position:0% community member. We really appreciate 00:09:24.959 --> 00:09:27.269 align:start position:0% community member. We really appreciate the<00:09:25.200> effort<00:09:25.440> to<00:09:25.680> make<00:09:25.760> this<00:09:26.080> happen<00:09:26.320> and<00:09:26.959> again 00:09:27.269 --> 00:09:27.279 align:start position:0% the effort to make this happen and again 00:09:27.279 --> 00:09:28.790 align:start position:0% the effort to make this happen and again I've<00:09:27.440> seen<00:09:27.760> because<00:09:27.920> we<00:09:28.080> we're<00:09:28.399> seeing<00:09:28.640> people 00:09:28.790 --> 00:09:28.800 align:start position:0% I've seen because we we're seeing people 00:09:28.800 --> 00:09:30.710 align:start position:0% I've seen because we we're seeing people go<00:09:28.959> on<00:09:29.120> there<00:09:29.279> and<00:09:29.440> star<00:09:29.760> the<00:09:30.000> repository<00:09:30.480> and 00:09:30.710 --> 00:09:30.720 align:start position:0% go on there and star the repository and 00:09:30.720 --> 00:09:32.470 align:start position:0% go on there and star the repository and stuff.<00:09:30.959> So<00:09:31.120> some<00:09:31.279> of<00:09:31.440> you<00:09:31.600> guys<00:09:31.680> are<00:09:31.839> nosy<00:09:32.320> and 00:09:32.470 --> 00:09:32.480 align:start position:0% stuff. So some of you guys are nosy and 00:09:32.480 --> 00:09:33.990 align:start position:0% stuff. So some of you guys are nosy and really<00:09:32.720> do<00:09:32.959> pay<00:09:33.120> attention<00:09:33.360> to<00:09:33.600> what's<00:09:33.839> going 00:09:33.990 --> 00:09:34.000 align:start position:0% really do pay attention to what's going 00:09:34.000 --> 00:09:36.150 align:start position:0% really do pay attention to what's going on<00:09:34.160> on<00:09:34.320> our<00:09:34.480> GitHub<00:09:34.880> repos.<00:09:35.360> So<00:09:35.760> hopefully 00:09:36.150 --> 00:09:36.160 align:start position:0% on on our GitHub repos. So hopefully 00:09:36.160 --> 00:09:37.590 align:start position:0% on on our GitHub repos. So hopefully you're<00:09:36.399> already<00:09:36.640> testing<00:09:36.959> it.<00:09:37.200> You're<00:09:37.360> having 00:09:37.590 --> 00:09:37.600 align:start position:0% you're already testing it. You're having 00:09:37.600 --> 00:09:39.590 align:start position:0% you're already testing it. You're having some<00:09:37.839> success.<00:09:38.640> We'd<00:09:38.880> love<00:09:38.959> to<00:09:39.120> hear<00:09:39.279> on<00:09:39.440> the 00:09:39.590 --> 00:09:39.600 align:start position:0% some success. We'd love to hear on the 00:09:39.600 --> 00:09:41.350 align:start position:0% some success. We'd love to hear on the comments<00:09:39.920> or<00:09:40.160> on<00:09:40.320> the<00:09:40.480> forums<00:09:40.880> if<00:09:41.120> you<00:09:41.200> have 00:09:41.350 --> 00:09:41.360 align:start position:0% comments or on the forums if you have 00:09:41.360 --> 00:09:44.470 align:start position:0% comments or on the forums if you have any<00:09:41.519> feedback<00:09:41.920> or<00:09:42.240> specific<00:09:42.640> issues<00:09:43.040> or<00:09:44.240> just 00:09:44.470 --> 00:09:44.480 align:start position:0% any feedback or specific issues or just 00:09:44.480 --> 00:09:46.470 align:start position:0% any feedback or specific issues or just any<00:09:44.800> any<00:09:45.200> info<00:09:45.440> you<00:09:45.600> can<00:09:45.760> give<00:09:45.839> us<00:09:46.000> about<00:09:46.320> what 00:09:46.470 --> 00:09:46.480 align:start position:0% any any info you can give us about what 00:09:46.480 --> 00:09:47.990 align:start position:0% any any info you can give us about what the<00:09:46.640> experience<00:09:46.959> was<00:09:47.200> like<00:09:47.360> using<00:09:47.600> it.<00:09:47.839> That's 00:09:47.990 --> 00:09:48.000 align:start position:0% the experience was like using it. That's 00:09:48.000 --> 00:09:50.389 align:start position:0% the experience was like using it. That's that's<00:09:48.080> that's<00:09:48.800> good<00:09:49.040> good<00:09:49.200> or<00:09:49.440> bad<00:09:49.760> frankly. 00:09:50.389 --> 00:09:50.399 align:start position:0% that's that's good good or bad frankly. 00:09:50.399 --> 00:09:52.630 align:start position:0% that's that's good good or bad frankly. So<00:09:50.720> send<00:09:50.880> it<00:09:51.040> our<00:09:51.200> way.<00:09:51.760> Yeah,<00:09:52.080> I<00:09:52.240> think<00:09:52.399> I 00:09:52.630 --> 00:09:52.640 align:start position:0% So send it our way. Yeah, I think I 00:09:52.640 --> 00:09:54.150 align:start position:0% So send it our way. Yeah, I think I think<00:09:52.720> it's<00:09:52.880> a<00:09:53.040> great<00:09:53.279> opportunity<00:09:53.760> just<00:09:54.000> to 00:09:54.150 --> 00:09:54.160 align:start position:0% think it's a great opportunity just to 00:09:54.160 --> 00:09:56.630 align:start position:0% think it's a great opportunity just to sort<00:09:54.320> of<00:09:54.399> showcase<00:09:54.880> the<00:09:55.360> kind<00:09:55.519> of<00:09:55.680> cooperation 00:09:56.630 --> 00:09:56.640 align:start position:0% sort of showcase the kind of cooperation 00:09:56.640 --> 00:09:58.630 align:start position:0% sort of showcase the kind of cooperation uh<00:09:56.800> that<00:09:57.040> we<00:09:57.200> can<00:09:57.279> get<00:09:57.519> not<00:09:57.680> just<00:09:57.839> between<00:09:58.560> you 00:09:58.630 --> 00:09:58.640 align:start position:0% uh that we can get not just between you 00:09:58.640 --> 00:10:00.070 align:start position:0% uh that we can get not just between you know<00:09:58.880> ourselves<00:09:59.279> and<00:09:59.440> our<00:09:59.600> members<00:09:59.760> of<00:09:59.920> the 00:10:00.070 --> 00:10:00.080 align:start position:0% know ourselves and our members of the 00:10:00.080 --> 00:10:02.070 align:start position:0% know ourselves and our members of the community<00:10:00.399> but<00:10:00.880> within<00:10:01.279> open<00:10:01.600> source<00:10:01.839> in 00:10:02.070 --> 00:10:02.080 align:start position:0% community but within open source in 00:10:02.080 --> 00:10:04.470 align:start position:0% community but within open source in general<00:10:02.720> because<00:10:03.120> again<00:10:03.440> Proxmox<00:10:04.080> being<00:10:04.240> open 00:10:04.470 --> 00:10:04.480 align:start position:0% general because again Proxmox being open 00:10:04.480 --> 00:10:06.230 align:start position:0% general because again Proxmox being open source<00:10:04.800> makes<00:10:05.040> it<00:10:05.200> really<00:10:05.440> easy<00:10:05.600> to<00:10:05.760> say<00:10:06.000> hey 00:10:06.230 --> 00:10:06.240 align:start position:0% source makes it really easy to say hey 00:10:06.240 --> 00:10:08.150 align:start position:0% source makes it really easy to say hey let's<00:10:06.480> look<00:10:06.560> at<00:10:06.800> you<00:10:06.959> know<00:10:07.440> their<00:10:07.680> API 00:10:08.150 --> 00:10:08.160 align:start position:0% let's look at you know their API 00:10:08.160 --> 00:10:10.070 align:start position:0% let's look at you know their API endpoints<00:10:08.720> let's<00:10:08.959> look<00:10:09.040> at<00:10:09.200> the<00:10:09.440> best<00:10:09.680> way<00:10:09.839> to 00:10:10.070 --> 00:10:10.080 align:start position:0% endpoints let's look at the best way to 00:10:10.080 --> 00:10:12.150 align:start position:0% endpoints let's look at the best way to work<00:10:10.160> on<00:10:10.399> these<00:10:10.959> and<00:10:11.279> just<00:10:11.519> from<00:10:11.760> somebody's 00:10:12.150 --> 00:10:12.160 align:start position:0% work on these and just from somebody's 00:10:12.160 --> 00:10:14.470 align:start position:0% work on these and just from somebody's idea<00:10:12.399> of<00:10:12.720> hey<00:10:12.959> let's<00:10:13.360> let's<00:10:13.680> consume<00:10:14.079> a<00:10:14.240> couple 00:10:14.470 --> 00:10:14.480 align:start position:0% idea of hey let's let's consume a couple 00:10:14.480 --> 00:10:16.470 align:start position:0% idea of hey let's let's consume a couple APIs<00:10:15.360> let's<00:10:15.600> understand<00:10:15.920> them<00:10:16.160> and<00:10:16.320> let's 00:10:16.470 --> 00:10:16.480 align:start position:0% APIs let's understand them and let's 00:10:16.480 --> 00:10:19.110 align:start position:0% APIs let's understand them and let's build<00:10:16.640> a<00:10:16.800> prox<00:10:17.360> or<00:10:17.600> a<00:10:17.839> plugin<00:10:18.320> to<00:10:18.560> sort<00:10:18.720> of<00:10:18.880> glue 00:10:19.110 --> 00:10:19.120 align:start position:0% build a prox or a plugin to sort of glue 00:10:19.120 --> 00:10:20.710 align:start position:0% build a prox or a plugin to sort of glue them<00:10:19.279> together<00:10:19.920> I<00:10:20.079> think<00:10:20.160> it's<00:10:20.399> a<00:10:20.560> great 00:10:20.710 --> 00:10:20.720 align:start position:0% them together I think it's a great 00:10:20.720 --> 00:10:22.470 align:start position:0% them together I think it's a great opportunity<00:10:21.200> to<00:10:21.360> say,<00:10:21.600> hey,<00:10:22.000> you<00:10:22.320> don't 00:10:22.470 --> 00:10:22.480 align:start position:0% opportunity to say, hey, you don't 00:10:22.480 --> 00:10:24.389 align:start position:0% opportunity to say, hey, you don't necessarily<00:10:23.120> need<00:10:23.279> to<00:10:23.440> be<00:10:23.600> closed<00:10:23.920> source<00:10:24.160> to 00:10:24.389 --> 00:10:24.399 align:start position:0% necessarily need to be closed source to 00:10:24.399 --> 00:10:25.910 align:start position:0% necessarily need to be closed source to have<00:10:24.640> something<00:10:24.880> that's<00:10:25.279> going<00:10:25.440> to<00:10:25.519> work<00:10:25.760> out 00:10:25.910 --> 00:10:25.920 align:start position:0% have something that's going to work out 00:10:25.920 --> 00:10:27.190 align:start position:0% have something that's going to work out really<00:10:26.240> well.<00:10:26.800> Um, 00:10:27.190 --> 00:10:27.200 align:start position:0% really well. Um, 00:10:27.200 --> 00:10:27.990 align:start position:0% really well. Um, >> yeah, 00:10:27.990 --> 00:10:28.000 align:start position:0% >> yeah, 00:10:28.000 --> 00:10:30.389 align:start position:0% >> yeah, >> I'm<00:10:28.240> excited<00:10:28.560> about<00:10:28.800> the<00:10:29.040> future<00:10:29.680> of<00:10:29.920> this<00:10:30.160> and 00:10:30.389 --> 00:10:30.399 align:start position:0% >> I'm excited about the future of this and 00:10:30.399 --> 00:10:32.710 align:start position:0% >> I'm excited about the future of this and the<00:10:30.800> collaborations<00:10:31.440> we<00:10:31.680> can<00:10:31.760> do. 00:10:32.710 --> 00:10:32.720 align:start position:0% the collaborations we can do. 00:10:32.720 --> 00:10:34.230 align:start position:0% the collaborations we can do. >> I<00:10:32.959> am<00:10:33.040> curious<00:10:33.360> to<00:10:33.519> hear<00:10:33.600> from<00:10:33.839> others<00:10:34.079> though 00:10:34.230 --> 00:10:34.240 align:start position:0% >> I am curious to hear from others though 00:10:34.240 --> 00:10:35.509 align:start position:0% >> I am curious to hear from others though if<00:10:34.399> there's<00:10:34.640> people<00:10:34.800> using<00:10:35.040> any<00:10:35.279> other 00:10:35.509 --> 00:10:35.519 align:start position:0% if there's people using any other 00:10:35.519 --> 00:10:37.110 align:start position:0% if there's people using any other virtualization<00:10:36.240> solutions<00:10:36.640> we<00:10:36.800> should<00:10:36.959> be 00:10:37.110 --> 00:10:37.120 align:start position:0% virtualization solutions we should be 00:10:37.120 --> 00:10:38.389 align:start position:0% virtualization solutions we should be paying<00:10:37.279> attention<00:10:37.600> to<00:10:37.760> as<00:10:37.920> well.<00:10:38.079> I<00:10:38.240> know 00:10:38.389 --> 00:10:38.399 align:start position:0% paying attention to as well. I know 00:10:38.399 --> 00:10:39.910 align:start position:0% paying attention to as well. I know internally<00:10:38.880> here<00:10:39.120> we<00:10:39.279> have<00:10:39.440> quite<00:10:39.519> a<00:10:39.680> bit<00:10:39.760> of 00:10:39.910 --> 00:10:39.920 align:start position:0% internally here we have quite a bit of 00:10:39.920 --> 00:10:42.710 align:start position:0% internally here we have quite a bit of XCPNG<00:10:40.959> deployed<00:10:41.360> and<00:10:41.600> we<00:10:41.760> we<00:10:42.160> play<00:10:42.320> with<00:10:42.399> that. 00:10:42.710 --> 00:10:42.720 align:start position:0% XCPNG deployed and we we play with that. 00:10:42.720 --> 00:10:44.710 align:start position:0% XCPNG deployed and we we play with that. That<00:10:42.880> works<00:10:43.120> quite<00:10:43.360> well.<00:10:44.160> We've<00:10:44.399> been<00:10:44.560> using 00:10:44.710 --> 00:10:44.720 align:start position:0% That works quite well. We've been using 00:10:44.720 --> 00:10:46.710 align:start position:0% That works quite well. We've been using that<00:10:45.040> actually<00:10:45.279> for<00:10:45.519> many<00:10:45.760> many<00:10:46.079> years<00:10:46.480> prior 00:10:46.710 --> 00:10:46.720 align:start position:0% that actually for many many years prior 00:10:46.720 --> 00:10:49.990 align:start position:0% that actually for many many years prior to<00:10:46.880> the<00:10:47.040> whole<00:10:47.200> Broadcom<00:10:47.760> fiasco<00:10:48.720> and<00:10:49.200> uh<00:10:49.600> yeah 00:10:49.990 --> 00:10:50.000 align:start position:0% to the whole Broadcom fiasco and uh yeah 00:10:50.000 --> 00:10:51.670 align:start position:0% to the whole Broadcom fiasco and uh yeah so<00:10:50.160> I<00:10:50.320> am<00:10:50.480> curious<00:10:50.720> what<00:10:50.959> other<00:10:51.120> things<00:10:51.360> people 00:10:51.670 --> 00:10:51.680 align:start position:0% so I am curious what other things people 00:10:51.680 --> 00:10:53.190 align:start position:0% so I am curious what other things people run<00:10:51.920> and<00:10:52.160> if<00:10:52.320> there's<00:10:52.560> any<00:10:52.800> additional 00:10:53.190 --> 00:10:53.200 align:start position:0% run and if there's any additional 00:10:53.200 --> 00:10:54.710 align:start position:0% run and if there's any additional integration<00:10:53.760> work<00:10:53.920> that<00:10:54.160> we<00:10:54.320> think<00:10:54.480> should 00:10:54.710 --> 00:10:54.720 align:start position:0% integration work that we think should 00:10:54.720 --> 00:10:57.509 align:start position:0% integration work that we think should happen<00:10:55.040> if<00:10:55.200> there's<00:10:55.440> interest.<00:10:55.920> So 00:10:57.509 --> 00:10:57.519 align:start position:0% happen if there's interest. So 00:10:57.519 --> 00:10:59.030 align:start position:0% happen if there's interest. So >> leave<00:10:57.680> your<00:10:57.839> comments<00:10:58.079> below 00:10:59.030 --> 00:10:59.040 align:start position:0% >> leave your comments below 00:10:59.040 --> 00:11:01.030 align:start position:0% >> leave your comments below >> an<00:10:59.360> an<00:10:59.600> open<00:10:59.760> source<00:11:00.079> company<00:11:00.480> using<00:11:00.800> open 00:11:01.030 --> 00:11:01.040 align:start position:0% >> an an open source company using open 00:11:01.040 --> 00:11:02.630 align:start position:0% >> an an open source company using open source<00:11:01.360> software<00:11:01.680> internally.<00:11:02.240> Well,<00:11:02.399> I 00:11:02.630 --> 00:11:02.640 align:start position:0% source software internally. Well, I 00:11:02.640 --> 00:11:03.670 align:start position:0% source software internally. Well, I never<00:11:02.959> Chris. 00:11:03.670 --> 00:11:03.680 align:start position:0% never Chris. 00:11:03.680 --> 00:11:06.069 align:start position:0% never Chris. >> Kind<00:11:03.920> of<00:11:04.079> weird,<00:11:04.480> right?<00:11:04.720> I<00:11:04.959> know.<00:11:05.519> Strange, 00:11:06.069 --> 00:11:06.079 align:start position:0% >> Kind of weird, right? I know. Strange, 00:11:06.079 --> 00:11:07.829 align:start position:0% >> Kind of weird, right? I know. Strange, but<00:11:06.320> yeah,<00:11:06.560> you'd<00:11:06.800> be<00:11:06.959> surprised.<00:11:07.279> We<00:11:07.519> use<00:11:07.680> a 00:11:07.829 --> 00:11:07.839 align:start position:0% but yeah, you'd be surprised. We use a 00:11:07.839 --> 00:11:09.430 align:start position:0% but yeah, you'd be surprised. We use a lot<00:11:07.920> of<00:11:08.000> things<00:11:08.240> open<00:11:08.560> source<00:11:08.800> internally. 00:11:09.430 --> 00:11:09.440 align:start position:0% lot of things open source internally. 00:11:09.440 --> 00:11:11.430 align:start position:0% lot of things open source internally. So, 00:11:11.430 --> 00:11:11.440 align:start position:0% So, 00:11:11.440 --> 00:11:13.190 align:start position:0% So, >> let's<00:11:12.000> have<00:11:12.079> a<00:11:12.240> little<00:11:12.320> bit<00:11:12.480> of<00:11:12.560> a<00:11:12.720> chat<00:11:12.959> here, 00:11:13.190 --> 00:11:13.200 align:start position:0% >> let's have a little bit of a chat here, 00:11:13.200 --> 00:11:14.949 align:start position:0% >> let's have a little bit of a chat here, though.<00:11:13.440> Uh,<00:11:13.760> we've<00:11:14.000> got<00:11:14.160> some<00:11:14.560> uh<00:11:14.720> there's 00:11:14.949 --> 00:11:14.959 align:start position:0% though. Uh, we've got some uh there's 00:11:14.959 --> 00:11:16.790 align:start position:0% though. Uh, we've got some uh there's been<00:11:15.120> a<00:11:15.360> lot<00:11:15.440> of<00:11:15.600> app<00:11:15.920> updates,<00:11:16.320> I<00:11:16.560> think,<00:11:16.640> that 00:11:16.790 --> 00:11:16.800 align:start position:0% been a lot of app updates, I think, that 00:11:16.800 --> 00:11:18.470 align:start position:0% been a lot of app updates, I think, that are<00:11:16.959> staged<00:11:17.279> up<00:11:17.519> recently,<00:11:17.839> and<00:11:18.079> people<00:11:18.320> might 00:11:18.470 --> 00:11:18.480 align:start position:0% are staged up recently, and people might 00:11:18.480 --> 00:11:19.829 align:start position:0% are staged up recently, and people might be<00:11:18.640> wondering,<00:11:19.040> you<00:11:19.120> know,<00:11:19.279> hey,<00:11:19.600> everything 00:11:19.829 --> 00:11:19.839 align:start position:0% be wondering, you know, hey, everything 00:11:19.839 --> 00:11:22.470 align:start position:0% be wondering, you know, hey, everything seems<00:11:20.079> to<00:11:20.240> have<00:11:20.399> updated<00:11:20.800> itself<00:11:21.279> again.<00:11:21.920> Um, 00:11:22.470 --> 00:11:22.480 align:start position:0% seems to have updated itself again. Um, 00:11:22.480 --> 00:11:24.230 align:start position:0% seems to have updated itself again. Um, what's<00:11:22.880> going<00:11:22.959> on,<00:11:23.200> and<00:11:23.440> what's<00:11:23.680> this<00:11:23.920> big 00:11:24.230 --> 00:11:24.240 align:start position:0% what's going on, and what's this big 00:11:24.240 --> 00:11:26.150 align:start position:0% what's going on, and what's this big change<00:11:24.560> that's<00:11:24.880> happened?<00:11:25.519> Why<00:11:25.760> did<00:11:25.839> all<00:11:26.000> of 00:11:26.150 --> 00:11:26.160 align:start position:0% change that's happened? Why did all of 00:11:26.160 --> 00:11:28.550 align:start position:0% change that's happened? Why did all of my<00:11:26.320> apps<00:11:26.560> suddenly<00:11:27.600> uh,<00:11:27.839> you<00:11:28.000> know,<00:11:28.240> say<00:11:28.399> that 00:11:28.550 --> 00:11:28.560 align:start position:0% my apps suddenly uh, you know, say that 00:11:28.560 --> 00:11:30.230 align:start position:0% my apps suddenly uh, you know, say that there<00:11:28.800> was<00:11:28.880> an<00:11:29.040> update,<00:11:29.360> but<00:11:29.760> maybe<00:11:30.000> there 00:11:30.230 --> 00:11:30.240 align:start position:0% there was an update, but maybe there 00:11:30.240 --> 00:11:31.829 align:start position:0% there was an update, but maybe there didn't<00:11:30.399> seem<00:11:30.640> to<00:11:30.800> have<00:11:30.959> been<00:11:31.120> there?<00:11:31.519> So<00:11:31.680> we've 00:11:31.829 --> 00:11:31.839 align:start position:0% didn't seem to have been there? So we've 00:11:31.839 --> 00:11:34.790 align:start position:0% didn't seem to have been there? So we've done<00:11:32.720> we've<00:11:33.040> done<00:11:33.200> some<00:11:33.360> catalog<00:11:33.839> updates.<00:11:34.320> So 00:11:34.790 --> 00:11:34.800 align:start position:0% done we've done some catalog updates. So 00:11:34.800 --> 00:11:37.110 align:start position:0% done we've done some catalog updates. So what<00:11:35.040> what<00:11:35.279> did<00:11:35.440> we<00:11:35.600> do<00:11:35.680> for<00:11:35.920> this<00:11:36.160> big<00:11:36.640> uh<00:11:36.880> this 00:11:37.110 --> 00:11:37.120 align:start position:0% what what did we do for this big uh this 00:11:37.120 --> 00:11:38.310 align:start position:0% what what did we do for this big uh this big<00:11:37.360> push<00:11:37.600> here<00:11:37.920> Chris? 00:11:38.310 --> 00:11:38.320 align:start position:0% big push here Chris? 00:11:38.320 --> 00:11:39.750 align:start position:0% big push here Chris? >> So<00:11:38.480> these<00:11:38.640> are<00:11:38.800> real<00:11:39.040> infrastructure 00:11:39.750 --> 00:11:39.760 align:start position:0% >> So these are real infrastructure 00:11:39.760 --> 00:11:41.590 align:start position:0% >> So these are real infrastructure updates.<00:11:40.240> So<00:11:40.399> if<00:11:40.720> we<00:11:40.959> if<00:11:41.120> you've<00:11:41.279> been<00:11:41.360> a 00:11:41.590 --> 00:11:41.600 align:start position:0% updates. So if we if you've been a 00:11:41.600 --> 00:11:43.430 align:start position:0% updates. So if we if you've been a longtime<00:11:42.000> listener<00:11:42.399> here<00:11:42.720> you<00:11:42.959> may<00:11:43.120> recall 00:11:43.430 --> 00:11:43.440 align:start position:0% longtime listener here you may recall 00:11:43.440 --> 00:11:45.110 align:start position:0% longtime listener here you may recall when<00:11:43.680> we've<00:11:43.920> talked<00:11:44.240> some<00:11:44.480> of<00:11:44.560> the<00:11:44.720> early<00:11:44.880> days 00:11:45.110 --> 00:11:45.120 align:start position:0% when we've talked some of the early days 00:11:45.120 --> 00:11:47.030 align:start position:0% when we've talked some of the early days about<00:11:45.360> the<00:11:45.600> transition<00:11:46.000> from<00:11:46.240> Kubernetes<00:11:46.800> to 00:11:47.030 --> 00:11:47.040 align:start position:0% about the transition from Kubernetes to 00:11:47.040 --> 00:11:48.550 align:start position:0% about the transition from Kubernetes to Docker.<00:11:47.360> And<00:11:47.519> at<00:11:47.680> the<00:11:47.839> time<00:11:48.000> I<00:11:48.240> said<00:11:48.399> it 00:11:48.550 --> 00:11:48.560 align:start position:0% Docker. And at the time I said it 00:11:48.560 --> 00:11:51.190 align:start position:0% Docker. And at the time I said it multiple<00:11:48.959> places<00:11:49.440> multiple<00:11:49.839> times<00:11:50.240> about<00:11:50.880> hey 00:11:51.190 --> 00:11:51.200 align:start position:0% multiple places multiple times about hey 00:11:51.200 --> 00:11:52.470 align:start position:0% multiple places multiple times about hey this<00:11:51.360> is<00:11:51.440> just<00:11:51.600> the<00:11:51.839> beginning.<00:11:52.240> There's 00:11:52.470 --> 00:11:52.480 align:start position:0% this is just the beginning. There's 00:11:52.480 --> 00:11:54.470 align:start position:0% this is just the beginning. There's going<00:11:52.560> to<00:11:52.640> be<00:11:52.959> as<00:11:53.279> time<00:11:53.519> goes<00:11:53.760> on<00:11:54.079> more<00:11:54.320> things 00:11:54.470 --> 00:11:54.480 align:start position:0% going to be as time goes on more things 00:11:54.480 --> 00:11:56.630 align:start position:0% going to be as time goes on more things that<00:11:54.720> evolve<00:11:55.040> in<00:11:55.200> the<00:11:55.360> app<00:11:55.600> ecosystem<00:11:56.399> more 00:11:56.630 --> 00:11:56.640 align:start position:0% that evolve in the app ecosystem more 00:11:56.640 --> 00:11:58.870 align:start position:0% that evolve in the app ecosystem more Docker<00:11:57.040> functionality<00:11:57.680> added.<00:11:58.079> Well,<00:11:58.720> this 00:11:58.870 --> 00:11:58.880 align:start position:0% Docker functionality added. Well, this 00:11:58.880 --> 00:12:00.870 align:start position:0% Docker functionality added. Well, this is<00:11:59.040> the<00:11:59.279> opening<00:11:59.680> salvo<00:12:00.240> and<00:12:00.399> some<00:12:00.560> of<00:12:00.640> those 00:12:00.870 --> 00:12:00.880 align:start position:0% is the opening salvo and some of those 00:12:00.880 --> 00:12:03.110 align:start position:0% is the opening salvo and some of those next<00:12:01.120> steps<00:12:01.519> going<00:12:01.760> forward.<00:12:02.560> So,<00:12:02.720> we'll<00:12:02.959> link 00:12:03.110 --> 00:12:03.120 align:start position:0% next steps going forward. So, we'll link 00:12:03.120 --> 00:12:04.630 align:start position:0% next steps going forward. So, we'll link to<00:12:03.279> it<00:12:03.440> here.<00:12:03.680> You're<00:12:03.920> welcome<00:12:04.079> to<00:12:04.240> go<00:12:04.399> look. 00:12:04.630 --> 00:12:04.640 align:start position:0% to it here. You're welcome to go look. 00:12:04.640 --> 00:12:06.310 align:start position:0% to it here. You're welcome to go look. Again,<00:12:04.880> if<00:12:05.040> you're<00:12:05.200> nosy<00:12:05.519> on<00:12:05.760> GitHub,<00:12:06.160> maybe 00:12:06.310 --> 00:12:06.320 align:start position:0% Again, if you're nosy on GitHub, maybe 00:12:06.320 --> 00:12:08.069 align:start position:0% Again, if you're nosy on GitHub, maybe you've<00:12:06.560> already<00:12:06.720> seen<00:12:06.959> this,<00:12:07.600> but<00:12:07.839> we've 00:12:08.069 --> 00:12:08.079 align:start position:0% you've already seen this, but we've 00:12:08.079 --> 00:12:09.990 align:start position:0% you've already seen this, but we've started<00:12:08.399> landing<00:12:08.800> some<00:12:09.040> networking<00:12:09.519> updates 00:12:09.990 --> 00:12:10.000 align:start position:0% started landing some networking updates 00:12:10.000 --> 00:12:12.470 align:start position:0% started landing some networking updates to<00:12:10.240> the<00:12:10.399> apps<00:12:10.880> infrastructure.<00:12:12.079> Well,<00:12:12.320> what 00:12:12.470 --> 00:12:12.480 align:start position:0% to the apps infrastructure. Well, what 00:12:12.480 --> 00:12:13.990 align:start position:0% to the apps infrastructure. Well, what does<00:12:12.560> a<00:12:12.720> networking<00:12:13.040> update<00:12:13.440> mean?<00:12:13.760> Well, 00:12:13.990 --> 00:12:14.000 align:start position:0% does a networking update mean? Well, 00:12:14.000 --> 00:12:15.990 align:start position:0% does a networking update mean? Well, what<00:12:14.160> it<00:12:14.320> means<00:12:14.560> is<00:12:14.880> really<00:12:15.200> this<00:12:15.519> first<00:12:15.760> step 00:12:15.990 --> 00:12:16.000 align:start position:0% what it means is really this first step 00:12:16.000 --> 00:12:18.150 align:start position:0% what it means is really this first step is<00:12:16.240> we're<00:12:16.480> adding<00:12:16.800> awareness<00:12:17.360> to<00:12:17.600> our<00:12:17.760> apps 00:12:18.150 --> 00:12:18.160 align:start position:0% is we're adding awareness to our apps 00:12:18.160 --> 00:12:20.069 align:start position:0% is we're adding awareness to our apps catalog<00:12:18.639> about<00:12:19.040> Docker<00:12:19.600> internal 00:12:20.069 --> 00:12:20.079 align:start position:0% catalog about Docker internal 00:12:20.079 --> 00:12:22.790 align:start position:0% catalog about Docker internal networking.<00:12:21.200> So<00:12:21.440> what<00:12:21.680> that<00:12:21.920> means<00:12:22.160> is<00:12:22.240> is<00:12:22.560> if 00:12:22.790 --> 00:12:22.800 align:start position:0% networking. So what that means is is if 00:12:22.800 --> 00:12:24.710 align:start position:0% networking. So what that means is is if you<00:12:22.880> have<00:12:23.040> Docker<00:12:23.519> networks<00:12:24.000> created,<00:12:24.480> say 00:12:24.710 --> 00:12:24.720 align:start position:0% you have Docker networks created, say 00:12:24.720 --> 00:12:26.949 align:start position:0% you have Docker networks created, say you've<00:12:24.959> already<00:12:25.120> made<00:12:25.360> them<00:12:25.519> via<00:12:25.760> the<00:12:25.920> CLI, 00:12:26.949 --> 00:12:26.959 align:start position:0% you've already made them via the CLI, 00:12:26.959 --> 00:12:28.870 align:start position:0% you've already made them via the CLI, you<00:12:27.120> use<00:12:27.360> other<00:12:27.600> tools<00:12:27.920> like<00:12:28.160> Dockage<00:12:28.800> for 00:12:28.870 --> 00:12:28.880 align:start position:0% you use other tools like Dockage for 00:12:28.880 --> 00:12:31.509 align:start position:0% you use other tools like Dockage for example,<00:12:29.760> you<00:12:30.000> can<00:12:30.160> now<00:12:30.399> deploy<00:12:30.720> your<00:12:30.959> Trunaz 00:12:31.509 --> 00:12:31.519 align:start position:0% example, you can now deploy your Trunaz 00:12:31.519 --> 00:12:33.590 align:start position:0% example, you can now deploy your Trunaz apps<00:12:31.760> from<00:12:32.000> our<00:12:32.240> catalog<00:12:32.720> and<00:12:33.040> select<00:12:33.360> which 00:12:33.590 --> 00:12:33.600 align:start position:0% apps from our catalog and select which 00:12:33.600 --> 00:12:35.670 align:start position:0% apps from our catalog and select which of<00:12:33.760> those<00:12:34.000> networks<00:12:34.320> to<00:12:34.560> bind<00:12:34.880> to,<00:12:35.200> which<00:12:35.440> is 00:12:35.670 --> 00:12:35.680 align:start position:0% of those networks to bind to, which is 00:12:35.680 --> 00:12:37.430 align:start position:0% of those networks to bind to, which is very<00:12:35.920> useful<00:12:36.240> for<00:12:36.560> kind<00:12:36.720> of<00:12:36.880> more<00:12:37.040> advanced 00:12:37.430 --> 00:12:37.440 align:start position:0% very useful for kind of more advanced 00:12:37.440 --> 00:12:39.030 align:start position:0% very useful for kind of more advanced setups<00:12:37.920> if<00:12:38.079> you<00:12:38.240> want<00:12:38.320> to<00:12:38.399> restrict<00:12:38.720> certain 00:12:39.030 --> 00:12:39.040 align:start position:0% setups if you want to restrict certain 00:12:39.040 --> 00:12:40.949 align:start position:0% setups if you want to restrict certain apps<00:12:39.279> to<00:12:39.519> talking<00:12:39.760> to<00:12:40.160> certain<00:12:40.480> other<00:12:40.639> apps, 00:12:40.949 --> 00:12:40.959 align:start position:0% apps to talking to certain other apps, 00:12:40.959 --> 00:12:43.030 align:start position:0% apps to talking to certain other apps, put<00:12:41.120> them<00:12:41.200> on<00:12:41.360> their<00:12:41.519> own<00:12:41.680> private<00:12:42.000> networks, 00:12:43.030 --> 00:12:43.040 align:start position:0% put them on their own private networks, 00:12:43.040 --> 00:12:45.269 align:start position:0% put them on their own private networks, all<00:12:43.200> that<00:12:43.360> good<00:12:43.600> stuff.<00:12:43.920> Now,<00:12:44.720> this<00:12:44.959> doesn't 00:12:45.269 --> 00:12:45.279 align:start position:0% all that good stuff. Now, this doesn't 00:12:45.279 --> 00:12:47.430 align:start position:0% all that good stuff. Now, this doesn't happen<00:12:45.600> easily<00:12:46.000> or<00:12:46.240> overnight<00:12:46.720> or<00:12:46.959> for<00:12:47.200> free. 00:12:47.430 --> 00:12:47.440 align:start position:0% happen easily or overnight or for free. 00:12:47.440 --> 00:12:49.110 align:start position:0% happen easily or overnight or for free. These<00:12:47.680> are<00:12:47.839> complicated<00:12:48.320> things<00:12:48.480> to<00:12:48.720> go<00:12:48.880> get 00:12:49.110 --> 00:12:49.120 align:start position:0% These are complicated things to go get 00:12:49.120 --> 00:12:51.509 align:start position:0% These are complicated things to go get in<00:12:49.360> a<00:12:49.600> nice<00:12:49.920> apps<00:12:50.320> catalog<00:12:50.880> infrastructure. 00:12:51.509 --> 00:12:51.519 align:start position:0% in a nice apps catalog infrastructure. 00:12:51.519 --> 00:12:52.870 align:start position:0% in a nice apps catalog infrastructure. So<00:12:51.680> hence<00:12:52.000> you're<00:12:52.240> seeing<00:12:52.399> some<00:12:52.560> of<00:12:52.639> this 00:12:52.870 --> 00:12:52.880 align:start position:0% So hence you're seeing some of this 00:12:52.880 --> 00:12:54.389 align:start position:0% So hence you're seeing some of this backend<00:12:53.279> churn<00:12:53.600> as<00:12:53.760> we're<00:12:54.000> making<00:12:54.160> the 00:12:54.389 --> 00:12:54.399 align:start position:0% backend churn as we're making the 00:12:54.399 --> 00:12:56.389 align:start position:0% backend churn as we're making the changes<00:12:54.880> and<00:12:55.120> it's<00:12:55.360> not<00:12:55.519> all<00:12:55.760> apps<00:12:56.000> yet.<00:12:56.320> If 00:12:56.389 --> 00:12:56.399 align:start position:0% changes and it's not all apps yet. If 00:12:56.399 --> 00:12:57.590 align:start position:0% changes and it's not all apps yet. If you<00:12:56.480> look<00:12:56.560> at<00:12:56.639> the<00:12:56.800> pull<00:12:57.040> request,<00:12:57.279> you'll<00:12:57.519> see 00:12:57.590 --> 00:12:57.600 align:start position:0% you look at the pull request, you'll see 00:12:57.600 --> 00:12:59.110 align:start position:0% you look at the pull request, you'll see we're<00:12:57.839> doing<00:12:57.920> them<00:12:58.160> in<00:12:58.399> stages<00:12:58.720> where<00:12:58.959> it's 00:12:59.110 --> 00:12:59.120 align:start position:0% we're doing them in stages where it's 00:12:59.120 --> 00:13:00.949 align:start position:0% we're doing them in stages where it's like<00:12:59.200> we<00:12:59.440> do<00:12:59.519> a<00:12:59.760> a<00:13:00.000> dozen<00:13:00.320> here,<00:13:00.560> a<00:13:00.639> dozen 00:13:00.949 --> 00:13:00.959 align:start position:0% like we do a a dozen here, a dozen 00:13:00.959 --> 00:13:02.150 align:start position:0% like we do a a dozen here, a dozen there,<00:13:01.120> and<00:13:01.360> we're<00:13:01.519> kind<00:13:01.600> of<00:13:01.760> working<00:13:02.000> through 00:13:02.150 --> 00:13:02.160 align:start position:0% there, and we're kind of working through 00:13:02.160 --> 00:13:03.590 align:start position:0% there, and we're kind of working through the<00:13:02.320> catalog<00:13:02.720> because<00:13:02.880> we<00:13:03.040> got<00:13:03.200> quite<00:13:03.360> a<00:13:03.519> few 00:13:03.590 --> 00:13:03.600 align:start position:0% the catalog because we got quite a few 00:13:03.600 --> 00:13:05.110 align:start position:0% the catalog because we got quite a few apps<00:13:03.839> these<00:13:04.079> days.<00:13:04.320> It<00:13:04.480> takes<00:13:04.720> time<00:13:04.800> to<00:13:04.959> get 00:13:05.110 --> 00:13:05.120 align:start position:0% apps these days. It takes time to get 00:13:05.120 --> 00:13:07.350 align:start position:0% apps these days. It takes time to get them<00:13:05.279> all<00:13:05.440> done.<00:13:06.240> But<00:13:06.399> the<00:13:06.639> goal<00:13:06.800> is<00:13:07.040> at<00:13:07.200> the 00:13:07.350 --> 00:13:07.360 align:start position:0% them all done. But the goal is at the 00:13:07.360 --> 00:13:09.670 align:start position:0% them all done. But the goal is at the end<00:13:07.440> of<00:13:07.519> the<00:13:07.760> day,<00:13:08.320> we'll<00:13:08.639> have<00:13:08.800> all<00:13:09.040> the<00:13:09.279> apps 00:13:09.670 --> 00:13:09.680 align:start position:0% end of the day, we'll have all the apps 00:13:09.680 --> 00:13:12.069 align:start position:0% end of the day, we'll have all the apps and<00:13:09.920> the<00:13:10.160> catalog<00:13:10.800> primed<00:13:11.519> for<00:13:11.839> this 00:13:12.069 --> 00:13:12.079 align:start position:0% and the catalog primed for this 00:13:12.079 --> 00:13:14.389 align:start position:0% and the catalog primed for this functionality.<00:13:12.959> So<00:13:13.600> of<00:13:13.760> course,<00:13:14.000> what's<00:13:14.240> the 00:13:14.389 --> 00:13:14.399 align:start position:0% functionality. So of course, what's the 00:13:14.399 --> 00:13:15.829 align:start position:0% functionality. So of course, what's the next<00:13:14.560> thing<00:13:14.720> you<00:13:14.959> ask?<00:13:15.200> I<00:13:15.440> can<00:13:15.519> already<00:13:15.680> hear 00:13:15.829 --> 00:13:15.839 align:start position:0% next thing you ask? I can already hear 00:13:15.839 --> 00:13:17.030 align:start position:0% next thing you ask? I can already hear you<00:13:16.000> saying,<00:13:16.160> "Yeah,<00:13:16.399> but<00:13:16.560> how<00:13:16.639> do<00:13:16.800> I<00:13:16.880> make 00:13:17.030 --> 00:13:17.040 align:start position:0% you saying, "Yeah, but how do I make 00:13:17.040 --> 00:13:18.389 align:start position:0% you saying, "Yeah, but how do I make these?<00:13:17.360> I<00:13:17.519> don't<00:13:17.600> want<00:13:17.680> to<00:13:17.760> go<00:13:17.920> do<00:13:18.079> it<00:13:18.160> at<00:13:18.320> the 00:13:18.389 --> 00:13:18.399 align:start position:0% these? I don't want to go do it at the 00:13:18.399 --> 00:13:20.710 align:start position:0% these? I don't want to go do it at the CLI<00:13:18.800> or<00:13:18.959> use<00:13:19.120> Dockage."<00:13:20.079> Totally<00:13:20.480> makes 00:13:20.710 --> 00:13:20.720 align:start position:0% CLI or use Dockage." Totally makes 00:13:20.720 --> 00:13:22.550 align:start position:0% CLI or use Dockage." Totally makes sense.<00:13:21.040> I<00:13:21.200> want<00:13:21.360> to<00:13:21.440> do<00:13:21.519> it<00:13:21.680> natively<00:13:22.160> myself. 00:13:22.550 --> 00:13:22.560 align:start position:0% sense. I want to do it natively myself. 00:13:22.560 --> 00:13:24.470 align:start position:0% sense. I want to do it natively myself. So,<00:13:22.800> we<00:13:22.959> also<00:13:23.200> have<00:13:23.279> a<00:13:23.519> ticket<00:13:23.839> in<00:13:24.079> progress 00:13:24.470 --> 00:13:24.480 align:start position:0% So, we also have a ticket in progress 00:13:24.480 --> 00:13:26.550 align:start position:0% So, we also have a ticket in progress for<00:13:24.639> that<00:13:24.800> as<00:13:25.040> well.<00:13:25.600> I'm<00:13:25.839> not<00:13:26.000> expecting<00:13:26.399> this 00:13:26.550 --> 00:13:26.560 align:start position:0% for that as well. I'm not expecting this 00:13:26.560 --> 00:13:28.470 align:start position:0% for that as well. I'm not expecting this to<00:13:26.720> land<00:13:26.880> in<00:13:27.120> 26.<00:13:27.680> This<00:13:27.839> is<00:13:28.000> more<00:13:28.240> likely 00:13:28.470 --> 00:13:28.480 align:start position:0% to land in 26. This is more likely 00:13:28.480 --> 00:13:31.190 align:start position:0% to land in 26. This is more likely looking<00:13:28.720> like<00:13:28.880> a<00:13:29.120> 27<00:13:29.680> thing,<00:13:30.560> but<00:13:30.800> the<00:13:30.959> goal 00:13:31.190 --> 00:13:31.200 align:start position:0% looking like a 27 thing, but the goal 00:13:31.200 --> 00:13:33.509 align:start position:0% looking like a 27 thing, but the goal will<00:13:31.440> be<00:13:31.760> that<00:13:32.000> we<00:13:32.320> have<00:13:32.480> full<00:13:32.800> Docker<00:13:33.200> network 00:13:33.509 --> 00:13:33.519 align:start position:0% will be that we have full Docker network 00:13:33.519 --> 00:13:35.829 align:start position:0% will be that we have full Docker network CRUD<00:13:33.839> through<00:13:34.000> the<00:13:34.160> UI<00:13:34.560> as<00:13:34.720> well.<00:13:35.360> So,<00:13:35.600> you 00:13:35.829 --> 00:13:35.839 align:start position:0% CRUD through the UI as well. So, you 00:13:35.839 --> 00:13:37.829 align:start position:0% CRUD through the UI as well. So, you don't<00:13:35.920> need<00:13:36.079> to<00:13:36.160> go<00:13:36.399> use<00:13:36.480> the<00:13:36.639> CLI<00:13:37.200> and<00:13:37.279> dockage 00:13:37.829 --> 00:13:37.839 align:start position:0% don't need to go use the CLI and dockage 00:13:37.839 --> 00:13:40.150 align:start position:0% don't need to go use the CLI and dockage down<00:13:38.000> the<00:13:38.160> road.<00:13:38.800> Again,<00:13:39.360> crawl<00:13:39.680> walker<00:13:39.920> run 00:13:40.150 --> 00:13:40.160 align:start position:0% down the road. Again, crawl walker run 00:13:40.160 --> 00:13:41.670 align:start position:0% down the road. Again, crawl walker run here<00:13:40.320> and<00:13:40.480> it'll<00:13:40.800> keep<00:13:40.959> getting<00:13:41.440> more 00:13:41.670 --> 00:13:41.680 align:start position:0% here and it'll keep getting more 00:13:41.680 --> 00:13:43.829 align:start position:0% here and it'll keep getting more involved<00:13:42.079> and<00:13:42.240> better<00:13:42.480> as<00:13:42.720> time<00:13:42.880> goes<00:13:43.040> on.<00:13:43.600> you 00:13:43.829 --> 00:13:43.839 align:start position:0% involved and better as time goes on. you 00:13:43.839 --> 00:13:45.750 align:start position:0% involved and better as time goes on. you will<00:13:44.000> be<00:13:44.160> able<00:13:44.240> to<00:13:44.320> go<00:13:44.480> into<00:13:44.639> the<00:13:44.720> tr<00:13:45.200> apps<00:13:45.440> UI 00:13:45.750 --> 00:13:45.760 align:start position:0% will be able to go into the tr apps UI 00:13:45.760 --> 00:13:47.030 align:start position:0% will be able to go into the tr apps UI and<00:13:45.920> say<00:13:46.079> great<00:13:46.399> I'd<00:13:46.560> like<00:13:46.639> to<00:13:46.800> create<00:13:46.880> a 00:13:47.030 --> 00:13:47.040 align:start position:0% and say great I'd like to create a 00:13:47.040 --> 00:13:48.629 align:start position:0% and say great I'd like to create a docker<00:13:47.440> network<00:13:47.760> I'd<00:13:47.920> like<00:13:48.000> to<00:13:48.160> manage<00:13:48.399> it 00:13:48.629 --> 00:13:48.639 align:start position:0% docker network I'd like to manage it 00:13:48.639 --> 00:13:50.310 align:start position:0% docker network I'd like to manage it let's<00:13:48.880> pin<00:13:49.120> these<00:13:49.279> apps<00:13:49.519> to<00:13:49.680> these<00:13:49.920> networks 00:13:50.310 --> 00:13:50.320 align:start position:0% let's pin these apps to these networks 00:13:50.320 --> 00:13:51.829 align:start position:0% let's pin these apps to these networks let's<00:13:50.560> remove<00:13:50.880> from<00:13:51.040> these<00:13:51.200> networks<00:13:51.600> let's 00:13:51.829 --> 00:13:51.839 align:start position:0% let's remove from these networks let's 00:13:51.839 --> 00:13:54.310 align:start position:0% let's remove from these networks let's create<00:13:52.720> you<00:13:52.800> know<00:13:53.040> let's<00:13:53.279> attach<00:13:53.680> that<00:13:53.920> tail 00:13:54.310 --> 00:13:54.320 align:start position:0% create you know let's attach that tail 00:13:54.320 --> 00:13:56.069 align:start position:0% create you know let's attach that tail scale<00:13:54.639> to<00:13:54.800> this<00:13:55.040> network<00:13:55.360> and<00:13:55.600> route<00:13:55.839> things 00:13:56.069 --> 00:13:56.079 align:start position:0% scale to this network and route things 00:13:56.079 --> 00:13:57.910 align:start position:0% scale to this network and route things through<00:13:56.240> that<00:13:56.800> you'll<00:13:57.120> be<00:13:57.199> able<00:13:57.360> to<00:13:57.440> do<00:13:57.600> a<00:13:57.760> lot 00:13:57.910 --> 00:13:57.920 align:start position:0% through that you'll be able to do a lot 00:13:57.920 --> 00:14:01.269 align:start position:0% through that you'll be able to do a lot more<00:13:58.320> interesting<00:13:59.120> isolation<00:14:00.560> with<00:14:00.800> the<00:14:00.959> apps 00:14:01.269 --> 00:14:01.279 align:start position:0% more interesting isolation with the apps 00:14:01.279 --> 00:14:02.870 align:start position:0% more interesting isolation with the apps catalog<00:14:01.680> which<00:14:01.839> is<00:14:02.000> cool<00:14:02.160> and<00:14:02.320> again<00:14:02.560> a<00:14:02.720> bunch 00:14:02.870 --> 00:14:02.880 align:start position:0% catalog which is cool and again a bunch 00:14:02.880 --> 00:14:04.230 align:start position:0% catalog which is cool and again a bunch of<00:14:02.959> you<00:14:03.120> have<00:14:03.279> already<00:14:03.440> found<00:14:03.680> workarounds 00:14:04.230 --> 00:14:04.240 align:start position:0% of you have already found workarounds 00:14:04.240 --> 00:14:06.470 align:start position:0% of you have already found workarounds and<00:14:04.560> people<00:14:04.720> are<00:14:04.959> doing<00:14:05.120> this<00:14:05.600> a<00:14:05.920> myriad<00:14:06.320> of 00:14:06.470 --> 00:14:06.480 align:start position:0% and people are doing this a myriad of 00:14:06.480 --> 00:14:07.910 align:start position:0% and people are doing this a myriad of different<00:14:06.639> ways<00:14:06.959> but<00:14:07.199> we're<00:14:07.360> trying<00:14:07.519> to<00:14:07.680> bring 00:14:07.910 --> 00:14:07.920 align:start position:0% different ways but we're trying to bring 00:14:07.920 --> 00:14:10.949 align:start position:0% different ways but we're trying to bring at<00:14:08.000> least<00:14:08.320> a<00:14:08.720> uh<00:14:09.120> a<00:14:09.440> stable<00:14:09.920> sane<00:14:10.240> framework<00:14:10.720> to 00:14:10.949 --> 00:14:10.959 align:start position:0% at least a uh a stable sane framework to 00:14:10.959 --> 00:14:13.590 align:start position:0% at least a uh a stable sane framework to do<00:14:11.120> this<00:14:11.279> a<00:14:11.600> little<00:14:11.680> bit<00:14:11.839> more<00:14:12.320> uh<00:14:12.880> structured 00:14:13.590 --> 00:14:13.600 align:start position:0% do this a little bit more uh structured 00:14:13.600 --> 00:14:15.829 align:start position:0% do this a little bit more uh structured in<00:14:13.839> our<00:14:14.000> apps<00:14:14.320> catalog<00:14:14.720> going<00:14:15.040> forward.<00:14:15.360> So 00:14:15.829 --> 00:14:15.839 align:start position:0% in our apps catalog going forward. So 00:14:15.839 --> 00:14:17.670 align:start position:0% in our apps catalog going forward. So again,<00:14:16.320> good<00:14:16.560> news.<00:14:16.880> It's<00:14:17.120> something<00:14:17.440> people 00:14:17.670 --> 00:14:17.680 align:start position:0% again, good news. It's something people 00:14:17.680 --> 00:14:19.430 align:start position:0% again, good news. It's something people have<00:14:17.839> asked<00:14:18.079> for<00:14:18.320> since<00:14:18.560> the<00:14:18.720> early<00:14:18.959> days<00:14:19.199> and 00:14:19.430 --> 00:14:19.440 align:start position:0% have asked for since the early days and 00:14:19.440 --> 00:14:20.710 align:start position:0% have asked for since the early days and it's<00:14:19.600> nice<00:14:19.760> to<00:14:19.920> be<00:14:19.920> able<00:14:20.079> to<00:14:20.160> report<00:14:20.480> we're 00:14:20.710 --> 00:14:20.720 align:start position:0% it's nice to be able to report we're 00:14:20.720 --> 00:14:22.870 align:start position:0% it's nice to be able to report we're seeing<00:14:20.880> some<00:14:21.040> progress<00:14:21.360> on<00:14:21.519> that<00:14:21.760> now.<00:14:22.000> And 00:14:22.870 --> 00:14:22.880 align:start position:0% seeing some progress on that now. And 00:14:22.880 --> 00:14:24.629 align:start position:0% seeing some progress on that now. And more<00:14:23.120> to<00:14:23.360> come.<00:14:23.680> Keep<00:14:23.839> an<00:14:24.000> eye<00:14:24.160> on<00:14:24.240> it.<00:14:24.480> There's 00:14:24.629 --> 00:14:24.639 align:start position:0% more to come. Keep an eye on it. There's 00:14:24.639 --> 00:14:25.670 align:start position:0% more to come. Keep an eye on it. There's going to<00:14:24.800> be<00:14:24.880> some<00:14:24.959> churn<00:14:25.199> in<00:14:25.360> the<00:14:25.440> app 00:14:25.670 --> 00:14:25.680 align:start position:0% going to be some churn in the app 00:14:25.680 --> 00:14:27.189 align:start position:0% going to be some churn in the app catalog<00:14:26.079> for<00:14:26.240> at<00:14:26.240> least<00:14:26.480> a<00:14:26.639> little<00:14:26.800> while<00:14:26.959> as 00:14:27.189 --> 00:14:27.199 align:start position:0% catalog for at least a little while as 00:14:27.199 --> 00:14:28.870 align:start position:0% catalog for at least a little while as we<00:14:27.360> make<00:14:27.440> these<00:14:27.680> changes. 00:14:28.870 --> 00:14:28.880 align:start position:0% we make these changes. 00:14:28.880 --> 00:14:30.389 align:start position:0% we make these changes. >> Yeah.<00:14:29.120> And<00:14:29.360> I<00:14:29.519> know<00:14:29.600> we've<00:14:29.839> tried<00:14:30.079> I<00:14:30.320> think 00:14:30.389 --> 00:14:30.399 align:start position:0% >> Yeah. And I know we've tried I think 00:14:30.399 --> 00:14:31.990 align:start position:0% >> Yeah. And I know we've tried I think we've<00:14:30.639> tried<00:14:30.800> to<00:14:30.959> make<00:14:31.120> it<00:14:31.279> a<00:14:31.519> little<00:14:31.600> bit<00:14:31.760> more 00:14:31.990 --> 00:14:32.000 align:start position:0% we've tried to make it a little bit more 00:14:32.000 --> 00:14:33.750 align:start position:0% we've tried to make it a little bit more clear<00:14:32.240> in<00:14:32.560> some<00:14:32.720> of<00:14:32.800> those<00:14:33.040> version<00:14:33.360> updates 00:14:33.750 --> 00:14:33.760 align:start position:0% clear in some of those version updates 00:14:33.760 --> 00:14:35.829 align:start position:0% clear in some of those version updates when<00:14:33.920> we<00:14:34.079> say<00:14:34.240> we're<00:14:34.480> doing<00:14:34.639> a<00:14:34.800> catalog<00:14:35.360> update 00:14:35.829 --> 00:14:35.839 align:start position:0% when we say we're doing a catalog update 00:14:35.839 --> 00:14:39.030 align:start position:0% when we say we're doing a catalog update of<00:14:36.399> the<00:14:36.639> the<00:14:37.120> app<00:14:37.279> itself<00:14:38.320> of<00:14:38.560> you<00:14:38.720> know<00:14:38.800> the 00:14:39.030 --> 00:14:39.040 align:start position:0% of the the app itself of you know the 00:14:39.040 --> 00:14:41.430 align:start position:0% of the the app itself of you know the underpinning<00:14:39.600> framework<00:14:40.399> versus<00:14:40.880> this<00:14:41.120> is<00:14:41.199> a 00:14:41.430 --> 00:14:41.440 align:start position:0% underpinning framework versus this is a 00:14:41.440 --> 00:14:42.870 align:start position:0% underpinning framework versus this is a new<00:14:41.600> version<00:14:41.760> of<00:14:41.920> the<00:14:42.079> app<00:14:42.320> that's<00:14:42.639> coming 00:14:42.870 --> 00:14:42.880 align:start position:0% new version of the app that's coming 00:14:42.880 --> 00:14:44.790 align:start position:0% new version of the app that's coming down<00:14:43.120> from<00:14:43.600> you<00:14:43.760> know<00:14:43.920> upstream.<00:14:44.560> I<00:14:44.720> think 00:14:44.790 --> 00:14:44.800 align:start position:0% down from you know upstream. I think 00:14:44.800 --> 00:14:46.150 align:start position:0% down from you know upstream. I think we've<00:14:45.040> tried<00:14:45.199> to<00:14:45.360> sort<00:14:45.519> of<00:14:45.600> make<00:14:45.760> that<00:14:45.920> a 00:14:46.150 --> 00:14:46.160 align:start position:0% we've tried to sort of make that a 00:14:46.160 --> 00:14:47.990 align:start position:0% we've tried to sort of make that a little<00:14:46.240> bit<00:14:46.399> more<00:14:46.560> visible<00:14:46.959> in<00:14:47.279> our<00:14:47.760> you<00:14:47.839> know 00:14:47.990 --> 00:14:48.000 align:start position:0% little bit more visible in our you know 00:14:48.000 --> 00:14:49.990 align:start position:0% little bit more visible in our you know our<00:14:48.240> latest<00:14:48.560> versions.<00:14:49.040> It's<00:14:49.600> you<00:14:49.760> know 00:14:49.990 --> 00:14:50.000 align:start position:0% our latest versions. It's you know 00:14:50.000 --> 00:14:51.430 align:start position:0% our latest versions. It's you know probably<00:14:50.240> going<00:14:50.320> to<00:14:50.480> improve<00:14:50.720> a<00:14:50.880> bit<00:14:51.040> more<00:14:51.199> in 00:14:51.430 --> 00:14:51.440 align:start position:0% probably going to improve a bit more in 00:14:51.440 --> 00:14:54.389 align:start position:0% probably going to improve a bit more in 26<00:14:51.920> as<00:14:52.160> well.<00:14:53.040> We<00:14:53.279> did.<00:14:53.600> It<00:14:53.920> labels<00:14:54.240> them 00:14:54.389 --> 00:14:54.399 align:start position:0% 26 as well. We did. It labels them 00:14:54.399 --> 00:14:55.750 align:start position:0% 26 as well. We did. It labels them differently<00:14:54.639> in<00:14:54.800> the<00:14:54.880> nightlys,<00:14:55.360> Chris,<00:14:55.519> if 00:14:55.750 --> 00:14:55.760 align:start position:0% differently in the nightlys, Chris, if 00:14:55.760 --> 00:14:56.949 align:start position:0% differently in the nightlys, Chris, if you<00:14:55.839> haven't<00:14:56.000> seen<00:14:56.160> that<00:14:56.320> yet,<00:14:56.560> where<00:14:56.800> it 00:14:56.949 --> 00:14:56.959 align:start position:0% you haven't seen that yet, where it 00:14:56.959 --> 00:14:58.790 align:start position:0% you haven't seen that yet, where it labels<00:14:57.360> things<00:14:57.600> as<00:14:57.839> there's<00:14:58.079> a<00:14:58.320> revision 00:14:58.790 --> 00:14:58.800 align:start position:0% labels things as there's a revision 00:14:58.800 --> 00:15:00.470 align:start position:0% labels things as there's a revision available,<00:14:59.440> which<00:14:59.680> is<00:14:59.839> different<00:15:00.079> wording 00:15:00.470 --> 00:15:00.480 align:start position:0% available, which is different wording 00:15:00.480 --> 00:15:02.470 align:start position:0% available, which is different wording than<00:15:00.639> there's<00:15:00.880> a<00:15:01.040> new<00:15:01.279> version<00:15:01.760> available. 00:15:02.470 --> 00:15:02.480 align:start position:0% than there's a new version available. 00:15:02.480 --> 00:15:04.069 align:start position:0% than there's a new version available. Again,<00:15:02.880> slight<00:15:03.199> distinction,<00:15:03.600> but<00:15:03.839> if<00:15:04.000> you 00:15:04.069 --> 00:15:04.079 align:start position:0% Again, slight distinction, but if you 00:15:04.079 --> 00:15:05.829 align:start position:0% Again, slight distinction, but if you pay<00:15:04.240> attention<00:15:04.480> to<00:15:04.639> it,<00:15:04.800> you'll<00:15:05.120> notice 00:15:05.829 --> 00:15:05.839 align:start position:0% pay attention to it, you'll notice 00:15:05.839 --> 00:15:07.590 align:start position:0% pay attention to it, you'll notice that's<00:15:06.160> to<00:15:06.320> give<00:15:06.480> you<00:15:06.639> the<00:15:06.800> indication<00:15:07.279> of, 00:15:07.590 --> 00:15:07.600 align:start position:0% that's to give you the indication of, 00:15:07.600 --> 00:15:09.269 align:start position:0% that's to give you the indication of, okay,<00:15:07.839> the<00:15:08.000> app<00:15:08.240> itself<00:15:08.639> hasn't<00:15:08.959> had<00:15:09.120> a 00:15:09.269 --> 00:15:09.279 align:start position:0% okay, the app itself hasn't had a 00:15:09.279 --> 00:15:11.110 align:start position:0% okay, the app itself hasn't had a version<00:15:09.600> bump.<00:15:09.920> So,<00:15:10.079> Plex<00:15:10.480> is<00:15:10.639> still<00:15:10.800> the<00:15:10.959> same 00:15:11.110 --> 00:15:11.120 align:start position:0% version bump. So, Plex is still the same 00:15:11.120 --> 00:15:13.590 align:start position:0% version bump. So, Plex is still the same version,<00:15:12.000> but<00:15:12.320> we're<00:15:12.560> pushing<00:15:12.959> pushing<00:15:13.360> an 00:15:13.590 --> 00:15:13.600 align:start position:0% version, but we're pushing pushing an 00:15:13.600 --> 00:15:16.389 align:start position:0% version, but we're pushing pushing an infrastructure<00:15:14.240> update<00:15:14.720> to<00:15:14.959> the<00:15:15.120> app.<00:15:15.519> Now, 00:15:16.389 --> 00:15:16.399 align:start position:0% infrastructure update to the app. Now, 00:15:16.399 --> 00:15:18.150 align:start position:0% infrastructure update to the app. Now, you<00:15:16.639> can<00:15:16.720> make<00:15:16.880> a<00:15:17.040> choice<00:15:17.279> now.<00:15:17.680> Do<00:15:17.839> you<00:15:18.000> need 00:15:18.150 --> 00:15:18.160 align:start position:0% you can make a choice now. Do you need 00:15:18.160 --> 00:15:20.629 align:start position:0% you can make a choice now. Do you need to<00:15:18.320> install<00:15:18.639> that<00:15:18.880> update?<00:15:19.760> No.<00:15:20.240> If<00:15:20.399> your 00:15:20.629 --> 00:15:20.639 align:start position:0% to install that update? No. If your 00:15:20.639 --> 00:15:22.069 align:start position:0% to install that update? No. If your app's<00:15:20.959> running<00:15:21.199> and<00:15:21.360> you're<00:15:21.519> happy<00:15:21.680> with<00:15:21.839> the 00:15:22.069 --> 00:15:22.079 align:start position:0% app's running and you're happy with the 00:15:22.079 --> 00:15:23.910 align:start position:0% app's running and you're happy with the version<00:15:22.320> of<00:15:22.399> Plex<00:15:22.880> and<00:15:23.120> you're<00:15:23.360> good<00:15:23.519> with<00:15:23.760> how 00:15:23.910 --> 00:15:23.920 align:start position:0% version of Plex and you're good with how 00:15:23.920 --> 00:15:25.509 align:start position:0% version of Plex and you're good with how it<00:15:24.079> runs<00:15:24.320> and<00:15:24.560> there's<00:15:24.720> no<00:15:24.880> new<00:15:25.120> features<00:15:25.360> you 00:15:25.509 --> 00:15:25.519 align:start position:0% it runs and there's no new features you 00:15:25.519 --> 00:15:28.069 align:start position:0% it runs and there's no new features you need<00:15:25.680> there,<00:15:26.000> great.<00:15:27.199> But<00:15:27.440> if<00:15:27.680> you're<00:15:27.839> one<00:15:28.000> of 00:15:28.069 --> 00:15:28.079 align:start position:0% need there, great. But if you're one of 00:15:28.079 --> 00:15:29.509 align:start position:0% need there, great. But if you're one of these<00:15:28.240> guys<00:15:28.399> where<00:15:28.560> it's<00:15:28.720> like,<00:15:29.120> I<00:15:29.279> do<00:15:29.360> want 00:15:29.509 --> 00:15:29.519 align:start position:0% these guys where it's like, I do want 00:15:29.519 --> 00:15:31.350 align:start position:0% these guys where it's like, I do want the<00:15:29.680> infrastructure<00:15:30.320> update<00:15:30.720> because<00:15:30.959> I<00:15:31.199> want 00:15:31.350 --> 00:15:31.360 align:start position:0% the infrastructure update because I want 00:15:31.360 --> 00:15:33.590 align:start position:0% the infrastructure update because I want to<00:15:31.519> be<00:15:31.600> able<00:15:31.680> to<00:15:31.839> attach<00:15:32.160> that<00:15:32.480> to<00:15:32.959> the<00:15:33.199> Docker 00:15:33.590 --> 00:15:33.600 align:start position:0% to be able to attach that to the Docker 00:15:33.600 --> 00:15:35.910 align:start position:0% to be able to attach that to the Docker network<00:15:34.079> or<00:15:34.720> sometimes<00:15:35.120> that<00:15:35.440> infrastructure 00:15:35.910 --> 00:15:35.920 align:start position:0% network or sometimes that infrastructure 00:15:35.920 --> 00:15:37.189 align:start position:0% network or sometimes that infrastructure update<00:15:36.240> might<00:15:36.480> have<00:15:36.639> nothing<00:15:36.800> to<00:15:36.880> do<00:15:37.040> with 00:15:37.189 --> 00:15:37.199 align:start position:0% update might have nothing to do with 00:15:37.199 --> 00:15:38.710 align:start position:0% update might have nothing to do with Docker<00:15:37.519> networks.<00:15:37.920> It<00:15:38.079> could<00:15:38.240> be<00:15:38.320> that<00:15:38.480> we 00:15:38.710 --> 00:15:38.720 align:start position:0% Docker networks. It could be that we 00:15:38.720 --> 00:15:40.790 align:start position:0% Docker networks. It could be that we added<00:15:38.959> a<00:15:39.120> new<00:15:39.360> checkbox<00:15:39.920> to<00:15:40.160> the<00:15:40.320> wizard<00:15:40.639> for 00:15:40.790 --> 00:15:40.800 align:start position:0% added a new checkbox to the wizard for 00:15:40.800 --> 00:15:42.949 align:start position:0% added a new checkbox to the wizard for that<00:15:41.040> app<00:15:41.279> to<00:15:41.600> turn<00:15:41.760> on<00:15:42.000> or<00:15:42.160> off<00:15:42.399> some<00:15:42.720> feature 00:15:42.949 --> 00:15:42.959 align:start position:0% that app to turn on or off some feature 00:15:42.959 --> 00:15:45.350 align:start position:0% that app to turn on or off some feature that<00:15:43.199> has<00:15:43.360> to<00:15:43.440> be<00:15:43.600> set<00:15:43.680> at<00:15:43.920> runtime.<00:15:44.959> Cool. 00:15:45.350 --> 00:15:45.360 align:start position:0% that has to be set at runtime. Cool. 00:15:45.360 --> 00:15:46.470 align:start position:0% that has to be set at runtime. Cool. That's<00:15:45.519> when<00:15:45.680> you<00:15:45.839> would<00:15:46.000> go<00:15:46.160> get<00:15:46.320> that 00:15:46.470 --> 00:15:46.480 align:start position:0% That's when you would go get that 00:15:46.480 --> 00:15:47.910 align:start position:0% That's when you would go get that revision.<00:15:47.120> if<00:15:47.279> you<00:15:47.440> care<00:15:47.600> about<00:15:47.760> that 00:15:47.910 --> 00:15:47.920 align:start position:0% revision. if you care about that 00:15:47.920 --> 00:15:49.590 align:start position:0% revision. if you care about that checkbox,<00:15:48.480> you<00:15:48.639> now<00:15:48.800> have<00:15:48.959> it<00:15:49.120> available<00:15:49.440> and 00:15:49.590 --> 00:15:49.600 align:start position:0% checkbox, you now have it available and 00:15:49.600 --> 00:15:51.670 align:start position:0% checkbox, you now have it available and can<00:15:49.759> use<00:15:49.920> it.<00:15:50.399> Um,<00:15:50.720> a<00:15:50.880> lot<00:15:51.040> of<00:15:51.120> reasons<00:15:51.440> we'll 00:15:51.670 --> 00:15:51.680 align:start position:0% can use it. Um, a lot of reasons we'll 00:15:51.680 --> 00:15:52.710 align:start position:0% can use it. Um, a lot of reasons we'll push<00:15:51.920> those. 00:15:52.710 --> 00:15:52.720 align:start position:0% push those. 00:15:52.720 --> 00:15:54.550 align:start position:0% push those. >> Yeah,<00:15:52.959> it's<00:15:53.120> it's<00:15:53.440> mostly<00:15:53.759> like<00:15:53.920> the<00:15:54.160> UI 00:15:54.550 --> 00:15:54.560 align:start position:0% >> Yeah, it's it's mostly like the UI 00:15:54.560 --> 00:15:56.870 align:start position:0% >> Yeah, it's it's mostly like the UI updates.<00:15:55.120> Uh,<00:15:55.440> things<00:15:55.680> that<00:15:55.839> maybe<00:15:56.399> used<00:15:56.639> to 00:15:56.870 --> 00:15:56.880 align:start position:0% updates. Uh, things that maybe used to 00:15:56.880 --> 00:15:59.110 align:start position:0% updates. Uh, things that maybe used to require<00:15:57.279> a<00:15:57.680> manual<00:15:58.079> environment<00:15:58.639> variable 00:15:59.110 --> 00:15:59.120 align:start position:0% require a manual environment variable 00:15:59.120 --> 00:16:01.590 align:start position:0% require a manual environment variable parameter<00:15:59.680> set<00:16:00.000> as<00:16:00.560> you<00:16:00.639> know<00:16:00.800> now<00:16:01.040> a<00:16:01.199> toggle 00:16:01.590 --> 00:16:01.600 align:start position:0% parameter set as you know now a toggle 00:16:01.600 --> 00:16:03.670 align:start position:0% parameter set as you know now a toggle or<00:16:01.839> a<00:16:02.000> drop<00:16:02.240> down<00:16:02.480> or<00:16:02.720> a<00:16:02.880> select<00:16:03.199> or<00:16:03.440> something 00:16:03.670 --> 00:16:03.680 align:start position:0% or a drop down or a select or something 00:16:03.680 --> 00:16:06.150 align:start position:0% or a drop down or a select or something like<00:16:03.920> that.<00:16:04.560> It's<00:16:04.880> that<00:16:05.199> that<00:16:05.440> would<00:16:05.600> be<00:16:05.759> your 00:16:06.150 --> 00:16:06.160 align:start position:0% like that. It's that that would be your 00:16:06.160 --> 00:16:08.790 align:start position:0% like that. It's that that would be your revisions<00:16:06.880> as<00:16:07.199> opposed<00:16:07.440> to<00:16:07.600> your<00:16:07.839> versions. 00:16:08.790 --> 00:16:08.800 align:start position:0% revisions as opposed to your versions. 00:16:08.800 --> 00:16:09.350 align:start position:0% revisions as opposed to your versions. >> Yeah. 00:16:09.350 --> 00:16:09.360 align:start position:0% >> Yeah. 00:16:09.360 --> 00:16:09.749 align:start position:0% >> Yeah. >> Yeah. 00:16:09.749 --> 00:16:09.759 align:start position:0% >> Yeah. 00:16:09.759 --> 00:16:11.269 align:start position:0% >> Yeah. >> Which<00:16:10.000> you<00:16:10.240> have<00:16:10.320> to<00:16:10.399> push<00:16:10.639> those<00:16:10.959> again. 00:16:11.269 --> 00:16:11.279 align:start position:0% >> Which you have to push those again. 00:16:11.279 --> 00:16:12.870 align:start position:0% >> Which you have to push those again. There's<00:16:11.440> no<00:16:11.600> way<00:16:11.680> to<00:16:11.920> just<00:16:12.079> silently<00:16:12.639> apply 00:16:12.870 --> 00:16:12.880 align:start position:0% There's no way to just silently apply 00:16:12.880 --> 00:16:14.150 align:start position:0% There's no way to just silently apply those<00:16:13.120> and<00:16:13.279> do<00:16:13.440> them<00:16:13.519> in<00:16:13.680> the<00:16:13.839> background. 00:16:14.150 --> 00:16:14.160 align:start position:0% those and do them in the background. 00:16:14.160 --> 00:16:16.069 align:start position:0% those and do them in the background. that<00:16:14.399> would<00:16:14.560> be<00:16:14.639> kind<00:16:14.880> of<00:16:15.120> uh<00:16:15.440> disruptive 00:16:16.069 --> 00:16:16.079 align:start position:0% that would be kind of uh disruptive 00:16:16.079 --> 00:16:17.590 align:start position:0% that would be kind of uh disruptive potentially<00:16:16.480> to<00:16:16.720> people<00:16:16.880> if<00:16:17.120> they<00:16:17.279> saw<00:16:17.440> their 00:16:17.590 --> 00:16:17.600 align:start position:0% potentially to people if they saw their 00:16:17.600 --> 00:16:19.189 align:start position:0% potentially to people if they saw their apps<00:16:17.920> flapping<00:16:18.320> up<00:16:18.399> and<00:16:18.560> down<00:16:18.800> and<00:16:18.959> didn't 00:16:19.189 --> 00:16:19.199 align:start position:0% apps flapping up and down and didn't 00:16:19.199 --> 00:16:20.710 align:start position:0% apps flapping up and down and didn't know<00:16:19.360> why.<00:16:19.680> So,<00:16:19.920> we<00:16:20.160> are<00:16:20.240> going<00:16:20.320> to<00:16:20.399> at<00:16:20.480> least 00:16:20.710 --> 00:16:20.720 align:start position:0% know why. So, we are going to at least 00:16:20.720 --> 00:16:22.150 align:start position:0% know why. So, we are going to at least flag<00:16:21.040> them<00:16:21.120> and<00:16:21.279> give<00:16:21.440> you<00:16:21.519> the<00:16:21.759> choice<00:16:21.920> on 00:16:22.150 --> 00:16:22.160 align:start position:0% flag them and give you the choice on 00:16:22.160 --> 00:16:23.509 align:start position:0% flag them and give you the choice on when<00:16:22.320> you<00:16:22.480> want<00:16:22.560> to<00:16:22.720> click<00:16:22.880> the<00:16:23.040> button<00:16:23.199> to<00:16:23.360> go 00:16:23.509 --> 00:16:23.519 align:start position:0% when you want to click the button to go 00:16:23.519 --> 00:16:24.470 align:start position:0% when you want to click the button to go and<00:16:23.680> deploy. 00:16:24.470 --> 00:16:24.480 align:start position:0% and deploy. 00:16:24.480 --> 00:16:27.030 align:start position:0% and deploy. >> Yeah.<00:16:25.199> Um<00:16:25.519> just<00:16:25.759> quick<00:16:26.000> little<00:16:26.240> side<00:16:26.480> notes<00:16:26.800> on 00:16:27.030 --> 00:16:27.040 align:start position:0% >> Yeah. Um just quick little side notes on 00:16:27.040 --> 00:16:28.949 align:start position:0% >> Yeah. Um just quick little side notes on apps<00:16:27.360> there.<00:16:27.600> Uh<00:16:27.920> there<00:16:28.079> was<00:16:28.240> a<00:16:28.399> little<00:16:28.560> bit<00:16:28.639> of 00:16:28.949 --> 00:16:28.959 align:start position:0% apps there. Uh there was a little bit of 00:16:28.959 --> 00:16:30.629 align:start position:0% apps there. Uh there was a little bit of uh<00:16:29.120> some<00:16:29.360> controversy<00:16:29.920> that<00:16:30.079> was<00:16:30.160> stirred<00:16:30.480> up 00:16:30.629 --> 00:16:30.639 align:start position:0% uh some controversy that was stirred up 00:16:30.639 --> 00:16:32.310 align:start position:0% uh some controversy that was stirred up this<00:16:30.800> past<00:16:31.040> week<00:16:31.279> over<00:16:31.519> one<00:16:31.680> app<00:16:31.920> that<00:16:32.079> was<00:16:32.160> in 00:16:32.310 --> 00:16:32.320 align:start position:0% this past week over one app that was in 00:16:32.320 --> 00:16:33.749 align:start position:0% this past week over one app that was in the<00:16:32.399> catalog.<00:16:32.880> I<00:16:33.040> believe<00:16:33.199> that<00:16:33.360> was<00:16:33.519> called 00:16:33.749 --> 00:16:33.759 align:start position:0% the catalog. I believe that was called 00:16:33.759 --> 00:16:36.550 align:start position:0% the catalog. I believe that was called Hunter.<00:16:34.720> Um<00:16:35.440> we<00:16:35.680> we<00:16:36.000> did<00:16:36.160> get<00:16:36.320> the 00:16:36.550 --> 00:16:36.560 align:start position:0% Hunter. Um we we did get the 00:16:36.560 --> 00:16:38.870 align:start position:0% Hunter. Um we we did get the notification<00:16:37.040> on<00:16:37.279> that<00:16:37.440> one.<00:16:38.000> Um<00:16:38.320> and<00:16:38.639> that 00:16:38.870 --> 00:16:38.880 align:start position:0% notification on that one. Um and that 00:16:38.880 --> 00:16:40.629 align:start position:0% notification on that one. Um and that one<00:16:39.040> has<00:16:39.360> been<00:16:39.519> pulled<00:16:39.759> out<00:16:39.920> of<00:16:40.000> the<00:16:40.160> catalog 00:16:40.629 --> 00:16:40.639 align:start position:0% one has been pulled out of the catalog 00:16:40.639 --> 00:16:43.030 align:start position:0% one has been pulled out of the catalog now.<00:16:41.360> So<00:16:41.600> if<00:16:41.839> you<00:16:42.000> do<00:16:42.240> notice<00:16:42.480> that<00:16:42.720> there<00:16:42.880> is 00:16:43.030 --> 00:16:43.040 align:start position:0% now. So if you do notice that there is 00:16:43.040 --> 00:16:44.949 align:start position:0% now. So if you do notice that there is something<00:16:43.279> that<00:16:43.519> is<00:16:43.839> uh<00:16:44.000> particularly<00:16:44.639> off 00:16:44.949 --> 00:16:44.959 align:start position:0% something that is uh particularly off 00:16:44.959 --> 00:16:47.110 align:start position:0% something that is uh particularly off about<00:16:45.199> a<00:16:45.440> given<00:16:45.680> app<00:16:46.000> or<00:16:46.320> there's<00:16:46.720> uh<00:16:46.880> some 00:16:47.110 --> 00:16:47.120 align:start position:0% about a given app or there's uh some 00:16:47.120 --> 00:16:49.269 align:start position:0% about a given app or there's uh some security<00:16:47.519> issue<00:16:47.839> that<00:16:48.079> needs<00:16:48.320> to<00:16:48.480> be<00:16:49.040> brought 00:16:49.269 --> 00:16:49.279 align:start position:0% security issue that needs to be brought 00:16:49.279 --> 00:16:51.110 align:start position:0% security issue that needs to be brought to<00:16:49.440> our<00:16:49.600> attention,<00:16:50.079> I<00:16:50.240> mean<00:16:50.480> please<00:16:50.720> do<00:16:50.959> let 00:16:51.110 --> 00:16:51.120 align:start position:0% to our attention, I mean please do let 00:16:51.120 --> 00:16:53.509 align:start position:0% to our attention, I mean please do let us<00:16:51.279> know<00:16:51.600> directly<00:16:52.399> and<00:16:52.639> we<00:16:52.880> will<00:16:53.040> try<00:16:53.199> to<00:16:53.279> jump 00:16:53.509 --> 00:16:53.519 align:start position:0% us know directly and we will try to jump 00:16:53.519 --> 00:16:55.829 align:start position:0% us know directly and we will try to jump on<00:16:53.680> those<00:16:53.920> as<00:16:54.160> quickly<00:16:54.399> as<00:16:54.639> possible.<00:16:55.360> Uh<00:16:55.600> we 00:16:55.829 --> 00:16:55.839 align:start position:0% on those as quickly as possible. Uh we 00:16:55.839 --> 00:16:57.509 align:start position:0% on those as quickly as possible. Uh we always<00:16:56.079> are<00:16:56.399> interested<00:16:56.880> in<00:16:57.199> you<00:16:57.279> know 00:16:57.509 --> 00:16:57.519 align:start position:0% always are interested in you know 00:16:57.519 --> 00:16:59.350 align:start position:0% always are interested in you know protecting<00:16:57.920> everybody<00:16:58.320> as<00:16:58.560> best<00:16:58.720> as<00:16:58.880> we<00:16:59.120> can 00:16:59.350 --> 00:16:59.360 align:start position:0% protecting everybody as best as we can 00:16:59.360 --> 00:17:01.350 align:start position:0% protecting everybody as best as we can and<00:16:59.920> if<00:17:00.160> we<00:17:00.320> see<00:17:00.480> something<00:17:00.639> like<00:17:00.800> that<00:17:01.040> sneak 00:17:01.350 --> 00:17:01.360 align:start position:0% and if we see something like that sneak 00:17:01.360 --> 00:17:02.949 align:start position:0% and if we see something like that sneak into<00:17:01.519> a<00:17:01.759> community<00:17:02.000> app,<00:17:02.320> we<00:17:02.560> certainly<00:17:02.800> want 00:17:02.949 --> 00:17:02.959 align:start position:0% into a community app, we certainly want 00:17:02.959 --> 00:17:04.390 align:start position:0% into a community app, we certainly want to<00:17:03.040> make<00:17:03.199> sure<00:17:03.279> that<00:17:03.519> is<00:17:03.680> cleared<00:17:03.920> up<00:17:04.160> as 00:17:04.390 --> 00:17:04.400 align:start position:0% to make sure that is cleared up as 00:17:04.400 --> 00:17:06.789 align:start position:0% to make sure that is cleared up as quickly<00:17:04.720> as<00:17:04.880> we<00:17:05.039> can<00:17:05.199> get<00:17:05.360> it.<00:17:05.839> Um<00:17:06.240> it<00:17:06.480> is<00:17:06.640> one 00:17:06.789 --> 00:17:06.799 align:start position:0% quickly as we can get it. Um it is one 00:17:06.799 --> 00:17:08.150 align:start position:0% quickly as we can get it. Um it is one of<00:17:06.880> those<00:17:06.959> things<00:17:07.199> though<00:17:07.439> you<00:17:07.600> do<00:17:07.760> have<00:17:07.919> to<00:17:08.000> be 00:17:08.150 --> 00:17:08.160 align:start position:0% of those things though you do have to be 00:17:08.160 --> 00:17:10.390 align:start position:0% of those things though you do have to be careful<00:17:08.480> about<00:17:08.720> which<00:17:08.959> apps<00:17:09.280> you're<00:17:09.520> running. 00:17:10.390 --> 00:17:10.400 align:start position:0% careful about which apps you're running. 00:17:10.400 --> 00:17:12.309 align:start position:0% careful about which apps you're running. um<00:17:10.799> take<00:17:11.039> take<00:17:11.280> a<00:17:11.439> look<00:17:11.520> at<00:17:11.600> them<00:17:11.839> just<00:17:12.079> because 00:17:12.309 --> 00:17:12.319 align:start position:0% um take take a look at them just because 00:17:12.319 --> 00:17:13.909 align:start position:0% um take take a look at them just because something<00:17:12.640> has<00:17:12.880> been<00:17:13.199> you<00:17:13.280> know<00:17:13.439> showing<00:17:13.679> up 00:17:13.909 --> 00:17:13.919 align:start position:0% something has been you know showing up 00:17:13.919 --> 00:17:15.669 align:start position:0% something has been you know showing up on<00:17:14.240> popular<00:17:14.640> trending<00:17:15.120> whether<00:17:15.280> it's<00:17:15.520> you 00:17:15.669 --> 00:17:15.679 align:start position:0% on popular trending whether it's you 00:17:15.679 --> 00:17:18.069 align:start position:0% on popular trending whether it's you know<00:17:15.760> on<00:17:16.160> you<00:17:16.319> know<00:17:16.559> the<00:17:16.799> Y<00:17:17.039> combinator<00:17:17.679> Reddit 00:17:18.069 --> 00:17:18.079 align:start position:0% know on you know the Y combinator Reddit 00:17:18.079 --> 00:17:20.390 align:start position:0% know on you know the Y combinator Reddit whatever<00:17:18.799> take<00:17:18.959> a<00:17:19.120> look<00:17:19.199> at<00:17:19.280> the<00:17:19.439> app<00:17:19.679> and<00:17:20.160> just 00:17:20.390 --> 00:17:20.400 align:start position:0% whatever take a look at the app and just 00:17:20.400 --> 00:17:22.630 align:start position:0% whatever take a look at the app and just say<00:17:20.640> you<00:17:20.799> know<00:17:20.959> do<00:17:21.120> do<00:17:21.360> I<00:17:21.600> trust<00:17:21.839> this<00:17:22.079> with<00:17:22.319> the 00:17:22.630 --> 00:17:22.640 align:start position:0% say you know do do I trust this with the 00:17:22.640 --> 00:17:24.870 align:start position:0% say you know do do I trust this with the access<00:17:22.959> that<00:17:23.199> I'm<00:17:23.360> going<00:17:23.439> to<00:17:23.600> grant<00:17:23.919> it<00:17:24.160> and 00:17:24.870 --> 00:17:24.880 align:start position:0% access that I'm going to grant it and 00:17:24.880 --> 00:17:26.549 align:start position:0% access that I'm going to grant it and you<00:17:25.039> know<00:17:25.199> just<00:17:25.679> give<00:17:25.839> it<00:17:26.000> give<00:17:26.240> it<00:17:26.319> that 00:17:26.549 --> 00:17:26.559 align:start position:0% you know just give it give it that 00:17:26.559 --> 00:17:28.309 align:start position:0% you know just give it give it that little<00:17:26.720> moment<00:17:26.959> of<00:17:27.120> thought<00:17:27.439> I<00:17:27.600> I<00:17:27.919> don't<00:17:28.000> run<00:17:28.160> a 00:17:28.309 --> 00:17:28.319 align:start position:0% little moment of thought I I don't run a 00:17:28.319 --> 00:17:32.630 align:start position:0% little moment of thought I I don't run a whole<00:17:28.480> lot<00:17:28.559> of<00:17:28.720> apps<00:17:29.039> myself<00:17:30.160> um<00:17:31.280> I<00:17:31.600> I'm<00:17:32.400> pretty 00:17:32.630 --> 00:17:32.640 align:start position:0% whole lot of apps myself um I I'm pretty 00:17:32.640 --> 00:17:34.230 align:start position:0% whole lot of apps myself um I I'm pretty picky<00:17:32.960> about<00:17:33.120> what<00:17:33.360> I<00:17:33.520> want<00:17:33.600> to<00:17:33.679> run<00:17:33.840> on<00:17:34.080> my 00:17:34.230 --> 00:17:34.240 align:start position:0% picky about what I want to run on my 00:17:34.240 --> 00:17:36.070 align:start position:0% picky about what I want to run on my system<00:17:34.640> and<00:17:35.039> some<00:17:35.200> of<00:17:35.280> them<00:17:35.440> I<00:17:35.600> keep<00:17:35.760> degrees 00:17:36.070 --> 00:17:36.080 align:start position:0% system and some of them I keep degrees 00:17:36.080 --> 00:17:37.430 align:start position:0% system and some of them I keep degrees of<00:17:36.320> separation 00:17:37.430 --> 00:17:37.440 align:start position:0% of separation 00:17:37.440 --> 00:17:39.350 align:start position:0% of separation >> I<00:17:37.600> I<00:17:37.919> run<00:17:38.080> more<00:17:38.320> than<00:17:38.480> I<00:17:38.640> probably<00:17:38.880> should<00:17:39.200> but 00:17:39.350 --> 00:17:39.360 align:start position:0% >> I I run more than I probably should but 00:17:39.360 --> 00:17:41.110 align:start position:0% >> I I run more than I probably should but that's<00:17:39.520> just<00:17:39.760> how<00:17:39.919> I<00:17:40.080> roll.<00:17:40.400> I<00:17:40.640> mean,<00:17:40.720> I<00:17:40.799> I 00:17:41.110 --> 00:17:41.120 align:start position:0% that's just how I roll. I mean, I I 00:17:41.120 --> 00:17:42.230 align:start position:0% that's just how I roll. I mean, I I think<00:17:41.200> we've<00:17:41.440> been<00:17:41.600> through<00:17:41.760> some<00:17:41.919> of<00:17:42.000> these 00:17:42.230 --> 00:17:42.240 align:start position:0% think we've been through some of these 00:17:42.240 --> 00:17:43.590 align:start position:0% think we've been through some of these on<00:17:42.480> previous<00:17:42.720> episodes.<00:17:43.200> Actually,<00:17:43.440> one<00:17:43.520> of 00:17:43.590 --> 00:17:43.600 align:start position:0% on previous episodes. Actually, one of 00:17:43.600 --> 00:17:45.909 align:start position:0% on previous episodes. Actually, one of my<00:17:43.840> favorite<00:17:44.000> ones<00:17:44.240> right<00:17:44.400> now<00:17:44.480> is<00:17:44.720> Meie. 00:17:45.909 --> 00:17:45.919 align:start position:0% my favorite ones right now is Meie. 00:17:45.919 --> 00:17:47.110 align:start position:0% my favorite ones right now is Meie. >> I<00:17:46.080> don't<00:17:46.160> know<00:17:46.160> if<00:17:46.320> you've<00:17:46.480> seen<00:17:46.640> this<00:17:46.799> one, 00:17:47.110 --> 00:17:47.120 align:start position:0% >> I don't know if you've seen this one, 00:17:47.120 --> 00:17:49.029 align:start position:0% >> I don't know if you've seen this one, Chris,<00:17:47.360> but<00:17:47.520> it's<00:17:47.600> like<00:17:47.760> it's<00:17:48.000> a<00:17:48.160> recipe,<00:17:48.880> you 00:17:49.029 --> 00:17:49.039 align:start position:0% Chris, but it's like it's a recipe, you 00:17:49.039 --> 00:17:51.350 align:start position:0% Chris, but it's like it's a recipe, you know,<00:17:49.200> application.<00:17:50.000> So,<00:17:50.160> I<00:17:50.400> can<00:17:50.559> go<00:17:50.720> and<00:17:50.880> it, 00:17:51.350 --> 00:17:51.360 align:start position:0% know, application. So, I can go and it, 00:17:51.360 --> 00:17:52.470 align:start position:0% know, application. So, I can go and it, you<00:17:51.520> know,<00:17:51.600> how<00:17:51.760> you<00:17:51.919> go<00:17:52.000> to<00:17:52.160> all<00:17:52.320> these 00:17:52.470 --> 00:17:52.480 align:start position:0% you know, how you go to all these 00:17:52.480 --> 00:17:54.070 align:start position:0% you know, how you go to all these websites<00:17:52.880> these<00:17:53.200> days<00:17:53.280> and<00:17:53.520> it's<00:17:53.679> like<00:17:53.840> here's 00:17:54.070 --> 00:17:54.080 align:start position:0% websites these days and it's like here's 00:17:54.080 --> 00:17:55.430 align:start position:0% websites these days and it's like here's a<00:17:54.240> cool<00:17:54.400> recipe<00:17:54.640> and<00:17:54.880> you<00:17:55.039> want<00:17:55.120> to<00:17:55.200> make<00:17:55.360> it 00:17:55.430 --> 00:17:55.440 align:start position:0% a cool recipe and you want to make it 00:17:55.440 --> 00:17:58.870 align:start position:0% a cool recipe and you want to make it and<00:17:55.679> it's<00:17:55.840> like<00:17:56.080> 22<00:17:56.640> pages<00:17:57.039> long 00:17:58.870 --> 00:17:58.880 align:start position:0% and it's like 22 pages long 00:17:58.880 --> 00:17:59.750 align:start position:0% and it's like 22 pages long ads. 00:17:59.750 --> 00:17:59.760 align:start position:0% ads. 00:17:59.760 --> 00:18:02.950 align:start position:0% ads. >> Here's<00:18:00.080> my<00:18:00.320> life<00:18:00.720> story<00:18:01.120> before<00:18:01.360> I<00:18:02.640> story 00:18:02.950 --> 00:18:02.960 align:start position:0% >> Here's my life story before I story 00:18:02.960 --> 00:18:04.470 align:start position:0% >> Here's my life story before I story before<00:18:03.280> you<00:18:03.440> actually<00:18:03.760> get<00:18:03.919> the<00:18:04.080> freaking 00:18:04.470 --> 00:18:04.480 align:start position:0% before you actually get the freaking 00:18:04.480 --> 00:18:06.070 align:start position:0% before you actually get the freaking ingredients<00:18:05.039> and<00:18:05.280> all<00:18:05.440> this<00:18:05.600> and<00:18:05.760> that.<00:18:05.919> And 00:18:06.070 --> 00:18:06.080 align:start position:0% ingredients and all this and that. And 00:18:06.080 --> 00:18:08.310 align:start position:0% ingredients and all this and that. And so,<00:18:06.480> I<00:18:06.720> copy<00:18:07.039> and<00:18:07.200> paste<00:18:07.440> those<00:18:07.679> eurals<00:18:08.000> into 00:18:08.310 --> 00:18:08.320 align:start position:0% so, I copy and paste those eurals into 00:18:08.320 --> 00:18:10.390 align:start position:0% so, I copy and paste those eurals into Mey.<00:18:08.799> It<00:18:08.960> parses<00:18:09.360> it<00:18:09.440> and<00:18:09.679> does<00:18:09.840> all<00:18:10.000> the<00:18:10.240> work 00:18:10.390 --> 00:18:10.400 align:start position:0% Mey. It parses it and does all the work 00:18:10.400 --> 00:18:12.150 align:start position:0% Mey. It parses it and does all the work for<00:18:10.640> me<00:18:10.799> and<00:18:11.039> then<00:18:11.200> I<00:18:11.360> just<00:18:11.440> get<00:18:11.600> a<00:18:11.760> nice<00:18:11.919> clean 00:18:12.150 --> 00:18:12.160 align:start position:0% for me and then I just get a nice clean 00:18:12.160 --> 00:18:13.510 align:start position:0% for me and then I just get a nice clean recipe.<00:18:12.559> So<00:18:12.720> when<00:18:12.880> I'm<00:18:13.039> at<00:18:13.120> the<00:18:13.280> grocery 00:18:13.510 --> 00:18:13.520 align:start position:0% recipe. So when I'm at the grocery 00:18:13.520 --> 00:18:14.630 align:start position:0% recipe. So when I'm at the grocery store,<00:18:13.679> I<00:18:13.840> can<00:18:13.919> just<00:18:14.000> say,<00:18:14.080> "Okay,<00:18:14.400> I<00:18:14.559> got 00:18:14.630 --> 00:18:14.640 align:start position:0% store, I can just say, "Okay, I got 00:18:14.640 --> 00:18:16.150 align:start position:0% store, I can just say, "Okay, I got that.<00:18:14.880> Got<00:18:15.120> that.<00:18:15.280> Got<00:18:15.520> that.<00:18:15.679> Great.<00:18:15.919> I<00:18:16.080> can 00:18:16.150 --> 00:18:16.160 align:start position:0% that. Got that. Got that. Great. I can 00:18:16.160 --> 00:18:19.029 align:start position:0% that. Got that. Got that. Great. I can go home<00:18:16.320> and<00:18:16.480> cook."<00:18:17.360> Fantastic.<00:18:18.000> So<00:18:18.320> again, 00:18:19.029 --> 00:18:19.039 align:start position:0% go home and cook." Fantastic. So again, 00:18:19.039 --> 00:18:21.029 align:start position:0% go home and cook." Fantastic. So again, is<00:18:19.280> it<00:18:19.440> an<00:18:19.600> enterprise<00:18:20.000> app?<00:18:20.320> No.<00:18:20.559> But<00:18:20.720> is<00:18:20.880> it 00:18:21.029 --> 00:18:21.039 align:start position:0% is it an enterprise app? No. But is it 00:18:21.039 --> 00:18:22.390 align:start position:0% is it an enterprise app? No. But is it one<00:18:21.120> of<00:18:21.200> those<00:18:21.360> little<00:18:21.520> home<00:18:21.760> lab<00:18:22.000> things<00:18:22.160> that 00:18:22.390 --> 00:18:22.400 align:start position:0% one of those little home lab things that 00:18:22.400 --> 00:18:24.630 align:start position:0% one of those little home lab things that makes<00:18:22.559> me<00:18:22.799> happy?<00:18:23.280> Abso<00:18:23.679> freakingutely<00:18:24.400> it 00:18:24.630 --> 00:18:24.640 align:start position:0% makes me happy? Abso freakingutely it 00:18:24.640 --> 00:18:26.630 align:start position:0% makes me happy? Abso freakingutely it does<00:18:25.200> that.<00:18:25.520> And<00:18:25.679> then<00:18:26.000> I've<00:18:26.240> talked<00:18:26.400> about 00:18:26.630 --> 00:18:26.640 align:start position:0% does that. And then I've talked about 00:18:26.640 --> 00:18:28.630 align:start position:0% does that. And then I've talked about Jello<00:18:27.200> as<00:18:27.360> well.<00:18:27.679> That<00:18:27.840> was<00:18:28.000> one<00:18:28.160> I<00:18:28.320> was<00:18:28.480> really 00:18:28.630 --> 00:18:28.640 align:start position:0% Jello as well. That was one I was really 00:18:28.640 --> 00:18:31.270 align:start position:0% Jello as well. That was one I was really happy<00:18:28.799> to<00:18:28.960> help<00:18:29.120> bring<00:18:29.440> over.<00:18:30.080> We<00:18:30.320> have<00:18:30.559> a<00:18:30.880> huge 00:18:31.270 --> 00:18:31.280 align:start position:0% happy to help bring over. We have a huge 00:18:31.280 --> 00:18:33.830 align:start position:0% happy to help bring over. We have a huge book<00:18:31.600> catalog<00:18:32.080> at<00:18:32.320> the<00:18:32.480> house.<00:18:32.880> And<00:18:33.120> so<00:18:33.600> my 00:18:33.830 --> 00:18:33.840 align:start position:0% book catalog at the house. And so my 00:18:33.840 --> 00:18:35.750 align:start position:0% book catalog at the house. And so my wife<00:18:34.000> and<00:18:34.160> I<00:18:34.320> use<00:18:34.559> that<00:18:34.720> one<00:18:35.120> all<00:18:35.360> the<00:18:35.520> time 00:18:35.750 --> 00:18:35.760 align:start position:0% wife and I use that one all the time 00:18:35.760 --> 00:18:37.430 align:start position:0% wife and I use that one all the time because<00:18:36.080> every<00:18:36.320> time<00:18:36.400> we<00:18:36.640> buy<00:18:36.799> new<00:18:37.039> books<00:18:37.200> to 00:18:37.430 --> 00:18:37.440 align:start position:0% because every time we buy new books to 00:18:37.440 --> 00:18:39.190 align:start position:0% because every time we buy new books to add<00:18:37.520> to<00:18:37.679> our<00:18:37.919> personal<00:18:38.320> library,<00:18:38.720> we<00:18:38.880> scan<00:18:39.120> the 00:18:39.190 --> 00:18:39.200 align:start position:0% add to our personal library, we scan the 00:18:39.200 --> 00:18:41.110 align:start position:0% add to our personal library, we scan the ISBN<00:18:39.760> on<00:18:39.919> the<00:18:40.080> back<00:18:40.160> and<00:18:40.400> it<00:18:40.559> gets<00:18:40.720> added<00:18:40.960> to 00:18:41.110 --> 00:18:41.120 align:start position:0% ISBN on the back and it gets added to 00:18:41.120 --> 00:18:43.350 align:start position:0% ISBN on the back and it gets added to our<00:18:41.280> catalog<00:18:42.400> because<00:18:42.640> when<00:18:42.880> you<00:18:43.039> hit<00:18:43.120> a 00:18:43.350 --> 00:18:43.360 align:start position:0% our catalog because when you hit a 00:18:43.360 --> 00:18:45.350 align:start position:0% our catalog because when you hit a certain<00:18:43.600> threshold<00:18:44.000> of,<00:18:44.320> you<00:18:44.480> know,<00:18:44.720> 5,000 00:18:45.350 --> 00:18:45.360 align:start position:0% certain threshold of, you know, 5,000 00:18:45.360 --> 00:18:46.789 align:start position:0% certain threshold of, you know, 5,000 plus<00:18:45.600> books<00:18:45.840> you<00:18:46.080> have<00:18:46.160> on<00:18:46.320> your<00:18:46.480> library 00:18:46.789 --> 00:18:46.799 align:start position:0% plus books you have on your library 00:18:46.799 --> 00:18:48.470 align:start position:0% plus books you have on your library shelves,<00:18:47.200> it's<00:18:47.360> very<00:18:47.600> easy<00:18:47.760> to<00:18:47.919> double<00:18:48.240> buy 00:18:48.470 --> 00:18:48.480 align:start position:0% shelves, it's very easy to double buy 00:18:48.480 --> 00:18:49.830 align:start position:0% shelves, it's very easy to double buy where<00:18:48.720> it's<00:18:48.880> like, 00:18:49.830 --> 00:18:49.840 align:start position:0% where it's like, 00:18:49.840 --> 00:18:51.750 align:start position:0% where it's like, >> did<00:18:50.000> I<00:18:50.160> buy<00:18:50.400> that<00:18:50.559> one<00:18:50.720> yet?<00:18:51.039> I<00:18:51.200> know<00:18:51.360> I<00:18:51.520> wanted 00:18:51.750 --> 00:18:51.760 align:start position:0% >> did I buy that one yet? I know I wanted 00:18:51.760 --> 00:18:53.669 align:start position:0% >> did I buy that one yet? I know I wanted to.<00:18:52.080> Do<00:18:52.240> I<00:18:52.320> have<00:18:52.400> a<00:18:52.559> copy<00:18:52.960> on<00:18:53.039> my<00:18:53.200> shelf?<00:18:53.360> And<00:18:53.520> so 00:18:53.669 --> 00:18:53.679 align:start position:0% to. Do I have a copy on my shelf? And so 00:18:53.679 --> 00:18:54.950 align:start position:0% to. Do I have a copy on my shelf? And so I<00:18:53.760> can<00:18:53.840> be<00:18:54.000> at<00:18:54.080> the<00:18:54.160> bookstore<00:18:54.559> and<00:18:54.720> just<00:18:54.880> pull 00:18:54.950 --> 00:18:54.960 align:start position:0% I can be at the bookstore and just pull 00:18:54.960 --> 00:18:56.950 align:start position:0% I can be at the bookstore and just pull it<00:18:55.039> up<00:18:55.200> and<00:18:55.280> go,<00:18:55.360> "Ah,<00:18:56.160> it's<00:18:56.400> on<00:18:56.559> my<00:18:56.720> shelf 00:18:56.950 --> 00:18:56.960 align:start position:0% it up and go, "Ah, it's on my shelf 00:18:56.960 --> 00:18:59.350 align:start position:0% it up and go, "Ah, it's on my shelf already.<00:18:57.520> Sweet.<00:18:58.080> Don't<00:18:58.240> need<00:18:58.400> to<00:18:58.559> reby<00:18:58.880> it." 00:18:59.350 --> 00:18:59.360 align:start position:0% already. Sweet. Don't need to reby it." 00:18:59.360 --> 00:19:01.830 align:start position:0% already. Sweet. Don't need to reby it." >> Yeah.<00:18:59.679> Well,<00:19:00.240> Neilie<00:19:00.799> sounds<00:19:01.120> interesting.<00:19:01.520> I 00:19:01.830 --> 00:19:01.840 align:start position:0% >> Yeah. Well, Neilie sounds interesting. I 00:19:01.840 --> 00:19:04.310 align:start position:0% >> Yeah. Well, Neilie sounds interesting. I I<00:19:02.160> uh<00:19:02.240> I'd<00:19:02.559> experimented<00:19:03.039> with<00:19:03.280> grossy<00:19:03.919> in<00:19:04.160> the 00:19:04.310 --> 00:19:04.320 align:start position:0% I uh I'd experimented with grossy in the 00:19:04.320 --> 00:19:05.590 align:start position:0% I uh I'd experimented with grossy in the past.<00:19:04.640> I<00:19:04.880> think<00:19:04.960> that<00:19:05.120> was<00:19:05.200> what<00:19:05.360> they<00:19:05.440> called 00:19:05.590 --> 00:19:05.600 align:start position:0% past. I think that was what they called 00:19:05.600 --> 00:19:09.190 align:start position:0% past. I think that was what they called that<00:19:05.760> one.<00:19:06.160> G<00:19:06.320> R<00:19:06.480> O<00:19:06.880> C<00:19:07.120> Y.<00:19:07.840> Um<00:19:08.720> sounds<00:19:08.880> like<00:19:08.960> it's 00:19:09.190 --> 00:19:09.200 align:start position:0% that one. G R O C Y. Um sounds like it's 00:19:09.200 --> 00:19:10.390 align:start position:0% that one. G R O C Y. Um sounds like it's interesting<00:19:09.520> because<00:19:09.840> it's<00:19:10.080> probably<00:19:10.240> a 00:19:10.390 --> 00:19:10.400 align:start position:0% interesting because it's probably a 00:19:10.400 --> 00:19:12.230 align:start position:0% interesting because it's probably a little<00:19:10.480> bit<00:19:10.640> more<00:19:10.799> aligned<00:19:11.200> for<00:19:11.840> what<00:19:12.080> you 00:19:12.230 --> 00:19:12.240 align:start position:0% little bit more aligned for what you 00:19:12.240 --> 00:19:13.510 align:start position:0% little bit more aligned for what you just<00:19:12.400> want<00:19:12.480> to<00:19:12.559> do<00:19:12.720> at<00:19:12.880> your<00:19:13.039> house,<00:19:13.200> which<00:19:13.440> is 00:19:13.510 --> 00:19:13.520 align:start position:0% just want to do at your house, which is 00:19:13.520 --> 00:19:14.950 align:start position:0% just want to do at your house, which is go,<00:19:13.760> you<00:19:13.840> know,<00:19:14.000> hey,<00:19:14.240> I'm<00:19:14.320> I'm<00:19:14.559> looking<00:19:14.720> for 00:19:14.950 --> 00:19:14.960 align:start position:0% go, you know, hey, I'm I'm looking for 00:19:14.960 --> 00:19:16.070 align:start position:0% go, you know, hey, I'm I'm looking for something<00:19:15.039> to<00:19:15.280> make.<00:19:15.440> What<00:19:15.600> do<00:19:15.679> I<00:19:15.840> have<00:19:15.919> the 00:19:16.070 --> 00:19:16.080 align:start position:0% something to make. What do I have the 00:19:16.080 --> 00:19:17.510 align:start position:0% something to make. What do I have the ingredients<00:19:16.480> for?<00:19:16.880> And 00:19:17.510 --> 00:19:17.520 align:start position:0% ingredients for? And 00:19:17.520 --> 00:19:18.950 align:start position:0% ingredients for? And >> let's<00:19:17.840> figure<00:19:18.000> it<00:19:18.160> out.<00:19:18.480> But 00:19:18.950 --> 00:19:18.960 align:start position:0% >> let's figure it out. But 00:19:18.960 --> 00:19:20.390 align:start position:0% >> let's figure it out. But >> well,<00:19:19.120> that<00:19:19.280> and<00:19:19.440> I've<00:19:19.679> gone<00:19:19.840> and<00:19:20.000> typed<00:19:20.240> all 00:19:20.390 --> 00:19:20.400 align:start position:0% >> well, that and I've gone and typed all 00:19:20.400 --> 00:19:22.150 align:start position:0% >> well, that and I've gone and typed all the<00:19:20.559> family<00:19:20.880> recipes<00:19:21.280> into<00:19:21.520> it,<00:19:21.760> too.<00:19:22.000> So 00:19:22.150 --> 00:19:22.160 align:start position:0% the family recipes into it, too. So 00:19:22.160 --> 00:19:23.909 align:start position:0% the family recipes into it, too. So instead<00:19:22.480> of<00:19:22.559> having<00:19:22.799> the<00:19:23.039> little<00:19:23.200> index<00:19:23.600> cards 00:19:23.909 --> 00:19:23.919 align:start position:0% instead of having the little index cards 00:19:23.919 --> 00:19:25.510 align:start position:0% instead of having the little index cards sitting<00:19:24.160> there<00:19:24.320> which<00:19:24.559> are<00:19:24.720> all<00:19:24.960> like<00:19:25.120> faded 00:19:25.510 --> 00:19:25.520 align:start position:0% sitting there which are all like faded 00:19:25.520 --> 00:19:27.669 align:start position:0% sitting there which are all like faded and<00:19:25.679> barely<00:19:26.080> readable<00:19:26.799> at<00:19:27.039> this<00:19:27.280> point<00:19:27.520> like 00:19:27.669 --> 00:19:27.679 align:start position:0% and barely readable at this point like 00:19:27.679 --> 00:19:29.190 align:start position:0% and barely readable at this point like they're<00:19:27.919> digitally<00:19:28.400> kept<00:19:28.640> so<00:19:28.799> I<00:19:28.960> can<00:19:29.039> give 00:19:29.190 --> 00:19:29.200 align:start position:0% they're digitally kept so I can give 00:19:29.200 --> 00:19:30.630 align:start position:0% they're digitally kept so I can give them<00:19:29.280> to<00:19:29.440> my<00:19:29.600> kids<00:19:29.840> someday<00:19:30.080> and<00:19:30.320> then<00:19:30.480> they 00:19:30.630 --> 00:19:30.640 align:start position:0% them to my kids someday and then they 00:19:30.640 --> 00:19:32.470 align:start position:0% them to my kids someday and then they can<00:19:30.720> say<00:19:30.960> that<00:19:31.120> was<00:19:31.200> a<00:19:31.360> great<00:19:31.600> recipe<00:19:32.000> or<00:19:32.320> I'm 00:19:32.470 --> 00:19:32.480 align:start position:0% can say that was a great recipe or I'm 00:19:32.480 --> 00:19:33.669 align:start position:0% can say that was a great recipe or I'm never<00:19:32.640> going<00:19:32.720> to<00:19:32.799> make<00:19:32.960> that<00:19:33.120> again.<00:19:33.280> I<00:19:33.440> hated 00:19:33.669 --> 00:19:33.679 align:start position:0% never going to make that again. I hated 00:19:33.679 --> 00:19:35.350 align:start position:0% never going to make that again. I hated it<00:19:33.840> when<00:19:34.000> my<00:19:34.160> mom<00:19:34.240> and<00:19:34.400> dad<00:19:34.640> made<00:19:34.799> that.<00:19:35.200> Which 00:19:35.350 --> 00:19:35.360 align:start position:0% it when my mom and dad made that. Which 00:19:35.360 --> 00:19:37.990 align:start position:0% it when my mom and dad made that. Which is<00:19:35.520> fine.<00:19:36.160> That's<00:19:36.400> life.<00:19:37.200> But<00:19:37.360> anyway,<00:19:37.679> yeah, 00:19:37.990 --> 00:19:38.000 align:start position:0% is fine. That's life. But anyway, yeah, 00:19:38.000 --> 00:19:39.669 align:start position:0% is fine. That's life. But anyway, yeah, please<00:19:38.240> again<00:19:38.559> do<00:19:38.720> run<00:19:38.880> your<00:19:39.039> apps.<00:19:39.360> I<00:19:39.520> will 00:19:39.669 --> 00:19:39.679 align:start position:0% please again do run your apps. I will 00:19:39.679 --> 00:19:41.430 align:start position:0% please again do run your apps. I will put<00:19:39.760> a<00:19:39.919> quick<00:19:40.080> bug<00:19:40.320> out<00:19:40.480> to<00:19:40.720> folks<00:19:40.960> though.<00:19:41.280> So 00:19:41.430 --> 00:19:41.440 align:start position:0% put a quick bug out to folks though. So 00:19:41.440 --> 00:19:42.950 align:start position:0% put a quick bug out to folks though. So we<00:19:41.679> don't<00:19:41.760> get<00:19:42.080> typically<00:19:42.480> a<00:19:42.720> lot<00:19:42.799> of 00:19:42.950 --> 00:19:42.960 align:start position:0% we don't get typically a lot of 00:19:42.960 --> 00:19:44.630 align:start position:0% we don't get typically a lot of community<00:19:43.360> involvement<00:19:43.840> on<00:19:44.080> the<00:19:44.240> development 00:19:44.630 --> 00:19:44.640 align:start position:0% community involvement on the development 00:19:44.640 --> 00:19:46.789 align:start position:0% community involvement on the development side<00:19:44.799> of<00:19:44.960> trz<00:19:45.520> you<00:19:45.600> know<00:19:45.760> middleware<00:19:46.240> UI.<00:19:46.640> We 00:19:46.789 --> 00:19:46.799 align:start position:0% side of trz you know middleware UI. We 00:19:46.799 --> 00:19:48.710 align:start position:0% side of trz you know middleware UI. We don't<00:19:46.960> see<00:19:47.039> as<00:19:47.280> much<00:19:47.440> engagement<00:19:47.840> there<00:19:48.480> with 00:19:48.710 --> 00:19:48.720 align:start position:0% don't see as much engagement there with 00:19:48.720 --> 00:19:50.789 align:start position:0% don't see as much engagement there with the<00:19:48.880> exception<00:19:49.200> being<00:19:49.360> the<00:19:49.600> apps<00:19:49.919> catalog. 00:19:50.789 --> 00:19:50.799 align:start position:0% the exception being the apps catalog. 00:19:50.799 --> 00:19:52.549 align:start position:0% the exception being the apps catalog. That's<00:19:50.960> an<00:19:51.200> area<00:19:51.360> we<00:19:51.600> do<00:19:51.760> see<00:19:51.840> a<00:19:52.000> lot<00:19:52.160> of 00:19:52.549 --> 00:19:52.559 align:start position:0% That's an area we do see a lot of 00:19:52.559 --> 00:19:53.990 align:start position:0% That's an area we do see a lot of community<00:19:52.880> engagement<00:19:53.280> on<00:19:53.520> and<00:19:53.679> that's<00:19:53.840> a 00:19:53.990 --> 00:19:54.000 align:start position:0% community engagement on and that's a 00:19:54.000 --> 00:19:55.350 align:start position:0% community engagement on and that's a good<00:19:54.080> thing<00:19:54.240> and<00:19:54.400> I<00:19:54.559> want<00:19:54.640> to<00:19:54.799> encourage<00:19:55.120> more 00:19:55.350 --> 00:19:55.360 align:start position:0% good thing and I want to encourage more 00:19:55.360 --> 00:19:57.350 align:start position:0% good thing and I want to encourage more of<00:19:55.520> that.<00:19:55.840> So<00:19:56.320> if<00:19:56.559> you're<00:19:56.799> looking<00:19:56.960> for<00:19:57.120> a<00:19:57.280> way 00:19:57.350 --> 00:19:57.360 align:start position:0% of that. So if you're looking for a way 00:19:57.360 --> 00:19:59.029 align:start position:0% of that. So if you're looking for a way to<00:19:57.600> get<00:19:57.679> involved<00:19:58.080> and<00:19:58.320> kind<00:19:58.480> of<00:19:58.640> be<00:19:58.799> part<00:19:58.960> of 00:19:59.029 --> 00:19:59.039 align:start position:0% to get involved and kind of be part of 00:19:59.039 --> 00:20:00.870 align:start position:0% to get involved and kind of be part of the<00:19:59.200> open<00:19:59.520> source<00:19:59.760> ecosystem,<00:20:00.400> the<00:20:00.559> app 00:20:00.870 --> 00:20:00.880 align:start position:0% the open source ecosystem, the app 00:20:00.880 --> 00:20:02.710 align:start position:0% the open source ecosystem, the app catalog<00:20:01.360> is<00:20:01.600> a<00:20:01.760> great<00:20:02.000> way<00:20:02.080> to<00:20:02.320> kind<00:20:02.480> of<00:20:02.559> dip 00:20:02.710 --> 00:20:02.720 align:start position:0% catalog is a great way to kind of dip 00:20:02.720 --> 00:20:05.750 align:start position:0% catalog is a great way to kind of dip your<00:20:02.880> toe<00:20:03.200> in<00:20:03.840> and<00:20:04.320> help<00:20:04.559> out.<00:20:04.880> Like<00:20:05.039> if<00:20:05.280> you 00:20:05.750 --> 00:20:05.760 align:start position:0% your toe in and help out. Like if you 00:20:05.760 --> 00:20:07.270 align:start position:0% your toe in and help out. Like if you the<00:20:05.919> thing<00:20:06.080> is<00:20:06.320> there's<00:20:06.559> just<00:20:06.720> frankly<00:20:07.120> too 00:20:07.270 --> 00:20:07.280 align:start position:0% the thing is there's just frankly too 00:20:07.280 --> 00:20:09.430 align:start position:0% the thing is there's just frankly too many<00:20:07.520> apps<00:20:08.000> out<00:20:08.240> there<00:20:08.400> in<00:20:08.559> the<00:20:08.720> wild<00:20:09.120> out<00:20:09.280> of 00:20:09.430 --> 00:20:09.440 align:start position:0% many apps out there in the wild out of 00:20:09.440 --> 00:20:10.870 align:start position:0% many apps out there in the wild out of the<00:20:09.600> millions<00:20:09.919> of<00:20:10.080> potential<00:20:10.480> Docker 00:20:10.870 --> 00:20:10.880 align:start position:0% the millions of potential Docker 00:20:10.880 --> 00:20:13.750 align:start position:0% the millions of potential Docker containers<00:20:11.760> and<00:20:12.000> we<00:20:12.240> cannot<00:20:12.640> possibly<00:20:13.200> even 00:20:13.750 --> 00:20:13.760 align:start position:0% containers and we cannot possibly even 00:20:13.760 --> 00:20:15.510 align:start position:0% containers and we cannot possibly even with<00:20:14.000> all<00:20:14.160> the<00:20:14.320> resources<00:20:14.720> I<00:20:14.960> could<00:20:15.120> throw<00:20:15.360> at 00:20:15.510 --> 00:20:15.520 align:start position:0% with all the resources I could throw at 00:20:15.520 --> 00:20:17.669 align:start position:0% with all the resources I could throw at it<00:20:16.240> get<00:20:16.400> them<00:20:16.559> all<00:20:16.720> in<00:20:16.880> the<00:20:17.039> catalog<00:20:17.440> and 00:20:17.669 --> 00:20:17.679 align:start position:0% it get them all in the catalog and 00:20:17.679 --> 00:20:19.190 align:start position:0% it get them all in the catalog and maintain<00:20:18.000> them<00:20:18.240> and<00:20:18.400> all<00:20:18.559> that.<00:20:18.799> it<00:20:18.960> does 00:20:19.190 --> 00:20:19.200 align:start position:0% maintain them and all that. it does 00:20:19.200 --> 00:20:21.029 align:start position:0% maintain them and all that. it does require<00:20:19.520> a<00:20:19.760> larger<00:20:20.080> community<00:20:20.400> to<00:20:20.640> go<00:20:20.799> and 00:20:21.029 --> 00:20:21.039 align:start position:0% require a larger community to go and 00:20:21.039 --> 00:20:23.750 align:start position:0% require a larger community to go and keep<00:20:21.280> a<00:20:21.600> real<00:20:22.400> good<00:20:22.640> and<00:20:22.880> robust<00:20:23.360> set<00:20:23.520> of 00:20:23.750 --> 00:20:23.760 align:start position:0% keep a real good and robust set of 00:20:23.760 --> 00:20:25.669 align:start position:0% keep a real good and robust set of applications<00:20:24.320> available<00:20:24.799> that<00:20:25.120> a<00:20:25.360> lot<00:20:25.440> more 00:20:25.669 --> 00:20:25.679 align:start position:0% applications available that a lot more 00:20:25.679 --> 00:20:27.430 align:start position:0% applications available that a lot more people<00:20:25.840> want<00:20:26.000> to<00:20:26.080> use.<00:20:26.400> So<00:20:26.960> again,<00:20:27.200> it's 00:20:27.430 --> 00:20:27.440 align:start position:0% people want to use. So again, it's 00:20:27.440 --> 00:20:28.950 align:start position:0% people want to use. So again, it's pretty<00:20:27.679> straightforward.<00:20:28.240> It's<00:20:28.480> easy<00:20:28.640> to<00:20:28.799> get 00:20:28.950 --> 00:20:28.960 align:start position:0% pretty straightforward. It's easy to get 00:20:28.960 --> 00:20:30.549 align:start position:0% pretty straightforward. It's easy to get involved<00:20:29.280> and<00:20:29.520> test.<00:20:29.840> We<00:20:30.000> have<00:20:30.159> quite<00:20:30.240> a<00:20:30.400> few 00:20:30.549 --> 00:20:30.559 align:start position:0% involved and test. We have quite a few 00:20:30.559 --> 00:20:32.390 align:start position:0% involved and test. We have quite a few people<00:20:30.720> doing<00:20:30.960> that<00:20:31.200> already.<00:20:31.600> So<00:20:31.919> thank<00:20:32.080> you 00:20:32.390 --> 00:20:32.400 align:start position:0% people doing that already. So thank you 00:20:32.400 --> 00:20:33.669 align:start position:0% people doing that already. So thank you from<00:20:32.640> the<00:20:32.799> bottom<00:20:32.960> of<00:20:33.039> our<00:20:33.200> heart.<00:20:33.520> We 00:20:33.669 --> 00:20:33.679 align:start position:0% from the bottom of our heart. We 00:20:33.679 --> 00:20:35.110 align:start position:0% from the bottom of our heart. We appreciate<00:20:34.080> that<00:20:34.240> and<00:20:34.480> it's<00:20:34.720> welcome<00:20:34.960> to 00:20:35.110 --> 00:20:35.120 align:start position:0% appreciate that and it's welcome to 00:20:35.120 --> 00:20:37.350 align:start position:0% appreciate that and it's welcome to more.<00:20:35.440> So<00:20:36.000> please<00:20:36.240> hop<00:20:36.480> on<00:20:36.720> there.<00:20:37.039> It's<00:20:37.200> on 00:20:37.350 --> 00:20:37.360 align:start position:0% more. So please hop on there. It's on 00:20:37.360 --> 00:20:38.870 align:start position:0% more. So please hop on there. It's on the<00:20:37.440> GitHub<00:20:37.840> repo<00:20:38.159> which<00:20:38.320> we<00:20:38.480> linked<00:20:38.720> to 00:20:38.870 --> 00:20:38.880 align:start position:0% the GitHub repo which we linked to 00:20:38.880 --> 00:20:41.029 align:start position:0% the GitHub repo which we linked to previously.<00:20:39.520> You're<00:20:39.760> welcome<00:20:40.000> to<00:20:40.400> uh<00:20:40.799> get 00:20:41.029 --> 00:20:41.039 align:start position:0% previously. You're welcome to uh get 00:20:41.039 --> 00:20:43.029 align:start position:0% previously. You're welcome to uh get engaged,<00:20:41.600> open<00:20:41.840> poll<00:20:42.080> requests,<00:20:42.400> or<00:20:42.640> at<00:20:42.799> very 00:20:43.029 --> 00:20:43.039 align:start position:0% engaged, open poll requests, or at very 00:20:43.039 --> 00:20:44.870 align:start position:0% engaged, open poll requests, or at very minimum<00:20:43.679> get<00:20:43.919> involved<00:20:44.240> by<00:20:44.400> just<00:20:44.559> reviewing 00:20:44.870 --> 00:20:44.880 align:start position:0% minimum get involved by just reviewing 00:20:44.880 --> 00:20:46.710 align:start position:0% minimum get involved by just reviewing the<00:20:45.039> incoming<00:20:45.440> poll<00:20:45.760> requests.<00:20:46.080> If<00:20:46.240> a<00:20:46.400> new<00:20:46.480> app 00:20:46.710 --> 00:20:46.720 align:start position:0% the incoming poll requests. If a new app 00:20:46.720 --> 00:20:49.430 align:start position:0% the incoming poll requests. If a new app shows<00:20:46.960> up,<00:20:47.200> test<00:20:47.520> it.<00:20:48.000> Let<00:20:48.159> us<00:20:48.320> know<00:20:48.480> it<00:20:48.720> works. 00:20:49.430 --> 00:20:49.440 align:start position:0% shows up, test it. Let us know it works. 00:20:49.440 --> 00:20:51.669 align:start position:0% shows up, test it. Let us know it works. Give<00:20:49.679> us<00:20:49.840> feedback<00:20:50.400> or<00:20:50.880> suggest<00:20:51.280> if<00:20:51.440> there's 00:20:51.669 --> 00:20:51.679 align:start position:0% Give us feedback or suggest if there's 00:20:51.679 --> 00:20:53.830 align:start position:0% Give us feedback or suggest if there's things<00:20:51.760> we<00:20:51.919> can<00:20:52.080> do<00:20:52.159> to<00:20:52.320> improve<00:20:52.559> it. 00:20:53.830 --> 00:20:53.840 align:start position:0% things we can do to improve it. 00:20:53.840 --> 00:20:56.950 align:start position:0% things we can do to improve it. >> Excellent.<00:20:54.960> Yeah.<00:20:55.679> Well,<00:20:56.320> I<00:20:56.480> think<00:20:56.559> that<00:20:56.799> I 00:20:56.950 --> 00:20:56.960 align:start position:0% >> Excellent. Yeah. Well, I think that I 00:20:56.960 --> 00:20:58.310 align:start position:0% >> Excellent. Yeah. Well, I think that I think<00:20:57.039> that<00:20:57.280> about<00:20:57.520> wraps<00:20:57.760> it<00:20:57.840> up<00:20:58.000> for<00:20:58.159> our 00:20:58.310 --> 00:20:58.320 align:start position:0% think that about wraps it up for our 00:20:58.320 --> 00:20:59.590 align:start position:0% think that about wraps it up for our show<00:20:58.480> today.<00:20:58.799> We're<00:20:58.960> keeping<00:20:59.120> it<00:20:59.280> a<00:20:59.520> little 00:20:59.590 --> 00:20:59.600 align:start position:0% show today. We're keeping it a little 00:20:59.600 --> 00:21:01.270 align:start position:0% show today. We're keeping it a little bit<00:20:59.760> brief<00:21:00.080> and<00:21:00.480> uh<00:21:00.640> you<00:21:00.720> know,<00:21:00.880> hopefully 00:21:01.270 --> 00:21:01.280 align:start position:0% bit brief and uh you know, hopefully 00:21:01.280 --> 00:21:03.029 align:start position:0% bit brief and uh you know, hopefully you're<00:21:01.520> okay<00:21:01.679> with<00:21:01.919> that<00:21:02.080> and<00:21:02.400> you<00:21:02.640> stuck<00:21:02.880> with 00:21:03.029 --> 00:21:03.039 align:start position:0% you're okay with that and you stuck with 00:21:03.039 --> 00:21:05.350 align:start position:0% you're okay with that and you stuck with us<00:21:03.200> through<00:21:03.440> to<00:21:03.600> the<00:21:03.760> end<00:21:03.919> here.<00:21:04.559> So,<00:21:05.120> thanks 00:21:05.350 --> 00:21:05.360 align:start position:0% us through to the end here. So, thanks 00:21:05.360 --> 00:21:07.350 align:start position:0% us through to the end here. So, thanks again<00:21:05.679> everybody<00:21:05.919> for<00:21:06.159> tuning<00:21:06.400> in.<00:21:06.720> Uh<00:21:07.039> again, 00:21:07.350 --> 00:21:07.360 align:start position:0% again everybody for tuning in. Uh again, 00:21:07.360 --> 00:21:10.310 align:start position:0% again everybody for tuning in. Uh again, so<00:21:07.520> the<00:21:07.760> Trunaz<00:21:08.400> 2510.2.1 00:21:10.310 --> 00:21:10.320 align:start position:0% so the Trunaz 2510.2.1 00:21:10.320 --> 00:21:13.110 align:start position:0% so the Trunaz 2510.2.1 hotfix<00:21:11.200> is<00:21:11.520> uh<00:21:11.679> out<00:21:11.919> now.<00:21:12.320> Go<00:21:12.480> ahead<00:21:12.640> and<00:21:12.960> uh 00:21:13.110 --> 00:21:13.120 align:start position:0% hotfix is uh out now. Go ahead and uh 00:21:13.120 --> 00:21:15.669 align:start position:0% hotfix is uh out now. Go ahead and uh give<00:21:13.280> that<00:21:13.440> a<00:21:14.320> download,<00:21:15.039> patch<00:21:15.360> up<00:21:15.520> your 00:21:15.669 --> 00:21:15.679 align:start position:0% give that a download, patch up your 00:21:15.679 --> 00:21:17.909 align:start position:0% give that a download, patch up your system<00:21:16.000> again<00:21:16.559> if<00:21:16.799> you<00:21:16.960> especially<00:21:17.440> you<00:21:17.679> were, 00:21:17.909 --> 00:21:17.919 align:start position:0% system again if you especially you were, 00:21:17.919 --> 00:21:19.830 align:start position:0% system again if you especially you were, you<00:21:18.080> know,<00:21:18.640> losing<00:21:18.960> your<00:21:19.120> network<00:21:19.440> team<00:21:19.600> on 00:21:19.830 --> 00:21:19.840 align:start position:0% you know, losing your network team on 00:21:19.840 --> 00:21:21.669 align:start position:0% you know, losing your network team on the<00:21:19.919> last<00:21:20.080> one.<00:21:20.559> Uh<00:21:20.799> give<00:21:20.960> it<00:21:21.039> a<00:21:21.200> shot<00:21:21.360> and<00:21:21.520> you 00:21:21.669 --> 00:21:21.679 align:start position:0% the last one. Uh give it a shot and you 00:21:21.679 --> 00:21:23.669 align:start position:0% the last one. Uh give it a shot and you should<00:21:21.840> be<00:21:21.919> good<00:21:22.080> to<00:21:22.240> go<00:21:22.400> this<00:21:22.640> time.<00:21:23.360> Uh 00:21:23.669 --> 00:21:23.679 align:start position:0% should be good to go this time. Uh 00:21:23.679 --> 00:21:25.190 align:start position:0% should be good to go this time. Uh please<00:21:23.919> again<00:21:24.159> do<00:21:24.320> those<00:21:24.559> usual<00:21:24.799> YouTube 00:21:25.190 --> 00:21:25.200 align:start position:0% please again do those usual YouTube 00:21:25.200 --> 00:21:26.630 align:start position:0% please again do those usual YouTube things.<00:21:25.520> Although<00:21:25.760> if<00:21:26.080> uh<00:21:26.240> Chris<00:21:26.400> is 00:21:26.630 --> 00:21:26.640 align:start position:0% things. Although if uh Chris is 00:21:26.640 --> 00:21:28.470 align:start position:0% things. Although if uh Chris is threatening<00:21:26.960> me<00:21:27.120> with<00:21:27.200> a<00:21:27.440> new<00:21:27.600> laptop,<00:21:28.159> I 00:21:28.470 --> 00:21:28.480 align:start position:0% threatening me with a new laptop, I 00:21:28.480 --> 00:21:30.230 align:start position:0% threatening me with a new laptop, I might<00:21:28.720> not<00:21:28.880> necessarily<00:21:29.440> complain<00:21:29.840> if<00:21:30.000> he's 00:21:30.230 --> 00:21:30.240 align:start position:0% might not necessarily complain if he's 00:21:30.240 --> 00:21:31.510 align:start position:0% might not necessarily complain if he's going to<00:21:30.320> give<00:21:30.480> me<00:21:30.640> one<00:21:30.799> of<00:21:30.880> those<00:21:31.039> anyways. 00:21:31.510 --> 00:21:31.520 align:start position:0% going to give me one of those anyways. 00:21:31.520 --> 00:21:33.110 align:start position:0% going to give me one of those anyways. But<00:21:31.919> uh<00:21:32.080> do<00:21:32.240> give<00:21:32.400> us<00:21:32.559> that<00:21:32.720> like<00:21:32.880> and 00:21:33.110 --> 00:21:33.120 align:start position:0% But uh do give us that like and 00:21:33.120 --> 00:21:35.190 align:start position:0% But uh do give us that like and subscribe<00:21:33.600> regardless.<00:21:34.400> Uh<00:21:34.720> feel<00:21:34.880> free<00:21:35.039> to 00:21:35.190 --> 00:21:35.200 align:start position:0% subscribe regardless. Uh feel free to 00:21:35.200 --> 00:21:37.190 align:start position:0% subscribe regardless. Uh feel free to sound<00:21:35.440> off<00:21:35.600> in<00:21:35.760> the<00:21:35.919> comments<00:21:36.240> below<00:21:36.799> uh<00:21:36.960> over 00:21:37.190 --> 00:21:37.200 align:start position:0% sound off in the comments below uh over 00:21:37.200 --> 00:21:39.750 align:start position:0% sound off in the comments below uh over on<00:21:37.360> our<00:21:37.520> forums<00:21:37.919> at<00:21:38.080> forums.trunaz.com. 00:21:39.750 --> 00:21:39.760 align:start position:0% on our forums at forums.trunaz.com. 00:21:39.760 --> 00:21:43.590 align:start position:0% on our forums at forums.trunaz.com. Uh,<00:21:40.080> shoot<00:21:40.240> us<00:21:40.400> an<00:21:40.640> email<00:21:40.960> at<00:21:41.280> t3trunaz.com. 00:21:43.590 --> 00:21:43.600 align:start position:0% Uh, shoot us an email at t3trunaz.com. 00:21:43.600 --> 00:21:45.750 align:start position:0% Uh, shoot us an email at t3trunaz.com. And,<00:21:44.000> uh,<00:21:44.159> thank<00:21:44.240> you<00:21:44.400> again<00:21:44.640> for<00:21:44.799> tuning<00:21:45.039> in. 00:21:45.750 --> 00:21:45.760 align:start position:0% And, uh, thank you again for tuning in. 00:21:45.760 --> 00:21:50.200 align:start position:0% And, uh, thank you again for tuning in. Chris<00:21:46.000> and<00:21:46.159> I<00:21:46.400> will<00:21:46.720> see<00:21:46.799> you<00:21:46.960> next<00:21:47.200> time.