What's up everybody? I'm back here with another Illumilani video. So today we're gonna be playing part 8 of Alice, like I said we were gonna do. But before we get into that, I have to address the last video that I made. Or the second to last video actually, cause technically last one was my con video.  Um, so actually I hit the 500 subscriber mark after I put out that video. Never expected that in a million years. I expected to be performing for an audience of like two people for the rest of my life. So first and foremost, thank you guys so much for coming to that video. I'm glad you guys liked it. I had a lot of people in the last video talking about how I should make more video essays, especially ones about the new girls in Chainsaw Man, which I have been catching up to by the way. I'm almost there. I'm almost- I'm almost there. And it's been getting like a lot of attention and a lot of praise, frankly that I wasn't really prepared for. Um, so I do just want to say this. I'm going to keep making video essays. I do quite frankly have a lot of opinions and told I'm a very opinionated person. But I don't think everybody's gonna like all of the opinions that I have. Um, so this is all kind of just to say I'm gonna keep making video essays. I'm really happy you guys liked the last one. I'm so glad you guys had some very interesting takes and points in the comment section as well. A lot of you guys were saying some very interesting things that kind of made me think even in the comment section too.  And you guys all really like that one. And I don't want you guys to hate the next one I put out. So just don't keep your expectations low for me, please. It makes this a whole lot easier to do any more video essays. But anyways, thank you guys all for coming to the channel. Thank you guys for subscribing. We hit the 500 mark, so I'm gonna be making a 500 subscriber video soon. And I do really appreciate everybody's thoughts in the comment section. Thank you guys so much for like all the praise too. Like I wasn't ready for any of that. I really appreciate it. Um, so yeah, uh, and then another commenter before had asked me to continue playing Alice Reddister Turns, which I do intend on finishing by the way. Um, I want to make more video essays, but I also really want to finish this game because it was kind of a promise to myself. And also I really liked this game. So yeah, I mean, I guess with all of that said, we're on part eight of Alice. We're gonna be finishing up the Oriental Grove this level. So let's just get into it. Let's just go. Sorry, this has all been a lot for me. This is like, this is more than I, oh my God. Oh, I'm gonna focus on playing Alice today, my little relaxing game. That's what we're doing today. I'm having a relaxing day playing Alice, or I would be if it didn't just glitch again. New drinking game.  But like maybe I diluted one or otherwise you're gonna get alcohol poisoning. All right, let me restart it. Fuck. Oh no, task manager's not on the right page today. Oh, I don't want to restart my computer.  Okay, please load. I'm begging you, Alice. Just, ah, okay, when the music is in that fast, I know we're in for a good time. Awesome. Okay. All right. Thank you. I much appreciate you actually functioning. Ooh, we have 800, 811 teeth. Let me see what weapons I qualify for today. Okay, um, I should upgrade the teapot cannon, but I kind of don't like it. Like I don't, I don't like it, but it has been useful for me again. I think the hobby horse has been more useful though. So I think I'm gonna go ahead and go with the hobby horse. We'll get that to level three and then we'll get the warple blade, the final level, and then I'll upgrade the teapot cannon. If I remember to do that, I don't know how long it's gonna be till my next upgrade. All right, let's get going. Style level! Style level? Yes. Why don't I feel like I already played this? Did I not save my last progress from the last video? Editing me. Tell me if we already played this level. Thank you editing me. Oh god. Oh god, we're going too fast! Eugh! Eugh! Nope, I've got out. I've got this all under control. Nice. Successful slide. Can you see it from here? Ooh, it looks like a water ride. That's kind of cool. I can't wait until we get to the card level. I think that is after this.  Rattrophy, if you're watching this, um, anything- Oh fuck! That scared me. Yeah, anyways, Rattrophy, if you're watching this, remember when I told you that I really hated the card level?  Thank you! For anybody who doesn't know, Rattrophy's a very good friend of mine. Who used to do YouTube doesn't anymore. But she says I told her the card level was not fun, which my opinion has changed. I've grown since then.  Okay. Am I supposed to get to that from here? No, I guess not. Okay, where do I go? Do-do-do-do. Where are we going? Oh, time bomb. Duh, okay. That's why it had the weird camera angle.  I hate that it did that. Ooh, do I need these? Oh. Oh, oh, I just got that. Okay, the bomb almost let me down. And then I would have had to do it all over again and that would have sucked. I don't like the noises that they make. They're just so in my ear right now.   They're not intimidating, but by God, did they just jump at you? Oh no, what now? Seriously, is it just the floaties? This is weird. What villain are you giving me the turnout telling me about? Dude, why isn't this one opening? It's just floating there. It's just standing there, menacingly.  I'm gonna get my coins though. You stay there right there. He's actually just not opening. I've like moved around the whole map and he's just kind of looking at me. You know what? That's what I call fighting against the system. Don't perpetuate. Okay. Damn it. He's waiting for him. Ah! No! I thought we were friends. That a hero's death for betraying me. Villains death. I meant villains death.   Oh, okay. Well, it's shown so that you'll go the right direction. That makes sense. Listen, sometimes I say things and I'm just not the smartest at analyzing why they're done. Oh, okay. Yeah, let's go do that. God, I love having an advanced adult brain. Like these things are just so much easier now that like I can think. Like my intelligence stats have actually increased IRL and that's so cool. Ooh, okay. That's kind of pretty. Why is it red? Let's go here first. Nice bottle. Whoa. That's kind of creepy. That it reminds me of the queen level. Kind of just looks like guts. Ugh, it's kind of grossing me out. You know what? My problem is not things underwater. I said that in the underwater level. My issue is not the things that are underwater. You know what my issue is? Gigantic large things. Cause like, like this, that's like massive.     My legs get shaky when I look at those bitches. The big things and it translates to large buildings. And I am kind of upset that I know that about myself now. Cheers everybody. It's cold coffee. A bridge will complete the path but this substance has blocked the way. Can you help us to remove it? Yep. I believe I've got the proper tool. At the top of the mountain you will find the entrance to the next sacred cave. Okay, this means boss fight. Ah, of course it does.  Woo, woo. Just be mindful of your surroundings.  That was not very mindful of me. Ah, I'm always rusty after I don't play this for a long time. There we go, there we go. Okay. You're free my friends. Why'd they walk out like that? They're widowy-widying. Can I talk to you? I wanna give you a hug. I'm a little salt shaker friends. Come here, piggy. No, run me my teeth. Thank you. The noises in this one are kind of freaking me out. It's very cool, but it's freaking me out. I hear the things blurry right here. There's so many. Do I just need to get past them and stop trying to kill them? I think I do. Okay, let's just, you know what? Let's just dodge. If we don't have to kill them, we're not killing them. No, hurry before we get shot, girl. No!   Yep, can't play games when I'm panicking. Also, oh my God, he's punking me. Ah! Oh yeah, no, they just come back. I just gotta keep going. That's annoying. Okay, let's get out of here. Oh, they're following me. Get away! This is fan behavior right here. Ooh, ooh, ooh, ooh, ooh. No, I want that. I want that. I want that. I want to go here. Nice! A memory. I wish it were that easy. Oh my God. Oh, they're following me. Get away!  No, I'm panicking. Oh, I'm gonna have to do this all again.  I don't have anything creative to say to you anymore. I'm just angry. I hate it. I legit hate it. Like, I fucking, I can't kill them.    Can I just, can I get rid of you for like two seconds? Oh! The price I pay for being curious and wanting to know things. Oh God. Don't look.   You! Thank you. This guy doesn't want to say anything? Is there anything in here? No? No? Ah, this guy don't speak. Okay, goodbye. How high are we gonna go here? Oh, there's a lot of slide levels in this one. Oh, it's not a side level. Oh, it's a beautiful shot. Don't got the brain cells to think about what that means. Editing me, you're on this. Okay, there's a memory over here and a pig snout. I just saw a pig snout, where'd it go? Oh, there it is, right there. Okay, gotta get there. It's a lot of navigating. Okay, how do we get there? There's a lot of fans over there and we gotta get there. We make those, we make those, we make those. Nice. Okay, is there platforms that I could ride? Yes. Okay, thank God. Please don't move. I would really not appreciate it if you moved. Thank you. Nice, okay. The other ones were deceiving. We didn't have to ride all those. That's good. Thank God.  Her sister used to sneak out and she taught Alice how she snuck out. So that's how she escaped the fire.  So the sister should have been able to escape as well because she was the one that taught her that. Keep that in mind, friends.   So I feel like I understand some more things. It's very cool. Oh, that's so pretty. Dude, that, oh, look at that. It's a bonsai tree. Well, technically a large bonsai tree, but okay, well, we're small. So it's still a bonsai tree because we're smaller than the bonsai tree. We're not getting into conundrums here. Anyways, look at how beautiful that is. It's like vase texture. That's fucking, ah, wow. Love that. I love that so much. Oh, I told him to speak and then it cut to a cutscene.  There we go. Wow, thank you so much, dude. Oh, I remember hating this level. You know what this reminds me of?  The Mario Brothers level where there's like flame sticks coming around and you have to like dodge them. Cool beans.  If I stand right here, will you shoot me? That was a dangerous game I played there, but it looks like we're good folks. I know, I need that memory before we can go that way. Rage of the Room and memory? Yeah, cool. Okay, well, yeah, let's do this. Hopefully this one's a time one. Time one, time one, time one, time one. Yes, absolutely. I can survive the passage of time, please. Who do you think I am? An amateur? God, I mean, they are kind of just flinging cannonballs at me. So just keep running, Lonnie. Just keep running.  It even slowed down time just a little bit before he killed me. Ooh, we live. Okay, what are we at? What are we at? One out of four? Oh, right, we're behind one. So do we have two more in this level? No comment. Yeah, that was heavy. How far is this range? Can you get me over here? Let's find out. Oh, God. Ooh. Cold black coffee is not good. Ooh, Zooey Mama. Ooh, I did not even know there was gonna be a flame there. I missed that on accident. Oh, God, he's gonna start flaming. He's gonna start flaming.  I shouldn't have panicked. Ah, I shouldn't have panicked. This time we'll try not to panic. Look at, see, he just went off. We have time. Okay, now wait until you get to the top. You can do this. There we go. Okay, and now we just gotta get over there without flame man touching us. Okay, we can do this. Ooh, no, no, I was at the stairs.  Oh, no way. I gotta do it all again.  I swear to God. Just gotta wait for the right time.  Run, run, run, run, run, run, run. Yes. Okay, I did not wanna do that again. I think this is the last one of these. I hope it's the last one of these. I don't remember. I think there was two though. So I think this should be the last one. Oh my God, my nerves are high. Without true cause or purpose, abused and murdered their pacific victims, whom they hated for being different. The invaders corrupted the vivid world. The assaulted could not comprehend the mass's brutality. Still, they stayed on, trying to placate their oppressors and recover their past. The cruel interlopers attacked at intervals instead of killing them all at once. The wretched survivors suffered in perpetual fear. Is there a worse fate? Ah, damn. That's cringe. Are they going at different times?  Actually that was a little bit easier.  That one just barely did not miss me, thankfully. Well, that was fun. That was fun. I got to break through the, oh. Crap, train train's coming through, isn't it? God damn. Kill him. Yeah. I get fucked. Whoa. Oh, that house is on fire back there.  I feel like there's historical implications to this part right here based off of like what the caterpillar was saying before this. I don't know enough history to know what that is. So if they have any history buffs in the comment section, can you let me know what the fire on the house means? I'd really appreciate that. Aw. Oh, I didn't think those would do the same thing. God damn. Yay, end of the level. My favorite part of these levels is when it ends. Oh, what is that noise?  Oh.  Come on. Oh, it's too close. Oh, it was too close. It was too close. Oh, no. Oh my God, let me out.  Oh my God. Games are not for the uncoordinated and that would be me. Oh, oh, oh my God. I can't even see. What is this? Just die already. There we go. Now we can just focus on you. There we go.  Does that get you demonetized on YouTube to tell an enemy in the game to KYS? I hope not. This guy deserves it, right? This guy deserves it. Once more, the Shadow Dragon winds along the path. Follow the Dragon Alice. Oh, I see how it goes. Makes perfect sense, really. At least now it does. All right, let's get these puzzle pieces. Three, two, one, speed run. You guys like that one? That was a little bit of movie magic. By that, I mean I sat here for 10 minutes collecting all those pieces, had a slug fight, but I just sped it up and showed you only the parts where I got the cubes. I know I'm really good, right? I think we can get this one in the first try. Look at it. See, because I realized my mistake that I made last time. So, oh, this one might be a little more complicated. Uh, oh, oh no. Now we get it like this and we get it like this. First try.  Now it appears that I can continue my ascent to the peak. She's so real for that, for just saying exactly what's happening. She's just like me for real.   I've been recording for 51 minutes. I feel like I need to finish this level before I can wrap up part eight, because I don't think I'm gonna be complete enough if I don't. So I need to finish this. I don't care how long it takes. I'll cut it into many segments if I have to.  Just to edit this video. Also, I might be getting employed soon. So, I mean, you guys know how I am when I get employed. I just like, content gets harder to make when you have a job. So I wanna at least finish this part. It's not enough that there is. Oh God.   Ooh, secret room.  We gotta go to the secret room and then we'll go help him or whatever. Lovers often exchange a lock up hand to symbolize their vows. Human heart is opened by a vast assortment of keys. Can we get them out of here? Cause I'm just leaving them and they're very well healthy and alive. I don't know. That's messed up to just leave them, I feel like. Oh no. I don't wanna spoil for you what this fight is right here, but I feel like you're all gonna know. Just based off my reaction alone and my unwillingness to tell you. And my heart palpitations, even though you can't hear those. Wait, you know what? Now would be actually a good time to upgrade the teapot cannon. He is quite useful in this fight, actually. Okay. Okay, okay, okay, okay, okay, okay. Fine. Come close. I can decide red riding could back work. I know my multiplication tables, two elevens, ice, ice. Really? Persuade me. To remove the obstruction, wake the frog and empty his belly. Wake that? What about its tongue and the prospect of warts? Oh, anyway, how do you know? I imagined how it was done while I was sleeping. Real intelligent right there, sir. You know what? We're not worrying about the teeth right now. We're going up and we are not looking at that. I don't want that. Oh, come on. Nice, okay. And there you go, folks. There it is.  I just, I don't like it. In fact, I might even hate it.  You know what?  X games mode. Oh God.  Oh my, oh my, oh my.   We need, come on. I don't know. We need, we need this up here. Oh, there we go. There we go. There we go. Yes. Okay. Nice. No, no, I wasn't looking. I wasn't looking. I wasn't looking. No, stop. Put me down. Oh no. After that, I need a moment. What is attached to me? Oh my God. No, he's going to kill me.   You know what? Bossing up was a mistake. I'm not going to get any hearts. I literally just, I can't get picked up by this guy.  I remember this fight being easier than this. Oh, this way, this way, this way, this way.  We have to boss up, we have to boss up. He's going to start flaming. He's going to turn on flame mode.  Please just die, please. I would like it if you just died.  We're good. This is a fantastic platform to have him on. The only thing is he's tanky. Can you reach me up here? He can't, can't. He can't. He couldn't reach me up there. I was not going to survive if he could reach me up there dude. Ah, I'm stuck. He might, but let me get my flowers first. Okay. Oh my God. I'm stuck, I'm stuck. I am stuck. Nothing is working guys.  If you were doing the shot marathon challenge right now this is another one because I'm stuck. Wast is working. Nice. And the flowers are gone. Why isn't the remote working?  I'm not playing this without the remote dude. Oh great. Okay. There we go. Oh my God. Jesus Christ. I did not want to have to use was for the rest of this game. We are an hour under recording. I don't remember how close I am to the end of this level actually. We do still have two radula rooms in this level though. So I'm skeptical. Nice. Wonderful. Is this guy going to get to get out though? No. I guess he's just going to watch me leave.  All right. Oh, here's the radula room. Nice. This is probably going to be a killer be killed. This is going to take a little while. Oh really? This one's kind of pretty though. I like how dark it is. I guess pretty sick. Ooh, actually I really liked the vibe to this one. It feels like a nightmare or a dream. I like the music in this too. Okay. Nice. That was a short radula room. Very beautiful. You never cease to remain. Aw. Thank you Cheshire. One more radula room then maybe? We beat the part that I was dreading though. I was really dreading that colossal ruin because I knew it was coming. And if we don't get the next radula room, that's fine. Like I said, I'm doing a final video for all that. So why is there a skull painted there? What horrors be on my comprehension lie here? Well, you're fine. You're well within my comprehension actually. So are you. Only the savage you regard the endurance of pain is the mission of the world. God, there's a lot of little guys in cages here. I feel like we should take care of that. Easy, easy.   Okay, but as long as we can keep it aimed on him, I think we're okay. Like we could definitely kill this guy as soon as we can. We know his weak point and that's enough. Now it's just up to killing you guys. And then they give us these guys, I'm tired of, I'm tired of you guys. At a certain point, you just get tired of fighting the same villains over and over and over again.   Hope you weapon of the year, hobby horse. Love you bestie. No way.   That's Aunt Booby. Does that count? I don't feel like it doesn't. It's clearly an aunt. Does that mean this aunt lady was encased? Nah, I think she's too big for that. Painting level? Yep, okay. A restless seeker on private business arrived in the misery infested land. She, despite ignorance, uncertainty, and unhappiness in her own life, was not in jaw to see them suffering.  Oh, now the struggle is over. Ah, how am I supposed to get past that? Can I go on above? Is that what it wants me to do? Oh, yes, it did. Cool. Ha ha, cool. Oh wow, thank you, Rock. This is hard, this is hard. Oh, oh, oh. Oh, I hate that. Really?    I truly do.  Okay, okay. Please be the end. Please be the end. Oh, thank you. Thank you so much. Oh wow, that is not rendered. Kind of looks like Borderlands art style, just a little. But I think we are close to the end here. Took us an hour and 16 minutes to get to this point. But in the video, it's probably closer to like maybe 20 minutes. Ooh, that's freaky. I guess that is where I started, huh? Everything in here was like kind of on the inside of this basically ant tower.  Thank you, Catherine Obvious. I can all this way to find a sim in Akron. If I had the time, I'd detail how often you prefer dealing with illusions rather than the real thing. Problems you refuse to deal with don't exist. You deny reality. That's not right. I know what's real. No, then you are now others to tell you what isn't real. Now, come inside. Cool. Very, very cool, really. There is a shattered. This wicked train has ruined nearly all I can recall. And Wonderland will perish completely as I lose my mind. So much has changed. I can't help Wonderland if I can't help myself. Much has changed, but you've got it backwards. Save Wonderland and you may save yourself. The carpenter was on to something, but he was hiding from the real. Your goal is to accept it. Where should I go then? What should I do? The queen must be served as the queen and all her guises must always be served. How can she stem this growing corruption or asses my search? What does she know that I don't? She is someone you once knew and loved. Time changes us all. Not all change is good. Remember that when you find the queen. That was quite pretty. He turned into a little butterfly in my window. Oh. Oi, you there. It's enough of that. Come and wriggle at this, Nick Ellis. Who's she this time, Fred? Holding outside the old lady, muttering about a murder in Threadneedle Street, cursing insects on the national rail road. Had to bring an end, didn't I? Ch-ch-ch-ch, I've managed to herself. Right, now it's time to develop her surely. Gee, that belonged in jail. Who threw it? Where then does she belong? Let's walk her out, Fred. Send her back to Dr. Bambi. He raised Olyell last time I kept her overnight. Oh, what happened? Same night, Jack splattered at the waist of mother's love, was nabbed, forgotten that every outsider mermaid. Yeah, I was taking Alice down, and we meet two coppers walking Jack to the cells. He's mad in the usual eye, never. Wrong bloke nonsense. When he sees Alice, that's a bitch-want-done-it-heels. She screams, yeah, miserable cur. Yeah, leech. Yeah, nag it. Living off another's labor, et cetera, et cetera. I'm admiring her line of inquiry, but suddenly she hits her head, or something, and fades. Couldn't send her home, could I? And Dr. Bambi pitched a fit.  Told him he could have the form, huh? Leave her there alone, make it very much. Good night, Alice. You know the way out. Wait a minute, so when was she in jail? He said it was after the Jack splatter incident. Also, I mean, he's kind of cool, actually. He was like, just copaganda. Anyways, yeah, he's kind of cool. But was that? Okay, wait, I have to piece this together lorically. After the Jack splatter incident, at the mangled mermaid, we ended up going to Wonderland. But as far as I know, we went to Wonderland after we got knocked out. Then we came back to jail, and then maybe we were driven over by our previous nanny? So confused. When was that supposed to take place? Because it was before we got in the jail this time, but we haven't been in jail the entire game. Okay, all right. That's confusing, but we're gonna keep it on going. Main takeaway is we were here before Bambi saved us. Kind of. You see the language.  Kitty. Never a good sign. All right, ooh. They really just let me out, and then I have another episode. Oh, brother. You poor thing. Oh God, can I look into these? I can't.  Oh my goodness. Man, down we go. This level is, wait, I was just in the Alice dress, why are we here? Anyways, this level is beautiful. It's so, so nice. But I have been recording for an hour and 24 minutes. We're gonna go ahead and cut it right here, and then we'll go ahead and play this level in the next episode. It really is so beautiful. Anyways, I hope you guys enjoyed this part of Alice, and if you guys wanna see more, just let me know in the comment section below.  Anyways, hope you guys come back next time. See you guys later. Bye.


