What's good, Joshua Boros back again with another video somewhere. Check out the hidden signal. The rock will betray Roman Reigns and the bloodline and other huge WWE WrestleMania matches in other wrestling news. Now, a lot of you guys have been talking about this all night long into today about the potential signs and signals that the rock may be betraying Roman Reigns and the bloodline and it's actually been quite interesting some of the theories that you guys have come up with. So we're going to check some of these out in this video. Appreciate all the love and support you guys are showing on channel. We're going to get right into this one should be a good one. What is going on guys? It is WrestleMania here back with another video. Things are really heating up after the WrestleMania press conference as Triple H plans to address the fallout from Thursday's event. So join us now as we look at this week's edition of Smackdown as well as the wildest news stories and rumors you need to know including the rock signal that he will betray Roman Reigns to massive bouts plan for WrestleMania and NXT superstar injured again and much more. Be sure to subscribe and hit that notification bell for daily wrestling videos and follow us on Facebook for exclusively is also to get our new videos on WrestleMania shorts. They are a little shorter but packed with detail. But as always, we won't recap the matches, but just look at the good, the bad and the downright ugly. As always, we start off with the good is number one. The Rock joins the bloodline of the Rock is back, but he quickly made it clear that he has no use for the fans largely because they ruined the match of the century by asking for Cody versus Roman rather than the better choice. The Rock versus Roman Reigns. This segment was all about two things making sure the fans know that the Rock is heel and solidifying his spot in the bloodline. We also love the fact that the Rock was kind of meshing into errors together with his look. Yeah, $500 shirts, but in the Hollywood Rock style waistcoat. Knowing the price is now those $500 shirts must be $5,000 shirts by now while some fans were upset that the WWE didn't set up the expected Cody Seth versus versus Rock and Roman match at WrestleMania. There's plenty of time to do this and the WWE isn't rushing a storyline this epic. Yeah, they don't have to the Russian to it. It's it's going to be very interesting to see how they played this out. If this is what makes this whole storyline so great. We don't know. We may get a Roman and Rock versus Seth and Cody. They may start setting that up at Elimination Chamber. Like I said last night, Seth and Cody are supposed to be in a Grayson Waller show and Grayson was talking to Paul Heyman outside their locker room. So that could be something right around the corner. That may be a real match we have at WrestleMania. This tag team match between the Rock and Roman versus Seth and Cody. So we'll see how that plays out to more good Elimination Chamber qualifiers. The SmackDown featured more magnificent Elimination Chamber qualifier matches while Logan Paul Naomi and Tiffany Stratton's win were foregone conclusions. The matches were still very entertaining and both the Elimination Chamber matches look to be pure gold. Number three did Logan Paul just wrestle on TV? Who was the long guy wrestling them is on SmackDown last night and what was he doing with the U.S. Championship? Oh wait, that was actually Logan Paul, the WWE's resident celebrity champion making sparse appearances here and there. Now many people have remarked at how quickly Paul has mastered the grappling game with his in-ring work. He's also shown it in another way by upstaging Roman Reigns and Brock Lesnar in the art of rare appearances and even rare title defenses. But all kidding aside, Paul may not show up often, but when he does, he over delivers as seen by his trash talk and his match against them is. Number four, now he's he's killing it. He's killing it. I know I've seen some people say, you know, that this wasn't there, you know, probably the least favorite match from Logan, but I think it was good. I think it was an enjoyable match and he's he's in his element on in wrestling and especially in WWE. He's in it. He's comfortable on the promos. He's good in the ring. And it seems like he knows what he's doing. Whether you like him or not, the dude is fantastic. And I think him being in that elimination chamber, it's going to be quite interesting to see how things play out. And I do think that's when we're going to get the L.A. Knight and Logan Paul, they're going to spark their feud in there. They're going to spark their feud in there. L.A. Knight and Logan Paul. That's going to be great.  Drew's smarmy heel act is nothing short of brilliant. Nonetheless, every good heel needs a good moment of comeuppance and L.A. Knight served up some humble pie to Drew last night. So Drew hasn't held a title since Knight's arrival. Knight dug the knife in deeper when he told Drew this room on his CM punk WrestleMania tombstone shirt for his name and DM punk. It'll be interesting to see how things play out between Drew and L.A. Knight in the coming weeks. Number five, Dekodekai is on her own. Bayley is no dummy. While the role model is back to being a baby face, she hasn't suffered the massive IQ drop that often comes when heels reverberate to baby faces. No, Dekodekai may have had a big target on her back thanks to her helping Bayley against damage control, but Bayley has been around the block enough times to know whom to trust. Number six, M- Good. I'm glad that they're doing that. I'm glad that Bayley isn't just instantly trusting her. That's good. Especially, and I hope that she mentions that. Like, Dakota, you know, I watched you in NXT. In NXT, I said NXT.  Jenae, NXT. But you know I watched you in NXT. You know that some of the stuff you was doing in there, I've seen you betray people.  I like that. Have more baby faces actually remember things, you know? And then if you want to try to play up her trust for Dakota, make it seem as if Dakota really has changed or whatever. You can do something like that where it caught Bayley by surprise because she almost believed her or whatever. You can do that, but I like the fact that she's not so trustworthy off-rip. R-Truth Goodness. R-Truth is the wrestling equivalent of MSG. Now, we're not talking about Madison Square Garden, but monosodium glutamate sprinkles them on and he makes any segment just that much better. Last night, Dominic Bisteria foolishly asked Truth for help during the Dirty Dom's match against Kevin Owens, telling the 9,234x247 champion to get him a chair. True simply complied, only to take the chair and just sit on it. Simple, yet gold. The Bronbreaker joins the Blue Brand. Now, the Blue Brand just got a huge addition in the former Bronbreaker, the former NXT Champion and current NXT Tag Team Champion announced that he's now signed with SmackDown. Fans have been waiting for Breaker to join the main roster for over a year and it's going to be interesting to see how he's used. He's a tremendous competitor with a proven pedigree, but he'll need a good storyline and opponent to carve out his spot on SmackDown, a roster that seems to expand weekly. That was the good. What about the bad? His number one AJ Styles storyline is meaningless. AJ Styles is mad as hell and he's not going to take it anymore not from other WWE superstars and not even from his teammates in the OC. Unfortunately, this is anything but high-stakes drama as the OC have been completely devalued since their latest return. Gallows and Anderson compete on NXT while Mitchell wins as many matches as Selena Vega. No offense to Selena Vega, but is the WWE Universe supposed to get invested in this storyline when there are so many other more interesting plots on the Blue Brand and AOP Squashman? Yeah, they kind of dropped a ball with AJ Styles return. Like people were digging his new character like his aggressiveness and just not giving a damn. But they really should have expounded on that sooner with him not caring about his group no more. But they're just now doing it. I don't think people are going to be as interested because there's a lot of stuff that's going on that are way more interesting and people care about right now on SmackDown than just that angle. So it's going to be very interesting to see what they do with that. Hopefully they can pick it up. But right now no one gives two F's. Man, spin cycle. As good as it is to see the AOP back in WWE. We hope that they don't get stuck in the squash match spin cycle where they beat up local talent or NXT undercard wrestlers every week but fail to get any further. Yeah, hopefully this is just a one and done squash match as nothing ugly as a proper build up for elimination chamber and the WWE also further the white hot rock storyline. Would you guys think of SmackDown this week? Let us know in the comments down below. It was a solid SmackDown. I enjoyed it. That ending segment was great and it's caused even more conversation which I think we're about to get into next. Now let's move on to the news. Now first we look at the rock signaling he will betray Roman Reigns and here's why. At the top of today's news is the rocks return to SmackDown and the fallout from him joining the bloodline particularly a fan theory that the rock is setting Roman Reigns up for a fall. It's been said that pride goes before a fall and Roman Reigns is hubris is taken on mythological levels just in time for someone to knock him off his mountain while Cody Rose will be the man who finishes the story. The rock and Roman will only be starting their saga. Next user Jimmy Van took a look at a trail end of the rocks promo commenting I rewatched rocks promo look at the camera work when he says he'll do everything to make sure you walk out a loser looks like he's pointing at Roman. Oh yeah rock is a double agent on this one while some people have a tendency to look too much into things especially with WWE which is traditionally been as subtle as a sledgehammer to the skull with his storytelling the WWE has improved its storytelling ever since Triple H became chief content officer you may recall WWE hired someone to serve as its continuity chief to make sure that storylines actually make sense as they develop over time. This was seen with the late Ray Bray Wyatt's return to the WWE with its meticulous white rabbit storyline. It's clear that there's more to the rocks return than just spoiling Cody Rhodes' WrestleMania dream. The beauty of this storyline is that fans just don't know whether the rock plans to help Cody or hurt him. What is clear is that a showdown is coming between the rock and Roman plays out remains a mystery and they should make for some of the best wrestling TV in years. Yeah, the potential clue that fans have noticed is when the bloodline raised their finger up one sign sign is much different finger and thumb are extended in an L. No, he's not part of the show guns, but it's a sign that the rock is the real head of the table. After all the rock is the biggest member of the bloodline yeah success is tenfold compared to any others of the bloodline does this show that the rocks ego is bigger and he's in it for himself. What do you guys think? Let us know in the comments down below and that's a very interesting thing. Everybody's talking about that him just doing this now it's easy to just put up one finger. That's that's super easy. You see how easy it is. You just put the thumb now and some people may think you're looking into it, but at the same time people made that mention now granny in the promo.  He says that before he even starts pointing at him, but then it's the way they framed it up. You can take that is if he's pointing at the rock not pointing at Roman saying I'm you know I you know I'm going to I'm going to make you a loser and then what he said afterwards which is Cody story is ending ours is just beginning if you really think about that Cody is trying to end the story. He's trying to end it at WrestleMania and obviously the rock and Roman story is just going to begin and it may not be with just Cody getting screwed out of the match because of the rock. It may be a situation where Roman gets screwed out of the match because of the rock and that's what he meant by Cody story is ending because he's going to take your title but ours is just beginning that could be something that's why oh man we this is the speculation alone about this promo segment. A lot of people were looking at this like this may not be what it is and I personally don't think it is what it is. I do think and I hope they do this. We start to see subtle hints of the rock taking over.  Roman's comfortable. That's why he was smiling. He was happy. He's comfortable but he doesn't realize the rock is not in it because he's going to follow behind Roman. Do you think Roman you think the rock is going to follow behind Roman Reigns and his orders? No, he's not going to fall in line. And that's what's going to be the deciding factor right there. How are these individuals are these guys massive egos going to align with each other because right now Roman is clearly the top dog but in comparison to the rock. He's just a little pup even with the championship. He's a little pup and it's going to be interesting to see how they show that dynamic on television. Looking forward to it. This is great. Some great stuff man. Next up to big bouts plan for WrestleMania looks like fans could see two major matches at WrestleMania 40 besides the much anticipated Cody Rhodes versus Roman Reigns matchup. Fightful select Sean Marzap was asked about the long rumored J versus Jimmy Uso match at WrestleMania and sap answered that was the plan to the best of my knowledge. WWE has done an impressive job maintaining the heat between J and Jimmy without it boiling over before their first one-on-one matchup. Many fans doubted if the WWE could keep them apart between SummerSlam. They've allowed just enough interaction to remind the fans and confrontation is inevitable without cooling things off. Maybe they did spoil it a little at the Royal Rumble, but that was only just a brief tussle. Don't be surprised if Jimmy cost J his intercontinental championship shot against Gunther leading to a clash at WrestleMania. There's also another matchup being discussed, but this one is still up in the air. Fightful Sean Marzap also discussed Logan Paul's opponent at WrestleMania 40 noting L.A. Knight's name has been discussed. That was the plan. I don't still know if it is the plan, but that was discussed at one point. Right now it looks like the WWE setting things up for a program between Drew McIntyre and L.A. Knight, whether that happens immediately or down the road remains to be seen as the two superstars or on separate brands. As for L.A. Knight versus Logan Paul, this would make for a fantastic matchup WrestleMania as fans could expect some great promo battles leading up to the match. This could be the WWE's chance to put Championship gold around L.A.'s waist and give the U.S. Championship back to a full-time competitor. While we understand the WWE wants to belt on Paul right now to draw an even more mainstream publicity going into Mania, Paul won't need the title after the WWE showcase event. Next up an aide. Yes, yes, yes, yes. That's WrestleMania cars looking good. You can have a situation where Roman gives our orders.  Go handle that for us on Monday Night Raw. Give him orders. Do something like that or it can be a situation where now that they got the rock, Roman's feeling some type of way. He's feeling good and he has, he sends the orders for Jay. I mean, for Jimmy to screw over Jay or whatnot so he can't get, he can't win the Intercontinental Championship from Goonther and it's basically because Roman's like, see, this is, you thought you can just be fine without us. You thought you could be good without us. You thought you can gain championships without us. No, we're not having that. Nope, just to spite him because now they got Roman Reigns. That would be great. Set up a match. Boom, set up a match and then I would have Jay win at the Royal, at the WrestleMania and then it could be a situation. Roman's like, you know what? You got to go trying to kick him out because you lost. Like, the story they can tell just with that alone. Looking forward to that and also Logan Paul, L.A. Knight, they've had their back and forth at last year's Money in the Bank. What are we waiting for? And I think the Elimination Chamber is going to set that up perfectly, they're both in there. It's going to be a situation where either L.A. Knight cost Logan Paul to match or Logan Paul cost L.A. Knight to match and that's how we're going to get into it. They're going to get into it in the Elimination Chamber and then it's going to go from there and I'm all for it. WrestleMania this year, this card potentially is looking to be really, really good and they have some great storylines they can expound on. E.W.'s star returning soon. There's potential good news for A.E.W. as Dave Meltzer reports that Dr. Britt Baker has been training hard. Although she isn't cleared for wrestling, Meltzer reports her return shouldn't be long. Baker has been off A.E.W. TV for some time and for whatever reason A.E.W. hasn't been used to cut promos to help others get over. A.E.W.'s women's division is mediocre at best and a mess at worst. Hopefully she'll be back soon and while she isn't carrying the division on her back, the recent addition of Deanna Parrazzo and the rumor debut of Sasha Banks should help very much. While former A.E.W. women's champion J.B. Hater's return date remains a mystery, her return can't come sooner enough. And finally, an NXT superstar injured again. And last but not least, apparently bad news for NXT superstar Nikita Lyons as Dave Meltzer is reporting she is injured again. Lyons has been repeatedly bitten by the injury bug with her previous injury being an ACL tear that kept her out of action for nearly a year. Hopefully the W.W.B. can determine what's going on and get Lyons back into competitive shape. While she has plenty of talent, the W.W.B. might be reluctant to give her a push if they feel she's injury prone and looking at her time in NXT. It's difficult to say she's not. But there you have it folks. I will look at SmackDown. That's definitely unfortunate. I hope she's able to recover quickly and she can get back into the swing of things and hopefully it's not a serious injury. Wishing her nothing but a speedy recovery. But hey man, comment down below. Let me know what's y'all thoughts on this whole rock joining the bloodline and do y'all feel like he is a double agent?  I think he's going to turn on him. Y'all actually believe that now with this promo he had joining the bloodline and what are your reasonings? What things kind of tip that off to you in your opinion on the rock? Turning on Roman potentially at this year's WrestleMania? Let me know down below. But I appreciate all the love and support you guys shown on the channel. Road to 150K. And I'm Still Yen. Speedy, YouTube, Wrestling, Champion of the World. I appreciate y'all kicking it with me. See y'all next one. Peace.


