Okay, welcome welcome everybody This is our presentation on the get me a network feature that was added in the newton release which is Given we've already released okada, and we're working on pike. It seems like I mean talking about a thing that we released a year ago is Sort of odd, but most people are just getting upgraded to newton. So timing is actually good I'm Matt rudeman. I am Worked for a while way on the nova ptl for the last three releases And I am Armando Miyacho. I work at Susan now, and I've been the newton ptl For the mitaka newton and look at the releases So today we're gonna go over what the rationale for the feature was basically use cases what the problem was What the proposed solution was the different community effort involved because it was a couple releases going and a lot of different people involved different projects between newtron and nova The test methodology how we came up with doing the testing the integration testing Possible future enhancements Armando is gonna attempt a demo a live demo and then questions if anybody has any hopefully So let's dive in with the rationale So you see here on the left of the screen a clueless user with a laptop and trying to boot his own first VM in the cloud and Prior to to get me a network He would either he or she would either Start a VM potentially with no net no networking at all or he would have to Basically get a good understanding of how newtron worked and provision newtron Networking building blocks in order to provide the VM with a way to to the cloud or to the internet and to To other the cloud resources so In reality what needed to happen was that again the cloud user in order to get networking to their VMs needed to get to Intimate knowledge networking knowledge And how newtron worked He or she needed to create a logical network for tenant isolation and on that network You needed to provision an IP space by means of a subnet and if the if then network If that VM needed to go out to the internet and then back you needed to create a router provision the router attach it to a public external network and so on and so forth they obviously led to frustrating users because That was obviously a multi-step process There ought to be a simple way to do this so the very high-level requirement was how do we Take that mess and automate it to make it easy and That's what get me a network does the operator performs a one-time setup With some defaults and then the user gets a network provision when they boot a first VM within their project and then he's Wooting I guess I mean that person doesn't look like you a little bit Yeah, I don't wear a sport coat though So the solution with on server create what we basically do is if you don't already have a network available Nova then works with neutron to see if there are some You know minimum requirements if we can actually auto-allocate a network topology If the news if the user doesn't have one then we tell neutron to create one Any other boot request after this basically gets the same network topology So this is a one-time only per project unless you delete everything But it's created the first time and then after that Nova will ask neutron for available networks It's already there and we'll reuse it We should note that this doesn't automatically give you a floating IP though There's good reasons for it will will show them in a bit So it sounds simple enough, but it took us about two years to get this done So in this slide we're outlining the timeline. So this this You know, we had the proper discussion back in the Vancouver summit in in 2015 again it's about to be two years now and We achieved the rough consensus in the in the room when we went went back home we worked on on the neutron spec and We start so the obviously we in that spec outlined a couple of strategies implementation strategies and ways to deal with with the auto provisioning problem as stated in the Vancouver summit And then implementation, you know kind of stalled for resource constraints reasons that I'm not going to digress too much in you know right now and But that said in the mitaka time frame we managed to resume the work and Achieve Further consensus with with the Nova team and the Nova mid-cycle that was held in January in 2016 in Bristol And we were able to complete the fissure on the neutron side in much doesn't 16 in time for You know in the mitaka official release at that point basically the ball was back into Nova's court And we said you know now it's your problem you you you get it from you know to the finish line and That's what happened. I mean So the novel team got together they put together a spec outlined what the strategy was in order to describe what the user experience needed to be like when dealing with the API as well as the common, you know the common line and you know might put many hours during the weekends and and and nights and the future got implemented in time for the Newton release and Throughout the integration testing. We kind of like ran on doubt a few a few issues that There were kind of like overlooked on the neutron side But we managed to you know get the future Tested like and went I was gonna add that During Liberty there was actually a lot of mailing list discussion about a lot of this Monty and J Pipes specifically had been talking about a lot of the sort of end-user requirements for this So this wasn't I think it's important to note that this wasn't just Nova developers and neutron developers saying hey We could write a bunch of code to do this thing and not really knowing if any actual end-users care about this or would be using it It was really driven by Mont we said at least if they know that we usually say well, how would an end user care about this? We'll go to Monty because Monty's got the shade with you know 50 different public cloud counts And we say for the UX on the end-user design. What do you want to see out of this? So there was a lot of end-user input on how this was done and design going up into the specs Yeah, and I mean from from a from a time standpoint Some we argue that actually took quite a long time You know roughly two years to get this implemented and this wasn't like overly controversial as a matter of fact You know when we go into You know into the neutron Like side of a side of the house there was some initial pushback and actually the pushback was mine because my main concern was Okay, now if you're asking me to do the provisioning a multiple steps at once You know atomically and in a potent fashion now you're putting an awful lot of you know constraints on on the implementation And potentially you we may affect the ability for neutron to to cope with load And I you know I was initially like reluctant to the idea of adding that much complexity into the code base But then obviously, you know the rationale was there and we just had to make you know, we just needed to again Work hard in order to pull that off and So okay, I mean I put this the spec in there for You know for reference But I mean even though there was an awful lot of like complexity to deal with on you on neutron side We were able to rely on on a building blocks that were already available in the neutron system Such as subnet pools and an external and default external network. So what? What subnet pools do? If for some of you who may not know about them It's a way For the operator to specify a much larger like pool of addresses that can be used to fetch IP ranges from when allocating tenant networking So rather than I'll force the tenant to come up with its own IP scheme By means of a default pool a tenant can say I want an address out of this pool and you know an IP scheme gets generated from it So the workflow I mean the way we went about implementing this from a neutron side is that then the operator has to come up with a you know with an enough large default subnet pool They may you know be IPv4 as well as IPv6 that he or she you know is confident that You know it's not going to get exhausted throughout the life of of its cloud. I mean it kind of can Things get complicated if you get to a point where you're you're the subnet pool gets exhausted then You know you'll have to Massage things a little bit So you end up like marking a subnet pool as default again as the Subnet pool to fetch IP addresses from you end up choosing a public network the one that you use in order to allocate your floating I think you're you know You're the ones that you're using to get VMs out to the outside world or the internet you mark that as default And those are basically the two Decision points that the human being makes on behalf of the neutron deployment so that the reason deployment when faced with a request of Provisioning a topology on the user's behalf In Newton knows, you know what what resources to use during the boot phase then Neutral simply takes you know goes in in the default subnet pool and Pulls up an IP space it creates a network a subnet rather an uplink as I showed you in the in the earlier slide and Returns the network ID to Nova at that point Nova has everything in its to do in order to proceed with you know with the Pool process and you know give a VM and a virtual nick so on the Nova side as As Armando said in Mataka neutron delivered their API that delivered their changes in the Newton release Nobody had really picked this up. I guess there wasn't really a Anybody already planned to work on this and I think it was just like one day in IRC we were talking about Well, they've already got this site this API available over in the networking service What is it going to take to use this thing and we sort of talked about it for I don't know a few minutes and I thought This doesn't seem that complicated. I'll start writing a spec. So here's the link to the spec. It's actually It's actually pretty detailed But I I generally go overly detailed in my specs But as I was going through this there was a lot of the interesting parts of this was when I started looking into When I started looking at the code and Nova and how it actually works now the funny thing is We found out that there was this weird case that you can get into where if you don't actually have a network available Nova doesn't fail. You just get a VM with no address no at no networking Nothing and we thought well, is this a is this a bug shout? You know, should we start failing if we failed that would be an API change? So let's not do that But are there actually use cases for people doing this thing actually specifically not wanting networking when they create the server You can attach it later There's an API in the compute service to attach a network later But it just seemed weird to us that you would create a VM with no networking to start So something like that drove a lot of discussion in the mailing list and how do we handle this? Do we actually specifically say in the API that if you don't want networking you say that you don't want networking? That drove the We were thinking about well, should we make defaults in the API? Should we sort of assume behavior and we just eventually came to the conclusion that Assuming how the user is going to use it as a bad idea. We should just be very explicit and specific in the API this is another case of We don't a lot of the problems that we have is Designing things as we don't really know how users are using things. We don't know users are using which API is and how they're doing them so We try to be very explicit in this case Another thing that came up was Nova supports rolling upgrades So rolling upgrades in Nova means that the control plane can be talking to the prior version of the compute and Since the compute is what's actually allocating the network When we were doing all this in the control plane We needed to know we could be talking to a mataka compute that has no idea that the user is actually requesting this specific thing So we had to build that into the code and there's act Nova actually has some Metadata built into it that we know what the versions of the services are and we can make decisions in the control plane Based on what level the compute is So really the way this works is you you don't auto allocate until all of the computers are upgraded to the level of code That understands this type of request As I sort of touched on with the the nun case is The boot request today takes a dictionary and it's got a either a port ID a network ID or a fixed IP address Or some sort of crazy combination of all three Which every time I have to look at how this works and what's actually required in different cases It's just it's confusing So we were thinking well the initial the initial draft of the spec said well, we'll just say They provide an enumeration for the network ID And eventually kanichi actually kanichi omichi was reviewing the spec and he said what if What if we just said you either if you want the specific stuff? You provide the dictionary as you have before if you want a specific network or a specific port you do that If you want the very simple case, we just have an enumeration You either say I do want networking automatically created for me or I don't And so that's what ended up being in the api Um Before this microversion if you don't specify networking, it's Automatic so we still have we still wanted sort of that same behavior, but the api is explicit So with this microversion you still have to specify Whether or not you want auto or non you cannot specify Just no networking without providing this network key There was some pushback on that in the development mailing list about This used to just sort of work automatically before and are we making it more difficult now by making people actually be explicit in the api request We thought if you're an api user You are probably being very specific about the stuff that you're doing anyway So the way that we massage this a little bit was we said if you're your cli user if you're using the command line You want it to be simple. You want to make same defaults So in the cli if you don't specify anything we still default to do auto allocated networking Another key thing was that nova doesn't do retry of this So when nova asks new neutron to actually auto allocate the network topology If it were to fails for some reason nova doesn't retry And that's really based on trying to make sure that everything is atomic and idempotent over on the neutron side Which when we get later into the test discussion that's drove a lot of the test um methodology So i've already talked a little bit about the workflow the workflow is basically it's a micro version So anything over 237 to do this The network's key that's where I was saying if it used to be it could be a dictionary or it can be an enumeration If you want auto allocated networking you specify networks auto Nova will check to see if all the compute services are updated to the latest level to support this If not it still goes back to the old behavior, which It won't auto allocate a network if there's one available you'll get it So it for anybody that's been used to how this has always worked. It's really no you don't lose anything You just don't get the new stuff Nova api will validate that if there's a network already available to the project We'll just use it as before if not we check to see if the defaults that the operator is supposed to have set up Has set them up if not then we have to fail the request because we can't we can't perform it Down on the compute side Same thing basically if there's already a network if you just Created dev stack dev stack gives you a public network. You just use it No problem. Nova won't tell new trying to create anything But if there's not if there's no networking available to the tenant already Then we ask new trying to create it If that's if it works we get the network id back we create a port on it if it fails we don't retry because Basically, this is a global failure if neutron isn't set up to handle this It's not retrying to a different compute isn't going to work So we fail and we put the instance into error state so the testing the going back to the Atomic and item poet in nature that we wanted this to be in the neutron side is When we wrote the tempest test The none test is easy. You basically just say I don't want networking Make sure that there's no networking. That's an easy test The difficult test was making sure when you start out with no network for the project That one gets created But just one gets created and it doesn't fail if multiple requests are coming in So the key point to this and I think when I wrote when I originally wrote the test I was creating two servers at once at the same time But that didn't really there was this weird little edge case where A third server three servers getting created at the same time was really what made this sort of fall over On the original implementation on the neutron side Yeah, and that cost like writing all the code was pretty simple Once we figured out the design it was really the testing that was like, oh look this Three servers two is okay. Three makes it all fall over and start burning Um, the reason is that the first two servers will come in concurrent and they'll see neutron will say There's no networking for this thing. I'll start creating it Eventually it figures out Wait a minute. There's only supposed to be one of these it rolls back the first one The third server coming in comes in After the first two and then it sees Something is getting created. But there's two of them. What am I going to do? There shouldn't be two of them And that's the whole network ambiguous error if you've ever gotten the network ambiguous error booting a server Where nova just throws up its hands and says, I don't know which one to pick you didn't tell me I Whatever I'm going to fail So based on these failures, we ended up having armando worked on a bunch of Actually hardening the neutron side of this. I don't know if you want to go into details. We ended up basically leveraging admin statuses on on networks where when when neutron does the provisioning Again, since the provisioning actually involves a number of steps that Cannot, you know for what for a number of reasons happened in an atomic fashion Because there is backhand coordination involved if you're using You know different sdn controllers and whatever You need to basically lay Atomicity as a semantic on top of the existing plug-in api that neutron implements and basically we did lever, you know We did accomplish that by Creating, you know networks in disabled state and turned the the admin state back to you know back to enabled Once we were happy that only one network was available was being was being provisioned and That was it, you know that that allowed us to work around this this particular corner case And I will say Everything in the everything in ci is gating on this test This is not a scenario test. This is not a slow test. This is something gets run on every patch So thousands of times a day so once we got this worked out. This is actually Gating on everything from ever actually merging. So it's pretty solid So, you know once we go to the point then it's okay. The feature is done done on the nord side on the neutron side what's next and Actually, one of the reasons why we're here is and there is also a forum session about about this develop and tomorrow It's you know get people interested in this feature trying it out because it doesn't do everything right? It doesn't address every possible provisioning case that the people may come up with In fact, as Matt mentioned at the very beginning of this session We don't auto provisioning floating IPs and the rationale there was okay If we have like dual stack deployments, so we have ipv6 deployments only Actually, we don't have floating IPs or we don't want to get into situation where you only have ipv4 Addressing you don't want to you know necessarily allocate floating IPs if a user is not interested in using one ever So we kind of like left it aside It's enough you know enough of a of a step a simple step that can be left to the end user on the other end we don't allow the You know the the neutron system to figure out which kind of external gateway mode to associate to the router A router is as you can you know can can do s nothing or not and We use the default which is s not is enabled by default at the same time We don't you know we we provision a very like explicit Network entomology which involves a logical tenant network, which is typically VX LAN That's backed by a router that's connected to an external network What if a system does Rely on provider network, you know provider VLANs alone. Those are not quite Addressed yet at this moment So I think you know words I can do solely so much so if you get you know Two minutes left. Let's see. Only two minutes. Let's see if we can pull that off Do I have to hold this? Right, so what we have here is dashboard. Let's see if I'm still logged in Oh, yay so What I want to do here is show How this works in practice So I'm going to I'll try to type very fast See so right here. We have a router external network associated to the tenant No demo tenant And we're gonna provision here Two servers And we don't specify any networking So to be to be told we started five minutes late So I think we can perhaps overrun a little bit, but let's see what happens Uh, so we did so what I did here boom We haven't touched anything except like Launching two servers without specifying any networking. What happened in the under, you know on the back of the screen at the terminal is two Auto-allocated networks have been provisioned an ipv4 and an ipv6 network because that's how I configured my dev stack that Are connected to the public external network now My vm should go and get attached to those networks. So it's still taking some time But eventually it should it should do that and it's a live demo. So I Left to see whether it's gonna work as expected We also found out a few hours ago this morning when we talked about this actually when we went through this dry run a couple weeks ago on a hangout Armando was using the nova cli with nova boot Everything worked fine this morning He was using open stack client And it was an auto provisioning the network and we were trying to figure out You know, is your dev stack actually running like, you know trunk code and What could be going wrong with this and we then I remembered that open stack client the cli doesn't Default to the latest of it. It doesn't do api version my Negotiation for the cli which nova cli does So if you're using open stack client by default, you're not getting the micro version that's gonna do this thing automatically All right. So everything is good. Life is good. The demo is behaving. Let's delete those servers and and now We want to try different deployment scenario where Let's wait these servers to go away So again, as we've seen right now The user hasn't done anything Except running the server and the networking provisioning has done on on his on his own her behalf The m's are gone But what we can do now is that we can use another clever command that was introduced at time in the in the mitaka time frame which is purging the the tenant deployment so by doing Neutron purge and that's the you know the tenant or project ID What Neutron is going to do is going to wipe out all the networking resources for that tenant so The task that prior prior to this command would require the user to script Deleting you know deleting the networks the routers and security groups and so on and so forth is done at a push of a single button So you should see that network. Yeah, which we had to do that in tempest and it was right It is not fun to code that up. It's a client side. It's a client side orchestration It's not something that actually we have actually there is there is a way to Delete the auto the auto allocated topology Neutron. So you have an api endpoint that takes the delete verb Uh, it's just not exposed through the api binding So if you were to talk directly to the api endpoint and you know, you could do that actually So the public that the public network is a rather external network created by the admin So what else I wanted to show you now is to create a shared network And that's obviously visible to all tenants and yet boot service on them And you'd see that actually no tenant networking is provisioned whilst the buddha server or servers But the shared network available to that and another project that the is going to be used in order to plug the bm So you can see, you know, I'm actually going to do that as admin I'll create a network and you know in an ip range and then I'm going to flip back to the Demo project or tenant and I'm gonna boot the vm. I'm gonna boot the servers. So let's do that and see what happens So you'd see now that The shared network gets provisioned under the hood Well, I will buy it by the tenant and when I boot the server servers, they're gonna plug into the shared network So give it a sec. It's not a very beefy dm and it's running on my laptop There you go. They're just plugged Nothing else is required So with the 10 seconds we have left does anybody have one question You could shout it out and I could repeat it if chat maybe mark If you could use the mic or we would just replay the question. I'll just replay it. Yeah Is neutron purge for auto-allocated networks? No, every resource provisioned by the tenant That's owned by the tenant and and Correct. So and the new you know the admin can also go and wipe any tenant or project environment that he cares about Or is pissed off by All right. All right. So I guess that deserves a round of applause.  That's an amazing demo that didn't fail Thank you So give it a try give us feedback again. There is a forum discussion tomorrow I should have actually added the note here, but I was lazy enough to not do that and Thank you very much for for coming here and listen to us. Thank you


