This is Covering the Spread part of the FanDuel podcast network. A jam-packed show for you today on this Tuesday. Of course, our first look at NFL week, number three coming up later on a recap of week two. We've got Brandon Gadoula on, talk about the president's cup and golf and betting on that. But of course it's Tuesday, which means K-Props with pitching ninja Rob Friedman will get his thoughts on all those later on today. This is Covering the Spread right here on the FanDuel podcast network and numberfire.com. My name is Jim Sonnis. I am a senior writer and analyst for numberfire.com. Join here by Rob Friedman. Check him out on Twitter at pitching ninja. You can find all of his fantastic work at Fox, MLB, Nessun and Peacock. Rob, only about two weeks left in the regular season. It is getting down to the nitty gritty here. How you doing today? I'm doing great. How are you? I'm delightful. I'm excited for some baseball. My twins are toast.   And I think we get that for tonight too. So I'm ecstatic about what we're gonna see the next couple of weeks. You make a really good point there. I think detaching yourself from your team and enjoying the game is, that's kind of the way I approach everything. So I don't root for anybody. I root for pitchers. And it makes it really enjoyable for me.  So I kind of like that too. Yeah. And I would prefer they were in it, but honestly, whenever I'm not gonna complain too much about all of that. Now the problem that we usually have, we have for today Rob is usually what we do is, I'll ask you for your strikeout props. You'll give me your recommendations. And then I'll ask you about one that I've got. We did get Jordan Montgomery last week at six plus, but I've got nothing today. I looked at every strikeout prop on the board of Fandral Sportsbook and I saw nothing. So I have to lean on you for this one because otherwise I'm just hitting back and hanging out. So when you look at the board for today, where are you seeing value in the strikeout props for tonight? First, I want to say I'm disappointed because every time I'm on, I hear a K prop that I really didn't appreciate as much as you did.  So the fact that you didn't see anything and I have three. Yeah. Yeah, I'm a little bit, but no, I'm very comfortable with my three. Yeah. The key thing, the good thing is that I didn't look at the games before 705 because I tried to like double dip my work. I'm looking at the DFS main slate. So I don't look at the early games. It sounds like you've got some action on those. So I think despite the fact I found nothing, that doesn't mean that I'm against these ones because they sound pretty fun. Good. Well, I have a three leg parley with the same game parley of Brian Beyo for five Ks or more, Nick Lodolo for seven Ks or more. And then in the night cap will go Luis Castillo for eight Ks or more. I think that that Beyo versus Lodolo matchup, just like a, you know, we're talking about having, you know, being able to root for whatever, that from a matchup perspective, two really fun guys is super intriguing. Now, Beyo, I want to talk about him first. We'll talk about Lodolo is super exciting in a second, but Beyo is a guy who combines like enough strikeouts, but also kills some worms. And that's a really tough combination. It seems like, especially for a young guy, what allows him to kind of tap into both those skills simultaneous? I think it's a combination of his, I mean, that's sinker changeup combo. His slider's been getting, I mean, getting some pretty good movement, but I think that sinker slot, obviously sinker changeup, you're going to pound the ball into the ground, but he gets enough movement on it. Sometimes the miss bats and the changeup, especially since his mirrors is sinker, he's able to at least fool folks with velocity. So he's got a really good changeup, obviously. I mean, people have made comparisons with Pedro and he thinks he's clicking with him. His last few outings, like he's been clicking, he's leaning on the veteran pitchers to learn stuff. I like him. He's starting to get a little bit more on the case side. I like what he's about. I think he's going to be an exciting pitcher for years. Yeah, and that's a good staff to learn from too. There are a lot of smart guys there who you can lean on for sure. Now, let's talk about Lidolo. It's been a rough year for the Reds, obviously, but he's been the exception in his 16 starts, which is a big sample, by the way. That is a big sample, 30% strikeout rate. Tough matchup, though, with the Red Sox, not a big strikeout team. What gives you confidence in him being able to navigate his way around that really tough lineup? I think it's just his pure stuff, that curve ball slider, whatever he calls it, I think it's just a let's go breaking ball. Is one of the low key, the filthiest pitches in the major leagues, it ends up behind a hitter, I think more than any other pitch in baseball for a strikeout, so he's like, I don't think he's the ordinary guy to go up against. I know the Red Sox lineup is tough, but seeing him is something different and that pitch looks like a strike for a long way and ends up often behind hitters. Yeah, and he's been a delight. So no objections, neither does for me again. They're not on the games that I analyzed. So you got a Bayon over four and a half at minus 118, Ladolo on a single leg minus 156. Do you pair them with the Castillo over seven and a half that gets you to plus 492 for the three leg parlay there and Castillo's facing off with Oakland. You were talking about that before he came on the air about his most recent start against Oakland and obviously the results were not there, but what do you see that gives you confidence in the bounce back here for Castillo the second time around? I liked his last few outings. I think he was electric and I also, the fact that Gilbert just dominated yesterday, I think he will feed off some of that and I just, I like Castillo generally. Yeah, I mean, I just do. I mean, he's been fun and I think it's been encouraging to see that translate to the Mariners. Can we talk about this with Jordan Montgomery a bit where you change teams, get a different set of eyes in there. They, I mean, outside of recent, they still let Castillo be Castillo. He's going deep in games, a bit of a different pitch mix. He's had a couple more, a couple more two-seamers in there as past eight starts with the Mariners, but honestly for him, I don't think that's a bad thing. Yeah, no, I agree. And I think that staff is actually a very competitive staff.   Good pitching staff does that. And I think having Castillo follow up somebody, you know, that angry outing by Gilbert just challenges him because Castillo pitches on a motion too. And I kind of, you know, I think he wants to one up Gilbert. I think he wants to one up Gilbert, but I also think he just wants to be on the mound. And that's encouraging for me at this point in the year where they're basically locked into playoffs. They kind of know where they're going to be. They're still letting him go about a hundred pitches per start. And it's not 115, 190, you know what he's typically going, but like it's still very long. So you pair those three together plus 492 for that one. Yeah. And, you know, obviously this is a tough time of year because you don't know. I've been burned recently by guys getting pulled early. You know, who knows, maybe Castillo have an outing like he did the other day where he's just keying everybody at the beginning of the game. You don't have to worry about it. Yeah. It's the fourth inning he's done. He already got those eight strikeouts. So I think that those are pretty fun. I feel better about this slate now. Having talked to you, I think that there are enough strikeouts out there for me to feel pretty good about it. But again, check out Brian Beyo, Nicoladolo and Louise Castillo. And make sure you check out Rob Freeman as well. Over on Twitter at pitching Ninja Rob. I hope the strikeouts are in abundance for you for tonight specifically with that Red Sox versus Reds game. I think that's going to be a fun one to watch. Castillo always in the light as well. Enjoy Charlie Morton is tonight too. I know he's one of your favorites as well. I almost picked him. Yep. Have a blast watching some baseball for tonight Rob. Thanks. Great as always Jim. Alrighty. Again, check out Rob Freeman on Twitter at pitching Ninja and check out his work at MLB, Nessun, Fox and Peacock as well. And check him out here every Tuesday as well for the next couple of weeks as well. We're going to get to Brandon Godulli to talk about some Presidents Cup from a golf betting perspective in a just one segment first. Big news, Fandall has an all new mobile gaming app, Fandall Face Off. Fandall Face Off is where you compete in quick fun games against other real people for real cash. It is all sorts of games you're familiar with like a homerun Derby, Wheel of Fortune, The Pattenac can be kicking game and so much more. Contests are action packed and last between two to five minutes so you can play on your couch, waiting in line during a commercial break wherever and on your schedule. Plus you can practice for free anytime whether it be head to head, multiplayer or large tournaments. Fandall Face Off has something for you. Plus in most contests we've matched up against players of similar skill levels so you are never totally over matched even as a beginner. Fandall Face Off is tied to your Fandall account and wallet so you can easily use your daily fantasy funds or sports book winnings in the app. Visit Fandall.com slash Face Off or download the Fandall Face Off app in the Apple App Store today to get in the game, age and location, restrictions apply, void for prohibited. See Fandall.com slash Face Off for terms and conditions. We got some golf back on the menu so let's bring Brandon Gendula back into our lives to talk about that. It is the President's Cup for this week in Brandon and because there's no DFS for this typically I don't know a lot about the President's Cup. My like golf focus is hyper focused on the DFS side of things. So I need you to educate me about this week but first though, we haven't had you on covering the spread in a bit because golf had a weird schedule. How are you doing? Good, good. Yeah, I was a bit busy last week when I talked about the Fortinet and did the heat check podcast solo which is always a bit of a grind because I learned how much of the hosting duties you do, which is all of them. But it's all about it. Anyone who did this point, baby. Anyone who did listen, hopefully took some action on Max Homa. Yeah, Max Homa, a thrilling win got out to that big lead early on and then used some witchcraft to win the thing on Sunday as well. Homa just seems like one of the best dudes on the tour so I was delighted when he does well. Now I got to ask you about the President's Cup because I know in theory what it is. I know it's like team play. I know it's the US versus the world but like what is the actual format for the President's Cup and what does that format do from a betting perspective? Yeah, so it's basically the Ryder Cup. The key difference is that just who's in it. It's the United States is in both of them as we probably all know, but the distinction here for the President's Cup is that it is the US versus the world minus Europe. There's a much newer event started in 1994. The host course alternates between the US and elsewhere in the world started in the US for the first two years but then has alternated since then. This year it's in Quail Hollow and Charlotte. It's a course that I know we're all probably somewhat familiar with at least in terms of hearing the name. It's a long par 71 and one of the aspects of a Ryder Cup, President's Cup is course selection and trying to figure out how best to pick the right course for your team. Unsurprisingly, the US picked a long course. They have a lot of long hitters and I'll break down sort of the general team strength a little bit later, but yeah, it's gonna be a course that benefits the US. Now, as far as the format itself, teams do play in team events, alternate shot or four sums and then also best ball formats or four ball. So we'll get two days each of those and then on Sunday we get 12 singles matches. The way that you accrue points is if you win your match, you get a point. If you tie your match or have it, you get half a point and first a 15 and a half will win. And yeah, it's basically, it's pretty simple. So you're just basically looking at team strength. Is that a fair way to look at it or do you need to like view it some way different? So I looked at team play for the Ryder Cup in detail last year and tried to look at team similarity and long-term stroke scheme numbers and granular stroke scheme numbers and like the better T-degree golfers have advantages and it all sort of boils down to the better golfers or the better golfers. And if you can, you want better T-degree golfers and that's basically the US in this event. So it kind of is what it is. I think that there's a mentality that match play comes down to putting and it's important, but if you're playing with other golfers and you both play similar styles, that's gonna help in theory, but also if you play, if you're getting two greens in regulation, gaining strokes T-degree, you're more likely to win. So that's basically what it comes down to. So you said this favor is the US and the betting odds reflect that.  That's actually an important number to have in mind, honestly, that does impact the way you wanna bet things in general. So you wanna keep that in mind with the draw. Is there any value for you in that market? Is it properly reflecting how good the US is or are you staying away from it? I think it's really close. These things are really hard to predict. Now we're not looking at like a spread here, like a point spread in terms of, we're just looking at outright. And it's important that I lay out how dominant the US has been. Since 1994, we've had 13 presidents cups, the US 11-1-1, the lone international win, came in 1998 at Royal Melbourne. The tie came in 2003, ended in darkness, that was in South Africa. So in the US, the US is seven and oh. Again, they hosted the first two. Only one home win for the US was closer than three points. Again, it's a kind of a tight spread of points, like a dispersion, but that's a pretty solid margin.  If you look at the true stroke-skinned averages for golfers available at Data Golf over the past year, the US averages a plus 1.54, which is the third weakest team in US history. However, it's within a 10th of a shot of being like an average US team. So it's not that big of a deal. For the internationals, there are a plus 0.91, which is more than half a shot worse on average than the US team. It's the second worst international team ever, within a 10th of a shot of being sort of average. We only have the 14th iteration of it, so it's kind of tight, but it's pretty lopsided from that regard. Additionally, we'll say the global golf landscape has hurt the international team pretty heavily. Why would that be Brandon? Expand. We're gonna have eight of the 12 internationals making their debut, so their veterans are Adam Scott, Hideki Matsuyama, and then Sung-Jee MNC Wukim have each played one. So an experience gap for the international side to overcome. The US still does have six rookies, but for the president, Scott does include Scotty Schaeffler, world number one, Colin Morkawa, multiple major winner. Max Homa, who's just like unstoppable right now. Billy Horschel, who's won the WC match play. Cameron Young, who has two top threes at majors and Sam Burns, four PGA tour wins. So, again, it's tough. Now I did my best to model this out, looking at stroke skiing averages and how that correlates to points scored and then the range of outcomes. And I have, so we need the international team to be about 12% likely to win. I have them around 20% likely to win. So the model, again, which went back and accurately would have predicted pretty well. The results here within the point margins, but I don't think I'm quite, maybe like a quarter unit for some fun, but if you're really trying to put down something large, I cannot recommend betting the international side because they're such a detriment, just based on overall strength, but also the course fit. Yeah, I saw data golf tweeting out their numbers yesterday and I think that they were pretty similar to yours in terms of like, they might have had international actually a bit higher. I think it was like 24%, but I also could be misremembered from a single tweet that I read. So I had it at 24% and then I tried to factor in the host advantage. There's a pretty big host advantage, so somewhere around there, yeah. Okay, that makes sense. So probably not betting into the USA versus international market unless you want some fun on the international side, but we do have other markets available depending on the states. I know New York is more limited. So if you're listening to New York, sorry. But other states do have other props up for this event. Any value for you in those? Yeah, so it's basically like point scores. So if you leave the US in points, international in points, if you're like a captain's choice or a wild card, you can be, there's markets for that. But if you look at the overall points leaders, we have 18, because we've had some ties over these. 16 of those 18 played in five matches. So you kind of want volume. They averaged a good stroke skiing number of 1.68. Just one golfer was below 0.75. The guys who were below 0.75 this year, Sebastian Munoz, K.H. Lee, Sewell Kim, Cameron Davis, Kevin Kisner, Ju Young Kim, and Christian Bezadenhote. So yeah, that's six of seven of those guys on the international team. 11 of the 18 ranked top 10 in stroke skiing average for, you know, among the president's cup teams. The top five this year, I won't list all of them. Scotty Schaeffler, Patrick Cantlay, Justin Thomas, Xander Schaufle, and Sung J.M., a name that I'll come back to in just a bit. 11 of them also were top 10 in official World Golf rankings points entering the president's cup. So again, we're kind of seeing more often than not, it's the better golfers, because you want to put out your better golfers to play more. And we've actually seen the international side, which has historically less depth, filter more of their volume to the top, their best golfers. Not going to read like, it's pretty marginal, but you know, we see that the U.S. much more willing to rely on their depth. So if you're looking at this market, just keep that in mind, especially with the veterans. We only have four veterans for the international side. So that's kind of bringing me back to Sung J.M. Sung J.M. is a very good golfer. He is top five this year. In true strokes gained average, according to data golf, he has played in a president's cup. He went three one and one in 2019 for three and a half points to tie for the points lead back in 2019. He, you know, again, I think people can get caught up in match player results and past performance at president's cups or Ryder cups. And I don't know if that's very predictive, but he did beat Gary Woodland four and three in singles and that's pretty dominant. So Sung J.M. has what it takes to see as much volume as he can be kind of treated as the number one guy. So I think him to lead the international side in points that was plus 600, it's now plus 500, but also to lead outright in points is plus 1800. I think that's a pretty good value bet. Billy Horschel, I think stands out as like a potential wild card point score, which is how it's listed on Fandall Sportsbook, plus 1400. Captain's picks can still see plenty of volume in this setup. So that's important. It's not just the qualifiers and then the captain's picks are all, you know, afterthoughts. And again, with the international side's tendency to focus more on the top of their lineup, we've seen 11 of 16 wild card point leaders come from the US team, which has more depth. It's willing to use more of that depth. Horschel, the kind of guy who probably is gonna get, you know, four matches, if not five. Just a note on that, we will not get Thursday lineups and matches until Wednesday afternoon. So be aware, be ready to pounce on that, depending on who, you know, for sure is getting a match. But he's also played quail hollow kind of well, if you care about the past decade, T7, T29 and a missed cut, but I think he stands out at plus 1400. And then just one final one, top overall score, Scotty Schaeffler plus 700. Those are like, those, those resemble sort of heavy favorite odds in like a full field. Yeah. He should get plenty of volume. He's the top golfer in the world by OWGR, by, you know, total stroke skiing average. He should be like a long-term anchor for the US side, both in Ryder Cups and Presidents Cups. Great match play player. We've seen that from him. He's got Ryder Cup experience already. Good course fit, does it all. And 72% of points leaders came from the host side. So a lot goes in his favor. If you're looking for something maybe a little bit shorter than 14, you know, 14 to one or 18 to one. With Sungjae, you mentioned value potential in both sides. Given the international tendency to go with a more concentrated approach, do you think that the 18 to one is the preferred market for Sungjae for total points scored? I mean, I think it's totally fine to go that route. Yeah.  But it's kind of up to you from a risk standpoint. I think he makes sense for both. I think you probably bet both and kind of hedge a little bit in that regard. But again, it's, you know, you want to have fun with something like this.  Yeah. And we know that a lot of the points scores, you know, from the overall standpoint come from the host side, the winning side. So just, you know, keep that in mind. But Sungjae, I think is in the best spot for the international team. Hey, man, written for Sungjae, there are worse scenarios than that. You're talking about having fun. That sounds fun to me. I know it's written against the US, but like it's Sungjae in, so I can make a leeway there. That's fine. Yeah. I mean, there's a lot to like on the international sides. They've just been kind of picked apart a little bit, which is unfortunate, but Sungjae and maybe a little bit of Corey Connors, if you really want to get wild if you're looking for Teter Green game, but I didn't want to recommend him fully. That was kind of just a you and me thing. We'll probably get there. Love Corey Connors. All right. That is Brandon Gadoula. Check him out on Twitter. Akadoula13 is senior managing editor of Number Fire. You can also find his PGA DFS takes on the heat check fantasy podcast. Love and sprinkled in throughout the fall. Talk some golf as well. Brandon, enjoy the president's cup. Good luck to you. And I'll talk to you again Thursday for some NFL DFS. You had best of luck tonight with all your strikeout props. And best of luck this week. I have none. As we discussed it wrong, I've got nothing. I have one money line, but I'm sweating. We'll see how that goes. But yeah, I'm all good. I haven't said sweating NFL week three. So we'll talk about that right now. Take our first look there again. Check out Brandon on Twitter at Gadoula13. Let's dive in now to our week three NFL first look and go through what my numbers are saying about the opening lines here for week number three. And there is some value, I think, specifically looking at some spreads here. There are a couple of money lines I like and then one total I'm betting. Don't know the model for that, but I will talk about that later on. The first one and probably the one I like the most from a spread perspective is the Steelers plus five and a half. I was five a fan duel this morning has lengthened to five and a half. So I'm probably on the wrong side of this one, but I'm showing value there and a bit of value in the money line too, plus 184. But I wanna go with the spread here. I've got the Browns favor by 1.97 points in this game, even with TJ Watt being out. And the reason I'm taking the points here is because I expect this to be a very low scoring game. The total does say that as well, total for this game is 38 and a half, justifiably so. I'm expecting a low scoring game. It's tougher to win by five and a half points when there are fewer points scored overall. The Steelers did look pretty bad Sunday, but I respect the Patriots defense quite a bit. I think that that is explainable. The Browns struggled a bit too. Obviously let up a couple touchdowns were there within the past 80 or so seconds. I think the one thing that concerns me most with betting plus five and a half here is that the Browns running game should be really good here. Nick Chubb, Cream Hunt, both those guys tremendous. And the Steelers do struggle there for sure. Having Watt out definitely does not help that at all, but it's five and a half. It's a low scoring game. I think it's a Jacoby Reset team that's here by five and a half. I think I'd rather go with the Steelers side of this. I have faith in Mike Tomlin, so I do like the Steelers plus five and a half and we'll lock that one in right now. My numbers like the Cardinals plus four, I've got this as the Rams by 0.98. Now I was joking on Twitter on Sunday when the Cardinals were down by 20, whatever it was points, that I was gonna put in a Vibes meter within my model to prevent myself from ever betting the Cardinals ever again, then they came back. I'm kind of back in. And now I'm not sure if I can fully recommend this one to you because the Cardinals have looked awful, but it's reassuring to me that the Rams have had the issues of their own too. They almost said Atlanta win that game. Atlanta was driving. They were in scoring position late in that game after coming back. I think I love Marcus Mario to full respect to him, but Kyler's probably better than the Atlanta offense right now. This game is in Arizona. They might get Rondale more back this week. So we'll see, I am betting this one, but not necessarily recommending you do the same. Kind of a do as I say, not as I do type situation. I'm gonna take it. I understand if you don't want to. I think my numbers are probably still too high on the Cardinals, but I think if there's enough there, I will bet it. So for me plus four on the Cardinals is totally fine. I don't blame you if you don't wanna go there yourself. The Denver Moneyline is showing value for me right now. That's at minus 102 at Vandal Sportsbook. I have Denver favored in this game by 1.78 points. That is with a bump up to the 49ers, Jimmy Garoppolo quarterback. I like Trey Lance a lot and I was excited for him to play, but there was a lot of uncertainty baked into my numbers because we hadn't seen Trey Lance at quarterback. There was also no George Kittle. So when you give me more certainty with Garoppolo, I kind of don't have a lot of choice, but to bump up the passing efficiency on this team. They will likely get Kittle back this week. They got IU, they got Debo Samuel. That's a lot of good pieces. So I do have the 49ers bumped up with Garoppolo in there, but I just can't get to this one being with the 49ers favor. Denver did struggle last week. They had a hideous success, right? But they didn't have KJ Hamler in that game. Jerry Judy came out mid game. Sounds like Judy should be good to go here. Sounds like they were saying you was day to day. And if they can't go, at least they've got the full week to plan around those absence versus losing hit mid game. It doesn't feel good to that Denver after how they played this past week. But I think this number moved too much after the Lance news with how Denver played in week two. I think it's an overreaction line to what we saw in week two with the Lance injury with the Broncos struggling. I think there is value in the Broncos money line. So I'll take them minus 102. And I feel pretty good about that one personally. My numbers do like the Dolphins plus five and a half and the Titans plus two and a half. I'm not betting either. Although the movement has been toward the Dolphins in this game. It moved like from four to six overnight with the Bills playing pretty well. Move back to five and a half between reopening this morning and when we're talking right now, my numbers do like the Dolphins, but like I don't, we talked about this with Ryan on yesterday's show with the Bills. Like I just can't envision, I can see so many paths to this game going totally bust to and feel like a moron for betting against Josh Allen. I think my numbers are a bit too low on the Bills and just, you know, separating out the idea of betting against Josh Allen. Also not a ton of value here with it being back at five and a half now. So I'll set this one out most likely unless we see something drastic happen during the week. I'm okay missing out on the Dolphins at plus five and a half. The Titans, instead of betting plus two and a half, I want the total in that game. It's 46 and a half. And I want the under there. I did get the under 47 when it was up on Sunday morning. Went down to 45 and a half. Then went back up to 46 and a half this morning. And I don't know why. I'm not sure what the Titans showed you in that game to inspire confidence. We should bet them. Maybe it's just faith in the Raiders. But the Raiders offense hasn't been that great either. Neither offense has blown me away to open this year. And it's a tough match up for Tennessee. The key strength they have on offense is running the football in theory. They haven't looked like that so far. But the Raiders defense, pretty good rush defense. So the Raiders, I think they're a good rush defense. They should bottle up this Titans offense, which is why I don't want to get to plus two and a half. But also I don't want to faith in this Raiders offense. They kind of run through Devontae Adams right now. We saw the Cardinals just devote every resource to stopping Devontae on Sunday. And their defense was pretty successful in doing so towards the end of that game. Hunter Renfrow banged up. I'm not sure what his status will be here. I don't have a totals model. And I want to be clear in that because this is based off of other stuff. So it's not based off of, oh, my numbers say X. I do have numbers that project out full game efficiency across both teams. If I compare this game's projected offensive efficiency with the rest of the games on Sunday Slate, the total for the other ones around it is around 41 and a half. So maybe you want the over on, you know, Packers bucks at 41 and a half, but I think 46 and a half is too high. So again, it's not based on the model. This is based on gut, based on matchup, based on projected efficiency. And there are a lot more things that go into a total than those things, but I will still take under 46 and a half on the Titans and the Raiders for Sunday. One other money line that my numbers like is the Jaguars against the Chargers. Now, my stuff tends to be very high in the Chargers. So this really did surprise me to see this happening. But I've got, this is a 5.25 point game in the Chargers favor. So the Jags win odds by my numbers around 33%, they're implied win odds at plus 265 or 27.4%. So there is about six, five and a half percentage points of value in that this money line on the Jags. I'm unsure. Cause I like what I've seen from the Jags. I think they've been interesting. They've been kind of past heavy so far this year. They're getting the first downs early in the air, early in the downs. Team Orisco of pro football focus tweets out those numbers every Monday morning. They've been getting first downs early, which is a key thing to do in the defense. Played well against a banged up Colts team on Sunday. I don't put a lot of stock into that defensive performance, but the offenses look good. So tentatively I'm holding off. I don't like betting against Justin Herbert cause he can do a lot of crazy stuff when the team takes the chains off of him. I'm tentatively holding off. That could change by the end of the week, but the Jags money line plus 265 showing value for me enough. So where I have to like, at least consider it, not quite there yet, but we're, we're looking into it. So the official ones I want to lock in right now, I want the Titans Raiders under 46 and a half. I want the Denver money line at minus 102 and I want the Steelers a plus five and a half in that game. Personally, I'm betting the Cardinals plus four, but again, I'm not going to subject you that once again. We'll talk more about the full slate coming up on Thursday with Ryan Williams. Again, Ryan doing well so far this year. We'll talk to him on Thursday to break down that slate and we'll have the prop preview coming on Friday, but those are the primary ones for me as of right now. Let's finish things up here for today by taking a look back at last week and recapping college football week three and NFL week number two on the college side of things. Ed Fang got awesome movement on his bet. He had Notre Dame minus 10 and a half. That one closed at 13 and a half. So no, no key numbers there, but still three points and three points, pretty big move in his favor, but Cal to their credit hung around the whole night. They had a chance to tie that thing up at the end. Notre Dame did hold on for the outright win, but seven point wins, so no cover there, but good movement for Ed longterm, you expect good movements to translate to good results didn't happen there, but we'll see what Ed says for tomorrow in premium college football week number four on the NFL side things. Our guests had a great week. Ryan Williams and Tom Vecchia, when he combined nine and one on their bets from last week's shows on Thursday and Friday, Ryan hit the bucks and saints under 44 and a half. He had the commanders and lions over 48 and a half. For spreads, Ryan had the Jags plus four and a half. And of course they won outright. You had the Packers minus nine and a half. They won that game by 17.  They won by three. You had the Chargers plus four and a half. They lost, or they lost by three. So pretty sick week by Ryan across the board for that one. As far as last side schemes go on the Ryan side of things, we talked about a couple of things. He liked the Eagles Vikings under 50 and a half. And I thought that was toast for the first half, but then second half really no scoring at all. Had Devontae Smith anytime touched on a plus 240 and a Dalvin touchdown at minus 115 didn't get those, but he was all over Stephon Diggs. And that pretty much covered everything for him in that game. He had Diggs over 75 and a half receiving yards. That hit by like halftime and he like doubled that up. Anytime touchdown, he had three a plus 115. So a couple of ones didn't hit there for Ryan, but overall great Monday for him too as well. So great week overall for Ryan. Last week, check out Ryan on Twitter at Ryan Alexander underscore W. Good week by Tom Vecchio as well. Find him on Twitter at DFS underscore Tom. Tom's loan miss on Friday was Ramondry Stevenson. Anytime touchdown, that was plus 230. He didn't score, but he hit Aaron Jones over 29 and a half receiving yards. He had Darren Waller and Mark Anders. Anytime touchdowns, both those guys are plus 135. So good week for Tom. Good week for Ryan across the board. Check out Ryan Alexander underscore W on Twitter and DFS underscore Tom on Twitter. We'll talk to Ryan once again Thursday to get his thoughts on NFL week number three. Not the best week for me. By any means, we talked on Monday but I had the Vikings money line. It was plus 118 we talked. I believe it closed there as well. They didn't play well. Every time the Eagles snapped the ball, it seemed like they were gonna pick up 10 yards. I know the second half was a bit different, but like they were kind of in coast mode at that point. That offense is real good. And I expected good things in the Eagles. I had the over on the wind total at eight and a half at when I bet it, but didn't expect that on Monday night. They played really well. So this Eagles team is very good. I still think the Vikings will be good too. I still think that long-term, they'll be a solid football team, but the Eagles are good. So lost that money line there. Other money lines I had from earlier in the week were the Panthers and the Commanders. Good movement on both those. They both closed at even money. The Washington was plus 115 we talked. Panthers were plus 118. They both closed at even money. So good movement in my favor on both those, but neither team could pull it away in the Panthers. Had a couple of shots to do so. The Commanders tried to claw their way back in that game. It did make it close, but no wins in either of those. I also lost Seattle on the spread plus eight and a half. They played that. I think they might be a bad football team. I might have underestimated how bad they actually are, but either way, I lost that one plus eight and a half. The Cardinals did rally to cover and win outright. I had them plus five and a half. I personally bet the money line as well. That helped study it at five and a half all week. I don't feel good about that win. Like it was a win, one of the few I had this week, but hey, I don't feel good about it by any means. It was a win, but we'll take it. The other one I had was over 44 and a half of the Ravens versus the Dolphins. That one was great. No movement on that one similar to the Cardinals one, but that one I did feel good about. My numbers for the projected total offense efficiency really did like the over in that game. It did turn that way with a devolving into a shootout. So feel good about that. Don't feel good about the Cardinals win. Austin Eckler did hit the under 97 and a half rushing plus receiving yards. Talk about that on Thursday's show. He almost got there with some late dump offs, finished with 10 total targets and 14 carries. He made me sweat, but still got the win there. Just didn't think his role was that good. It did wind up being better than I thought it would be, but still hit the under there. So overall three and four across the week between Thursday, Monday night, and then Sunday was not my best week. We'll see if we can bounce back here in week three, but I think I feel pretty good about the week three bets we discussed before. So I didn't feel good about them. I wouldn't bet them, but we'll see if we can bounce back. I'll try to emulate what we got out of Ryan and Tom this past week. As I mentioned, our college football week number four preview is coming up tomorrow with that fangle breakdown. His favorite bets for this week will also get to Ryan on Thursday and we'll talk with JJ Zachary in Friday to get a proper breakdown should be a fun week once again.  We had Rob Friedman pitching Ninja on, talk about his favorite strikeout props, find him on Twitter at pitching Ninja, find Brandon Gadoula at Gadoula 13 and check out all of his golf betting work over at numberfire.com. I am on Twitter at Jim Sonnis, J-I-M-S-A-N-N-E-S. You can also follow the FanDuel Podcast Network at FanDuel Podcast. Thank you all for tuning in for today.  We'll talk to you once again tomorrow. Talk about some college football. This has been covering the spread right here on the FanDuel Podcast Network.