Hey, Sandro. Charo. It's been a while. Indeed, it has. I can only stay for a little bit, though, and then I have to go to another meeting. Aw. Does it make sense then to do CRST's stuff earlier in the meeting? No, actually, I'd prefer for you to save it till after I leave. Just for that, it'll be at the beginning. Right, exactly. Let me take a look at it. But Vadim has my update for me. It's about halfway through, but we'll, you know, basically there's the short of it is there's people who are ready to take it on. There's like five different people that are interested in forming a little subgroup. That's fantastic. Let's get started with the meeting. So Vadim, go ahead and give us the latest release updates. There we go. Much better. So there hasn't been much happening in our releases, mostly because we're blocked on multiple ways. The most pressing issue was that Fedora CROS has regressed in stable and testing develop. There was a bug filed for Fedora CROS streams related to network manager and some weird system desetting which prevents it from booting when we pass the master recognition. The fix for this is to revert back to the older Fedora CROS stable that is one from May or from June. I have updated all the night list for 8, for 9 and for 7 and on CI for 7 still fails on this year. So we would need manual confirmation before we cut out a new stable release that will be working or we need to look into something more. This is one of the reasons why we didn't cut the release two weeks ago so that we would make sure. Another news is that Kubernetes would be re-based in for 8 and for 7's branches. We're waiting for the final tags to be added to the PRs and hopefully it would make it into the night list and we'll cut a new for 7 release based on 2020, 10 I think. The largest problem is probably that we still don't have a safe upgrade path from for 7 to for 8. First of all, there are multiple issues and regressions in Cryo which supposed to be fixed and we'll get them in the new release which are affecting OCP as well. And in our case, we have a bug with OVM team where the applications are still getting disrupted more than we expect them to. This is why the CI cannot create an upgrade path and we have no annual way to override this. So we would have to wait or come up with actually a manual way and some known issue that your obligations might be disrupted about like 10% of all the time. Although our target is less than 1%. There has been progress on bare metal IPI. We created an OCD specific version for ironic IPA downloader I think and we have a great chat with bare metal team and I think we had the progress on the actual ironic image. So we would need to land a full request and a promotion PR in release repo and we should have all the bits and pieces necessary for the night list. Once we confirm that all of these are ready, we can port them back to for 8 and for 9. And another interesting issue with Fedora was that they have changed the CLNX profile rules which led to too many stats failing. We have a full request to actually fix that but until then we cannot upgrade CLNX targeted packages in our Fedora cross which leads to inability to update Chilip C which leads to an ability to update a bunch of packages. One of them is network manager 132. So at this point we have to revert back to network manager 130 which has an issue with reverse pointer resolution. So that's an unfortunate casualty while we figure out things with upstream and how to land the fixes and pick them back to for 7. So that's something I will write a known issue about when we cut out a new stable release. I think I mentioned that we have a full request in upstream, Mustafa is looking into this. And I'm hoping it would plan fairly soon because general folks agree on the approach and matter of picking the buttons. And I believe that's all I have for today. Excellent. Any questions on what Vadim covered there? Anyone have any questions or comments? Looks like we're good for that. Thank you Vadim. Moving on to Timothy with Fedora Cora West updates. Actually, sorry, I have a small question. Just that on the various releases under the upgrades from section, there are sometimes some individual letters, you know, F or S, which presumably means something failed or succeeded. And occasionally there are four of them, sometimes there are three of them, and I haven't been able to find anywhere what those actually mean. Well, yes, F means failed, S means succeeded, P is repenting. The exact job. So I have to start them manually. I think I covered this previously, but I can get more into detail. So the way we create an upgrade path is actually make CI run an upgrade from one release to the other. There is some automation which runs upgrades from previous nightly to the latest nightly, but there is no automation which runs this same sort of jobs on stable branches. So I have to pick these myself. Usually I'm guided by latest two releases and the most popular for six from Telemetry. But if you need a specific stuff, just bring me, I can run it, but I can start it. Now, thank you Vadim. With three of them, I originally guessed it was like AWS or, you know, something like that, but individual jobs that I can probably go. Like, in that case, the change log makes a bit more sense. So thank you. Yeah, I'm trying to split them between AWS and GCP just cover all the platforms. We probably could try a vSphere upgrade, but the pass rate would be very low. Again, all that is done health manually, at least I invoke those jobs, you cannot affect them once they started. So if you need a specific edge or to try out a specific platform, sure it can be done. Thank you. Let's any other questions or comments. All right, let's move on then to the Fedora Core OS updates. Hi, I'm from the course team at Red Hat working on Fedora course mostly. So I've linked several issues. So the one of the big thing we fixed recently is around the UEFI booting, especially the live ISO. If you are troubled in the past, booting the live ISO, it should not be fixed in Fedora Core OS. So I don't know. Well, the exact versions are linked into a ticket. I don't know how that impacts OCD directly, but probably for the first boot up node, it will have an impact for the first boot. And we still have one in progress. So booting by firmware's configuration. If you had issues like when we installing nodes with Fedora Core OS and in the past, if you had some kind of issues and probably this is something you've hit before. If you want to take a look and chime in, if you have anything to add on the discussion. Fedora Core OS was live ISO type of trees. So it's essentially the live ISOs are live versions of Fedora Core OS. So it's essentially live system, fully live system Fedora Core OS running from an ISO. But it just booted from an ISO, either be it like a real disk or if you write your ISO onto a USB stick or whatever, it boot up from that. Yeah, so that's one of the issues we fix recently and one progress. Another thing in progress that is coming up is third platform console default changes. So the goal is we're working on making it possible to have third platform, different console configuration per platform. So that will make sure that on AWS, you get the version of the console that you need to get on AWS. And on Bermuda, you get the version of the console that works best in Bermuda. And for each different platform, we have different defaults. And this is work in progress. So it's not there yet. But if you have like anything interesting, if you think that we should use a specific version of the specific configuration for the console for Bermuda or whatever, feel free to chime in into the issue. Okay, so that's like two biggest items. Then we have a couple of deadlocks and a couple of issues with the kernel infrastructure that have been reported to us. So that might be of interest to, if you encoded those, hopefully you won't yet because you don't probably don't have the same kernel yet on OKG. So I'm just thinking there, then there in case you have something that looks like this and you can chime in too. And yeah, and I forgot, we are really, really close to have a 64 artifacts now. So we essentially have them available. It's, you know, don't have like the nice download page and everything on the website, but it's there and it should be working. So right now we have testing release. I don't think we have the stable release yet. Oh yeah, maybe we have it do have a stable of this. Maybe we already have one. Yeah, we just have one. Right now. So we've just had one stable release for HR 64. So you should be able to try them. We have a BSA buys we have very little we have a lot of stuff open stock images or. So yeah, here's 64 is definitely coming to federal chorus. It's there. Yeah, and the remaining things are mostly cosmetic like me sure that it's listed on the website and anything like that. So that's just coming up right away. So yeah, let's just link this one there into. I've already linked it. No. Builds are there. I'm updating the notes at the same time to make sure I don't forget. Oops, where it is. And the. Okay, and one last item that I want to point out is, if you have only fiber channel or fiber channel of the internet connections on very little nodes. For example, you might currently have no way to get a date work and you did with working. We have looked, we are looking into that to see if we need to add by default. Well, including the image, any other utilities to make fiber channel free working. On federal chorus. And so yeah, if you're interested in that if that's something that just raising interesting for you in your use case on their middle mostly. Again, feel free to chime in and. And we'll on the discussion. And that should be it for me. I think that's like the top items from federal chorus formula two weeks. We've got a couple of questions in the chat channel. Okay. Just go ahead and articulate your questions for people watching the video. Okay, sure. I mentioned the F cause sports. Live ISO stuff I didn't know that that was the thing doesn't support like hybrid persistence type stuff as well like if you put it onto USB stick that bar home would automatically be provisioned in the remaining space and you could use it. So it's it's not automatically done, but you can do it. And if either you use the space you have on the USB stick, but it's probably not what you want, but most probably you want to do what you want to do is use the disk on the system to like persist data. So best slash bar, essentially, and you can do that. So the live ISO is a fully. We're keen federal chorus environment and he is running ignition. So if on first boots.  It's for it. And it will do and so if you want to like say run. So you can even like in bed in each and each and each and can fix into the ISO and it will be picked up by addition at first boot and then applied and so let's say you want to partition slash bar and put slash bar on the persistent disk and keep running the live ISO as a pressure pressure in like a familiar environment, you can do that. And let's say when you reboot, then you will get the live ISO again so you have to figure out like another way to do updates. In this case, if you use it like that, the main use case for that kind of stuff. That kind of way of working is PXE booting well, where you just like you date the version of federal chorus directly on the server and you will reboot your notes and they just simply rebooted to a new version. I see so it's for bare metal provisioning basically. You, you can either use it to provision the moveable to install federal chorus onto nodes, because you have fully working environment and you can run chorus install my new leader, or automatically the ignition, or you all kind of arguments directly provided to the kernel on the command line during the live ISO boot up, or you can directly use that as an environment, it's possible. But yes, probably better use, well better feed it for your bare metal use case, you're right. Excellent. And any other further questions or comments about that. Let's move on now to docs update. Brian, go ahead and take it away. Okay, so we've been working on updating OK DIO. If anyone has actually tried to update the main site, you'll understand that it's not trivial and the learning curve to understand the various packages that make up that and you really do need to be a full front end developer to actually achieve that. So what we've done is we've, let me actually share. We've actually set up a beta branch. Can you see that? Yep. Okay, we've actually set up a beta branch within the main repo. And this has now been switched over to use MK docs. And you'll see there's a link on the side, which actually takes you to the beta site. So this is being rendered using GitHub pages. And on a GitHub push, you get all of the automation to build and update the site. So when we accept a pull request or a commit on to the branch, it will actually automatically update the documentation. So there's no infrastructure needed within Red Hat or anywhere else. The site is fully mocked down. So even the home page now is being fully mocked down. It means that we don't have all the fancy animations that's on the current site, but in terms of updating it, it is much simpler. We also have a much better navigation where we've got the high level site navigation here on the left and an in page navigation on the right. So you can just click and navigate round based on the headings one, two and three. This is all sort of automated. If I look at the site, it's fully, fully responsive. So if I come onto a phone, you'll see that the menus vanish and they sort of switch up to here and I can get to the in page navigation. So it's a fully responsive design. It also will flip between light and dark mode depending on your browser and if your system settings allow that whenever you open it, it should adopt to whatever your system settings are. So the basic site is there and I'm not precious about this if anybody thinks there's a better color scheme or anything like that. It's fantastic. It is. It's fantastic. And I think we can live without the animation. Okay, the only thing that I think honestly, the only thing that make it better is if we got rid of the weird gradient background that's behind some of the imagery. Because ironically, it makes it less readable. Like if you go look at the title where you see there it says community distribution of powers red hat open shift. Like it's actually a little hard for me to read it because of the background reducing the contrast. Okay, I put this in I mean the homepage is got some custom templates just to make it a little bit so I know Diana was very keen to keep a rocket man in. The rocket man's fine. I just really have a problem with the weird bubbly hexagon background pattern thing. Yeah, which is which is just from the outside. I'm happy to take that out. Other than that, it is solid. I just wanted to add a little bit more interest rather than having solid. You'll see that as we get into the if we get into the main site. We lose all of that. So it just becomes. Yeah, these are the guys so if we look at the bad ends. And we've got his pictures. Yeah. So it's all and you've got navigation, the search again, I can type v sphere and it just pops up and then these are all the places v sphere. And it appears so we have a sort of an automatic search index on the side as well. So if you want to find stuff. And what I have done in the community section if you're interested, I started putting documentation about how the markdown. We use standard markdown, but we also use an extension library so we can do things like have these sort of information boxes. We can put tabs in so you can see that we can actually switch tabs and just add a little bit more control and information. Tables co blocks, we can actually put line numbers in or leave it out. It's got the copy paste automatically in there. The other thing I've done is I've added a spell checker. So whenever we push something, we automatically do a full spell check and it is set to US English. So I know you guys use your simplified version of English, not real English. But I have gone and adopted US English as the standard default. So everybody needs to sort of use US English. If you want to, on a page, you can actually put a comment in which you can add words. So if you've got technical words, you can add them in to pass a spell checker. We'll not publish if there's spell checking errors or if there is link checking errors. The other thing we do is a full link checker on publish. So again, we should never have broken links or bad spelling within the content. So it's there. Go play with it. As I say, it's in the beta branch on the main GitHub repo. I'm now looking at the content and trying to sort of beef up the content and get there. One thing that we've talked about is on the install page, maybe moving some of the content from the OKD readme. So this is on the OKD main repo. There's some quite useful information within the readme there. And some of this we think should be part of the OKD documentation rather than being in this readme. And there we go. That's that's it. Yeah, I wanted to actually loop Vadim in on this. So Vadim, the readme from the repo has sort of a mix of a lot of different aspects, right? So installation and the releases, nightlies and stuff like that. So the thought was that we would break this up a little bit and make the readme more of just a true readme of this is the project and then have links to the various OKD.io web pages for those particular topics. Do you have any concerns about that? This has been kind of your... No, that sounds very good. Just not sure which site do people first encounter. Do they look for OKD.io or do they go to GitHub and figure out that it's OKD. So I think there should be some text, very brief description on both sides so that people would not get confused. But other than that, we definitely should have looked at a bunch of text from readme's way over look. Excellent. Excellent. All right. Any other questions or comments for Brian? And this is awesome work, man. Awesome. Absolutely fantastic. Brian, what's your sense in terms of timeline? Do you think a month, two months? Oh, I'm thinking a fortnight.  Yeah, because I mean, I think the sooner that we can actually make this move, I'm hoping people will pick up this banner and actually contribute content. I mean, for example, the COC, we can actually move it, move into here as well. I mean, I actually do have COC section in there, but I think that we can actually add... And make this a much more dynamic site. Hopefully it's easy enough to use now. So if we have like a headline on build X is broken, please use a previous version. We could actually put that on the front page and have sort of like a headline section and it can be updated almost weekly as we need to. And as people get stuck and they figure it out, they can just go and throw something on the site because it's really simple to do now. There's no sort of steep learning curve. I think Mike appreciated just how horrible it is adding content with his guides. So hopefully it all just makes sense and sees you now. But yeah, I'm hoping to have the core of the reorganization in the pages in place within the next two weeks. So then we can maybe this call in two weeks time. We can have a look through and actually make make take the decision needs more work or let's switch it live now. I think a primary thing we'll be getting that read me parsed out and that text that Vadim mentioned. That's going to be a necessity. And once we have that, I think it's safe to do the other stuff sort of as needed. Yeah, Brian. Yeah, no, it looks, it looks fantastic. And I'm really happy that you made this switch. We might consider at like a lower level of priority after the substance that people were talking about earlier. We should make sure that we get the color scheme reasonable because when I look at it, it you're sort of lighter background in the the middle looks like it has sort of a bluish tinge to it.  You know, the human eye can't focus simultaneously on both red and blue because they're opposite to the spectrum. But I'm just saying that we might look at the, the color balance and the accents and things like that as a, but you know, I'm happy to defer that to the docs working group. Yeah, I say, I'm not precious. I just picked colors that were on the existing sites. And a lot of thought didn't go into it. So I'm very happy for people to go and make changes or suggest changes. Yeah. Oh, sure. Well, I guess from the red hat side, you know, we like red. But that doesn't mean that we should destroy everybody's eyes. You know, in the process. Yeah. So we can use the colors incorporated into the rocket man. Right. And just sort of. But I'm guessing the, like, is it, is it themed? Is there like, I haven't looked at how hard is changed the template for colors. I've broken them all out. So it's really easy. If you go and look at the. There's a CSS folder in the docs folder. It's in there. So every color has got a CSS variable name against it. So we can just go and change them. And there's a switch for changing. Right. So that people, we need to let people know that that's there. All right, I do want to move on because we do have a full agenda and some, we have some guests here. So I need to get through some of the other things that we've got. I'm real briefly. I'm noticing in the channels that there's a lot of folks asking questions without providing a lot of context. Does anyone asked us in the docs group and folks who are sure is there like a Kubernetes based how to ask questions document that you're aware of. Like I know there's that one site that's been around for years. That's like how to ask questions. Does anyone know of a good text that we can point to or build upon about how folks should ask questions when they are. You know, seeking help in the channels or in a discussion item or and Vadim started to put some stuff together, which was really helpful. And maybe we'll just put that into a document if we don't know of anything else. It's just for information. I do plan to have that page on OKD.io so we can actually use that as a way to point people. Excellent. Very cool. It doesn't sound like there's a Kubernetes specific page. So I think we'll just build on what Vadim has and the docs working group can tackle that next week. We'll just add those items. Vadim came up with a list a couple weeks ago. We'll just put those items together and then put that in a format that can be put into the description of the Slack channel. And then at the top of the Google, well, in the Slack channel, then we're going to change the Google group to actually point to the discussion section. And then in the discussion section, we can put that there and have folks provide that information. Vadim, that can be done. There's templates in the discussion section as well, right? You can have templated answers, but I don't think these are shared across all order. I have a list of mine. And I'm not sure how to share them. These are saved in my account. Get up might be weird. All right. Just wanted to throw that out there. Docs group will talk about that a little bit more. And training materials for Docs support resource. That was basically docs about docs. And so we answered that a little bit at the last docs meeting. And we'll be talking more about that at this next meeting. Repo issues. Is there anything that people want to pull out of the repo to discuss real quick from the issue section of the repo? Any actual issues? Vadim, I know you've been pushing a lot of stuff to discussion because a lot of it was discussion oriented and you covered a lot of issues at the beginning here. But anything you want to bring to our attention? No, I think I haven't seen anything super interesting or at least something which cannot be covered with a log bundle. I wanted to discuss the whole procedure when I learned that GitHub has discussions. So I was thinking that would be a great place to figure out what this issue is about. And then you can move it back to issues. Now it turns out GitHub has a label called bug. And if you mark it as a bug, that will give you a brand new tab outside right nearby between issues and discussions. And it's going to be a dedicated place for bugs. So you can have three places where you can figure out if it's a bug or not. I don't know if I should go on with moving issues to discussions or should we keep them as issues and just mark them as bugs? My head's getting on it, honestly. Yeah, what do folks think? I'm surprised that there's not going to be a third option. I'm curious what their thought process is for doing that. Probably because a lot of people use the issues with a bug label or something like that anyway. So they're thinking, oh, let's make it easier for them. But we kind of came up with our own thing in the meantime. I don't know. Honestly, like I've been keeping an eye on the discussion sections and watching what Vadim moves in there. A lot of it isn't really like a bug bug, you know, it's not like it's just a bunch of people over and over having trouble deploying their clusters, which is understandable because it's really hard, but it kind of illustrates how far we have to go here. My idea was that if we figure out that it's an actual Fedora-Cora's bug in a discussion, we close the discussion and reopen the bug. But this happened maybe twice. Apparently, that's not the way to go. Conversely, like not everybody should be able to say that it's a bug, right? Like to me, like the normal usage that I used to see is that anybody can raise an issue and then after discussion decide whether or not it's a bug. And then I guess a discussion would then be something that people don't even think is an issue. It's just they want to talk about things, maybe propose new things or whatever. So I could see having those three categories, but definitely we would have to tell people how to use them. I don't think they went into it that. No, it's going to say conversely to what Vadim was saying about Fedora-Cora's bugs. If we surface bugs in OpenShift components, those bugs need to get brought back into like bugzilla.redhat or somehow need to make it to the components. So I can guarantee you that aside from like Vadim and myself and probably anyone else on this call, none of those OpenShift engineers are looking at the OKD-like issues list. It is also hard to figure out because oftentimes I do notice that a lot of bugs that I run into personally already are tracking and being fixed, but it's very hard to figure that out from the outside looking at. Yeah, I don't think that's necessarily really secure, but I think other people are having that problem as well. We could probably go a lot further to closing a lot of these things out quickly. If we had some way, us as external people, not just, you know, those of us inside of the red hat bubble to be able to triage that kind of stuff. I don't know how to bridge this gap. This is still a question I would like to see answered. If we could teach the community how to get more communication with the red hat people who are working on OCP, I know that if there were bugs getting into bugzilla, I know we're migrating to JIRA in the future and everything, but if we had bugs going into that pipeline, then you would have people responding more quickly, at least from people who are working on the code. I think now it's just there's this gap that we need to kind of like fill up. Okay, I want to table this discussion because we've got 20 minutes left and we have a guest and we have a couple of other important items that I wanted to do. But let's put this on the agenda for the next meeting and try to come up with an actual plan for how to move folks around. Vadim, do you know of a resource for must understanding and parsing must gather? Like if we can, if we can get more people understanding how to work with must gather, then we might be able to get through these things that get posted much better. I don't think we have a guide where to look first in the must gather era.  But then it depends on on basically specific components like. API server issues are very broke can be out it can be just simply bonus starting so. For a start you can have. I think we have a short guide I'll try to find it and well open source it just like we should have. I didn't want to spend too much time on that but I think I noticed there's a lot of stuff that if, if we can get through the must gatherers of community members can get through the must gatherers. We can save Vadim and a lot of other folks a lot of time. And we're incisely answer people I think. Okay, I'm going to breeze through these really quick. Can I ask a quick question about the must gatherers. I don't I don't know if this is ever something the community would accept but like is it like would it ever be possible for us to create the kind of service where someone could like. Make a must gather and be able to like drop it in a place where we can review later we can't do that but. GDPR and CC is with killers. That's progress. So, even if we ask people like up front to like, you know, to upload their content or whatever with some sort of proviso. That doesn't get us out of like GDPR and whatnot. Yeah, because they are uploading and they are controlling the results. They have to upload it to some servers of which they can. All right, well, let's move on because I do want to get to this other stuff. The user questionnaire the group decided to the docs group decided to user questionnaire would be great. And at this meeting we talked about it last time and so user questionnaire is up and posted. Dreeti posted a response with some great suggestions. If other folks can chime in the goal is to get the survey out to okay to users. What's missing?  What do they like the most, etc. So, check that out. Code ready containers subgroup. We've got Neil, Daniel, Dreeti, myself, Charo, Brian and anyone else want to be on that anyone else on the call who wants to be part of that subgroup. That's helping maintain code ready containers. Your name in the chat or speak up. Okay, Bruce is interested as well. Okay, we'll add your name. Okay, very cool. And we're in the process of navigating that out. Basically, I think Neil and Daniel are going to be sort of the leads on this. And yeah, it looks like we got a fair amount of people that are interested. So that's awesome. And that's that was Diane's measure of success for the subgroup was that there were people interested to obtain it. Vadim answered the operator questions. Please check those out. We won't go over them here but there's some clarity about operators and we'll talk about that at the next meeting. New business was a migration path outline. Would it be possible Vadim for us to create a simple table that we could direct people to because it seems like a lot of questions are can I upgrade from this version to this version etc. Is it too complex for that or do you think we'd be able to pull it off. For OCP, we have a full blown service which gives you an upgrade path. For OCP, it's a bit untrivial. I mean, if you can parse JSON manually, we have an endpoint but visualizing this is a bit tricky. So I think we have like a static dot type diagram, which can give you the edges because we don't use any channels that's much easier than OCP. Visualization of this is always a tricky question. I think I can find this diagram which can be rebuilt dynamically. I'll put an action item for myself. Awesome. Thank you. So now I want to move on to our guest Sandra, who is here to talk a little bit. And did anyone else show up or is it just you or which topic.  There are a few people here, it's me, Michal and Fabian Deutsch here. I would suggest to get Fabian introducing the subject. Okay. Our discussion item is because of a desire for OKD to be more stable or the switch to Cupid for virtualization, the upstream of Red Hat's virtualization offering. And we received an email about about that and invited folks to come here and talk about it. Yeah, I see that Fabian dropped it. Okay. So you probably know that within OpenShift we are shipping OpenShift virtualization and we have not really a fully integrated solution corresponding to that based on OKD. We started trying to get Cupid running on top of OKD while ago, and things are improved over the past few months. And now we would like to see if there is interest in getting things more integrated and make Cupid like a special interest group within the OKD project providing virtualization on top of OKD. I'd like to see that for sure. Like, it's a very interesting thing to me and I think one of the bigger weaknesses of Kubernetes as a whole is, you know, how poor it is at doing, you know, what people tend to expect for virtualization. I feel like overt and OKD are complementary in this regard and bringing them closer together can only lead to a better solution. So the thought would be that there would be like a subgroup, like a working group, a subworking group that would focus on this with maybe some Red Hat folks and some OKD folks. Is that what the general thinking is? Yeah, I think so. The idea is to get the community involved in this process and getting more closer to providing something that can be tested by the, for example, for the overall community to see what's the future and getting more in touch on what will happen. For example, with Rev and OpenShift Virtualization, it will help getting more understanding about the differences and the possibilities that OKD can provide in that area. Excellent. This work on multiple sort of different backgrounds because obviously OKD rugs on cloud. I mean, I think we've got a fairly large vSphere population. I run over it, but I think majority tend to run vSphere and then obviously we've got some bare metal. What is the dependency on the underlying platform on the virtualization layer? I would expect that people that want to run virtualization on top of OKD are going to install on bare metal. That's the expectation. Despite I think that also running on nested virtualization will work with one level of nesting. I think that there's nothing really specific that we require from the OKD installer for that. The other thing is that I remember reading this in the OpenShift documentation. I don't know if this is still true, but if you pair OpenShift container platform running the OpenShift virtualization module on top of RedAd virtualization, you can still orchestrate VMs from the OpenShift interface. They just get provisioned through Rev. That means that you get the ability to do direct virtualization management through the OpenShift API for Rev. So you get an open stack, cloudy, superscalar type provisioning API combined with the more traditional virtualization resource management interface and API of Overt with one solution. Yeah, we got an Overt conference today and Gal Zeidman from my team presented the integration between OKD and Overt in these terms. So I added a link to the agenda to that presentation and I would suggest to have a look. The integration works pretty well. So I think that on that side we are already in a good point. Here the proposal is kind of different. It's not really having OKD more integrated to Overt, but providing an alternative to Overt itself, which is running Covert on top of OKD. Yeah, my understanding to those like with Covert, especially if we're able to like use that as the catalyst or whatever the substrate, then you can run OpenShift on OpenShift basically, right? Oh my God, I don't want to think about that. The only real problem, actually it's not the only real problem, but the biggest problem with OpenShift virtualization, at least from my perspective, like I played with it a little bit at some demos and whatnot, is that it's too hard to work with. Like it is extremely alien to someone who's more used to like how the Overt UI works and how virtual machines tend to be managed that way, how provisioning works with that. Like I would class OpenShift virtualization closer to OpenStack rather than closer to Overt, whereas like say something along the lines of what's it called? Harvester. Harvester is closer to Overt than it is to OpenStack in terms of how virtual machine management works, and they're both using CubeBird. So like at least having used Overt and OKD, like I, if I wanted to move from Overt to OKD, I think a prerequisite would be some kind of UX migration that makes it so people who are working that way can still continue to function in an OpenShift world, and I don't think we're there yet. Maybe we will be someday, I don't know, but that's really the big gap that I see is that people who work the VMware over Rev style of virtual machine stuff basically have no home in OpenShift virtualization. Okay, let's see if we have any questions that were there. No, mostly discussion in the discussion. I just, yeah, go ahead. Sorry, Jimmy. I just want to add a side note about some of the tech behind this too, if people are curious. So like, you know, in OpenShift now we have a CubeBird cloud provider, you know, like machine API provider that we've been working on for a while. I'm not sure how up to date that is, but recently Apple has come to the cluster API community and they've put a lot of people behind trying to create a cluster, a full cluster API provider for CubeBird. And I know that our Red Hat team that's been working on CubeBird is now like kind of linking up with some of these Apple people to help maybe see if we can bridge the gap between the machine API provider that we have now for CubeBird, and what Apple wants to do in the, yeah, yes, Neil, Apple wants to do with CubeBird in the upstream. Like, so in the cluster API project, it seems that Apple is very curious about building and automating clusters of Kubernetes on top of CubeBird, you know, Kubernetes clusters basically. They want to, they want to put a lot into that. And I know that they had been looking at the OpenShift machine API provider because that was the only thing out there for a while, but it's very OpenShift specific. It doesn't work with the cluster API pieces. So another kind of interesting tidbit to this that I think will probably bear a lot of fruit over the next year or so. Do you think that the, I can't believe what I'm saying, do you think the Apple folks might be interested in coming with us in OKD to try these kinds of things? Because like, if we're heading down this direction, it would be interesting to have them involved to, like, sync up and collaborate to, like, working with the Red Hat OCP folks, you know, the CubeBird folks at the Red Hat teams and like, you know, generally like making OKD and OpenShift work this way for them. I mean, that's a great question, you know, like I talked with some of the Apple folks and I talked with some of the Red Hat folks and basically made some introductions and tried to hook them up because I don't work on CubeBird, like, specifically. My impression is that Apple is really curious to get this cluster API provider running and they would love to have Red Hats help working on it. So I know those two groups are, you know, there's some communication happening there. I don't have my nose in the middle of it to know really if, like, could they be, could Apple be convinced to do this all on OKD or something? Like, that would be really cool. Do you still have those contexts where you could? Yeah, yeah. I mean, Apple's still coming to the cluster API. Like, I could continue this conversation with them and see if we can maybe convince them to come here or something. Let's do that as much as my brain hurts a little bit from thinking about this. Yeah. All right. We've got three minutes left. So let's do a sub working group on this. I think it would be great to have a sub working group on this. We'll get the Red Hat folks, Sandro, anyone else that's interested. And then folks here, OKD folks, I'll send something out over the working group, Google group email list. And then we'll get volunteers for that and actually solidify this as a project. So it's a great offering. And then Mike will reach out to Apple folks and let them know that we're starting this as a sub project and invite them. Maybe they'll be interested. We have three minutes left. Someone wanted, someone asked, I didn't want to get to this because I know it's, we want to be fair to everyone in terms of access. Someone asked about changing the meeting time to support basically folks that are in Europe and Middle East and Africa. This is a little bit late. This is so it starts at 1pm for me. We've got some other folks where this is starting at 9am, like I think it's 9am for Diane. I don't know that we can go. What are people's thoughts? I don't want to direct this conversation. What are people's thoughts about going earlier? I don't think I can go any earlier. Like my days are already kind of sandwiched hard as it is. Like I front hall most of my community meetings through the first half of the week and then the latter half of the week is when I actually get to do other things. And like some of y'all have seen my calendars like my Mondays and Tuesdays are basically chock full and I basically don't have any more free time left. So I don't think I can really move it anymore. Even though, and like the West Coast folks, I don't think Diane can get up earlier. I don't think she wants to get up earlier. I'm at the same time zone as Diane. We're actually not that far from each other and it is actually currently at 10 because of daylight savings time. But then I guess October, whenever we flip back to standard time, it'll go to 9. And I wouldn't be able to make it any earlier. Diane said quite a while ago that it was impossible negotiating a time in the redhead calendar to get it somewhere, which makes it really hard to move. And for folks that don't know Vadim, this is what like going on 6pm for you now, is that right? That's like eight. It's acceptable moving it later would be very bad. Moving earlier might might make conflict with my page of meetings. I'm fine with the time and I can understand that some folks might not be able to make it. Make sure someone from you can make him to one of these meetings and that means they could hit me or Christian beforehand so we can pass the information and then watch the recording.  Yeah, what I suggest is if like if there is enough interest to have another meeting. Yeah, because like that sort of fragments things. I'm hoping we can avoid that. There's 24 time zones plus. It's impossible to find anytime that works. You know, like, there are more than 24 time zones. There's enough in the form. I know that I was being already already have a documentation music. So we're really spread. Yeah. All right, let's, I think we're going to stick with where we are for now. This is, I don't mean I understand that this for some folks that might be difficult. I just wanted to just pointed out that it's 1130 there. We'll keep it here for now and we'll come up with a communication mechanism to make sure that people get the recordings. After the fact very quickly and that people who have input into meetings can get input to point people and their ideas across via point people if they can't make it. I think that's our best compromise. Yes, yes, that would be very helpful. Okay, awesome. Okay, folks, we are over right now. So I guess it's a good time to end. And thank you so much. This is a hugely productive meeting. And I'll get the video up as soon as possible. And I'll talk to you all soon. Thank you. Thank you. Bye.


