Russian Army's paratroopers have approached Ukrainian fighters' position in an armored combat equipment and opened fire at them. Later, the invaders trying to take a position in the nearby trenches were targeted by the Ukrainian Army. Abandoning their Elf fellow soldiers and fleeing from their position, most of the Russian invaders were killed while attempting to escape.


COVID-19 vaccines are now available for children ages five and older. It's normal for parents to have questions and concerns when making a decision for their child's health. It's critical that you turn to the right resources for accurate information. We're here to help. We encourage you to speak with your child's pediatrician about the COVID-19 vaccine to make an informed decision to protect you and your family. COVID-19 vaccines are proven safe and effective. Visit scdhec.gov for more information.


I'm Rosa Abraham. I'm a postdoctoral fellow at the Centre for Sustainable Employment which is based in Azim Premji University in Bangalore, India. I actually had no formal training in labour economics. I kind of stumbled upon it while I was doing my PhD. And so this was actually giving me some methodological rigor that I was desperate for. A lot of labour economics and a lot of the labour economics theories as well as the textbooks are developed in a western country context. So it was really useful to not just attend the classes but also to see other researchers who are working in related topics and seeing how they are looking at these questions. It was useful for me and I think it's something that I will take back. Just that experience but of course the methodology that I have learned is also something definitely that I want to take back to the classroom. A lot of things are you supposed to just learn on your own and by reading papers and just coming here and learning it from people who have in a sense developed some of these methods. It was just fantastic. But I think the more personal highlight was to meet Gary Fields because he's just somebody that I and I told him that I've known you as Fields 2003 for the longest time and to see him in person and to be taught by him and to interact with him was just amazing.


Hello and welcome to Nias Klick. Today we're looking at a case where a 21 year old climate activist has been taken to a remand for five days by the Delhi police. She was flown out of Bangalore and brought all the way to Delhi. And there are interesting legal developments which are taking place, which are crucial to understand the case. And Disha Ravi has been the founder of Friday's Future India, which is an organization which was looking at multiple campaigns. And the allegation against her is the fact that she had edited a document on Google Drive, which was shared by Greta Thunberg, the climate activist from Sweden. And she had prepared a document in favor of the ongoing farmers protests in India to amplify the campaign. And we're discussing the legal developments today with Kotlin Gonzales from the Supreme Court of India, as well as from the Human Rights Law Network. And thank you, sir, for joining us and speaking with us. A major issue which is being discussed currently about the case is the fact that she was sent to the remand without the magistrate, you know, her council being in front of the magistrate with her. So this is a big question and the kind of repercussions that it has. So can you explain that to us as to what has happened and why this is so crucial? Well, it's really very simple. The Supreme Court has declared quite some time ago and has repeated that order again and again. And that is that a legal aid lawyer is required to be present. And the accused may demand a lawyer of her choice as well at the stage of the first remand. And apparently that was not done. And it's not understandable as to how the remand magistrate proceed in the matter. One, second and equally important is when there is no evidence shown to the court of her involvement in any crime. No evidence, I said. Not just a story. A police may give you any story that they want to give you about Kalistan and all that. But it is the duty of the remand magistrate to ask, do you have anything with you today, apart from your general theories and your general, you know, fairy tales, so to speak, what is the evidence you have today? And remand magistrates are routinely making this mistake. You must insist to see the evidence before you remand the person. I'll explain this a little bit. You see all over the world and in India as well, you conduct an investigation. The police does that. No problem. The police could have conducted an investigation against her. But they only arrest when they have a good enough docket of documents, proof, evidence, that she is involved in some criminal activity of a serious kind. Now this guy is this remand magistrate is going in the reverse direction. He's accepting the story and he's presuming that after 90 days when the police filed the charge sheet, then some evidence will come up. But then if evidence is going to come up, then you can't arrest now. So it's a totally illegal arrest without any evidence requiring the custody of the freedom of a person to be caught in. Absolutely. And there are other two activists and non-ailable warrants have been issued against them as well, Nikita, Jacob and Shantanu. So what kind of a case do you see is building up now? And it's just the kind of message that it is sending out to young climate activists or young activists and people involved in politics. See they don't have a case. They're building up something in the air, you know, castles in the sand, so to speak, or what are castles in the air or whatever. They don't have a case. Right? What can the case be? Toolkit. I've read the toolkit, you've read the toolkit, the whole country has read the toolkit. In fact, it should be used by all activists throughout the country now, since the government of India is challenging us on this toolkit and is making a big hoot about it throughout the country. People should now spread this toolkit, use the tool, believe a step-by-step guide to peaceful, democratic, secular actions. Yes. What's wrong? So I think now we should take advantage of that situation. So what case do they have against them? Nothing on being linked to the, you know, the Kalistaan movement, nothing. Nothing. So I think every journalist and everyone asking the government should ask this question. You've curtailed the liberty. You are making out as if some grave offence is there. So tell us, sir, the whole country wants to know, as somebody would say, the whole country, the nation wants to know what is the evidence against them that you curtailed the liberty. And everyone will tell you, we'll tell you after 19 days as the investigation goes on. So they are fishing, they're fishing, hoping that they'll catch some fish, but there's no fish to catch. And you know, the process being so excruciating, especially for young people and activists like her. So how do you see this process for young people and the kind of chilling effect that it might be sending out to so many people? See, the normal answer that a person would give you is that it has a chilling effect on young people and so on. Yeah. But that is undeniably true. Of course. Exactly what the government wants to do. It wants to bully you.   Right? Absolutely. So that's exactly what they want to do. Chilling effect is another word for bullying. But I look at it in a different way. I want to tell all young people in the country, take this as a super opportunity, super opportunity, because they've got no case against it. Shameful. No case against it. Take it as an opportunity and challenge the government toolkit. This is what I'm using. And this is, and throughout the country, take the opportunity and chance today for peaceful, democratic, secular protests. Spread it. This atrocious government, this very autocratic and pernicious government has given us a chance by making the toolkit, the center of their attack. So we'll make it the center of our counter attack. Everybody use the toolkit, not for violence, not for something undemocratic, but for democratic, peaceful protest. Everybody use the toolkit. Let's see who will survive. Will the attack survive or the counter attack survive? So young people throughout the country, don't be afraid. Don't go on the back foot. Don't feel bullied and threatened. On the contrary, take this as a unique historical chance, a once in a lifetime chance in India. Go on the attack and say we are not going to be bullied. We are not going to be threatened. We are not going to back down. This is a new India. This is a new generation of young people. And we are not going to be threatened like this, bullied like this anymore. Just one last thing. So this is a very important message that you've just given, because these kind of cases can create an atmosphere of fear like that. But just, you know, what happens with the 90 days, if they do come up with evidence or they just create evidence. So then how do you see this case taking its legal course? Do you feel that, you know, after 90 days, it will be done and dusted, but too much damage could have happened by then? See, have confidence in yourself.  Now take this girl who's in jail. Did you fire a gun? Did you throw a grenade? Did you kill somebody? Did you conspire with some, you know, deadly terrorist? In your heart, you know you're innocent. Why should you bother what they're going to do in 60 or 90 or whatever days, you know? Why should you bother? You know that they don't have anything. Challenge them, face them. See, a person doing some kind of underhand activity, some planning, some criminality. You have reason to fear. Once you are moderately on the right track, you have no reason to fear. No matter what they do, have courage and face these tyrannical people, the tyrannical government, the tyrannical police force, who thinks they can take India in this direction of, you know, state terror. What are we doing? We are battling state terror. We are battling police terror. And very often nowadays, the biggest terrorist attack is coming from people in power. It's the old colonial system again. They terrorize the freedom fighters, calling them terrorists, isn't it? They use sedition against freedom fighters, calling them terrorists. It's the same. So, recognize yourselves as the freedom fighters of today. Recognize yourselves as the foremost citizens of India. It is your duty to protect India. It is your duty to defend India against anti-national forces, anti-national forces in the government, anti-national forces in the police. It's not worth the law to destroy the law, to break the rule of law. Today it is us who tell them that they are the new anti-nations. And we must boldly say, reverse the dialogue. You are the anti-nationals. We are not going to be bullied by you. We stand for a strong and great India. We will not allow you to bully us like this. Thank you so much, sir. On that note, we will end this interview, but we will continue to, of course, bring our viewers, our readers, extensive coverage of this case and, of course, take your message forward for the kind of fights that the young Indians are envisaging today. Thank you so much. Thank you. Thank you very much for doing this. Thank you very much, news click, for doing this and standing up.


