Hi I'm Dr. Eric Green. I'm the director of the National Human Genome Research Institute at the National Institutes of Health and I'm here with my wonderful sidekick. I'm Dr. Carly Easter also at the National Human Genome Research Institute at the National Institutes of Health and I'm the Education Specialist. And today we're here to isolate strawberry DNA using household things I guess. Basically we are going to show you how to get DNA out of a strawberry. Great. And why do we pick strawberries? Well so for me there are many reasons. The first of all they smell really nice. They're very pretty. The other thing is they're nice and edible and their seeds are on the outside of the strawberry and I have found that it's very easy to get DNA out of a strawberry. Yeah. Although of course like all living things they have DNA we could pick a variety of different other things to purify DNA from. We just pick strawberries because it's easy and they're easy to get. There we go. So. Okay. You ready to start? Yep. What do we do? So the first thing we're going to do is take our frozen strawberries you notice they don't look like those nice strawberries and we're gonna place them into this plastic bag. And now you could purify DNA from these strawberries or these. We just picked frozen ones because they're squishier and mushier right and we're gonna and you can get them any time of the year. Yeah that's true. Okay so we're putting it here in the plastic bag. Yep. And the reason we're doing that is because the first thing we need to do is blast them open. You get that's right. Okay. That's right. And the reason for that is that the DNA is inside the cells in that strawberry and we gotta get that DNA to sort of go into solution so that we can purify it. So we do this and I'm gonna smash I'm gonna point this towards you just in case it breaks open but I know my job here is just to smash them all up. Smash them up. Excellent. So while Dr. Green is smashing I'm going to make what's called a lysis solution. Lysis. Lysis. What is lysis? So lysis means to break open and the purpose of the lysis solution is to break open the strawberry cells to get to the DNA which as Dr. Green said is inside the strawberries. And a cell is just basically a bag of living materials and living different kinds of molecules surrounded by a membrane sort of thing maybe like saran wrap or we can think of it actually like a water balloon and we need inside instead of water there actually is water but in there is also DNA and we're gonna do us use a solution to bust open these cells or bust up on these teeny teeny little water balloons. Excellent. So we're gonna use household chemicals as we said at the beginning this is just regular detergent. Just like for cleaning dishes. Exactly. Or you could use hand soap or shampoo. Works really well. So two teaspoons of detergent. We're gonna take a half a teaspoon of salt and then we're going to add half a cup of water. Okay. And I'm going to stir this up. Okay. I think the strawberry puree is already ready to go. Perfect. So here we go. Detergent and the salt together are gonna just bust open those little cells, those little water balloons. I'm gonna do this and I know I'm not supposed to pound on it anymore otherwise we actually will get a shower. There we go. With soap and all. So the point is you don't want to create a lot of bubbles as you're mixing the lysis solution around with your strawberry puree. Otherwise you just have a bubble bath. That's right. Okay. So we're just and I can hear the water balloons just busting out from the side. And you hear that DNA coming out? It is. And it's saying I'm free. I'm free. I'm liberated. I'm in solution now. Excellent. Okay. But now we have all bits and pieces of strawberries mixed in with all this liquid. So that's probably a little bit too icky for what we need to do. It would be very hard for us to see the DNA in this mess that we've created. Right. So what we're going to do is filter. And as you can see I'm using just a regular coffee filter. Just one that you would use for making coffee at home in a coffee maker. And it's just going to pull out. It's just going to separate out the liquid from the strawberry gook. Gook is a technical term we use here in genetics all the time. Yeah. So we're going to pour. We don't actually need all of it. We just need a good amount. Right. Exactly.  And this just makes it easier to push the DNA that's in the liquid away from the big pieces of strawberry. And you want to be gentle. You don't want to squeeze so hard that you actually break the filter. Otherwise the gook will go back in there. It's like coffee grounds. It would just get in your coffee. Exactly. Okay. Does that look good? Looks good. Perfect. All right. So this is basically the material that was in the cells of the strawberry. And it has lots and lots and lots of different kinds of chemicals in there because all the contents of a strawberry cell. But the good news is a lot of DNA should be there because strawberries have a lot of DNA. And so we need to get the DNA out of solution because it's now dissolved in that in the in the detergent. So we're going to do what's called precipitation. Okay. Precipitation. Precipitation. So it's going to rain. It's going to rain basically. So when you think about precipitation in this case, hopefully if we've done this right the DNA will fall out of solution. We'll actually get to see the DNA start to form just as the rain comes out of the clouds or the snow. We'll see DNA start to form in our solution here. Or in science or in particular in chemistry when you talk about precipitation, it's often about something that's in solution becoming solid again or becoming material that you could then see and manipulate not in a liquid form. And so we're going to try to get the DNA to come out of solution. Excellent. So to do that, what do we do? We're going to use just regular rubbing alcohol. So just any old rubbing alcohol that you would buy in any old drug store. Right. Okay. And this is not the alcohol you drink? Nope, certainly not. And we're just going to pour an equal amount right to the strawberry juice, if you will. So I'll just carefully pour about there. Perfect. And what you immediately see of course is almost like two different layers forming. Exactly. You can see two different sort of phases. So you have all that red stuff that's at the bottom. And then we've got something that's forming up here in the top. Slimy, gunky, gross, almost like snot or a cotton ball. Sort of cotton ball in liquid. Excellent. Interesting is that the redness of the strawberry is not on the upper layer. It's in the lower layer. And so what's the gunky, slimy stuff? I don't know. I think it's the DNA. What do you think it is? I remember in medical school, you know, in medical school, we started with strawberries and we learned strawberry medicine. And here we go. So yeah, so you can sort of see the DNA precipitating, coming out of solution into a solid form. And there's a lot of it. Awesome. So you can see that nicely. So I guess we can use something, and we just happen to hear a popsicle stick with a little bit notch to go in. And we can just touch it and very easily pick it up. It looks like just a big old slimy wad of strawberry DNA. That's awesome. Now that you have it, you have it separated, this is purified DNA. And what's amazing is that it has no red with it at all. It's just totally white, which is exactly what DNA should be. What can you do with this after you've done it? So I always tell the students when I'm doing this in the classroom that first of all, this is extremely dirty.  But one of the things you could do is actually analyze this DNA. So just as you would watch CSI or any of those other forensic shows, this is the same way they would isolate DNA from skin or from blood or anything just using different chemicals. So the opportunity would be to now analyze it and sort of figure out what is it, where is it from? All right. Now, so this of course is strawberry DNA, but in hospitals increasingly now we're purifying DNA from blood or from scrapes from inside of your cheek and doing all sorts of medical tests. And that in many ways is the future of medicine is looking at humans DNA and trying to figure out things about it that may be relevant for your health. And now for students at home who actually do this, can they save this DNA? How do they do that? Actually, you could put it into a sealed container and put it in the refrigerator and it would stay for a long time. Like a like a Ziploc bag or a small tube as long as you could seal it up. Okay. So so if they want to do this at home, what are they? How do they get instructions to figure out how to do this? You could visit our website and just go and look at the instructions and do exactly what Dr. Green and I did here and isolate your own strawberry DNA. Point by point, tell them exactly what to do. Those instructions are on our website. Well, that's great. Okay. So this was wonderful. Thanks for helping me do this. And I hope everybody enjoyed it.


