Good evening. I am the only Speaker between you and dinner So if that got everybody quiet Awesome. Good evening. My name is John King. I have the privilege of serving as vice president for student life at Roger Williams I'm in my 20th year and coach Amanda for whatever reason has asked me to kick off tonight This is among our most beloved events bringing together current student athletes our successful alumni and family members in a fun Competitive environment wasn't today fun Possibly the wettest captain's cup ever. I'm glad everybody brought balers. That was a good move Amanda If you are a new student and family member You are joining a special tradition and a culture that is second to none We are indebted to our longest standing alumni sailors who have stewarded this event for decades and for coach Amanda for Creating and sustaining such a strong and positive culture that emphasizes the engagement and networking of alumni and Parents along with sailing excellence This was an exciting and busy summer in the sailing center and on our waterfront and Amanda asked me to tell you a little bit about it Roger Williams served as the host site in support of US sailing and the 2023 youth Championships during the last week of June Sailors and family members from across the country converged on campus and in Bristol for more than a week Naturally our waterfront and campus facilities showed well US sailing turned our lower field beneath the rugby site into site headquarters with a large tent The sailing center served as a hospitality and viewing center and family members remarked It was one of the best venues they had ever experienced Most impressively it seemed that no matter where the sailors and family members hail from They knew one of you one of our current sailors or more recent alumni They knew coach Amanda and they were very much aware that the Hawks are Paranaly one of the top sailing teams in the country This year's youth champs served also as a qualifier for world sailings 2023 youth world championships and there were seven racing classes Just three week later our waterfront and facilities served as the venue for the US Junior women single-handed and double-handed championships for young women ages 13 to 18 With no private coaching allowed US sailing coaches were provided to enhance the experience sailing skills competitors and networking within this group of athletes I'm not leaving the podium tonight without taking the opportunity to salute the sailing prowess of our very own coach Callahan who qualified for Who qualified for and who will compete in the pan-american games? Representing the United States along with our outstanding junior sailor Mateo Dale Representing st. Croix. Let's give it up for Mateo They start next weekend in Chile, which is amazing Amanda never talks about her own sailing She never talks about herself She just sails and excels in the Sunfish category and because Sunfish is not an Olympic class option The pan-american games are actually one of the top International showcases and venues for that championship So once again, please join me in raising the roof again Supporting Amanda and Mateo at the pan-american games in closing. It does not get better than this This is an incredible event the sense of belonging the sense of community within this crowd the traditions and How you feel about each other in this tradition? It's phenomenal every college student every family should be able to experience something like this But few do you do so enjoy tonight enjoy captain's cup and we're off to dinner. Thank you Thank you everybody for coming We're gonna kick off the dinner part with a little video To thank everybody who has made our our fleet happen and Hopefully everybody can hear it Sailing is all about being in the community and with Roger William sailing team. I found my people and my family I've gotten so many great opportunities and gotten to meet so many amazing people through sailing that naturally I just want to continue it at Roger Williams University. It's always been something I've been extremely passionate about from the time I was seven years old The new fleet has enabled our team to actively compete at the highest level of region sailing and it's just been We've been so blessed this year to have this Thank you guys and this wonderful new fleet We really feel blessed to have received it and it's really added a lot to our sailing program here at Roger Williams It really means the world to us. We're so excited to be able to sail these boats every day Thank you guys so much. We are looking forward to a phenomenal season and we cannot have done it without you Thank you! I just want to say that Those are our captains Carly who's down at St. Mary's today And Claire Buckley who's here in Hank I didn't give them any heads up that they were gonna film that that day I think they did a really great job and it was very much from the heart, so Great work everybody Hold on for one second. I really can't see from you so I have the privilege every year of Recognizing an alum we have a bunch of former winners a few anyways former winners of the alumni award in the house Mack is one of them Maybe he's he might be the only one anyways We're really fortunate to have an actively engaged Set of alumni who come back to this regatta every year who when I call them on day of giving they They heed the call When I call them and I'm saying hey, I'm sailing a regatta in Florida. Can I stay on your couch? They're like absolutely I get to see them at regattas Outside of college sailing all the time. It's so great to have alums that are like I said really involved with the program and We like to recognize them at the captain's cup the person who's winning the alumni award this year is not here And in fact, they're the parents of an alum, but I wanted to recognize them As I mentioned them earlier today. Yannis mentioned them earlier today the McGraw family who made the lead gifts to make our fleet possible and As has been stated many times today Many of us not everybody but many of us in this room were introduced to sailing through our family members and that love of sailing is Passed down from generation to generation for most of our sailors Those formative sailing experiences end up turning into passion and that passion literally fuels What we do every day on the water that passion gets you through practice in February when it's really really cold When it's maybe snowing and maybe when you're on the far side of the golf course and you have a westerly blown at you Donald McGraw Loved sailing and he passed that love of sailing down to his sons Peter who graduated in 76 from Roger Williams Josh his brother who was a parent of a 2005 grad David parent of a 2010 grad and their other brother Robin The McGraws also passed down their sail number number 44 It had such significance to the McGraw family and particularly for David He petitioned he petitioned the postal service in Osterville to get his address changed to number 44 like that's how serious they were about that sail number And how much it means to them and that was a little bit behind the design for this year's logo Along with their love of sailing the McGraws also have a love of Roger Williams as I mentioned Peter as an alum Liz is a 2010 alum Erin Oh five alum all proud graduates of Roger Williams David the dad of Liz He's also got two other kids, but we'll leave it with Liz He has been our fairy godfather. He's been I got introduced him pretty early on and Every every chance that he's on campus, which is rare, but we get to go grab a lunch come to the sailing Center He regales me with amazing stories about his rides on Sturgis and the folks that he meets along the way But they have truly Made such an indelible mark on our whole entire program as the honest mentioned earlier today They helped us get to the finish line when we were doing the sailing Center campaign In fact this the classroom in the upstairs is named for their dad Donald McGraw again, he handed down that passion that love of sailing and Their lead gifts to this fleet Allowed us to get this new fleet along with the Matthews the Recklers in the hunts and the Levins Outside of their philanthropy and leadership on various boards the Cape Cod Academy the Mystic Sea port just to name a couple As I mentioned David's just like a genuinely great guy, and I really wish that he were here tonight So we could all thank him for their contributions Unfortunately, I have like a family medical situation that one didn't allow them to be here tonight, but He's such a great person I would love for you all to meet him. He's a sensational story teller super down-to-earth a Real pleasure to hang with he's also an expert he he Refurbishes vintage motorcycles. That's his passion. He would he he loves sailing, but he would rather be riding Oh as you can tell that's just one of his bikes. I think that might be his favorite I've seen him and on that bike more than any other bike, but he's an avid rider The McGraw Foundation is focused That's their they're giving arm the McGraw Foundation focused on advancing community efforts in health education and human services they recently named The McGraw distinguished chair and emergency medicine at Brigham and women's they support substance abuse and prevention The spalding rehab adaptive sports centers hospice care on and on their generosity Goes far and wide and we are beyond grateful that their generosity extends to us the David and the McGraw family have made a truly transformative impact on our team and I'm delighted to recognize them in there even though They're not here tonight and Thank You David. I will Kate and I will have lunch with him when I get back from Chile But I just wanted you guys to know that we have a fairy godfather out there who? Loves and as I mentioned earlier today, you know continues to support what we're doing believes in what we're doing and We we just love them to pieces so anyways at this point I would like to welcome to the podium our Race committee for the day. We have Emmett Neville class of 25 Who is ably assisted Dom? I see you hiding back there Dom come on up This is taken yesterday before the rain. We have a small scoring error We thought somebody was meant to be scored OCS, but we will get to that part later We'll start with They cleared themselves evidently Anyways, we'll get right to it. Well first off. I want to Say thank you to everybody. It was a great day nice and warm and dry I Had a great time out there everybody was super super great super nice Great racing not too much contact, which was good Not that I saw apparently a lot at the Woodward mark, but All right. Yeah, so that's all we got We're gonna start off with the family division the best division By far. They were the only ones who weren't over every single time All right, so Spot them up. We had Jacob and Jersey Give it up Keith and Zach, I'm just gonna rip through them now. We can clap at the end Tim and will Leo and Frankie Karen and Drew Kailin Casey and Cameron Jack Roman and Kate Roman Alyssa and Tim Jay and Tavia Katie and Ethan Eric and Oliver now we're getting to our top three. So in third we have Joanne and Addie in oh If the top three has got a come up here, we've got a Some wonderful mugs for you. Are we gonna have them all stay up here? congratulations guys in Second place we had Peter and Mary and finally In first place Aiden and Darcy give it up first Like to thank my parents for coming. There's a first captain's cup This was my mom's first time ever sailing FJ. So I thought it was a good experience for Maybe one captain's cup she'll she'll drive an all crew and we can we can run it back So I also like to thank Emmett and Dom for being raised committee. I was it last year So I know how it goes a little bit of a burden, but I think they did great Thank you everybody.   What do we hit Leonard and Ruby? Yeah, fourth place Claire and Mike Set third place Katie and Jeff and Betsy. Oh third place. Come on up. Oh Yes, well elite we got to get the picture in second place We've got Hank and Katie give it up and In first place we have Marin and Rob. I would like to thank my mom and dad for coming and Yeah, I don't really have anything and my sister And it was a fun day today Congratulations. All right now. We are going on to our elite siblings In sixth we've got Max and Matthew Then we've got Olivia and Lexi Julian and Luke Ethan and Wyatt third place Very very close racing in our elite siblings of vision it is what it It sounds like Congratulations, you gotta get Second we've got Mike and Katie It's worth noting that Katie fired her dad after they ended up in the water three times last year and And even though she thought she was safe with her brother they ended up capsizing in the last race and Finally to end off our elite siblings. You've got Joey and Lucy By a large margin might I add they had a big buffer there Congratulations I'd like to thank my parents and my brother for coming out for another race against us this weekend. Oh And obviously Riley You'll see it you'll you'll hear it in a second here, so we've got a slight slight scoring issue here Sorry about that guys It's too late for that now All right, we're just going with it. All right guys All right This is a big one. All right, should I do them all? All right starting from bottom up Matthew and Dawson Michael and Madeline Mike and Claudia Hockey and Riley Chuck and Becky Bob and Maggie Michaela and Taryn Kelsey and Chris I tried I didn't see the eye Riley and Molly Martim and BB. Oh Oh, oh actually I didn't say that Forgot it forget I said that Mac and Abby Connor and Jennifer Cameron and Grace Ed and Megan George and Cal Johnny and Anika.  Is anybody here to represent them? In second place we have Chase and Julia Give it up for them These guys last year did just so well in the elite siblings of vision that they have now been promoted to Honorary alone Julia's not here. Yeah, congratulations Due to the scoring we had a little bit of scoring, you know, but In first place we have Martim and BB. Congratulations guys We did do a circle. What do you want to say? I just want to say it's a fantastic event start your Third fourth event. This is my second. I just want to say thank you so much to Amanda for hosting this event Fantastic so many new boats. We're lucky to have these boats. Remember my freshman year. We had six brand new 420s and This is a pleasure to have like 18 fj's fantastic great program very happy all the alums here Really happy to have these boats.  Whoo now The moment we've all been waiting for the crash cup the crash cup this year goes to someone who I Don't know if you guys if you were here last year. He stood up in front of everybody before we went out racing day one and and Told us all how we needed to be very very careful with the old boats Not to hit anything. We needed to keep them nice Keep them clean. No more dings This year he did not make that speech Instead he decides to Probably do quite the opposite and just I think hit if it was on the water he tried to hit it and It's very disappointing To see from from him, you know, one would think it's new fleet of boats after that wonderful speech last year We'd have a little bit of respect for all the new gelcoat, but I guess not so without further ado This year's crash cup goes to Mac not Abby Abby was very clear that this was not on her It rests solely with Mac Forgot to say this at the beginning, but I also have to thank Dom so much for helping me out today Give it up for Dom. I Would not have been able to do my job so well if it wasn't for him, so Thank you everybody and enjoy the rest of your evening It's gonna give everybody a quick kind of rundown about where we are what we're doing how things are going Danny Petrovic is good for the record. It's they're kind of a funny thing Right, like highlights are like the Instagram version of what's actually going on Right, like you just show the shiny glossy things that happen and truth be told we had a really good year last year We did time spring rolled around we were races. Perhaps we didn't see as much adversity as we needed to and I think by all accounts We underperformed at nationals. I don't think that is unfair to say As I said, it's easy to talk about unicorns and rainbows It's less hard to talk about the things that didn't go according to plan As you know, we're always trying to compete at the highest level of college sailing And sometimes it doesn't go the way you want it to go We discovered at nationals a little too late that maybe we weren't the team that we thought we were Spent the whole summer thinking about why that was. I think everybody who was there at nationals also Did a lot of reflection at the end of the day we ended up 17th out of 18 at the women's semi-final, which was not disappointing at all. We started Pretty much a whole new team at that semi-final and they had some success and built some confidence at that event I think. Then we got to team racing nationals and we ended up finishing sixth in a three-way a three-way tie with Yale and Dartmouth After some after-hours shenanigans that Brown pulled to like slide on to the podium One one race behind them very very close racing But we had we had bigger goals in that and we we struggled pulling it together after tough losses and then a Devastating 10th out of 18th at the semi-finals and not moving on to the finals We were a much better team than how we performed at the end And I think a lot of us carried Well, I know I did carried a lot of everyone's really quiet Beauty of sports, right? You have the opportunity to fail and we didn't fail enough in the season to learn the lessons that we needed to learn And we have preached that in years past. We need to lose races You learn more from the losses than you do from the wins And so the lessons taking away from taking away from last year is how do we build a better team? How do we have stronger communication? How do we lean on each other a little bit more and those are things that I think have been fueling us quite a bit this season Or at least for me anyways You know in years past we've done team dinners or we've gone to play laser tag And I said hey, we're not gonna do that stuff We're gonna do a different type of team building right this year so that when we get to nationals And we were coming off the water off of a pretty tough loss We're gonna be able to turn to each other and say hey, we got this. Let's build each other back up. So That's what we've been doing this spring and this fall I think it's been motivating rather than debilitating and so now we'll get to the highlights of this season the Instagram version but also the real version As John King mentioned earlier. Oh, he didn't mention it But he mentioned Matthew and I are going to the Pan Am games But also Matthew is was just selected to go the single-handed nationals later on this season To not mention the highlights from sort of last spring Molly Matthews who's here was named as an ICSA All-American crew and just last yeah Just last night like a whole I don't know how many months later Just last night nine sailors from the team were named to the ICSA All-academic team and they are all in the room tonight, which is awesome We have Hank Bailey will Bailey Katie Ben-ha, Aiden, Cameron Wood and Grace Woodcock all made up the all-academic team and a huge boost Stephanie Hudson who's coming to practice coach practice once a week and is working specifically with our women's team to get them firing Which we're psyched about They just finished third at the Atlantic Coast Tournament last weekend at Brown and coaches. We are delighted We are delighted to welcome back down at St. Mary's at the Atlantic Coast Championship and Earlier today, we're sitting in third. I think they had a tough last set and they're sitting in six So we wish them all the luck going into tomorrow I know they can pull it together. They said it was really quite windy down there a lot of fun for the season So that's a quick snapshot what you see on Instagram is is somewhat of reality and then We're gonna keep plugging away We've got big goals again this year at the beginning of the year I said to the captains we had our preseason meetings set to the to the upperclassmen We're not messing around This is our year to really put it together and we got a lot of good lessons from last year So we're happy to take those forward I wanted to take a take a second to you know in in the captain's cup has been one of our biggest fundraisers of the year and the day of giving I've always like leaned on Riley eager giving him about three minutes notice to come up here and Try pledges to buy new sales or buy trailers for our j-22s or whatever the case is Whatever whatever big thing we're hoping for on our wish list the day of giving with structured a little bit differently and We wanted to I did a lot of outrage to all of our lumps and former folks who former parents and whatnot who aren't here today and they came in huge for the team During the day of giving more than a hundred donors to our sailing program over the day of giving with some more donations still coming in and It's really tremendous to have this level of support for the team from parents grandparents alumni friends of the program it is really really heartwarming and We need it. We definitely need all your support like I mentioned earlier one of the lessons that we learned last year We needed stronger communication. And so one of the things we want to do again is bring Betsy butter work butter Rick butter work not butterworth back to work with the team. She made a huge impact on our team in 2020 So we plan to use some of that for good Probably some of the money raised will go to offset some of our training training trips both the winter and the spring training trip and other Team team initiatives that like like I mentioned before but just intentional team bonding activities that we can do and our really critical training trips so Thank you to everybody who gave if If when I post the photos from today online, and you happened as As Emmett mentioned earlier, but if you happen to notice that you you were touching another boat I'll also post the link and if you want to make an extra donation as a result of you touching those other boats We would welcome that and Finally just to kind of wrap up the night. I want to thank again all the people who made tonight possible Some behind-the-scenes folks to start Heidi and her special events team in the back Who's always trying to keep me on time and focus? Very difficult wrangling me so she does a great job. I want to also thank our friends at Bon Appétit They there's nobody who takes more pride in food service than the folks at Bon Appétit I mean, I know I eat there at least twice a day But they love what they do they serve amazing food and they take a lot of pride in what they do So thank you guys for amazing lunch and dinner tonight We had a full alumni division this year and I can't thank the What Bob coil refers to as the usual suspects in the back tables 16? I think you guys are at but thank you guys for continuing to or I don't know where they are Anyways, oh there. They are there they are Thank you for continuing to show up and we appreciate you so much coming out in the pouring rain The newer alums class of 18 and 19 showing up in and 20 showing up in full force It's so much fun to see you guys I wish you could hang out more and you guys can come back and hang any time all the time I Have to go back to the list here just to make sure that I've got everybody but huge Thank you as I said to the McGraw family and the McGraw family foundation We'd like to thank the Matthews for donating the love boat to us today Thank you to Leibn's family the Wreckler family and we have the Ben Haas who have Kicked off they have led off a sailing ambassador program and they are We're really delighted that they were the first ones to jump on board with that and hopefully Kate will be reaching out to Invite more people to join our ambassador program Then the raw bar. Sorry the cocktail reception was sponsored by our trustee Marsha Morris The raw bar tonight was sponsored by the Matthews. Oh I read it in the wrong order my bad and then folks who's brought the sponsored programs Michael Reuter the fishers and Eric Stockey Thank you so much for all of your support and making today possible making our boats possible Making all that we do possible. Just close on. Oh, we're gonna invite Claire and Hank up Definitely not. Thank you for supporting the 19th annual captain's cup on behalf of all team captains myself Carly kiss who's like currently at ACC and Hank Bailey We want to take this opportunity to thank you all for coming And we also want to take some time to appreciate our alumni as well as all the families that help support this team We could not do it without you All right First let's start with our alumni the loudest group in the room very thankful for all the alumni that uh, I'm just gonna grab this Very thankful all the alumni that show up and just make Roger it is today. Hi Darren I want to give a shout out to cam wood For donating 400 pairs of clipper boots to the team at the beginning of the year If you are wondering what those swaggy white and yellow boots are those are Cameron woods clipper boots And the whole team has been rocking them all season and we've been loving them. So thank you so much cam But uh, overall, I just want to say, um, you know, we have the most incredible reliable and generous alumni network that an undergraduate sailor could ever ask for We love that so many alumni return to campus to assist coach at practice And while our focus is to be the best on the water our alumni network helps us to also be the best on shore Our alumni our alumni continue to be available to our current sailing program Whether it's postgraduate advice helping soon to be graduates open doors to the corporate world Or simply exchanging anecdotal sailing Sailing experiences that only an older and wiser fellow sailor can provide As a soon to be alumni, I look forward to being a part of your legacy Now for a little bit about the families your support definitely does not go unnoticed There's no way we could compete at the highest level of sailing without you Some big shout outs one to the frang kyle is currently not here. He's at accs But his family is always just supporting us at regatta bringing us doughnuts everything to get through the day The dales who have hosted st. Croix winter training trip for the last two years. Let's hear it for them Shout out to the mafios who provided meals to us during last nationals You guys are phenomenal and this program is so lucky to have you all And a major one to the entire snider family who hosted us Last weekend at the nevins when things didn't go exactly to plan We are so lucky to have you as part of our big community And with that being said, please enjoy the rest of your evening and understand the huge value add to our community go hawks Sorry one more announcement. Um D brief video will be at eight evelin drive Max said for every time on the video we see him hit a boat. He'll donate $100. So We're in cows many times eight evelin drive. Let's see It's it's eight evelin drive riley And let's call that nine nine p.m report time nine p.m at eight evelin drive