You see these ravens, they've been doing stuff in the background to prepare for the possible extension of one Lamar Jackson, let's talk about it. First question came from my guy, Siderian, he said, I ain't graven, hope you and the fam all well. Hey, we are doing really good, I hope you and your family are doing even better. With the ravens drafting 10, well it was actually 11 players and having several roster spots occupied by undrafted free agents, it seems like the ravens are purposely getting younger. In preparation for Lamar Jackson's contract extension, I honestly can see all of the drafted players making the 53 man roster and some undrafted free agents as well with possible PUPs and IRs. This gives the ravens a large percentage of players that will be signed to rookie contracts on all 3 sides of the ball, cushioning whatever Lamar Jackson's future annual cap number will be. What are your thoughts behind this? P.S. I got my David Ajabo prediction right, hopefully he can play later this season, but I wouldn't mind red-shirting him either. So congratulations on calling the ravens drafting him back in April. But as far as the way that they're building the roster, I mean, they would have been doing all this stuff either way, whether Lamar Jackson's getting paid or not, because they simply needed to retool the roster. And the way that free agency works in the draft and all that, you, I mean, in Madden I do it, but I know real life not, isn't always Madden, a lot of times it is though. But in Madden, if I'm retooling my roster, then as far as free agents, I'll look for a few different guys that are like at premier positions. If it's, I'll look for like an offensive lineman. I may look for an edge guy. I'll look for a wide receiver depending on who it is. I'll look for a tight at what? I guess I really just look for anything. Cornerback safety. A lot of stuff, but I can only do so much and gotta do a lot of reloading through the draft. So even with Lamar Jackson's contract coming up yet, they certainly had to, they gotta do a lot better when it comes to not only drafting, but getting impact players from the draft guys that can come in right away and be difference makers. You have to have that, especially once you pay your quarterback.  You should be doing it, but you should definitely be doing it after as well. So yeah, it is for Lamar Jackson's contract, but it's also just for the team too because they had a lot of spots and a lot of holes on this roster that they needed to plug and play. So they did a good job drafting. They still got a little few things that they go fine too, but they did a good job with the draft based off of how good some guys are projected to be. They of course, we gotta see it and no draft is truly greatable until like two, three years down the road. So we'll see when we get there on paper, the draft is good, but now we gotta see it on the field. We gotta see the impact from guys. We gotta see how guys, well, if they are truly quality depth for the Baltimore Ravens. And we'll start to see how that works to self out over the next, over the next week and over the next couple of weeks in training camp, then in preseason, and then the season will be here and then we'll be able to start to evaluate, but the evaluation doesn't just finish after one season for rookies. Now we hope that these rookies can come in and it's like, whoa, man, oh, they came through.  I'm glad that guy's a Raven. Wow. He made such a big impact.  You want the guys with the higher draft status to have a higher impact, but you also want guys with low draft status to have a higher impact to as much as they can. You know, a lot of the times the guys that are picked lower, they're going to be getting less playing time and a lot depends on the situation, but bottom line Ravens need more impact from their drafts, more immediate impact from their drafts. Lamar Jackson, once he does get paid and hopefully is from the Baltimore Ravens. But once Lamar Jackson does get paid, yeah, eventually his cap number is going to go way up. It's going to take a significant amount of money from the cap, from the salary cap. Now there are, that does not excuse the Baltimore Ravens for, from providing for Lamar Jackson. So I want to make that clear, even though I think we've made that clear already. We've got to continue to make that clear just because Lamar Jackson is getting ready to get paid and again, hopefully it's from the Ravens. But if the Ravens pay Lamar Jackson, this does not excuse or prevent them from supplying him. They should have been supplying him more already, but hey, that's the past and we're in the present now. You get the point. Yeah, this feels like a dream, just what I made, you two team, keep it clean. You see my boy, he like, I done made it, I done made it, boy, that's my home. He ain't that right in Raven, right in Raven. Way too early. Next question came from my guy D3, he said, what's happening in Raven and team keeping clean? I hope that you and your family doing well. I have two questions for you with the pride that the Ravens taking their undefeated preseason records. As of right now, who do you see us signing as an undrafted free agent? Oh, you mean like keeping on the roster? I think the answer to this question is actually the title to your question. Way too early. We haven't got to see any of these guys yet on the field in the game. I haven't even got to see a training camp yet. So I can't even answer that because my first thought went to maybe one of the wide receivers, but we haven't seen him in action yet. So I can really can't say. But number two, he said, does the undefeated preseason solidify the fact that EDC has had solid drafts during his tenor as GM? He catches a lot of heat with some for draft picks not panning out while completely ignoring what he has done midseason to improve the team. Oh, I love that question. That's a really good question. Again, thanks for the content and please keep up the great work. Appreciate you a lot, man. And I do every single comment section. Oh, you see my god, D3. So does the undefeated preseason solidify the fact that EDC has had solid drafts during his tenor? No, I don't think it does. Reason I say that is because that's preseason. That's preseason. And you want and need impact in regular season. You want and need impact come playoff time. So you want and need impact when it counts the most preseason. Their preseason record is great. It's fun. It keeps us tuning into the preseason. It's fun to think about. Hey, we we preseason Super Bowl champs every year. Let's get on. I don't even remember the last time they lost. I forgot when it was, but it's been years. But that's preseason. It's preseason. And guys have got started. It is a nice confidence booster for a lot of young guys that are on the squad. But preseason, in my opinion, preseason is not enough. Now, with Eric Dacosta's drafts, he he can't do everything. He can draft the guys, but it's also important because context is everything. It's also important that because we talked about in the previous question, getting high impact players. But it's important to know that he's not a coach. He's a GM. So his job is to build the roster, construct the roster, make any trades for the roster, personnel decisions for the roster. But he does not play the roster. He's not in control of the scheme. He's not in control of the coaching staff. The coaching staff, they're the ones that got to put these guys in positions to succeed. And a lot of times we've seen it to where guys, they end up leaving or not panning out and I use quotations when I say that because a lot of guys just weren't really given the right opportunity. Guys will have done something great in college and they get to the Ravens and the Ravens are like, Oh, you know what? We're not going to have them do what they did great in college. We're going to have them do something completely different. And it's not like that with every single player, but a lot of players, it can be that way where the Ravens just completely changed who that player was and try to make them something different and it just doesn't pan out. So not everything is on EDC. It's a group effort. It's a collective effort. There are guys that some guys where it's worked out great. Some guys where they've drafted them and it's worked out phenomenal. It's been, oh, let's go. Oh, great job. Then there's been other guys where it hasn't been so pretty. So it goes both ways, but it takes everybody in order for each player to have success. And of course, the players themselves, too. Budget buster. Next question. Wait, this is been a long time. Next question came from my guy. He's not going to go so, baby. Anyway, he said, I engraving. Hope you in the family having a great summer. We all it's really hot down here, but I love the heat. We're not traded for the cold ever anyway. He said, I'm sure Carter haven't met a second Ravens legend and Lamar Jackson. We know you're the goat. Not at all made that made his day. Oh, yeah, it sure did. He they love me to Lamar and hopefully he gets another opportunity to meet him again this week. But we'll see. Anyway, you said here's my comment slash questions when Watson signed that massive contract with the Browns, even with so many questions looming about his past actions. I thought it was an outlier, a bad business decision by the Browns, but a move in line with the Browns previous QB history. Yeah, it was great.  But yeah, it was wild. Anyway, he said, personally, I imagine EDC and Bishadi cringing at the thought of paying Lamar that kind of money. Now, with the Cardinals extension of Kyla Murray, it suddenly makes two 230 million dollar contract extension, the new norm. Yes and no, because the Sean Watson, two hundred thirty million dollar contract, two hundred thirty million dollars guaranteed Kyla Murray's two hundred thirty point one million dollar contract. So slightly above what the Sean Watson, I think he had. Was it a hundred forty nine? No, one hundred sixty. It was it was seventy mill less. So thirty forty. So yeah, one hundred sixty mill guaranteed. So that was the big difference between those two. But anyway, let's keep going. He said if the Ravens don't want to break the bank to sign a top number one wide receiver, what makes people think they will break the bank for Lamar Jackson? Oh, that's a question right there. But to answer that question, because they already have Lamar Jackson and they they know what he means to this team. And I as much as he's done for the Ravens already, a lot of the success that he's brought, a lot of the things that he's covered up, the deficiencies that he's covered up for them to all while not he's he's done this all while not even being his best. All while not even having reached his full potential yet. And I say that because I just really don't believe he's reached his full potential. Reason being, because I don't think they've put him in position to reach his full potential, I think they've limited him a lot. They've held him back a lot, a whole lot. And this is nothing new that we've been talking about this from last year to and in the year before it's just it seems like they like, oh, you know what?  We're going to reel you in. All right, calm down, chill out, chill out. But anyway, he said his potential contract could end up being twice as much, 240 mil as the 120 mil contract that Flacco signed. Oh, wow. How long when was that? That was 2013, where he signed that deal. And yeah, now that's 2022. Wow, QB salaries. Yeah, they've doubled. It's taken a little while though. It's taken about nine years for them to double, but still. Yeah, man. Wow. Thank you for that. I appreciate it. Like reflecting on that. He said some of my questions are number one, do you think the Ravens will come up with the money to sign Lamar to a new contract? Oh, that's pretty straightforward. I hope they do. I hope they do. I just I wonder, I know, because I know a lot of people have said that. Oh, yeah. Like like you mentioned, the Deshaun Watson contract, that's not the new standard. That's not going to be the new norm. But Lamar Jackson could look at that like, hey, hold up. This dude, he hasn't played in a year. So he's been gone. He's been out. He has all these allegations going against him. And whether they're true or not, hey, who knows? Again, only Deshaun Watson, anybody who was involved in whatever, only they would know. But he got all that all that unknown going on right now. But the Browns still with that information. They still gave him $230 million guaranteed. Fully guaranteed. Has he won a Super Bowl? No, I think he only won one playoff game, too. Now, we know when he played, he could do some stuff now. Deshaun Watson definitely a talented quarterback. That boy can play when he did play. But with all that being said, and they still gave him all that money, Lamar Jackson could be looking at that like, hey, what's up? That's that's what we starting at. That's what we starting at. And it actually needs to be higher, especially because, you know, timing and everything. But that's that's what we starting at. Y'all want to talk? Hit me with that. I ain't got nothing against it. Ain't got no allegations, none of that stuff. I'm team keeping clean. So it's like and I've been here and y'all know what life is like with me. But y'all certainly know what it's like without me, too. So you make the decision. Hey, I'm good. I got money. I knew I could I could play out on this twenty three point one. This 50 option cool. I play out on it. That's fine.  If y'all coming with this little rinky thing stuff, this little chief said, no, straight. So hopefully the Ravens make the right decision. Hopefully they make the right decision. Um, do I think they'll come up with the money to sign Lamar to a new contract? It's there. They can do it. They can do it. It's just up to them to make it happen. Do I think they will? I would lean more towards the side of, yes, there's always that little possibility, though, that they may not see things the way he sees things. And he may not see the way they see things. And hey, we're going to see we're going to see. Because we know what they need to do. We know what they should do, but it's the matter. Will they do it? We're going to see. I don't know. And he said, number two, if so, how much? Oh, yeah, we already don't answer that question. Lamar, for him, it should start at the Deshaun Watson thing. It should start there. It should. Why not? The timing, the situation, it should start there. He said, number three, and if they do, will they rely on him to become even more of a super? See that? That's the scary part right there. That's the scary part right there. Oh, let me finish, though. He said, if they do sign him to a new contract, will they rely on him to become even more of a Superman because they can't afford top tier talent moving forward? Remember and Juan Bodin's departure after Joe's extension? Keep up the great work and congrats on the success of the channel. Appreciate it. Appreciate that. See, that's that right. That's right there. What I was saying earlier, if the Ravens pay Lamar Jackson, this does not excuse them from still being able to provide talent around him. Now, something to think about. Um, excuse me. I wonder because, again, public perception, it plays a part and a lot of fans already have it in their mind. Hey, Lamar should take a cheaper deal. He should take less money because if he takes the most money that he can get, oh man, and we're not going to be able to provide anything around them. We're not going to be able to pay anybody else. And that's going to be it. We're only going to be able to pay Lamar Jackson. He take all the salary cap. Man, uh-uh. No, no. If there's truly a wheel, then there's always a way to get it done. The cap is capped with so many ways to work around it. I know some owners got more money than others. I get that. But there are ways to do this thing, man. So when it comes to Lamar Jackson getting paid and he should not take a cheaper deal, just a reminder. And the Ravens, I would just hope that they wouldn't put it out there to the public or they wouldn't start, or the Ravens wouldn't say it themselves. But they could have little reporters like Leak Little Stuff here and there. Oh, well, the Ravens paid Lamar Jackson out and now they're not going to be able to pay anybody else. Now they're going to be limited on what they can do. Now them paying Lamar Jackson will change some things, but it doesn't stop everything like so many people are trying to suggest. Sometimes I feel like my face be so shiny in these videos. Next question came from my boy, Nicholas. He says, Super Bowl contenders. And Ravens, I want to start by thanking you for doing this question from Subscriber Series. School to have an actual conversation with a YouTuber that I've been a fan of. I also appreciate how you treat everyone's questions. So respectfully, no matter how much your opinions differ. You're the go for a reason. I'm not the go at all. I'm a donkey. But no, you're saying conversation with a YouTuber. Look, don't make it sound like it's special. But it's not. I'm just a regular person like we all are. And this is just us having conversations about football. That's it. That's it. That's it. So it's a conversation with another person. It's a conversation with another Ravens fan. And that's it. Nothing more, nothing less. But I do appreciate you, man. He said, I think most Ravens fans agree we are one or two moves away from being a definite contender. Well, there's some Ravens fans that say, hey, we are already. We are right now. But anyway, he said, yes, we could contend now with a little luck, but our roster feels incomplete. I should have kept reading before I started running my mouth. So I've cooked up two moves that I think puts us in the conversation for the Super Bowl. Okay, let's see what he's talking about. I was originally in the camp saying, we don't need a wide receiver. Give the young guys a chance. Oh, we leading into my favorite conversation. Let's see what he's talking about. I trust Bateman to be our number one guy in Dove while his Pro Shae all deserve a chance for the number two in slot spot. But if we're not even sure who's gonna be number two, what happens if Bateman gets hurt? I haven't seen enough to trust these guys to be the number one wide receiver and we can't run a three tight end set every play. All right, you mess around and get a Raven the Greg Roman three tight ends. They gonna mess around and find a way to have them three tight ends out on a fit. Maybe even four, but be careful what you say because it just might end up going down. Anyway, he said, I'm gonna assume DK Metcalf is off the table. Okay, I think that's everyone's first pick. Well, not everybody. I know a lot of people with the DK Metcalf, but a lot of people are not. But anyway, with the Baker trade going through, I think Robbie Anderson for a second or third is a solid possibility. Oh yeah, I do too. He gives us more vertical threat and he's more reliable than some other names like Denzel Mims, Scotty Miller, Kendrick Bourne, Nikhil Harry. Where did he get traded to? Was it the Bears, I think? I think it was the Bears, it was somewhere. If we go to free agent round, I think fans are sleeping on Odell Beckham Jr. Yes, he's hurt, but early season is when the Raven shine. Lamar can be on chemistry with the younger guys, then come late season playoffs or offense will gain a whole new dimension. It's been a lot of talk about Odell Beckham Jr. I was just talking to one of my guys the other day about this. Me, I would prefer somebody who can impact right now. Odell Beckham Jr. is, he's a gamble. And I feel like the Ravens are already gambling big time with the Y receives that they have already. He could certainly help. He's talented. When he can play, he can play. But when are you going to get him? When is he going to be on the field? I just, I would rather Ravens has somebody now. I understand Odell Beckham Jr. thing. Me, and I know some people are going to be like, what?  Yeah, I probably am. But me, if the Ravens signed Odell Beckham Jr., I'd be cool with it, but I would still want them to get somebody else right now. But anyway, he said, yes, he's hurt, but early season, oh, I read that already. He said, second move. So that's one move. So wide receiver, that's one move. And he said, Odell Beckham Jr., also mentioned Robbie Anderson. Okay, two solid ones. Second move is edge. On paper, we are a top 10 defense right now. If we get someone across from away until a jabbo is healthy, I think we could be a top five easily. Robert Quinn and the Bears aren't seeing out of eye right now. And if he plays like he did in 21 or 19, our defense would be nasty without having to rush a jabbo back. I think with his age and skipping mandatory mini-camp, we could snag him for mid-round picks. Well, I think this is going to be a dream deferred because they signed Justin Houston back. So I think that they'll be done at edge. Well, yeah. He said, I've also heard Deon Jones from the Falcons mentioned as a cut candidate who could take the mic roll so Quinn can play a wheel but that's wishful thinking. Oh yeah, he has been a topic of a lot of conversation. Deon Jones, and it's just been like a waiting game to see. Now that would be somewhere where, because you still got Josh Bynes. And it's like, but if you could get Deon Jones, that free up Patrick Quinn, let him be more loose, let him be more free, give him, give the Ravens even more flexibility. But if the Ravens could get a significant wide receiver, I'd rather that money be allocated to that. But Deon Jones, he could make Patrick Quinn's job easier. Therefore letting him play better and more freely and more confidently and him playing his natural position. Since his natural position with LSU was not Mike Linebacker, like you mentioned. But anyway, sorry for the super long question, but what do you think of these moves? I think they're relatively realistic. I'm no cap guru. So that may be where my ideas flow. But, love it. He said, I'm no cap guru. So that may be where my ideas flow, but the cap is cap anyways. Any other moves you make as a GM? Oh, you know me, man. You already canceled my number one move. But yeah, those are some solid stuff. Would the Ravens make any of them? Ah, maybe, but probably not. And last question on this episode came from my boy, Jarvo. He said, it's been a while since I did a question. So I'm gonna keep you busy with these, LOL. Which receivers make the roster if you had to choose seven? That's a lot. I think, I don't even think the Ravens keeping those seven. I think for the Ravens, I think even six receivers is pushing it for them. Ooh, seven, right, we'll throw everybody on there. So Bateman do Pro Shae Wallace. And if we go on seven, ooh. I say Shamar Bridges. Maybe Benjamin Victor, cause he got sort of a leg up on him, UDFAs. And one more. Maca Poke. And then how many games do you give Roman to open his vault before he gets fired? Oh man, I think it would take a lot for Ravens to fire Greg Roman. I think in order for Ravens to fire Greg Roman, they, hopefully this doesn't happen. But they would have to really be losing and offense would just really have to stink. Another way could be if they may not be losing, but their offense may not be having all the success in the world and they just, they may be close, but just no cigar. And then the bi-week rolls around. Or that, yeah, that long stretch from, I think between the Bucks and the Saints. Cause I think it's like an 11 day stretch right there, something like that. But I think around then, if things are not right by then, then I think that's when they could make a move because that would give them the most time in season for them to make an adjustment. Then he said, the last question, what are your thoughts on the new Madden trailer and improvements? I watched it, but I ain't dissect, cause I'm like, I play Madden, but I'm not, I'm not one of them people that's like, oh man, well, this is going to be great for the new Madden and da, da, da, da, da, cause I don't really care that much anymore. I just play it for fun. I just play my franchise. Anything new that I notice, oh yeah, this is new, oh cool. Hey, that's different. I gotta get adjusted to it, whatever. But I don't like look at the trailer and just, I just look at the trailer, I'll watch it once and then that'll be it. I ain't gonna watch it over and over again. I just, I don't care that much. I'm gonna get the game. I ain't one of them people, oh man, Madden sucks, I'm not gonna play it this year. It's the same game. They just, they just changing the rosters every year. A lot of people that be saying that same thing, they still buy the game every single year too. But I'm gonna get it, play it, do my franchise, and that's it. So I don't, I don't really know what's new in there. Yes, but I don't really care that much either. Not a real last question. So I thought that previous question was gonna be last, but I feel like doing one more for this episode. Anyway, this next question came from my boy Kevin B. He said, ain't Graven man has it going? I hope all is well. Let's talk Raven's talk, man. Now for those who don't know, Chuck Locke is one of John Harbaugh's guys for real. The only way I see them trading him is if he asks for it. I think he's too valuable to the Raven. So I can see us doing a bit more three safety sets with this new system. So let's drop the talk about Raven's giving up their first round pick to anyone. They get those picks, not give them away for any player. Now, okay, so you jumped to something different. It was all in the same paragraph. So I thought it was all the same thing, but you did a little shift right there. So first, the Chuck Locke talk. It's, I don't know, because if somebody offered a third or higher, I think the Ravens take it right away for Chuck Locke. I think they take it immediately. If somebody offered a fourth or higher, I think a fourth, they talk. I don't know if that would move them enough. I think it would definitely had them talking and definitely had them considering. But I think a third or higher for sure, I think they will take it right away.  Ravens is like, ah, give me that, give me that, give me that. Well anyway, the next part, he said, let's drop the talk about the Ravens giving up their first round pick to anyone. They get those picks, not give away for any player. They don't pay wide receivers, so I don't see them giving up a first round or four one. They'll just wait until someone is cut and give them a try. I say let's try what we have first. With good coaches and shorter routes that can help guys get open, it's up to them to catch the ball. Sorry for the long comments, peace and blessings to all. Oh, trust me, that wasn't long at all. Now, piece by piece, let's drop the talk about Ravens giving up their first round pick to anyone. Yeah, that's something that they don't do. But what has that been getting them? Now, a lot of it, the whole wide receiver thing, a lot of it has to do with scheme. It's certainly, a lot of it has to do with scheme. No, Greg Roman, run game, yeah, pass game, it's like. And even before Greg Roman, even with the Ravens, run game, yeah, pass game, they were never this team that was just this prolific passing team, it's not them, it hasn't been them. So it's more a philosophy thing than it is a Greg Roman thing. But it's like the thing is when you put those two together, you put the philosophy together mixed with Greg Roman's offensive scheme and it's like, boom, not a good look for wide receivers. Now, last year, their passing game did take a step forward, but this year we'll really see if that passing game took a step forward due to injury, only due to injury, excuse me, because we gotta see what it does this year too, hopefully without the injuries, hopefully not. But Ravens, you get what you pay for. You mentioned like, yeah, they like to wait to see guys get cut, you get what you pay for.  Last year, they got Sammy Watkins, one year, $6 million deal, five million guaranteed. If he could ever stay healthy, that would be a good signing. I felt like it was a straight signing, but I kept saying, can't put all your eggs in the Sammy Watkins basket, it can't be him, and that's it. So then they drafted Rashad, baby, and I was like, all right, cool. But then everybody got hurt, messed everything up. Then Ma got hurt, Rashad, baby got healthy, and they didn't really get to play together that much. But you get what you pay for. They signed as Brian, who hadn't played in like three, four years. Willie Snead, he was solid, but he was solid. Seth Roberts signed him to one year. I think it was maybe like a five million dollars. I don't remember how much it was. He was, all right, he was, yeah. He signed Michael Crabtree, who was a good route runner, but known for drops. He had that attitude. He had that dog, boy, he got that dog, he got that heart, man. I like Michael Crabtree, but he did have little drops, he's a little bit. But they signed him to the, really a one-year, seven million dollar deal. It was technically a three-year, 21 million dollar deal, but I think only that first year was guaranteed, so it was always constructed like a one-year deal. They signed John Brown to a one-year, five million dollar deal.  They don't wanna pay for it. And I think part of it is because of their philosophy, because they like, hey, like receivers, we got, we got a hat. I think, I feel like the Ravens would be like, Ravens would be like the only team. If, I don't know if there's, in the NFL, I don't know if there's like a certain, like a minimum amount of wide receivers you got to have on your roster. But I feel like with the Ravens, if they could be like, you know what, we don't want no receivers for wide receivers on our team. I feel like they'll be the one team that would do that.  Just give us tight ends, and that's an offensive line and running back, and we'll do our thing. But no, seriously, I just, with their philosophy, I think that's why they are so cheap at the wide receiver position. They don't wanna pay big money at the wide receiver position because they just don't value the wide receiver position like other teams do. They don't. That's not them. Now, I do always hear that about like what you were saying, they had Ravens, they not gonna do that.  They not gonna do that. I think they should. But yeah, you're right, they don't do that. But who's to say that they can't change that? Who's to say that the way that they do things is 100% right? Who's to say that the way that they do things, it doesn't need any fine tuning at all? Who's to say that the way that they do things is perfect? It's not. It's not. The way that, and nobody's perfect. I know GM is perfect, no organization, team, perfect. I get that. But Ravens got some things and some little thing they could fix here and there that I feel could take them to another level, especially offensively. Defensively, they fine there. They been about that defense. But offensively. And again, same conversation, man. The reason this conversation keeps coming up so much, especially with me, is because, especially offensively, is because of what they have on offense. And what they've had on offense since 2018, who they had on offense since 2018. And what they've done and what really, what they haven't done in a lot of areas, with him, for him, including him. So yeah, they could really step it up there a lot. A whole lot. So, so we'll see, man, we'll see. He said, they don't pay Y receiver. We talked about that. They'll just wait until someone is cut and give them a try. Yeah, that's what they do. I mean, yeah, that's what they do. With good coaches and shorter routes, they can help guys get open. I mean, if a guy can get open, he can get open a shorter route, medium route, intermediate route, deep route, whatever. If a guy can get open, he can get open. Period, whatever route. But, yeah, we'll see, man. We'll see. That's what they brought in, Team Monique Williams 4, so we'll see, we're gonna see. You two team keep it clean. You see my boy, he like automated, automated. Boy, that's my homie, ain't that right engraving? Right engraving. Shout out to engraving.


