All of us. Hello, everyone. Dr. Akir Momen, junior resident department of cardiology, Seema Thikashi, by name of the Medical College Pune. My paper was on unusual, it was an unusual case of coexistence of adenocarcinum of appendix, juvenile ovarian granulose cell tumor peritoneal deposit in a 34-year-old female. Juvenile granulose cell tumors are rare gynecological diagnoses. Combined adenocarcinum of neoplasma of appendix can be musinus or non-musinus type. In our case it was a non-musinus adenocarcinum of appendix. The current study was to present a rare case of juvenile granulose cell tumor of ovary giving peritoneal deposits with non-musinus adenocarcinum of appendix in a 34-year-old female. My aim of the study was to report a rare case of coexistent non-musinus adenocarcinum of appendix with granulose cell tumor of ovary and peritoneal deposits. It was to evaluate and present the radiological feature of the above mentioned appendix in a new ovarian neoplasma. Detail USC CT MRI was done of the female, which was referred to radiology department with abdominal distention and pain. She had complaints of nausea, vomiting, loss of appetite, history of menstrual irregularities. Previously, the patient was operated for a large simple ovarian cyst in January. On current examination, the serum examination, serum CA-125, CENCA-19.9 were within normal limits. On ultrasound examination, there was a left adnexal lesion, which appeared, it was in well-defined spherical to ovarian heterogeneously hypoechoic lesion. The corresponding B1 image is the CT image showing a cystic density lesion with thin peripheral walls in the left adnexal, which is delineated by the red arrow. On MR findings, this is the star image, the B2 image. It shows a fluid intensity thin wall lesion in the left adnexal, which was slowly abutting to the superior surface of the ovary. The image C1 and C2 shows CT of the patient, which reveal partly solid and partly cystic lesion arising from the pelvic peritoneum in the left adnexal, such as peritoneal deposits. The D1, D2, D3 images of the appendix, which showed an hypoethynoating intramural, intraluminal growth within the appendix, which was in the base of the appendix, and it was in closed relation with the cecum. The patient was operated for bilateral sulfin gopherectomy, the hysterectomy, with pelvic peritonectomy, and bilateral pelvic lymph nodal sampling, with omentectomy and right hemicolectomy. Histopathological examination revealing the uterine granulesal tumor of the ovary with pelvic peritoneal metastasis, and the appendicular mass revealed well differentiated adenocarcinoma, which was of non-muscular state. On discussion, granulesal tumors are relish sex called tumors, which are divided into adjuvenin and adels, depending upon the age of presentation. Synchronous primary musinus neoplasma of appendix and ovaries have been reported previously. This was a very unusual scenario of involvement of appendix and ovaries of different embryonic origin, which has been rarely reported in literature. This case also stand out for reporting juvenile granulesal tumor of ovary causing peritoneal dissemination, which are also been scattered reported. Thank you.


Last non-conference matchup for the women's basketball team taking on D3 UW Superior after a slow start down 25-14 Brooklyn Bachman driving gets three the old-fashioned way they're down eight later in the second Bachman again putting the moves on the smaller guard 17 points for her in the first half she can dish it out to down to Gabby Du Bois in the paints to power dribbles and a bucket but a disappointing night for the Beavers they fall 58 to 50 if you enjoyed this segment of Lakeland news please consider making a tax deductible contribution to Lakeland PBS


Do you struggle to build your audience the number of followers on your LinkedIn company page? If so, I've got some good news for you because there is a specific invite connections to your company page. A really, really handy feature and in this video I'll be explaining the benefits of it and showing you in step-by-step instructions exactly how you can take advantage. I'm Jonathan Pollinger. I've been a social media trainer since 2009 helping businesses achieve their objectives using social networks like Facebook, LinkedIn, Instagram, Threads, Pinterest and all the major social networks. I've also been a trainer for NILC and established an agency where we manage social media. If you're interested in learning more about the contents of this video or any aspects of social media, check out the links below. Let's get straight into the video. So in this video we're going to look at the invite connections feature which is available on your LinkedIn company page. Now this is really useful if you want to grow your audience and there are lots of good reasons for wanting to increase your audience or the number of your followers on your LinkedIn page. So this is going to give you more visibility which is going to lead to greater engagement which should hopefully lead to more sales for your business. Plus there's actually a few features such as audio events where you need a minimum of 150 followers on your LinkedIn page. So that's a good target to go for and LinkedIn actually say that once you get to that 150 number your visibility of your posts is improved. So it's a good feature to get you up to 150 followers and beyond. So let's see how it works. So first of all it's very easy to locate because it's on the top right hand side of your page here and if you click on invite connections this pop-up box comes up here and you'll see that I can just scroll down and select people that I want to invite to follow in this case the NILC training page. So what is also useful is that as well as just the kind of like browse down here you've got filters. Now this is like really handy because I can filter for example by location. So if I wanted to look at people in the greater Bristol area I can click on show results like that and they will show up but there are other filters too like the company where the person is working, the school where they're currently being educated at or even their industry. So quite handy that you can filter by these characteristics here and of course you can just search for somebody at the top by their name and pop them an invite. So that's essentially what this feature does once you've selected the people you want to invite they're moved over here for confirmation. If you change your mind you can unselect them or you can remove an individual person here and then when you're ready you click this invite button and then they will receive an invite to follow your page. You're also prompted to make a post here about your invitation to follow the page but you might as well just do the post in your own time really so not really too much a benefit to this prompt here. Hope you enjoyed that video and that you now have a new way of growing your audience on your LinkedIn company page. If you did enjoy the video please like it and also subscribe to the NILC channel here on YouTube. For more information about our other videos please check out the links below and you'll also find links to our training courses as well. See you next time.


Over the past several months, we've been building out a model to better understand future data platforms. We use the metaphor of Uber for the enterprise. Now what we mean by this is if you think about the Uber app, it takes people and places and things, i.e. drivers, riders, destinations, ETAs, money, data in all different forms, structured, unstructured, semi-structured, and makes all that data coherent so that actions can be taken in real-time. Data is becoming the digital representation of your business. Incoming data informs the state of your business and data is the API by which you will program your business in the future. The problem is today's data platforms are not built for these types of real-time distributed interactions. That's why Uber had to build it themselves. We believe the combination of AI and new data architectures are emerging from innovative companies and ecosystems to deliver this type of capability to all enterprises without the need to have hundreds of Uber-class engineers on staff. This is Dave Vellante and on August 1st, please join John Furrier and me as we unveil the next step in the future of data. It's called Build Beyond, made possible by vast data. In this program, you'll hear from thought leaders in AI like David Fang of the Allen Institute, Max Tegmark of MIT, other data and AI experts from Zoom, Pixar and independent analysts like Merv Adrian. For more information, you can click on the link in the description of this video and register to mark your calendar. August 1st, 9 a.m. Pacific, we'll see you there.