Hi, my name is Adam Philogen Herron. I work at the University of London at Goldsmiths College. I'm a lecturer there in social anthropology. Why anthropology? Anthropology for me has offered the opportunity to journey into other worlds, the possibility to write about difference in an honest and sincere way, and to give people who might be well-depart the opportunity to understand one another, to understand the full breadth of the human experience, as best as I possibly can, and to share stories. And hopefully in so doing, anthropology can have some transformative potential, can make this world somewhat more equal, while still respecting the differences between us.


Nobody comes into bow rap anymore with their own original style. It's a very rare thing to see someone with a completely unique style. And I think the last bowler to do that is Shuffle T. There's definitely no one up north that can stand up to shuffle his A game. So on May the 9th he stayed behind because he threatened Mr Davis' life with a pastry knife. So we made him do 80 lines. He turned up two hours early with a mirror caked in white saying you can't swim for a crazy night. Shuffle T. Oh my God. He's going to bring out, he's going to shut it down. It's just another way to see himself to be honest.


The question is that amendment 6899.2, in the name of Humza Yousaf, which seeks to amend motion 6899, in the name of Jackie Baillie, on protecting primary care, be agreed and members should cast their votes now. The vote is closed. Point of order, Alasdair Allan. I would have voted yes. The system wouldn't work. Thank you. We'll ensure that's recorded. Point of order, Mary McCallan. Sorry, my app wouldn't refresh, I would have voted yes. Okay, I can confirm that your vote was recorded. Oh, good. Thank you. The result of the vote on amendment number 6899.2, in the name of Humza Yousaf, is yes, 67, no, 54, there were no abstentions, the amendment is therefore agreed. The next question is that amendment 6899.1, in the name of Sandesh Gulhane, which seeks to amend motion 6899, in the name of Jackie Baillie, on protecting primary care, be agreed. Are we all agreed? The Parliament is not agreed, therefore we'll move to a vote, members should cast their votes now. The vote is closed. Point of order, Alasdair Allan. Presiding Officer, I would have put a shilling in the meter and voted no. Thank you. We'll ensure that vote is recorded. The result of the vote on amendment number 6899.1, in the name of Sandesh Gulhane, is yes, 53, no, 67, there were no abstentions, the amendment is therefore not agreed. The next question is that motion 6899, in the name of Jackie Baillie, as amended, on protecting primary care, be agreed. Are we all agreed? The Parliament is not agreed, therefore we'll move to a vote, members should cast their votes now. The vote is closed. The result of the vote on motion 6899, in the name of Jackie Baillie, as amended, is yes, 66, no, 55, there were no abstentions, the motion as amended is therefore agreed. The next question is that amendment 6898.2, in the name of Shona Robison, which seeks to amend motion 6898, in the name of Mark Griffin, on cost of living mortgage rescue scheme, be agreed. Are we all agreed? The Parliament is not agreed, therefore we'll move to a vote, members should cast their votes now. The vote is closed. The result of the vote on amendment number 6898.2, in the name of Shona Robison, is yes, 67, no, 54, there were no abstentions, the amendment is therefore agreed. The next question is that amendment 6898.1, in the name of Miles Briggs, which seeks to amend motion 6898, in the name of Mark Griffin, on cost of living mortgage rescue scheme, be agreed. Are we all agreed? The Parliament is not agreed, therefore we'll move to a vote, members should cast their votes now. The vote is closed. The point of order, Monica Lennon. Thank you, Presiding Officer. I lost connection. I would have voted no. Thank you, Ms Lennon. We'll ensure that it's recorded. The result of the vote on amendment number 6898.1, in the name of Miles Briggs, is yes, 30, no, 91, there were no abstentions, therefore the amendment is not agreed. The final question is that motion 6898, in the name of Mark Griffin, as amended, on cost of living mortgage rescue scheme, be agreed. Are we all agreed? The Parliament is not agreed, therefore we'll move to a vote, members should cast their votes now. The vote is closed. The point of order, Shirley-Anne Somerville. Thank you, we'll ensure that it's recorded. The result of the vote on motion 6898, in the name of Mark Griffin, as amended, is yes, 72, no 49, there were no abstentions, the motion, as amended, is therefore agreed. That concludes decision time and we'll now move on to members' business.


I wanted to start by saying that, yes, the name of the story sounds like the real lost, found, variant called, Cimmeron, but this variant is so lost, only a description of the logo was the only way to describe it. According to therapist papers and documents, people reported a lost variant of Paramount Pictures logo called, Zeus, used in the test footage that was gonna be used in three of the Paramount movies released later on DVD and VHS. Limoni Snicket's series of unfortunate events, Shaft, and Double Jeopardy with Tommy Lee Jones. During the year 1999, VHS was booming with DVD already released by 1995, popping movies on both VHS and DVD. Of course, things were normal with most companies except for Paramount Pictures. According to an anonymous source, testing groups tested an alternate version of the Paramount Pictures logo. The project name was Zeus, and everyone gathered around to watch the variant. It started with the Paramount logo as normal, with the stars flying through and coming over by the mountain. However, the sky was noticeably darker with dark clouds, suddenly a very loud thunder clap was heard as the logo was shown after the lightning strikes the mountain. It ends with a blackened tip on the mountain with the Paramount logo name in gold colors. It was reported that two of the testers died of heart attacks, three jumped out of the company's window, and one reportedly was sent to the insane asylum, mumbling that Zeus is the devil. The two people responsible for showing the test footage were horrified, they immediately scrapped the logo variant and kept the original as is. Now, it may sound familiar with what I was describing. Well, you may recognize the Paramount Pictures DVD logo variant used in DVDs of later Paramount movies. This grew as one of the biggest mysteries on what happened to the variant of Paramount Pictures. Some people claim this was some sort of Bambella effect where people misremember things that were true. I won't go through the theory too much as the theory is very extensive. As of November 10th, 2023, the logo variant hasn't surfaced. I may sound crazy, and to this day, I haven't found anything that could prove I'm not crazy, but if this gets popular, I'll make more lost variants. I know I'm not alone. I know it.