As introduced, I'm Eckhard Gaul. I'm the head of the School of Mechanical Engineering here at Purdue, and started pretty much at a similar time as Bill, both academically, but also as a head, and really have been enjoying this position, moving the schools forward. But today, it's my distinct pleasure to introduce to you Professor Adrian Buganza Tepole. Adrian got his BS from the University of the Pan-Americana in 2010, then a master's in 2012, and a PhD in 2015. Both of those are graduate degrees from Stanford. So he moved to the US after that, after his bachelor. Then switched from Stanford to Harvard for a year to be a postdoc, and started at Purdue in 2016 as an assistant professor. So I like to go through these years, because you see the rapid progression of his career and how he moved through the system. So in 21, just this August, he was now promoted to associate professor after being and ranked for five years as an assistant professor, so there too, moving ahead quickly, and certainly very deservingly so. So now he is an associate professor, and he's part of our celebrating associate professor, which, of course, is really a nice event hosted by the college to really bring out the contributions of our associate professor. His research, Adrian's research, focuses on engineering mechanics with applications to medicine. So there's an overlap maybe to somewhat that she mentioned earlier, so overlap with biomedical engineering. But in particular, he advances computational mechanics methods and tools, and then makes these tools and methods available to clinicians for real-time surgery planning and execution, as well as for long-term treatments after surgical procedures, evolving skin and mechanical cues. His work is rooted in computational mechanics, incorporating experimental tissue biomechanics and 3D imaging analysis on animal and human subjects. Others have described his research work as innovative, cutting-edge, and real-world impact. For this type of research, he has attracted significant funding from various agencies, including NSF and NIH, as well as from industry. And he has been very productive, as you can imagine, to publishing, disseminating these results, considering his rapid progression in promotion and other activities. But on top of all of this, I would like to mention that he's an effective and innovative instructor. For example, he has incorporated innovative computational simulations and exercises into some of our basic courses, even like ME 270, which is statics, ME 274 Dynamics, but then later on also in the course of introduction to finite element analysis. And that's a really great contribution to the school using what you learn maybe from research to incorporate in your classes. So these curricular developments include Python coding, data visualization, and data curation. On a personal note, I would like to mention that he's always eager and willing to help the school, which is greatly appreciated if you're ahead of the school. He has served as the representative of our assistant professors, while he was assistant professors. And now he got promoted, and he had never nothing else to do than to immediately volunteer as well as being elected by the associate professor to represent the associate professors. Now, on our ME leadership team, that meets once a month. And his input there is really valuable. I can always count on him, and I appreciate a lot. So with that, I will hand it over to Adrian. Adrian, we're looking forward to your presentation. Thank you very much. Thanks so much for the introduction. I'm really humbled to be here. I'm sorry I cannot be there in person. But hopefully, I can give you a little bit of more details on top of what Eckhart has said. But first of all, I think following more of what Chihuan was saying, I think the first thing would be to really thank everybody that has supported me in the five years that I've been at Purdue. I think that is really the secret sauce. I don't think it's so much what I bring. Obviously, I work hard, but we all work hard. But I think the secret sauce is Purdue itself. I think the environment that has created for assistant professors is just perfect for success. So I'll give you a little bit of a background of where my trajectory and then more details on the research and teaching. I think that's kind of how I prepared the presentation. So a little bit about me. Originally from Córdoba in Mexico, so southeast of Mexico, you can see the little star there in the map. And then I moved for my undergrad to Mexico City. I was in Mexico City for five years. So I did my undergrad there, and then I was a high school teacher in Mexico City. So I knew that I wanted to stay in academia from that point. Then I came to the US in 2010. I did my master's and PhD at Stanford. So I was there for five years. Then I did a very short postdoc. So I moved across the country, and I was in Boston for one year between 2015 and 2016. And then I moved to Purdue in 2016, where I have been for the past five and a half years or so. So what do I do in terms of research? I would say my lab has two main thrusts. One is incorporating mechanics and machine learning. That's one big area that I focus on. And then the other one is trying to incorporate mechanics with biology for biomedical applications or mechanics plus mechanobiology. And I think those two have been pretty much the core of my research in these past five years. And typically, I've been working problems that tend to do with skins or wound healing, pressure ulcers, growing skin. And that's just because it's a really good model system. It's easily accessible. So you can image it without complicated imaging setups. You don't need MRI. Necessarily, you can do 3D pictures, for example. You can have tissues. So it's just very convenient as a model system. And that's not the only tissue that I've been working on, but I think that's definitely the one that I have used mostly as a model system. For different applications, for example, wound healing and pressure ulcers, skin growth to a growing skin, skin graft, and reconstructive surgery. So I'm going to talk a little bit about just one of them, which is the reconstructive surgery. And there is some why I want to highlight it, is because I'm kind of like Chihuahua. And I think one of the motivations for me is to try to do work that has some real-world impact. And this project I really, really like, because it's really connected to what physicians do. So for example, it is one case where you can have a patient that is going to undergo some surgery because he needs to replace that scar. And he needs to grow a skin in order to have new skin to replace that scar. So we have 3D imaging analysis to get that type of geometry of the patient before the surgery and then also during and after the surgery. And based on that, we can create patient-specific models that we can use to simulate what the formation of the tissue would be and try to anticipate where you have complications. This is a little bit of how we use machine learning to then try to replace the usual computational tools. So typically we'll run a finite element simulation like it's shown in the slide, but that usually requires a lot of computational power. So it's not particularly good for doing things like optimization or uncertainty analysis where you want to get an idea of, what's the most dangerous place or where do you expect that you will have problems for wound healing. And so replacing the finite element software with some machine learning meta model is usually good for doing that type of uncertainty or optimization problem. So here we were able to determine the regions that were more at risk and actually indeed, the two regions that are highlighted in our analysis actually were the ones that had slight delay in wound healing, but everything was all right at the end. So then we moved a little bit to sort of back from the patient-specific case to try to do some more genetic simulations. So these are common flaps that surgeons decide to use. They have names. So this one is called the advancement flap. This one is called the rotation flap and this one is called the transposition flap. And so we were interested in again, trying to replace these simulations with some machine learning meta model and then trying to use the meta model to go optimization. So that's sort of what we were trying to do here. So going from the basic designs to try to optimize the surgery and then trying to use that information and then going back to the patient-specific cases where we can do the same pipeline that I was showing before, we have patients. We know what surgery they're going to go through. We can take pictures, get the model and then simulate what the stress distribution will look like in the end. So the optimizations that we do are in terms of mechanics and that's because the mechanical state is related to complications, to wound complications. So it's not, in these simulations at least we are not solving the full couple of problems where we take into account things like inflammation or all the biology that takes place. That is something we are also doing but I would say that is a little bit more basic science at the moment. But in terms of what do we do with the patient-specific simulations because we can take a look at stress and then we don't need to worry about all these other details. We do this based on just basically stress distribution in the tissue. Yeah, and this is what it looks like and this is the actual outcome of the surgery for these two surgeries, these two cases. So that I think it's kind of the, I would say a little bit of flavor of what I do. There's other projects that I've been working on but I don't wanna bore you with the details but things like skin growth, to grow new skin, wound healing applications, doing more sort of basic progress in data-driven and uncertainty analysis of tissue and then applications in reconstructive surgery. That's about what I have for research and then I did want to say one thing about teaching because I also really like teaching and incorporating sort of creative ways of doing teaching. So what I have been doing this semester is I've been teaching the honors section of ME270. And I don't know if anyone in the audience is familiar with Minecraft, any of your kids, if you have kids playing Minecraft or you yourself playing Minecraft. And this is because in some of the service for students at the beginning of the semester, you ask them whether you're interested in, you do get sometimes some video game and I myself like playing video games. So then I thought, oh, why not bring these two together? And so with a group of undergrads, we've coded an elasticity solver, a mesh-free elasticity solver in this video game and we've been doing basically challenges to connect the concepts of 270 and 323 with challenges in this video game. So what I'm showing here, for example, is this barn trust challenge. So they had to build some roof over the barn so such that it didn't break. And then they also had to show me that they could do the analysis by hand. And then this other one that you have here is for a bridge. So that's a beam design challenge. Again, trying to build the structure and then making sure that it doesn't break. So that's one. And then the latest one, so our class on Thursday before Thanksgiving was this group challenge. So we were in the video game and we had a copy of the Eiffel Tower, kind of. And then the goal was to split them in groups and they had to do sort of the supports and then we ran the simulation in the end and then we see hopefully they didn't break. Apparently one student said it broke. I don't think it broke. I think it was close to breaking, but it didn't break. That's it. So that's what I've been doing this semester having fun with ME270. And just to end, I just want to emphasize again the incredible support that I've been having here at Purdue. And in particular, I think special thanks to my direct mentors, Thomas Sigmund, Eric Nauman, and Stuart Bolton and Eckard, the department chair. I think their support, especially toward the end to submit the tenure package and go through the process is really, really appreciated. And I don't have a list of all the people. I mean, there's a lot of colleagues and friends at Purdue who have supported me in these five years. I don't have a complete list, but I wanted to have this special mention to my direct mentors and department chair who were instrumental in the last year, especially during the pandemic and submitting the tenure package and going through the process. And more thanks, I think, to my lab. So all the students, definitely the talent in the group is what makes the work actually happen. Collaborators both at Purdue and outside of Purdue that I can list and then some funding sources. And that's it. That's all I have. So thanks again for giving me this opportunity to talk a little bit about the work that I do. So I guess I have the usual slide. But yeah, I think that's all I have. I'll stop sharing. Great. Thank you very much, Adrian. Really appreciate it. Any questions for Adrian? Maybe I can start out. Adrian, as a mechanic engineer, how do you establish contact with a surgeon to do some of the skin things that you have done on actual patients? I think just cold calling people. BME, for example, does a really good job of connecting. So doing events where the surgeons from IU come to campus or events where colleagues from BME and ME go to IU and have poster sessions or brainstorming sessions. So I think that type of effort is just bringing people together and then just having talk to each other. So I've benefited from that type of setup. Thank you. Anything in the chat? I see a question in the... Yeah, can you see it? Are there any other video games that you are interested in integrating into the classroom? Not at the moment because I don't know how editable they are. And the nice thing with Minecraft, if anybody knows Minecraft, is that it's very easy. There's a lot of sort of well-established methods to edit the game. So it's not like we are hacking the game. The game itself allows for people to code their... They are called mods, they even have a name. So that's why I decided to go with Minecraft. But no, I haven't really looked into other video games. It will be cool. I think it will depend on how easy it is to edit. Okay, thank you. Any other questions? Yes, Will. Adrian, this is Bill Crossley from Arrow on Astral. I actually do a lot of work on optimization myself. So I'm kind of curious about what kind of surrogate models are you using and what advantages are you seeing? Is it a massive speedup? Does it smooth the function? What's making an advantage for your problems? Mostly speedup. Just replacing the simulation that would take the order of hours to something that just takes maybe milliseconds to evaluate. Even if there's some uncertainty associated with the result, you can always use the meta model to do an optimization and then also find maybe points where you don't know much about the function and maybe refine. So you don't have to run as many of the costly simulations. But mostly speedup, I would say. Okay. Let's see. Adrian, what's next? That's one of the standard questions that we have here for our associate professor. What's your plan? What's your goals being in this profession? Difficult, very difficult question. Because I think the short-term challenges are pretty clear because there's research projects that are moving on. I think definitely tackling those. I think I will have a little bit harder time defining like a 10-year or 20-year plan at the moment. I think one plan is that, is to try to figure out more longer term now that I have gone through this first stage. But I think one thing is clear. I definitely want to have impact in real-world applications. So kind of like Ji Huang was saying, I think that is definitely a big motivation to plan things around. And of course, getting promoted to full professor. That's always next for every associate professor. But maybe the last question. What's the background very quickly? This is a new collaborative effort with Dave Humilis, who's the PI on this Institute proposal that was awarded to Purdue and other institutions. But Purdue, Dave Humilis is the PI. It's called the Embryo Institute. And this is work that I'm really excited to continue. So this just got awarded this year. And it's about integrating information from different species, different scales, particularly around morphogenesis type of problem, which is what I'm interested in. And how do we use computational models to do that integration of systems that maybe plans to mammals, to fish. So how do you tie together the rules of life question? And that's kind of what the institute is about. And this is the logo of the institute. Very cool looking. Adrian, thank you very much. Really appreciate it. Thank you. I'm always amazed by the talent that we have at Purdue. So thank you very much for coming for today.