This message brought to you by Snow Teeth Whitening. Whiten your teeth in nine minutes, anywhere you go, and use the promo code LETITSNOW for 25% off today. Check the description and pinned comment for that link. Something about the 69 million people that voted for Donald Trump.  You think that's every Trump voter? They voted for this consciously knowing what Donald Trump's stood for for the last four years. They know him.  And I don't think that they should be forgotten, and I don't think that we should look the other way. I think we need to remember. People must remember and hold you to account. I do think that people need to be held accountable. How much are we going to just let pass by? You cannot come into this White House with the idea that these people aren't the enemy. They are.  Shame on them. They are going to lose way more than this election. We want the prisons so filled with Trumps and Trump flunkies and Trump apologists and Trump enablers that we have to convert Trump buildings into new, goddammed Trump prisons. We want enough of them in there that they can hold reunions and birthday parties. Oh, my God. I have a ton of gripes with the Democrat Party and what they're doing to this country, but I'm not calling for you all to be locked up or sent to re-education camps. Why would I do that? Because I know that exact same warped logic can be used on me. And what alternate reality fiction has Donald Trump victimized you or anyone? Oh, but as we all know now, simply disagreeing with the left is tantamount to violence. One of the things that I've been talking about over the years is the danger posed by the left and Democrats because they seem capable of rationalizing just about anything. For a great example of this, just look at Chris Cuomo and his insistence that protests aren't supposed to be peaceful. And he only said this after Democrats started getting blowback for the violence committed by Antifa and BLM. It's been clear to me for at least the last 20 years that their ultimate goal is one party rule and complete destruction of their political opposition. We've been a thorn in their side and their policy agenda for a long time and they want an ultimate solution to that. What will happen is when we send over Republicans to re-educate them? Ha ha ha! You imagine Mitch McConnell? Oh, God, he wouldn't survive a 10. Lindsey Graham? I like that you guys are founded as re-education. Right. The first school line that was open, have you heard about the Bellemore Canal? People came from America to work in the Bellemore Canal for the Soviet project, the communist project. What a beautiful day. We want the prisons so filled with Trumps and Trump flunkies and Trump apologists and Trump enablers that we have to convert Trump buildings into new, God damned Trump prisons. We want enough of them in there that they can hold reunions and birthday parties. For example, they've convinced themselves that violence and intimidation on university campuses around this country are a legitimate response to political views they don't agree with. They've decided that months on end of rioting and looting from far-left extremist groups is mostly peaceful, while the real threat are Republicans and conservatives. They've ghosted all the prominent right-leaning figures.  Over time, they've slowly been stigmatizing with the ultimate goal of criminalizing their political opposition. It started by calling everyone they wanted to shut up and then it escalated to white supremacists when races lost its punch due to indiscriminate overuse of the word. But as those labels escalate, so do the justifications for what you can do in response to those you disagree with. That's what you're seeing in this video montage and it should concern you because if it carries on, more and more people are gonna feel justified in taking action. That's all for this one. If you enjoyed it, please hit that like button and share. If you wanna support this channel, you can find all those links in the description or pin comment. Thanks for watching. Keep coming back.