Item number, SCP-216. Object Class. Safe. Special Containment Procedures. SCP-216 currently resides in Laboratory 5. Access requires level 2 clearance. Insertion of recording devices into SCP-216 is prohibited without O5 approval. Description. SCP-216 is a 35.6 centimeter or 14 inch high iron safe with a multiple dial combination lock. The lock has seven dials each with numbers ranging from zero to nine. The combination cannot be changed while the door is open. The weight of the device appears to fluctuate in an obtuse manner. The door of SCP-216 can always be opened, but the accessible interior space appears to change depending on the currently entered combination. Objects placed inside SCP-216 may be accessed by re-entering the combination that was configured when the object was inserted. Objects retrieved from SCP-216 appear to be undamaged by the device. It is speculated that every possible lock combination results in a different interior and that there are approximately four million available compartments. It is unknown how many objects currently reside inside SCP-216. An engraving found on the bottom of the safe reads three quarters. It has been hypothesized that the compartments of SCP-216 are shared with three other devices of a similar nature. This hypothesis is consistent with the findings reported in Document 88B. Document number 88A. Initial test log. Combination lock set to 6692724 and door opened. Compartment appears empty. One notebook and pencil placed inside and door closed. Combination lock set to 6692725 and door opened. Compartment appears empty. Combination lock reset to 6692724 and door opened. Notebook and pencil retrieved from compartment. Note SCP-216 appears to be a very efficient storage solution. Document number 88B. Test log 1. Testing the effect of inserted items on the SCP's total mass. Total mass of unit before inserting item 935.877 kilograms. Notebook and pencil total mass 350 grams inserted into SCP-216 and door closed. Total mass of unit after inserting item 935.965 kilograms. Expected mass 936.227 kilograms. Actual mass 935.965 kilograms. Difference 262 grams. Testing shows that SCP-216 takes on approximately 25% of the mass of its contents. Suggesting the mass is distributed evenly between SCP-216 and the three other hypothesized devices. Document number 122-A. Test log 2. Compartments 000000 to 000206 checked for contents. Compartments 000000 found to contain traces of sawdust. Compartments 000001 through 0000206 found to be empty. Other testing arranged. Document number 152-D. Test log 3. Compartments 000332 through 000398. Each compartment had a body part from a 28-year-old female who had been reported missing on data expunged. Contents removed for identification and then incinerated. Liver, spleen, and lungs not recovered. Document number 159-B. Test log 4. Compartments 000409. A live wolverine, gulo-gulo, adult male, with a mass of 30 kilograms. Upon the door being opened, it attacked and killed Dr. R. R. and mutilated two nearby D-class personnel before being shot five times by guards. Autopsy of the wolverine revealed no anomalies. Subsequent examination of Compartments 000409 has revealed it now contains only loose wolverine hair with residual traces of wolverine urine and wolverine anal musk. Document number 160-A. Test log 5. Compartments 000456. A fully loaded Glock 19 handgun with a round in the chamber and one regular flavor Klondike bar ice cream dessert. The ice cream bar was not melted, cold to the touch, and remained so as long as it was in the compartment. It was removed for inspection and began to melt within two minutes. It was placed back in the compartment. The door closed for three hours and then reopened. The ice cream bar was in the same slightly melted state as when it was placed back three hours prior. The ice cream bar was removed, placed in a freezer in the nearby second floor cafeteria for one hour. After one hour was placed back into the compartment with the handgun and the door closed. Document number 161-A. Test log 6. Chamber 000501 confirmed to be empty had one standard foundation GPS unit placed inside it. When the chamber was sealed, GPS failed. Data from the unit upon retrieval showed that the satellite was unable to confirm source location during this time. Document number 174-B. Test log 7. Chamber 6162384. 51 apple seeds. Chamber 1846563. 22 apple seeds. Chamber 29060104. 9 apple seeds. Chamber 855821. 78 apple seeds. Chamber 1111111. One heavily decomposed apple. Document number 152-E. Test log 8. On 04-16. All previously checked compartments were opened with the intention of confirming contents. When compartments 000332 and 000398 were opened, individual body parts were found corresponding to an unknown male. Arranged in the same order as found in experiment 152-D. Including the liver, spleen, and lungs. All previous traces of tissue from experiment 152-D, which had not been cleaned, were found to have been sterilized from these compartments. Pursuant to request for 05 directive, body parts were placed back into their compartments. Containment procedures currently under review. Document number 162-A. Test log 9. Testing performed by Dr. One digital video camera recorder was set to record and placed in compartment 550000. Oriented so as to face outward towards the door. The door was closed and compartment 5500001 was opened. Compartment 5500001 was found to be empty. The door was closed. Compartment 550000 was opened again and the video camera recorder was retrieved. Upon viewing the recorded footage, Dr. suffered from a transient ischemic attack. The recorded footage shows said Dr. placing the video camera inside the safe and closing the door. No time passes before the door is reopened and the video camera is retrieved from the safe. This is inconsistent with the scene reported by Dr. No audible sound is present on the recorded footage. Subsequent analysis of the video camera revealed that several internal components of the camera had been fractured. Document number 162-B. Test log 10. Data expunged. Data expunged. Document number 162-D. Test log 11. One tape recorder was placed inside compartment 550000 and the door was closed. All other compartments were opened and closed before returning to compartment 550000 and retrieving the tape recorder. The following file has been reported to cause disorientation, nausea, sweating, and a sense of overwhelming despair, abdominal pains, panic attacks, migraines, and strokes. This file should only be listened to in a secure environment. Do not drive or operate heavy machinery for up to 24 hours after listening to this file. Refrain from making quick eye movements while listening to this file. Lesson complete. If you missed the previous orientation, go watch SCP-215, Paranoia-Inducing Spectacles, right now. Or for the complete course, watch this playlist.