We know that you can get to very comfortable with that style. You need to be able to kind of be ready for the multiples, which we know Kung Lao can bring to the table, especially in the hands of Koki. And I believe we're going to get straight into this and this loser's action is dizzy was sent to losers by Tekken master and winners side top eight in a game five last round situation. And Bokey, of course, managing to defeat Yamani to get this far. I think our matchups today have been absolutely ridiculous. Then there's loads of time to reflect and capitalize on what to do differently.  We can't extend the box below and there's a full punish. Just build the final bar he needs for damage and it's getting rid of all of the defensive bar for Dizzy. He has confidence to make a comeback, but honestly, there's a confirm. This should be the round for Bokey. Oh, no. Unless he drops a dizzy throwing a lifeline. No defensive bar though, so no last breath to save him. Oh, I thought for sure we'd see a dive kick. Hello. The clutch block gets hit. Oh, no way. No way. No way. Dizzy TT with the impossible comeback. He had no defensive bar and less than a percent of health. How did he do that? It just came down to just the back one mix up and Bokey being very, very defensive. And then in the scramble, you just need one more hit. It can sometimes be really hard to decide what to do because the dive kick was unsafe, right? You're going to dedicate to that one last breath was a factor. I think not. Oh, no, the wake up down to was a bad call to make there getting completely crushed by the back one for confirms as well. Side switch. Yes. Okay. Down three blocks. Dizzy still moving in Bokey has to be really careful. You see, just he has to be so careful on the defensive against Sonya. Oh, point black teleport and they're paid off Bokey. All the stops. Oh, okay. Big neutral hop goes low this time. Oh, crushing blow almost enough to take the life bar by itself, but another teleport Bokey. Not afraid. Oh, big neutral jump and there is the quick cheeky load. Going to get tagged. And he's taking that first game on the back of what is all intents and purposes a real master comeback by all definitions. The fatal blow is a wonderful thing, especially if you've got an advancing mid that keeps the opponent grounded. The crowd, they're going to be cheering for Bokey. They do want their hometown hero to win this. He has one hell of an opponent with the DTT, but Bokey is, I mean, this was the guy that defeated Honeyby yesterday. He's collected some amazing heads already. So that was an expensive sequence from Bokey. He spent a bar on the orbiting hat just to use it. And then the second on the amplified spin, of which was breakwade by Dizzy for a free punish. Bokey lost half his life almost and most of his resources for that decision, unfortunately. Okay, big jump kick.  So good. Yeah, really. Yeah, it's mega plus. Oh, risky stuff there. Oh, he's stuck playing it now. Dizzy TT, very, very good at confirming the 1-3-4, even if it hits a little bit late. Unable to confirm now. Wake up roll. Instant jump kick. The reed's going to be on point. The forward one doesn't believe, doesn't confirm the rest of the string just in case. But unfortunately, that's another round gone. And it feels like already things are kind of falling apart for Bokey a little bit. A big thing is Dizzy is playing very carefree, right? Like, he's very confident. He knows he beat Bokey yesterday. No, he is one of the younger players to take very much to rally. Oh, no! And he's playing like that right now. I feel like it's important to keep your call against this kind of playstyle. Bokey, very chaotic. And if you can keep very calm against that kind of playstyle and really contain him, which is easier said than done, for sure, you can have a much easier time with it. And that's what we're seeing from Dizzy right now. Did he dropping the whiff punish on wake-up but able to capitalize anyway? And his ring's going to get jumped in on, but that forward one string's not going to hit its mark. Bokey's feeling nice and safe. He's getting little hits here and there, but unfortunately, apart from game one, Bokey hasn't landed a single significant connection yet. Because every time he leaves the ground, Dizzy is going to challenge himself. Oh, wow! What's up into it? That was unfortunate. Here comes the grab now.  Chip damage into it. That's why Dizzy's being confirmed. Oh! I thought for sure that might be it. And he's just waiting for the counter poke. He was waiting and waiting and waiting and the fatal blow never came. Bokey tries to do something else and unfortunately, that also was the wrong decision to make. And I think, Albert, a big part of it is just putting a lid on it. The moment every time Dizzy TT is getting hit, it is something single. Like a dive kick or a jump kick. It's nothing really to write home about. But you're seeing Dizzy's defense against the general Kung Lao mix up is if he reads the mid, he's going to sit there and block. If he reads the throw, he's neutral jumping. We've seen him do it a lot already where he just holds up and if he thinks he's going to throw, that's his option. And if it pays off, he's going to get a huge reward for it. A two on two on two is actually slightly plus on block two, so Dizzy's going to sit there and hold it. Okay, hops not to amplify. He wants to keep positioning and the wake up up three from Kung Lao. Meet a spent and nothing accomplished. Come back, dive kick, hard read. It's going to work out as well. These big decisions Bokey's kind of known for. Again, the neutral jump. There it is. Oh! Is that enough? No, not quite. Oh, well that will be snap off. Get out of here, twin. Stop stealing my brain. My point for Dizzy TT. No. Okay, last round to go. Fight. God, Bokey has such a mountain to climb. This has been a fast, fast five rounds as well. I get another. I mean, he's not always getting a hit for it, but it's showing Bokey that the throws are dangerous. I want to meet you down three too. Sonya's down three. Oh no. Except it's really good to second hit hits so the crushing blow requirement ticked off. Down three, low profiles, the jump kick. Locked the energy ring, but it's not clear enough. Here we go. He needs more. He needs so much more. Oh no. The whiff. No punishment though, really, Dizzy. He's going to get a grab anyway. This is Bokey's last lifeline. He has to do something. Oh, the drone drop coming in hot. And there it is, the minus seven. Walk back. Okay, here's confirmed, Dizzy. He has no bar. This could be huge. You see the fatal blow? No holds it. All the mid. No bar. And there it is. The reversal. Just swift punch to the jaw is going to be enough to send Bokey out of the tournament, unfortunately. But what a run. What a run. I was, honestly, I was half expecting Bokey to just dedicate to forward one fatal blow. Because he hit it. Yeah? He hit it, man. And yeah, the round of applause for Bokey, the hometown hero. Unfortunately, fifth is where his journey ends. But top eight was a phenomenal result. He took out some superb players on the way in.


