Hey everyone, welcome back to Nintendo Prime. We have some really cool stuff to talk about today. Three big stories, potential Nintendo Direct News. It's gonna be a lot of fun, but before we get into that, I wanna went out to brand new giveaway we have going on now through the month of February. It's actually our February giveaway, but because of some snafus that happened with a potential partner who I'm not going to name, I've decided to forego them and just say screw it, we're doing it ourselves. So right now we are giving away PlayStation 5, Xbox Series X or Switch OLED. It'll basically be a console of choice by the winner. All you have to do is go down to the gleam.io link down in the description or the pinned comment. We also have a couple other giveaways that are wrapping up this week, so I'm just gonna mention them quickly. We're also giving away three copies of Pokemon Legends Arceus this week, and yes, we are giving away $100 cash to one new subscriber in the month of January. So yeah, we kinda gotta jumpstart on the February one because of a partner snafu, but you know what, screw it, let's have a good time and get into today's news. So the first thing I wanna tell about is this weird thing because we still don't have Grand Theft Auto 5 on Switch, right? We got the Trilogy Remaster, which was sort of a hot mess, but has been cleaned up a little bit since, but we still don't have Grand Theft Auto 5 that was on the Xbox 360. Yeah, two generations ago, this game came out. We got Skyrim from back then on Switch. Why can't we get Grand Theft Auto 5? Well, some of people speculate it's because it's about the online multiplayer. Maybe Switch for some reason can't handle the online multiplayer, and they did kill the online multiplayer on the Xbox 360 version anyway, so that could actually be the reason. But what's weird is a fan went out there and modified a Game Boy to play Grand Theft Auto 5. And when I say modified, they didn't do anything. It's just the original OG Game Boy playing Grand Theft Auto 5, not a joke. Now, to be clear, obviously the hardware inside a Game Boy could not play Grand Theft Auto 5. What they ended up doing is creating a customized game cartridge that could stream the game from a PC to the Game Boy and actually have all the buttons and everything work and obviously have it be in all its pixelated glory on that screen. So yeah, it's pretty cool. By the way, we've had Grand Theft Auto 5 ran on Switch in this way, although it required the Switch to actually be hacked. In this case, the Game Boy itself isn't hacked. It's a Game Boy cartridge. In case of Switch, you would hack the Switch itself and then put Android on and run streaming apps from there. But yeah, I just think it's kind of cool that somebody did this and it always reminds me why the hell isn't this game on Switch. I know what the real reasons probably are, but I don't care. It's from two generations ago. Telling me you couldn't get that online multiplayer or work on Switch, I don't know. Maybe you can't. Next up, this is a weird story that has been making rounds in the last day. It has to do with Mario Kart 8. So Mario Kart 8 Deluxe is going down today. The online's going down the day for five hours. The official update from Nintendo says, on January 25th from 4.30 p.m. to 9 p.m. Pacific time, Mario Kart 8 Deluxe will undergo expected and standard maintenance. Online play features will not be available during this time. We apologize for any inconveniences may cause. And the reason that this is getting a lot of pub is one, this online maintenance is happening during prime gameplay hours. That's number one. It's really, really long maintenance. Most online maintenance is only an hour and Mario Kart 8 Deluxe has only had this happen twice. Last time they had any sort of maintenance was back in May of 2021 and that fixed a couple bugs in the game. And the last time before that was all the way back in 2018. So they don't do this often for this game. Now this made me wonder, what's the big deal with it this time? And why is it five hours? And why is it during prime time? Is this because they're preparing to announce Mario Kart 9? No, I do think however, the Nintendo is finally going into Mario Kart 8 Deluxe's online and maybe making it run on the new servers. I don't think they're going to announce this. I don't think they're gonna make a big deal out of it. But I do think they want to move Mario Kart 8 Deluxe onto their new server infrastructure as they start to transition away from the old servers. So that's what I really think is happening. And the real reason they need five hours during prime time because they need a lot more employees on hand to handle a transition from old servers to new servers. This wouldn't be something you would just do in the middle of the night, randomly on a Tuesday. You're gonna need a lot of employees there because there's probably gonna be some issues. So yeah, that's what I think is happening. And I do think that's a big deal. However, Mario Kart 8 Deluxe online already works really, really well. So I don't really think that us as fans are gonna notice any difference. But I do think that this could be in preparation of testing things for a new Mario Kart. But yeah, I honestly think that this is much to do about nothing publicly, but internally, you never know, there could be something there. Now this last story is what I guess most of the video is about, it's in the title, Nintendo Direct, right? We all expect a Nintendo Direct at some point early in the year. Okay, we didn't get it in January. Well, I mean, I guess we still get it this week. Nintendo doesn't usually give us more than 24 hours notice so they would announce it tomorrow, but I don't think it's in January. We have Legends Arceus coming out this week, so it'd be really weird if they did a Direct the same week. Obviously, we have February, right now there's no major Switch games. March, we got two big games coming out, so maybe they do a Direct in March. Here's the thing, I've always been on the train because of Legends Arceus, we're not getting a Nintendo Direct till February. Well, now we have some potential evidence that we are going to have some sort of event announcing games next month. So Nintendo Dream Magazine, which is not an official Nintendo magazine, but does get early copies of games from Nintendo for the purpose of the magazine coverage, put out a tease for their February 21st issue. In that February 21st issue, in the little tease they put advertised in it in their most recent magazine, they mentioned things like, yeah, we're going to be talking about Kirby and the Forgotten Lamb, which makes a lot of sense because it comes out really quickly after that magazine comes out. However, they mentioned, we also get to talk about a brand new announced game that has everyone in a tizzy. Now look, I don't really know what this game is. They obviously can't talk about it yet because it hasn't been announced, but it's interesting when you think about just announced because it means, hey, obviously there's a game being announced next month that we don't know about. I can't wait to see what that is. It's obviously, I presume, related to a Nintendo Direct. Lots of rumors on when the Direct's gonna come. Is it the 17th? Is it the 24th? Is it the 10th?  I have no idea. You can make your predictions right now. I think 17th, but it could literally be any other day. It could be a Tuesday, it could be a Monday. Nintendo's done weird things with Direct's in the past. So I'm not gonna be able to tell you what day it's coming, but I will say that one, we should already expect it and two, now we have a magazine that got access to a game that hasn't been announced yet teasing us. So here's hoping that that's related to the Direct. As for what could be at this Direct, obviously advertising for Kirby and project triangle strategy. When I do think they're gonna set up their lineup pretty much through June, if not through July, they usually don't like to announce games in June to release in July. So I do think they're gonna have basically from now through July, maybe even August, taken care of in this Direct, and then whatever Direct in the summer, whether it's at E3 or just a Direct on its own, will end up covering the rest of the year and then we'll get our September one that re-advertises the holidays and then teases 2023. Really weird to be talking about 2023 right now. We're still in the first month of 2022, but yeah, that's what I think is going to happen. So as for what this game could be, who knows, man. Nintendo has so many games already scheduled for this year. Maybe it's Metroid Prime 4. Maybe it's a new Mario game, Mario... It could be anything. So I want you guys to actually go down in the comments and assuming this new game being announced is actually made by Nintendo, what game do you think it is? Make a prediction down below and I guess we'll see by the time that the Nintendo Dream Magazine comes out. If nothing else, if you were correct. Of course, we'll probably know before then because it will be announced because that magazine is not announced in the game. Anyways, thank you guys so much for tuning in. You could obviously tell I'm feeling under the weather.  So yeah, but we're to a point now where I'm actually able to talk so I can talk and record videos again. So we're back to making content and doing the best I can while I'm feeling up and well enough to do it. So thank you guys as always for your support. This has been a lot of fun and be sure to tune in tonight to our Pokemon Brilliant Diamond Stream. It should be the last time we streamed that game ever. We should be beating the final gym and hopefully the Elite Four tonight. And that's it. Our next livestream for games will probably be on Friday when we livestream Pokemon Legends Arceus for launch. And then I have no idea what we're playing next Tuesday. Are we playing more Legends Arceus?  Are we gonna play some other new game? Maybe an indie game? I have no idea. I guess tune in to find out. Catch you guys in the next video.