Hey guys, it's Nate, AKA The Foot Accountant. Welcome back to the channel. It's Monday, market outlook time. Let's take a look at the second week of Future Stars, talk about the market, what is going on right now, how we can make some coins, and just content and market movements to watch out for, because honestly, the stuff that we're looking at this week in FIFA, yes, Future Stars is going on, but honestly, I'm kind of shifting my mind away from the actual Future Stars promo, except for some of the content that might come out, because we have big time stuff that could be coming this week with icon swaps, winter upgrades, icon moments cards being in packs, road to the finals, market movements, all of that kind of happening either during the week or at the end of the week. There's a lot going on this week, man. So we want to talk about it all today, kind of take a high level approach and cover all those items in a sense on the market outlook and where I think you can expect to see the market heading this week. First of all, let's talk about the content that we had yesterday on Sunday. Pretty quiet day, right? Pretty quiet day on Sunday with this Kukarela Future Stars Academy Player card. Now EA is playing right into the current meta inside of FIFA with that 532 or the 352. A lot of people using wing backs and like left and right mids that have, you know, very balanced and well-rounded cards that can get forward and come back on the fence and this guy fits into that meta perfectly. Not the best card ever, but definitely something. Some people will grind, right? I think people would rather do Renier first because this Striker card looks really good but also people might grind this Kukarela this week. So that was also content that we had. I expect one or two more, honestly. Maybe just one more of those Future Star Academy Players this week with the Foot Future Stars being in packs for the rest of this entire week. And I think that's where we start the week. I think today on Monday, since we had that yesterday on Sunday, probably not an objective player, but honestly, the most interesting thing today is that the SBC player picks are expiring. The player picks, the 81 pluses and the 82 to 88 upgrades to your last opportunity to get in on some of those. And this is gonna be probably like the end for some of these upgrade packs and the amount of coins that they'll be taking off the market. Now I do think EA could put out different upgrade packs if they really wanted to until Friday. Like if they wanted to do like an 80 plus player pick or the 81 plus double upgrade pack. I think there was a possibility that they would put out more upgrade packs to kind of keep us, I guess, involved until Friday. But also, EA might look at it and say, hey, we just dropped two Future Star Academy Players and objectives so we're not gonna release any upgrade SBCs because people are gonna be busy doing that. Well, that could be possible as well. We also could see another player SBC today with Curtis Jones, Torebo, Musa Dambili out, of course. They've been doing a lot of player SBCers doing this promo. I don't know if it will come today, but they've been kind of doing like a couple days on and they take a day off. Then they come right back with another SBC. I forget what SBC we got last week on Monday. But I do believe that we got one. I just don't remember who it was. It might have been Goncalves. I think we got Goncalves last Monday for the Future Stars player pick. Now again, we have a lot of SBCs out right now for players. I don't know if they would do another one. One thing we maybe could see today would be like that double 85 plus pack or like an 84 plus player pick. That might be some sort of upgrade SBC.  I do think that we're expecting though another big time flashback SBC player at some point this week. Now, Ferland Mendy has obviously been in conversation. Could he get a flashback card? There's a lot of Future Stars that EA could pick and say, hey, we're gonna use a flashback of this card back to FIFA 19 or FIFA 20 Future Stars and put them out. So that is, we haven't had a flashback, legit flashback SBC. The player moments done barely was kind of like a flashback but we haven't had a legit flashback to a Future Star. I don't think, unless I'm thinking incorrectly. But I would suspect that one more big player SBC comes in this next week as we head out of Future Stars. Now, SBC fodder right now is dropping a little bit, right? I think it's just because the lack of new SBCs that are out, a lack of people wanting to grind like the icon pack or whatever. Some of this stuff has dropped off, right? And you can see this by looking at the price of Curtis Jones, 394,000 coins. This card is literally 35,000 coins cheaper right now to do as an SBC from scratch than he was when he first came out. So fodder's dropping a little bit. And I think that's just because, you know, we just had squad battle rewards that's supplying the market a little bit. And you're seeing some of this stuff drop as well as the demand for actual SBCs is diminishing as well since we didn't have any new ones yesterday. That supply is just kind of making that part of the market drop down a little bit. So that's kind of how I feel about the SBC fodder market. It's probably gonna continue to fluctuate this week if you're really good with fluctuation trading a fodder when an SBC comes out like panic or mass buying right away. That stuff's probably gonna be pretty profitable this week. Now, of course, a lot of people are gonna be asking, player of the month, Neymar, that is like a big SBC that is on our horizon. I feel like there would be a bigger SBC. I feel like there's still another like either Future Stars flashback or a Future Stars player SBC that would come out before a Neymar would which could still move fodder around on the market a bit. I have a feeling that the league one player of the month vote always goes for so long. And right now we just checked just a little bit ago and it is still live. The vote is still live for league one player of the month. The Yazeki SBC I think expires in a few days still. So I'm honestly not expecting player of the month Neymar. If it's this week, it could be at the end of this week but it also could be next week. It all kind of depends on when the league one voting stops on the player of the month website for EA. So we'll keep an eye on that. But of course, it's not even guaranteed to be Neymar. So I think could be Kevin Volland. I think he's gonna win just not necessarily the popular fan votes, but he had an insane month and Neymar is now injured. So an EA doesn't have full control over player of the month. That's more up to the leagues and the voting. So I think it might actually be Kevin Volland winning that player of the month. We'll talk about that more later this week as it doesn't get closer but I could see that coming later in the week this week. Now we mentioned SBCs, we mentioned objectives. Let's talk about the market, right? Tuesday, right? Tomorrow, Champions League is back baby. We have Champions League games that are back and road to the final cards are the next thing and I wanna talk about because some of these cards have still maintained at very high prices and have even gone higher than they were before in price. Now, number one thing about this that worries me Cancelo road to the final is 400,000 coins. Crazy, right? Now, yes, these cards are very rare. The upgrade potential is huge but since the market has continued to drop off out of this weekend league, these guys have not really dropped with it and that to me says people are still investing in these cards and they're holding on to them and that is a sign that you probably wanna sell and take the cash sooner rather than later on a lot of these cards. Honestly, that's how I feel on some of them is you wanna take the cash sooner rather than later. Right now I'm looking at this Cancelo, the 86 rated in form because this is literally 200K cheaper than his road to the final card and the stats are almost the exact same. So I think that this card, of course, it links to the brand new Ruben Diaz. I'm gonna be watching this card because I think he will rise a little bit out of this weekend purely also because Cancelo is 400K. This card's almost the exact same and it's 200K cheaper and it's a very popular right back in FIFA. So I think that some of these road to the finals and as we take a look at this price right here, some of these prices ravaged 215, Pogba 710, Brandt is 155, David Alaba's up like 30K from where he was earlier today at 610. I really, really think that just like with the headliner cards, they get so inflated hazards a million, wow, hazardous a million coins. These guys get so inflated before their actual upgrade happens that you wanna sell them then because so many people have been hoarding these cards and holding on to them and of course this week as well with the games actually happening, you're not guaranteed to upgrade, right? Some of these guys could lose, especially the one thing I wanna talk about and we'll look at road to the final cards more specifically tomorrow and like the trading you might be able to do with these actually on Tuesday and Wednesday. These cards had the potential to just drop a ton depending on how the first round games go, right? Especially for Champions League games, these cards get upgraded after the first leg. If they win, they get an upgrade. But also you have to think about that second potential upgrade coming in a couple weeks when they would play the second leg. Is that team who is down and lost, could they potentially make a comeback and their cards price rise back up with a comeback win moving on to the next round? Stuff like that you have to keep in mind. Literally these cards are gonna swing hundreds of thousands of coins at a time on the really meta ones that are high priced as goals are scored. But the safe way again with these road to the finals is selling in the hype pre-game with all of them, right? All of them. And again, I'll make the point like I said before, this Ed and Hazard card is one million coins. Look at this guy's graph, a slow upwards trending price, right? And he's actually at his peak right now. I think you wanna take the cash on just about all of these cards. Yes, you could say, yo, Hazard's gonna go to a 91. But I think you wanna take the cash because why risk it? You're making coins already. If you bought a Hazard like during team of the year, when he was 700K, you're making like 200,000 coins after tax on this card, you're feeling good, right? Even some of these lower tier cards, Perlmez was 220 this morning, he's 240. Portus was like 170 during team of the year. Akanji was like 200K last week. Kulabali was 700K this morning. If you're making profit on some of these cards, take the cash because I do think since the rest of the market has come down a lot in the past couple of days, as you can see here, the icon market was at 88 points and now it's down to 82. The whole entire rest of the market is doing that as well right now. And that's why I think you might wanna take the cash on some of these because as the rest of the market drops, these cards have held their price. It seems like these cards need to drop off as well just because so many people have bought them and held onto them that they're gonna wanna try to realize their investment profit very soon. And I do think you are gonna see some of these RTTFs drop. So that's one thing that I'm really, really looking to see and really looking for a market movement early this week into Monday into Tuesday. Now of course, these cards are a bit extra inflated right now because people bought some of them probably right around the squad battle rewards timeframe, which is a timeframe where a lot of people just buy cards on this game for whatever reason. This Bruno Perez earlier today was under 200K and looks like right now he's been bought up about 10,000 coins. This guy was in the low 190s, he's back to 206. Now some of these cards are gonna get a little bit hyped up more than others depending on their links and depending on what matchup they actually have and the potential upgrade, right? These are in form upgrades these cards could be getting. So you look at a guy like Akaji, like this guy is an 84 rated road to the final card at 230, 240,000 coins. But this guy, if Dortmund win that first leg of their Champions League knockout fixture, this guy is getting a plus two, not just a plus one, right? He's gonna go to an 86, it's gonna be an informed type upgrade, he's gonna look literally ridiculous, especially with a lot of Dortmund links being popular right now, that might be a card to keep your eye on, but still, almost on all of these cards that are RTTFs, I would sell on the hype because again, I feel like a lot of them need to be corrected in price as this whole market has dropped recently. So that's one thing I wanna keep in mind with those road to the finals and again, we'll talk more specifically about those in the upcoming week. Now let's talk about future stars again for a second, just talking about where these guys' prices could go. I think these guys are gonna continue to drop until the weekend and honestly, these guys might get cheaper when this actual Friday comes with whatever content comes out with the new icon swaps. That's a big focus for a lot of people. If icon moments come out, you might see some of these top tier guys like Fatih and Saka whenever he becomes available on the market. You might see some of these guys drop. Now this team as a whole looks really cheap compared to team one in my opinion. You only have one, two, three cards that are a million coins or over and I think in team one, you had a couple more than that. You had Reina, Kamavinga, I guess there was three in this team as well, but there's a lot of like 600K here, 660 for this Reese James, booming out of packs as he has become very rare and just so meta and so valuable. A lot of these guys I think will bounce back this week, even though the market's kind of dropped back down, these guys are fresh, they're hyped, people wanna try them out. Super Sly for like 550 is a buy in my opinion. Bergwine was 940 today, rebounded all the way back up to like one million coins and a little bit above. I like Harvey Barnes with the Curtis Jones links. So I like buying some of the sell off on the Future Stars from team number one that we're out of packs and for the rest of the market with special cards, I know we talked about Centerback, Todebo only being out for a few days, but seriously, watch Centerbacks. Keep an eye on Centerbacks in this game right now because some of them that might be sold off a bunch that's still very meta or very rare and have good links, those could bounce back faster than I think the center midfielder's could bounce back because Curtis Jones is out for two weeks, whereas that Todebo is only out for like six days, five days, and just like we saw with Boateng, we saw some of those Centerbacks bounce back pretty quick, right, Alaba wrote to the final card.  He was like, he went from 500 and something, 1,000 coins all the way down to like 500k flat, and now Alaba is back up to like the 610,000 coin range as we have Champions League kind of coming up. So yes, these are live items and that maybe impacted their rise a bit too, but I'm looking at guy like Freeze Casamiro. Those links are just kind of crazy, right? La Liga, Real Madrid. You know, we've had some Real Madrid players recently with the Lunen, there's some goalkeeper links there or Varan in form, stuff going on with Madrid players. So links right there, maybe bringing that card price back up and he's just rare in general. So definitely keep an eye on some of these Centerback cards. And you know, I bought a Cuadrado today because you know, there was a lot of Centerback and center mid sell off in this game, but I watched this Cuadrado and he is just a, if you're gonna link that Ronaldo or Kulusevski on the right side of your team, I mean, this is literally the guy that you're gonna do it with. So I bought a Cuadrado at 177, I think. And it looks like right now he's still right around 180. This guy was 220k and this is like the premier right back in the Serie A and he's got those Uve P-Monty-Cauchio links. And I think that that is a very valuable thing in this game. So a lot of meta cards that are just rare for their position, for their league, and just very hyped up in general. This Kunde, even though he's a French Centerback, was like 95k, went down to 79,000 coins. This headliner streak, Ben Yetter, was like 165 and he's bounced back, man. I was gonna buy one at 152. He's all the way back up to 1.6 mil after he actually scored two goals today and dropped down. So there's mad fluctuations right now on this market. Looking at a lot of these cards, you know, these record breakers that are very rare, there's still ways you can make coins in this market this week because cards are gonna fluctuate, cards are gonna be rare, especially icons, right? People are scared to trade with icons right now. This Ronaldinho is 1.6 million coins right now at the moment. I bought one for 1.43 today and I sold it for 1.557, I think was the price. And I also flipped a Blanc. Yeah, 1.1547 for Ronaldinho. He was around 1.5 for all day, bought one at 1.43 and flipped it and this was bought at 990K. I'm at a solid flip right there.  So that's why I took advantage of some of those flips and bought some of those cards was because I knew that I was gonna be able to fluctuation trade some of those icons. So don't be scared to trade this week, right? Yes, the market has lost some of its buying power, prices have dropped, but usually when that happens, people are scared to trade. There's less competition and you can actually make coins. So that's kind of what I'm thinking along those lines. Now, one last thing, right? I'm making this video kind of longer. I don't want it to be too long, but things to watch out for this week related to what could happen on Friday. Winter upgrades. We're gonna have another video coming out after this later today on Monday, talking about winter upgrades specifically, but then also icon moments and icon swaps. Those are really, really big things people are wondering about right now. Definitely watch the pack code because I feel like once we get pack code stuff and add it in, that's when we're gonna know what timeframe some of this icon swap stuff could be. Some of the SBCs that we could be getting. We still need an icon moments card design has to be added to the code because that should be coming soon and that should be a part of the next set of icon swaps. There should be icon moments cards that we can attain through swaps in my opinion and especially through hopefully some of the packs. Maybe like a mid prime or icon moments version as one of the swap objective packs. That'd be kind of a cracked out pack. That'd be very interesting to try. So keep an eye on that kind of stuff incoming. And then of course this Friday with maybe it's icon swaps, maybe it's icon moments and are they gonna actually brand it as winter refresh? Again, maybe we'll see some loading screens this week. I doubt we will though because usually E8 doesn't like to do a lot of loading screens to promo another promotion coming up while they have something going on. Like we didn't see any loading screens last week for set to a future stars but if E8 really wanna cause some hype or start to get the minds turning maybe we could see some loading screens this week about whatever could be coming this Friday. So that's kind of like the biggest questions this week with the market. Road to the finals are gonna be crazy to trade with. They're gonna be crazy to make coins with. Honestly big time fluctuations. It's gonna be risky but fun. And of course future stars people are gonna be trying them out. We're gonna have pack supply. We're gonna have more SVC and hopefully some objective content as well with another future stars Academy player. It's gonna be a busy week. It honestly is. We're gonna be here for it. We're gonna be riding it through all the way. That's the market outlook. If you enjoyed this video smash the thumbs up on it. Comment down below if you have any questions and subscribe if you're new. It's been Nathan Foot Account and catch you guys later. Peace out.