Gotta go places and do things. Maybe to walk... Here because it's open till 10, so it makes sense.  I only have an hour and a half here, but I'm sure I can get a lot of compish. I do have Express Pass, so that gives me a plus. And, uh, yeah, just wanna hang out. So, let's go do this. The good ol' Premiere Pass. Thank God for that and the Express Pass. Really let you let the adventure begin. Sometimes I find the cheesiest things I can put together just to do stuff like that. I like that guy. There are a couple of things I'm hoping to get accomplished tonight. One of them be Ride Hagrid's motorbike at night because I've never done that. I've only done it during the day. Also, maybe Ride Jurassic Park without getting wet. So those things, you know, may or may not happen. Probably not gonna happen, but we're gonna try. Hagrid's motorbike is posted at a 160 minute wait. So at least it's open and they're still letting people on. It looks like they finally took down the extended queue for Hagrid's here in Suisse Landing. Bunch of them all up there. See it on that side, too. Well, that's good. That's good. I feel like Halloween Horror Nights could do some really good things over here in Suisse Landing.  That's a jogaloon. A jogaloon? Huh. I'd also like to add one more thing to the list if you guys would allow me. I would like to see the projection show on Hogwarts Castle because it is different since the last time I really stopped and watched it. So if that can be done, Hagrid's Jurassic Park, not get wet, and the projection show on the castle in an hour, I think I could do it. Walking through these archways always gives me the chills and that music timed perfectly. First things first, jump right to Hagrid's because I feel like that needs to get accomplished first. But it's too light out, but hopefully by the time I get through the line it's going to be a little bit darker. Look at her go. And check out the taillights and headlights. I love it. There's that dame's roof. Really messing with my perceptions. Oh, look at this. We're loading up. I'm loading on up. Plus this, we got front row. A downside is we're stuck. A million times better at night. That's amazing. So much better at night. I know I said that a couple of times already, but when you're coming off the ride, you're in a hurry because I'm pulling out my camera because I'm like, ah, I'm so excited because you can't film on the ride.  It was pretty awesome. So now we're going to try to watch the projection show and then head to Jurassic Park. I got like 35 minutes left. I can do this. Oh, here she comes. There she goes. I don't know why I call it a sheet, but I just like it. So there it is. Okay, so that was the same projection show that I've seen before. I just didn't realize it. But now we're going to head over to Jurassic Park and I'm going to see about riding Jurassic Park without getting wet if that's possible. And everybody keeps on talking about how long the wait time is for Hagrid's. But look at this, current wait time for Raptor Encounter is 12 hours. It begins at 10 a.m. That's insane. All right, river adventure and the goal is not to get wet. No wet, please. Thank you, thank you. Which lane is the express lane? Oh, it's over there. Why don't I wish you were on this part? Oh, you don't? Well, thank God. I hear the back row is probably the least wettest. I hope that's right. I'm not going to name my source, but it's a reliable one. Oh, do-do-do-do. Didn't even get touched by water, except for by the drooling dinosaur that was actually in the JPEG containment. That's the only one. That would be it. Perfect, not a drop on me. That's the way. Our picture was great. You couldn't even see anything. Nothing. Universal at night is so awesome. There's hardly any waits. Literally, Jurassic Park, I had it expressed. I walked to the stand by. It was a five minute wait. I looked at Skull Island and it was literally maybe 10 minutes, I think it said. So there are plenty of awesome things to do and no waits. Before I head out, I want to see about getting my annual passpin and hopefully I think we're in the right spot. If not, we'll find out. But yeah, that's a freebie and if it's free, it's for me. Here it is. Oh, my fingers blocking the scanner. One penny. One more time. One penny, one more time. One pin, please. Thank you. Look at that, baby. Time. The ever-flowing river. I like free things, so I like this. Hold up. Wait a minute. No way. Do any of these say universal on them? What? No, but they are some nice hats. I like them a lot. All right, I'm going to throw one more ride in there before we call it a night because we have exactly five minutes. Look at that. We don't blow it when it comes to the news. That's disgusting. Will. Oh, wow. It's disgusting that I'm touching it. Oh, boy. Not a bad way to end my night. One hour. Road Hagrid's Jurassic Park. Watch the projection show. Den Road, Spiderman. For anything better to go. So it's 10 o'clock now, the park's closing, but we still have time to walk around and walk out, which you can't even ride any rides. Look at all these cool Hagrid magical creature motorbike adventure stuff. A nice little hat.  Fluffy. The unicorns. A tumbler. I like it. Oh, wait. What's over here? Oh, look at that. I don't think it has anything to do with the ride though. Maybe it does. I don't know. Oh, they got lots more. They even got socks, cell phone cases, pictures, and backpacks. Wow. But that really went together well. Socks, cell phone cases, pictures, and backpacks. So that's going to do it for me tonight. I am a hot mess and very hot, but it was fun and definitely a great way to end the night. So I guess we'll see you next time. Bye.


Whoa, dude, one of one Brandon Miller rookie laundry tag Hornets whoa Oh my goodness Josh M, dude Josh M for a player that does not have autographs. That is massive. Whoo One of the last teams taken two. Oh, yeah, I'll do that will do right there Oursers one of one Brandon Miller, baby


What is going on guys? Welcome back to the channel and I appreciate you being here. Today I am back with another Destiny Top 5 video and today we have Top 5 Funny and WTF Moments of the Week. But before we get into the video people if you do enjoy leaving a like really does help out. If you're new around here and Destiny is what you want to see be sure to subscribe and if you have any amazing clip that you think is worth sharing with the world send it into the email I've just linked at the top of the video description but guys let's get straight into this top 5. In at number 5 we have a clip sent in by decked Arliev66 who submits this clip showcasing how not to warlock. While we have a clip sent in by Will Wombat 1999. Is there even such thing as they draw in gametes? If so surely this would have been better. We have a clip sent in by Crunchy's patient. Don't grab that bro it looks dangerous. In at number 2 we have a clip sent in by IbrahimIHX. I ain't certain but I think his own ghost killed him here. In at number 1 we have a clip sent in by the vortex spirit. The most dangerous loot ever. But guys that is the end of this top 5 if you enjoyed it leaving a like really does help out. If you're new around here and enjoy a daily Destiny 2 video be sure to subscribe and if you're never one I miss a video I upload turn notifications on by hitting that bell button but guys thanks as always for stopping by and hopefully I will see you on at next one.