Hi, I'm Sergeant Warnacky with DPD TV. Today we're here to tell you about a new scam that's occurring in the Denver Metro area involving you and the electric company. Beware, here's the information. Meet Saeed Benjalung. Moroccan food is excellent. For 17 years, Benjalung has owned the Palace Casablanca restaurant in southeast Denver. All kinds of people, they love it. From low-key people, regular people like us. Sinators, movie stars, even President Bush was here for dinner. One Friday, Benjalung got an unwelcome visitor, a man posing as an Excel energy worker. A person came through the back door, knocked, and I went open. It was like from Excel energy. He gave Benjalung an ultimatum.  I need you to go wild green and get me a card, calling card, and put money there and give me the card. Benjalung not wanting any problems on a busy Friday night and a restaurant full of people handed over the $500 card. When I called Excel energy, I explained the situation. I said, no, nobody come. We never receive any payment. We've been scammed. To get Excel energy's advice on how to avoid this scam, we went to talk with them. It is true that from time to time, we will have individuals who go out to collect on bills. And that's after we've made other attempts to contact the customer about an outstanding debt. They have a right to check for Excel energy ID. They have a right to say, I don't know if I trust you completely, can I call back Excel energy and ask them if this is true. And in all cases, our bill collectors, or those who might be so contracting for us, have to wait until you make that contact. And you have a right to determine in most cases how you want to pay. So if you have a situation where they want to run you over to Walgreens or take out some type of online payment, that's definitely a telltale sign. If you suspect this scam is happening to you, call the police right away. If you're not sure about your Excel account balance, here are the numbers you can call to check.