Hello, I'm Christophe de Dinsin. I'm working at Red Hat on virtualization, and today I'm going to talk about Kata containers and QMU mini. So as most of you probably know, Kata containers run containers in their own virtual machine, and that's in order to provide additional isolation features, et cetera. So this talk is mostly about packaging that for Fedora. So let's start with a short story, why package Kata containers on Fedora. So you want to put containers in virtual machines to provide isolation additional features, and I'm taking the value proposition here straight from the Kata containers website, the speed of containers, the security of VMs, and it's a drop-in replacement for container runtime. So where you used to have Run-C, for instance, you just have Kata runtime instead, and the rest should work more or less the same, and should work with Docker, Podman, Kubernetes, et cetera, OpenShift, and so on. So of course, as engineers, we may ask questions, do we really get everything at once? Security, compatibility, performance, simplicity. You probably guessed what the answer to this is. You see on the top right, square peg, round hole, doesn't fit. So how do you actually run Kata containers? Well, if you have any experience with containers, you know that the answer is, it depends. So for instance, with Podman, it's fairly simple. You simply add a dash-dash runtime option, and then you specify Kata runtime after that, and that's basically it. Well, I'm sorry, I lied, and that's not the last time. Because for now, you need to also disable AC Linux, so dash-dash-security-opt label equals disable, so that's probably going to be fixed relatively soon, I hope. For Docker, it's just slightly more complicated because you need first to edit your Docker service file to, so that it knows about the new runtime. Then after that, it's pretty much like for Podman. For CIO, that's basically you need to add an entry in your CIO.conf, and that's how it knows about the runtime. Okay, so installing Kata containers used to be what you see on the little picture on the top right. With actual federal packages, it's a bit easier. It's basically GNF install, and you have five packages though Kata runtime brings, as a dependency, most of the others anyway, but we'll talk about why we have five packages, what they do. So Kata runtime is the OCI runtime itself, so that's the part that takes the OCI commands and forwards them. Then you have Kata OS builder, that's the second most important component, and what this one does is take the existing kernel in your system, so that's the federal kernel. In that case, and build an image that Kata containers can use after that. Then we have Kata Sheen, that deals with the IOs and signals for your running container. Kata Proxy, that routes the data to the agent inside the guest. And one that is sort of outside of this picture, which is a same page merging throttler. So you may have heard me mentioned the agent, so you might wonder why is there no Kata agent package? And that's because basically it's integrated as part of Kata OS builder, so the builder builds the agent, the Kata OS builder includes the agent and puts that in your image. And if you know Kata, you know there are other components that are not packaged yet, like Kata netmon, but at this moment I wish this was the worst of our problems with what we need to do with Kata containers. So in terms of configuration, there's a lot that you can configure with Kata and it's found in the, oh, no, that's weird. Is that true for, okay, so I tried to push some things on GitHub and I think I did a mistake in my rebase because you're supposed to see the configuration to mel file there and it's not there, so sorry. And a variance for Firecracker, for instance. So configuration.tomel is where you have your various configuration options. So why is all the config, okay, I don't know. So the runtime, for instance, the runtime section looks like this. These are pretty standard config files, so I'm listing them so that you know where to look for each of them and I'm sorry that they show up empty. That's the thing with having the presentation generate that in real time. I don't know, I think I must have moved the files away or something. And there are many other knobs. So Factory is one that is interesting, I'm sorry it doesn't show up, but that allows you to do VM templating, for instance, and you have configurations for all the subcomponents, the shim, et cetera. All these are in different sections in the same configuration.tomel file. So, okay, now that's going to be really annoying. Where is, sorry, but now you see the secret source. Where is the file? Okay, the files are gone. No, that's annoying. Sorry? Yeah, so that's where they come from, and let me show you what they look like in real life, not in the talk. So for instance, the main one is here, and so the section I had was basically, so what I'm looking at right now here, so this one is configuring.tomel. Sorry, real life, real life, now it's there. Hi, it's still in my Emacs buffer, so I'm saved. I'm not saved. Oh, I'm saved. So you have the path, you have the cam, so basically it was ready, I think it's my git push to git have that. I tried to push the presentation on GitHub, and I had to do a rebase, and I think I lost it in the rebase. So, the path to the values components is found in this hypervisor configuration file, so you have the initRD, the image. You have to choose one between initRD and image, and by default we select initRD because it's basically about 10 times smaller, because you don't have everything, you don't have the whole file system. And you have similar configuration for other hypervisors than QMU, but who would want to do that, right? So choices are Firecracker, NEMU, and Acorn, I guess you say that. And in terms of hypervisor, you can put QMU, but you can also put QMU Lite, which is the kind of version that they built in Catacontainers itself, or a QMU Mini, which is the other part of this talk.  So, let's start with a bit of history and how does Catacontainer fit with all the rest, and with all the rest, I mean the world. So, let's start with words of wisdom from folks before us that you will see will come back again and again. So, the first one is for every problem, there is a solution that is simple, clean, and wrong. You know, if you have done any kind of pearl, you know about there is more than one way to do it, which they use so often, they have a timetoddy acronym for it. The good things about standards is that there are so many to choose from, there could not be more true than in containers. You probably know about the second law of thermodynamics, which is that entropy, which means disorder, it's a fancy name for disorder, increases with time. So, do you know who the guy is on the top left? So, his name is Karno, and it's a very interesting life. You should probably Google him on Wikipedia. And our friend, Richard Gabriel, has written a nice essay way back, you know, last century called the rise of the worst is better. And in it, it says one thing that I find very interesting, which is in the future, we will have a good operating system and a good programming language. That's the good news. The bad news is there will be Unix and C++. That was really prescient. But he also said that, get half of the right thing available so that it spreads like a virus. And once people are hooked on it, improve it to 90% of the right thing, as opposed to trying to be the right thing right away. Our friend over here told me yesterday, you know, while we were discussing this, break it properly so that you can fix it properly. And I had to actually modify my presentation to include that great quote. And finally, you know, because so far I only coded folks from our world, your computer science world. So who knows Gretchen Rubin? Who had heard of Gretchen Rubin before? So the fun thing is I was looking for great quotes about containers. And that's actually the one that popped up. And this one is into, you know, home organization and cleaning up your home and stuff like that. But I find this really, this applies so well to our world. I love cunning containers as much as anyone, but I found that if I get rid of everything, I don't need. I often don't need a container at all. So now you're more knowledgeable about things. Okay, so let's go back very, very far in history and talk about software, containment, boxing, sandboxing, all this kind of things. And I'm going to show you that this is all us being controlled freaks, you know, trying to contain things, everything. Do you remember that thing? Way back when mainstream operating system were running directly on the hardware, and that's what you got, basically, you know. So this is back to this quote, right? Running directly on the hardware is the wrong solution. It's simple, but it's wrong. So then we invented hardware things like MMUs and so on, and you control memory access. And from there, IBM went to IBM machines and then in the x86 world, VMware and others. But the problem is that you need your sandbox, you need something in it that you own. And that's where things like Fruit, for instance, was one of the first instances where you'd actually get your own kind of private thing where you could do your stuff and not touch the rest of the system. Then VMware was basically how to control the non-virtualizable x86, which was a feat in itself. Initially it was to run Windows on Linux.  V-server allowed to control the ports, Solaris Zones controlled views on the file system and things like that. C-groups gave us control on processes and namespaces control on things like real access, stuff like that. And then you had to add, you know, user space access for all of these things. And basically you were ready to build Docker with it. Does that make sense? But there is a cost for control and you can see, you know, on the top right picture, you can imagine what lack of control looks like, right? And so there is a constant trade-off, a tick-tock between conflicted diamonds. For instance, bare hardware gives you full access but it's fragile, it's not portable. Virtual memory gives you memory production but then you had early on distrashing performance costs and so on. So it's always a trade-off between inexpensive or easy and something that you really control. Shrewd and jail give you an inexpensive and easy way to do things but you had limited benefits. It was basically only the file system and full virtualization would fix that. You could run DOS on Linux but it was so slow, at least initially. Containers went back to the, you know, lightweight set of things and you could then orchestrate a lot at large scale. But then you want to product that so you put Kata containers and again you're going to see something that is actually slower. And then back to try to make things lean and mean, you know, QMU, the VM engine that we use, the hypervisor is basically a huge beast and for years we searched for an excuse to get rid of IDE, we finally got it, right? If we want to run containers in it that don't need IDE, we can scrap that stuff. Okay, so what do we do with that, actually? What really matters is your software. It's the stuff at the center, that's what we care about. So, you know, if you were running on a Macintosh or in a unicannel, your software basically has direct access to the hardware and you're happy with it. Where this runs into trouble is when this other guy tries to run stuff on your machine. Now their software is going to steal the CPU or the memory or whatever and it's bad for you. So that's why you invent real operating systems that will schedule stuff and protect you from these other nasty folks. Your software is perfect, of course, but theirs is not. So you need to address that. So far, my picture on the top right is, okay, everything is fancy, I'm happy, and so on. But then you start saying, okay, I want my sandbox. So now you need to bring some thing that looks like a file system. For instance, inside your own sandbox. So you start trying to do that with the operating system and then that starts to be complicated. You have the same thing at two places, which means probably slightly different semantics at the two places. It's not going to do exactly the same thing. So if you wanted to really do the same thing, then you need to bring up the whole machine. So that's where virtual machines are invented. You know that now you can run inside and it looks really like a real machine. So it's a full machine sandbox, but starting to say to go home. So you know, the components in our case, like cumuliverts and the kernel component KVM. And that's too big, that's too fat, that's too slow. Okay, so let's try to do the same thing, but inside the operating system and that's containers. So it's OX, OX built sandboxes. I don't know who said that, but I think it's somewhat true, is that whenever you need to use virtualization, it's because there is a bug in your operating system. Which is, in a sense, it makes sense, right? And so the good thing about containers is that they scale pretty well, because you're sharing resources in an operating system that is designed to share resources. So that can scale well. And from there, you can build things.  And that was a pipe dream for so long that it's worth stressing software composition, software components, stuff that you could pick. It's another of these things that were predicted in the 90s and for kept dreaming of software components that you could compose, assemble, et cetera. That's exactly what Docker brought and that's why it's so successful. Now that we use Docker, I wish I could go back in time and for all these folks screaming, we need software components that are, no, don't do that. Well, too late. So to orchestrate all these things, then we have tools like Kubernetes on the side and so on that manage all that stuff for you. And then you need to talk to what is inside the containers. So that's why you need a common runtime interface and stuff like that. But if they want to talk to virtual machine, then it changes a little. And for instance, you probably lose, if you don't do something special, you lose all the benefits you had from Docker because the composition of software that Docker was providing, the overlay file system and stuff like that, you don't have that in VMs naturally. It doesn't fit there. So you can have containers inside the VM, but you can have your VMs themselves be containers. So that's why Kala container is trying to fix that. They are trying to bring the best of both worlds, basically to bring the software composition back to VMs. Does that make sense? I mean, this diagram is a bit busy, but I'm trying to summarize 20 years of folks thinking about this in one slide. And QMU mini is QMU optimized for Kala. So we are just trying to have something that does just what we need for that use case. So now my smiley on the top right is like, I'm lost. Are you confused yet? How did we get there? That's the predictable results of open source software is great, but basically we grow things step by step. There is no giant design. There is no one guy who said, we are going to do the right thing. And so that's exactly what we expect, but now we have to make it work. That's the bad news. So general architecture of Kala containers. So there was a great talk yesterday. So this is going to be a bit of a repeat for those who saw Matt's here on yesterday, but basically Docker talks to container through a number of layers. So it's a story of the guy who talked to the guy who talked to the guy who talked to the guy who finally talks to your container. And the part that is really replaced is at the bottom is this RunC red box that gets replaced with this Kala runtime red orange box. Let me digress because I think you're tired by all that stuff. So RunC CRUN, we really needed another language war. So let's look at what RunC is. RunC is a CLI tool for spawning and running containers according to the OCI specification. That's fine, right? Looks good. CRUN, a fast and low memory footprint OCI container fully written in C. How is that different? Well, why another implementation? Most of the tools used in the Linux container ecosystem are written in Go. I believe C is better fit for. Let's do it again. And let's name it CRUN rather than RunC so that newbies like me are completely confused. Okay, so that was not the end of my digression. And I can go all the way. Why stop digressing? Hypervisor-based runtimes for OCI. What is that stuff? RunV is compatible with OCI. Okay, the others too, so that's not different. However, due to the differences between hypervisors and container, the following sections of OCI don't apply to RunV. Namespaces, capability, device, namespace, does that? Is that useful for containers' namespaces? Capabilities, I mean, who needs to drop capabilities? Then what should be happy to have a runtime that doesn't care about capabilities, right? That's the moment where you want to bang your head like this. BAM! Okay, so now time to show a simplified diagram of how things actually work. What I like about this diagram is that, in a sense, it's like we had a time travel thing just before. In a sense, this is time going downward, right? So on the left, you have things like Docker. And they talk to a cubelet, and then they talk through the common runtime interface. And then you need to run on the other side. Oh yeah, you're right, Karen. On the side, it's on this way. The thing that this is backwards. So basically, this started with plugins everywhere. We want to do this to be very, very modular, so Docker, same Docker, container, D, and so on. And the problem, well, it's very flexible and so on, but it's a bit complicated to make all this stuff work. And so we'll see that many times, there was an attempt at simplifying by putting things back in the black box. No, sorry, Marie, not now. So I also use this slide as an opportunity for you to understand the differences between, for instance, CRI and Cryo, or CRIO. Now what, so there are CIs that are not OCI compliant? What do they do? I don't know. And there is a, okay. So the good thing is that all these things are perfectly standard. You just need to learn their names and what they do. So Cata containers is basically, I swap the runtime. Nothing could be easier, right? I just replace the thing at the bottom with the things at the top, fine? Where's the problem? Okay, there is actually more than the runtime. And that's why it gets complicated. I already showed this in a smaller version, but you can see in its full glory, it has picked up straight from, lifted up straight from the, I think, Cata Container website. And so one of the trouble things is that you need to talk to the VM and this is done through, you see this hypervisor serial interface. I think they can use vSoc as well now. So these things get complicated. That's basically yesterday's, the Matt Heans talk I talked about yesterday, this is it summarizing one slide. But the problem with all these are rows is that they can break. Anything in there can break. And so what do they do? They do a v2 that looks like this. You know, this is called the great black box simplification. It's really this exact same diagram, right? Except you locked the black box. Inside it does the same thing, trust me. Okay, so now I'm running out of time already. So there are plenty of things I would like to talk about, but I can't, because I have only 45 minutes to talk. So I can talk in details about ContainerD, DockerD and all the nasty little demons that do their stuff in the corner. Sheens and proxies and all the other, on agents, all these little helper processes I can go into much detail besides large diagrams on what they actually do. Cubelet, that's another story. How does it talk to pods and so on? All the fancy exotic runtimes, how do they fit in that picture? Frankly, for this one I just have no idea. And then Podman, well, so we have Podman, we have Docker. What is the difference? Why does that matter? It's a very interesting topic itself. I can't go in depth into this. And what is Moby? Okay, that's yet another one. Container image formats are also another interesting question. I won't touch that at all. Repositories build tool, don't ask me about this. I know nothing about that stuff. All these things are additional standards and ecosystems and communities that you need to know about if you're serious about containers. So the summary of all this is that the Rubik Goldberg School of Computer Programming, led us to this situation of there's not just more than one way to do it, there's more than a thousand ways to do anything. So back to packaging, which was the main topic. I digress a little for now. It was supposed to be simple, but now you can probably guess why it was not. So what did I start with? I started with some bits and pieces, a little bit like the picture on the top right. Some work had already been done. The most important one of use is that Kata containers itself was largely working, so you could build it manually and have most of the stuff run. There were some Suzy packages available and they were sort of working if you were ready to add fancy dangerous repos on the side. And sometimes you had interesting stuff, like QMU Lite, the name of the package in these repos is OpenBios Development Utilities. Copy, paste, error somewhere, maybe? Hello. But also, and that's much more of a problem, there are some interesting conflicts because that all relied on their own custom build version of QMU which of course is completely outdated. It was based on QMU 2 something. That leads to somewhat nasty and let's call them interesting conflicts. So bottom line is you don't want to do that. And of course these packages were not following any of the federal conventions. Some of them I'm going to talk about later related to Go which are really another thing entirely. And inside Red Hat, some test packages had been built but not submitted yet and so meaning they were not built on a regular basis. They were not really working, they were outdated, they were based on Kata containers 1.4 and the original packator had obviously stopped putting any muscle into it. So basically you had half of the packages and the half that was there did not work. The other bad news is that I'm a total newbie with respect to federal packaging. The first federal package I did was like six months ago, eight months ago, something like that. So that means that if these packages are broken, please tell me, sorry, strike that, I lied. It is broken, please tell me. Okay, so Kata package structure, why did we decide to build one package to build five packages? Well, the obvious answer is why build only one package when you can build five, right? I mean, I'm paid by the package. So you have seen that already but it's a refresher. The main package is Kata runtime then building the OS image with Kata OS builder. So can you think of reasons why you would want to have the runtime but not the OS builder or the other way? So for instance, it depends on where you store things, right? So you might want to have one place where you actually have your reference bills and then leave from there, things like that. So there are good reasons why each of these components you might want to upgrade them or install them independently because basically there are really different parts in this system and because they communicate to one another, they expose interfaces. So you might have cases where to fix a bug, you might want to upgrade one of them but not the rest. I'm not even talking about QMU yet but we're going to talk about it later. So why was it complicated? It's in large part a tale of two package managers. Go and RPM don't mix too well, much like Diet Coke and Mantos don't mix. More or less the same effect. Oh no, no, that's really nasty. Okay, so why are, there's no rhyme and reason on which files were gone, it's really real. Okay, so you can build a, let me show you what this was showing. This was basically showing that you can build inside a spec file. Oh, hey, I can use the same trick. I can have that in my, so it's called bidmanuage.spec and I have it there, ta-da, okay, that's going to be annoying. Okay, now you know that this is colorized in real time by the way, this is fancy. Okay, so in order to build a go package manually, you need to do stuff like that. And that's basically using the make file that was provided by them. And I highlighted this not check version equal blah blah blah which I added in the, so let me explain why. This if not check version that you see in there is disabling this have yq, yq I guess is pronounced yuck. And this yq is something that you can't find anywhere. It's a small little project in the corner that happens to be pushed in the right go repositories. And so implicitly what this does is it fetches stuff from the internet, expands all the sources for yq, builds yq on the side, and does all that stuff. That requires internet access which typically you don't want to do while you're building federal packages. And so in order to, so I scratched my head quite a while trying to bring the yq source file. There was no documentation. I did not know where to find them, et cetera. Until one of our colleagues, Dave Gilbert mentioned, you know, this thing is only checking the version number and you're doing that anyway while you're building. So you don't need that. And so, hey, yeah, I can set this not check version internal variable and that works. The rest of the package builds. That tells you the level of, high level engineering that went into that stuff. When I was done with that, then I learned, hey, you can't do that on Fedora, Rohide, or 31 at the time when this was introduced. Because now this go stuff is so crappy, is so dangerous, and they had so many issues with it that they decided to have packaging guidelines for GoLang and a brand new set of RPM macros called GoLang RPM macros that I can't say without. Because that was under development while I was doing that stuff. And the problem again is that Go has its own package manager and downloads its own stuff, Fedora won't have that. So of course, on the website documenting this stuff, it looks simple. That's the example they give. And that example works perfectly fine. But that's about the only thing that works. In real life, okay. Sorry. So in real life, that doesn't really work because that may file is doing stuff that GoBuild itself does not know how to do. Like setting the machine type, the kernel parameters, stuff like that. And you can't really do that with GoBuild. There is no simple way to, which is why they have a May file by the way. So they are setting files and turning in files into the actual files, the fields and so on. And all that stuff does not compute with GoRPM macros. So I have to use the half that is mandatory because otherwise they won't accept my package and then completely ignore the rest, which is a bit annoying. And then they have this nice tool called GoToRPM which gives a good starting point. The only problem with GoToRPM is that it did not exist when I started. And so in the end, I take my existing RPM and I run GoToRPM and I see this nice section of provides and that explains the problem with GoPackaging. That's the stuff that my package provides. Because it's building it, it's dragging that stuff. And so they are trying to find a way to tell all these bundled things are inside your package as well. So we all thought this would be easy, much like when you try to feed a kid, right? You think, hey, everybody can do that. And then you get a picture on the top right. It turned to be really messy. So having all these commits just for that, well, when you see what is in the commits it was. Okay, so by now you really want to exit this room and you hope I'm done. Well, I'm sorry, but there's still a bit of work to be done for this Kata container. Not everything is under control, much like when you have, it looks very much like my cat, coffee, cat, laptop. What could go wrong there? So one issue is that you have moving parts left and right. And the Linux kernel, for instance, for someone who is outside looks a bit like this. It's a fractal maze of things that move all over the place. And it's really hard to understand what's going on. So one of the issues is that they moved to C-group V2 and Fedora has adapted that quite early. This means that you need to do this work around every time you reboot your machine to make sure that container sees the C-group at the right spot. Except if you run for a while, then chances are that the CPU one is already mounted elsewhere. And apparently you can't mount it C-V2 and V1 at the same time. So now you're stuck. You have basically to reboot your machine just to be able to do that mount thing because there is no way to force and mount it. I tried, well, at least I did not find it. Then there is the support for Vitaio FS, which is much faster than 9P. I'm going to come back on this. But that's very recent. The commit for Vitaio FSD was last Thursday upstream. I don't know, something like that, right? So it's very recent. And the commit for the kernel was I think 5.3.15 or something like that. So it's in 5.4, but it's relatively recent. And the problem is that that forces you to go to recent kernels, which have C-group V2 back to the problem above. Then that stuff is running at root. And we mean real root without dropping capabilities or Linux or anything fancy like that. So this is really Dr. Ible at play. We can have that on a real system. So we need some kind of jailer. We look at it, we see that, right? Except the reality, it works like this today. And we are lucky sometimes, some things may be caught like the little, but not that often. So we would like ideally to leverage Invert. And I have the kind of Goldilocks, for those of you who saw Daniel's talk, he was talking about Goldilocks level of security. And Invert is sort of providing that. So we'd like to leverage that, but that brings in a whole kind of worms of who does the work. Are we asking to do that in Kala containers, but then that will be Kala containers only? Or do we find a way for Invert to offer a jailing feature that is easy to use from go? Or do we see that as a QMU option that where QMU would sort of double fork itself and do the stuff for you? Or whether, it's hard to tell what is the best solution at this point, we're still discussing it. So SELinux is both, which is that your containers at the moment look a little bit like this pipe here from a security standpoint. So again, not in production, please. And then there are a number of enhancements that we may want. And as this picture illustrates, one of the problems is that we have diverging versions of what enhancement means. So for instance, do we want to have memory mapped kernel? Do we want to boot PVA? So we had this nice experiment. We have various experiments on how to boot things fast, for instance, or using less memory, leveraging the kernel image between multiple booths, this kind of things. And how do we want that? And then we want to have a VM optimized kernel. I mentioned that QMU mini is a good excuse to get rid of IDE. So can you guess what this thing on the right is? It's the very first IDE drive from a compact of 19, I forgot, I think it's 1980s, I forgot. Way old. But the same is true for your standard federal kernel. It supports tons of stuff that you don't need. But out of the box, it doesn't build by default, it builds as module, all the virtio stuff, et cetera, which means that basically you don't get much help from mapping it or things like that. Okay, so virtio FS, there was a whole talk about this. I'm not going to expand in great details, but the thing is that networking in general is a bad thing, you all know that, right? Fake networking like the picture on the top right, it's even worse. And 9P is exactly that. So if you compare virtio FS to 9P, there is really no discussion, and it's even better if you compare for async IO. So you have a very, very good reason to switch to virtio FS, just need it to be upstream, available everywhere and so on. Okay, so I mentioned QMU mini a few times and I don't have that much time left, so I'm going to very quickly brush over what this is. This is really a QMU tuned for color. The point is to try to make it as straight QMU as possible, as little change as possible, no patches, no nothing. And that turned out to be actually relatively easy once I understood what I was doing, which took a while. For instance, in the existing configure script, there is this run configure disabled everything, which is very fancy because I spend a lot of time writing my own, till I realized that this was basically in the standard. And then after that, you can enable your own stuff. So there are some miscellaneous, if you really look carefully, there are some miscellaneous things in there, like for instance, VHOS Cuzzy, and what is this mini FDT, stuff like that. So there are still a few things that we don't really want to have in there, but if they are not there, you have unsatisfied symbols, you have missing bits, that means it doesn't really work. So then I was relatively happy with that, and I started discussing with other folks, who said, ah, no, don't add another binary, because we already have QMU system, blah, blah, blah, and 10 variants of it depending on the system you emulate, and then you have QMU KVM, and the spec file, there is a single spec file that builds all of this, which is already quite hairy.  But that means yet another version of QMU that we have to explain, to have main pages for, to maintain, that might be a different version, and so on. So overall, we wish we could do without it. And the worst part is, I did that work, but I'm convinced by the argument, and I was convinced before I did the work, actually. So I was working stuff that I thought was. In terms of patches, there were only four trends in patches. By trends, I mean that many of these things are actually now in the existing code base, so if I rebase, I would probably not need these patches, but something else. And so, the thing is I had to learn over and over again, because it looks simple when you see the end result, but I had to learn how to get there, and that was actually my version three to get it. So, what do we gain from doing that? That's a much, much smaller binary. The size went from 13 megabytes down to 5.8, so that's pretty significant saving. That's not just ID that we dropped, right? And do we gain something in terms of performance? It's a bit unclear, frankly. That's the diagrams. So this is the best of five with 10 runs. So this means that what you see here is the range of time. And you can see that QMU KVM, for instance, on one vCPU with two gigs of memory, has a relatively large range. And yes, QMU Mini seems to be, it goes lower, meaning it's faster, but it's also sometimes as high or higher. So it's unclear that we really save much in terms of performance. Now, I did not do much more extensive testing than that. I took basically the worst case, which is to start up container, have it echo a number, and shut down. So that's the worst case, and my workload is practically non-existent. It's all boot time and shut down. And by the way, you remember the thing that was said at the beginning about it's being fast and secure, et cetera? Look at Podman on the left. Podman without color runtime. So yes, it's fast, except if you care about boot time. Inside the VM, there is not that much difference, frankly. But if you care about boot time, there is a difference. So will it ever ship? I saw this nice picture of a launch of a ship, which I thought was. So on the pros, should we ship something like that? It does reduce the footprint. It may reduce the start of time. It's built from a single source. It's the same spec file. It's basically the same version, et cetera. So we get all the patches and all the series solutions and so on. And it's definitely shorter to type QMU-mini than QMU-space-mini, right? That has to be a pro. On the cons side, we have multiple binaries when we already have too many. This requires some additional testing because it's a very different configuration, so it needs some testing. It's an overly specialized use case. Or maybe it is not. Maybe with some tweaks, it could also be usable by Qvert, it could be usable by other cases. That binary does not exist anywhere else. So it would be in Fedor, but that means that the same config files would have to have a different argument in another distros. And that's really the killer, is we think that we may do almost as well simply by having QMU-DL open the large stuff. Like for instance, Spice. Spice is big. It brings tons of other libraries with it. It brings in particular Orc, which is a code generation runtime, which you might not really want to have in your binary, stuff like that. So we want to do an experiment with the L open before committing to anything like QMU-Mini. My conclusion is we have only begun making this complicated. It's only the start, it's going to get worse, and that's logical because entropy always increases. Thank you, and time for questions. Thank you for being patient with me. So the question is whether there is any plan to support checkpointing and restoring? I'm pretty sure there are, but I'm not familiar with them. We had a talk just before that on, for instance, I'm not sure if a solution like what was presented before could apply in that case. What kind of interface would you use for your checkpointing? So that would be a throughput man. Frankly, I don't know. I don't know of any plans. Well, you know, if you shout loud enough, they will plan it, right? For it to be planned, you only need to open a GitHub issue, so. Any other questions? Yes? So the question is why do we provide CataOS Builder and not the kernel directly or Inetardee? The answer is that if you want to build your own kernel and Inetardee, you still can. But from this stuff in the long term, we might want it to migrate to RHEL, and there is little doubt that from RHEL's point of view, what will be supported is the RHEL kernel running in the container as well. So now what we want to have is that if you update your host kernel, the image gets updated as well. And so that, basically that spec file does that. It will, whenever there is a kernel update, it will reinstall an updated image. My Inetardee business. That's what happens. That's what happens. I see you frown. You don't like that? Only the image is rebuilt, right? And the old image is kept. So the old image gives its own name. You get a new image. Then you have to do it manually. And there are scripts inside this RPM. There are scripts that allow you to do that with any random kernel you want. By the way, you may have not seen that in the values config file, but there was a decision relatively recently, I think it was in version one, eight, one of the package or something like that, where we moved the stuff you build under varkash, where Scata containers typically put it under user share. And the reason is we see that as be your stuff. So we don't build stuff in user share anymore. So the question is, can you stuff the images in Quay or Docker or any other place? From that point of view, I don't think it's different. That the part of building the images and creating the overlays and all that stuff, it's pretty much the same way. From the user perspective, at least. The way they are mounted inside is different, but the way they are built is not. So the question is does Caddox support side cars? And I don't know. It does anybody have a reasonable clue about that? So in any case, the short answer would be no, because the notion of Caddox containers supporting is not clear, right? So the next question would be to a point where Red Hat could support that, which is a slightly different question. The feature does not exist as far as I know today, but I'll check. So could you repeat the question please? So the question is how does Caddox deal with volumes? Well, so you have two parts to this. One part is the initial image, the your start volume, et cetera, and the fact that you want to expose something that are sort of available initially to your image. And for those, basically that's why the choice of Vata UFS or 9P comes into play. Now, if you want to add any additional volumes, well, you have either the path of going the same way you would do for a container, but now because you're in a VM, you have additional possibilities as well. And basically stuff that you can do inside of VM by passing the additional options, you can mount an additional volume or do stuff like that. So you have more options, so whether they will be supported, whether they will be used, at some point it's not very clear to me. Did that answer the question? So if you mean whether you can pass the dash view option? Yeah, that works. The question is how that dash view option is shown inside. That's, so that's where the choice between, so one thing I did not really touch about Vata UFS is that because it's not a network file system, it's basically talking to the host file system. It's a shortcut. So now what you see is a real file system with full file system semantics and you have values caching options that you can tweak and stuff like that, but in the most conservative mode if you want, you can even, at least in theory, I'm not sure if it's supported, but you could even have things like locking work properly between host and guest. Does that answer the question better? I'm out of time. So if you have one last question, I'm just to annoy my moderator. Thank you for listening.