Baltimore Ravens got it done and hopefully we can say that in a couple hours after this Raven Steelers game coming up But we are talking about them agreeing to a contract extension with none other than mr. Michael Pierce interior defensive linemen for the Baltimore Ravens who has really helped been an anchor For this Baltimore Ravens defense before we get into that I got to say I thank y'all and Carter Thanks y'all I really appreciate y'all because your comments really made his day the other day in our last video about Dalvin Cook because of course, you know, we were headed to the parking then the news came out and then Carter was like It's okay. You can go make that video real quick and then we made it and we went to the park I had a good time, but y'all comments just y'all really came through and showed a lot of love Took Carter. So I appreciate y'all doing that for baby boy. I love y'all team keeping clean y'all know y'all family y'all all uncles and aunts the Carter and stuff So I appreciate y'all big time now Back to the news Well actually before we get into the new make sure you subscribe to the channel Turn your notifications on leave a like on the video because y'all been doing that already but continue to do that And it just helps a lot. So Michael Pierce the Baltimore Ravens and Michael Pierce agreed to a two-year 7.5 million dollar contract extension through the 2025 season So if I know Michael Pierce his contract was getting ready to be up this year I know he had some void years tacked on to the back of it So I'm not sure how those impact this but a two-year 7.5 mil contract extension is 3.75 mil per year So I'm not sure if those are the accurate numbers because again, I know he has some void years on the back of his deal So I'm not sure if that impacts that but That's pretty good For Michael Pierce. I remember Michael Pierce last year to me He was a forgotten man because with him I'm like man when he tore his I think he tore his triceps or biceps and then he had a surgery didn't hit that Ended his season. So going into this season. I had forgotten about Michael Pierce I had I've been thinking about Matt a beat gave and thinking about Travis Jones Been thinking about Kaleas came before a little bit then they cut him But um, I had not been thinking about Michael Pierce But he let it be known like hey, I'm here and when you look at his numbers Because Phil Yates who reported the contract here is also reported Michael Pierce numbers I said the 31 year old has 37 tackles a sack a force fumble and a pair of fumble recoveries this season You could look at those numbers and be like They're resigning that they resigning the guy who has 37 tackles only one sack Only one force fumble and two fumble recoveries. Uh, what is he going for the quadruple single? What's that? But this is why when you actually watch the games It's important to actually watch the games to see his impact and Michael Pierce has had a huge Impact this year for the Baltimore Ravens defense even dropping back sometimes, too Who knew Michael Pierce was good in coverage as well But anyway, it was nice to see the Baltimore Ravens get that done So Baltimore Ravens, it seems like they really trying to get that d-line right and take care of those guys and knock it out The way because remember going into the season they signed Broderick Washington And then a lot of people like oh, well Broderick Washington got signed So that means just a matter be gave Friday gonna get a deal, huh? Why would it mean that Broderick Washington deal wasn't even for that much money? But I've been seeing a lot of people say the same conversation to oh they resound Michael Pierce Guess just about a big case out of you. Huh? Why would that mean that Michael Pierce did not sound for that much money? Justin Matt a big a is still going to be a priority for these Baltimore Ravens. You can trust and believe that Why would that 13 sex from an interior defensive line? Those two just don't fall out of nowhere all them QP hits he got they don't just come out of the blue Baltimore and again, they showed us already because we like what we learned and we we learned it way Like later on this season, but this past offseason this this most recent offseason that we came out of going into this season The Baltimore Ravens they tried to sign Justin Matt a big game But it obviously didn't work out cuz they no contract But they tried to sign Justin Matt a big a break Ravens knew they knew something They're like, oh, we got to try to get this dude G while we still can and because they knew they were like Oh, this dude better go off and then we are going to be geniuses because it'll say the Baltimore Ravens Oh, they signed them just in time had they waited to sign them Then his price would have been way up, but We got him but that obviously didn't happen. So Raven gonna have to cough up even more bread now another conversation that a lot of Ravens fans have been having would be this impact on Patrick Queen and Everything just depends everything depends on everything. I didn't see somebody brought up my god wallah He brought out how the Baltimore Ravens they have never paid two linebackers at the same time to two linebackers significant money at the same time So will that history repeat itself? I know Baltimore Ravens don't want it to I know they want to keep Patrick Queen But I don't know if they want to do it at all cause I like I said, I don't know I don't know. We all know they love Patrick Queen. We know that for sure and I know they want to keep him But how much are they willing to spend on a PQ now? Some other guys that they could be spending some money on which Adam Schefter brought out which I appreciate it Thanks for talking about that money Schefty He said Ravens defensive end your Davion clown. He needs just a half a sack today Versus dealers to reach nine sacks this season and trigger a $750,000 incentive you think you David McLeod want to play today? Oh, you bet as best believe he does. Will he I Wouldn't play him But I get him wanting to play and if he does play okay, but if it was up to me I wouldn't play him. I say to Davion clowning sit down But if and I know he gonna want to get that bread and I get him wanting to get that bread I want to get the bread too. I'd be like, hey, I want to play. I want to go get my seven hundred fifty thousand dollars I don't care if I'm rich or not. I seven hundred fifty thousand dollars seven hundred fifty thousand dollars No matter how you want to slice it man. So if I was him, I would be big. Hey, let me play Please just let me go get it man Mason Rudolph ain't out running me. I might miss a couple here But I'm gonna get one so Hey, let's see. Um, he also highlighted how Nelson Aguilar He just needs 58 receiving yards today versus dealers to reach 400 this season and trigger a 250 thousand dollar incentive And needs 10 more catches verse Pittsburgh to reach 40 this season to trigger a $500,000 incentive If Nelson Aguilar plays I guarantee you they will be feeding him that ball. I guarantee you because They like doing that stuff teams like doing that stuff or some some of them not all of them Actually, you know what a lot of them don't because they don't want to pay that extra money to players That's why they signed them to some contracts with the NLB TE with the incentives not likely no NLT BE Not likely to be earned in LTV That's in a lot of these contracts man. They'll give me these nice incentives. Oh, that's pretty Oh, that's a nice chunk of money But it's not likely for the player to reach that and a lot of teams don't want the players to reach it But if Nelson Aguilar plays I guarantee you Tyler, honey gonna be throwing on that ball Raven might whisper in his ear like hey, huh? Chill out on the passes to Nelson Aguilar. That's enough of those we ain't trying to give him all that money But we'll see how it all works out And he also talked about how Justice Hill now this will be a big game for him. I don't expect him to play But this will be a big game for me said Justice Hill needs 113 rushing yards today versus dealers to reach 500 this season and Trigger a 250 thousand dollar incentive my goodness What's a lot of money on the line right now a lot of money on the line for these players man a lot of it and again So I know some of y'all might be oh, yeah, they're rich. They got all this money Why why wouldn't they want even more? Why wouldn't they want even more especially cuz it's NFL You never know man. You never know when you Cut release Done so get it why you can get it why you can so Odeo Beckham, Jr. He was another one, but he already let it be known on Instagram I'm playing today. Don't don't don't bet on me with my incentives. So Odeo Beckham, Jr. Can't expect him to get his But anyway shout out to the Baltimore Ravens for how they constructed a lot of these contracts And we are getting ready to see in just a few short hours if these guys are gonna get that extra bread Cuz again all this stuff when you think about like really think about it And you ain't really got to think about all this stuff is doable all of it Justice he'll go over 113 rushing yards. That won't be a little tough But especially because it's steal is deep but still Nelson Aguilera 58 receiving yards Nelson Aguilera get 10 catches Yeah, Judea Vane Clowney get a half a sack today. Oh, yeah, like all these things are Reachable they're attainable. They're right there It's just a matter of if these guys will even play and if they do play how much will they play and if they Do play and how much will they play? How big or the steal is gonna be in trying to stop it