Welcome back to the review and today I'm gonna take a look at the making of one small step. Well, let's check out the making of book. This is the front, there's nothing in the back really, small spine, but that is the front. And there we go. Xiaofu used to be my students, and I don't say this in terms of like, he learned from me. He was already really good when he was in class. So it was, I'm not surprised that he went to Disney and has now is now CEO of TECO Studios. It was abundantly clear that he has so much talent. It was great. So it's great to see him flourish. But anyway, me dropping names, but that is the forward. And then you got the studio photo here. Oh, there you go. He was in my, he was in my class. Dude, that's awesome. Xiaofu right there. Research trip. I would love a research trip like that. Come on. Here's a story. By the way, spoilers, if you haven't seen it yet, I'm just gonna let you know there's spoilers. Early pitch as it says here, you know what this is. This is a flip through. Cute. Always like seeing storyboards and explorations like that. You can see the whole thing right there. As I said, spoilers design are super cute. Love it. It's very cool. Definitely pay attention to the change of hairstyle. She gets older, recurring themes. I love this. I don't know why this fascinates me so much when you have a model and then you have drawovers with text. There's something like, ooh, this, this screams learning. I don't know. I don't know why. Love this though. This is great. Great to see this silhouette treatment. Your characters from model render to the actual look in the short, which is really cool. The body mechanics of her going up the stairs and all that stuff is also really great. Super cute with the shoes. I mean, I really have only, only glowing words about the short. Absolutely. Check it out. And this is why I love that this has a, a making of book with all that stuff in here where you got the models, you got reference footage, you got, you know, the different elements and layers as to how they did this. Actually, I think Andrew tweeted this out a while back. I'll put the link description as well where you see that or how the hair is animated. It's not simmed from what I remember. Super cute. Come on. It's just so great to see this. I love that. It's just inspiring to see how it starts and how it ends. Again, more spoilers rigging. Yeah, I am. Under the hood as it says here, but it's cool to see full insight into the pickers, how many controls they have. Of course, don't use all the controllers. Breaking down the hair rig. That's what I was talking about. That is so cool. That's the cheat and that's the look of it. So neat. Lots of controls on that box, which you need. You're going to deform it like that. Probably my favorite part. I'm biased, but I do love animation. There you go. From storyboards to writing manics to the final version. There you go. I look into Maya scenes as well. There you got the team. So cool. Technical animation. Yeah, it's so neat. There's so much awesome stuff in there. Lighting and compositing, which is huge because the look is really, really nice. I think I remember seeing this back when I was at ILM. They showed it there in the big theater, which was fantastic. There we go. Got some beauty shots there. They're awesome. Of course, different kind of mood depending on what's going on. I love this when she continues with that. It's so great. And then at the end, she makes it. Beautiful frames. Come on. And then we have course effects. Also really nicely done. Love this. Should we spend any time on the animation minute or anything where I go through 2D effects? I love it. And yes, the sound and the music was also great. See that? I love that stuff. If I wouldn't do animation, I would do anything with... That sounds like I could just do what I'm saying. If I could magically change my profession, sound design and that type of music, more sound design. But I see this and I just, to me, these are cool instruments where you can tweak things and just... It's a different kind of emotional manipulation anyway. Instead of the visuals, it's through audio. But look at this setup. I don't know. This is to me just... I nerd out and I love it. Team collaboration. Lots of famous faces in there. It's cute to see a personal touch to all of this. And there we go. Towards the end. Super cute. One small step. There you go. The end. Super cute. Highly recommended. Again, if you haven't seen this short, you should absolutely watch it. It is really, really well done. And all the work they've done since is this really high class. So I can't wait to see more of what they're doing. If you like this and you want to see more, feel free to subscribe if you want. You're not missing any of those uploads. As usual, like and subscribe. Pitch at the end for the algorithm, as some people say. And that's it. Thank you for watching till the very end. If you're still here, thank you for taking the time to do so. And hopefully, see you in my next upload.