There are few conditions for an electrolyte to be used in to be used in salt rich, ok. The first reason is what the ionic mobility of these ions must be equal, ionic mobility is more tendency to move in the solution. Now, suppose why these two ions must have equal ionic mobility, suppose if it is not equal K plus has more ionic mobility than CL minus, then this K plus will utilize this negative charge faster than CL minus. Then also what happens, the electrolyte will not be maintained. The condition is what these two ions must utilize this positive and negative charge simultaneously. If one negative charge will get utilized here, at the same time one positive charge must get utilized on the other side, right. That is why the first condition is what the ionic mobility of ions of electrolyte present in the salt rich must be same, right on the first condition. Now, this point to write I will discuss. The ionic mobility of the ions present in the electrolyte, of the ions present in the electrolyte in salt rich must be equal. Second condition, second and last condition. The ions of electrolyte present in salt rich, the ions of electrolyte present in salt rich must not react with, must not react with, the ions present in the half set, both half set must not react with, the ions present in the half set. Now, the second point means what, suppose we have, suppose I am using K plus and CL minus here, if the electrode is silver or AG plus ion is present in one of the half set, right. So, AG plus and CL minus combines and forms what? The precipitate of AG-CF, AG-CF solid. This precipitate, if this ions, ions of salt rich reacts with the ions of present in the half set, that forms precipitate. If this precipitate forms, then what happens in the half set? There will be some accumulation. This initial precipitate will start accumulating on the bottom of the precipitate and that will also stops the working of, affects the working of electrochemical set. So, second condition is what? The ions present in the electrolyte must not react with any ions present in the half set. Basically, if we have silver electrode, we cannot use KCL. We can use of any other, we can use of any other electrolyte, right. So, this is the condition. Unless you have this, can it out? No. Okay. Next we have of EMF of the cell, right down next. EMF of the cell. Have we discussed Nernst equation? No. Okay, after this. EMF of the cell. Next point. You will not get any numerical question on this electrochemical cell transformation, theoretical question you can give. Now, EMF of the cell can be defined as E cell, for it as E cell. E cell is equals to, we write E of the reduction potential we are taking of cathode minus the reduction potential of, this is the formula of EMF. Both are reduction potential of cathode minus. But we also know what, we also know E reduction potential of cathode is equals to what we can write? Minus of E oxidation potential of cathode, right. And E reduction potential of anode, reduction potential of anode is equals to similarly we can write minus of E oxidation potential of anode. So, we can write EMF of the cell in terms of oxidation potential and reduction potential. If both we are using oxidation potential then what happens? This is the one formula. I will ask you to memorize only this. Okay, you can write down in any other option. But write down the formula, if this and reduction potential will convert into oxidation potential, in the formula becomes what? Can I write this E cell is equals to E oxidation potential of anode minus E oxidation potential of cathode, right. Again you can write E cell is equals to minus E oxidation potential of cathode minus E reduction potential of anode. Or we can also write E cell is equals to E oxidation potential of anode plus E reduction potential of cathode. Is it right for the four different forms? Correct. Zn is equal to form but Zn is equal to form precipitates. Zn is equal to form but it will exist in the form I am Zn plus NCl by Zn plus 1 to Cl minus. So, EGCl forms what? EGCl forms precipitates, it will start building over here, right. We will have a solid building here but Zn stays in any component, it will remain in the form of I am Zn plus 2 to Cl minus, right. Understood this? Okay, now this is actually at any condition, right. At a standard condition what we can write? At standard state, the standard EMF of the cell, right. EMF of the cell at any condition but when we take a standard EMF becomes what? Standard EMF. Standard EMF of the cell is what? E0 cell, right. E0 cell what we can write? E0 of reduction potential of cathode minus E0 of reduction potential of anode. So, you just memorize this one. Okay, all these other three you can write since you know this. Only one, this one is the part of the reduction potential of both if you are taking right cathode minus anode. Since cathode is present on the right side, we also write as E right minus E left. Yes, in some way we will see this also. E right minus E left. Why right? Because cathode is present on the right side. Only one thing you remember, cathode minus anode where both are reductions, right. E, reduction potential of cathode minus anode at a standard state. What is the E0 cell for this Daniel cell or electrochemical cell? What is the E0 value for that? 1.1. So, for Daniel cell what we can write? Daniel cell is nothing but this electrochemical cell. Daniel cell we can write E0 of the cell is equals to E reduction potential of cathode. What is cathode copper? What is the reduction potential value? 0.34 for cathode minus 0.76 for zinc that is anode. This becomes what E0 cell is equals to? 1.1. Next write down cell notation of electrochemical cell. Cell notation of electrochemical cell. For cell notation there are some rules we have. According to that rule we represent a cell notation for a given cell reaction. Cell reaction is different. Cell notation is different, right. Cell reaction is what? Zn gives Zn plus 2. Zn plus u2 plus gifts. Zn plus 2 plus u sorry. That is cell reaction. But cell notation is different. So you should know the conversion of cell reaction to cell notation and cell notation into cell reaction. Both are important. Right on the first point into this cell notation. The first point is the anode is written on the left side and the cathode is on the right. Anode is on the left side and cathode is on the right. Next second rule. The phase boundary are represented by, the phase boundary are represented by a single vertical line. Single vertical line, single vertical line means the phase boundary are represented by this single vertical line. The concentration of electrolytes, the concentration of electrolytes in anode and cathode half cell, in anode and cathode half cell must be written in parenthesis, must be written in parenthesis. In case of the gas, in case of the gas, in case of the gas, the partial pressure is to be mentioned, the partial pressure is to be mentioned in ADM atmospheric, in ADM or MMR. A comma is to be used to separate, to separate two chemical species present in the same solution, in the same solution. Double vertical line is used, double vertical line is used to represent, to represent salt rich, to represent salt rich. EMF of the cell, EMF of the cell, must be written, EMF of the cell, must be written on the extreme right, on the extreme right. Now you see, the first very simple example we are discussing, we have Daniel's cell. And what is the reaction of Daniel's cell? ZL from it converts plus Cu2 plus H1. Suppose this concentration is C1 mole and it converts into, that was C2 mole plus Cu4. This is the reaction. Now the reaction of anode is what, reaction of anode is what, this is the oscillation right. And this is the reduction. Anode is zinc electrode and cathode is copper. Anode must be written on the left side, left side of salt rich. Salt rich is represented by this, double vertical line is salt rich. ZN is converting into ZN plus Cu2. So we will write what ZN, solid and the phase boundary because this is solid, this is aqua solution right. The phase boundary is represented by the vertical line okay. And here we have ZN plus 2 C1, sorry C2 mole. Just after this we will write down the concentration right. After this this is anode, whatever is written on the left side of the salt rich that is anode, that represents anode right. Now cathode is what Cu plus 2, concentration is C1 mole right, converting into Cu4 right. This phase boundary, this is the metal we have and in the last we will write E. So this is cell rotation and this is cell reaction. Understood?