Hello and welcome to the session on TCP services in the TCP IP protocol suite. Here are the learning outcomes. At the end of this session, students will be able to identify the services offered by TCP. TCP IP protocol suite. Here the figure shows the relationship of TCP to the other protocols in the TCP IP protocol suite. Here you can see in this figure where the TCP stands in between the application layer and the network layer. There are different layers like physical layers, data link layers, which will be covered under underlining LAN or WAN technology. Network layer, the IGMP, ICMP, IP protocol is there, ARP protocol is there, RARP protocol is there. At transport layer, there are three protocols, the UDP, TCP and HTTP. Previously, there are two protocols only on transport layer, UDP and TCP. Now it is newly added, the stream control transport layer protocol. At application layer, there are different protocols like simple mail transport protocol, file transport protocol, trivial file transport protocol, domain name servers, simple network management protocol or the boost trap protocol. So you can see here the TCP working as an imaginary between the application layer and the network layer. TCP services, here we are going to learn the services offered by TCP to the processes at the application layer. The number of services provided by TCP are process to process communication, stream delivery service, full duplex communication, connection oriented service and reliable service. First process to process communication. TCP provides process to process communication using port numbers. Here you can see in the table the list well known port numbers provided by TCP. Like the port number 7, the protocol used is ECO and which will be ECOs the received datagram back to the sender. Like 13 port number day time, which returns the date and time. Like port number 25, which is SMTP protocol, simple mail transfer protocol. Stream delivery. TCP is a stream oriented protocol. In UDP, a process sends a message with predefined boundaries to UDP for delivery. UDP adds its own header to each of these messages and delivers it to IP for transmission. Each message from the process is called a user datagram and which will be becomes one IP datagram. Neither IP nor UDP recognizes any relationship between the datagrams. But the TCP on the other hand allows the sending process to deliver data as a stream of bytes and allows the receiving process to obtain data as a stream of bytes. TCP creates an environment in which the two processes look like to be connected by an imaginary tube that carries their bytes across the internet. This imaginary environment is shown in this particular figure. The sending process produces the stream of bytes and the receiving process consumes. Since the sending process becomes writing to and the receiving process are reading from the tube. Sending and receiving buffers. Here the figure shows the moment of data in one direction. At the sender, the buffer has three types of chambers. The white section contains empty chambers that can be filled by the sending process that is producer. The colored area holds bytes that have been sent but not yet acknowledged. The TCP sender keeps these bytes in the buffer until it receives an acknowledgement. The shaded area contains types of to be sent by this sending TCP. TCP may be able to send only part of this shaded section. This could be due to the slowness of the receiving processes or congestion in the network. Also, after the bytes in the colored chambers are acknowledged, the chambers are recycled and available for use by the sending process. The TCP segments. Even though buffering handles the inconsistency between the speed of producing and consuming processes, we need one more phase before we can send data. The IP layer as a service provider for TCP needs to send data in packets, not as a stream of bytes. At the transport layer, TCP groups a number of bytes together in a packet called segment. TCP adds a header to each segment. The segments are attached for the use of control purpose and delivers the segment to the IP layer for transmission. The segments are encapsulated in an IP datagram and transmitted. This entire operation is transferred to the receiving process. All of these are handled by TCP sender with the receiving application process unaware of TCP activities. FIGUR shows the how segments are created from the bytes in the buffers. However, segments are not necessarily all the time same size. In the figure, for simplicity, it is shown that the segment carrying three bytes and the other carrying five bytes. But in reality, segments carry hundreds of thousands of bytes. Now the other services offered by TCP, the full duplex communication. The TCP offers full duplex service where data can flow in both directions at the same time. Each TCP endpoint then has its own sending and receiving buffers. And segments move in both directions. Multiplexing and demultiplexing. Like UDP, TCP performs multiplexing at the sender and demultiplexing at the receiver. However, since TCP is a connection-oriented protocol, a connection needs to be established for each pair of processes. Connection-oriented service. TCP is a connection-oriented protocol. When a process at site A wants to send to and receive data from another process at site B, there are three phases occur. Like first phase, the two pieces establish a virtual connection between them. The second phase, data are exchanged in both directions. And the last phase is the connection is terminated. Here a virtual connection is established, not a physical connection. The TCP segment is encapsulated in an IP datagram and can be sent out of order or lost or corrupted and then resent. Each may be routed over the different path to reach the destination. There is no physical connection. TCP creates a stream-oriented environment in which it accepts the responsibility of delivering the bytes in order to the other site. Next service is reliable service. The TCP is a reliable transport protocol. It uses an acknowledgement mechanism to check the safe and sound arrival of data. We'll discuss this feature in the section of TCP error control. Now pause the video. Here is the attempt the MCQ. In TCP sending and receiving data is done as either stream of bytes, sequence of characters, lines of data or packets. Give the answer. Here the answer is A. Likewise attempt the second MCQ. The answer is A. True or false. The services offered by TCP to the processes at the application layer. Stream delivery service, full-duplex communication, connection-oriented service. Pause the video and give the answer. The answer is true. These are my references. Thank you.