Good morning all. Usually we go, we allow about five minutes for everyone to turn up. I do want to go ahead and remind everyone that our meetings are recorded from the time that they start. So you're currently being recorded. This will be posted to YouTube. If everyone could also please go to the meeting minutes and add themselves to the attendee list. That's actually super, super helpful to us. And we'll get going here in a few minutes. Thank you. Also please add any topics that you want to discuss. I see that Michael is here. He has something to share with us. So please add your topics at the bottom of the agenda. That is absolutely fantastic. And please do add your stuff to the agenda. We actually run fairly free-wheeling meetings. I think some of our very best meetings have started with an empty agenda and become amazing. So awesome. So yes, it turns out a gender list doesn't mean there's no agenda. Just means we instantiate one on the fly. What's the old, my favorite definition of serverless is that traditionally you would provision resources and then accept requests and in serverless you accept requests and then provision resources. So a gender list does not mean that you don't have items in your meeting. It means you start your meeting and then you figure out where you're going. So our meeting minutes are world-rightable for a reason primarily so that everybody can contribute. Also feel free to take notes there as well and help us know what happens in the meeting. Also good this. Can you get someone to share the agenda please? Thank you. So we'll give a couple more minutes and then we will get started. So are you good going? Yeah let's do it. So welcome to the next network service mesh meeting. So we have this call which occurs every week. We also have a user friendly call which occurs every other week at I think it was 10 a.m. Pacific. Sorry no it's 10 a.m. CET and definitely not Pacific. The next one will be on January 21st. We also participate in the CNCF Telecom user group which occurs every first Monday at 8 a.m. Pacific and every third Monday at 3 a.m. Pacific. And we also are participating in the CNCF networking working group. The next call will be on Thursday, January 16th and that meets every two weeks at 11 a.m. We have a few events coming up. The first major, the next major one is KubeCon and the five major con in Europe which is going to be at the RAI and Amstrad. The CFPs have been closed for a while. We're just waiting for the schedule to be announced. The schedule should be announced the day after our next Asian meeting on January 22nd which should be a Wednesday. We have a set of CFPs which have been added to a spreadsheet. So if you have added something that is related or of interest to telecom networking then or to CNS please add it to the spreadsheet. We are also going to have a NSM con at KubeCon EU which will be in a larger room. We now have an event page. We have opened or rather we are going to open a CFPs which will close on February 21st and I don't think I've created a form for that yet have I? So I'll get started. There is a form. I created a form. In fairness I copied your previous form and edited it for the new information. So created like a little bit much but I caused there to be a form in existence. Do we have, have we opened the CFP for that because there's no CFP open date? There is if you look in the events overview there's a CFP link and that is open. Cool so feel free to start submitting things now. It is open until February 21st which gives you time to work out what you want to do if your talk, if you submitted one to KubeCon does not get accepted. There is an opportunity to submit it into NSM con as well and still get it heard by the smaller but more highly targeted community. We also have sponsorship opportunities available. So we were very pleased there was good response to the sponsors last time. So if you work for a company that would like to sponsor NSM con we've got a variety of different levels and ways in which sponsors should can be achieved. Yeah so feel free to have, have we loaded the prospectus up yet? Yep it's behind the become a sponsor button. Perfect so the prospectus is behind the become a sponsor. So please, please consider, please consider, consider sponsoring. It's a, it's relatively, it's relatively low in price for the value that you get if you're heavily interested in this space. Cool so you know why my Google Docs never loaded so can you switch back to the agenda? Yep. Cool thank you. Yeah I'm getting the endless loading screen on Google Docs so. Great so we also have open networking and edge summit which CFPs I believe are now open and they close on February 3rd so please feel free to submit to ONES in Los Angeles and that will, that will be on April 20th through 21st. We have, we are, we have a couple new announcements and so the first major announcements is we are creating a NSM PR and issue review meeting which is going to occur right before this particular meeting starting next week. We'll get a calendar with a, we'll get a calendar event up pretty soon on this and so we kept this short on purpose because we don't want this to, I don't know if evolve or devolve is the right word but we don't want it to convert into a, to a architecture meeting. This is purely for let's go over the issues, let's make sure things are tracking, let's make sure we unlock people who are currently blocked. So that'll occur at 730 every day right before this meeting. Yeah so excellent meeting to sort of see exactly what's going on on the ground and particularly if you want to get involved that's going to be an excellent meeting. We wanted to make sure that was happening publicly for folks and my guess is if we had an architecture question in that discussion we'll simply punt it up to this community meeting to resolve. And if you're looking for something easy to get involved this, this is the place to ask how to, how do I get involved? What's, what's the right first issue for me? And we'll, we can get that conversation started here. We finally also I have been, we also received the QCon North America 2019 report and so we also noticed that the NSM has had very strong interest higher than any other NSM, sorry higher than any other Sandbox project. And so I think, are we higher than all the other incubating as well? No we're kind of middle of the pack compared to the other incubating projects but the fact that we're in the same general range as some projects that are like extremely well established is kind of telling. So like the open tracing guys came in 1800, we came in at 1500 which is certainly not bad, right? You know we came in at 1500, CNI came in at 1700. So we're right up there with a whole bunch of those things. Obviously we're not in the same range as a Kubernetes or a Prometheus at 9k or 5k but we're, you know, given, given the age of the project and where we stand we're kicking ass. And the topic as well, I mean people usually think of medworking as like this boring thing but once it's up you leave it alone. What was the the unofficial slogan network service mesh, making networking sexy again? Exactly and so the usually thing medworking is the thing you don't care about until it breaks. Do we want to bump the SROV item down to the the non sort of turning the wheels part of the agenda? Yeah, that got mixed in somewhere. I was just trying to get that on here. Better to capture than not to capture dude. So please thank you for getting it there at all. It's easy to move things around on the agenda. It's hard to magically know that there are agenda items that we've missed. Yep, absolutely. So I'll go ahead and stick it down on the sort of substantive part of the agenda and we can figure out where we want to put that water-wise. Cool. Okay, we can scroll up very slightly and then I will do my best to cover Lucina stuff. So social media community team, Twitter stats, we have seven additional followers and we are following an additional 37. We have added eight tweets for a total of 924. So we will be approaching a thousand pretty soon and we have posted four main things, the CNCF Signetwork, 2020 Telecom, sorry, topics of interest for CNCF Signetwork. That's actually something we should mention about before or soon as well. We have 20, 20 telecom predictions. I'll have 20, 20 events lineup and the CFP live for ONS. The CIG, so the CNCF Signetwork is a little bit of background. The CNCF is going to, they're reorganizing the way they do their talk a little for sandbox projects.  And the line for this is during absurdly long. And so in order to speed things up and in order to get better, I guess, visibility and tracking into what's going on, they're going to start asking the CIGs to start doing some of the vetting and some of the recommendations towards this. And so the CNCF networking CIG has been revived. It's been revived and what's going to happen is things related towards service mesh, networking, and proxying, etc. are all going to start their path in those CIGs. And so one of the things that will be good is to make sure that we get some level of representation there and also some diversity in that space as well. So I'm definitely going to participate in that particular path. I'm also going to seek people from the oddly community and some of the service mesh communities and so on to see if I can get them to go in so we can help with that particular process. But part of that is also going to be, we also want to hold when talks on a regular basis that are on interesting topics. So the involvement doesn't have to be, hey, you show up every two weeks. The involvement could also just be coming and give an interest. I have a brief point of confusion on the item we had about that in our meeting minutes. It said it meets every Tuesday at 11 a.m. and it says next call Thursday, January 16th. Hi, good catch. Let's double check the time schedule because it turns out there is an older SIG networking group that I've been starting sort of a year ago and we're still chasing down. Yeah. So I think Thursday is the right one. I believe, now that I'm thinking about it in my memory rather than relying on the words, I believe it's the same time slot as the Kubernetes networking SIG but on the days where they don't run Kubernetes number SIG. Okay. Yeah. So there's a different page. I'll fix the links that we have in the thing because the link that we have is to the old CNCF networking working group. We probably want to change that to the SIG. Yeah. Good catch. So let's double check the time. But yeah, it's definitely Thursday. It's early afternoon Pacific time. And so we'll double check the exact time for that. Cool. Okay. I won't go too long on for that, but that's something of interest that is changing in the CNCF itself. And with that, finally on the social media community team, we're going to have the prospectus and sponsored lineup and so on sent out. And once we get to go ahead on the contributor podcast, and Ed, we may be the ones blocking it because I think he's just waiting for approval from us if we haven't done it yet. That will go out soon. Okay. Oh, definitely we don't want to be blocking that. Yeah. The only reason I can think to ask them to hold off would be if we want to get it right over in a few comments. But yeah, the only thing I need to check is that they properly CC my PR minders who get very upset. They literally don't care at all as long as they know. And then once they, as long as they, but if they don't know, they get very upset. So yeah, no surprises. No surprises. They don't do very well with presents. So we do. With that, jump into the main agenda. We have breaking cloud tests into a separate repo. Ed, do you want to drive this part of the agenda? I think it's more Andre. Andre, you want to talk about it? Sorry. I was muted about the cloud test. Yeah, we have a separate repo for the cloud test. We have already through CCI, pass it for it. Yeah, it has just initial documentation. It will be updated in the next few days. And we have a pull request to switch to network service mesh to use this separate cloud test from this repository. I think I've merged that now. Oh, okay. It's nice. So we switch it to use a separate cloud test repo. Next steps will be, yeah. Good. Next steps will be to add more examples. So this tool will be more widely could be more widely used. Cool. Yeah, Ed. Awesome. My recommendation is once this is more user friendly that we spend a little bit of time on this specific topic so that other people know not only what it is, but how to properly use it. Yeah, yeah. This is my next steps to use a friendly regarding the presentation and just initial steps for anyone. Yeah. For those of you who are sort of newer to the community, when we were trying to do testing in our CI across all the many clouds, we discovered that's hard. And it was annoyingly hard. And so cloud test was to sort of make it easier because it turns out that you get all kinds of weird things like the varying time it takes for clusters to start and scheduling tests across clusters and a whole bunch of other things. So, you know, that got built in the network service mesh repo and then a bunch of people sort of looked at it and said, that's really neat. Could we use that? And that's part of why we're breaking it out. Yeah. When we say that we run six clusters per cloud for every single PR test, this is the driving thing. So, okay, so we have some information on a rough cut on the forwarder to the cross connect and path and simplified healing. So this looks like it's your handiwork it. So you have the work. We talked through all the stuff before the break, which is we realized we could simplify things a great deal if the forwarders stopped having their own API and just became essentially a particular kind of network service endpoint. It actually simplified a ton of stuff, not just the API. It made a whole bunch of interesting things possible. And there's a lot to be said for discovering that if you make your system simpler and more maintainable, that it's also more powerful. And so there was a general fondness towards that notion. And when we looked at that, we realized that we'd have to rethink how we were doing our healing stuff. And so we looked at how to revamp the healing stuff with the path concept. And it turned out that that made healing phenomenally simpler and more comprehensible as in the current rough cut code for healing is less than 150 lines of code. And it's generally reusable. So this was also kind of an awesome realization. And so we talked about this a couple of times before the break. People were generally friendly. And so over the break I hacked a bit on this. And so the result of that hacking is in PR 2050. And there's entirely too much there. It needs to be pulled into smaller pieces. But you have to get to a certain point before you figure out what all you're actually doing. So I pulled that out and I put that up so that everyone could take a look at sort of where what's there, the kinds of style with which it's going. Among other things, it'll make the existing code enormously more unit testable because all the individual pieces will be unit testable because essentially you end up building servers out of chains of things. And yes, I know about the conflicts. They'll be fixed. And so in looking at that and sort of talking about this with some folks, one of the things that occurred to us is one way to make this more accessible in general to folks. We've been talking for a long time about pulling pieces out of the network service mesh repo into their own repo because while the network service mesh repo from a line of code point of view is still relatively small, from a thematic point of view it's gotten kind of a little bit bloated. And so the sort of suggestion here was to essentially start with the new code that we're doing here and start an SDK repo and start an SDK dash VPP agent repo. And the reason those are two separate repos is VPP agent is a particular forwarder platform that you can use with that work service mesh. And while I happen to personally think it's an awesome choice, you don't want to make your general SDK stuff pull in dependencies from one particular platform among many, because we already have things like the kernel forwarder that is a different forwarder implementation. We've got people looking at others. And so you want to keep the sort of platform specific stuff platform specific. And so the general proposal is to start breaking the new code out into separate repos where you can go in a bit by bit and a little bit faster and start with the SDK and SDK VPP agent repos. Do people have thoughts questions? We wanted to sort of talk through this a little bit before we pull the trigger and started moving code in that direction. Yeah, we already shared thoughts with you, but maybe it's worth discussing this also here on the work group call. So yes, I do agree that maybe there are bits that you wouldn't want to pull in just for the sake of using our SDK. I mean, like we can see here that VPP agent is here. Maybe some other things are coming along with other stuff. Still, at least for me, currently it's a more or less, I don't know, integral part. So do you think there is a way that we can still keep an SDK in a single repo, but then have all these other subfolders as separate packages so that you... I mean, we absolutely could. Like one option would be, we could in fact do multi-module repos, but I think we've discovered that while it's awesome you could do multi-module repos and it certainly beats the hell out of having a single module set of dependencies for something as big as the network surface mesh repo has gotten. It does have challenges. So for example, there's a whole bunch of replacing cantations right now that if you want to use our SDK, you have to use to get it to work correctly because it's living in a multi-module repo. And so it's all trade-offs, quite honestly. And my general sentiment is, however we do it, I think we can all agree that we would like the platform neutral pieces to be in a different go module from the platform specific pieces when it comes to SDKs. Does that make sense to everybody? Is that something we all agree on? I didn't mean to presume. I think that's a good approach. Yeah, and then that's related to but not strictly the same question as whether we want the platform neutral and the platform specific pieces in different repos. Then of course we should be aware of the other challenges that because everything has ups and downs. So multiple repos is a bit challenging on the side of having multiple PRs merged at the same time. Otherwise you end up with broken software in general. Right. The place that this goes sideways is if the repos have bilateral cross dependencies between each other.  If for example SDK, SDK VPP agent depends on SDK, but SDK never depends on SDK VPP agent, which I think is the desirable behavior, then if you make changes in SDK and changes in SDK VPP agent, then the changes go into SDK first, then they go into SDK VPP agent, then the dependencies that are depending on both of them can update the points on the tree together. And we should be, it should be relatively smooth as such things go. Does that make sense? Yep. And come to think of it, Go does not permit. I don't think Go permits circular module dependency. Yeah. So literally, we can't hurt ourselves. We can't hurt ourselves in the worst way here. It doesn't mean we can't hurt ourselves, but the worst errors are precluded. So okay. Let's go. Okay. So I'll start breaking pieces off of the work that I've done and dropping them in this PRs for the SDK repo. The other nice thing about it is we literally have had some folks turn up and say things like, I'm looking for starter work. Or we even had someone who turned up who said, I'm programming these other languages and I have, but I don't know Go and I'm looking for starter work. And because the stuff that we're doing here in the SDKs is so small and self-contained, things like how about you go build the unit testing for this module is a very small chunk of work and very instructive if you're newer to the network service mesh or newer to go. Cool. Okay. Awesome. So I think we've sorted that out. On SRIOV, who brought this up? Because this is awesome. That was me. It was Ryan. I don't see Przemyk who I think has been doing a lot of work on this. So my question is really, I can help move this along. I hope you have the right folks here to give me some pointers. I know CI has kind of been an open question. I know there's a couple PRs out there. Probably be useful if we were able to actually pull down the code and run it. Yep. So hang on it a little bit. So out of all those things, does anyone know where we're at with this? And so I think it's hard to move this ahead. Yeah. So I can tell you what's in my brain about this, which doesn't make it real, but it does make it what's bouncing around in my head. Right. Which is that you remember how we talked about the forwarder to cross-connect network service transition, where instead of having something that speaks to the cross-connect API, you just have a network service that speaks to the same network service API that's providing the forwarder stuff. Yep. So effectively in that world, you would want to take the work that's been done for SRIOV and transition from using the cross-connect API to using the network service API. And if you'd like, what I can actually do with that is we can start by, I can point you to how the forwarder is coming together right now for the existing hand-to-hand forwarder, which hopefully will give you a pretty good notion of kind of what that's looking like. And then you can tell me if that looks same to you. And we can talk through a bit, what you think needs to happen to transition the good work that Zemmick did in that direction. Does that make sense? Sure. Yeah. And does anyone know if he's still working on these PRs that are outstanding or what? I guess I don't know who's working on what. Yeah. Usually my experience with Zemmick has been, he seems to be closer to the embedded guys. I don't know if you've ever worked with embedded for people. They tend to be kind of quiet and introverted. And so you may just want to ping him on Slack. Okay. Right. And say, hey, you feel free to ping him on Slack via direct message or pulling him into the NSM Dev channel or whatever. Because I think what you're basically saying is, this has me really excited. How do I help? Is that more or less your message? Exactly. This is something I'd like to see kind of come to be a thing. Oh, yeah. Lots of people are super excited about this. There was one unfortunate timing issue, which was we had a refactoring of, so we mentioned about the refactoring of the data of the boarding elements of the API. So we worked out that we can change these things into internet work service. So you don't ask specifically for like an SROV thing. You can get them chained in as part, as a service themselves. And so the hardware is now represented as a network service once these patches are merged in. And so this simplifies things a lot down the chain, because the previous chain was quite complex. And then we had to work out, well, how do we select which one do we want to run and a whole range of other issues? And many of those issues go away. So it'd be absolutely fantastic to, like once those patches land with the dead was talking about earlier, to make sure that this stuff gets transitioned nicely towards that. And so if you want to be helpful to them, I would recommend offering help along those lines if you have the cycles to do so. Okay. Sorry, I wanted to add that I have reached to Przemyk, I think. Before the holidays about this talk that we're preparing, we will be preparing, of course, if accepted for KubeCon. So I can say that he's pretty responsive and he's open to any feedback. And my experience with him has been absolutely fantastic in terms of responsiveness. It's just, and this has been my experience, engineers differ in their propensity to attend meetings. And he does not seem to be a meeting guy. So if you sort of look around the meeting and say, where's Zemyk? It's not surprising to me. He's still pretty responsible. Yeah, that's fine. I guess it sounds like I just need to reach out to him. So that's the big thing. And same thing with Radislav, because I think Radislav is also working on this as well. Yeah, exactly. I was going to mention that I'm trying to prepare the environment on my side so I can try and evaluate his PR and so on. So I'll be more than, yeah, it will be more than awesome to join this. So one other area you can help out as well is this stuff will eventually need to land in our CI and ensure that it works in testing. So if you have any operational experience with SRIOV, helping us with CI on that in order to set that up and make sure it runs would also be extremely helpful. And we have credits through packet.net, which has ConnectX from Melanox and also has some Intel SRIOV-enabled chips. So we can make sure that we land the right instance type if that's something you're interested in helping us. It's also true. I know you mentioned Radislav, you're trying to get an environment going. I mean, one of the simpler things we might do is just arrange for you and Ryan to have access to a couple of packet boxes that you can play with that would have it available. That would be awesome for me. I have access to a lot of Intel hardware that I've been playing with for other things, but I'm having a hard time hip-checking people that have access to the Melanox hardware out of the way. I'm sure we can arrange for that for you and for Radislav. Does that something that will help you as well, Radislav? Yeah, for sure, yeah. Okay. I mean, normal courtesy applies. Try and pick the smallest box that meets your needs. Try and be in a position to turn the box off when you're not using it, that kind of stuff, because it's just courtesy. This is also generously donated by packet. We don't want to burn their resources unnecessarily, but we also do want to put them to good use. And what you guys are doing is definitely stuff that would be good for them and good for everyone else. If you can send me your email addresses that you would like to use for your packet.net account, send them my way and I'll make sure that you gain access to the project. Yep. Easiest way to get a hold of me is through Slack. And if we do it in packet, I guess it will be helpful for the CI as well, because it would already be there. Yeah, that's exactly the thought, right, is doing it in packet, especially since one of the pieces you're going to want to do is, we're not just plumbing a random SOV interface into a pod. Yes, we do that, but we're not just doing that. Network service mesh also can let you have some sort of network service endpoint that will muck with your physical network to give you the service you want. And packet.net has a very simple API for the networking they present to their services that would let you do something like assign a VLAN kind of thing and connect VLANs to things. So you could even do like a toy network service endpoint of that sort against packet. And that would not only be a great demo, but it also is immediately useful for the CNF Testament folks. Yeah, also, Nicolai pointed out something interesting. I think it's Nicolai's stream of acquiring, Equinix acquiring packet. So interesting news. Yeah, it looks hot off the press. It looks like a good thing as far as I can tell. You know, it's sort of the peanut butter and chocolate, two great companies that taste great about it together. Cool. So the last part that we have, or are we are we done with SROV or is there anything else we want to discuss on that? I think we touched on everything I wanted to touch on. Okay, cool. I'm happy to move on. Thank you very much. Let's move on to Michael's as the NSM example with arbitring network topologies. So you have work. Yeah, we do. Yeah, cool. Do you want to share your screen? I can drop the sharing. Just I can try and share. Yeah, I'm on a very dodgy internet connection. So I can I can show things for you if you guide me, whatever. So I guess, by the way, we can start from this. So yeah, so it's nice to meet everyone. It's my first time. It's cool. So excited to be here. Thank you. So I come from a very traditional kind of networking background and kind of one of the things that we tend to do a lot is to to lab some of the designs that we're about to implement in the physical network. And that usually involves like building some network topologies out of virtual devices and doing this for a relatively small network is easy for a medium size, a large one is almost like not impossible, but it's a it's a big task. And and so quite some time ago, I came across this problem of like trying to simulate large scale to political physical virtual network topologies. And I sort of started looking at Kubernetes and back in the day, I decided to go down the path of writing my own CNI plugin because back then the CNI did not properly support multiple interfaces, etc. etc. So long story short, I, I presented this during the OSX or Open Networking Summit in Europe. And that's where I met Nikolai and somehow it's transpired that the work that the Nikolai was presenting was almost like it was yeah, it was so close to whatever I was supposed to present that it wasn't even funny. So because I was, they basically in their presentation, they presented half of my presentation. So I had to kind of repeat them. But anyway, the back then the Nikolai said that let's cooperate and build something based on an SM. So the idea is that I have some virtual network device, which could be in this particular case, and this is example is Quagga built inside a Alpine container. But in real life, it could be anything like all the big vendors, Cisco, Juniper, Arista, they'll have virtual devices that can run inside either a VM or a container. And the idea is we wrap them inside a container format and then somehow distribute them or use Kubernetes scheduler to distribute them across multiple nodes. And then the main point is interconnecting them the same way they would be connected in the real network. And in this particular case, I'm using NSM and I'm slightly abusing all the concepts of NSM. So I'm kind of like the client and endpoint, they almost lose their meaning in a way so that every link contains a client and endpoint. And it can be arbitrarily assigned to either end of the link. So I need to be very... That's actually in some sense fine and expected.  Do you remember the Lisp guys when they realized that nobody cares about ingress tunneling rotors or egress tunneling rotors is just XTRs? Yeah, yeah. You've kind of come right out of that place. And that's cool. Yeah, yeah. So, yeah. So yeah, for me, the main point was to build those point-to-point links. Doesn't matter how they build. In this case, I use kernel folder, which just connects the two types of link, vxlan or vis link. And the main idea is, yeah, I have a certain topology that has a certain layout. And I have some configuration that I want to apply to each one of those devices. And then at the end result, I want to get full-blown topology that I can interact with troubleshoot, debug, try new designs, whatnot. So this particular example just shows five routers or routers connected like this. And they each run OSPF on all their links. And they each have a unique look back. And the testing that I do in the end is just try to peek from router 5, try to ping every other router in the topology. So, yeah. So I set about abusing NSE and NSE. I'm not using the standard admission webhook basically statically injecting NSE as a sidecar. With all the correct labels that I need. And the same side for NSE. But at a high level, this is a new example. But then what I also did is I, a couple of years ago, when I first did it with my own C9 plugin, I've written a kind of a high-level topology orchestrator that it's basically orchestrator is a very good word for it. It's just like a basic Python script, 400 lines. But what it does is effectively takes the topology in a very defined and a very concise short way. So it's literally, I don't know, something that's if you could click on the network service mesh, I believe. And this will and click on the NSM5 node YAML example. So that's a similar kind of example to what we've seen before. That's the whole definition of the topology. That's how it's supposed to be connected. Then you can also optionally supply configuration files that are going to get assigned or injected into each container as a startup config, which is where you define your SPF config and whatnot. And then you basically run one command that says create. And it takes that file, the config files, the config files get injected as config maps into communities and then as subsequently as volumes. And at the same time, it creates all of the manifests that are required for NSM with all the sidecars, NSC, NSC sidecars with all the correct labels, expanding both ends of the link, blah, blah, blah. And including injecting the actual network service itself. So basically it does a lot of the heavy lifting. So all you have to worry about, me particularly have to worry about is how it looks like, not the funny bits like the annotations and labels and the environment variables. So yeah, so I haven't done a lot of testing. To be honest, I've just finished it at the end of last week when I was coming back from Pete Tomoff, had some time to work on that. So there's still maybe some bugs, but based on my preliminary testing, it seems to be working fine. It produces the right manifests and it does what I want it to do. So probably do some more testing once I get to the actual real life use cases. But for now, this is it. If I may just add a couple of updates here. So first of all, I really, really, really like this moment that I saw Michael's presentation and I was immediately, we should have this in. So I'm really glad that we finally have it. Like this whole discussion started back in September. So a couple of months later, we already have it. The other thing that actually is really interesting for me is that this is the very first time that we have some tool that runs on like uses NSM as an API, like it generates configuration files for NSM. So let's say that the first controller for that leverages NSM API, at least to the best of my knowledge. I was surprised by many things on the last NSM console. Who knows, maybe on the next NSF there will be a lot of other interesting stuff going on. And what I wanted to do, so what we have today is all these files are kind of statically generated. But I would really like to be able to make this in the following up PRs so that all these things are generated at runtime. And then eventually I was, I don't know why I was imagining that I will be able to kind of generate even these files. So I was saying, I want a 10 node topology. So if this file is generated, then it goes to Kate's top, it generates all the Kubernetes. This is all super exciting stuff. I mean, because two things strike me. The first one is, you know, it's good to have outside people using stuff. And so one of the things I'm curious about is how is your experience using NSM, particularly using NSM for something that wasn't, you know, wasn't exactly what it had been envisioned for when it started. So to be honest, it works fine. I came across a transient bug that I knew ahead of time existed. And that bug is when an interface gets created in, sorry, when an interface for the pod gets created first, it gets created in an outside of a namespace, in host-wise-namespace. And then it gets moved to a pod's namespace. So when you have two pods coming up at the same time that have the same interfaces, they may have the interfaces created in the host-namespace at the same time with the same name. And the first or the last call to create an interface is going to fail saying file exists. And then it sort of triggers off of like, because it happens very fast, I haven't had time to actually build a full story of what happens after that. It's sort of like, it goes away after some time. And in another library that used to use before when I was doing it using my own CNI plugin, they used to work around that by first generating a random interface name when they created in the host-wise-namespace, and then moving it to the network namespace and then changing it to the actual... That's actually, if you could file that issue, that would be fantastic. Because that's something we should be able to get fixed. I'll try to collect enough in our vlogs and information about that before I log in. It's a fantastic catch and it's a good example of how many eyes make all books shallow. Because we happen to... We don't happen to hit that particularly, but it's immediately obvious that it's a real problem when you mention it. And so this is super good. But yeah, we can definitely get that fixed and you're right, that is a good thing to get fixed. Yeah, I mean, the other thing that's super nice about this is this was absolutely not what we designed for. That said, I've always maintained that the measure of architecture is not whether you meet your requirements. It's whether you can easily be adapted to meet new requirements as they arise that you never thought of. And it sounds like this has actually gone really well. And that's heartening. It kind of means we maybe are on the right track. Yeah, it's a lower level of abstraction to allow other people to build something that wasn't designed to build in the first place, to do in the first place. Yeah, in that case, in that sense, it's good. Yeah, so the only thing is that fog and the fact that the documentation was a bit sparse in some places, like contrary to the notion of labels, I still don't fully understand the client and the labels and how they passed around and their meaning. But we had a whole discussion on this back over at NSM con and the consensus for most people was hop online, ask a question, get a response two minutes later. So yeah, there was a funny point. We had a panel after NSM con where the speakers sort of spoke up about their experiences. And we had two conflicting opinions. And the first opinion was, well, documentation is a little bit sparse, and that's hard. The second opinion was, oh, that's fine. Just jump on Slack. You'll get your answer in two minutes. It was from two different people who had had experiences of hitting something that wasn't well documented. And I think you shouldn't have to jump on Slack. So I'm hugely in favor of doing, you know, I'm hugely in favor of getting better documentation. But it is a good thing that the Slack community helps. Yeah, definitely. Definitely. Okay. Is this all my coming? Do you want to? Yeah, that's it. I guess we can discuss offline. So if there are any extra future steps that we want to take and generating this at runtime and all that. So, yep. Great. Now that's it. Thank you. Thank you very much for presenting this. Definitely. What is it all? Cool. Yeah. And if you run into any problems, like definitely feel free to reach out to us. We'll do our best to help you. And with that, are there any, we have five minutes left on the agenda. Is there anything anyone else would like to discuss before we close it up? Okay. Well, with that left, I want to thank everyone for your time. And we will see you all again at the same time next week. Y'all have a good day now. Thank you. I'll see you. Bye. Bye. Cheers.