Top four technical courses for all the product managers. Number one, you don't need to know how to code, but you must know system design, system thinking from MIT. System design means you know the architecture diagram to understand the differences between different systems so that regardless of what kind of technology you want to work on, either AI or crypto or API, you know how to design the entire system. Course number two, software architecture. This helps you to understand end-to-end what does it look like to design any kind of software product so that you're able to communicate with the engineering team. Number three, generic AI 101 courses. You only need one hour, maybe two, to understand the basic of generic AI so you can be up to speed about the latest tech trends. Number four, AWS certification. It's only three hours you're able to get AWS certification for free. It's going to help you to understand how most software engineers can run on the cloud, how to make technical decisions, even if you don't know how to code.


So, it's time to talk about OpenStack on OpenStack. It should really say OpenStack on ALS because that's what we're really here, that's what we're about here today. About me, I work at HP on OpenStack. I don't know what HP does. I work on Nova and Triple O. So, we're here to talk about OpenStack. This is, you've all seen this by now, I hope. And this is the nice little image from the website and they call it a cloud operating system. I'm not sure if it is or not, but let's call that for now. And so, what does OpenStack do? OpenStack is a cloud operating system that gives you APIs to programmatically manage, consume, and use compute network and storage resources. So, you have your application, let's say it's Jenkins or something, you need to consume some resources. You say, I need a compute node, I need some storage, I need some networking. You tell the API that and you get them. Nice and simple. It has some really great impacts. And so many of you hopefully know by now, this is one thing that cloud does that enables velocity. So, now you have a really fast resource allocation, no more. I need a server. I've got to wait two weeks to, you know, get the server into the data center, have it installed, have it networked, DNS, et cetera, agility, speaks for itself, unless we could deploy test or develop test and deploy in the cloud. It's one environment for everything, it makes it easy. It's really easy to spin up resources to get rid of them, to scale things out, and so you want to take some of these properties and actually try to use them to make deploying OpenStack easier. So, OpenStack has been very successful to date.  This is once again taken from the website. We have lots of happy users, but it turns out it's really hard to deploy and actually upgrade. So, I don't know if any of you have tried to actually do that here or actually deploy OpenStack in a non-trivial environment. Turns out it's getting easier, but it's still a huge pain. So, part of that is because OpenStack is actually really, really complex.  We have Cinder, Nova, Neutron. Those are compute storage network. We have Keystone for user management. We have object storage and block storage. Lots of different systems.  And we have databases and we have message queues. All of them you want to have highly available. So, this is actually a very simplified model of what OpenStack in production will look like. Yeah, it's a little crazy, right? Turns out this is actually really hard to deploy for some obvious reasons. It's really big, complex, and hairy looking. I want to be nice if this is easy to deploy. You don't really have to sort out where all the stuff goes and deal with all this by hand, deal with upgrading by hand and all that. So, to do that we need some sort of system that actually allows us to deploy big, complex systems. Turns out OpenStack is designed to do that. So, I want to deploy OpenStack with OpenStack. And this is where you have the inception music. So, this is now officially the OpenStack's official deployment program as of a few months ago. And so, we're actually working on making sure this actually works. I'm going to talk about how we get there. So, this is a quote from the actual description of the project. So, triple O is the use of self-hosted OpenStack infrastructure. That is OpenStack bare metal, noven cinder, heat, disk image builder, and in-image orchestration to chef, puppet, install, maintain, and upgrade itself. So, we're trying to address some major issues here. Three main issues with triple O. One is bugs. We all have bugs. We all hate bugs. We have a few ways of solving that. Already in OpenStack today, we actually have a continuous integration process. We actually gate every patch in OpenStack on making sure we think it works. Our definition of works is never what you guys think means works. And so, we're working on fixing that. And furthermore, we're actually going in addition to continuous integration, continuous deployment. And this solves this split-brain problem. I've had this a lot. I don't know if you guys ever have this. On a personal level, you're working on two things at once. On a company level, you have the developers working on the next generation OpenStack and you have your production guys working on something six months to a year old. And they come to you and ask you a question about a bug.  And you don't know what it does because that was six months ago. And so, we solve that by actually trying to get deploying trunk all the time. So, continuous delivery. And this helps because instead of thinking back, man, what did I do six months ago? It's, oh, I think I did that two days ago. And you go back and it's sort of freshen your memory and you can fix it quicker. We also want to have a common API and code base for the cloud and everything under the cloud. And this is just lost code, lost complexity. We already have one API we're sort of comfortable with. Why not use it again? We also want to try to standardize the installation upgrade process. Everybody heads a little differently. And that means everybody heads a little different bugs. And that means it's really hard to test on a thousand different ways upstream. So, we want to actually have one more or less standard away with a bunch of variations in it that we could actually gate upstream open stack on. Another problem we're trying to deal with is entropy and cruft. I mentioned this in the last talk a little bit, which is you do app get install one day and it's different a week later. So, it's a bunch of different ways of solving this. Our approach is we bake everything in beforehand. So, instead of doing app get install and doing something like Chef or Puppet, after you stamp the image onto the machine, we actually do it before. So, we change the image. We have these golden images that's all the code in them. So, you know that everything you're testing is the same code you can see in production. You don't have to deal with app cache mirrors and gem mirrors and pit mirrors and et cetera. We build everything beforehand, do it once and then deploy it out. And so, we only have all the software will be in the golden images and configuration and state is outside. And hardware failure, this is a standard one. We see standard high availability techniques. So, there's a bunch of different pieces, the puzzle for deploying something like OpenStack or many other systems. Provisioning, software configuration, state and orchestration. Turns out in OpenStack, one of the reasons why we have triple O is because we have these two great pieces, orchestration and provisioning, that already do big parts of what we have today. So, instead of using something else for orchestration, we have this nice tool called heat that does that. In provisioning, we have this thing called NOVA, which gives you provisions for you, compute resources. Instead of using virtual machines, we just use bare metal machines instead. So, the same API on top and underneath instead of using a hypervisor, using bare metal driver. And the last three pieces are the pieces that are a bit more, we had to write ourselves, and they're a bit more independent and you could swap them out for things like Puppet or Chef. Disc image builder, this builds the golden images. And actually, OS, Config Applier and OS Config Refresh, we've actually renamed. We swapped Config and Applier and Config and Refresh for silly reasons. So, now it's OS Apply Config and OS Refresh Config. And those are how we actually manage the configuration of the state on machines. So, provisioning, we use a NOVA API on top of it, NOVA boot, instead of giving you a VM that gives you a bare metal machine. And this is done via a bunch of different ways. The standard way is Pixi and IPMI. This piece of code is actually being currently pulled out of NOVA into Ironic, which OpenStack actually has trademark, so you can't use that anymore. So, Ironic is now a trademark of the OpenStack Foundation, which is pretty funny. So, now we actually, this will plug instead of a virtual driver, I'll actually use Ironic instead in the future. So, you say NOVA boot, it'll talk to Ironic underneath everything. And then it'll talk to Pixi and IPMI or some proprietary third-party API. For software, use golden images. And so this does encapsulate a known good set of software. So, you build your image, you test it out if it works. Awesome, you ship it to production. If not, you try it again and you do it until you get a working image. This excludes all configuration and persistence date. So, all config files, things like database, that's outside of the golden images. And this is sort of the equivalent of packages at the cluster level, at least we think so. Another nice thing to say is it actually moves all the testing up. So, instead of you test everything in your lab, it all works out great. You go to production, something changed. You don't know what it is, it's not working. They have to go and debug everything in production. I've had to do that a few times in past companies, it's never pretty. So, we actually move all this, the problems of things breaking in, dependencies changing and things like that up into the actual testing environment. So, we have a small tool chain that we wrote ourselves for this, but you could use any sort of image-building tool chain for this. And once again, we actually get to deploy things the same way we tested them. Bit for bit, it's going to be the same except for your configuration and persistence date. So, for configuration, you use OSApplyConfig, and this is a little basic tool we have that combines metadata delivered by your cloud, something like Keat or something else potentially, with the templates on your image to produce a working config file. So, things like NovaConfig, that will be in there, Swift, anything like that. All the config files you put into here, OSApplyConfig, and that will stamp out an image. It's a little template, it's nothing too complicated. And once again, we actually wrote our own thing here instead of using a bunch of the options out there, Salt, Puppet, Chef. And the reason is because we don't want to stick ourselves, be dependent on the third party, the reference implementation, and we know many people could be very heated about which one they like, Salt, Chef, Puppet. And so, we wanted to stay out of that battle altogether, but you could use anything you want here. And OSRefreshConfig, it's the other tool in the config, OS StarConfig, sweet. And this is triggered when the metadata changes. So, in addition to actually deploying the cloud, you actually want to be able to upgrade it too. So, that means something's going to change when you're able to reconfigure things and handle that. So, there's a little service that every time something changes, it'll talk to heat, restart services, coordinate data migrations, things like that. If we're doing continuous deployment, we actually need to have a way of doing this often. So, it's a very basic process. Pre-configure, configure, migration, and post-configure states. So, a good example is if you're upgrading NOVA, you'll do something like turn NOVA off, upgrade the code, change the config file, maybe turn NOVA back on. And if there's a database migration, you'll run a database migration in there as well. Orchestration, so we use heat, which is OpenStack's official orchestration tool. And it uses its AWS-compatible, it's cloud formations, and it gives you this concept of stacks to build a whole complex system. So, you say we have all of OpenStack in heat template. So, you say turn on OpenStack, and it'll deploy OpenStack for you. So, this also supports any sort of configuration management system within a machine. So, this works on top. This sends metadata to the machines, and it manages turning machines on and off, but it doesn't actually do anything inside the machine, which is why we have the OS refresh config and OS apply config. So, this is actually a screenshot of what it looks like in Horizon these days. So, this cool little interface in Horizon actually show you the stack being built and being unbuilt. So, we have this crazy concept of underclouds and overclouds. It's OpenStack on OpenStack, so we have lots of crazy layering like this. The basic idea here is we have an undercloud which should be provisioning your overcloud. And your overcloud is what's actually producing the KVM servers that you're selling to people or giving to your tenants. And the undercloud will be bare metal So, undercloud is a fully HA bare metal cloud. So, instead of running Nova KVM, you're running Nova bare metal. It's self-hosted, so that means it's running on itself. And the goal here is to aim for one, two control nodes or so. So, you have 100 nodes, two of them would be a HA cluster for control and everything else would be blank servers that you can stamp images down using the Nova bare metal driver. And all these extra nodes are for the overcloud. The overcloud is a fully HA KVM-based overcloud hosted by the undercloud. It's orchestrated by heat running on the undercloud. And this could actually use the same disk images as the undercloud for most services. So, we have two different clouds and they're mostly the same, so you can actually run the same, you build images once, and they're for the undercloud and overcloud. So, this is what it all looks like when put together, which is a little mind-boggling and confusing to look at. It took me a few minutes to even look at this the first few times. The basic idea is the first problem we have is how do we actually, you know, create a classic bootstrap problem? So, our answer for that is we have a seed cloud running in your VM, something like DevStack, or running a laptop, something like DevStack. You plug this into your data center. You have to register all the machines in somehow. Hopefully, you know what machines in your data center. Maybe have them automatically discover. There's a bunch of different options there. And now you tell your seed cloud that I want to scale out to the undercloud, or I want to scale out. So, now it's a single VM. You want to have it scale out to the undercloud to a single VM into a HA cluster of management nodes. And now you have one VM running, or one machine running the OpenStack core services on your data center, and one copy that running in your laptop. So, you unplug your laptop, and they have a non-HA pair. And now heatnodes is a non-HA pair, and it wants to fix itself. It wants to heal and scale back at. So, you tell heat, okay, go scale out again. So, now heat will take a second node from its pool of undercloud pool to another management node. So, now you have two management nodes running in your undercloud, and now it's all self-hosted. So, that's where that little circle is here. So, this is actually running in itself. So, when it upgrade itself, you tell the undercloud upgrade me, and it'll upgrade itself. And so, there's a bunch of strange logic in there to make that all work with heat. You need to make sure that you can actually do rolling upgrades and things like that. We can't actually bring down the whole cloud using two machines out of, let's say, 100. And you have the other 98 are free. The other 98 are free now for your overcloud. And you can have more than one overcloud. And this is running Nova KVM or Xaner, whatever you choose. And this is actually what the customers will be seeing. So, one of the problems, actually, today with the undercloud is that we want to keep this as a very restricted cloud. And the reason is because it turns out things like Pixi and IPMI are not too secure yet.  Biosis could be your flash, things like that. So, the idea here is to keep the undercloud as a private thing for the deployer. And so, the goal here is now we have, we get rid of the seed cloud and now we have undercloud running. And it looks something like this. We have more than one overcloud on top and we have our undercloud. And we're continuously deploying the undercloud and the overcloud. They're both HA and continuously deploying the same code to them. So, they're always running something close to trunk. They're always up to date. They're always in HA. So, this is the basic installation process I mentioned before. Create a bootstrap node. You plug it into the data center network. You enroll all your machines. You tell heat to deploy your HA OpenStack templates. That's a nice heat template that we have. Heat drives a nova API to scale out. So, once again, we're talking to the same API that we can be using on top and below the nova API. It tells it to scale out the cloud nova boot. Spends up another bare metal machine. Switch off the bootstrap node. Tell heat to recover. So, we're fully working undercloud and we can deploy the overcloud. So, managing your deployment. When events occur that change the state, heat will trigger causing the system to respond rapidly. So, you lose a machine. You know, we're not in HA anymore. We discover that. Now we need to fix it. Or something happens. We want to upgrade the system to rolling upgrades. We need to update all the machines. Heat will manage that. And once again, heat also solves some of these problems. Or any other orchestration tool allows us rolling upgrades, make it really easy. And also, we could actually roll back as well. We just deployed the old image we had. Instead of using the something that worked, we tried to deploy on a few machines. Everything went horribly wrong. We roll back to the previous known good image and we're back to everywhere before and we can debug what happens. We also, this whole process will prevent entropy by managing the cloud in cloud ways which is using images everywhere. And we'll try to store up. The only things we'll have to keep around between is the neat that we need. And any configuration which will be in persistent volumes. So the idea there is we don't have it today but we'll have a... So Nova has a bare metal driver. Cinder will have a persistent volume driver. So it'll actually manage something like an LVM volume on the machine. So you can actually upgrade your machine and leave your LVM volume managed by Cinder around between upgrades. So this brings up a whole bunch of interesting possible applications now that we have this whole concept of clouds and crazy things like that. Well, one thing is we have more clouds everywhere and everybody likes clouds here, right? We get this strange multi-cloud tendency. We have clouds and clouds. We can have different users, different things like that. We can integrate this into the CI, CD, infrastructure, continuous integration, continuous deployment. We can actually deploy part of... We can have a take the under cloud and partition off a small part of it for a separate test over clouds. You can have your production over cloud, or testing over cloud. You can have a bunch of different over clouds. You can have two over clouds. You want to make a private cloud for somebody for a public cloud provider. You can spin up another private over cloud on top and it'll be completely isolated from every other over cloud on the system. But you have the same to actually note a node pool underneath that you can actually pull from. So you can very easily elastically scale up one cloud, bring down another cloud. All of a sudden bringing up and down cloud and what's left to do? Turns out it works today and there's a lot left to do. So we do this today. We have a... We have a testing harness that's running all the time on trunk. Trying to make sure this always works. And it actually works quite well. We're not running this in production that I know of, but I don't know anything about how HP works. There's a bunch of big pieces missing here and we're working on them and we have solutions for all of them. We just haven't done them yet. There's no persistent storage. So Cinder doesn't have a notion of this bare metal management. We actually have some concepts for having Neutron actually work in OpenSTAT in triple O today. So that's another big component is the networking.  We don't have a full networking story sorted out yet for deploying the under cloud networking and the over cloud networking. We have the over cloud working and most of the under cloud working. Rolling upgrades aren't supported in heat yet or this concept of canary upgrade. So we have a big system, 1,000 machines, 10,000 machines. You can't just upgrade everything at once. You won't work. You actually have to upgrade things slowly, try a few machines. You do a canary deployment. You'll try a few machines, roll them up, see if that works, if it doesn't work, bring it back down. If that does work, then you go and deploy everything slowly. We don't have the full story sorted out for that yet, but we're working on that. We don't have the ability yet to actually upgrade Nova Compute without taking VMs down. It's a really big one. You have your over cloud. You want to upgrade the image on it.  It's the cloud. You can't take it down every five minutes and you want to do that. So our solution to that is actually not actually upgrade the VM itself. Don't take it down and upgrade it. We actually want to r-sync the route partition as read only and r-sync the changes to the image in and then just re-kick services. So the idea is we'll have the VM will be running long-term and you have a new image, a new version of... You fix critical bug 5, 4, 3, 2. You need to push this out of your work because your users are yelling at you. You just fixed it. It's a big bug. So you can actually deploy this out. You r-sync the new code over. So now you have a new image out there and you're not deploying from packages on production. You have...  Now you have the new Nova Compute running with the bug fix in it. Routementary HA support. We're working on this today, but we need everything to be super HA, work well, scale out, etc., and we're working on that. And the general problem of the one big thing here is that this is sort of like a double-down kind of play for OpenStack, which is using it to install itself means you have double the fun if it all works and double the amount of failure. So you have a bug in your undercloud and your overcloud now. So this is going to help us actually flush out more bugs. We need to be able to handle network failures and more. We're going to see that on multiple layers now. Hardware failures. We're going to see on multiple layers too. And so now we're going to have... We have to make sure they have less bugs in the underlying system. And I know this is very fast and there's a lot here, so I hope you guys have questions. Yes, the answer, the short answer that is HEAT. So HEAT has this idea of the dependencies in the system. You can see here this is a database and servers and a load balancer I think in the front. And it has this notion of the dependencies in the system. So you can actually use HEAT to manage that process. So HEAT will actually help you manage these... You tell HEAT the interactions between the services and it'll take them down accordingly. This goes back to the whole idea that we have... We already wrote this nice orchestration tool and we're still writing it. Why not use it for deploying the cloud and for the users of the cloud? There's a core CI over there so you can ask him. The answer is very responsive. We have...Triple O has members of the core. We have some HEAT cores on the project. We have...  And so we have a lot of good pull on the system. And when we have a bug, and if it's a critical bug, we know how to fix it. So very responsive. Yes, I don't know anything about that though. So you have to ask somebody else about that. The answer is this is all open source. None of this is the team in HP that's working on this. We're all working upstream on this. So everything we do is public. We have a free node. All the code is upstream on GitHub. So GitHub open stack. Slash triple O incubator. It's all there today. We're all trying to make this public as possible. And we think there'll be multiple... Red Hat's also very involved. We expect HP and Red Hat will both commercialize this at some point. We also have invested interests, which is HP has a public cloud. We deploy massive clouds. We want things to work really well. We want to do continuous deployment. And so we believe in open source. We're doing it for everybody. Different part. HP turns out it's really, really, really big. 300 something thousands. I think I'm in the printer department though. I'm not sure. I know there's Converge Cloud, Public Cloud, and a few others. No, I work under Monte Taylor. And I don't know who you worked for. So I may. I mean, yeah. Once we have the template deployed for the over cloud, it's really hard to plan under cloud. So we have it. It's sort of like, you know, we need images somewhere. We might as well put them in glance. Keeping the same API is sort of... That's right. What? That's correct. You put everything in. Yeah, all the gold images go into glance. So we actually have a... The problem with this is you need a lot of machines, right? So we actually have a... a Nova Bear Metal virtualization driver. So the idea is you... That's right. So you could do on your laptop. A big laptop, but a laptop. So the idea is you spin up some instances outside and you have, you know, SH to the power driver and it's a whole big convoluted mess. But it works. Yes. I mean, you can't put into production on a laptop obviously, but yeah, we need bigger laptops actually. There is a talk about that. If you go to the triple O incubator, you can actually see there is a test, I believe it is. It is like a 40-step test or a 40-step instruction that will walk you through the whole thing, deploy the undercloud on your laptop, deploy an overcloud on your... undercloud on your laptop, and everything in between. Yeah. So please try it out. We're very... We like bugs, so file bugs and we'll fix them for you. It gets slow, but... You have a bunch of different layers of virtualization inside of itself and it's a little iffy at times, so... Yeah, so it's a bit slow, but it does work. Right. So the answer is in production, the answer is no. Running 50 VMs in your laptop, no matter how many layers nested, it's going to be slow or 10 or whatever it is. So in production, there's no actual errors in production. So we have the bare metal cloud. The idea is there that you... when you deploy an instance on the bare metal cloud, it's actually stamping an image down on bare metal and it's a regular old machine just like it was managed by another system. Then on top of that, you have KVM running on native bare metal and everything's fast. Yeah, so there's... Docker containers is one option here for the over cloud. And the idea would be... There's some caveats there. One is you have different kernels. You can't really do that in Docker. If you have a big system, that'll fix that. If you want to run really high-performance things, let's say you want to run something like Trove, let's say, or Database Service or something else. You can actually instead of swap out the KVM over cloud and use a Docker over cloud, let's say. I don't know if you've actually tried Docker today. No, I think we've tried LXC on top, right? So for the under cloud, you don't use containers. We use bare metal. And that's sort of the difference there. Yeah, so it's been great. We've had great feedback from the community on it. We have a bunch of other people are joining in from other companies. Red Hat's very deeply involved with a whole bunch of others. And the goal is to one day... Yeah, we agree. Oh, exactly. Yeah. The deployment's the easy part, so to speak. It's the upgrades that are hard. It's everything else after a deployment. So we're trying to make this easy. We want to make this standardized as much as possible. We don't actually... We don't prefer any OS. We support Ubuntu. We support REL or maybe Fedora. I'm not sure which one it is. We'll support anything else anybody else wants us to support. So we're trying to be fairly agnostic as long as they want to support whatever. And you put some manpower behind it. We'll happily do that. Yes, there's a bunch of different ways we need to fix that problem. This is a big part of it. The big step is actually being able to have an upstream tool that we can actually use to test upgradeability. And so this is the big one. There's a bunch of things we could do before that. But we're really hoping that we're all embarrassed that we can't upgrade an open stack that well. So this is where it gets complicated. And so every patch, ideally, should be a new... Or every day, let's say, will be a new release. We ideally want to go every patch to trunk will be a new release as much as possible. But we also want to support because open stack does have releases at least for now. And we're trying to change that a little bit. We do want to actually support Grizzly and Havana too. So upstream testing hopefully will actually support both. I actually tried that out recently and it almost worked. I was able to spin up a VM on a Grizzly Compute node in the Havana cloud, which was surprising. But something like this could help not only just actually testing the backwards compatibility, but testing the upgrade process as well. We hope to standardize sort of the upgrade process. There's some questions like, what do you upgrade first? And so hopefully we'll be able to standardize those in something like this. And then a downstream consumer of open stack could say, this is how they're testing the upstream. We don't like that. We'll tell them to do it this way maybe. And maybe they'll do that. So hopefully a known path that works. Which is not the case today. I mean networking issues always bring some crashing down. Right. So that's ultimately the goal and that's why we're trying to make sure that we don't actually have to restart VMs when you want to upgrade software. And so the hope is that we actually, yes bugs like those will exist. One that benefits having the same, we're going to have the same code path on top and below. We'll hopefully hit the bugs faster and we'll have one less code path to debug hopefully. But we're going to hit those hopefully and hopefully we'll sort this out quickly. Kernels are hard ones. There are ways of upgrading kernels, but we're not trying that I don't think. Hopefully you're not going to upgrade your kernel every couple of days. In which case, one option, this is the standard answer obviously, is you could migrate VMs and things like that. But if we wanted to, or somebody wanted to, whatever they call it, destroying kernels and upgrading them in place. And that's an option and we, I think, stayed away from that for obvious reasons for now. But, you know, case by case that is possible. Very. Yeah. So depending on how you want to set things up, you could have one machine. I think right now we have the two core machines in the undercloud running everything. So they're all running, and that's going to change in the future There's a bunch of different ways you could do that. You could have as many images as you want. We bake the images beforehand, and once you bake them, they're sort of set, they're not going to change. And so hopefully that's not going to be a problem to have too many images. What we hope to actually use, saying we're using KVM or using bare metal, is a fairly small change in the config. And so hopefully we actually have the same Nova compute, you know, use the same images for the top and the bottom as much as possible. Yeah, so separating things out, we want to do that. We haven't actually really sat down and decided how we want to do that yet. But there's many ways we could do it, and the idea is to do some of this as much as possible in heat and then existing tools whenever possible. So we have a bunch of people on the heat team who are working on triple-one. This is a great, you know, deploying something big and complex like this is a great, you know, if open-sat heat could do this, any other questions? That's a really good question. I think the answer is no. The problem is you're going to have a whole different layer underneath for deploying everything and managing everything, which will be open-stack. And so you'll have to do some sort of migration from there to here. I guess the real answer is if you want to use this in the future, try to work upstream with us, tell us what you want and we'll try to see what we can do. We're welcome. Do you want more and more people on this? It's an open-source project. We'll have more feedback saying, this is a terrible idea, do it that way. That'd be great. Yeah, so I don't think we've actually approached that one yet. Right, yeah. We have to actually migrate all the data to underneath and the databases and the other questions. Thinking about it. I don't know the overlap between heat and Bosch. Yeah, that's it. So it's recovery for us and it's also I change something, make it look like the new thing that I want it to look like. I change the image, make it do that. Nothing we're trying to address here is new. There's nothing here that it should be new to anybody. I think everybody's hit the packaging problem. Yeah, so it should fit in pretty well.   That isn't to say that if you don't have OpenStack anywhere, it's sort of silly to use it for this. But if you already have OpenStack somewhere else in your system and you want to use bare metal, you could actually build a separate image that's not OpenStack that uses whatever you want on there and deploy that. Right, it's when you're using OpenStack somewhere else in the system, we don't want to have two systems that do almost the same things with two different APIs on top. We want to try to use the same code base for whatever possible. I mean, I think it would be, but I think there's other questions you could ask if you're not using OpenStack. All of a sudden, I think there's more options that are really good things to evaluate. I'm not saying that don't do it if you're not using OpenStack, but when you're using OpenStack, you want to use the same code base. You already have something that does the same thing. Instead of using provisioning VMs and provisions bare metal instead of volumes in a VM somewhere or in whatever, it's LVM module, you know, volumes on a bare metal machine. So it's sort of this nice analogy with treating bare metal like cloud resources. Which makes it great if you want to, you know, go from bare metal environment to a virtualized environment for your system. Nova boot will work the same way. So, use some nice properties there. Go in once. Thank you.