Okay, good morning everyone, let me first introduce us. So my name is Sergey Lukyanov, I'm working in Miranches. I'm senior development manager and the head of a few CCP project in Miranches. So with me today, I'm Peter Prokop from Intel. He's a cloud software engineer in Kvansk from Korea. He's a software engineer as well. So the main topic for us today is to talk a bit about the OpenStack in Kubernetes and what we learned while running it on a scale and different options. So we'll have the following plans for the day and we'll talk a bit first of all about how we are taking the benefits from Kubernetes to run OpenStack. And it's very interesting because like Kubernetes provides really lots of the benefits that we can just reuse and not develop our own stuff. The next thing is obviously what's mission in Kubernetes and what we need to cover for us to run OpenStack. And it's mostly about the stateful services. And then we'd like to talk a bit about how it was working on scale and we have some lighting demo in the very end if we'll have time for it. I think we'll have. So let's proceed. So today we're going to talk about the two projects that were started in parallel. It's a few CCP and Stackinatis. Both of these projects are targeted to run OpenStack on top of Kubernetes and the main goal is to make it Kubernetes native application. Not to run external orchestration or some like black magic out of Kubernetes but really to make Kubernetes application out of it. So the next slide you can see the comments to deploy OpenStack. So both projects using the metadata driven approach where you can specify the topology configs and et cetera in the config files. And they will be just used as like for the infrastructure as code approach or something like this. And all operations are done based on the metadata for the both projects. That's like probably why we threw our site today here and sharing information about these two projects because they are like very similar but still have like lots of interesting differences. Okay, so for guys who don't know what is Kubernetes, like what I can say like for sure is a container management platform that's doing a very, very huge set of different plug abilities, like different networking and different container engines like Docker and Rocket. They mean the policies supporting the different objects and types for running their workloads in containers. So in general, you can think about it about like the OpenStack for containers and the world around the Kubernetes it's open source project started by Google and actively driven by Google so far and like there are lots of companies joining it and there is like showing very, very good growth angle and more or less showing the same story as OpenStack was showing like four years ago probably. So let's, I'm like passing the ball to Quentin. He will talk about how Kubernetes actually using our life easier. Hi, so if there is one thing that I learned since I started deploying OpenStack on Kubernetes is that Kubernetes really makes our life easier. So through a little animation, I will show you and describe you some of the fundamental aspects of a Kubernetes infrastructure. So first of all, we will deploy a Keystone deployment declared Keystone deployment here in this example, which is roughly 100 lines of YAML. So it's pretty simple. As we defined a desired count of two, Kubernetes will automatically start and make sure that two Keystone instances are running across our cluster at any given time. So now let's consider that we have a Cinder container running somewhere. How can this Cinder container discuss with Keystone? So where we have a Kubernetes cluster, we do also have a network overlay. This can be powered by Kana, Flannel, Calico, Weavnet, or even advanced stuff like OpenVswitch. So now technically we understand that Cinder can technically discuss with Keystone because everyone has an IP address. Well, but that's not great because we do not want to deal with these IP addresses and because there are maybe dynamic and stuff. So instead we should write 10 or two 15 more lines of YAML to get ourselves a Keystone service, which is another Kubernetes object. It has a service IP and it will load balance the traffic that is directed to that service IP to any of the containers that are labeled with the same, that have the same labels. So here we have application equal Keystone and version equal one. So that's pretty cool. I mean the Cinder could communicate using this virtual IP, but we don't really need to, we don't really want to deal with any of these IP addresses and stuff that again can be dynamically assigned. So furthermore, Kubernetes will periodically probe any of the running containers to make sure they're healthy and if they are not healthy then they won't receive any traffic and they will be killed automatically by Kubernetes and be risk-aduled automatically. So the health checks can be done by either a simple HTTP probe or more advanced scripts for testing MariaDB and such, for instance. So, well, how can actually Cinder communicate with that virtual IP? Because it's a virtual IP that is not suitable. It's in the 10.3 range, where the network is in the 10.2 range. That's where we have Q-proxy, which is a Kubernetes infrastructure container running everywhere and queries the service IP, like it gets basically every service IP and the list of healthy containers for that service. And then it creates IP table rules with probabilities on each node. Therefore, when Cinder tries to communicate with 10.3 the packets are going to be rewritten to discuss with one of the healthy keystone container on the 10.2 range. So like I said, it's pretty cool, right? But we do not want to deal with any IP addresses. So instead, we're going to consider another Kubernetes infrastructure container, which is called kubedns, and this thing will simply as the service name and the service IP of every service is declared, right? So now that's pretty cool because Cinder can discuss with keystone by just saying, well, query keystone, right? It's the same thing with any of the open stack services, of course. We could go a bit further and say that this internal load balancing should also be external load balancing. So to do this, we declare an ingress resource, which is again roughly 10 to 15 M lines with an host name, a service name and path and optionally TLS certificates. With the help of a third Kubernetes application called an ingress controller that can be, it's essentially a black box. It can run internally like HAProxy, Nginx, traffic, et cetera, but you don't really want, you don't really need to know what it is, right? You just have to know that it's gonna use all the ingress resources to basically expose externally on an external network, a public network, whatsoever you have on a specific port your service. Therefore, you will be able to query keystone from anywhere. So far we deployed, we declared three objects. We declared a deployment, a service and an ingress. It's roughly like 200 lines of YAML. So that's pretty short. And we've got a scalable service with self-feeling capabilities, internal and external load balancing, and also service discovery. That's a little, it's a very little effort. But we will go a bit further. So this is, so Kubernetes is able to perform updates. Basically there are two ways to do it. There's a more standard way, I guess, that everyone would know is a traffic shifting method where we will deploy another keystone deployment. For instance here, I said V2, but it can be just a configuration change. Kubernetes will again create containers for it automatically. And then we will simply change the label on the service to say, well now you have to serve V2, V2 pod instead of V1 services. But more interestingly, you can do rolling updates, right? So we will again deploy a keystone V2, but this time instead, Kubernetes will automatically reduce the number of V1 containers and start starting V2 containers instead to eventually only have our new containers running, therefore being entirely on the new stack. So I've presented some of the most basic bricks of Kubernetes. Creates do have way more features than that, way more advanced features that we're gonna describe here in such a short amount of time. But recently we got some nice features as well over the summer, such as Petsets, which are very useful for cluster, stateful applications such as Galera. We've got node affinity and anti-affinity, which goes into the same pattern. We have init containers as well for all the initialization tasks that we might have to do, schedule job for all the maintenance that we may have to do or dynamic persistent volume provisioning as well, which is quite cool, and rocket support. So rocket is an alternative container engine that has been built from the ground up for composability, security, and built-on standards. You can start using it on Kubernetes with a single flag, so it's very easy. It has various advantages, one of them being the fact that there is no daemon that runs the container, so there is no single point of failure on this, and you can live update the engine. It has also some very advanced security features, including the fact that you can run some containers with a simple CH route isolation, but you might also run containers with a more standard C groups based isolation or even go all the way with a full virtualization. I will now hand on to Piotr who will talk about dependencies, management, and stuff. Yeah, so we talked a lot about the Kubernetes, but OpenStack itself, like installation of it, is not a trivial task. One has to follow certain rules and sequence of the playing services and do some kind of batch jobs as registering endpoint, create databases, et cetera. In Kubernetes, it looks even more challenging because you have dynamic host names and IPs, and Kubernetes was not designed for stateful application and has no native support for interpot dependencies. So we tried to make OpenStack services more self-aware of their dependencies. So that's why we developed an application. We developed applications, so we divided them into two groups. One is a container level dependency management stuff. So there is a few SCP entry point, so we keep it as a Docker entry point or the container entry point. It works on Rocket too. So the state of the deployment is kept in HCD, and each container before launching an exit service is checking its dependencies via key value store as HCD. We also have a second approach, a Kubernetes entry point. So we are not using any key value store, but the application is querying Kubernetes API. It's inside the container directly, and it's checking its dependency through Kubernetes. So there is another approach, a cluster level, dependency management, another orchestration layer. Example is Kubernetes app controller. So user is specifying a deployment graph, and the Kubernetes app controller is following it with deploying application. So we had also problems with stateful application on top of Kubernetes. One of them is clustering MySQL with Galera. So to do it, we just are creating a Kubernetes job as a primary component of Galera cluster, and then using pure finder script to find another piece of Galera cluster. And then when the Kubernetes job, which is running primary components, see that the cluster is formed, it's killing itself. So under any circumstances, the cluster won't be reformed. And to use local storage for performance. Another big thing is RabbitMQ. So we used the RabbitMQ auto cluster plugin with HCD backend. The RabbitMQ is keeping its state in HCD and doing a TTL. So after a brain split, the RabbitMQ note with the highest detail will become master to easily recover from brain split. And thanks to new features in RabbitMQ, you can use in configuration files, IP addresses instead of host names. It's cool. So another thing is Nova Kubernetes drain. So we'll try to make Kubernetes aware of OpenStack deployment and not treat it specially. So for example, running keep still drain command, which is basically putting a Kubernetes node in the maintenance mode. We are catching this event through the Kubernetes event stream and triggering auto evacuation. So further, we are disabling the note in OpenStack and then do life migration all of the VMs from the note. Yeah, I will pass to Sergey. Actually, I want to continue the idea of this slide. The overall idea behind the few CPUs taken that is, I think, is that there was a very important thing to separate the layers of, let's say, bare metal LC Kubernetes provisioning and OpenStack provisioning to make them like self-containing and self-sufficient while not mixing them between each other. That's why we were doing this Kubernetes native application from OpenStack, not just running containers on Kubernetes. That's possible as well. You can run containers in Kubernetes and orchestrate with Ansible, but it's molded as the same if you will be doing like on a plain docker probably, and it's not using the benefits of Kubernetes. And this concrete feature about the draining, after draining the workload from OpenStack on a Kubernetes operation sites, it's actually a very essential part of this stuff because the operator of Kubernetes don't need to know about the workload that is running on OpenStack. And you can just run the usual operations on a Kubernetes site and it will automatically deal with the workload. So the same, I think, approach is available and needed for any workload running on Kubernetes and the separation of layers provides ability to not worry about the upper layers and to not oversee the approach of trying to go in from upper layer to down there. So you only should know what's behind, what's the layer underlay part. Okay, so for the scale, it's specifically about the few CCP. That's what we were able to run so far and it's not probably very, very huge scale. We were running on up to 350 machines with like 340 computes out of them, something like this. So all the test plans used scenarios and results are published under the Scaling Performance Working Group. So you can find fancy charts and more detailed data there. I just want to go through the highlights and some issues that we're facing when running on OpenStack on Kubernetes on some at least small scale. So on the highlight side, we were running in general various combinations. So boot and list and boot and create scenarios for another virtual machines with and without network interfaces. And for the keystone, we were running the authentication scenario to test the RPS as we know from our experience with MOS. It's one of the main thing that's going to block everything on some significant scale. So we wasn't doing any tuning over services intentionally. We were just willing to see what will be the initial results and the complaint to like the usual deployments, it wasn't bad. It was like 20 to 10% worse than the usual deployments. And it's one more time I went to explicitly repeat that it's without any tuning done. So during this process of enabling different tuning for the OpenStack components and Kubernetes itself, we were seeing like significant increase of our performance and we're still not completed. So we will probably see even better performance and bare metal due to some abilities to distribute services. For example, across the nodes and like with few CPCP and stack connectors, you can very, very easily distribute your services. You don't need to run the whole control plane on a single node. You don't need to, I honestly don't know how it's done in stack connectors, but like in few CPCP you define your roles on the go and you can say that, okay, we can run around keystone on these three machines and on one of the computes. And for example, for scale, you need to run additional Nova schedulers and especially Nova conductors. And we, for the scale testing, even try this scenario to distribute all of the control plane services across of all of the computes, just the one compute service per compute. It's not something for production, but it's very interesting that it's very easily possible to be done through such framework. Another scene is actually that for few CPCP, we build the containers from sources. You can build it from just a source folder on your local computer and just update the cloud from it so you can tune both configuration and the code of the OpenStack component on the go. And it takes, for me, I was personally trying to tune keystone on a scale and it was like two, three minutes before the attempts and between the changes. So it's much, much faster comparing to what we were using before and it's only time to rebuild a single container and push it to Kubernetes to make this rolling upgrade that Quentin was covering. Now a bit about the issue that we were facing. I want to say that all of them was not real blockers and some of them was fixed already and some have good workarounds. So I will probably start from the end. When we, half a year ago, started thinking about the test and fuel CPCP on a scale, we faced the first issue. There is nothing on the market to install Kubernetes on scale and we were evaluating different solutions and we ended up with a cargo and we write some small wrapper around it named fuel CPCP installer to just install the Kubernetes and the only stuff for Ryan fuel CPCP. And in addition to it, we were contributing a lot to cargo and the last release at two points or release contains like lots of features to run Kubernetes in a different place like in containers or from binaries with Calico or Flannel. So right now it's a very fancy installer for Kubernetes that supports different operation systems and we tested it on this 400 node scale and we like virtually pre-tested on the 1,000 nodes and done unit optimizations for Ryan and it was 1,000 nodes. So like our next step will be to try all of the stuff on the 1,000 nodes and we like right now thinking about first try on a like emulated environments with probably compute on a virtual machines and then to switch the bare metal to have a more real results as our experience showing that it's very, very different results showing when you're emulating the scale and we'll have any real scale. So the next issue obviously was how to distribute all these dark images when you're building them on a single node and pushing to registry and all 400 nodes don't have this images and in the Iranian services it's I think four or six containers on a compute node that they're sharing some common part but for example, Neutron agent and OVS with VGD share only the first layer like the first guest operation system so they have a pretty huge diff and the Docker registry itself was showing that it's not enough just to run Docker registry and like here we were doing some optimizations on the container image size and another thing that we started just deploying registry inside the Kubernetes and exposing it to all hosts through the service and it's actually improved a lot the way how the load distributed and how it's working in general and we just like mounting the host directory to the registry to increase their performance as well. So it's like on 500 nodes, it's works well for the larger scale we believe that it will stop working and we look on two options first is to scale the Docker registry itself like run a few instances probably try another backends like Artifactory or something else and another approach is that we're looking on a torrent based distribution of Docker images using the import expert or safe load features of a Docker just to distribute the image binaries across all nodes and load them locally to the Docker. Next issue that we were facing starting from probably 50 nodes testing it was a slowness of a cube DNS and the very low reliability so it was like failing showing all data and it was like really not working even on 50 nodes under the load, sure like but I think it was 1.2 Kubernetes half a year ago and with the new versions it was improved dramatically and now it works like thousands of times better and we are in addition to these improvements done in upstream and some of them was done by Mirantis guys working on the Kubernetes team. We run in the DNS mask on each node to cache DNS request to the cube DNS locally on each node and it's a couple of big bypassing to the Docker containers that we're running so it's like additional layer or decreasing the load on a cube DNS. And the last thing that we were facing for the whole times is a Docker demon freezing. So on a scale after some containers restarting and some, I don't know, bad moon phase Docker demon can freeze and is just stopping answering any API calls and here it was like lots of improvements done and the last minor releases of Docker but still it's sometimes happening. So that's like, we're using it right now as a marker of how good Kubernetes survive it. So right now it means that usually only one node will have a Docker frozen. So it's not affecting workloads. It's kind of usual hardware outage or anything else. So we're working on this issue and they're trying to find the root cause and so far we find out that there are different reasons for this thing happening. It's just interesting that they're the same outcome is visible for people when there's like demon freezing and this bug, if you will search for such kind of a bug on a Docker bug tracker, it was fixed. I don't know, like probably a dozen of times and it's still happening sometimes. Okay, so I think that's all from my side. I was willing to share about the scale testing and I wanted to switch to the short demo recordings. It's not really like a demo sets. It's like highlighting, like in recordings of how it works. So the first part is just want to show how the deployment looks like and then how some simple operations like scaling up, changing configs and changing images. Obviously rolling upgrades looks like and we have this recording for after drain feature as well. So let me switch to, okay, so for Phil's CPN was second as as for both we're using the separated namespace to deploy OpenStack and for this recording I was using a 30 nodes lab and drawing a compute on the first five nodes probably, a bit distributed between them and all of the nodes were just used for the compute. So just here I'm showing that there is nothing yet deployed and after that for both tools there are command line interface that you're working with and you need to define the metadata in a config file. So for Phil's CCP it's just simple YAML file that's have information about the way where you need to find the Docker registries, tags for images, namespace for Kubernetes, some configuration like which interface to bootstrap for Neutron, how many replicas for each service to run because it's decoupled from the topology because sometimes you want to run probably like two keystones on the same node just to increase the performance because it's like not always scaling well in one instance. So after that you can just run the deploy commands. I think that for Staconetys it's a KPM deploy and for the CCP deploy. So after running it it will get the DSLs and this config file and compile them into the native Kubernetes objects and it will just push them to the Kubernetes itself and on that point of time the work over CLI is ended, the same for the Staconetys. So the CLI is technically just a compiler from a DSL that describes how services should run on a Kubernetes and just compile it to the native Kubernetes application together with all configuration and all new stuff to run. So I think for both projects using the Kubernetes jobs for the bootstrapping and here you can see like this single time operations, like creating databases, synchronizing them, creating the users and endpoints. So all of them are described as a jobs in a Kubernetes and it's like natively running on Kubernetes and Kubernetes will ensure that these jobs will succeed. And if they will be failing it it will restart them on the other nodes so we don't need to implement our retries for creating endpoints or installation database, Kubernetes will do it for ourselves. So we're using the deployments to run the usual services and the demon sets to run the services that we need to have on each node. So I will probably speed up it because we have it's last time. So here is a view of jobs that are currently running as single time operations. And for both projects we just need to evade for all jobs to be completed to name OpenStack up and running. So in that case you see that all desired status achieved so we can try to access OpenStack with like here I'm using the OpenStack CLI to make some comments to verify that OpenStack works. In general, we have in both projects the readiness probes configured in a Kubernetes for each service. So it's there are exposing it with a real healthness of application under each component to Kubernetes. So when you get in the list of pods, for example, and see the readiness of the pods, it means it's not just container running but something inside the container is real working. So next thing that I want to show in this video is that's how we gonna to make some simple operations. So let's scale up the keystone. Like by default we have a replica one for everything. And it's currently running out of a Newton tag. So we can override the specific image spec for the keystone, for example, to run that it's from a Cata Docker image, run the three instances and enable debug and keystone. So it means that we're doing a single time three operations. We scale up keystone, change it in its config in a keystone Oslo config file. And we're switching the image from the old one to the new one. I just, it's switching to the node that's running keystone to show that it's running the old version. And after that I'll be running the command to apply. So, and here I'm showing that there is no debug logs, only info logs in a keystone log. So the real upgrade will happen. So one more time, like we changing the tag, changing the value for the debug and changing the replicas. And after that, for both statistics and CCP, we just need to rerun the deploy command and it will regenerate all needed state and push it to Kubernetes. And after that it will be natively resolved in the Kubernetes what need to be restart and actually here Kubernetes will run this rolling upgrade for keystone. And as you can see, there is one container with the old version running for nine minutes and the three new ones running for 20 seconds. And when they're starting to show in their healthy, as a healthy in the Kubernetes, it will just kill the old one. So after that we can try that still keystone works by running the project list commands. And the, after that I'm going to show that logs starting showing the debug. So I've just run the Qubectl log for one of the running container since now have lots of a debug lines. And like that's kind of everything that I was willing to show on that side. So we already, I think they have only five minutes till the end. So I will probably not show that says after drain stuff. It's just working very obviously by running the Qubectl drain node and the workload will be automatically migrated from the node using the life migration feature of OpenStack. Another scene that we need to show is like legal notices and disclaimer. Hello, Intel. And that's like last slide we have about the like some useful links and our names one more time. So like sense for attention, like some questions. So we were running it on our private labs. Are you talking, do you mean like hosted query? So on our private labs, there was no access to internet. So the hosted one wasn't working and we were not trying to, like we were trying artifactory, but artifactory showing not very good performance for Docker specifically. It's like it's not supporting divs between the common layers. It's fixed right now, but half a year it wasn't supporting. So few CPUs currently require 1.4. We, whether it depends on some features that introduced in 1.4, I think the same for Staconitis. I think like for such kind of projects, it's very important to follow the latest release and the leverage the last like features. Yep. So in Phil's P we're not right now using the Petsets. We almost have a support for them. And we are thinking about running Memcached D as a Petset to like natively use the direct names of each of the hosts. And the Petset provides this ability to have static names for all instances. So you can just use these names in a services of OpenStack without a loan balancer that directly. Right. Staconitis doesn't either use Petsets just yet. We are using some different ways as pure describe it with scripts and stuff. But we do plan to integrate Petsets like in the coming weeks as it just got released. Yeah. Actually in 1.5 there is most probably updates for Petsets will be merged. So without the Petsets updates, it's not very interesting to use them as a limiting the functionality or upgrading. Right. The same actually with the DemonSets. We like if the updates for DemonSets will not be merged in 1.5 we just migrate everything to deployments and we'll use only them in PhilCCP. So in PhilCCP we're using just a third party installation of CEP. You just need to, if you want to have like a senior volume with a CEP backend or glance with a CEP backend or Rada's gateway. So we run on all of this stuff on Kubernetes but you need to provide access to the external deployed CEP. So we're not. So sorry. So yeah, with technologies it's essentially the same you can or not use CEP. You just decide in a parameter as a single parameter and then you may deploy CEP as part of communities or not, like depending on your existing infrastructure or not. Any other questions? All right. Yeah. Right. Right now it's Takanete since we've seen that we only support CEP. Yeah, same for PhilCCP. We just know CEP better. You can always like make a pull request for it and we'll happily to update it. Yeah, we don't know any technical reason not to do it. So as I was saying in the beginning of the talk we like both projects have a goal to have a separation between layers. So we just don't care about what's kept on the bare metal level. And we just expect that there is a Kubernetes available with some list of prerequisites installed on the host operation system needed to run OpenStack. What's the next layer is managed like separately. Right. So we do assume that you already have a Kubernetes cluster running with all the nodes available, what not. Now, so this is for the Takanete and PhilCPP part of it. But of course, Kubernetes does have discovery for bare metal nodes, et cetera. So at Chorus we will mainly use IPXE to bring up nodes and they will automatically register to the Kubernetes cluster. Cool, awesome. Thank you.