السلام عليكم و رحمة الله و بركاتكم و بركاتكم أحكام S.O.S و سنشاهدوا إسلام السماعي في إمكان الدعية و تجعلوا مثلنا الساوية التي يع Verfاضيها و إشارة أنا شخص مصنعي ادعين مئيش شخالي معا السلام عليكم و رحمة الله أتواحكم لداخل وجودها ماشاء الشخص هل بكم تراهول أيضاً؟ هل بكم أقوم بلحق اصلاة صلاة؟ على زندها شيد اللهم سأتنا قصر صلاة و نظروا بها المجابات نحن نتحدث عن how far we want to travel نحن نتحدث عن كيف تريد أن نتحدث عن مدينة المدينة نحن نتحدث عن مدينة مدينة المدينة ونحن نتحدث عن لا تغيير مدينة المدينة ما هو next criteria of Qasr Salah أعوذ بالله السميع عن عليم من الشيطان الرجيم بسم الله الرحمن الرحيم الحمد لله رب العالمين وصل الله على محمد وعاله الطيبين وطاهرين الله صلى الله عليه وسلم The fifth criteria is that the journey in which the one is taking is not for a prophet and haram purpose In other words, if the one intends to go for a haram journey For example, the one plans to go and steal from a specific let's say he lives in Birmingham or Manchester or Scotland and he wants to come and steal in London a jewel shop for example and leave that day In this case, the Salah of this person will be in full He cannot pray Qasr Salah because the intention of the travel was for haram travel Likewise, the said mentions the example of a wife traveling without the permission of her husband Again, that traveling is a sin that she is not taking the permission from her husband Also, the son and the daughter they travel despite the objection of their parents Again, that is a travel a disobedience travel In this case, they have to pray in full There is no Qasr Although they are going to go just for 2-3 days And the rule of Musafir is for them, they have the right if they were just normal travelers they should have prayed in Qasr واجب But now because the whole travel the intention is about committing a sin or disobedience In this case, the Salah will turn to be in full So that's one of the conditions that we have to make sure to avoid of course Because in including that is the Ma'asiya and Haram act We shouldn't displease our parents We shouldn't as a wife displease the husband And of course, the main thing is to please Allah And not to disobey him by Na'udubillah going for a journey to steal for example or gambling and so forth There is like Someone is being punished in a way that if you want to travel for these purposes then obviously I'm not going to give you the mercy of having Qasr Salah How does one actually recognise his hometown or his house, his home city I mean, a lot of people travel sometimes with Ulama they have to travel for a very very long time sometimes they move between one house to another house for let's say for example, someone from Iran has come to London and he's going to live here for a year But when he travels around in the UK and so forth is his Salah Qasr or not because he's not technically leaving his home he left his home in Iran What happened in that situation? The one who makes the intention and chooses to stay in a place and considered to be as his hometown In this case even if he was not born in that country let's say he was born in Iraq or Iran or Pakistan or India and now he wants to move to the UK or Canada or America When he decides to stay in that country and live there then that country becomes his hometown and he can start praying full fast and so forth So it's all up to the person's intention and choice that if I choose this place to be my hometown you start your life there and you pray in full and you fast the month from Iran in this situation Shaykhana Is it possible to have more than one hometown? I know a lot of people go back and forth from let's say house of students they're from London they go to Qom they live in Qom they study in Qom and they come back and go back and forth Is it possible to have two hometowns? Yes, if you consider two places let's say your own hometown where you were born and the place in which you go for study or work let's say you're six months in this city or in this country and six months in that country or city in this case you have now two hometowns in this case you should pray in full in both places whether you've stayed there for a day or for a month you're passing through that city to go somewhere else because it is your hometown you must pray in full you cannot pray Qasr unless yes if you decided to abandon that second hometown let's say you're in Hausa now you live that city of Hausa and you go back to your first hometown where you were born for example in this case that place becomes no longer your hometown your second hometown so whenever you come there to stay for two, three days you pray Qasr and you have to break it fast because it's no longer your hometown yes and masha'Allah شيخنا what about those who travel as purpose of work pilots captains of ships and you know they do like regular traveling let's say they have the same three flights a week they do for them is a mandatory to do Qasr Salah those who travel often for business and work they known to be as كفير سفر often travelers they have to because they travel often let's say every week you know passing this 44 km of distance then they have to pray in full they cannot pray Qasr because that's part of their life now they work and they travel it's part of their life so they cannot pray Qasr at all they have to pray in full if they go for the work and business they pray in full if they go for holiday pleasure and pleasure then they have to break their Salah and pray Qasr in this situation so it depends I see so it's all down to the near really are you going for you know business or are you going for pleasure and if it's business then obviously you pray in full if it's pleasure then you pray Qasr شكرا you discuss one of the criteria is that the length of stay has to be within 10 days what if someone wants to stay longer than 10 days does he get to pray Qasr Salah for 10 days and then go into full if you make the intention to stay 10 days in a place which is not your hometown then with the intention of staying 10 days you have to start praying in full anything below 10 days you have to make the Salah Qasr and pray to shorten the Salah in this case so it depends really on the intention I mean even if you stayed there for 2 weeks for 3 weeks and you did not make the intention of staying at least 10 days you still have to have to pray the 3 weeks in Qasr and break it fast as well unless you make the intention so that's the core that I make the intention to stay in a place for 10 days at least onwards without this intention I cannot pray in full and I cannot fast I have to break the fast and shorten the Salah and pray Qasr so the main thing is to make sure that if you want to pray full and fast you must make the intention of staying 10 days what if one makes the intention for 10 days and then changes his intention for example I intended to go to Paris for 2 weeks 14 days and something emergency happened and I have to come back I've been in Paris for 2 days now praying full Salah and now I know that oh I'm going back home in 4 days there's an emergency or something I need to get back home quicker so what happens in that case do I need to redo my Salah and what about the remaining days because you made the intention of staying 10 days and you prayed let's say in full the 6 days passed now the next 4 days in which you don't want to stay in that place and you want to break it and travel in this case you stay you remain praying in full until you leave that city so you do whatever you did before by praying in full until you leave the next day or the day after so you don't switch to Qasr you cannot switch to Qasr because you already made the intention of praying in full so you continue the Salah as they were and then you leave the place and continue your journey I understand Shaykhna Shaykhna what happens when I have the Nia to stay for let's say 9 days and then I decide to extend my stay for another 9 days so I've stayed now for a total of 18 days in the city do I have to start praying full prayers now or do I still pray Qasr because the intention wasn't there to stay for more than 9 days well if somebody is is uncertain about his stay and it happens a lot that am I going to stay in this place for 2 weeks 3 weeks less than a week I don't know in this case if that continued and that individual prayed the Qasr because he didn't make the intention of staying 10 days at least because that's the intention it must be made if you want to pray in full and fast you must make the intention otherwise you keep praying Qasr and breaking your fast however the maximum limit for the one to be able to perform the Qasr Salah is 30 days so you extend the days a week after and then another 12 days or 15 days till the 30th day when the 31st day is there you start to pray in full because the maximum you can pray Qasr in 30 days you cannot extend it anymore so on the 31st day of your stay in that place in that particular city or country you stop praying Qasr now you turn and switch to praying in full so that's the rule about it what about those who travel between multiple cities multiple distances over 30 days so I'm continuously travelling I'm on tour as they say I want to do 4 days here 4 days there 5 days here 10 days there 6 days here and so forth let's keep it to 9 days so 9 days here 9 days there 9 days there and it's been 30 days I'm going to be touring for 40-50 days does that same rule apply that for 30 days I pray Qasr and then I do my full Salah the maximum 30 days condition that if you stayed in one place so let's say you stayed in Najaf only for the whole 30 days and you didn't make the intention of staying there for the Iqam to stay there at least 10 days and you prayed all your time Qasr the 31st day as I mentioned you start praying full that is only for the the one who stays in one place okay not the multiple places that you mentioned but if you decide to stay 9 days in Najaf 7 days in Karbala 8 days in Mashhad I don't know 5 days in Qom in those holy cities and that will make up about 45-50 days let's say of your journey in this case you stay praying Qasr the Hakam over 30 days is only for those who want to stay in one place 30 days otherwise you keep praying Qasr by moving from one place to another so 9 days here Qasr 7 days there even if it's up to let's say 50 days that's fine as long as there are multiple cities you keep praying Qasr but one place you stay up to 30 days Qasr 31st day you start praying in full masha'Allah Shaykh thank you very much for today's discussion and thank you for all the viewers for joining us wherever you are in the world Insha'Allah join us on the next episode the Hakam as I mentioned we'll be discussing further on Qadar prayer Insha'Allah hoping you're not traveling too far and if you are traveling may Allah SWT protect you on your travels Insha'Allah see us on the next episode سلام عليكم رحمة الله وبركاته سلام عليكم


Naaman's bias, also known as prevalence incidence bias, is a type of bias in research. Naaman's bias occurs when there is a higher enrollment of prevalent cases with longer disease duration over the incident new cases. For example, in a study on a chronic disease conducted over a short period, participants with a longer disease duration are more likely to be included, leading to a higher observed prevalence. Naaman's bias can be minimized by selecting cases and controls from the same time frame using a longitudinal study design and analyzing and reporting the study results separately for prevalent and incident cases.