ԳՆԳՅԍՃ, Ե՝ԿԜմԿՅ, ԊԷՍԵԱսլ, ԲԿՎԴԵՄԿԱԷՈ 친enin 11 amra mathonzef Beause water supply,沉 waves,Our needs can claims." We are not making any surface huge because of lack of water supply. There is no lag behind and water cried well. One is easy cleaner than that. May艶2 также look preferable for us to avoid. According to India, where did people come? When we tillers the People Kabir life the upper part of the river. There is practically no knocking on the door.


What's going on and welcome to the MLB DFS Q&A. My name is Tom Vecchio. Every day I'm here at 4 p.m., taking your questions about the Knights MLB Slate. We have a four game slate tonight. It locks at 805 Eastern, not 705 805 Eastern, not getting that extra hour in for some research. And hopefully more important than research and update when it comes to the weather tonight, specifically for the Cubs and the Brewers. This game at Wrigley Field is set to have plenty of rain tonight, this all according to Kevin Roth on Twitter. He's a fantastic follow for the DFS industry when it comes to weather and weather issues specifically for baseball. We are dealing with a lot of weather, a lot of rain tonight for this game. Now, he's saying that there's a late start at best. There's gonna be a ton of rain, but if they do play, it's gonna be warm and humid, winds blowing out 10 to 15 miles per hour. That's a good bump to the bats. And then of course, as I said this morning on the solo shot, winds blowing out in Kansas City, another bump to the bats there, which is good to see. So a four game slate, which could turn into a three game slate, depending on whether or not the weather in Chicago cooperates for the Cubs and the Brewers. So that of course is something to pay attention to. We don't have too many confirmed starting lineups as of now, only the, I think the Brewers out will circle back on that. Starting off, Sivan, favorite stacks for today. That's what he's asking on YouTube. Tonight's slate, we should be seeing some very chalky teams. We have very, very heavy favorites. We have four heavy favorites. We have four pretty large underdogs. We should see all four favorites as the chalkiest teams on tonight's slate. Looking to the Yankees and the White Sox is probably overall the safest option. All things considered, yes, the Brewers are in a good spot against Alec Mills, especially if the wind will be blowing out, but ultimately we don't know if that game will in fact be playing. So that's why, aside with the Yankees and the White Sox, if we flip to the, some White Sox hitters, of course, they will be getting back, Luis Robeir tonight. He was activated off the 60 day IL and he comes in at the minimum salary, $2,000. I mentioned him this morning on the solo shot. If he's gonna be in the lineup, but just really matters where in the lineup, hopefully we're looking at middle to top of the lineup, which will be great to see. He's minimum salary and that's something we absolutely need on tonight's slate where there's just such limited value and ultimately most people will be paying up for either Joe Musgrove or Lucas Gilito, who are the two best pitching options on tonight's slate. And that's the order. Ultimately I'm gonna be looking at them tonight. We'll be taking Joe Musgrove number one and then Lucas Gilito number two. Now, I think Robeir is probably gonna be one of, if not the chalkiest players on tonight's slate. We should be looking him as a solid overall option. Of course, we're gonna be looking to Jose Ebreu as another fantastic add to the White Sox stack overall. Gavin Sheets was sent down to the minors with them bringing Robeir back. So make sure you don't have Sheets in your lineup. Let's just double check to see if the White Sox lineup has been confirmed. It's not confirmed yet. So we'll look to Luis Robeir, of course. We can certainly add in shares of Tim Anderson and in some Andrew Vaughn. You want that potential power upside after they get past the Ruddy's, which would be good to see. So the White Sox are leading off at number one. Let's just flip to some of their options. Overall, not that expensive. They offer some clear value with Robeir $2,000 and then I'll be filtering in plenty of shares of some of their power hitters. The Yankees would be the number two stack that I'm looking on tonight's slate, right here. Obviously plenty of power upside, specifically from their righties tonight with the wind blowing out to left. That's something we want to see, but we also should be focusing in on Joey Gallo. He's not on the split right here. He hasn't, I guess, will change the filter for plate appearances. Hasn't had enough plate appearances. Obviously a strong ISO from him in 26 plate appearances versus righties as a Yankee, of course, that power upside is always gonna be good for him, regardless of there's wind blowing out or not. So Joey Gallo, Aaron Judge, Stanton, all gonna be super, super popular tonight. Now the Yankees lineup should look a little bit different tonight because of course there's no Rizzo. They got Luke Voitback. Labor Torres went for an MRI after yesterday's game and we should be getting value with again, Kyle Higashioka getting a start at Katcha because Gary Sanchez is on the COVID IL. So we could be getting a bit of value with the bottom portion of the Yankees lineup. Ultimately, we'd like to side with the top of their lineup and pay up for what is clearly the home run hitters in their lineup. I will say that Luke Voit, $3,000, not super expensive. He came back from the IL, the other day. Yesterday was his first game back. Yeah, 0 for 4, not great to see, but he does have that clear power upside. Best type of stacking method today, Saban is asking on YouTube. I think tonight's slate is a slate that I'll go mostly 4, 3, 1 and 4, 2, 2 tonight. I normally go 4, 4 as a good portion or a good percentage of my stacking allocation, but this is the kind of slate where it's a small slate. This is where I'll differentiate and jump into a little bit of 4, 2, 2, which I think is certainly viable on every slate. Whether it's 10 games, 15 games or four games, I think going 2, 8, 4, 2, 2 could work tonight. So I'll use the White Sox or the Yankees as a primary stack and then if the Yankees are my primary stack of 4, trying to get two hitters from the White Sox which would ultimately include, I would almost certainly say Luis Robeiro because I wanna be spending up for the Yankees full stack, get Robeiro at that low salary, get that value and then probably look to add in a few more Padres hitters. It'd be great to have some Brewer's hitters in there, but we're still waiting on a weather update in fact that game does play. Short Slate's Tyon to be contrarian since everyone will be on Musgrove. That is totally, totally an option. Also the, I would say a slight amount of salary relief that James and Tyon brings at $8,100 is totally, totally something that you want in your lineups and that because you can pay up for Tyon plus three hitters from the Yankees. You can go to a full Padres stack at home. Obviously plenty of home run upside for them and they can be quite expensive up the top. Grisham, Cronenworth and Machado are certainly expensive. So yes, absolutely go to Tyon today. Now I will say I do have interest in Kansas City. Some of their hitters tonight, let's flip to Kansas City quickly and then I'll bring up Tyon right here just to give you a little comparison. So Tyon is allowing too many home runs this season and that's something that we can be taking advantage of with the wind in Kansas City. 1.97 home runs per nine to lefties this year is certainly not good just over one home, one home run of per nine to righties. He's allowing a 51% fly ball rate to lefties and a 44% fly ball rate to righties. We look to some of the power options on Kansas City. Ryan O'Hearn, Sal Perez. I wrote up Perez today on numberfire.com. He's probably my favorite overall a home run call on tonight's slates. Carlos Santana, a hundred dozer, also plenty of power. Injuribin and Tendi hasn't been starting as of late for them he's dealing with some shoulder injury but if he's gonna be in the lineup you could also look to add him. So as much as I'd like Tyon tonight and I will 100% have some shares of him in my lineup build I also am looking to Kansas City again to be a big contrarian because that power upside from some of them against the picture with a 51% fly ball rate against lefties with extra wind blowing out in Kansas City is not something that you want to be passing on. Let's give these an update. Let's hop back in. Do we have no other confirmed lineups? Saban is saying today seems to be a little weird. It is a little bit weird. It's a four game slate which of course small to begin with and we're waiting on major weather information for the Chicago Cubs hosting the Brewers because this game might not even play. As Kevin Roth says, it's a late start at best and he's saying the field could be in rough shape where if it's just gonna be pouring and pouring for extended period of time they might just turn it into a double header tomorrow and then we're dealing with a three game slate where we're gonna be dealing with super, super chalky options, a lot of overlap when it comes to lineups, et cetera, et cetera. So we're waiting on this weather update. If it comes through, hope, I mean it's gotta come through before eight o'clock. I mean it would be like worst case scenario that doesn't come through before eight o'clock. Yeah, so we're waiting on the weather update for Milwaukee and Chicago. Best Milwaukee hitters for today if they play. Milwaukee is right here, we look to their power. William Domus is really, really bringing some power for them after being traded. Rowdy Tiles is also certainly an option you can be looking to. Basically anyone here in the top tier, let's look at some of their salaries for the Brewers. Obviously we've seen Eduardo Escobar be traded there. He's looking solid. The Retinso Cain is back to them. He's been playing outside of his big game yesterday. He's actually been relatively consistent for them. Not offering a ton of power upside like he did in some of his younger years, but certainly an option can be adding in. And really for the spot that the Brewers are in, in a game, again, if it plays that has 10 to 15 mile power wins, like if it does play, this is wind blowing out at Rugly, which we know is so beneficial. I wanna say these salaries are very, very affordable. Christian Yellich is under $3,000. The power that Rowdy has at under $3,000, yes. So if I had to rank the hitters on the Brewers, if that's what you're asking. Oh, I would take Eduardo Escobar number one, Adames two, Abyssal Garcia three, and then it's probably just a toss up between Yellich and Tiles at both at 2,900. So Eduardo Escobar has been super consistent. The, I would say point per dollar value that Willie Adames brings at 3,300 is certainly fantastic. Game stack of the Yankees, Royals, especially this turns into a three-gamer diffuse on YouTube is asking. Yes, absolutely. This game has an over under at 10. I believe it opened at nine and a half or nine and it jumped up to 10. Total, totally viable strategy, especially this is a three-gamer.  You know, we could be getting some extra value in here where, you know, Tyler Wade, right? If Glaber's out, Tyler Wade, I guess could be getting the start at minimum salary now. He's not the ideal add to a Yankee stack, but if you're really looking to jam in the hitters from the top and then you wanna get in some of the hitters from Kansas City, right? Like Sal Perez and Carlos Santana and Ryan O'Hearn aren't overly expensive, but when you're paying up for over 4,000 from multiple hitters from the Yankees and then you probably wanna pay up for Musgrove or Geoledo. Like, what would that look like? If you wanna pay up for just take Musgrove because it's a little bit cheaper, we'll go to the Yankees. You just take some Yankees here, you flip to the Royals. I'm big on Santana tonight. I'm, excuse me, Perez tonight. Like this is not the easiest build in the world, right? Like this is barely 3,000 left per player and we have four open spots. So it's certainly doable. And I love the idea of doing a game stack. You just really capture all those runs, especially if it's the over on 10, which we should see. Favorite one-off at second base, 2K and under. Okay, that's very specific. That's from Kyle on YouTube. Like that's a great question. It's gonna be super specific. So one-off at second base, second base from all teams, 2K and under. Ian Hap, I wrote about Ian Hap on Number Fire. Again, if that game plays, so let me give you an alternative and I'll jump into Ian Hap a little bit. So it'd be Ian Hap and then, I mean, if Tyler Wade plays, he'd be minimum salary. That's just obviously a bit of a long shot. Adam Frazier, Adam Frazier at 2,800 or Ian Hap at 2,700. I mean, Rudin O'Dore is also just as good. He could be bumped up into the lineup, especially if Glaber is out. We could see him hitting a little bit higher. So there's three viable options. Ian Hap, I think is going to be probably coming in at the lowest percentage. So he's going up against Freddie Peralta and let me just bring up Hap stats real quick. Now, there's no doubt Freddie Peralta is a very good pitcher, right? He's coming in with his massive strikeout rate overall. This season versus lefties, 29% strikeout rate was obviously great, allowing 0.87 homeruns per nine versus lefties. Hap's a switch hitter, so he'll be hitting lefty. A 53% fly ball rate is terrible, right? Now, if we flip to Hap, now I said this on my article on Number Fire today about Hap is that Peralta is a better pitcher than Hap is a hitter. But if the Cubs are going to be at lower roster ship percentages compared to everyone else, why are we not looking to take a hitter like Ian Hap, who has a decent 32.7% fly ball rate? This is, these are the updated stats for Hap this season. Yeah, he's at an 18.4% homerun to fly ball ratio with the wind, right? With the wind blowing out in Wrigley. So if this game does play, right? Freddie Peralta is a great pitcher, but if this 53% fly ball rates can be shining through, like homeruns can just fly out, right? And there's nothing he can do about that. So I like Hap as a one-off. Frasier should be decently popular. So it'd be Hap number one of door two and then Frasier. Rod on YouTube is asking on a small split, do you focus more on just playing the best plays or focus on what we call roster ship now? We don't use that word anymore. Just to be, just our company policy, but we use roster ship now. Do I focus more on playing the best plays or? No, I focus on just trying to nail down the stacks to make roster construction work where I'm gonna get exposure to what should be the chalkiest teams and I wanna make roster construction and my player pool allocation appropriate. So I will, if the Yankees are gonna be super popular and it's a three game slate and you don't roster the Yankees and they go off for 10 runs, you're just done, like you're just left behind. So I want plenty of shares of the Yankees. I want plenty of shares of whoever it might be and then it'll work in a secondary stack which could be Kansas City tonight. So it could be Kansas City plus the Yankees, Kansas City plus the White Sox, Kansas City plus San Diego. So that is just the way I go about it. Like I don't focus on like any, like one specific position on slates like this just because it's mostly gonna be about stacks on this. Savannah is asking which game we think we'll have the most offense tonight.  But it's tough not to say Milwaukee at Chicago. Again, if we get an update on that game because Alec Mills, a low strikeout pitcher for Chicago and of course, Glaver is placed on the 10 day IL. We got an updated lineup from both the twins and the White Sox. Okay, so this means he's obviously not gonna be playing. We're gonna see a bump in the lineup for probably Ruben and Odore as I said, we'll probably be seeing Tyler Wade start. So that gives you plenty of value. White Sox, Tim Anderson. Her name is a brave man. Okay, so Luis Robert is batting seventh. He's minimum salary. You would certainly look to, I mean, Robert should be one of the most popular players on tonight's slate. Twins, the twins also should not be popular. I did write up Kepler as a potential under the radar option for his home run upside. He absolutely has plenty of power versus righties. Geolito struggled a bit recently with home run. So I wouldn't hate taking a few shares of some twins players as one-offs in tournaments. But this twins lineup is pretty solid. You could go to three, four, five, seven as a stack. You could just go one through four, but Robert should be popular at only $2,000. So to answer your question, New York and Kansas City is my favorite game stack. Millwalk in Chicago is two. Yeah, as Michael Starr just said on YouTube. Yeah, these lineups are, these are good lineups. Robert makes lineup construction now much easier today. So if you go to this game, Robert in there, you wanna pay up for Musgrove, that's totally fine. You wanna add in the power with Judge and Stanton. Also totally fine. You wanna get, let's see, shortstop for Tim Anderson. Like that's the start of a good stack, right? 3,100, if you take Tyler Wade, he's $2,000, increases your average that much more. Like a full Yankees White Sox stack, if you wanted to go four-four, which is obviously totally viable stacking strategy on every slate, is certainly doable tonight. I like India and Farmer from Sinsi today. Yeah, those players are always in play. They're not on this, the main slate, that's the earlier game that starts at 6.05 or 6.10 or 6.15, whatever that is tonight. 6.10 tonight. That game's not on the main slate, but yes, Jonathan India and Kyle Farmer are both solid options from Sinsi, especially if you're playing the single game slate, like Jesse Winker, Nick Castellanos, and Joey Vado should be much more popular than Farmer and India. So that makes a nice option if you're building single game lineups. So tonight's a slate where I'm gonna be looking for my main stacks, which will be the Yankees and the White Sox. I guess we're just at the mercy of Chicago and Milwaukee and the MLB, if they just decide to cancel this game and postpone it until tomorrow if we get a double header or whatever it might be or sometime later in the season. But really focusing in on the Yankees once their lineups confirmed what that looks like, getting plenty of shares of Chicago, getting some New York and Chicago stacks together, but then also getting some Kansas City with New York and Kansas City with Chicago just because ultimately, Ty Ohn's giving up too many home runs, right? He's giving up too many home runs specifically to lefty. So looking to some of the power from Kansas City, again, a team that probably shouldn't be as popular I think is a really, really solid tournament called tonight. Perez has great splits versus righties. Even it's a ready, ready match for much I'd say. So I'm going to Ryan O'Hearn, Perez, Santana and Dozier from Kansas City as the main four players. Like Ben and Ten deal, take some shots on depending if you started or not, just be dealing with the shoulder issue. Do you like Ryan Jeffers or Thales whether puny? It would be Thales. Like I just want that power, especially in that park with the wind blowing out, as you said, whether permitting. It's Mr. Jack Moon and everyone who has Fandall sports but better have 25 ready for Dinger tomorrow. Yeah, it'd be great if we get some Dingers today, you know, get the week started off on a good note. Get maybe South Perez to hit a home run since I wrote him up today on number five. That'd be the player I want to hit a home run today. I also think he's like legitimately in a good spot going up against Ty Ohn. Let's just look on him. So of course I'll be back tomorrow for another home run call. Perez is my number one option onto night slates for a home run call. Like 189 iso slightly a little bit lower than we'd like to see but solid fly ball rates, solid hard contact rate and a solid home run to fly ball ratio from him. You know, it'd be great if it was a lefty like Andrew Keeney if he was pitching for the Yankees this would be an absolute crazy spot for some of the righty hitters on the Royals. But, you know, we're working with Ty Ohn who still is giving up too many home runs and too many fly balls, especially with the wind blowing out. The weather again, major, major concern on tonight's slate. I would say that if Chicago does play, Peralta is a risky option. He just is. There's no way we can say that Peralta with his 50 or 48% fly ball rate overall is it's 53 against lefties. It's 42. So that makes it was a 48.7 overall. It's 48.9 overall. There's no way we can say that Peralta is as safe of an option as Musgrove or Geelito which is why this morning I ranked them Musgrove, Geelito, Peralta in that order, all things considered. And the matchup for, you know, even though Chicago is not a good team anymore, they trade away all those players, they're still better than Miami. So I think we could be looking to Musgrove absolutely overall number one. And then, you know, going to Geelito number two, I know he burned a lot of people last time, myself included, putting up zero, Fane two points and four innings with six earned runs against these Royals that are on tonight's slate. Obviously just not a good performance from him, but he had been consistent for the most part except for the zero. That's the All-Star game. Don't worry about that. Or just some random thing. Overall, just like not a picture that we really need to be that concerned about. He is much better than he showed in his most recent game. So Musgrove, Geelito, Peralta in that order, Yankees, White Sox as my two primary stacks, San Diego, just half a step behind New York and Chicago, Chicago, White Sox, I should say, and then Kansas City as kind of that next best option. Milwaukee would be in there. It just depends on the weather. I think Milwaukee is in the same tier as New York and Chicago, White Sox tonight. Can you rank the players from the Padres game? I assume you mean the Padres hitters, not the Miami hitters. So do I still have the, let me just bring up the Padres real quick. They are facing Righty, San Diego here. Obviously we want to get Manny Machado leading things off as the number one option. $4,000 can be expensive if you are trying to pay up for Musgrove or Geelito and Yankees or White Sox stack depending on how you go about things. But they do have plenty of other options obviously. It's still without Fernando Tattis. Going up Manny Machado is solid. Jake Cronworth, 202 ISO is fantastic. Will Myers, Trent Grisham and Tommy Tham are all three hitters. I think you should be very interested in tonight because we're getting decent value on all of them. Will Myers, 2400 I know he's been underperforming this year overall, but he's affordable and can be used in a larger stack for the Padres. So ranking them would be Machado. I think it's just one, two, three. Machado, Cronworth, Grisham, Myers, Frasier, Pham. Hosmer's also been underperforming this year just really not bringing a whole lot of power upside. Also not a player I've been rostering a lot as of late. So I would just go one, two, three. Myers, Pham, Frasier. Like those, all those players should be super solid tonight. Especially, you know, I like these players on the bottom tier just because they make line of construction a little bit easier. They actually don't have much power as these top players, but that's why you're paying a more expensive salary. So I'm going to the Padres tonight, half a step behind the Yankees and the White Sox. I do like their matchup tonight at home. Best pictures for tonight. Mike, Mike on Facebook is asking, it would be Joe Musgrove as just the best overall option. Point per dollar option, best matchup, best park factor, all these sorts of things. He's number one, G-Lito would be number two, and then Freddie Peralta would be number three, accounting for his salary, you know, which makes line of construction that much more difficult on a four game slate. Also the weather is an issue. You don't want, you know, Milwaukee and Chicago to say that this game is going to be delayed and you have Peralta in your lineups. And there's, you know, there's no real direct swap from Peralta to, you know, one of the other pictures, like if you drop from Peralta to Musgrove, that's $1,200 of savings. Like you'd have to change up roster construction quite a bit. So if push comes to shove tonight and we don't have a confirmed update on Milwaukee and the Cubs, the Cubs line up is in, you know, I like Hap in the three spot. I just spoke about him. I am on board with Ian Hap tonight. If push comes to shove and it's coming down to roster lock and we don't have an update on the Cubs and Brewers game, I'm simply removing, you know, Peralta from my player but I just don't want to have him in there. I don't want to have to rearrange things. I'll keep some hitters in there just because, you know, generally we see the slate, the lock move back for that specific game. So you can swap the hitters out. It's obviously easier to swap the hitters out than it is the pitchers. Musgrove would be in the later game, but the Chicago White Sox game would be starting at the same time, I guess, as the Chicago Cubs game. So I would remove Peralta from my player pool, keep Geolito, Musgrove, Tyone as my main three pitching options and then just take a few shares of Milwaukee and, you know, like a one off like Ian Hap from Chicago, trying to gain some of that fly ball potential from Freddie Peralta. Again, if this game does play, that's what we're really waiting on for this because, you know, this lineup isn't good. Like Hap and Wisdom, I guess would be my two favorite plays from the Cubs for that home run upside. Do you like Carlos Hernandez at all with the San Diego, Chicago White Sox stack? Yes, so I mentioned him briefly this morning on the solo shot. Obviously a smaller sample size from him, only 39.1 innings, like a 28% striker rate like is solid. It's above the league average, 14% walk rate, that's an issue, right? Allowing Yankee hitters on base when you're also allowing a 40% fly ball rate in a game with wind blowing out is a deadly combination. Too many hitters on base for free and a high fly ball rate, you know, with wind against the lineup like the Yankees is obviously a deadly combination. So I do like him tonight. I mentioned it again on the solo shot this morning, like his strikeout upside is pretty solid. Like as long as you can get deeper into the game, none of these like relief starts. We want to be looking at, but like he's putting up some decent performances like six strikeouts through four innings, granted it's Baltimore, six strikeouts through five innings against the White Sox only one or run, like that twice, I should say six and four, 10 strikeouts over 11 innings versus the White Sox and one or run like isn't bad. The walks can be a big issue for him. So I do like Carlisthen Anders to answer your question. It would be limited shares of him, right? And it's just to be different. It's just to differentiate the roster construction, differentiating my player pool. I have no interest in, Bo Burroughs by the way is just gonna be an opener for Minnesota. He's actually not actually gonna be starting. So he probably shouldn't be rostering him. He's literally gonna pitch like an inning, maybe 1.2. So he shouldn't be rostering him. Alec Mills going up against Milwaukee, even if there was no rain in this game and you know, it was just normal amount of wind. Like you probably still shouldn't be rostering Alec Mills just because he doesn't have a whole lot of strikeout upside. And then Zach Thompson for Miami. Listen, you wanna take a picture against the Padres knowing that the power that they have in that lineup. I mean, more power to your braver man than I am. I would not be doing that. So tonight's slate I wanna say is very clear with the options that we have. And if this game gets rained out in Chicago versus the white, the Cubs Brewers game, it will become even more clear where you just roster Geolito or Musgrove and then you just pay up for the Yankees, the White Sox and San Diego with a few shares of Kansas City as a bit of a one-off. All right, so that does it for today's Q&A. I'll be back tomorrow 9 a.m. right here on the Fandle YouTube page for the solo shot. I'll be back tomorrow for the Q&A at 4 p.m. right here on the Fandle YouTube, Twitch and Facebook page. You follow me on Twitter at DFS underscore Tom. Until next time, good luck in your contests.