Hi everyone, Tasha here from Stardust Gold Crochet. Today we're going to do a little tutorial for C2C in companion to my corner-to-corner calculator for how big your blanket size will be. So what this is, a corner-to-corner is used as a graph and it works from one corner to another corner and it goes diagonally instead of working in rows but you can obviously work a graph in rows too. But the corner-to-corner blanket works this way which is really interesting. You can create some really great patterns with it. So for the tutorial I want to just give you an idea about what C2C is, how to make some color changes and also how to do some decreasing and some increasing and what that means with corner-to-corner because it is it can be kind of confusing. So and also another question that a lot of people ask including myself is how big will my blanket be? So that's a universal question because everybody has a different tension and everybody is using a different hook size, a different yarn size. So the calculator I made will help you determine how big your blanket will be according to how many squares you have in your graph as well as a swatch that you make and I'll go into that. The link will be down below for the other video on how to use the calculator. It's really simple, not complicated at all so don't be scared. So let's get started on this little swatch pattern and I'll show you guys how to do some some C2C. Okay so what we're going to do first is I'm going to work we're going to work three squares using red and to start go ahead and grab your yarn. I'm using 24 7 cotton, a 4 millimeter hook and so the first thing you do like with most crochet is we're going to go ahead and make a slip knot. I'm going to zoom just a little bit and so for corner to corner you can start out using six chains or five chains. The difference between those two will the six chains you'll have a little bit bigger square and the holes will be slightly bigger. I'm going to show you what I mean by that. The holes between each of the squares right here those tend to be really large when you use the six method when you chain six and then chain three between each of the squares. I like to chain five and then chain two between each of the squares because it leaves a slightly smaller hole you can see it's pretty can't really see holes that much but. So for this tutorial I'm going to chain five one two three four five and then with CTC we're going to work three double crochets into the very first three chains so you're going to start by counting down one two three and work into the third chain from the hook and do a double crochet and then go into the next chain and do a double crochet then the third chain do a double crochet and there's your first square so we've made our first square now we're going to work our second square and a good indication of where you're started is where your tail is so that's going to be your square because your tail comes off and goes to the right so with CTC you kind of work a little backwards and forwards but so here we're going to do the next row technically that would be row one that we just worked which is right here and we worked it's going to lay this this way so now we're going to extend it and then work row two so the way you extend it is you're going to go ahead and chain five again and then work in the third chain from the hook again and do three double crochets in each chain until you reach the base part so there we have our extension and we've actually worked this square so we've we have this square and this square worked right now and it looks a little crazy and kind of confusing but what you do here is you want to bring up if they were side by side like this on your first square you want to flip it bring it up side by side like that and then work into the space of the last double crochet that you did sorry about that okay and then do a slip stitch in here we're going to make our next square which is going to be this one so we're not going to do an extension we're just going to chain two and then work three double crochets into that space two and three and there we've worked our first little section right there so for the next for the next row we're going to go ahead and change colors and we're going to work it in orange so how to change colors is fairly simple and it's the same that same method you use when you join using row-to-row crochet and what we're going to do is we're going to go ahead and pull out the very top part of our last stitch reinsert your hook and of course you can you know before you even complete this stitch on the next one you can use a new color then add your new yarn to your hook and pull through to complete your your stitch so there we have our new color very easy and so with the pattern you can see we're going to extend off here so we're going to chain five over here and then work our way back up this way so we're going to chain five three four five and here we're going to work back down the chain into the third chain from the hook double crochets three of them in one in each chain the joins are always they always get a little bit loose just no big deal just tug on them if they get loose and so here we've made our first square of the new color and we want to do the same things we did before is join them so how we do that is you kind of you have to flip it and put it side by side and then go into that top double crochet space and do a slip stitch and that joins them and then chain two three three more double crochets sometimes it's easy to fold this little piece back to get it out of the way when you're working and so here we're going to do our join into the next double crochet space there slip stitch chain two three more double crochets and our row will be complete and I recommend marking the front of what would be the front of your project with a stitch marker or loop through a little piece of yarn or something so you know which direction you're facing it really helps when you're working a big graph so here we have our comparison and we've got our one two and three rows it's one two three so now let's go ahead and we'll make changing up the colors again to yellow just so you can get used to color changes so we'll do the next row in yellow I'm gonna do the same thing and just kind of pull out the last part of that stitch and then go ahead and add the yellow and just kind of pull them tight C2C you have a lot of tails in C2C but if you do color changes but you can also do just a one color blanket or project but the fun of C2C is you get to work any kind of graph that you can so go ahead since we're going to do an extension now or what they would be calling an increase or what I call an increase because we're increasing the length of the blanket and that or the scarf or hat whatever you want to make it into C2C but so when you're doing increases what they mean is you're increasing the size both horizontally and you're increasing it vertically as well so when you do the increases you chain five on one end and then when you work your way back up then you'll be working back down this way and then you would be making your increase here five so let's do this and chain five working to the third chain we're gonna flip it to bring that part up to this part and go ahead slip stitch so I'll cut to the end of this row and when we come back we're going to do a color change in the middle of a row so you can see what that's like and also teach you how to carry colors so when you carry the color behind the stitches right so I've reached the end of my yellow row and so we're actually up here right now and what we're gonna do is I'm gonna work one more yellow there and then we're gonna do two orange or three orange and then we're gonna work another yellow right here so that will show you how to do color changes in the middle of a row and also show you how to carry the color behind there and you'll see that because we're working back down this row back down this way we're gonna do our increase right here so remember you'll keep track of that just by marking the front of your your work so you know where your tail is always going to be coming off the bottom right hand side so one two three four five and then we're gonna work back into the chain just like we did before move the little graph for a moment okay so here is where we're going to make our color change and we want to flip our work again and bring it up next to it but we want this next square that's going to be right here to be orange so I'm gonna grab the orange yarn and we're gonna do a color join and we do the color joins when you make the slip stitch into the space of the double crochet so instead you can just let the yellow drop add the new color over your hook pull it through and complete your slip stitch with the new color like that let your tail drop and then just kind of grab them so they're tight and here's where you're gonna chain two and then complete so well before we do the completion of the the thing the yellow color you can carry underneath and in the stitches of the next yarn too so you can actually pick it back up over here so we're gonna do that so let's take the yellow and just like we carry colors when we're doing rows you're gonna work it into the stitches as you do your double crochets like that and then we do our join and when we do our slip stitch join into the next we're just going to let the yellow yarn kind of lay alongside it's always tempting to just do a single crochet isn't it so chain two continue doing your three double crochets hiding that yellow yarn inside carry it up one more time some people don't like to carry yarn in C2C some people do it's completely your preference it depends on the colors really sometimes if you have a light color with the black behind it you might not want to carry that black because it really shows up but with this color here you can hardly see the yellow even transitioning up through those stitches through the back so it's just your preference and trial and error really trial and error error error so here we're gonna switch back to yellow because our last square is yellow so that's what we're gonna do is do the join and we've carried our yarn in back you can pull it loosen it stretch it however you want you might want to stretch it just a little bit because you want your blanket to be flexible and if that's too tight it's gonna pull on it and mess up the tension of the blanket but okay so here we're going to drop our yellow I mean our orange just pick up the yellow I did that off-screen so we're gonna drop the orange insert pick up the yellow and pull through and then just chain two and work your last square as normal there we go you can just pull that tight and so there we've completed our little squares like that pretty awesome huh and so the next one we'll do is we'll work back up using the yellow and since we're at a point right now where we're gonna start working decreases that's what we're gonna do because our blanket stopped right here right our little swatch so we have one two three four five one two three four five so our next one is gonna be working up this is actually not as complicated as it sounds so if you look at it like it kind of looks that way and it was to me at first I was like oh no how do I do that so what you're gonna do is this square is right there so we're gonna fill in this square so what would you do to get from point A to point B the most simple solution to get from here to here and what that is is a slip stitch so go ahead and turn and then slip stitch into the top three of the double crochets and then once into the double crochet space there we have it so now we're up to this point where we can just create our new square right there and we do that by going ahead and chaining two and then working your regular old double crochets into the edge and then continue on working into each one of the spaces there I'm gonna pause it and we'll come back at the end of the row now we've worked up to this point I'm gonna flip it so you can see because we're actually this is the front and we've done this square right here and we're working our way back up this way see because C2C is directional so we just we did this one and now this one's working back up this way and so here we've only have one two three four squares one two three four squares we've done it but we're not connected right there so let's go back and we're going to make our connection with a slip stitch just like before like that and so ourselves well how do we get from here to here because our next our next square is going to be right here so we're like oh how do I get there how do I get there well slip stitch so flip it and work back down the other way slip stitching into the top three tops of the three double crochets and then once into the double crochet space and there we are we're back at the beginning so we can make our next square which is right there okay so now that we've done that I'm gonna rip it back you can rip it back with me too if you want and we're gonna we're gonna rip it back to the point of the corners right here right there and there and I'm gonna show you how to do it as a rectangle so when you have two different sides that are asymmetrical so say the one two three four five six squares and this one's one two three four five so a lot of the graph side I work are 80 squares by 90 squares so this will help you work a pattern that's rectangular so let's rip it back till we come to our square corners okay so now we have our one two three four five that's one two three four five and we have five one two three four five that way so what we're gonna do because this graph has six horizontally and five vertically we're gonna leave five alone and we're gonna extend on numbers on the horizontal row which is six so we're gonna do an extension here by chaining five and working our normal double crochets back into that chain then we're gonna join like we normally do chain two and work your double crochets join I'll cut this and we can come back okay so now we've actually worked our six down here we've got one two three four five six so you see we've made that extension there or increase there and then we're gonna we already worked back up this way and now we have the flat end there so similar to what we did before with making the square we're just going to join into the top of this double crochet there slip stitch it turn it and slip stitch back down those three to get us back to our beginning point where we can make our next square without doing an increase right there so that puts us right back there so we've got to this way and it's longer this way and stays the same height and gets longer and then you just work your normal rows down and if it extends out further then you do more extensions and if not you bring it back in like we did before so golly I really hope that this helps you guys it took me a minute to get C2C especially the increasing and the decreasing because the terminology I didn't quite understand I was like but you're not increasing but I didn't see it the way that they that it was supposed to be seen which is you're increasing the width or you're increasing the height and all the flipping and stuff got confusing but it just takes practice trust me you can get it if I can get it you can get it I know you can all right so please subscribe if you have any questions about this video or anything I'm happy to answer them any tips and tricks you have on C2C leave them down below because I love to learn new things and I hope you do too and that's it so I hope you guys have a great day happy crocheting bye oh and the C2C calendar or cacca keep saying calendar calculator that's in my blog in the descriptions down below so if you want to head on over there and give it a shot please share it with your friends thanks a lot