What's the word y'all? I'm trying to one take this one, ladies and gentlemen. We here to talk about the Cleveland Cavaliers cashing in their money in the bank briefcase and snagging Donovan Mitchell out of nowhere. I'm sitting here watching Eurobasket enjoying, well, France has been disappointed through the first half or so. I guess watch it, didn't it true? To beat up on France and out of nowhere, Donovan Mitchell gets traded.  What was the package? What did they give up? Did they give up Mobley? Obviously not, y'all. Come on, man. One of the most untouchable young players in all the basketball. The trade ended up being Colin Sexton, Larry Markin and O.J. Abadji, three first round picks and two swaps. But I'm excited for Cleveland basketball. I went to change the shirt, so don't make fun of this. This is a small, I don't wear it often. And I don't really like it because they 2015 rolled to the NBA Finals and down here, my Chicago Bulls are in the grave. So don't really wear it often. It's anti-Bulls propaganda at this point. But the trade happened. It felt inevitable that Donovan Mitchell is gonna get traded to New York. But I kind of, I don't wanna make this about New York, obviously. But they've been in these conversations for the last month or so. The jazz said they wanted to get it done before training camp. And then a couple days ago, Leon Rolls decided he didn't want Danny Ains dictate in the future of his organization. So he extended this guy, RJ Barrett. But the experts even said, even when RJ Barrett's extension, there's still a world where Donovan Mitchell ends up on New York. So I was like, okay, he's gonna end up in New York, right? No, these boys came out of nowhere. There are teams that were linked to him. Like the Cavs had been linked to him. But nobody really thought that they were gonna really put it together. The Wasis was had been linked to him. Nobody thought the Wasis was gonna really put it together. The Cavs did it. And if I'm the Cavs, I do this 100% of the time. Now you can have some conversations around Donovan Mitchell being 6'1 and Darius Garland being 6'1. This is one of the smallest backcourts in all the basketball. How is it gonna work out? So we can have some conversations about what it'll look like on the court over the next couple of weeks. This right just happened 10 minutes ago. Let me go ahead and get my initial reactions out of this. I love this for the Cleveland Cavaliers. This is why. Like in that period of time between when I'm filming this video and when the actual pieces came out, I saw some people say overpay, overpay, overpay. This is why I don't believe this is an overpay and this can come back and bite me in two years or whatever. The reason I don't see this as an overpay is if we break down every single piece of this trade, there is nothing that you should be extremely attached to if you're the Cleveland Cavaliers as far as we believe that once we get to the point we're ready to compete for a championship, these pieces have to be on the team. Colin Sexton, we don't wanna give him no money anyway. You know what I'm saying? We don't wanna give him no money anyway. He was a big trade piece for somebody. We thought we was gonna have to dump him to the Dallas Mavericks for basically Reggie Bullock in a second.  He got an extension by the way. So shout out to Colin Sexton. Four years, 72 million dollars, easy. The next piece, Laurie Marketing. Laurie Marketing is over there playing in Euro basket right now. It just got the notification that he got traded. So poor fellow. He's going to Utah though. I don't know. Maybe he blossoms, you know? Laurie Marketing was there for a season and he was good in that season. The Cavaliers surprised the world with their three center lineup or three seven footer lineup. Now they're kind of going the opposite direction. They get in a lot smaller. But there was nothing about what he performed last season to say, oh, once we really into it, he has to be safe. Absolutely not. Ote Abadzi played four games in the Summer League and I was there for a couple of them. He looked really good. You know what I'm saying? He was one of the older players in the draft if not the oldest player getting drafted in the first round. People saw him as a guy that could take some ice to crow opportunities because he defends well and he shoots the ball well and ice to crow only does one of those two things. But again, he's only been in the organization for two months. There's no attachment to him whatsoever. If you told me that Ote Abadzi was going to be the piece that we don't want to give in for Donovan Mitchell Trey, I will call you crazy. And then we talk about the first round picks and this is why I don't care about the first round picks in this circumstances for the Cleveland Cavaliers. We draft the Dearest Garland who's already an all-star and only 21 years old if I'm not mistaken. I would not be surprised if Bro made multiple all NBA teams throughout the course of his career.  He looked amazing in this rookie season and I'm guessing he'll only get better and better and better. We got here that we have this young core that like we basically should have made the playoffs this year if everybody just stay healthier. Not even everybody. If 80% of our roster, 70% of our roster stay healthy, we would have been in the playoffs. So I'm looking at those first round picks like man, with Donovan, we ain't guaranteed luck to make the playoffs. We talk about 23rd overall pick, 29th overall pick. I'm not it, they probably won't be that good but these are picks that aren't gonna be super valuable to us, right? And then I know it's basically five years worth of pick equity but we got Evan Mobley for seven years, guaranteed. We just extended Dearest Garland. We got him for four more years guaranteed. Jared Allen, four more years guaranteed. How many years of Donovan Mitchell's contract? Whatever it is, guaranteed. Those picks don't mean nothing to me, right? So I'm looking at their depth chart. So it's probably gonna look somewhere along the lines of Dearest Garland, Donovan Mitchell, Karis Levert, Evan Mobley, Jared Allen. That is a really good, really good start at five.  You will eventually have Ricky Rubio. I don't know when that is. Kevin Love is still on the roster. We brought in Robin Lopez, Jenny Osmond is there, Dean Wade is there. The benches may be a lot to be desired but I think that they can finagle this and they mess with the minutes enough where Darryl Garland and Donovan Mitchell are switching gears. One of them is going with the second unit, one of them staying with the first unit. You know what I'm saying? They can figure it out. JB Beckerstaff is a very smart coach. I love it for them. You know, I'm excited for Cleveland Cavaliers basketball because as long as Cleveland's been a thing, at least as me being an NBA fan which started in 2002, 2003, if LeBron wasn't on the roster, this team was heavily irrelevant. And I understand it was only a small window when LeBron went to Miami and then recent but they were irrelevant. And when a trade like this, that is no longer the case. I would argue last year, they weren't irrelevant. You know what I'm saying? It just took the injuries that pulled them out of the hunt. The team has one of the best young cores in all the basketball now. Not one of, maybe number one. I might be pushing the gun a little bit but Darryl Garland, All-Star, Jared Allen, All-Star, Donovan Mitchell, All-Star, Evan Mobley, Superstar, that's one of the best young cores in all the basketball. And as they continue to get reps and reps a part of each other and on the same team, it's only gonna look better, I believe. Again, we can talk about the only course stuff. How does the defense look for Donovan Mitchell and Darryl Garland? Cause I think we can all agree, Donovan Mitchell was absolutely dreadful defensively over the last couple of seasons but specifically this year it was just some of the worst defense I've ever seen. You know what I'm saying? It was really that bad. But they have the pieces in play that can hold them up. Now of course, you need your perimeter defenders for sure. And I'm sure Ike Kerr was gonna get a ton of minutes this year and they're gonna ask Harris Leverge to lock in defensively a little bit more. But whatever Mobley and Jared Allen download the defense will probably still be, not probably, they will still be competent. Can we somehow convince Donovan Mitchell to turn back the clock just a little bit to when he was in college because when he was in college he was a plus defender. And now he don't have to worry about controlling the entire load offensively. Like, you know what I'm saying? When they were in Utah, they brought in Mike Connelly like, hey, we gonna ease the pain for Donovan Mitchell to give him a real point guard at Mike Connelly. But Mike Connelly was cool. He even got an all-star appearance. But like, there's a difference between current Darius Garland and the Mike Connelly that we got over the last couple years. So maybe since we're not asking Donovan Mitchell to be him 100% of the time, he can give us a little bit on the defensive side of the ball because we know it's there. He is undersized, obviously. There's only so much you can do when you're undersized like Donovan Mitchell is. But we just need you not to just let your man walk to the basket. One of the main reasons why this team has been eliminating the playoffs over the last couple of seasons, we're talking about the Utah Jazz with Donovan Mitchell is because the defense had been lackluster, terrible at the perimeter. And now we can ask you, we don't need you to average 40 in a playoffs series no more. You did that in Utah, congratulations. I'm exaggerating, but congratulations. We don't need that here. Lock in a little bit more defensively. If we could get 10% more effort from Donovan Mitchell, we feel very good about the way this team looks defensively, right? The only thing that hurts them a little bit is that if they want to get better in the near future, hypothetically, at a trade deadline, they don't really have a lot of stuff to potentially throw in. Five years worth of pick equity is a lot. Again, like I'm saying, I would do that as well. But there's no other piece there, unless you're saying, listen, there's a team out there that's selling that might be interested in the 21-year-old Isakura in a couple months. Boom, we got a couple of pieces that can help. I don't really know. If I'm in Utah Jazz, what the hell of an offseason for me? You know what I'm saying? As a team that has buckled down as a rebuilding team, trading, Rudy Gobert for basically five first round picks and basically getting five first round picks for Donovan Mitchell as well, pretty good. We got Oteobaji, we got Colin Sexton.  We have a couple of players there that might be interesting enough for Utah fans to buy tickets. Colin Sexton, I don't know what he gonna look like after injuring everything, bucket. Bro's abs in the dub, bucket. And I'm looking at my notifications because I feel like there's more to be said. I'm looking at Shams and Wojus Twitter right now. Okay, they have been tweeting. The Utah Jazz, here we go. Cleveland is sending three unprotected first round picks. So that's 2025, 2027 and 2029, and then swaps in 2026 and 2028. The Jazz acquired 13 unprotected or lightly protected picks through 2029, which is great because if you are the Utah Jazz, you're not getting people to sign to you. So the way you become an contender again or become a team that's a playoff guarantee like they have been in the last, I don't know, five seasons ago, seasons or so, is you have to draft well. They trade it for where you go beard on draft night. They trade it for Donald Mitchell on draft night. These are the things you need to do.  So to trade two all-star players and get back 13 picks is pretty good. Unprotected slags, lightly protected picks is amazing. And similarly, this is what Wojus says. Similarly to what the Minnesota Timbills did with Walker Kessler, same thing with the Cleveland Cavaliers. So that's basically another lottery pick or another first round pick because Ocea Bajane played a single second of NBA basketball just yet. And even Wojus saying, this is the lineup that Wojus is talking about. A lineup including two all-stars, the Darius Garland, Jared Allen, and the future all-star Evan Mobley. And Donald Mitchell just quoted Darius Garland's tweet and puts some emojis. I think they're ready. I think it's time the NBA has been shook it up again. And now we gotta start thinking about what tier of team does this put the Cleveland Cavaliers? Does this make them, are they a contender this season? I think a lot of that would have to do on what type of jump Evan Mobley takes because it's in them. I think we all can agree. I don't know, man. I'm sitting there thinking about it, trying to rock my brain around like, okay, what tier of teams to put them in the East? Are they better than Milwaukee Bucks? Would they be better than the Miami Heat? These are the Philadelphia 76ers. These are like the top teams in the Eastern Conference. Can't forget about the Boston Celtics. How many of those teams do Cleveland Cavaliers just jump? Maybe it's none of them right now. Maybe it's none of them in this exact moment, but you have to realize 21-year-old Garland about to be 26-year-old Donald Mitchell, 20-year-old Evan Mobley. This is not a trade thinking that, oh, we about to go win this ring right now, even though that will be cool.  But this is not a trade thinking that this is our last go round. We gonna be solid because they extended pretty much all of the guys over there. And again, Evan Mobley sold his rookie deal. I think they leaped over like the Bulls. I think this trade helped them leaped over a team like the Raptors. The Atlanta Hawks made their own deal. I'm probably more secure with the Cleveland Cavaliers. And I am the Atlanta Hawks at this moment. Again, those are two teams that ain't played a single minute of basketball with their current teams. Maybe this doesn't put them in the upper echelon this season, but it helps them become part of that in a year. And two, that boy Cavalier stuck through it. Think about that. Two years ago, Kevin Love was pissed off at his teammates and the one teammate that he was specifically pissed off on, ooh, ooh, that's a bad sentence. He was pissed off with, is gone. He ain't got to worry about Collin Sexton taking up all the shots no more. And now he could be a savvy vet to some of the one of the best young courts in all the basketball. I'm excited for Cleveland Cavaliers basketball. I'm sure there's other things about this trade that I wanna talk about. But if this is the only piece of content we got, I might be back in a couple of days to give y'all a take number two on my takes of this stuff, man. Donovan Mitchell 45 and 10 in that backcourt. That's kinda nice.