Hi guys, welcome back to my channel. Today's video is going to be my week 31 update of my fitness journey. Man, this was a week. So like normal I'm just going to go through what I did this week give you guys some updates And then we are going to show you the progress photos. So starting off on Saturday I actually didn't work out surprise surprise. I never worked out on Saturdays But I was a little bit more physically active because I had a work event I was at a virtual event so I was like standing and help setting up like cameras and taking down equipment and everything and I also had a YouTube day So I basically edited videos Sunday. I did the 15 minute body workout by Pamela. It's really intense I really suggest that one if you want to get a quick workout in and then I also did the 10 minute six pack workout and I really like that one as well. It's really fun And I really didn't feel like working out on Sunday But I pushed myself and I just did and that is why I only did two workouts, but that's okay Monday, I did the 20 minute intense workout by Pamela reef as well as her upper body workout It's about 10 minutes and her 10 minutes booty workout. This is basically my favorite favorite workout plan so far I love Pamela reef like overall. I think she's my favorite. She's so challenging and I also really like her accent Tuesdays, I don't work out So there's no footage there and then moving on to Wednesday Wednesday is normally my easier day Because it's in the middle of the week and everything But I actually went hardcore on Wednesday and I switched Friday and Wednesday's workouts So on Wednesday, I did the 20 minute full body workout the 10 minute waist the trained waist workout I did the 15 minute thigh workout that one kills me every time and then the 10 minute water bottle arm Toned arm workout. I love that one Thursday. I actually worked out yesterday. That's why I'm coming to you with nice clean hair today and it's like all down and I'm pretty cozy because I worked out yesterday So yesterday Thursday, I did the Jason drulo hit workout Super hardcore the 15 minute six pack ab workout and then I also did the 12 minute happy sweat dance workout I only did those three on Thursday because that's what I normally do on Wednesday if that makes sense So I just kind of swapped everything because I know on Thursday I do not want to work out But because of my schedule and everything I just had to rearrange a few things So it was a little bit of an off week, but that's okay Moving on to the updates don't really have a lot of updates, but I'm gonna say food wise It was a terrible week because you know I'm having Starbucks now. I Had McDonald's yesterday for dinner. It was so bad guys so I normally do teriyaki Tuesday, but it was a little late on Tuesday when I got home from a work thing and Honestly, it was just too late and I didn't want to have that many carbs So I was like, oh, let's just do it on Thursday. Of course the Panda Express we go to is a little bit of a mess All right, so they were out of teriyaki chicken I know that's it's a little silly and I didn't want to go all Karen But it's not the first time that this sort of thing has happened is probably like the fourth time Yes, I guess I sound like a Karen, but like come on I mean one time they were out of white rice like oh, I just Anyway, I don't know what day it was, but we also had Hooters And the Hooters wings are so good and I also had french fries. Those are so good After Wednesday's workout and still to today my arms and shoulders have been super super sore So I don't know really what caused that but I don't know I just found that after my Wednesday workout my shoulders slash arms were super sore After I did the water bottle workout and I don't know Maybe it's just because I haven't been working out my arms as much. Who knows another update I wanted to bring you is who am I trying next for workouts? I loved and I checked out everyone that you guys have suggested to me Some of them just I wasn't really feeling their vibe Like I just didn't really like their personalities. No offense. Like I mean that's the beauty of the internet Like there's a lot of workout gurus and bloggers bloggers out there So we can all appreciate one another and the differences But some of the ones that you guys suggested to me. I was like, I'm just not feeling it Um, like the way they come off across on camera and I have to genuinely like Or feel motivated by the person I'm doing their workouts or also it'll just become like unmotivating and I don't like The super like oh my gosh guys like kind of we're so excited to work out like Who is that excited to work out like not really me? I mean, I like working out, but we don't have to be like that. You know what I'm saying I also don't like the people who completely Talk through the workout like and now make sure your elbow and the match together Like I don't really like that. I I prefer the music the timer and then the just focusing on the workout I don't really like the talking so much back and forth Um, that's just a personal preference But the person that I found I cannot wait to try her workouts is San Vallette sanny sanny She also does videos with this girl named sammy. I know their names are like super similar, but San sannette sanny Oh my gosh, this is terrible Her last name is la let I think she's from a different country. I don't even know. I haven't done a ton of research But I found her channel through my friend heather's video about all the workout vloggers she tried out So san the let I believe is how you pronounce her name. I'm trying her workouts along with Probably a couple of her friends sammy's workouts. They're kind of like workout gurus together So I mean I might try some of theirs if you guys are wondering what my favorite Pamela reef workouts are I have a whole playlist so go to my playlist sections on this channel and you will see the 14 videos I love from Pamela. If you guys have tried sanny Vallette's workouts, let me know down below I think she was like a victoria secret angel model, which was like super cool But let's move on to my photos So on the left is alex last week and on the right is alex this week And then here is the side version of that and I cannot believe I actually look pretty good for eating like total crap this week So i'm not complaining whatsoever And then moving on to pre-workout alex on the left is pre-workout alex and on the right is current alex And here is the side view of that Honestly, I can't believe the way I look and feel after not having the best diet this week But as I've learned food doesn't impact my body as much when I'm working out consistently regularly and everything So I hope you guys enjoyed this video Question of the day beach or pool. I would have to say pool. I don't know why I just like the pool better Anyway, give this video a thumbs up Don't forget to subscribe to my channel and I'll see you guys in my next video. Bye