Oh, wow. I wasn't aware there were computers 100 years ago. Must be Ada Loveless. It's easy to save money, by the way, doing open source. Easier than earning money. That's right. You can essentially sell fire insurances. I think I lost you, but I don't know whether it's your side or not, because I'm having a pretty good ping. Is this something that fixes itself? Okay, great. I was saying that the ping looks good on this side. Anyway, it may be just the weather. Yes. Just five hours ahead, I'm sure. Not that far in the future. Not far future. So just a couple of things. So while, of course, I'm DigitalMinister.tw, I'm also still a hacktivist. I'm kind of starting new ventures, too, working with, say, Vitalik Buterin and Glenn Wilde, Daniel Allen, and friends in a New York international NGO, the social innovation organization called Radica Exchange. I'm still on the board of the Council of Democracy Foundation in Amsterdam, which started from the 15M Occupy Movement in Spain and many other things. And so I'm a slushie. So DigitalMinister.tw is just one of my titles. But that being said, I do believe that the main contribution I bring to the table, what drove me, if you will, is that when we occupied the parliament in Taiwan in 2014, there was the first massive demonstration. That's not just a protest, but also a demo, in the sense of a demo scene, right? A demo. A demo that shows, with half a million people on the street, many more online, people can intelligently have a conversation with a collective intelligence, or ACI, with listening skills, tools. People who have never been to an internet engineering task force meeting can nevertheless, if well-facilitated, hum into rough consensus on important issues such as the trade deal with Beijing being deliberated on the street at sign. After three weeks of occupying, we eventually agree on a set of demands and which got accepted by the head of the parliament. And so people cannot un-seem that scene. They cannot un-participate from that feeling that actually some sort of participatory democracy is not just possible, it's also fun. And so the value that I bring to the table is mainly to introduce the career public service who are very much into this, because they understand this reduced the risk. If the agenda is set by the whole population, there's almost zero risk for the career public service to implement the will and the mandate of the people. But they were afraid that it would be very time consuming. They were afraid that they'll be sidelined. They were afraid that it become populist and exclusionary. They were afraid that it will lead to polarized communities and so on. And we do have that in open source, too. We had all of that, too. In open source, we had religious wars, right? Flame wars. And we also have some experience in how to merge after the fork. A lot of open source philosophy is just on how to merge after a fork. And that is the value that we bring to the table as a young reverse mentor freshly retired from the business sector into the public sector and as a kind of part-time consultant. And nowadays, of course, I'm ostensibly working full-time, but while in my copious free time also mentoring some not-for-profit startups. Yeah, I went in saying that I'm a public servant to the public service. I'm here to A, save you time. B, reduce your risk. And C, increase trustworthiness. And we can't do everything like all three of them at the same time. But I agree and I promise that I will not increase the risk or waste people's time or reduce people's trust at the benefit of some other people's time or risk or trust. And so these are Pareto improvements. That's the technical term. I make improvements on one of the three axes, but never at the expense of the other two axes. And also the secondment, that is to say public servants that volunteer to work with me but not for me because I give no order and take no order. They understand they have to come up with the ideas, but I will absorb the risk. And so that sort of collaboration, a horizontal team, if you will, is quite difficult to imagine unless you've actually participated in it. So most of my first work, aside from recompiling the Linux kernel so we can run Sandstorm and things like that, was just making sure that a personnel, if they refer to me as minister, I simply pretended I didn't hear it until they referred to me as AU or Audrey. And then we started building the culture kind of from the kernel of just maybe 20 people in the office, but then gradually into a horizontal network of more than 100 participation offices and interns and things like that. So it grew kind of organically and gradually, but I never forced any ministry to associate them with me. So as you mentioned, the Ministry of Defense never sent anyone to my office. I still know nothing about the military. That's exactly right, yes. And the Ministry of Foreign Affairs didn't send anyone for the first year, but on the second year they decided to develop their Twitter game and turns out that there are parts in diplomacy called public diplomacy that really benefits from the open innovation model. So they started sending people to my office. Yes. Well, I would say it's the norm actually in the judiciary branch and it's probably the same for you too. I mean the legal opinions, the regulation text themselves, they are not subject to copyright because if it would, only very wealthy people have access to justice. And then the proceedings, unless it's for reasons that pertains to privacy or trade secret, usually the court proceedings are in the public domain as well. So I would say the entire judiciary branch all the way to the constitutional courts work on the open innovation model that delivers the legitimacy because of the radical transparency. And in Taiwan, our parliament wasn't that transparent, but after it gets occupied it becomes really transparent really quickly with live streaming and all. And so in a sense this is the executive branch, the administration catching up to the legislation and judiciary branches when it comes to the radical transparency. When framed this way, people because in Taiwan, we only have our first presidential election in 1996, which is after the war web, that means that in people's mind there's no hundreds of years of Republican or Democratic tradition. From the very beginning it's intertwined with the web. So people think, yeah, sure, why don't we reconfigure our constitution as our kernel? Why don't we recompile it five times? That's five constitutional amendments. We're deliberating one right now. And so everything is, you can change it like the software design or integrated circuit semiconductor design, which of course the M1 chip did pretty well, I guess with the TSMC. And so the constitution and the regulations around it are seen as technology, democracy is seen as a technology. And I think this is important because for many people if the like 200 years or more of Republican or Democratic tradition is already like in the ancestors, then it tends to fossilize. But in Taiwan, this is always in our lifetime as to remember the martial law. And so it means that it is maximally hackable, if you will. That's right. Yeah, as a, of course, pioneer or as research. But on the other hand, 23 million people isn't really a small country. It's actually quite large population-wise. And so I think we have the best of both worlds. We have a kind of easy to travel landscape. The western part of Taiwan, especially from the northmost to the southmost is just barely 90 minutes by high speed rails. So people can experience each other's realities quite easily. But then we have 23 million people. So any model that worked here is much more likely to scale to other jurisdictions as compared to maybe just a 2 million people jurisdiction. And so I think the kind of R&D advantage of Taiwan lies both in the shared reality but also in the larger population. But they all have broadband. If they don't have broadband anywhere on the top of Taiwan or on the small islands as we refer to, if they don't have timid bits per second both ways at just 16 euros per month, that's my fault personally. Yeah, it's broadband as human rights. Yeah, I was born in martial law, as I mentioned. And so we understand how it's like. People were encouraged even in my parents' and grandparents' time to even snitch on each other. It's a very bad state of surveillance called the white terror. And I think it extends for like four decades or something. So the world's longest martial law period. And so we understood how bad it was. And so we don't want to go back there. And that is why the Civicus Monet human rights group rated Taiwan really as the only place in the whole Asia of the only jurisdiction that scores completely open when it comes to the rights of assembly, right of speech and right of press and so on. And this is important because this is built upon the kind of negative liberty like freedom from state surveillance, freedom from nowadays multi-national corporate surveillance and things like that. So I would say that both the positive and negative liberties are highly valued. And whenever people want to start an argument based on the kind of instrumental value of convenience or things like that, is a non-starter. People would just say, the counterargument would be, do you want to go back to white terror? And then people are like, OK, of course not. So that's how we, for example, fought off the pandemic with the heuristic saying, the state must never collect any data that we were not already collecting before the pandemic. So not using the pandemic as a data collection excuse. And that's how we fought the infodamic without resorting to things like without due respect, less DG. So we didn't take anything down for the infodamic so on and so forth. For people around 40 years old or older, yes. The younger generation doesn't remember martial law anymore. Yeah, definitely. And actually we just had a negotiation with Facebook on the topic of advertisement during election. And last year, I think Taiwan is the first jurisdiction that they really published the advertisement library in real time as structure open data for independent analysis so that dark patterns will be uncovered in real time actually and also they ban the foreign sponsored advertisements during our election season as well. So all the advertisement pertaining to political or social issues need to be domestic in nature just like our campaign finance law. And the remarkable thing is that we did that with no jurisdiction over Facebook at all and we didn't change or pass any acts related to that. We just basically said our campaign donation expenditure or even accounting process is to be made immediately open like open data and because of that it creates a social norm, a social expectation and those advertisements on Facebook back in 2018, mayoral election, these kind of become a bypass because we analyzed the data in 2018 and very few, if any, candidates filed their social media campaigns as campaign donation or expenditure. So obviously it's a way for foreign interference to enter without any auditing or accountability. And so we basically said to Facebook, look, there's two choices. You can either publish the same as we do for the campaign finance and treat it as campaign finance or even if we have no jurisdiction over you you may face social sanctions and there are legitimate alternatives such as the PTT which is the social sector maintained by national talent university students alternative to the Facebook and so on. There's also D card and many others and because of that Facebook eventually shifted their mind and then they started doing advertisement transparency. I used this very long example just to say that when we say people, public-private partnership we always put people and therefore the social sector first. Well, it didn't have that much influence during our presidential election so we didn't have that conversation but if it proves to be an issue in our next like national referendum or election session then of course we're going to have the same conversation. Oh yeah, definitely. That's what we occupied the parliament for. That's one of our demands. One of the consensus that we formed on the street which essentially said there is no private sector vendor. Private sector vendor coming from the PRC and if we get into 4G using those components then every now and then we'll have to do a systemic risk assessment whether there has been a de facto takeover by the party from the PRC side and a mortise that's going to be much more expensive than just going to Nokia or Ericsson or develop some of our own and so the decision was made then to exclude PRC in all the procurement not just telecoms but also anything pertaining to sensitive data or cybersecurity or national security or things like that and by 2015 I think we erased all the components from PRC so that's five years ago. Yeah, of course. In all our procurement tenders this is making sure that the PRC supply chain do not take a hold in any of our ICT facility. This of course only pertains to things in the data pipeline so I don't know about, for example, the medical masks. I mean we produce a lot of medical masks locally but we're not banning PRC medical masks. They're still quite helpful. Like 5G and Tina or entire Raspberry Pi. I've seen this video. It's getting easier nowadays though and I think nowadays the Taiwanese companies even when they manufacture some of their parts in the PRC they aim to do so for primarily PRC audience PRC customer, more and more customers elsewhere in the world are asking for a different supply chain configuration and this trend has been accelerated during the COVID and during the few months where the PRC was not at capacity so yeah, I think this trend is increasing. We see more and more manufacturers essentially maintaining two supply chains. That's exactly right. Yes. Oh yeah, yes. Yeah, one is primarily for their productions that's ultimately targeting the PRC market and the other one that's for the non-PRC market. Well, at this moment the Taiwanese public service is free to use whatever word processing software as long as it produces open document, period. And so I'm sure Office 365 also produces open document. That's my position. So in essence what we're saying is that we want to do everything to ensure the freedom from vendor lock-in, especially in education sectors where if the vendor lock-in sets in during people's like digital competence curricula then essentially it creates a generation of people beholden like locked in to particular vendors and we can't have that. And this is not just about Microsoft, it's also about pretty much every other proprietary software vendor. Now I don't have anything against PowerPoint but I will simply say that if we lock people into particular features of PowerPoint that can't be expressed in liberal office then we are in real trouble because then it builds a kind of vicious cycle. Yeah, as I mentioned the literally first technical thing I did as digital minister four years ago was to recompile the Linux kernel in the government cloud so that I can run Sandstorm. And later on I would get the best and brightest which would went on to win the second place in DevCon the next year in DevCore in Taiwan to do a thorough penetration testing of the Sandstorm system which they file three CVEs. And after that we're pretty sure that this is secure because it's a security product. It's safely sandboxing pretty much all the productivity software the spreadsheet part, the EtherCalc I personally maintain and into the office workspace. So Sandstorm while it's not like centrally developed nevertheless pieces together sufficient amount of new innovations like the HackMD which is also a Taiwanese team and then we just repackage it into code EMD within the Sandstorm system. So it's a cloud service of course you want to collaboratively edit markdown or reach text it has to be like cloud hosted but it doesn't mean that it's just service as a software substitute if anyone can fork or clone any of the greens in Sandstorm and modify the code and even publish their own apps it's called citizen developer except now it's more like public servant developer and they can develop their own applications knowing that the single sign on the cybersecurity are all taken care of and so one of the most trendy apps in Sandstorm here in Taiwan public sector is a simple form to order lunch boxes together which we use practically every week and anyway we have this photo of all the lunch places around the cabinet office but anyway I digress so the point is that one does not have to give up control just to go to cloud enable it just means that one needs to work more with white hat hackers with penetration testers yeah I know and that's something that we kind of overlooked during the fork from free software movement to the open source movement because we were kind of worried about the market adoption of freedom one and two and three which is the freedom to fork collectively but really freedom zero which is the freedom to use it for any purpose that is actually something that we're now defending much more nowadays in the time of software and service or service instead of software but preferably service but also software that's right that's right yeah sure so we're now entering the second phase of the national digital strategy and which is called DIGI digitization innovation governance and inclusion and I would say that the digitization the first pillar and all that we're pretty much there there's of course still room for improvement but we're pretty much there the innovation with the enabling like sandbox acts presidential hackathon and things like that there's a pretty good room for growth but again according to the world economic forum time has been for the past couple years one of the four super innovators in the world so we're doing okay so the focus for the next couple years is going to be on governance and also inclusion because we do not want AI to become authoritarian intelligence we're wanting to become assistive intelligence and for that all the 20 different national languages need to be on equal footing instead of just forcing people to speak perfect English or perfect Mandarin right so that's the inclusion part the governance part we are seeking and almost getting GDPR adequacy I think the only missing piece in the puzzle was the dedicated independent data protection authority we do have data protection authority but not a single independent national one we were more like Japan in that regard so we're going to I think within a month or so stand of a kind of foundational acts for a independent DPA and we look forward to implement not just GDPR but also parts of the currently being deliberated the EU Data Governance Act specifically about data collisions and collaboratives that is the part that we're also very interested in California too although it's not yet a country okay sure yeah I think disruptive innovations to me is best when it disrupts the technological sector rather than disrupts the society because things that are disrupted to the society usually have a large impact but negative with a minus sign to it while the truly disruptive but to the technology sector but beneficial to the society innovations such as for example just today right Ethereum switched from this old carbon dioxide burning proof of work to proof of stake for the mainline Ethereum 2.0 it's really good but it's disruptive I guess mostly to the Ethereum developers but it is just an environmental friendly gesture to everybody else actually the term open source itself was such a disruptive innovation by the benefit of the community so in that vein I would suggest that in the next few years we'll probably arrive to the point where the co-presence of realities can enable the liberation at scale even without people taking high speed rails to enjoy each other's company that is to say face to face like meeting and flying past it we'll enable us to talk not just about the episteme not just about the knowledge as we are doing now but also about the affect the feelings the ambience and things like that which at this point is unable to transmit over two-dimensional glasses such as this very one I mean we can project some gestalt to it but it doesn't really work and so some sort of co-presence technology I think would be quite inclusive in addition to disruptive that's right that's right okay definitely definitely we'll I mean I have XR space.io classes with me it's just in the next room and it's pretty good as VR glasses go and I also try magic leap although the viewing field could be larger that's definitely the place to go the VR one it doesn't have this problem because it's essentially taking lives in and reprojecting that's what XR space is doing no no no the XR space is really lightweight I can wear it for like three or four hours and it doesn't use a controller it's purely gesture so I think it's pretty good it really redefines to me the VR experience because previously I was like you I can't do this more than one hour but with XR space which is like built in 5G really lightweight and gesture only I can do this for hours awesome sure I'm going to clap to catch up yes definitely and I'll send you a copy of my local recording and if you can send me your local recording too that would be awesome okay thank you cheers live long and prosper bye