Let's go ahead and stand. Good morning everybody. Welcome to morning prayer. We're so glad you're joining us. As we just enter into the presence of the Lord, I just want to exhort us very briefly with just a few verses from a Psalm of David. In Psalm 57, the context here is a lot of external pressure for David. Saul is after him. He's hiding in the caves and I just want us to look at the posture of David's heart and just sort of grab onto that this morning, no matter what context we're facing in our own individual lives. And in verse seven, David says, my heart is steadfast, oh God. My heart is steadfast. And I will sing. Yes, I will sing praises. Awake, my glory. Awake, harp and lyre. I will awaken the dawn. And I will give thanks to you, O Lord, among the peoples. I will sing praises to you among the nations. For your loving kindness is great to the heavens and your truth to the clouds. Be exalted above the heavens, O God, and let your glory be above all the earth. And so Lord Jesus, we just thank you for this privileged hour to stand and to minister to your heart, to agree with you in your prayers as the great intercessor. And Lord, we just posture our hearts like David. We just say, Lord, we are steadfast, regardless of the context in our individual lives, the external and the internal pressures, regardless God of the challenges of culture and all that we're facing in our nation right now. Lord, we just make a declaration this morning at the altar that our hearts are steadfast as loyal lovers of Jesus and loyal worshipers of the living God. Lord, this morning we awaken the day to the sound of singing. We herald your praises in song and with our instruments this morning. Lord, we just choose, we make a choice to exalt you above all the external and internal pressures of life and culture. Over every circumstance and situation in our life, we just say, Lord, your loving kindness is great. Your truth and your faithfulness, it's unending. And we will exalt you this morning with one voice and one heart that is resolutely immovable in devotion to you and reverence to you in Jesus' name, amen. Hearts are resolute. Our hearts are steadfast this morning to make much of you, Jesus. In every season of the soul, in every context of our pilgrimage, Lord, our hearts are steadfast to make much of you, to exalt you over and above everything. Come what may, Jesus be exalted. Jesus be rightly adored, rightly worshiped. Your name, the highest name, your word, the final word and declaration. Love you, Lord. Love you, Jesus. Jesus. We're going to stay in that posture of worship and reverence and we're going to turn now just a little bit and we're going to go into a first prayer cycle where we're agreeing with this beautiful man and his heart for our city and his people in our city and those cities represented on the livestream this morning. We're going to ask the Lord for a revelation in the knowledge of himself, the knowledge of his beauty and worth to be imparted to us, his people in Kalamazoo and if you have your prayer manuals this morning, you can turn to Revelation chapter one. Revelation chapter one is when John, the apostle John is on the island of Patmos in exile and the Lord breaks in and he gives him a powerful revelation beginning in verse 10. I was in the spirit on the Lord's day and I heard behind me a loud voice like the sound of a trumpet saying right in a book what you see and send it to the seven churches verse 12. Then I turned to see the voice that was speaking with me and having turned I saw seven golden lamb stands and in the middle I saw one like a son of man clothed in a robe reaching to the feet girded across his chest with a golden sash.  His voice was like the sound of many waters and in his right hand he held seven stars and out of his mouth came a sharp two-edged sword. His face was like the sun shining in its strength and when I saw him I fell at his feet like a dead man and he placed his hand on me saying do not be afraid I am the first and the last the living one I was dead and behold I am alive forevermore and I have the keys of death and of Hades and so Lord we thank you for this beautiful revelation of who you are we thank you for your transcendent beauty and holiness conveyed in the written word we thank you Holy Spirit that it is your joy to unveil this beautiful man to the bride of Christ and so we stand in agreement with the longing of your heart God that we would be a people who see and who hear and who respond rightly to the beauty and the worth that you possess so Abba here we are we're knocking and we're seeking and we're asking this morning for the outpouring of a spirit of revelation on your church in Kalamazoo, Michigan every representation God of your beautiful bride in this city and in the cities represented I'm asking Holy Spirit would you open spiritual ears to hear the voice of Jesus that voice like many waters that voice of Holy Spirit like a still small whisper God we're crying out open ears all across the city voice calling us today is the day of salvation to hear the voice comforting us to hear the voice singing over us and quieting us in love to hear the voice of eternal counsel and wisdom Holy Spirit open ears and let us hear the voice of this one we love in Jesus name ears to hear Lord give us ears of leaders and littles alike just everything Lord your voice breaks in and sets the trajectory of a prophetic generation your voice breaks in and turns souls into paws your voice quiets in love your voice shakes and splits the cedars so we're crying out God break in and open ears to hear the voice of Jesus the voice of Holy Spirit today in this chorus transcendent there is none you can compare to you in worth and beauty we love joining the heavenly sanctuary declaring your worth declaring your beauty oh you stand alone you stand alone beloved Abba your son is beautiful we love entering into this realm of beauty glory our voice is a sin you receive it as a precious offering last little bit of time of this privileged hour go back into a time of intercession pastor Garrett shared on Sunday from John chapter nine where Jesus healed the man who was born blind by spitting and putting mud on his eye creating quite the controversy with the religious leaders and one of the ways that Jesus is glorified and made much of in our cities and in our homes is through the outpouring of his power unto healing and so we just want to stand in the gap this morning and just cry out for the release of his healing power in his church in Kalamazoo healing for physical bodies healing for minds healings for broken hearts we're just gonna lean in now because it is his heart and by healing God is glorified he is seen and he is made much of John chapter nine the disciples asked Jesus if it was because of the man's sin or his parents sin that he was born blind and Jesus answers them in verse three it was neither that this man sinned nor his parents but it was so that the works of God might be displayed in him and so Lord we just stand this morning in that with your heart that your way in the city of Kalamazoo in our homes our families our hearts our bodies our minds God we're asking that you would do what you love to do that you would be who you are the God who heals in this hour in this city in our very midst God we're asking that you would tear open the heavens that you would show yourself strong again through the release of healing power as you heal the sick as you heal the brokenhearted as you heal God those with mental handicaps and disabilities God we're asking break in and release a healing all throughout your people in Jesus name your church in Kalamazoo that you would fan your heart for healing that we would not give way to fear and doubt the Holy Spirit once again that we would move in healing power again that we would believe this city God surprise us would you just break out we're two or more church services that they would just become places of healing we would be amiss if we didn't ask if there's anyone gathered at the altar this morning who is in need of healing in your body is there anyone at all in the room we want to pray for you we don't want you to come to the house of prayer and then leave without receiving prayer anyone with sickness or any condition just raise your hand okay pastor Sunny okay can we just gather around those who have their hands raised and you guys can just begin to pray for them as I close out Lord we love you and we thank you for this hour we thank you for the privilege to sing your praises to declare with the hosts of heaven your worth and to agree with your heart is the great intercessor and Lord we ask that all that is transpired that it would be multiplied many times over in this place in our city in the cities joining us God via the livestream this morning that you would find a praying church God in the earth on earth as it is in heaven we love you Lord and we bless you in Jesus name amen thanks so much for joining us for morning prayer we're going to be back here at noon praying for the nations and then again tonight at 6 30 God bless you