What if we can use our COVID-19 scientific discoveries to help save lives? Here at Hackensack Meridian Health, we are attempting to do just that through a new COVID-19 vaccine trial. I'm Dr. David Koons, an internal medicine physician and co-chief academic officer at Hackensack Meridian Health.  We need your help and are actively recruiting volunteers. We are looking to enroll people of diverse backgrounds to better understand how well this vaccine might work for different groups of people. This means participants of different ages, races, and health conditions. We look forward to working with you for the betterment of everyone. To find out if you are eligible, go to hackensackmeridianhealth.org slash COVID-19.


Bienvenue, encore une fois, pour les gens qui m'ont déjà vu à l'hôtel de la seconde session. Je m'appelle Julien Stroéker. Comme vous pouvez le voir, je vais faire le même drac ce matin. Les gens ne sont pas de France. J'ai originé de France, borné en Montpellier, en France, vivant en Montréal, au Canada, et travaillant pour Microsoft Seattle. J'ai beaucoup de fonds en travaillant pour Microsoft et j'aimerais dire que j'ai du plaisir avec la technologie d'open source et j'ai beaucoup de focus sur la technologie de DevOps. J'ai partie de la division du CSE, pour l'engagement du succès des clients, je pense. Nous avons juste une réorganisation, nous avons changé le nom, c'est pourquoi. Mais l'idée est d'engager avec un client qui est en train d'utiliser Azure et d'être un de ces groupes de feedbacks avec l'engagement de l'engagement, donc d'engager avec un partenaire et un client et de donner le feedback à l'engagement de l'engagement, et de l'envers de la technologie d'open source. C'est beaucoup de fun. J'ai vraiment aimé. Aujourd'hui, je vais parler de l'autoscaline mesos cluster. Donc, l'agenda pour ces 45 minutes, je pense. Un petit peu de concepts. Je vais partager le code, en fait. Il y a quelques slides et la plupart de mes presentations, la plupart de mes presentations seront live demo et code. Donc, quelques slides, et ensuite, on va changer la présentation à la demo. Donc, un petit peu de concepts. Comme je l'ai dit, parce que la plupart de mes temps à Microsoft, j'ai engagé à faire des codes avec les partenaires et les clients. Une d'entre elles m'a demandé une façon de faire l'autoscaline sur DCOS et sur Azure. Donc, je vais vous montrer le code. Donc, je vais vous montrer le code, c'est partie de ça. C'est un peu de concept. Je ne peux pas partager le code avec les clients, mais j'ai essayé de l'extraire et de jouer avec ça et de partager ça pour faire l'open source. Donc, c'est d'une POC. La idée de nous, c'est d'évoquer un cloud privé de public et d'être capable de l'autoscaline. Donc, je n'aime pas ce monde parce que l'autoscaline est magique. Et le problème de l'autoscaline, il n'y a pas de manière magique pour l'autoscaline. Parce que je suis sûr que si l'autoscaline est magique, pourquoi elle n'est pas dans le produit aujourd'hui, pourquoi elle n'est pas sur DCOS, je veux dire sur Mezos. Autoscaline, c'est un aspect juge, ce n'est pas un problème, mais c'est un aspect juge. Vous pouvez l'exprimer par CPU, GPU, RAM, Troupert, netwalking ou quoi-même. Donc, c'est un scénario custom pour chaque case. Donc, celui-ci, parce qu'on veut qu'il soit simple, 45 minutes, encore une fois, je vais juste partager mon vision sur ce code et prendre un scénario plus simple et plus facile. Oui. J'aime faire la joie, parce que je travaille sur Microsoft, j'ai dû faire un slide de marketing. Et, encore une fois, c'est le même que j'ai présenté hier-bas, juste pour vous donner un petit concept. Je ne sais pas si ici les gens sont en Azure, dans la salle. Oui, non? Wow, 1. Donc, oui. Je pense que c'est bien juste d'expliquer ceci. En Azure, nous avons un service qui s'appelle ACS. Nous sommes pour Azure Container Services. C'est juste un moyen de déployer un orchestrateur, un orchestrateur, donc un orchestrateur, Kubernetes et un DCOS. Le cool chose, c'est que, pour exemple, pour un DCOS, nous travaillons dans la salle et quand vous déployez un DCOS clusters, c'est un cluster backing, supporté par Microsoft et la salle. Donc, les meilleures practices. Et quelque chose pour l'autre provider. Nous appelons ceci ACS, les container services. Nous avons un peu de services différents. En Azure, nous avons annoncé un nouveau service, qui s'appelle AKS, pour les services à Azure Kubernetes. Mais oui, nous avons un peu de services C'est l'ACS, et nous avons aussi une source d'open source. Quand vous déploiez et utilisez l'ACS ici, c'est le Microsoft Way. Vous pouvez aller sur le portal ou en utilisant le CLI. Vous avez un peu de différents interfaces. C'est mon cluster, je veux 3 master, 5 nodes. C'est le site que je veux. C'est tout. Nous faisons tous les magiques pour vous. Mais si vous voulez une configuration custom, comme l'intégration VNet, vous voulez utiliser GPU, une version spécifique d'ACS et d'autres. Nous avons aussi une source d'open source, l'engin derrière cette magique sur le portal et sur l'ACS. Nous appelons donc l'ACS Engine. Si vous voulez un déploiement custom, vous pouvez toujours faire cela avec l'ACS Engine. Ça fait le sens ? C'est tout pour la construction d'ACS Engine. Vous avez juste à définir. Mais il n'y a que de 50 lines de JSON, vous avez juste à définir la structure que vous voulez pour déployer sur Azure. Vous avez des options de mandatory, donc je veux utiliser D.C.OS. Vous pouvez aussi spécifier la version, je veux une master. Vous pouvez spécifier un bunch de différents nodes. Et c'est tout. C'est ça. Vous avez juste passé ça pour dire que l'ACS Engine va générer et parler à l'API, derrière la scène, et ensuite déployer tout, tous les VMs, les networkings, les storages, etc. Ce n'est pas ce que je vais utiliser pour mon demo, et la chose que j'ai envie d'insister ici, j'ai envie d'insister sur le fait que j'utilise un custom label pour Mezos, donc je déploie trois différents pools d'agent, donc basically three stack of nodes, if I can say that, so three times, sorry, three times this VM, which is a standard D2v2, it's two CPUs on Azure, so two CPUs for Gease of RAM, so I want three times that one, and for that one, I want you to also include the tag, the Mezos tag, the constraint, for workload with the value stateful, we're going to understand that later, same thing for stateless, and I also have the public node somewhere, here, three public nodes. So the cool thing with that, you can change the parameters, pass that to ACS Engine and then it's going to deploy that for you. Again, think about that, 45 minutes, so now 40 minutes or 30 minutes, the simpler, easier scenario, right? So we're going to focus only on the stateless workload because we're going to, I mean, what I want first is to easily auto-scale without any storage constraint, for example. We're not going to start to play with stateful scenario, right? Here, the idea, it's okay, I want to be able to easily scale my CPU, for example, or I want easy, I want you to scale, when I need more CPUs to deploy my application, I want you to scale on that matrix, make sense? So then, when it's done, pass that to Azure and Azure doing the magic for you, like I said.  So if you're not using Azure, the same thing on AWS and GCE, basically. And one thing interesting here, you remember, I'm supposed to have three agent pool, which on Azure, we call that the VM skillset, so bunch of VMs together, let's do that. And here, I tag one with stateful, one with stateless, and we suppose I have a third one for the public agent, right? So on Azure is that thing here, I don't know if you can see, but it's as we call the VM skillset, so one for DCOS agent public, another one for SF for stateful, another one for stateless. So I just click here for the stateless one, and per default, I have three instances running on that one. That's normal, because I ask for three, right? So this is what I have on my deployment right now. Now it's came to the code. So I think I share on the slide the URL of the code of my auto-scaler. So basically, it's a Python tool, let's say that. I'm using click. I don't know if you heard about this framework. Click is just a cool Python framework to follow with you to do CLI frameworks. So this is the way that I code that. So here, when I start to code that, I say, OK, I don't want to do something just 100% compliant and related to Azure. I want to be able for people, if they want, to also use the same logic for any cloud provider, public or private, right? So the idea is I'm using a provider, so in my case, Azure, and then I deploy a bunch of nodes, so one for stateless, one for stateful, and it could be different constraints. Let's focus on stateless. And here, on that example, I have four. I want to be able automatically to scale for four, four plus two, plus two, plus two, plus two, depends on the demand. I want to scale up, scale down. Makes sense? So what I'm going to do, I say, OK, fine. It's not really complicated. I have to find a way to ask mes us how many resources I have, how many resources I want, how many I'm consuming right now, and then do the math and talk to the provider first. And I mean my class provider, and the provider is going to say, OK, because you're using Azure, this is the class that you have to use, and you're going to say to Azure, OK, scale up or scale down. And then, it comes also to constraint. You remember, on my deployment, I also specify some constraints. So I have one for workload, and workload as stateless and stateful. Why the constraint? So when I'm doing the math on term of CPU conception, I want to do that only on the stateless one. We don't want to play with the stateful right now. So on the code, this year, it works. It's really, really straightforward again. Kind of shitty code, but it works. I have a cluster class. I was talking to provider class, and that class talked to different provider. In my case, it's Azure. So when you start the CLI, you just have a switch option for provider. In my case, it's Azure. And because Azure knows that we're using Azure, and all the logic to scale up and scale down for Azure, it's here. And yeah, that's really, really straightforward. That guy's going to talk to Azure, and then when it's come back, he's going to redo the math. It's just a loop, actually. I have a timer every minute, so every 10 minutes, for example, I want to ask Mesos the conception usage, do the math again, and then again send a request to my provider. Makes sense? So let's do the demo. So first, the link here. So that's the code. Like I said, three classes, cluster provider and provider Azure. And my main file, Python file, actually. And here, I have all the options. Again, I'm using the click framework. So this is all the options to specify. So I'm not going to go deep on the code, but at least I already explained how it's supposed to work. If you want to state to have more explanation, actually, I try to describe how it works. And this is all the switch and all the options that I have. So for example, I have to specify the provider name. That one is monetary. I am specifying that I want to Azure. That's the only one that I implemented right now. If you want to implement it for AWS, GCO, whatever, you're more than welcome to do pull request. The timer, per default, is every minute. It's going to poke the API, the mesos API. But if you want to have the 10 minutes, 20 minutes latency, I can also reduce or reduce that. Here, I call that the cap. So the trigger. When I'm doing the math, so for example, if you're consuming 80% of the CPU consumed by my application, this is added trigger, the 80 percentage, that is going to scale up. So I can change that. When I'm going to reach 50%, for example, on my conception, I can trigger the scale up, or 60, or 75. For example, that's this option here. Same thing for the scale down. If you want to implement the scale down, actually. I can also have specify the limitation. You can scale, scale, scale. But maybe you don't want to scale to 100,000 nodes. So if I want to stop the tool to scale at maximum 20, and something for the minimum 3. Then for Azure, if you, I mean, only one person using Azure here, but the way to talk to the Azure API is we call that the SPN. We stand for Service Principal. Basically, just a key password, subscription ID, and so on. So for information to be able to talk to the Azure API, so trigger action like scale, add VMs, reduce VM, and so on, the location, and so on. So that's last option here. It's really specific to the provider that we seek. So if you want to implement AWS, for example, I'm pretty sure that for AWS, you also have specific options that you have to specify. So it's something that you can have, same thing for GC, and so on. So this is how it works. So I'm a cluster here, deploy. And again, if you remember, one master, three different nodes for the public agent and stateful and stateless. So for example, if I'm going on that one, that first host name, if I'm going on details, you can see here on workload. I don't know if you can see. On the back, can you see? So that one, for example, is a stateful node. So we're not supposed to touch that one here. We can if you want, but I can say let's keep that simple. Same thing for the second one. So here, the way that I deploy that on Azure, a different subnet here. So I know that that one, one, two, three, it's supposed to be the stateful one. Normally, the next one, that one's supposed to be the stateless, actually. So yeah, we have the stateless node here, and so on. So I already deploy an application, actually. That's my beautiful Hello World application here. And if I just show you the marathon file here, while I specify, again, let me know if you can see. But I deploy that one only on the stateless. So it's just a web application, right? No storage. It's not a stateful application. That's the one that I want to handle. I want to be able to scale any stateless workload. Because when I start with Mezos and DCOS, I mean, I guess it was the same thing for you. When you don't really understand that's consumption stuff, right? When you have to specify how many CPUs you need, how many memory you need. And sometimes, you deploy, deploy, and then you can see waiting. Yeah, why do you wait? I mean, why were you waiting? I have resource available, right? But yeah, when you say I want one CPU for this application, even if you're not consuming the CPU, it's going to block the CPU for this application, right? And here, I'm running three instances on my web. So again, back to my configuration here. That one, it just, in term of transition, I'm asking for one CPUs for that application. That means I'm consuming three CPUs. Again, on my nodes, on my stateless nodes, there are three times, as we call a d2v2 on Azure, which is one VM, one d2, it's a two CPUs.  So I basically consuming 50% of my CPUs here, right? So let's launch my awesome auto-scaler. So here, it's supposed to work like I described. So I specify all my parameters here. So then I'm crashing all the logs for debug reason. So it just trigger and detect that it's Azure. The timer is 10 seconds. The scale-up cap, it's 80s. That means that when we're going to 80% of construction, this is when it's going to trigger the scale-up, sensing for the scale-down. Maximum node is 20, minimum is three. The endpoint I'm going to reach, actually, that's interesting. This is where all the magic happen. Basically, I'm curling that endpoint here. If you don't know that, this is where I'm grabbing all the resources. So when I'm doing that here, on the leader mesos slash slaves, I have all the resources from the slave, right? And basically, I'm parsing this JSON file. Because that one, from that one, I can see the CPUs available, the CPU consummate and so on and so on. So back to my thing here.  And then, every 10 seconds, it's going to poke the API and going to check the consumption. So you remember the scale-up cap, it's 80%. I'm consuming 50%, no magic here, right? So let's scale to one more here. See if it works correctly. I'm scaling to four. And we have 66, right? If I'm scaling one more, we're supposed to still be good. Oh, 83. So now, scale-up kicked. So now it's calling the provider. The provider is calling, so the provider knows that we're using Azure. So the provider is going to call the provider Azure classes and going to scale. So the way it works on Azure, you remember I talked about the VM scale set. So it's supposed to scale the correct one, which is the DCOS-Mesos SL for stateless. And we're supposed to scale, if I'm doing instances, so it's creating instances here, and it's going to scale. And the cool thing with the VM scale set is going to bootstrap the Mesos agent and everything, everything. And then after a few minutes, we're supposed to see three more VMs here with the stateless tag and so on. And then it's going to be able to deploy. So here, we're just at 80, but the ID, let's say, we scale to something like 10. It's going to deploy. We have six instances, right? So it's waiting for more. So the ID is going to scale to three other nodes. So that means I'm going to have, or two other nodes, sorry. So I'm going to have four CPUs available, four more CPUs available, and then it's going to be able to deploy my application until 10, and so on. So it's an easy way, actually, to scale. Again, stateless application, right? Just web app. And the cool thing here, it's supposed to also scale down. So when we're going to reach, like, under 20% consumption, it's going to do the same, the opposite, actually. It's going to scale down to, from six or eight, I don't remember how many we're supposed to have, to two less, and so on, and so on, right? So it's just a cheap way to save money on Cloud provider, right? And again, stateless application. Like I said, autoscaling is very complicated. I don't know if you're about that. Microsoft, we work with a company called OpenAI. It was more on Kubernetes, but just the story about that, it's we developed their own way to autoscale GPU training. So OpenAI, I'm pretty sure you're about that. So the player, the guys who played Dota 2, and a machine beats the best player in the world at that game. And yeah, everything was hosted on Azure, but the story about that, we developed their own autoscaling model based on a bunch of different scenarios, like networking, storage, and everything, everything. And I asked the generating team why we didn't, like, not open source, but include that in the product because it's a good story. It's supposed to be cool or so. Maybe gonna help or provide other customer. It was too custom for the needs and this is why we engage the conversation about that. We also have the same kind of code for Swarm and Kubernetes on open source set, actually, but again, it's still stuck to one kind of resources. On that case, it's CPUs, but maybe you want to scale for GPUs, for example. GPUs make sense also because it's really, really expensive. So maybe we want to be able to scale GPUs, launch a training, right, and then shut down of the VM. So yeah, that's just the concept and the idea of that. So let's see. I tried to talk to just to wait before the... Okay, C scaling, let's see on Azure, so it's creating, running. So I guess now it's bootstrapping like all the Mezos and DCS bits. As you may be not ties, it's the way that I did that for now, it's just a docker code. It's really ugly, running on a master, right? But it should be really easy to push that and deploy that on a cluster. And the fun thing also that I did I also create a universe package. So normally, yeah. So basically, here on the package, it's basically the same thing that is going to ask you for the service, I mean the provider name, the scale threshold and so on and so on. For now, we only have just Azure, but it's the beginning of the way to run that inside DCS. For now, it's again docker on the master, really ugly, but I'm pretty confident that it should be able to work also on the inside the cluster. Let's see what we have here. Okay, gonna wait anyway. Do you have any question in the meantime? Who is doing auto scaling right now on DCS? Okay, which way doing that? Or so custom code, I guess, or? Okay. Sorry? Okay, based on, so you're, they say they're running their own code, right? To scale, based on what? Still based on resources available on the cluster or? Yeah, it's based on, we all scale services and clusters. Okay. Dependent on services we scale on a metric that the service owner asks for and clusters, then we scale based on CPUs. Okay. Well, yeah, we choose CPU and memory and choose whatever's worse. Yeah, do you scan, okay. But it's still pretty dumb. Yeah, it's tricky, right? Because you get into the situation where you're tracking a lot more things than just CPU and memory. Oh yeah, probably. In marathon, for example, what defines whether a task is waiting or not depends on whether it can get an offer with all the things it needs. And those could be CPU, mem, GPU, but they can also be like attributes. So it could be like tags for a specific OS or tags for a specific region or something. So yeah, our autoscaler is still kind of dumb. It will handle CPU memory or other things like that where we can just scale on the worst one. Yeah, exactly, and that's also a good point. Why people use, I mean, one of the reasons we're using public cloud actually is to be able to also to scale on different region, right? And sometimes we want to scale on different region, not only on Micas Westerrop. So it's also a good point, something that you wanna watch. And again, just not CPU. If you check the code, it's only maybe 200 line of code. It's really, really simple. But again, the idea of the session because it's end of the last day, right? Just to share again, just to give some ideas. And the fun thing, I didn't fight any open source code about that. So I thought it could be fun just to at least publish something and people can start from that because in my case was the case with my customer to start from that. And they kind of did the same thing, but custom, they not use my code. I mean, that was the deal, right? But they doing that on OpenStack and Azure. So the public cloud that they are using OpenStack and they using Azure on the public one. Yes, so our code is open source. But it, like you said, it's a very specific problem to your organization. I'll support AWS. I mean, people would be free to try and use it, but whether they would get it working without our infrastructure is questionable, I guess. Yeah, yeah. Cool, thanks for sharing. So yeah, in the meantime, yeah, in the back there. In the meantime, I have a new guy here. No, that's not the correct one. Yeah, it's coming, actually. Yeah, in the back question. Wait for the mic here. And please share, guys. Like I said, it could be just if you wanna share something about the topics. That was also the idea why Mesosphere asked me to do this tour because I start and engage on that topic, but the idea is also to share and if we have multiple feedback, we can also talk with them with Mesosphere on the topics, right? So yeah, question? Yeah, my question was a relay.  Yeah. So meaning that, okay, it might be interesting for if you have very, very large stateless load and you want to split your cluster into two, but sometimes it's more maybe mixed on that or do you have any ideas? Yeah, so yeah, that's a good point here. It's really, really straightforward reading one tag and just do the math on that. Actually, on the report, I think it's published, let me check. Yeah, future resource tracker. So it's another branch. So when I was motivated, I started this thing. It was kind of, it's kind of the V2 on that. So be able to track all the tags that you want to watch, actually. So just not one, but be able to say I want to watch like CPU or mem on CPU and mem CPU GPU, but also I want you to tag like, so I want to check the tags or the stateless one, but also that tag. So maybe on that way you can combine, I mean, there's just something in mind, right? But you can combine, okay, that node or VM or VM scale set or whatever is going to add a stateless tag, but also, I don't know, GPU tag or you can have custom tag, right? And do the math also on that one, if you want. Yeah, but my point is more about, in order to do that, you have to have strict conditions regarding resource allocation on the mesos cluster. For instance, no stateful node, no stateful application will install on a stateless node.  So basically, you are splitting your cluster into two parts. Maybe it's not a good practice, you're right here. And the thing is, it would be probably possible to explore, for instance, the tags on each deployed node to see whether an application is stateful or stateless and may I destroy this node, for instance, but in this case, you have another issue which is fragmentation. Yeah. Yeah, I got your point. You have to repack the stuff and... I got your point. And oh wait, that just confirmed the point that I said that custom, there is no magic way to autoscale, right? It's just a way, and again, the easier 45 minutes way to do that. But yeah, totally agree with you. On that code, I can add more, let's say, smart way to scale, like reading the, I don't know, the variables or whatever I want or the name. But yeah, I'm totally agree with you with that. I mean, fragmentation is one point here and maybe not the best way to do that, but again, 45 minutes talk. Are you doing autoscaling? Yeah. No, but I did similar stuff for OpenStack long time ago. Okay. With migration of VMs, it was easier because you could... Yeah, yeah, yeah. Yeah, right, yeah. Just a few remarks. Yeah. The first one is, there is the Marathon LB autoscale project, which aims to scale application on top of Marathon. To me, your project is a good extension of that one because basically, when you're blocked, because of resources proposed to scale you up on top of the message cluster, you can act at the underlying level, meaning that you can increase your cluster size. Yeah. Because you're blocked in increasing number of instance due to resource leak. Yeah, yeah, that's a good point. And also, the thing on, I mean, I know where's Azure, right? I don't know about Amazon and other cloud provider, but the thing on the VM scale set, the idea of the VM scale set on Azure is to be able to automatically autoscale, actually. So, you have this magic switch button to, okay, autoscale for me. But the problem of that, it's Azure gonna read the CPU construction of the VM by itself, you know what I mean? It's not gonna be able to read like Marathon or Mezos, right? This is why we need that tool. And yeah, to tell you agree, I also saw this project. And again, I'm not in the engineering team. That's also one reason. I'm not in the Microsoft Azure engineering team, right? My work is to engage with customers. So, unfortunately, I don't have time to invest a lot of time on that project. I would love to. But yeah, that's a very good point. Okay, and the signal remark was, our intuition so far on crypto is that you have to gather more business metrics to. Start really doing autoscaling. And if you want to push the thing really far, potentially you have to apply some machine learning stuff on top of that. Meaning that you have to understand what's the pattern and to act upon conditions. Yeah, and we know that executive people loves dashboard, right? Metrics. So yeah, that's agree.  Just bin packing. Yeah, bin packing. And that's, I mean, that's awesome. I mean, the concept is awesome. I'm pretty sure that executive people would love that. But it's, I think it's pretty tough metrics to which, right? To gather, I mean, to have the correct math on that and reach the correct. Yeah, exactly. If at some point we are able to do that for sure you have to prepare this operation carefully and also have a lot of insight through the business and your applications. Yeah, and I'm curious, which tool, I mean, or people open question, which tool are you using for the metrics? Are you using Prometheus or, I don't know which, which, yeah, Prometheus, yeah, here? Or the guys, no? Any, and do the row way. No dashboard, then. Okay. And we also ingest a lot of logs and stuff into Splunk. Okay, yes. And that provides some useful metrics as well. Okay, cool. Yeah, so that's it for me guys. If you have other thing that you wanna share or question or whatever. No. So if you wanna reach me, my Twitter, it's that one. Or I think you're gonna be able to have the slide anyway, but if you have any question. And if you are using or planning to use Azure, let me know. Again, no worries, I have nothing to say, I'm not in the sales part. But if you have nice technical challenge on Azure, let me know. I'm not willing to come and help you with awesome people from Microsoft. Because what we want and what we like is challenges, actually. So that's just the idea of my team. It's just to be challenged and just because we're gonna be challenged, we're gonna have the tricky scenarios that we never see before. And then it's gonna be the better way to give feedback to the engineering team and to have the best product on the market. So that's how we work on my team. So thank you very much for your time guys. And yeah, hope to see you after.