Thank you for joining us. I'm librarian Emily and usually I'm a librarian at the Marina Branch of the San Francisco Public Library, but right now I'm also a librarian at home. So today I and Bunny will be helping you to learn a new song and it's a fun one, a really fun little baby bounce that you can do with your baby. So what we do for this one is for the main part of the song we do a bounce up and down on the knee like this and then we go and your baby may or may not like being lifted. So if they like being lifted up you can say first floor, second floor, third floor, fourth floor, fifth floor and down and down we go and gently settle them on your lap but they don't like that you can always just do a little gentle touch on their abdomen or on their arm and say first floor, second floor, third floor, fourth floor, fifth floor, something like that. And so you still have the gradation but it might be a little gentler if your baby doesn't like being lifted up high in the air that's okay too and maybe if they're having tummy time or crawling around you can also just sing this song to them so plenty of options. All right why don't we go ahead and do this bounce here we go. Let's go riding in an elevator elevator elevator let's go riding in an elevator come along with me first floor, second floor, third floor, fourth floor


What's up everybody I'm Eoreb and we are here on Torque Drift today to do a little tutorial and to help out some people with tuning a lot of people when asking about cartoons so we are going to take that E30 of mine and basically do a breakdown on it showing you everything about it but before we do that I feel we should probably get a run in it so you guys can kind of get an idea of if you guys have never seen my E30 it is now a pro it well it is a pro level 1200 horsepower on next and tires and it's it's got a rotary in it all the Doritos little Dorito little Dorito action today so this car is kind of set up very soft it kind of does some three-wheel motion on it and it's kind of a interesting car right there little three-wheel motion riding that outer bank a handbrake grab there a little flick there so little sparks there just click the wall a little bit too hard well so much for a really good baller run with a zero penalty score but still a good run nonetheless as you can see this car got a little bit of a three-wheel motion going on some little slick he left it right but it's definitely a solid car I do love my E30 and you guys remember from the beta I used to rock the rotary E30 and it was awesome so I decided to bring the rotary E30 back so we're gonna do it again because we didn't really get a chance to chase we are rocking just a generic little livery here for today on the E30 so let's see who our next challenger is gonna be do we crack open a drink for ourselves there we go nice cold beverage while we wait for our opponents to load there it is oh looks like we got a pretty interesting s13 in the mix so this car likes fourth and what I like about it is when I first start off it doesn't get squirrely on me right away like some of the other cars I have get squirrely right away off the start this one kind of does not and surprisingly I can hold a lot of angle for not having a custom angle kit I believe it's only on a pro angle kit but I am rocking the suspension sponsorship which gives me a or angle quit sponsorship which gives me a little bit more angle on my cars than the actual angle kit can give me right on that wall oh white oh you want to tap that while I want to stay off the wall but still a decent run nonetheless so this is just a testament to show you what the E30 is kind of capable of and then we're gonna get into the breakdown of it and kind of break it down for you guys show you guys what I'm using for tuning and stuff like that see if it gives you guys a little bit of a idea on how to help get your cars handling how you want them now my style may be a little bit different than yours but a car tuning is a kind of very similar between this car and my other cars but each car is slightly different based on weight and motor and stuff like that I'm a little bit far behind this guy but he's running kind of a wonky line so we're trying to just stay somewhat close and get our points and not wreck our car I'm not wreck our car there so I believe we're gonna take that win so the E30 four-rotor well rotary engine I don't it's not a four-rotor but we did take the win so let's go take a look and get down to the nitty-gritty of the car and see if I can give you guys a little bit of a some tips and tricks if I say so because my cars do handle pretty well but like I said the cars may not handle that well for you if you're driving styles a little bit different than mine my driving style is pretty pretty quick and aggressive I guess you would say alright so E30 for for the most part we're running a 26B and we are running a pro clutch basically all pro parts pro integral why don't we not run this one oh that one gives us less so we're gonna sell that sell that part probably gonna get my money back up and pro exhaust I could be selling all these parts and making a lot of money on these parts probably but I will do that another time we are rocking a pro turbocharger and for we are running full 18 pounds of boost so we're running a lot of boost on this car I didn't show you any of the other we should look at the clutch so for the clutch we're running a point three shift speed and a negative point 28 clutch kick I don't really use clutch kicks too much I usually use handbrake which if you notice if I'm on the gas and I hit the handbrake same time it kind of acts as a clutch kick in itself so that's why I do it that way because of my driving style might be slightly different so for ECU we're rocking you know higher RPM high idle and high rev limiters that's probably a good thing to do because you spend a lot of times on the high revs especially in this game you need to stay in high revs otherwise you will grip up or lose drift depending on what kind of tires you got on your car and then a pro intake so that's what we're rocking for our engine management we are running zero downforce all the way I could probably tune in a little downforce I want to make the car grip faster in the rear by adding some rear downforce a front downforce if I wanted to handle a little better but the e30 handles pretty well out of the box with no no downforce so that's why we're rocking no downforce on our body kit so nitty gritty of suspension so we are rocking just some import wheels 35 profile nine and a half's in the front I found that nine and a half and ten and a half's front rear pretty pretty good I like nine and a half's in front I think I'm running tens or ten and a half's in the rear we'll see that 35 profile just kind of keep oh got a little shout out to that you'll be in it awesome driving so big shout out to you thanks for the comment on the YouTube shout out to you right there free shout out right there free shout out I'm charged for shout outs so that's we're running for rims in the front and then as for our angle kit we are running 65 degrees of steering lock and camber we're running almost six degrees of camber in the front more camber does help with the transitions and grip so negative one half and we're running eight degrees of caster more caster gives the car a better feel I guess so this is kind of like the basic setup I run on pretty much all the cars in the front kind of the same camber and toe and stuff like that this car doesn't vary in the front from other cars so and then for tires we are running the nexons and we're running 24 psi in the front I you want to run a higher psi in the front than you do in the rear just for grip aspects and stuff like that I the rear's will change based on driving and temperature and stuff like that so the fronts don't heat up as quick and you want a little extra slide in the front with a little harder tire pressure personally that's what I like so that's what we're running for tire pressure in the front on our tires and now for braking pressure we are running 60% braking force so that you can left brake and still keep the rear wheel spinning that's a kind of a basic basic tune for any car my forza drift cars I keep a 50 50% but I keep a lower pressure so I can map the brakes and still have a wheel speed so for suspension in the front we are running pro-field suspension we are running a 12k stiffness and spring length of 11 we could drop it down to 10 but I found 11 works good I wouldn't slam the car all the way down to the ground personally for vent scraping and bottoming out and losing traction and speed and the stiffness is kind of like you don't want to be super stiff but you don't want to be super soft so a little bit softer than stiffer but not in the middle is kind of a good mindset so that's what we're running here so that's for the front and as for the rear we are running only a import diff I should probably upgrade the diff so we're running a 65% diff lock with 3.8 final drive the final drive is something you need to tweak for the car depending on what gear you want to be in with rpm brand you want to get into but diff lock you want to have as high as possible depending on your diff to get the most lock out of the rear ends and then for our angle kit in the rear we are running just a little bit of camber and 1 16th tow I don't run a lot of camber in the rear I know I see a lot of people running massive months camber in the front of the rear I don't run a lot of camber I kind of want to keep the tires a little bit flatter a lot of these but a little bit of camber makes for the body roll when you're leaning on the outer edge tire you're kind of more of a flat plane I could probably run a little bit more to help with that probably grip up a little bit more but this is kind of like the good balance I found for this car you definitely don't want to run as much camber in the rear as you do in the front so I mean you can if you want to be a stance kid no offense stance kids I was dance kid for a while so in the rear we're running a 10 inch wide wheel with 35 profile that's just a wider bigger more grip wider tire you know equals more grip obviously and for suspension we are running our pro suspension we are running a spring length of 13 running a little bit higher just because of the stiffness of it is a lot softer so the higher the suspension so that when it squats down and like when you accelerate the back ends gonna squat you don't hit the ground as much if you notice a couple sparks on Cali banks that's because it's well it's I could drop it down to that but we're just we scrape it everywhere it looks sweet but it's not and then that is just a little bit too high and it changes the acumen of the camber and stuff so 13 is what I've found works so we're going to continue so that is the basically the build rundown of the e30 the rotary e30 so if you remember the settings that we just did there if you take a look at say this custom one we're on 70 eight and a half seven and a half a caster kind of very similar to the front as the e30 is like I said that that's pretty much kind of a standard the s14 we're running a lot stiffer in the front just because of the motor that I have in there the 2j is heavy so I got to kind of keep it stiffer because the weight of the engine is was bogging down the front so that's why we're running a lot lot stiffer in the front spring like just like that is personal preference I guess but try and keep it a little bit off the ground you don't want to bury yourself into the ground brakes are the same way six shim braking force in the front which is weird that my custom brakes are the same braking force as the other ones tire pressures we're running pretty much the same pressures I didn't think I should I don't think I showed you the rear pressures of the e30 I did forget that so let's go take a look real quick at the rear pressures of the e30 and I said I run lower in the rear 10 psi I believe my s14 is also 10 psi in the rear so very similar setup very similar camber and toe notice it's kind of the same I probably should run a little bit more in the rear of the s14 but I'm not spring length is higher stiffness is softer in the rear and that's just for the squat so if you notice that the and then we are oh geez what did I do we are running some downforce in the rear and we're running some really wide track some really wide track in the front and not so much in the rear I think it just totally messed up my tune so we're gonna have to recheck that but that's so that's some tuning tips that I have for you guys here in the game stiffer in the front it's often the rear make sure it's high enough so it doesn't bash the ground when it squats as well as you know you definitely want more camber in the front and you do the rear this car pokes a lot because if you look at like the pro cars kind of set the same way so I kind of based it on what I know from tuning the cars and forza and it kind of it kind of worked out of my favor and we got my e46 which needs a little love looks like we need to give the e46 a little love here soon we do have the mx-5 which we haven't really used yet that much that I got to build up we have our s15 and then we have our little little s13 girl over here that needs to needs to hit the track a little more so with that being said we're gonna hit the track a little bit more before we end this episode off but I want to give you as a little tuning tips to show you guys a breakdown of the 30 maybe that I'll help you guys get on the track a little bit I feel like it's like going to my Cali banks try and get a good solid look run without smack in the wall we're gonna bring out the 30 again so make sure you guys follow me on Instagram and Twitter all of which found in the description box below big thank you you guys coming back and understanding about torque drift being gone but torque drift is back if you haven't noticed too for this week so I promise I'd bring it back and it's back and a lot of people been asking about tuning and tips on tuning their car well hey go little uh tuning tips tuning tips for myself so let's see if we can get a good solid run here on the banks definitely gonna want to bring some uh livestream back to the channel I did have a lot of fun doing livestream other the gas I want to make a little smack in the wall wall tap is okay I will take I'll definitely take that wall run I got a little hesitant I was worried I was gonna like smack the inner wall that was gonna be a too much power so if you noticed like I said I use handbrake and when I get off it's kind of like a clutch kick no there it is that's not what I wanted to do I'll get wrecked I would have been so much better with a cleaner lead if I wouldn't have tapped that wall I guess 112 is not bad see what our opponent got it's a pretty decent uh pretty decent bank run I do say so myself so as always I like thank you guys for coming back and watching I appreciate all the support and all the comments we have gotten over 6,000 subscribers so welcome to all the new subscribers a big thank you for you guys and all the support you guys give me and we're gonna finish this run off well I just made my car get really squirrely by hitting that handbrake initiate in oh too much left foot brake it was just a quick tap on the break but that totally screwed up my line see I tried to do a little effort break even though I should have just handbraked it or further off the gas like I normally do I want to try something different and see how the car reacted so definitely was not ready for that need to be on turn when that happened and I was not so I think that's gonna do it here for this episode here on torture you guys want to keep seeing torture on the channel make sure you comment and like this video I do appreciate all the support if you're not a subscriber tap that subscribe button so as always until next time like thank you guys for coming back I'm evil rabbit and I'll see you guys on the next one


The U.S. Department of Housing and Urban Development announced today that it has charged the owners of a house in Beltrami County and their real estate agent with discrimination for refusing to rent the house to a family because of their race, national origin and their children from a case stemming back from 2016. The charge alleges that lakes and more realty doing business as Bemidji Property Management refused to rent a six bedroom home to a family of four adults and seven children because of their race being Native American and national origin being Hispanic, along with the family's children. The charge further alleges that the owner and real estate agent discouraged the family from renting the home by offering them less favorable rental terms, including increasing the rent by $1,000. After being denied the house the family had to split up and live in two separate homes, the Fair Housing Act makes it unlawful to discriminate in housing because of the applicant's background. HUD's charge will be heard by a U.S. administrative law judge unless any party elects for the case to be heard in federal court. If the judge finds that discrimination has occurred he may award damages to the family for their losses as a result of the discrimination.