Okay, so I think we'll get started here. I think, let's see. I think we'll let everyone kind of come in still, that's out there. Mike is a little loud, I think. So welcome to this session on intent and SDN-driven service chain. I'm Kyle Mestri. I think anyone who's here earlier knows who I am. I'm the neutron PTL and chief technologist of open source networking, not network at HP. So, go ahead, Dave. Nice thing you said. Yeah, I like that. It's like, we're all about network. Dave Lenro, I'm from HP also, and work in the CTO's office in HP networking. Yeah, hi, my name is Kai-Zi Zhang. I'm a principal engineer at Huawei, USA. I'm going to start first. So, what is service training? By service training, what we mean is that through service training management and control platform, different traffic flows can be auto provisioned to go through different sequences of service function, service function chains. For example, for tenant's eighth flow, it will go through a firewall, a net, a firewall, an IDS, a video, and a load balancer. For tenant's B's flow, it will go through a net, a firewall, and load balancer. Even for the same tenant, different application flows can be steered through different sequences of service functions for different types of service function treatment. So now let's look at what is service training from the data path perspective. So, on the open stack management plan plus SDN control plan together will automatically coordination of all the data plan components and program those components to steer different flows through different sequence of service function paths. And those data path components include the class file service function forwarder which can run on virtual switch or physical switch. And then a bunch of service function devices can be run on VM or on the physical device. So why do we need service function training? Because service function training can be used in many scenarios. One of the scenarios is it can be used in public cloud. For example, as this diagram shows, you know, like one video flow from one client look at the pink path will need to go through a net and then firewall and then video optimizer and then load balancer to reach a video server. And then the same client's email flow might need to go through another service sequence for the server treatment. For example, you know, the red line shows the path. It will go through a net, a firewall and then mail security service and load balancer to reach the mail server. So for another client's flow, which is a database access flow, it will go through a net firewall, load balancer to reach a database server. Another use scenario of service training is in the hybrid cloud. You know, when the private cloud does not have enough resource to serve attendance request, it will leverage the resource in public cloud and then there will be communication between the private cloud and public cloud. So for the data traffic from private cloud to the public cloud, those traffic will need to go through encryption. And then for some other traffic, besides going through encryption, also need to go through a one optimizer and then a load balancer. The other direction when the data is shipped back to the private cloud, it will need to go through a firewall, IDS, intrusion detection service, IPS. And sometimes they need to go through a cache so that it's saved in the cache. And then the next time the private cloud doesn't need to access public cloud, just access the cache. Another use scenario is GGSN, mobile wireless scenario. So either from iPhone, iPad, or laptop, when the user need to access the internet, it's the traffic you already go through GGSN, PGW. And then from that, different types of traffic need to go through different service chain paths. Like, you know, those green box shows a service node. For example, some of them could be parental control and others could be like, you know, some security boxes. And so what's the benefit of the new service chain solution? Why we need it? We know that, you know, in existing service chain deployment, it's usually done through a manual configuration of all the boxes. And then that will require advanced business planning. With the new solution, the service chain can be automatically provisioned. And also, we will provide a simple user interface for the user to specify the service chain requirement. It will be an intent-based interface. So it will be a simple user interface. The user does not need to do manual configuration on all the boxes along the path. So that will lower the operational cost and also increase the agility of deploying a service chain. So also another aspect is, you know, in existing solution, when you want to change, when the user change a service requirement or need to scale out, then, you know, those will really require reconfiguration of all the boxes. So in order to avoid that reconfiguration, which can happen for weeks, then, you know, we have to plan for the peak to allocate peak capacity. But with the new solution, right, because all the service chains are automatically provisioned and the data path components are automatically programmed to set up the service chain. So any change of the service chain requirement can be done in real time. So this will lower the capital expense because we do not need to plan for the peak capacity. And another benefit is high performance. In existing solution, you know, the existing boxes are not all, you know, application aware. So usually, you know, we provisioned, you know, all application flows belong to the same tenant to go through the same service chain path. With the new solution on the service chain path is application aware. So different types of applications for the same tenant can be customized to go through different sequences of service treatment. Now I'm going to hand over to Dave to talk about intent. So, you know, we've decided that we wanna have certain subscribers or tenants get certain services and they're described by something called a service chain, but that still leaves the question of exactly how do we build that and how do we put it together? And I wanna talk a little bit about what we mean when we talk about intent and then talk specifically about how this applies to service function chaining. And so, essentially, the spirit of the intent approach is to tell the network what you need rather than what we've done traditionally, which is tell the network how to do it. So historically, we sort of build a model of the network that we want and we describe that to network equipment and that results in supporting our applications. The intent-based approach isn't really about describing the network, it's about describing the applications and modeling their behaviors and their interactions in a way that allows some smart piece of software that we might call an intent engine to do the translation from the what you want to the how do I do it with the current infrastructure. And it turns out that once you kinda define intent, it has some interesting properties that make it valuable for describing what we want out of networks and the goal of a lot of the work that's being done across several open source projects and standards development organizations and things is all designed to converge on sort of a universal language for intent so that all kinds of different applications can describe what it is they need from the network in a common language that can be implemented by multiple infrastructure controllers. So rather than having a kind of a traditional vendor interface to a vendor device and the resulting vendor lock, you end up with a common agnostic interface that works across a variety of equipment and in order to figure out sort of what is intent and what isn't intent, there's some kind of simple tests we can do and the first has to do with the fact that the intent is invariant with respect to the state of the network. So if your high level intent is that Bob should be allowed to connect to the internet, that doesn't change because one of your servers went down or you changed protocols on a device or you bought a router from a different vendor or any of those kinds of implementation details, the piece that's the true intent and the piece that's truly portable and invariant is this description of Bob wants to connect to the internet and assumes he can somehow resolve what Bob is and what the internet is. So that the portability point is closely related, I won't belabor that, but intent doesn't include any references to addresses, protocols, VLAN headers, media types, vendors, anything that's specific to the implementation, it's purely about how do the entities connected to the network communicate with each other and what do they need the network to do for them. It turns out it's highly scalable because it's position and location independent, you can take the entire description of the intent for a network system and you can pass it to one giant mega controller or you can pass it to thousands of small, smaller domain controllers. The information that needs to be sent to those devices doesn't change at all and they can use their local context to figure out how to translate whatever the intent is to the specific rules and implementation details of the devices they control. And finally intent brings context when you're looking at requests coming into a controller, asking for various things. If you go down to something low level like an open flow type of protocol and you try to figure out when things are contradicting each other and aren't consistent, it's essentially impossible to do because you don't have any of the what are we trying to do context, you just have the what are the match and action table look like context. And so by working in the intent space where we're understanding higher level things, the internet, Bob, the secure servers and the finance department, that context can come into the automated resolution of that and help contribute to understanding whether ultimately whether the controller should say yes, I'm gonna do all these things for you or no, I'm not gonna be able to. So just some kind of simple examples and from everyday life, I think I want my headache to stop is intent. Give me to aspirin is prescription. There's lots of things that might help your headache. If you narrow it down and say the only thing I want is aspirin, you actually take off the table all kinds of wonderful opportunities for getting rid of your headache that have nothing to do with aspirin. And so the intent, that's kind of the idea is let's give the automated infrastructure as much latitude as we possibly can to make decisions about how to fulfill the intent rather than assuming that the end user knows how to fulfill the intent and could possibly understand the state of all the equipment in the system.  You don't give them a map of every blade of grass on your lawn and some specification for the length to cut it to. Just kind of the high level what I want. That's what we're trying to get to. And what we're doing with this across some different organizations is trying to create sort of a common interface that will be infrastructure agnostic and be uniformly implemented across a lot of things. And so in the ONF Northbound Interface Group, we're working on creating and approving some level pieces of the information model that would describe what this interface wants to look like. And then several projects downstream are gonna consume those software artifacts. In the case of the Open Daylight, it'll consume those as Yang models. In the case of some other infrastructure, it'll be translated to some other kind of format that's understood locally. And we'll end up with this single information model and sort of conceptually identical interface running in the Open Daylight NIC project in the Onos Controller project in a OpenStack Neutron based implementation which Kathy's gonna talk about in some detail as part of this presentation. And on whatever common infrastructure controllers emerge, the idea is to get kind of a network effect and get enough things working through this scheme across different pieces of infrastructure that it draws in more users and more applications and more use cases. So we end up with kind of a common interface to collapse all of this. So when you talk about service function chaining and where's the prescription and where's the intent, it really comes down to the forwarding graph description talks about the kinds of virtual functions in terms of their behaviors and what they do, it doesn't refer to specific instance of a virtual function. If there are 10 virtual machines running a firewall, the intent-based approach says, I want it to go through a firewall. The prescriptive approach says, I want to go through firewall number seven. And the problem that arises with this is it essentially becomes a question of where do you handle errors and faults and where do you do self-healing in this automated system and what's the appropriate layering and partitioning for that? And what I'm gonna suggest is that when you have a low-level event like a network link going down, that doesn't change anything about the forwarding graph. If what you've said is the people in the sales group need to go through the auditing system before they can access the blah, blah, blah server, that doesn't change at all based on how many instances of that you have or those levels of detail. So what we're trying to do is capture pure intent, which is what are the things that need to go through the service chain and what kinds of virtual functions exist in the service chain? And then we hand that to a northbound interface that can then resolve the rest of the details. So that intent-based interface inside the controller in sort of a black box, that's where you're gonna know about the fact that there's 10 different instances of that firewall and where you're gonna get to make a decision based on some higher-level logic. Maybe it's proximity to the subscriber's point of attachment. Maybe it's based on the utilization of the links between the virtual functions, a number of things, but you allow the latitude for the controller to apply all the things it knows about the state of the network locally and then if there's some fault, like a link goes down, the controller, without having to go back and have any interaction with the cloud management system or the upper layers of OpenStack in this case, it can go ahead and pick a different instance, change the forwarding rules and the switches, fix the path so that the virtual function continues to work and between saving the latency of going up to another control system and back and the complexity and the amount of logic involved, you end up with a much more seamless, self-healing kind of a behavior and you end up restoring the customer's service much more quickly. So if you just look at some common things that can happen in the network, if you have the prescriptive interface, you end up with a sequence where basically, outside of the network controller, you try to harvest lots of information about the state of the network, then you try to make decisions about which piece of the network to use and then if something changes, you go back to the cloud management system which has to try to pull all the state out of the network again and try to make this same decision over again. It causes lots of distributed state problems that are hard to solve and it causes a lot of overhead and errors. So here's just a simple table showing kind of with the prescriptive approach, there's a whole bunch of errors that can occur, all of which are gonna cause you to go back through this long, painful cycle of having the orchestration system try to suck all the state out of the network and make sense out of it and then tell the network what to do where when you go to the intent-based solution, what you find is that the network controller can completely heal all of these kinds of faults locally without having to have any more interaction. We've really cleanly layered network-based faults and decisions that require deep understanding of the state of the network, stay inside the network controller and things that have to do with the high-level business purpose and the interaction of the compute and storage and network, those stay in the open stack domain. So for an intent-driven service graph approach, we still are working in the community to try to kind of pin down exactly what the info model is and what the syntax is gonna look like, but the basic model is it's based on these ideas of groups and so a system administrator or some piece of automation would start by building a database inside the infrastructure controller of endpoint groups that it knows about and some of those endpoint groups would be specific to different kinds of end users who might be subscribers of virtual function services. The other kind of endpoint groups become the pools of virtual function resources. So you might create a firewall type A endpoint group that maybe has some firewall appliance that's less secure than the firewall type B, which would be a separate endpoint group, but those become the pools of virtual functions that the network controller has at its disposal to try to satisfy the forwarding graph requests. And then during the life of the system, you can, as the orchestrator needs to scale out some virtual function, it's gonna add a couple of instances of firewall type X and what it's gonna do corresponding to that is add them to that firewall group so that that's its way of letting the network controller know that it has a larger pool to work from and some new candidates to assign things to. So essentially where we're trying to get to is the single intent-based API that comes from a common source and a common definition that gets built on multiple systems. In the case of the Open Daylight NIC project, a service chain user would sort of speak the northbound interface to that SDN controller directly and would get intent-based service function features through that mechanism in a system that didn't have a standalone SDN controller with that intent-based service chain API. That would be sort of the right-hand diagram where actually the upper layers of that intent engine would be implemented as extensions to the neutron system and Kathy's gonna talk in some detail about a proposal for building those extensions into the neutron system and thus supporting the intent-based service function chaining. So we know that in existing OpenStack, the core infrastructure, there's no support for service chaining. So in order to add the service chaining feature to the OpenStack infrastructure, one way is to extend the neutron API to support the service chain. So there will be a neutron API extension to support service chain. And besides that, we also need a common service chain driver API for the different drivers to hook up to implement the service chain functionality. And on top of that, we have this intent engine which will provide the user with intent-based service chain API which Dave already talked about. And then that intent engine will translate the intent-based service chain API to neutron API extension for service chain. And another part is that, currently OpenStack support a few service functions like firewall as a service, load balancer as a service, and VPN as a service. But there are many types of service functions which are not currently supported by OpenStack. For example, like an IPS, IDS, and parental control. So those service function will be created, instantiated by third parties service function manager. So how we can include those service function into the chain? And in order to include those, we have to provide a common API for third parties service function manager to register their service function information so that those service instance instantiated outside of this OpenStack infrastructure can also be included as part of the service chain path. So now I'm going to talk about little bit more in detail about the neutron API extension for supporting service chain. So suppose a user like a service chain from a traffic source to this traffic destination to go through LB, firewall, and VPN. And before on calling the neutron API extension, the user needs to first create those service function instances, create a firewall instance, load balancer instance, and the VPN instance, and also create the neutron network subnet, and then associate those instances with the neutron network. So after that, then the user can specify the service chain specification at this neutron API layer. So this layer is now the intent layer underneath. So there will be two parts of specification. One is the chain path, and the other is a chain classifier. So the chain path will suppose here, the user has created the two LB instances, three firewall instance and two VPN instance. So the user need to specify the neutron port for all these instances. And this information will be passed down to the control plan. So let the control plan figure out what exactly service instance to use based on network proximity, load status on the service function instance, and some other criterias. So besides specifying this chain path, the user also need to specify what kind of flow will need to go through this chain. So that's the chain classifier. So basically composed of a source, n tuple specification, the destination n tuple specification. Here this n tuple could be on any descriptor. You'll say, okay, a finance department is a source. It could be said, the engineering department. So it's not necessarily those network descriptors. So we mentioned before that we also need to provide a common service chain driver API and so that different drivers, so that we do not need to write a service chain driver for different types of service chain API for different drivers. We need to have a common service chain driver API that will pass the information down to the driver layer, for example, OVS driver, so that it can start implementing the service chain path, the data path. So here's a common service chain driver API and then it's very similar to the neutron API except that instead of the neutron port information, it will translate from that neutron port, it's going to get the service functions, locator, information and other information associated with the service instance and then passed it down to the driver layer so that it can set up the data paths. I will also talk a little bit more about the service function instant registration API. So as we mentioned before, this is used to integrate service function instance instantiated by third-party service function manager into the chain. So because the service instance information is outside of the open stack infrastructure, so in order to chain that in, we need to know what information, we need to know the information associated with that service instance. For example, we need to know all this type of information, like what kind of service instance type it is, is it a firewall, is it a parental control, is it an IPS? Also service instance flavor, even for the same firewall, it has different flavors. Also the locator information, the load status on that service instance and also the service instance group for load distribution. For example, you can create five firewalls and they are part of one load balancing group so that the control plan can automatically load balancing between these firewall clusters and also decide which one is the best to use to serve that service chain path. Also the service instance chain correlation method, basically this information need to be collected and passed down to the data path so that the switch knows what kind of chain identification method the service function instance is using so that it can communicate correctly with the service function instance. For example, if it's use vLine to identify the chain, they need to communicate use vLine. If they use the IETF new service chain header, they need to know what kind of chain correlation method is supported by that service instance so that the switch can be properly programmed to communicate with that service instance device. Yeah, so here's the information about this service chain proposal. It's open for discussion. It's not like finalized. So everyone interested in this feature is welcome to join the meeting discussion and then contribute and also post your comments, give your input and ideas. Yeah, that's, thank you, I think that's all. Can I take questions? Yeah, this one, the neutron thing, right? No, no, no. Yeah, here, not necessarily, this neutron port can be identified, can be associated with MAC address or IP address or vLine ID plus MAC address. Okay, so I think here, the neutron port, because currently neutron already have an entity called neutron port besides subnet network and neutron port. So this chain will be based on the neutron port and will assume the user has created a service function and that service structure has attached to the neutron network through that neutron port. But the ways to identify that neutron port could be, it's not necessarily like a MAC address. It could be any address that's associated with that. This is not a classifier. The classifier is on the left side. This is to specify the service functions. For example, in this diagram, it's a green box. So what kind of service function the traffic flow needs to go through? This is used to for specify the service function. In terms of the traffic flow, it's on the left side. So how you specify the chain classifier? How you classify the flow? For example, you say on this engineering department flow need to go through. So that's on the left side, engineering department flow or you say like a finance department or you say a group of people. Yeah, that's what we specify on the left side. The right side, the chain pass is for the real service function instance chain. Okay. But I think maybe... Yeah, different service functions instances will have different ports. Yeah. And do they have to, it can be a cluster, right? But then in order to reach that instance, you need to have a port, neutron port on the neutron layer, right? Because neutron layer, you have a network and then you have all the VMs attached to the network. Each VM will have its own port, right? If you have the same port, then you know, in order to identify with the LB1 or LB2, you need to have a way to identify. That will be virtual interface another. So we need to extend that. If that's because you need to identify the instance, you cannot just say send to all the firewall instance, which, you know, you need to identify to pass that information down to the control plan so the control plan can figure out. Yeah, I think one of the things that creates confusion in this area is, you know, we could talk about layer seven or layer four through seven service function chaining. And what that means is that we use layers four through seven to classify the traffic and understand what source it's coming from. We then use, as you said, pure layer two traffic to steer it through the service functions, assuming they're layer two attached and they're referenced by MAC address. Similarly, if they were layer three attached and referenced, it would all be layer three forwarding. So we're doing layer seven forwarding with either layer two forwarding or layer three forwarding. It's a little confusing, but maybe that's where some of the confusion comes from. Okay. John, can you go to the microphone, please? I think we want to get it on audio. Or we can, we'll repeat your question. We'll repeat your question. Or you can go to the microphone. Can you hear me? Yes. Yes, so my question is about the endpoint groups which you were talking about earlier on. So in this later part, we've been looking at what were classifiers, which were basically looking at the packet headers at different layers. And it seems to me that your endpoint groups are actually a much more useful abstraction than assuming we can grab that information out or anything that's in the packet itself. Because we may have duplication of MAC addresses, IP addresses and all that kind of stuff. So it seems to me that, I guess that's my question. How do you answer it? Yes, I think we're finding that the group abstraction is really important for getting to pure intent. So the intent is that the things in this group behave this way with respect to that group. The fact that there's things called classifiers and layer three headers and layer seven, all that, that's implementation, which by definition is not intent. So we've sort of teased the two apart just so that you can have a pure intent API where you don't have to know anything about how you identify that endpoint. And then there's a separate service which is the endpoint registry or has a name similar to that, which is when you go to actually implement the individual policies, the way that the rendering engine, which is what we use to describe the thing that converts pure intent to the switch rules, the rendering engine needs to know how to classify the endpoint, because that's the thing that's actually gonna see the traffic at an edge, encapsulate it and send it downstream. So we leave the, how do you identify that traffic out of the intent expression? The way you put the whole package together is the intent engine has to go to the endpoint registry, which will then say, here's the mask you use for your five tuple classifier or however that engine behind it is built. But I agree, I think we get completely distracted and we have highly variable information baked into all of our intent expressions if we don't tease them apart separately and that's why it's designed that way. It's a good question. Yes. Well, so the notion is that the intent engine has an interface where you ask it to do things and it either says, yes, I'm gonna do that because I know based on the state of the world that I can fulfill that or it says no, that's an error. Sorry, can't help you. And then obviously there's the case where the network state changes unexpectedly or asynchronously and so there's gonna need to be sort of a callback mechanism as well to say, I promised you I was gonna give you X but the world changed and I'm letting you know that you're no longer receiving that service. Again, I think there's either a synchronous error returned or there's some kind of an asynchronous event that tells you that your promise was broken but I think there's in sort of pure promise theory there's the idea that you don't need any of that overhead because the system will just perpetually try to fulfill the promise which is fairly useless for building an SLA around the fact that it was perpetually trying to give you your SLA values while dropping all your traffic really doesn't meet the needs of most operators. I'm gonna ask you to repeat that once before I try to repeat it. I see. So really this is a data plane agnostic proposal and should support all of the different encapsulated and unencapsulated schemes which really deal with that issue. As long as the data plane bookends the encapsulation and strips it off before it reaches the endpoint, you'll get the original source and desk addresses undisturbed similarly if some other non-tunneling scheme decides to overwrite them, you better put them back before it's done but all of that is sort of orthogonal to this which is really just the control plane proposal and doesn't actually get involved in the details of how you build the data plane. I think we got one more question. Me? Yeah, hi, thanks. So two questions. First is this sounds a whole lot like an effort that's been underway for about a year called group-based policy. Could you please comment on how the two differ? That's the first question. Second question is how are people actually gonna deploy this? As I sat here listening to this, I was just withering under the complexity of what you were trying to describe, not to mention all the complexity that already is inherent in OpenStack networking. DVR, OVS, OVN, holy smokes, who is gonna deploy this? This is crazy. So the first question was how does group-based policy fit into this world and where does it live in this space? And I think the answer is it is one of many different intent-like projects that are being done in the world. And one of the things that we've been doing and I've been pushing through my role as the chairman of the Northbound Interface Group in ONF is to try to get all these projects to work together on a common intent interface in such a way that they can still bind their different implementations to the backend and compete over who can fulfill this API the best but we get agreement and concurrence on what the API is and it's portable across all kinds of infrastructure. So currently in Open Daylight, we're finishing up building an instance of the intent-driven service function chaining where we use the group-based policy implementation as the backend implementation. We're also working on another version of it in the same project that we use the VTN backend to implement the service chain and we expect there to be several others. So group-based policy is certainly a part of this story and fits into what we're talking about but may not be the top layer API that most people see if they're looking for portability. In terms of how you deploy this, what we're expecting is there gonna be two camps that form. There's a camp that says I use an SDN controller which is a smart standalone autonomous black box that hides a lot of this complexity so you never have to know anything about it. You just ask the SDN controller to hook up these magic service chains and life is good. The other camp is gonna say we don't believe in the SDN controller or we can't or we won't deploy that particular packaging so we're gonna do all this using the neutron code that's part of OpenStack and I don't have a good answer to how that's gonna reduce the complexity on the OpenStack side. You're right, it's gonna make a already complicated beast even more so before we're done unless we can come up with some really clever abstractions to hide all of that. But I've probably already shown my cards in terms of which camp I come from but that SDN controller is gonna be really easy. Thank you. Just one last. So let's use the mic guys. So just one request I think after seeing this it would be really good to see a life of a packet or a life of a flow, a little bit more detail as well as looking at some functionality with an NSH header capability to actually show some real life events. I think there's a lot of confusion here that was brought up. Blueprints and such related to the neutron proposal are gonna be discussed in neutron meeting next Wednesday and that that's probably a more appropriate format for the deep dive. Friday. Friday. But the day in the life of the packet probably better for that audience than this one. I think we're a couple minutes over. Thank you all for coming. Thank you.