Hi everyone, I am Dr. Radhika Narendra Barde, a second year radiology resident at VKL Vallavalka Rural Medical College and Hospital Ratnagiri. The study that I shall be discussing today is Cartagena Syndrome, a Radiological Perspective. So this case came to us in the month of September. A 39 year old unmarried female, known case of cytosine versus presented the chief complaints of shortness of breath and frequent episodes of lower respiratory tract infections throughout her life. The surgical history included pulmonary lobectomy done in childhood, no family history of cytosine versus bronchic cases or sinusitis was present. The investigations performed were chest x-ray, a high resolution CT thorax, CT of the paranesal sinuses, contrast ring hand CT and ultrasound of abdomen and pelvis. The chest x-ray findings revealed a right sided cardiac apex and a right sided aortic arch, indicative of textrocardia, a left sided stomach bubble, hyper implanted lump fields, flattened domes of diaphragm and resection of a sixth strip on the right side consistent with history of lobectomy. On high resolution CT of thorax, we see hyper implanted lump fields with emphysematis changes in both lower lobes. Significant cystic and tubular bronchic tated changes are seen in the left lower lobe and tubular bronchic tated changes are seen in the right lower lobe. Inspecated mucus plugs are seen in few of the dilated airways giving it a classic finger and glove appearance. Multiple central lobular nodules are seen scattered bilaterally, collapsed consolidation involving the posterior and medial basal segments of the left lower lobe are seen with few dilated air bronchograms within. Another interesting finding was that of a multi-loculated, multi-septated cystic lesions within the superior mediastinum in the left paratracheal location. There's a communication seen at five o'clock position with the trachea, suggestive of tracheal divertically. Another finding was that of a dilated thoracic esophagus. Here we can see dextrocardia with reversed positions of the vertebrae vessels, a right-sided aortic arch and pulmonary artery, along with left-sided superior vena keva, inferior vena keva and azygous wave. On ultrasound, we can see reversal of the position of vertebrae vessels with the IVC being on left and aorta on the right. There's also reversal of the position of superior mesentric vein, which is on the left, and superior mesentric artery, which is on the right. Another finding was that of a midline liver extending in bilateral hypochondriac regions, along with myelipatomegaly and polysplenia in the left hypochondriac regions. CT of the paranasal sinuses revealed hypoplastic sinuses and bilateral maxillary spinoid and frontal sinusitis. A relatively hypoplastic middle nasal turbinate is seen here. Coming to the diagnosis, so our patient presented with history of frequent colds, chronic cough with expectoration and recurrent pulmonary infections leading presenting from early childhood. The radiological findings in our case are dextrocardia with cytosine versus bronchic cases, bronchoceles, central lobular nodules, pan sinusitis and hypoplastic paranasal sinuses, tracheal diverticulum, midline liver and polysplenia. So, diagnosis of Cartagena syndrome was made based on the clinical presentation and imaging features. Cartagena syndrome is an autosomal recessive genetic disorder, a subset of primary cillury dyskinesia, characterised by a triad of bronchic cases, paranasal sinusitis and cytosine versus tetanus. The estimated incidence is 1 in 30,000 live words, male-female ratio is 1 to 1. A gene mutation at DNA I1 and DNA H5 leads to impaired cillury motility and mucosillury clearance. This predisposes the patient to recurrent sinus pulmonary infections, infertility and errors with left-right body orientation. Coming to features of Cartagena syndrome, bronchic cases in patients of Cartagena syndrome is an acquired condition. It results in airflow limitation, obstruction and impaired clearance of secretions, leading to repeated respiratory infections. Chronic bronchitis bronchiolitis and emphysema are often associated with bronchic cases. The second finding was that of central lobular nodules and bronchoceles in both lower lobes as a result of super added secondary infection. Acquired tracheal diverticulum is due to increased intraluminal pressure and weakened tracheal wall, resulting from chronic kerb, bronchitis, bronchic cases, emphysema and recurrent respiratory infections. Pancytus occurs in almost 100% patients of Cartagena syndrome, which results from accumulation of secretions inside the paranesal sinuses, eventually leading to hypoplasia or a genesis of paranesal sinuses. Textrocardia with cytosine versus is present in nearly 50% patients of primary CLE dyskinesia. This immediately raises the suspicion of a genetic disorder with multi-organ involvement in patients since it's a very uncommon radiological finding. Another finding in our patient was that of midline liver and polysplenia, which again is a rare coincidence in Cartagena syndrome. A diagnosis is based on patients' history and radiological findings that is X-ray, CT and ultrasound, which can further be confirmed by genetic testing. So following the diagnosis, goals of management are improvement of the lung function and limitation of the disease progression. The treatment strategy includes aggressive antibiotic therapy, prophylaxis immunization, strong pulmonary toilet, regular physiotherapy and in patients with recurrent pneumonia and hemoptysis, we advise segmental lung resection or lobectomy. So to conclude, early diagnosis and symptomatic treatment as well as prevention of the infections is important in patients of Cartagena syndrome. Granting access to proper diagnostics and referral to a higher center is necessary. These are my references. Thank you.