If you want to live sensibly, you should have contact with the earth that you live on. Being in touch with the earth can complete the health process altogether. So is there some way to do it? Yes, there are specific methods with which we can do. We will provide this substance to you. In terms of health and well-being, there will be immense benefits one can clearly see. The most intimate of the physicality in the existence is your body. And this body is just a piece of earth.  Right now you're an outcrop who prances around. After some time, you will become a small mound. You may be living many fancy things about yourself, but that's not the reality. Somehow this fundamental thing that we are just a small outcrop of the soil in which you're sitting right now is forgotten generally till we abide. If you want to live sensibly, you should have contact with the earth that you live on. Today because we have lost this contact in certain ways, it gets disorganized. This disorganization can lead to disease and weakness and ultimately destabilization of the system itself. To strengthen the integrative elements in our system is very important. So is there some way to do it? Yes, there are specific methods with which we can do. We will provide this substance to you, which is being called as thayamannu, which means the mother earth. This is a mixture of five different aspects. Nearly fifty percent is soil. There is some amount of green gram flour. There is what is called as organic camphor and there is a little bit of soap nut powder and there is one more herb in that. All together you can apply this. If you have the time, the best way to do it is apply to your entire body. Do your practice and then shower without soap because this will act as soap because it has soap nut powder and other aspects to it. It will leave a mild sense of camphor on the body. It is very healing in various ways. It opens up the pores of your skin. If you do this at least for two to three hours do not apply any cream or oil or anything because the body has to breathe. Breathing is not just through your nostrils. The pore in the skin has to breathe. The more it breathes, the more it is connected to everything around you and your energetic body will develop well if you allow the body to breathe. You must understand this if you put any harsh chemical on the thing. By natural resistance, the pores will close. This is what is happening when you apply soap. It is closing. Well, if it is necessary, your body is in a certain condition, you want to use soap, it's all right, it's not you have to be puritanical right that but generally being conscious that applying anything sticky or oily also blocks the pores. Applying any kind of chemical, naturally the body cringes and closes, it will open after sometime but it will close at that time. Especially if you are showering with cold water, body should open up, body should receive the water. And if you use this as also like soap, you apply it as much as you want and you can wash it off with water, you will see the difference that the body feels because not because of its own accord, because of the way it opens you up to the elements. But if that is not possible for you, you have only certain amount of time for your sadhana, then the places that you need to apply is the soles of your feet, very important and your palm around the navel, anahata where the rib cage meets, pit of the throat or the entire throat and forehead, just here you can apply or you can apply the whole thing or you can apply for your whole face if you wish. But it's all a question of convenience, you may be working and you may be seeing people with your face full of mud, it may not be practical, you can just keep it like this, like how Vibhuti is kept like that, you can just apply, according to your convenience you do it, but there is no harm in applying it at least once a month or once a week or whatever it allows, entire body and doing that. If you keep at least one day in the cycle of the moon, that is one during amavasya to pavarnami and one during pavarnami to amavasya, that means every fourteen to fifteen days if you keep one day where you apply head to toe, spend two, three hours doing this, in terms of health and well-being there will be immense benefits one can clearly see.