Everybody forced here up in 2022. I'm act wwe hobby five box case number nine random hit style Type in all the hits and cards as they come out We'll pair some up at the end to make sure that everybody's gonna get at least the hit So all the numbered base parallels will get combined with Hits so there'll be 25 if there's a one of one We'll probably leave that on its own If it's a base parallel because that'll be bigger than most of the just our regular base relics I just FYI Let's get started. Thanks for joining everybody. Good luck Come on bloodline booklet. Yeah, like the Hulkster. All right, first up is a Tyler Bate Base five out of 40 Sheamus relic 52 of 99 Superstar warns. Superstar ones all says Lesnar canvas 82 of 99 From SummerSlam 2022 nice Brock Lesnar 82 of 99 canvas Rookie Otto Elton Prince 10 of 49 Elton Prince Rookie Otto 10 of 49 I can get I can get a beer can relic real quick. Give me a sec Hope we stone colds, but Kevin Owens on the patch auto 19 of 25 Nice Owens three color relic there Superstar warn and say anything else about it. Kevin Owens on the patch auto 19 of 25 Nice one there Noice. Noice. Noice And that's really cool looking all time greats auto Lita 79 of 99. That's really cool Great photo and everything all-time greats Lita auto 79 of 99 Good luck on that one everybody good stuff there for sure Which is kind of surprising Is she? I guess because I heard Mike would know Mike's bigger wrestling guy. Oh Mike's not here anymore is he? All right second one up Would you look at that Tyler Bates 64 of 65 on the base Cool Damian priest relic 24 of 25 Superstar worn Damian priest relic 24 of 25 Do drop jumbo shirt relic 42 out of 50 Do drop shirt relic 42 out of 50 super star worn Yeah, he's a loose like edge. He was like the one heel that I liked as when I was younger like edge I was like, yeah, you edge awesome a redemption memorabilia autograph Natalia Pretty solid one there memorabilia autograph redemption Natalia I did like his entries. Maybe that's why I liked it Very simple when you're a child, you know Relic auto of the miz 38 of 99 That's pretty solid The miz Who likes the miz one of rich or lane likes the miz? I think it's uh rich. I think it is too The miz 38 of 99 I am crying Dusty eyes Next up ray mysterio jumbo relic auto 30 of 99 that's the goat right there Dude, if they get a mask relic It's over. Yeah Superstar worn jumbo relic auto ray mysterio 30 of 99. We'll get that one magged That's what's up playoffs. That's a fact Bruins might be able to lose out and make the playoffs at this point Donny guess which base card this is uh Donny bait Donny is a is a prophet Tyler bait uh two of 65 base parallel I could not believe he got that Well, you saw it here first you guys these. Oh my god. I tend to notice a trend. Donny knows the future Donny, what are a lot of numbers? Please tell me. I'll bet my whole life. I'll bet my whole life. Don't do that. Who's the one that's terrible next year? But what everything I have Nervous we got a An ivar 9 of 99 relic ivar 9 of 99 relic There is there's something in my eye though It's the other eye this time It probably is Yeah, rookie jumbo relic jc jane 37 of 99 JC jane relic 37 of 99 Get into the autos of third box now. We've got the blue meanie auto 97 of 99. What's a blue meanie Who is that? That's a big time throwback right there I never really watched the blue meanie. I just the name is great. Was it gel submarine? Dude what what an autograph to the blue meanie Got a relic auto of ivy nihil rookie relic auto ivy nihil 77 of 99 Dude wrestling wrestling has the easiest autos You just write your character's name. I mean, yeah, that's solid. Do you like canes auto? That's the best just came So great Got a redemption for ronda rousey marks of greatness.  It's uh, ilia draganov numbered four of 10 Oh Ilia draganov four of 10 on the relic Alba fire relic numbered 85 out of 99 Alba fire relic Next is a live morgan relic 75 and 99 the live golf tour Next up is a Oh london wigg kaiser a marcia greatness auto 83 and 99 did not expect to see a london wigg kaiser Well, that's cool heralded signatures eight of 10 kelly kelly That's pretty cool legends auto kelly kelly eight of 10 Dude, I hope we hit a booklet or multi-sig. I'd be pretty sick Might have one up here. Huh? A multi-sig or a booklet. Oh, Kelly Kelly to 10 redemption Dual auto rk bro matt riddle randy orton. Good luck on that one everybody Rk bro Matt riddle randy orton Man, that was like that'd be sick. It's still gonna be sick when she gets in hands now you're asking for uh Uh, timmy Learning he's understanding No, I've been really quiet today Donny sleepy Donny's a day off. No, I'm just I'm just me I was like, you know what today? I'm gonna not ask any questions Here we are on their heels john sena 26 of 65 Should I make a joke about how there's nothing on this card? Donny thought I was funny Good one. Nice seeing a good good uh, good parallel there Relic card shana baszler number 19 of 99 Are there not any dust and I thought there were I thought there were I don't have the checklist up. What am I looking at? I have no checklist up Well, here we are just talking about earlier edge canvas relic 77 of 99 from musselmania 38 night 2 edge canvas 77 of 99 modern marx robert rude 65 and 99 on the auto Modern marx robert rude Next up is a damian priest patch auto six of 25 There we go. Nice damian priest. Good relic there Super star warner says and on the back is a rookie auto of solo sekoa 3 of 99 my solo Solo sekoa rookie auto 1099 good stuff there All right guys, give me just a moment. I'm gonna combine hits here Make it make sense for us. Hmm. Tyler bait. Tyler bait Tyler bait Illya draganov and John say John Cena is the best one of those I would say Even though draganov's 10. Okay. John Cena with I don't know. Tyler Bates is you pretty popular shameless relic Oh him and shameless are boys. So that makes sense We'll do a scene in with the shana baszler relic Same box makes sense. Shameless works out at John Cena's gym The draganov base can go with the alba fire relic Tyler bait two of 65 can go with jc jane jc jane's rookie Go ibar You missed the first one TD Let's see. Damian priest of 25 do drop to 50. We'll go Tyler bait with the do drop shirt to 50 And then Tyler bait to 40 can go with the Shameless relic. Yeah, that's fine Yeah, so I try to keep it in the same box I just paired up with one of the relics in the same box guys.  She had a baszler John Cena Probably the simplest way to do it here. That makes 25. Good luck. Let's do the random a five four and one names first five times One two three four and five Matthew mo down to ryan d and then five times on the hits good luck one two three four and five uh blue mini auto down to the do drop relic and the Tyler bait base Honestly, the biggest hits in that one were redemptions All right, so Matthew mo with the blue mini auto ricky m with the solo sokoa auto Ty and Ludwig Kaiser auto rob h live morgan relic Damian T has a Damian got the Damian. That's interesting Damian T at the Damian priest relic auto Edward P the shameless relic and the Tyler bait base Andrew a remastered relic auto congrats. Andrew. That's pretty sick. Kenneth h ivar and Tyler bait base Um ivar relic ty and Damian priest relic ryan d jc jane relic jason b Orton riddle dual auto redemption cratch jason braiden k with elton prince auto james h robert rude auto jim j Lita auto to 99 congrats with jim. Matthew. M. I with an italia redemption Salsi brock lesnar relic ty and the miz relic auto priest odd one there jerald a with the edge relic Eddie h albu fire relic and ilia draganov base um Matthew g shanna basal relic and john sena base jesse s ronda rousey redemption nice one jesse chris m Kelly kelly auto to ten. That's pretty cool too ty and kevin owens relic auto Brian g ivy nile relic auto and ryan d with do drop relic and the Tyler bait base Get the results posted. Uh, thanks again everybody one more case coming up