This study examined the creation of political will for pro-equity policies in Australia. It found that the strength of path dependency, electoral concerns, political philosophy, the strength of economic and biomedical framings, whether elite interests were threatened, and the success or otherwise of civil society lobbying all played a role in creating political will for pro-equity policies. In order to create political will for pro-equity policies, it is important to determine how path dependency that exacerbates health inequities can be broken, work with sympathetic political forces committed to fairness, frame policy options in a way that makes them more likely to be adopted, outline factors to consider in challenging the interests of elites, and consider the extent to which civil society will work in favor of equitable policies. This article was authored by Fran Baum, Belinda Townsend, Matthew Fisher, and others.


All right, welcome. Hi everyone. Thanks for sticking around late. My name is Greg Bantz. I'm with Intel IT. I'm in the engineering group within the hosting portfolio. And my responsibility is automation and enterprise integration. And I've got with me Shridhar. Hi, I'm Shridhar Mahankali. I'm also part of Intel IT Engineering. And within that, I focus mostly on the cloud infrastructure architecture. And I'm grown up in the networking side of the house. So there's a lot of networking back down. But right now, look at the infrastructure architecture. All right, standard legal disclaimer and on to the agenda. So tonight we're going to talk to you about Intel's IT cloud transformation and journey. Why we selected OpenStack for our control plane strategy. Our control plane status and plans, automation framework, workforce transformation and call to action. We'll have summary and wrap up at the end since we're the last presentation. We'll probably stick around and talk among ourselves a little bit longer if folks desire. Is my mic overdriven? Okay. So our IT cloud transformation started back in the 2009 timeframe when we made the shift to virtualization. So we brought in a virtualization platform and it started to transform our hosting business from one of 90 plus days to land and application, very siloed in terms of capacity, extremely manual in terms of how you interacted with IT as a customer. And then variability in terms of reliability. In 2010, we turned on our first implementation of our private cloud at the end of that year, right? So we drove through a PDV process to pick up workloads, running on physical platforms, move them to virtualize and got from a 10-day native virtualization kind of throughput down to less than an hour for folks through self-service to come through and request their virtual resources. In 2014, we're driving toward a hybrid cloud, converged cloud strategy. As our enterprise sits, 75% plus of our enterprise is virtualized. We offer on-demand compute network and storage. And we've got full self-service, service across fulfillment with four nines availability. In the last two years, we've actually done quite a lot in terms of cloud enablement. So it hasn't all been an IAS virtualization story. We also have some SaaS success stories. So some limited applications starting to come into IT and onto our customers in a SaaS model, right? And these are hugely disruptive, but in a great way, right? It transforms the face of IT. Also, in the platform as a service space, we've turned on Cloud Foundry as our past offering last year. And we're driving our environment such that our end users, our developers can conceive of an idea and have it deployed and running in production in less than a day. And then in the IAS space, we have taken what was our proprietary and internally developed automation control framework and are shifting toward OpenStack for a control plan. And that's the premise of this discussion here today.  So Cloud 1.0 for us was all about velocity reduced instance, sustained operations, getting to less than an hour for VMs, really minimize our incidents in down times, and just run IT, right? But now in 2014, it's a very different landscape. We are doing idea to production in less than a day, zero downtime, our customers should never experience an outage. And we're doing this in the face of flat budget and down head count, right? The point of this foil is really just to illustrate the current environment. So we're still pushing across. But on the left-hand side, you can see, you know, yes, we've got this proprietary automation that does fulfill self-service for some of our environments, but other environments are still stranded and quite siloed and highly manual. So with our OpenStack control plane, we will be able to extend similar functionality across our entire environment, transform the way that we do our network architecture security architecture and really pass on all of this goodness to our end users. When we went through the process of selecting OpenStack and revalidating our control plane strategy with our CIO, we looked at it in terms of what Intel calls QVAC, quality, velocity, efficiency, capability, right, as our four main vectors. So in a velocity vector standpoint, what OpenStack gives us is a very forward-leaning means to service development delivery and operation. It is also natively geared toward agile methodologies, DevOps, continuous integration, continuous delivery, continuous deployment, right? These are things that are exactly where we're trying to take IT because they align with what our end-users and customers are doing. So instead of feeling as though CICD and agile are things that our vendors are doing or things that our customers are doing and are being imposed at IT, we're trying to drive it from the infrastructure of capability-wise OpenStack is really the perfect automation framework. It's defined by its APIs. This allows us to not only stitch it into our environment in whatever way we have to, but it gives us an extremely rapid way of delivering line of business requirements. And then, again, from an efficiency and quality standpoint, kind of back to the DevOps tool chain, right? So we leverage the same tool chain used by the OpenStack community used by our end-users and customers to deliver IT infrastructure. So what this represents to our customers is really an up-leveling of capability. They are able to do things across the environment regardless of what hypervisor they're sitting on once we've fully rolled out this control plane strategy. So it's broken into phases. Phase one is put the control plane over our existing infrastructure, giving the customer start, stop, delete, snapshotting capabilities, self-service volume, create and attach, resizing functionality. These are all things today that would require, in the legacy environment, a manual ticket. I need more BCPs. I need more RAM. That takes a couple of days to percolate through the system. Phase two that comes on a little bit later in the year is importing all of that metadata that's sitting in our existing cloud environment into OpenStack so that customers who have VMs that were built by hand on that virtualization platform or built by our previous generation of automation get it all natively through Horizon. So we're driving towards Horizon as the front end for all of our operations. Turn it over to Shridhar. Hello. So what I'll do is over the next few slides dive more into detail in terms of what our infrastructure architecture looks like. Mostly I focus on the infrastructure as a service aspects of it but I can touch on some other platform as a service capabilities that we're going after as well. If you look at our virtual hosting environment, where it was about around 2011, so our journey started in 2009 but towards the end of 2012, essentially we had around 75% of our office and enterprise environment virtualized. Right now we are running about close to 17,000 VMs on top of this infrastructure and where we started, where we were in 2011, essentially if you were to categorize our environment you can categorize into basically three primary vectors. There's an internal facing environment and a significant portion is non-onclaved and then there is a regional portion that is onclaved and then there is an internet facing element for that. And as you go through that what you'll see is there is an increasing amount of segmentation and security as you go from the left to the right. So I'll start to walk through some of the details from the network app. So in terms of you look at our internal environment, the non-onclaved piece of the environment, you have a physical network, you are typically leveraging network services like load balancer which is more commonly used network service in that environment and then what you have is a large shared networks that all the application tenants share. Primarily because it is not as much of a need for oncleaving in this space so you use shared networks to make it easier from that perspective. We do use from a compute perspective we are using a proprietary hypervisor and we run the proprietary virtual switch on top of it and the only network service that we are virtualizing there is the switching capability.  Basically oncleave all it means is that it is a segmented portion of the infrastructure that is at the core level is separated by a firewall so that there is more security to basically for the applications that are being hosted there. So typically Intel has these four different classifications of data. So there is public data, there's Intel confidential, there is restricted secret and secret. So as you go towards dealing with a higher level of confidentiality you have to apply more and more security controls. So that's what you're seeing as you go down this scale. And even within the oncleave there are actually the additional segmentation that we have. I'm not showing it here for simplicity purposes. So there is an element that is designed to host Intel confidential and lower data and then anything that is restricted secret it has even higher level of security controls that we apply and that is actually physically segmented today. So that's one of the things that you're seeing right here is the differentiation in terms of as you go to is you're seeing more and more granular network segmentation as you go into that space. Because you have to segment one application from the other with the theory being that if one application gets compromised to prevent it, that compromise to extend to the other environments you want to lock it down into a container. And in the non-oncleave environment indicated that there is some custom automation that we have written that allows you to provision VMs in a self-service manner. But what we were doing there is primarily the provisioning aspect of it but once it is provisioned there is less control that folks have in a self-service manner on top of those VMs. And then as you go to the oncleave space because of a lot of the segmentation and having to make a decision in terms of which network do I land a VM on there is a lot we essentially were doing manual provisioning there relying on a cloud administrator or one of our hosting administrators to may have provision VMs in that space. So this is one of the things that we are trying to address and have a consistent interface as we go along our journey. That's where OpenStack comes into play. So what I'll show you is different ways and different flavors of what single control plane means to us. One is from the perspective of having a consistent interface across our environments where you saw previously somewhere behind a custom portal, somewhere behind manual provisioning. And so there was differences in terms of the capabilities across those environments. So what OpenStack is giving us which we've been evolving our OpenStack based cloud environment over the last two and a half to three years. And here's where you see we are using the open APIs to expose the underlying infrastructure in a way that not only users can use from a GUI perspective but developers can actually use those APIs to run higher level structures, automation structures on top of that to basically deploy groups of VMs or do network cell service, do storage cell service on top of that. So here what you're seeing is again we're differentiating a non-enclave and then an enclave environment. But one of the things that we're doing is we're collapsing what you saw as a non-enclave environment into the same compute pool. And you're able to offer the same level of capability across that. So what we are moving towards is just an internal facing and an external facing, internal facing environment. So again, a few things to highlight here as you move onto the physical network. On the enclave side we are changing our security architecture which I'll touch on in the next couple of slides. In terms of key transitions that we are seeing in this space is we have been using open source technologies. So you see KVM as a hypervisor using open source storage in this environment. Essentially we use CEP in that space. There is an image repository that is exposed by a glance. So all these capabilities that is allowing us to do things in a more automated manner which we were doing more manually before. And OpenStack is the control plane that sits on top of all of it. So where we are headed to in 2014 is we want to extend this OpenStack control plane not only across these new environments that we've been working and advancing over the last couple of years but to have it across all of our virtualization environment which is across all of the 17,000 VMs that we have by the end of the year. So what that means is we are transitioning from where our OpenStack-based environment is purely using KVM as a hypervisor to a hybrid hypervisor environment. So essentially use the same control plane but be able to provision across multiple hypervisors. So this goes along with our strategy where for all of our infrastructure components in general we look to dual source, the servers, the network as well as the hypervisors in this case as well as the storage elements. So it fits in that type of model where you can have a consistent API but you are actually able to change infrastructure solutions in the back end while the customer's experience hasn't changed. That's really the key. So again we are using the same API as we talked about and as I indicated we are moving in a direction where we are able to support multiple hypervisors. We are able to support multiple storage solutions so both scale up and scale out storage from that perspective. And another thing that you see is the use of the trusted compute pools which is allowing us to basically collapse those internal enclaves and non-onclave elements. So on the same common resource pool where we were segmenting the compute resource pools previously we were not getting the best use of the resources whereas by combining those and using trusted compute pools you are actually able to land your secure workloads on secure systems or trusted systems and that's what allows us to use a common resource pool there. Actually one more thing I want to highlight is we are actually also using Heat and Murano as high level APIs that allow us to provision collections of systems where we can create a policy in terms of if you want to deploy a multi-tier application with web server application and database and in addition it needs to have a certain type of security policy implemented all that you can define in terms of in a heat template and be able to deploy it that way. So that's another way where we are leveraging OpenAPS. So the other thing that we have done is as we have evolved we are changing the security model in terms of how we had implemented it before OpenStack our journey with OpenStack and how we are going forward. What we mean by that is where previously our parameter was primarily our access control was primarily being implemented on a hardware-based firewalls and these are monolithic firewalls that we were implementing the access control on. We are moving to more a layered parameter or distributed security model where the controls are being implemented on the hardware firewalls more towards the edge of the data center. Then you have what we are calling as a tenant and zone parameter. So essentially you define security zones and then you have tenants within that. So each tenant at the tenant edge we are applying controls on the hypervisor and then within the intra zone using security groups to create segmentation within the tenant. What that allows us to do is especially when you look at internet-facing environments we used to have separate physically segmented pools of compute for say a web server layer, a database layer and an app layer. All those we are able to collapse and actually are able to run it on top of the same same resource. So this kind of gives you a view, a conceptual design of what that looks like. So what we are separating out is there is a shared infrastructure and hosting services layer which provides services like say LDAP capabilities, identity, patch management and things of that nature. DNS being another example is a common services that we will have in a hosting environment that we provide in a shared manner. And then you have the individual tenants and by virtue of creating an SDN layer on top of our environment we are able to create richer model, richer network models where on self-service each tenant can get their own private network space and create their application within that allows us to basically segment them from the other applications. Previously we had to do this manually and that used to cause deploying an application when the customer engages to actually get them live. It could take several weeks by the time we provisioned the network, provisioned the VMs as well as the security associated with that. So all that is now cut down where they can implement this in less than an hour or less than a day if they have all their pieces together. So basically everything is done in a self-service manner from this perspective. So another element in which we are looking at a single control plane is by using an orchestration layer, by using OpenStack to not only provision to our private cloud environments but also to a public cloud environment. We've done implemented hybrid clouds against some of the public cloud providers out there but one of the key changes in strategy that we are going after at this point is to interact more with cloud providers that expose an OpenStack API and the benefit there is that we don't have to write an additional abstraction layer or leverage another abstraction, another solution for creating that abstraction between a public and a private cloud. So that basically allows us to optimize and leverage the automation that we already have but be able to provision both to public and private. So our first stage is to implement OpenStack across all of our private cloud environments and then as we progress towards the latter half of this year and early next year this is where we're going to essentially expand that to public clouds as well. What we are doing right now is doing the proof of concepts with the couple of vendors to essentially experiment and refine our strategy from a hybrid cloud. And with that I'll hand over to Greg to walk through our automation framework. So for us just in general terms cloud itself is an inflection point for how we do hosting. And OpenStack is the perfect time for us to be really doubling down on driving some cultural workforce and business transformations across the board. And the tendency is to kind of attach to fancy buzzwords, CICD, Agile, training on tools, these all tend to cause people some target fixation. And really for us to be successful in a broader cloud sense and in an OpenStack sense we need to acknowledge and act upon some additional dimensions. Intel IT is an established IT shop. We have pretty mature processes for the way we used to do things. And running a hybrid cloud strategy mandates that we transform or become irrelevant. So team structure and composition, just the way that we've historically put teams together in IT. You have your hypervisor expert, you've got a storage expert, a network expert, your windows and your Linux guys, and throw them together and kind of expect to have a high performing team. And that's worked in the past, but in the cloud future, running cloud at scale, we really need to drive toward these pluggable resources. We call them T-shaped resources where they're able to go very deep on some technology, but they're also very broad and quite pluggable. We can use them around the infrastructure as needed. Our software engineering processes, Intel IT has historically been a waterfall shop. Driving toward the agile end of the spectrum is hard. I hear all the time, oh agile doesn't work, it's not going to work for us, but it has to. And it does work when done right, it's just painful. It's painful to get there and you have to have some faith that you're going to get there, you're going to reap the benefits. Workforce transformation. We've got a pretty mature workforce in terms of skills. They're able to do their jobs very well, but in this cloud model where we're changing the way we build teams and we're changing the how of delivery of cloud infrastructure and cloud applications, it forces us to transform the skills of our workforce. So bring them ahead, get away from process and tool-centric skills and drive toward the software engineering discipline, the large-scale system administration end of the spectrum support models, level one, level two, level three. These are established and quite mature, but they also introduce handoffs and some accumulated time as we try to work through problems. So driving to DevOps models where they make sense. They don't universally make sense, we're still getting our heads around where we will use them, but it will be a spectrum of support models from post-implementation hardware support, kind of the bone standard all the way up to the really highly agile, highly innovative end of the spectrum at the top, the DevOps end. And for us to be able to do this, we need to measure ourselves a little bit differently. As an idle shop, we have KPIs and these are how we measure ourselves, but in a DevOps world as we're driving toward the software engineering end of the spectrum, then we need to start bringing in some of the metrics that are relevant to software. How many releases did we do over such and such a time? Also including think things that are more mundane, like how many servers per admin are we supporting? These are the additional metrics beyond the KPIs that are kind of the standard idle playbook. So the metric scorecard is important. Being able to measure yourself is crucial. Being able to fold in these new metrics and have them become normal is very important. And then red is good. When you have a dashboard and there's some red on it, people kind of lose their minds and get really concerned. But for us doing DevOps, delivering cloud infrastructure, red is good because we know where the problems are. We know where to focus our energies. And then in our release and quality assurance realm, these are no longer separate teams of resources bringing a bucket brigade methodology to QA and what gets released, right? In a test driven development shop, everybody's doing QA. And they're doing QA first and it's just part of the software release process through automation, through CICD. So actually automating deployment. We've got a hugely complex environment. We've been guilty of building automation and deploying it by hand in the past. And then expecting the environment to remain static, not drift, not break, not cause problems. So how do we continually improve the system, deploy it to a specific specification and be able to pound out clouds as frequently as we have to, whether it's in a lab environment in a dev environment or the production environment itself. So continuous integration and delivery really is delivery of infrastructure, right? And we are at the maturity level where we're starting to shift to continuous delivery. We're not sophisticated enough where we think that continuous deployment is going to be a thing for us in the infrastructure space. But as we mature over time, we would get there and the bedrock is laid through continuous delivery. The automation still pushes the software updates out to the environment the exact same way. It's just a human drives it. And then longer term for us, infrastructure CI is really what we envision metal as a service. Metal as a service plus plus. So the lower left hand graphic kind of depicts where we are today. What we're turning on this week in an environment. It's deploying our own cloud infrastructure through automation, CI CD, nothing gets to the production environment unless it flowed down this automated path to production. But we've got additional use cases that are targeted for later in the year when, or not later in the year, next year when things like Ironic get a little bit further down the path where we will have targeted use cases to be able to deliver end using applications on metal to customers, right? And then ultimately we will find ourselves back in our software development and validation lab environments where customers can consume the same framework to deliver products to market. And really for us metal as a service is a game changer, right? We've got a huge silicon design environment. A bunch of us working in the cloud space today came out of that environment, came over to the enterprise space to work on this cloud stuff. And we really see that we'll link up eventually where we're talking about our industrial workloads that are taping out SFC projects or validating software projects are just running on a platform, running on infrastructure. And it's really no different than cloud applications, running on a platform, running on infrastructure. So metal as a service becomes a game changer once it's as easy to get metal as it is to get virtual and mass. And we could take the pets versus cattle kind of meme and drive that to the foundation. It changes everything that we do. We're on to QA. 2014 focus areas, rolling upgrades, no tenant downtime for resources of services, connection into all existing infrastructure. So a single control plane is our biggest focus for the year. Disaster recovery between sites for VM tenants, restart a VM when a host fails, hybrid cloud enabled through Horizon. And then using OpenStack to do additional work, right? So back up in recovery, we still have kind of the traditional media master client kind of architecture for Bar. We need to drive that forward. Bare metal provisioning, as I mentioned, some of the higher order load balancing firewall as a service type automation. And then, you know, we will, we've got some proprietary code around databases, service load balancers, the service that will be displaced with OpenStack going, going forward, things like Trove, right? So in summary, our direction is federated, interoperable OpenCloud. You know, the single control plane provides a compelling glide path to get us there, right? It doesn't displace or rip and replace all of our past investments. It really up levels the capability that we deliver to our customers. So it's highly compelling in that regard. And then in order for us to run cloud of scale, we're still going to be focused on IT culture. Our skill set continuing to tweak our business process, so, you know, including governance, right? And then down to the technology discussions. So what we are doing is we have implemented an SDN as an overlay network on top of our hypervisors. So and then we are leveraging two different models for networks where we have those non-onclave environments. We are still using shared networks with VLANs extended. And then where we have more secured environments, there, the model that we're going after is a pertinent router with private networks behind it. So that's how we are getting the segmentation from a network perspective. The next thing that we are actually working towards is, so this addresses the virtual environment. For the physical environment, as we want to introduce a similar level of abstraction that allows us to simplify our underlying network fabric. So along with the ironic or whether we introduce an open v-switch on the physical switches, whether we do open flow. So that's an area of research that we have that we are investigating so that eventually we are able to abstract even the physical servers from the network. Okay, thanks everyone. Thank you folks.