Hi, in this video I'm going to go over the basics of using Miro. Miro is a great digital whiteboard app that allows you to run workshops remotely and it has everything that you would need like sticky notes and voting dots and I'm going to show you the basics of how to use it right now. So this is an example of a Miro board and you can even get started without creating an account if someone shared a link with you and this is what you would see when you first open it up or something like this. So I'm just going to dismiss this getting started guide and take you over the five basics that you really need to know to use Miro proficiently. So the first one is panning around which just means knowing how to move around the board left and right up and down and to do that if you're on a trackpad on a laptop you simply scroll in any direction to move in that direction. If you're on a computer using a mouse or keyboard you just hold the space bar and you see this hand icon and then you can click and grab to move around. The second thing you need to know is how to zoom in and out that will make it easier for you to read something that is small or zoom out to see the entire board.  If you're on a computer with a mouse and keyboard you can just scroll on your mouse wheel and that should zoom in and out. Additionally you can hover over this area here near the bottom right and click the plus button to zoom in and the minus button to zoom out. The third thing you need to know is how to edit a sticky note. If you're part of a workshop then chances are you'll be working a lot with sticky notes so to edit a sticky note all you need to do is double click and then start typing words and this is where zooming in and out becomes very useful so that you can make the text larger and focus on the sticky note that you're typing. The fourth thing you should know is how to move objects around so like sticky notes or voting dots and to do that you simply click and drag to move the element so you can move a sticky note like this or you can move an image like this and that's pretty much it. The last thing that's useful for you to know is how to use the raise hand feature that way if you're working with a facilitator you can let them know that you need help and the way you do that is from near the top right over here you click on reactions then you click raise hand and you can lower it once you're done and as a bonus sixth thing you should know if you do something accidentally and want to undo it you can simply click the undo button near the top left or just press command z or control z depending on your computer to undo that action. So those five things are really everything you need to get started using Miro. Thank you for watching and I hope this helps you get started with Miro. See you next time!