All right. So I feel like there's a lot more to talk about than originally planned. I'm just gonna get my self logged in here so I can read the comments. Okay, perfect. I really don't know how to do this stream right now because there's a lot going on. So it looks like what I thought was the media having early access to releasing the video turned out to be actually one of the new sites in Canada actually stealing it from someone and pre-releasing it. So we're just waiting for an update on how to handle it. The stream I was actually just gonna show you the screenshots of the ride and all that, but I'm not gonna do that anymore just in case. The video will stay up until we are told to take it down. And if the park wants us to take it down, we will take it down. But yeah, we'll wait until that. So I will answer any questions about the ride though. So if you guys wanna talk about it, get my opinion on it. I will talk about it because we didn't leak the ride. We've done nothing wrong. It was actually a major news outlet in Canada that did it. So it's not like it's like a big leak like that. So I'm gonna try and answer your questions in the comments section about the ride. Feel free to ask me anything about the ride. I will talk about it. I guess what do you guys think about Yukon Striker, the name? Is the announcement tonight? It looks like it ended up being tonight, unfortunately. I mean, Wunderland's really lucky in this case. I mean, Cedar Point has their rides leaked sometimes years in advance and Wonderland got to get up to seven hours before announcement or something like that. I don't know how close we are. Like seven hours away now? Yeah, seven hours away. By the way, my admin team is like here at my house as well. If you hear someone talking in the background, we are all going to Wonderland tomorrow. I don't have a question for the ride, but to go on early rides tomorrow, do I have to have it? Yes, you do have to have a 2019 season pass. If you can't get into early ride times, we will be there all day, so come hang out with us still. The name is fine. The name isn't terrible. I just, I wish it was a bird. The park definitely tried to throw us off with their teasers then, with the eagle and all that. So that's funny. Maybe there's more to announce. The Giga and the teaser poster. So definitely some red herrings. Is the drop bigger than Leviathan? We don't know yet. So this news site that posted the information stole the POV and they don't actually, we don't know how much they stole. The ride renderings kind of confuse us a little bit because it looks like it's about three-fourths the height of Windseeker. So we don't know if the coaster is actually 246 feet tall, which nothing suggests it would. So at the moment, I would assume the drop is 246 feet, by the way. Just for those that like to twist our words, apparently we claimed this was gonna be a Giga. But yeah, okay, I'm gonna try and answer these questions as quickly as possible, because they are coming in our discords off the roof. I was hoping for Thunderbird that's taken though, Yukon Striker, hashtag Yukon Striker. Do you think it's going to be the Bestive Coaster? It is hands down the Bestive Coaster. I'm sorry, Cedar Point fanboys can definitely attack me for my opinion, but this is unique. It's got a larger drop, which is the most important part of the dive coaster, and it's got a really awesome layout. So come at me all you want, I totally understand. The name is a bit weird. I get that Striker part by Yukon. What is that? So Yukon is a place in Canada. It is a Gold Rush kind of area. It's a pathway between Alaska, I believe, and Yukon too, the theming that they're going for. It was definitely a Gold Rush area that both America and Canada kind of benefited from. How's your admin team? They are great. How are you walking by? I'm doing great. Why is Yukon Striker getting so much hate? Yukon Striker is getting a lot of hate because it's different. It's a dive coaster. Enthusiasts tend to not like dive coasters, and that's totally understandable, but it is an amazing coaster. This is what Canada's Wonderland needed. I think Cedar Fair hit it out of the park. We needed a looping coaster, and they delivered with also a GP magnet. So, great job. I couldn't be more happy. Is Yukon Striker the worst names in SteelCurt? No, SteelCurt still has that. Kind of maybe Ziz will be in the future. I don't think Ziz is going to be in the future. The park is definitely going down a Canadian route. How steep will the drop be? The drop will be 90 degrees, but again, everything will be released by the park tomorrow. Nothing is confirmed until the park makes their announcement. This is all still speculation. Despite the layout and the POV being released. So, the park will be releasing their information at 5.30 in the morning. Maybe they were lying. Okay, thanks. That's how I'm walking right by, I love him. Yes, you needed a 2018 season pass for the early ride time tomorrow. The live stream, we will not be hosting a live stream tomorrow at 5.30 in the morning. We'll be posting videos, and then we'll be at the park first thing tomorrow morning around 8.30 in the morning. Again, come hang out with us. I think Ziz might be safe for another attraction. I don't think, there's nothing to prove that at the moment. I feel like that name isn't the best, to be honest. I agree, I agree. It's not the best name, but in that tunnel is 30. That means the coaster is three feet taller than Val Raveman. We don't know yet. We don't know. Wait for the details tomorrow.  The ending is definitely weird. The mid-course brake run being, so if you guys remember, how did I describe the ride? I think I described the ride as Val Curia and Val Raveman had a baby. So hopefully you guys see what I was talking about when I said that. This ride definitely screams Val Curia and Val Raveman had a baby. I hope, hopefully you guys see that. Comment down below if you disagree or agree. Is this becoming 2022? What is your opinion about the name? I think I said it. It's not the best name, but it's okay. I love the colors. I actually really love the colors. Next news story. Ken is one that's suing new site for $3 million. So yeah, this ride is now sponsored by that new site that leaked the coaster. It's a 90 degree job, fully 90 degrees. Yeah, is there no live stream? Yeah, the live stream is canceled tomorrow morning. There's no point to do it at this point. We were actually gonna do what we're doing exactly right now, holding like a question period about, basically, we were gonna release the POV and the animations and everything. There's gonna be more videos, by the way. There's a bit more to the announcement, but now there's no point.  Is the only announcement for tomorrow? No, Yukon Stryker is not the only announcement tomorrow. There is more. Something else is coming, yes. It's not gonna be a coaster, but something else is coming. Teasers aren't meant to tease us, exactly. So cameras on carowins hit it right on the dot and we are definitely guilty of this, over-analyzing teasers. Teasers are not always meant to be taken seriously. There are definitely red herrings in there and they definitely threw us off with these teasers. And there is no shed now. 30 million is the cost. It's definitely gonna be very expensive. Yukon is a territory. Yes, you're right. Yukon is a territory. Well, it looks like it has vest restraints. The park has made some comments on it being leaked. We are in direct contact with the park right now. Again, if they ask us to take down the video, we will honor that. They have not asked us to take down the video yet. I wish they themed the tunnel. The tunnel is themed. It doesn't show it in the video, but it is themed so far. So stay tuned for that. Maybe it was a very poor quality rendering, so everyone will be releasing the higher quality renderings tomorrow. Hopefully the park sends out a high quality rendering. The dip right after the loot reminds me of when you don't probably smooth out the track. Have to go to bed. Have a good one, Jake. Just checked. It's not the Canadian trademark database yet. Yeah. Usually they don't post things until a little later. Again, the coaster has eight seats. We knew that all along. We were speculating if it's a giga to have six seats though, just for forces. It uses people. I like the name, but now the color doesn't really match up. Just wait. If you see the color scheme in person, it's gorgeous. Don't worry. It's there because it goes through a forest. Enjoy the park. Thank you. I'm wild eagle at toilet. Maybe, I don't know. This is really unique. I'm excited. I'm really excited. I mean, Canada's Wonderland did a really fantastic job with this coaster. I do visit the park every day. Yes, I have no life. What's the world's longest MCBR? Leviathan. Leaked POV. Yes, we have the leaked POV on our channel. Go watch it and share it, please. Who wants to ride the ledge? Yes, this ride was never going to be called the ledge. We knew that, but we also got the name wrong too. So we can't comment on that person getting the name wrong either. They teased the loop with the sky rider. Yeah, they definitely, yeah, they did. I liked the teasing campaign, to be honest. Is the name confirmed or just still speculated? Nothing is confirmed until the park says so tomorrow, morning at 5.30 in the morning. What's your favorite McDonald's item? A junior chicken or a Diet Coke? Say cream sodas. Cream sodas. They also have the record for world's longest brake run. Yeah, twice now, right? I'm kidding. Now the human looks even smaller. I live in North Carolina. Well, aren't you lucky? I wish I lived in Carolina. They have the better park. It was told in the behemoth, right? I don't know yet. So there are a lot of facts this new site did not release. So we have someone running the speed with the projected length of the lift hill to figure out an actual height. So I'll post on Instagram if we figure that out compared to Valkyria. This is better than Valkyria. I mean, I get it. A lot of it to a lot of Americans, this coaster looks just like almost like an out and back looping coaster. Sit down coaster by B&M with dive coaster trains in a 90 degree job. I get it. But to us Canadians, it's the first custom looping coaster since 1981. It's got a 90 degree drop into an underwater tunnel through vortex. It's got a zero G roll, which we have not seen in our park. And it's got a wicket looking station from what I can see with theming and a storyline. And the park needs that. So for any Canadians, this is like the best thing that could happen to us. And for Americans, this is like any other Tuesday. I get that. I get it. But definitely just maybe lay off the hate a little bit and let us Canadians really like revel in this awesome news for us. This is a fantastic coaster for our lineup.  So that's awesome. Moves are hard to detect in blueprints. Still current and you come straight here. So yeah, again, everyone doubting that we had blueprints. I'm sorry. If you still doubt that we had blueprints, you'll find out tomorrow we have the blueprints. You can tell by the layout that they just posted in this video that we were pretty close. We were like 90% there. If I had, I would say we were about 90% there. I think the vertical loop we got wrong and a couple other elements, we didn't see the trench because you can't see trenches. But we got it about 90% right. I'm sorry for those that think that we're gonna be 100% right all the time. We're not. Again, we had the Kennywood blueprints and we didn't even know it. If it's the exactly who cares the same thing happened to Valerie even exactly. I wonder what they're getting in 2020. Will you be live streaming at the park tomorrow? Yes, we are bringing battery packs and everything to film and live stream at the park. I'm not writing any rides. I'm filming reactions from Canadians about this attraction for a really cool video we're gonna work on. And we are starting our documentary on the coaster tomorrow. So we are officially allowed to start filming our documentary on the coaster just because we have so much footage of this coaster that we thought what better way to use it than make a documentary. What's the name again? Yukon Stryker. No hate. What time will you be there tomorrow? We will be there at 8.30 in the morning till pretty late. I'm a pretty big guy and strong heat and all that. I'm gonna get wiped out. So who knows? I'll try and stay there all day. How's the Yukon theme? My team will be there though. If I'm not there, they'll still be there. And my team is cooler than me. So they ride rides. I don't know if it's taller than Behemoth yet. We'll find out soon. It does not have a splash down from what we can see. Yeah, the vertical loop is definitely unexpected. There's no shed. I wonder what can this next closer. And RMC would be great. I agree it would be great. I think we're gonna see another B&M though. I kind of wish it was a wing coaster. I think a lot of people wish it was a wing coaster but I think this looks like a wing coaster layout minus the 90 degree drop. Would you disagree? I think this looks like a wing coaster layout. It almost looks like a smaller gatekeeper. Yeah, it looks like gatekeeper and wild eagle had a baby and then Val Raven kind of got jealous and then came in and was like, no, no, this is mine. And then Valkyria gave it a little bit of an influence. I don't know. That's my take on it. Do you like the layout? I love the layout. The drop is 75 meters. Yes, that's what we know so far. But nothing's confirmed until the park releases it. The name is definitely better than Val Raven. I like Val Raven. I don't mind Val Raven. Is the Canadian theming part of a five year plan? From what I'm understanding and what I've heard the Canadian theming is part of a much bigger plan than five years. They're trying to become literally Canada's Wonderland. This is the strata Wonderlands getting for their 40th anniversary in 2021. Oh, what do you think about the vertical loop on a dive? I wasn't expecting it. Again, you know that because you didn't see it in our prediction layout. And again, we always said prediction layout because we didn't want to come out and be like, yeah, we have the blueprints. Here's what it's pretty much going to do. But as you can tell, and when you see these blueprints, when we make that video and you see these blueprints, you're going to see how we struggled to figure things out. And remember when we thought there was an MCBR after the emerald loop? You'll see why. There's weird things. I think we'll put a wing coaster around mighty Canadian. I think we'll eventually get a wing coaster for sure. I guess 301 is pointless now. Wait for tomorrow. Again, we are looking into things because the renderings are a little confusing. CBC ruined it. It wasn't CBC's fault from what I understand. Another party was involved that ruined it. The park will probably be busy tomorrow, but we will be there all day. I won't be riding rides. So if you just want to come say hi or get yourself, again, we're going to be filming a video. So if you want to be in the video, come say hi. If you're under 18, please bring a parent. So I can get permission to have you on our channel. The announcement is not being broadcasted anywhere, but every news network from what I understand will be announcing it and every YouTube channel will be announcing it. No, Canada is one of those. Not the test site for Cedar Fair. I actually think Cedar Point is the test site for coasters and Wonderland is the test site for flat rides. This ruins the announcement. That you have been talking about. The Alma that we were talking about was definitely the zero G roll that we weren't expecting for Canada's Wonderland. I get it. Americans are like, what? How are you not expecting that? There was a point in time that we thought it was a zero G stall, though. That was why we were like, oh, a secret element. Two more weeks for announcement for Carolins. It's only a bit of them Valoraven. Yes, it's way better than Valoraven. I'm sorry at me, whatever. When you get a whole layout before an MCBR. No splashdown. No splashdown. A splashdown would stop that ride so quickly. Steel current versus Yukon strike. That's a tough one. I'll have to ride both. Oh, there's so many questions. I was saying, compared to Windseeker on the website, it says the drop will be 246 feet tall, meaning that it's not that tall. Yeah, and that's what I'm predicting too. It's just the angle too, could be throwing things off. Golden Eagle would have been a better name, I agree. Sad phase. Will it smell nice? Hopefully. Yukon Stryker, it doesn't mean anything. We looked it up. It has no meaning, confuzzled. I have no idea.  They're fun and all, but once they announce stuff and people think it would be better, but it could, it's a poor marketing scheme to actually, and I took marketing and business. It is a poor, poor decision to over height something in your teasing campaign for anything. Even a business that's like selling coffee and they're advertising a new product and they over hype it. It is a very bad decision. So doing certain things can be bad. I do think that Wonderland didn't really cross any lines, though. So it's fine. The Giga on that poster though, a little confusing. I assume she's hoping that Giga, maybe she thinks the Giga is over 200 feet. Grace Peacock is an amazing person. My comment fee just glitched out, so I'm trying to figure out where it was. I don't think it'll have the highest inversion. We'll find it tomorrow. Again, the rendering is a little weird and the fact that the site that we're all getting this information from stole the information. I just wanna make sure that it's correct before we comment that it's solid. The POV is real. The information, it cannot be confirmed real. The beast is one big MCBR. What do you think the name should have been? I would have liked Golden Eagle. Gold Rush or Zizz. Why break around so long? Imagine the emanation is fake. Animation is fake, it's not. Oh my goodness, 137 people watching. Or essential. We're not doing 5.30 in the morning tomorrow live stream. We will be posting our videos, the high def ones hopefully, and any information that we missed. How long will the wait be? We are hearing the ride will open in April. The ledge, I don't know, I just, I never saw it and the fact that it was trademarked in the U.S. I knew right away it wasn't for us. Behemoth and Leviathan weren't trademarked in the state so it wouldn't make sense. Yes, I've been to Cedar Point. Good job. You have been doing a good job. I wish your channel was the one that showed the video of the ride. I wish so too. Why didn't they name it Despacito Striker? Actually the best vertical loop on a dive coaster. What's your favorite thing at Tim Hortons? I don't drink Tim Hortons, but if it was an ice cap, is the ride really announced? Is the ride really the announcement? No, there's more coming. So there is more to announce tomorrow. Don't expect too much. They're not announcing another coaster on top of it, but I'm expecting the Hotel Gulbaz Winterfest and all that. Maybe Hotel. I don't know if they're gonna announce it two years in advance. Thanks for liking my edit on Insta. It took lots of time. Trying to catch up. Here's a Eurofighter. Kind of. Yeah, actually that's a good description. Canada isn't real.   Yeah, they just need to scrap the SLC and the Dime War. What do you think this should have been? I think it should have been Golden Eagle or Zez or something. I think I've seen on a coaster. I'll have to go back and look at it again. I haven't really watched the video in full. I've watched it once. I haven't gotten to really dive in, unintended, deep into that and figure it out. Amazing world-class coaster. Please, please, where do you find the video of the coaster on our channel? Just watched the video. We posted it like an hour ago. Brian H, I hope you enjoy it. Coasters are definitely a wonderful thing. I'm super excited for other Cedar Fair announcements. I'm actually really excited for the Six Flags announcements as well. I really want to see. I think we might see some more custom coasters coming to Six Flags this year. Thank you, cameras on Carolyn. So yeah, I definitely agree. We obviously got the giga theory wrong, but there was definitely information to go off of to think this coaster was gonna be tall. Again, people were reaching out to us as sources, things we were seeing, we're suggesting it was gonna be a very large coaster. And I mean, were we technically wrong? We got the height or the drop wrong by 50 feet if you technically look at it. Like we were off by 50 feet. Yes, giga as a whole sounds crazy, but if you bring it down, we were off by 50 feet. One out of 10 times I went to the park. Where are the blueprints? The blueprints will be leaked tomorrow and so-called screams, if you still don't think they're real, you are definitely mistaken. The layout is essentially the same, very close to the one we leaked yesterday. So you need to get over it, hashtag the ledge. Also a certain other site needs to get over the fact that this isn't going to break any records in quotations. You definitely got that wrong as well. And so-called screams, we never said we were gonna leak anything. There was a point in time that we were, but we decided as a team not to and we made that public to our patreons and all of our followers on Instagram and YouTube. So it would definitely be Steel Vengeance or Maverick or El Toro. The comments don't match the audio. Yes, cause I'm trying to keep up. Is there a delay? Okay. Okay, I'm gonna skip over. I'm gonna try and catch up then. Oh my goodness. Okay, so yeah, I can see why. I just literally scrolled down. Chris, you can block SoCal screams from commenting. Okay, perfect. Do you think there will be fog effects in the tunnel? Hopefully. I really hope so. Hi, I'm Chris to Crystal Lay. Hi, that tunnel needs more theme. And yes, hopefully. I mean, we don't know all the information yet. We'll find out more tomorrow. I like how the color scheme is apparently the same as Skyrider was. Yeah, I agree. Brennan, do you have a sister? I do. Hi, I just joined. What's happening? We're just talking. I'm answering questions about the coaster leak. So if you go on our YouTube channel and watch the video that right before this stream, we leaked the, well, we didn't leak. Someone else apparently leaked. We didn't know. The POV of the new ride. Biggest news of the week. Universal opening up the Aventuria hotel. Jovey, it was the big news. The ledge is coming. It's coming. The Panfari strata launched wooden tenant version inverted coaster running SLC trains to Michigan's adventure. How do you know it's an SLC? One is Six Flags announcements. I think August 30th, but I do not know. So don't quote me on that. Can we get an F in chat for SoCal Screams? MSN, our party poopers. 246 is the height, hopefully. Yes. Oh, sorry, I said yes. I mean, it looks like it's the draw, but we won't know until the park makes an announcement. I think two of them will be the year can is when it comes out and we'll receive a much higher annual attendance. Yet this is going to draw a large crowd, but so is Carolin's. I'm super excited for Carolin's announcement. As many of you know, I've always said that the map coaster will definitely win best new ride over even this dive coaster for 2019. The name of the proposed hotel is Hyatt. H-Y-A-A-T, or H-Y-A-T-T. H-Y-A-T-T, I think it is. We actually have a video. If you go down on our videos, we have leaked pictures of the hotel a while ago. Is Cobus, no, Cobus will be at my house tomorrow. The admin team is gonna be at my house tomorrow. Say hi to your sister for me. Oh my God, she's probably watching. Is it 222 feet? We're not sure yet. We actually have someone running some numbers with the information that was given to us to figure out the height. Evan is doing that, I believe. Oh, I can't even keep up with comments. I'm struggling. Like what part of the park, you know the height or have an estimate. We never knew the height and we never said we knew the height. We were very honest all along. We did not know the height. We knew the layout for the most part. Obviously we got the vertical loop wrong, essentially. And some of my team thought it was gonna be foreign version. So the whole team didn't think it was gonna be three. I thought it was three. So throwing myself out of the bus. So obviously we got that wrong too. I did not think they were gonna take the inversion record from Val Raven. Getting a gig in 2020. Again, yeah, giga in the teasers. We don't know the height, but it's height of the drop is 246. Okay, yeah, I saw the stuff and it's unique. It's 30 feet plus. Hello, Thrillscentral. Hey, Thrillscentral. Hi, it's Wonderland will not win best coaster for doing not even close. I agree. I didn't say that either. Kamen's got me shook it after this. What's the height? Wait, 75 sounds right for the height. Can you ask him? Just clarifying the height information based off of the speed and the angle is what we're doing. Again, if we give you a number in this stream, it is not clarified. It is speculation till the park makes an announcement. You know what I mean here. It's lucky that it is your fave Wonderland ride, Behemoth. It was probably meant to be the tallest inversion until Steel Curtain. Man, you guys are really asking questions. I apologize. I'm not able to answer all these. I really try. Again, if any of you are in Canada or near Wonderland, come hang out with us tomorrow. I'm not gonna be riding rides. I'm gonna be filming. And you can ask me as many questions as you like and pick my brain. I'm definitely gonna wrap this stream up shortly. A, because I need sleep. And B, we're super hungry. I'm getting the food symbol from walking by over there. Fave Flat Ride. Definitely Skyhawk or Lumberjack. It's a toss up, but Skyhawk right now. I have world's most, I guess Behemoth is better than him. Well, I'll definitely announce the height once Evan gets back to us in a second. I wanted it over the shoulder restraints, but from the POV, it looks like it's gonna be best. Thank you, Fina. Oh. Okay. Where is it? So he's saying that 75 meters is probably the height and not the drop. I'm sorry, guys, stay tuned. We're trying to figure something out. Let's just go with, okay, so 75 meters, 246 feet, is either the height or the drop. The site that stole the information didn't have all the information, if you noticed. So they might have posted 246 feet as the drop, but it might be at the height. I'm gonna stick with the drop to save over promising anyone at the moment, but using the speed with the angle of the left hill and the friction and all that, you can somewhat get a better idea of height. So this widow line with what we were told of 280 feet, that might be the drop if that's actually possible, but we're not gonna get into it. 246 feet is a drop at the moment. We will find out, again, maybe this just helped wonder, maybe Amusement Insiders just saved Wonderland. They have their announcements from about 5.30 in the morning. They will announce all details on the ride. You'll find out if 246 feet is the drop or the height. It's gonna be a gig at, no. Oh my God, after the announcement around going on vacation, I'm definitely getting beer at Wonderland tomorrow. I'm kidding. Hey, it's turning for its feet that M1 could be nearly 200 feet. That'd be amazing. One foot drop, no, it's not. Talk about Valley Fair, talk about Valley Fair. What's your sister's name? Oh no, her name's Shannon. When in the park will you be interviewing people tomorrow? All day. Again, we have battery power to last us forever. So if you wanna be in a video reacting to the ride, again, we do ask that we'll be monitoring the reaction so we're not gonna be putting in just anyone's reaction, but come hang out with us tomorrow. We're all in Amusement Insiders gear, come hang out. We are not just there to talk to you and then leave. You can really hang out with us all day. Do you believe in the Raptors? Yes, I do. Do these. So we thought when they made the announcement 5-3 in the morning that they were going with the premise the early bird catches the worm. Like that's what we thought it was with the whole bird. What is the 5-30 clue? Maybe 5-30 is actually the announcement time, like Wonderland. I'll be sending you a face reveal reaction. That'll be popular, if they're essential. Maybe we could both do one. And now I've shown my face on Instagram. Five, two, four, six is the height. Let me find you tomorrow. We'll be there early ride time interviewing park management about the attraction for a video. And then we will be wandering around. If you can't find us message me on Instagram, I will try and respond. We actually have a very large group of people wanting to meet tomorrow. We have a couple of people coming from the States, which is crazy. Yeah, so come hang out with us. I'm not riding rides. So if you just want to talk to me or hang out, I will be there filming. Or my team is going to be riding rides. You can go ride with them as well. There's gonna be a lot of people. So it'll be fun. We'll just celebrate this awesome new attraction we're getting all together. Do you and Thrill Central have beef? Not at all. Not at all. Thrill Central is actually really cool. I think we both understand each other. We're very similar. Channels and I think we're very down to earth people to not have beef together considering we have the same channels. And actually maybe we'll have some collaborations. I was gonna come up for the announcement but I have school stuff. Yes, school is more important.  Work's more important too. Oh, if this takes the inversion record from seal current, my depression will intensify. Oh, I don't think it will. Don't worry. Unless it's 280 foot drop. Great adventures getting a giga. You heard it here first, oh God. What do you think about Coaster Studios? I think, pinfari question mark. I don't know what to say about pinfari. Vest restraints, yes. Where's RageBob? I would have rather seen a dive loop for the turnaround. Yes, I thought, we thought it was a dive loop too but again, you can tell that it's very hard to predict that. Let's go circuit my depression. I'm very happy with how this turned out. I was gonna come but I need to be on that Fortnite grind. Where are we dropping? Great adventures getting a statue of Brennan that is speculated to be a giga. I left my window open and my head room is filled with fog. What the heck dude? Wow, that's kind of scary. Best coaster in the world. So far, steel vengeance. I have not been on the voyage or El Toro yet so I can't unbiasedly say it's steel vengeance. So take that with a grain of salt. Rebirth of son of beast. I don't think son of beast is getting a rebirth. I think the lore of son of beast is getting a rebirth. If that makes sense to you guys. Will they announce what's getting removed from all potentially? If something is getting removed. El Toro is great. I hear it's great. I hear it's great. And I actually have a lot of people and have a lot of friends that have written El Toro on steel vengeance and a lot of people are saying El Toro is still better. Not to trigger anyone. I haven't done it yet, but I am hearing. Costa studios is the shade. Dinosaur is alive is closing. The voyage is my favorite love holiday park in general. I get that a lot. I hear that a lot. I hear El Toro is better than steel vengeance and then I hear the voyage is better than El Toro. It's not a giga guys. It's not. Do you think they'll remove the orbiter in the bare future? Definitely the bare future. I'm not so sure about the near future. We'll have to wait and see. I'm kidding. What do you think the next coaster? Canada's Winnipeg will get are either a GCi RMC or a Wing Coaster, right? I definitely think the kids are gonna get something too potentially. Valley Fair Invert for 2020. Who knows? Valley Fair is definitely up on the list now. They are an expansion park if you saw my 2019 predictions. Have you been to Hershey Park? I have not and I heard it's an amazing park. I'm doing a lot of parks next year, by the way. In 2019, I am definitely probably gonna hit up a lot of the major parks. Triggered. A road steel vengeance in my neck gut again. Me too. I actually was in a lot of pain at the ending of that ride, but I'm a bigger dude. So that's my fault, not the ride's fault.    But at no point did we say it was going to be a giga, right? We were just talking about, we were seeing things suggesting the Coaster was gonna be tall. I mean, did it not turn out tall? Turned out tall, it turned out a lot larger in terms of drop. We were off by 50 feet with the 301 speculation. So I mean, it's not that big of a deal, but no, I'm not offended. I mean, deep down, yes, I'm offended.  I'm doing as possible that the name isn't Yukon Stryker. I'm hoping, I'm sorry, I'm really hoping it's not Yukon Stryker. Will they add such hammer to other Cedarford parks? No, unfortunately not, it's had too many problems. Closing joint right now. Okay, I feel like I have to catch up with, oh, I'm actually pretty caught up. Go to Silver Dole City, yes, Kenny Wood came out with the curtain, but his foot came out from under the lake. Can't beat that. Make the waterfalls on Wintermont into a log room as a 90 degree job. I almost fell down the stairs. That sounds relatable, that's a mood. When do you think the ride will open to the public? We're hearing April. Stay tuned tomorrow. We are actually hearing that the park, and we don't know this for sure. So amusement insiders like quote here, take that with a grain of salt. They may open it earlier than they typically have. They hid, it was a strata very well. My spinal cord, 2018 steel vengeance. You constrictor takes the airtime record from steel vengeance. How many trucks are coming into the park? There is a truck coming every day with track now at the moment, and they're adding a third driver actually very shortly. Talking to the drivers is really cool. They don't know any information, so no, they did not leak anything. They're just cool people that deliver the track and like to have a conversation because they sleep there overnight. Says the Giga Wing Hoster. What would stand up SLC be like? It would be painful. Back barren curve. I miss that ride actually. I also miss like the Great Whales of China, if any of you remember that, is not a thigh, Skyrush is not a thigh crusher. I know a lot of people that love Skyrush. What are the seat restraints on Valraven? They're vests. Gatekeeper Valraven, they all have similar restraints. 2019, the year of bad coaster names, retweet. Thanks so much for all the updates leading up to today. It's been a fun run. Can't wait to follow all the construction updates in the coming weeks and months. Yes, the drone is ready to go. The weights aren't too bad at Wonderland. It's definitely worth going. I mean, they're busy, but they're not like in the Stanley busy, the kid's section's very busy, the water park's very busy. Yes, they've been to center islands, and yeah, that's the last time. Vest restraints, in my opinion, because I'm a tall person and I'm also bigger, definitely ruined coasters. When was your first visit to Wonderland? Oh my goodness, I think 1992, 1993. I have my season passes still. I forget which one I had. It's okay, Phoenix. Smurfs blue ice cream revival. Where is your hometown not trying to be creepy? I am from Aurora, even though I really don't think I should be giving out that information, but I just did. He could have said the idea and tomorrow you see me murdered. Oh man, I'm gonna wrap this stream up very shortly, guys. I'm really honored that you guys even want to ask me questions right now. Like thank you for joining in on this journey of speculation and now we're gonna turn speculation into construction updates. So thank you so much for following along. Thank you so much for growing the channel so quickly.  We were not expecting this. We were like, oh my God, I'd be sick if we get to 2,000 subscribers by the end of the year. And now we're like past 6,000. We're at like 6,200 now as of like right now. Thanks to you guys. Like every time you share a video, like you help us out. Every time you like a video, you help us out. Every time you comment, you help us out. Like thank you so much because it honestly means a lot. And it's helping, it's working. Thank you so much. Like honestly, thank you. Again, do you get a season's pass every year? Yes, I get a platinum pass every year. I work at the park. Lucky you. Jealous, actually. I love Wonderland. What's your thoughts on the Fastlane passes? I love Fastlane. I mean, I use it here and there. I don't get it every time. But if I go to see your point, I'm definitely getting Fastlane. In Aurora, Missouri. Like different universes. Did the live chat die? Yeah, I think I've answered everyone's question. So I think I'm gonna end this live stream. Again, thank you so much. I'll be at the park tomorrow. Join me. We'll be doing live streams in the park. We'll be recording all day. And thanks so much for joining me on my journey. Have a good one, guys.


Miles, the state governor, Senate of Doi, Deary, his son, the state's 2024 Appropriation Bill of $489,443,632,374 into law. He expressed optimism that a careful implementation of the budget will improve the living conditions of the people and address rural and urban poverty. Carefully crafted this budget to prioritize key sectors aimed at improving our infrastructure, expanding access to mass education with emphasis on technical and science education, enhance healthcare services, and promote agriculture. And together I am sure we can achieve the sustained and shared prosperity that we have been preaching about. The Biosha state government now has the authority to not only to generate and distribute, but also to commercialize. To all the private people who have been approaching me before now, knowing that we have the primary resource of gas in Biosha states. And so you are now under pressure to bring private investors. We are sorry you have taken serious oversight functions to work with the various ministries, departments, agencies to ensure effective implementation, just as we did with the


Personal notice, dangerous my stock and trade. If the job's too tough for you to handle, you got a job for me, George Valentine. Write full details. Greetings, friend. Time again for Let George Do It. Oh, which reminds me. How would you like to sit in on a nice little card game? I happen to know four charming fellas who are just dying for a fifth. On the other hand, though, maybe you'd better forget about it, because these boys would not only take your bankroll, they'd just as soon take your life. But it's a pretty good game at that. So while we're waiting for George Valentine to show, let's take a look in on this happy foreson. Well, it's ten o'clock already, gentlemen. Shouldn't we... I mean, my watch says ten. Chester has the cards and... Sure, what are we waiting for? We're gonna do it. Let's get... No! No. Ames, Salto, this is crazy. It's insane. Was your idea, wasn't it, Norton? Yes, but a man's guilt is no more to be bandied about. I'll get off the words. There's the good name of the man to be thought of afterwards. Let's get it over with now, now. It's all right. Need a piece of paper. Unvelop here in your jacket, do you mind? Of course I do. It's got my name on it. Valentine. George Valentine. What? Oh, your wife's letter from somebody named Valentine. If I'd know her friends. Here, here's a blank sheet, club stationery. Couldn't we get on with the... Dear Mrs. Ames, I'm so sorry to hear of your concern over your husband. Naturally, I will do whatever I can to help. Sincerely, George Valentine. Me either. Concern. How do you like... I haven't sakes up the stalling, both of you. Will you get... All right, I draw one.  Me? Go on, Salto. All right. Nine of diamonds. Yeah. Norton. Nine of clubs. Nine again? Give me one of those. Jack. Diamonds. All right. Chester. Chester. Your turn. Draw. Oh, I'm all right. Draw. Yes. King. King of hearts. Look, Chester drew the king of hearts.  You understand, Chester. High card. Yes. Yes, the paper. Here, here. You can use the pen there. I'm all right. Hi, Jeffrey Chester. Hereby confess, one year ago to this date, it was I who murdered Miss Dorothy Fullman. After 10 o'clock now, Chester? I'd like to have a drink or two. I'll have to run down to my boarding house. There's a bill I should pay. The watchman's bare gun is in the locker room, and it would look better if you did it at the same place that... Leave him alone, Salto. I'm all right. I could run down town first, then come back, have the drinks if I could borrow your car, Mr. Ames. Sure, Chester. Let's go over and get you my car. Sure. Thank you. You can mail my confession of guilt to the police. I got the high card. I'll be dead by midnight. You are listening to Let George Do It. Our adventure will continue in just a moment. Now back to George Valentine and Let George Do It. Sylvia, it's a big idea that letter in my coat pocket. Miss Valentine, who is he? Oh, there you are. So sorry to hear of your concern over your husband, of all the meddling... This is Mr. Valentine. Miss Brooks, my husband, Mr. Ames. How do you do, Mr. Ames? My foot and my mouth. Just who are you? Did you have a nice time, darling? Where have you been? Oh, over to the club. Yeah, they let me in. Just playing a little card. Look, Mr. Ames, I had a letter from your wife. My wife is leaving me. What difference does it make? Go on, get out. She's hired snoopers before, my friend. Get to your couch.  Listen to me. You were beaten up the other night. Get them out of here. Get yourself out of here. Stop it. No, listen. What's the matter with you, friend? Victor, that was your car, wasn't it? Driving away? Yes. It's a loan to do. Somebody needs it for a while tonight. You've got some things to do. Mr. Ames, I know I'm budding in, but your wife has been worried. Please. I'm going back over to the club. There's nothing anybody can do now except to make things worse. What? Darling! Send him home, Sylvia. I'll take care of myself. I put your letter in his pocket on purpose, Mr. Valentine. He'll never listen to me or believe me. It was certainly an understatement when you said he was upset. Yes. But you haven't said why yet. Now, just what's going on tonight, Mrs. Ames? Where's your husband really been? I don't know. Playing cards, I guess. He doesn't generally, but no harm could come out of that, could it? Maybe not. You said he'd been beaten up. Oh, yes, I know he's in danger.  Your husband's a lawyer, isn't he? He was until a year ago. His practice disappeared on him. What do you mean? Suspicion? Distrust? Whispers? This is a small town, Mr. Valentine. A very nice town. My husband used to be a very nice person. What happened? Have you ever heard of the Dorothy Fulman murder case? Well, yes, yes, I think so only. I don't remember the details. It was never solved. She was murdered, beaten up. It was horrible. They never even found the weapon. Police, experts, everyone's been over a million times. It was a whole year ago. They'll never get a confession from anyone. Mrs. Ames was your husband. My husband was very nearly tried for that murder. Oh, I see. But then if he weren't tried, then... There are people in this town who believe, who really believe that he killed her. Who will always believe it. There wasn't any actual evidence. But the circumstances, horrible, sordid, awful. Mrs. Ames, just tell me one thing, will you?  Mr. Valentine, I don't want anything worse to happen. That's all. I say, excuse me. You're Mr. Valentine, aren't you? George Valentine? Yeah, I was looking for the club dormant. My name is Norton. This is quite a pleasure. I've heard of you. I've seen your name here and there. Oh, is that so? See here. Join me on the veranda for a cup of coffee, will you? Hospitality of our little club. I'm sorry, Mr. Norton. I'm looking for a man named Ames. Oh, yes, Victor Ames blended, Jeff. Haven't seen him in some time. Might be here later. We can wait together. I said I'm sorry, Mr. Norton. Well, I certainly don't tend to be pushy. Or wait a moment. Perhaps I should be a bit more honest and say there's a little matter I'd like your advice on. I'd still go looking for Mr. Ames. Even if I said the little matter concerned, Mr. Ames? You twist my arm. Then we can do better than the veranda, I think. People there. There's a lounge in the locker room. All right. Through here? To your left. Generally closed at night. There we are. Okay. Now, what's the story? Nothing so very important, but sit down. Sit down. How'd you know who I was out there? Well, Ames had mentioned you're coming. You said you haven't seen him lately. Try again. Really? It's the other direction. Who's that? Hey, anybody in here? Walkin' up. Blue shirt. Private police? Just a moment. Yes, yes, he is Mr. Vanatee. Let go of me? Well, what are you doing here? Ah, what do you mean? Stop it. Who are you? Hey, hey, what is it? Jimmy, Jimmy, I found this man. Break it up, break it up, man. Break what up, John? I found him in here. I left my wallet in my locker. All right, all right. Oh, it's you, Mr. Norton. He was snooping, Jimmy. Now my wallet's gone. He took it. He must have. Oh, brother. What's he supposed to do? Search him. Oh, but he won't have it, will he? That's not the way they work. But he's trespassing. You can lock him up for that. I'll see the steward. Prefer charges. I'm sorry, Mr. Norton. What? I said I'm sorry. You're not going to prefer anything. Good night. Jimmy, my father was the founder of this club. When I issue an order to one of the paid employees, I expect that. Yeah, yeah, yeah. Sure, sure. Issue away. I'll handle this end. Good night, Mr. Norton. Jimmy, I have never in my life been sued. Good night. Yes. Good night. Well, that was something. Okay, bud. Hand it over. What? Oh, now wait a minute. You don't mean you believe that old school ties gag about... and still you put him out? The wallet, bud. Oh, sure. Mine. Here. Prudentials. The works. But enough. Well, I didn't exactly figure. Valentine, huh? That's right. Only look, Buster. Why? Why'd you treat him like that? Will him like lettuce before you even know what he had to say? Because I have no use for the high and mighty Mr. Norton. And don't worry, I won't get in trouble either. He may be down now. But he's being eased out the side door of this club anyway. All four of them are. All four? Would you clear that up? Do you hear the Dorothy Fulman murder? Well, that nice dignified man there, that Norton. For my money, he's the one that killed him. All right, so you've got your opinions, Jimmy. It's just an opinion. I'll stick to it, Mr. Valentine. But there wasn't any concrete evidence against either him or Victor Ames. And what did you mean all four of them? And why did Norton want to stall me like that? That's all he was trying to do. Keep me away from something. Yeah, the detective, mister. Uh-oh. Excuse me. Huh? Hello, Mr. Chester. Oh, Jimmy. Just standing here having a couple of drinks. I was downtown. Yes. That's done. Looks like you've had enough. Oh, no, no, no. I'm all right. I'm fine. I'm all right. Sure, sure, Mr. Chester. See him? Hmm. Oh, that guy? He's one of them. Say it faster, will you? One of the four.  Yeah. They never got enough evidence. They never will. But the police did prove that it couldn't be anybody else. It had to be one of the four men mixed up with him. Who are they? Mr. Norton, Ames, big fool always in trouble. Another man named Salto. He asked me he couldn't have got to first base with it. And Chester there. Oh, I get it. Not much left of Chester, is there? All of them have changed. But he don't even know what he's doing anymore. Hmm. Nobody will confess? No evidence. Oh, Jimmy. Jimmy, come here. No, no. I'm right behind you. That's Victor Reigns with him, isn't it? But the Stewart, sure it is. Valentine. Yeah, we catch up again, friend. It's a busy night. Excuse me, gentlemen. Jimmy, there's trouble in here. What? The card room. The one with the back entrance. I put those cards in there myself just this evening. Valentine, I've got to see you all along. Hold on a minute. Hold on, will you? Go on, Stewart. This deck of cards. There's some men I've been playing in there, apparently, or drawing high man or something. What is it? What's the matter? Well, sir, it's more puzzling than anything else. At a club like this, someone was being dishonest. Rather hasty job, but here you see, this deck has been marked. You are listening to Let George Do It. Our adventure will continue in just a moment. Now back to George Valentine. Of diamonds. Nine of clubs. Jack diamonds. Your turn, Chester. Draw. Yes, I'm king of hearts. I hereby confess one year ago it was I who murdered Miss Dorothy Fullman. I got the high card. I'll be dead by midnight. Only if your name is George Valentine, all you know is that Dorothy Fullman murder case has never been solved. But there were four suspects, but the police have disbared of ever finding out who her murderer was. Yes, all you know is that Mrs. Ames was worried about the strange behavior of her husband, and more recently that four men have been playing cards in the back card room of the local club, and that the steward says the deck of cards is marked. No, no, they can't be given a... Hey, hey, take it easy, Mr. Ames. Let's cease to it. They're not marked. What's bothering you so much, Mr. Ames? Kind of a crude job. Yes, Jimmy, little ticks on the edges like this. The person who did it could tell the cards, all right. Get out of here, both of you, Jimmy. He stole it. Hey, hey, slow down, Buster. Look, I've got to see you, Valentine. I've got to see you along.  What's so important about Chester? Chester. Hey, where are you going, Miss Ames? He was downtown. He's back now. Oh, Buster, would you please... The bar is here, and the bar is having those last two drinks. Well, there you are. Oh, hello, Angel. Oh, Mr. Ames, I saw your wife to the station. She said to tell you... Yes, yes, of course. Where is he? What? Little guy, Bruxy. He was in here a few minutes ago. He was having a couple of drinks. Yeah, he's gone now. Well, I did see somebody leaving just when I came in. He looked like he could use a little sleep. It's five minutes to twelve. Time for you to clear it up, friend. Where is Chester gone? What's happening tonight? Could have been any one of us. I mean, the cards marking them. But I didn't try to save my own skin. I would have gone through it if I'd been a high man. What on earth? I tried to remember. The watchman's spare gun, that was it. Quick, pulling buster. What? Yeah, the closet, the back hall. Come on, hurry. Will you the watchman's gun, that was it? Only the cupboard was bare. He's taken it already, Chester. You're certainly no gun in here. We drew. High man. He had the king of hearts. Little Chester, the weakest one in the whole bunch. Didn't even seem to react. What are you... Look, I know I'm talking wildly. I'll explain later. We've got to find him first. Hurry. We're with you, all right. But who is he going to use this gun on? Oh, isn't it perfectly obvious, Mr. Valentine? On himself. It's just like Jimmy said. How so about the bluffs across the golf course? I'm certainly deserted looking for sale, for lease. Chester must be here. It's where he'd come. Mr. Dorothy Fulman's house, huh? Where she was killed? Yes, in the living room. I found her body there. Beat me to death. The door's open, you see. Chester? Chester! He's not here. The fall guy. Well, we're a long way on the outside of that old crime now, aren't we? Perhaps we beat him here. Missed him in the dark. Chester! What do you mean, George? Ames here knows what I mean. This is where it happened. It wasn't a pleasant crime. And inside a man, a terrible thing like that can get bigger in a year, huh? Mr.  Sure, sure. That's what they all say.  Wait a minute. George, listen. Upstairs. Come on. Chester? Where are you, Chester? It's me, Victor Ames. Salto? Salto, what are you doing here? Mr. Valentine's all right, Salto. He knows the whole story now. But I didn't mark any cards. It wasn't me. Then what are you doing here, Salto? Hiding... Leave him alone, Ames. Leave him alone. And never mind who marked the cards.  Four men actually drawing to see which one would be a fall guy. Which one would confess to a murder? I don't believe it. Oh, yes, it's very easy for the two of you to talk like that. I told them it was ridiculous. But the same as Russian roulette. Spin the cartridge wheel. See who gets the bullet. Yeah, they couldn't stand to be pointed at. The suspicion, the shadow of guilt. The crime that would never be solved otherwise. Yes, I told them that, but Ames and Norton kept saying that. You were willing enough, Salto. You didn't have any solution, anywhere to keep yourself from going insane. Maybe you can't believe it, Miss Brooks. Why should you?  I don't think that's exactly what she meant, Ames. Sure, I know it's not like in books where people just forget about murder, but to try to dig yourself out of a swamp by drawing, taking one chance and four of being tapped for guilt, just to lay all the ghosts for the others. If we did it so what, we did it. We've nearly killed each other, trying to make each other confess anyway. I was thinking about the second part of the bargain. Suicide for the elected guilty one. Yeah, to make sure the police would accept that confession. Mr. Andes, you might have gone through with it. You're that kind. But I just don't believe that most men would... Shake, Angel. All right, how about it, Salto? That's why you're here, isn't it? To see if Chester would go through with something that you wouldn't do yourself. That I... I'm sorry, Victor. I wouldn't have. I couldn't have. I went along with it. Of course I did. I'd been high-card. I don't know what I would've done. Okay, there's one down. Wet feet. By this time, Chester must be aboard the nearest freight train, headed for parts unknown. Chester, you signed the confession. But he wouldn't do it. I know he'd been drinking. The last moment is a little hard to pull a trigger. Is that so? You're so sure, aren't you? Moonlight out there, window, come here. Look, it's him. It's Chester. Just walking. That's the path runs up by the bluffster. Yes, and if anything happens to him, it's our fault, Salto. Come on, step on it. Run! Chester! Chester! What's the matter with him? He doesn't even listen. Call him about, George. These bluffs are pretty steep, aren't they? Chester! I'm going to climb up this way, too. Oh, no, you don't, Buster.  Valentine!  Stand still! What a... Norton! Get out of here, leave him alone. Norton, wouldn't you know? Stand still! I'm warning you, I have a gun. Oh, yeah, sure. The one from the Watchman's Locker. He didn't take your Chester, didn't take what's all this. So you did, sure, sure.  You'd get him to write a confession and then murder him. He killed her. He killed Arthur from when he confessed. George, he's up on the edge. Look at him. Leave him alone. He'll jump. I tell you, look at the way he's acting. I just followed him. Forgive him, the gun he didn't take. Ames, listen to me. It will all be over. For all of us... Let it happen! If you don't, it'll be the same thing over and over again. Yeah, look. We can't stop him from here. And he does look like he wants to jump. Okay, so I've been wrong, so I... Valentine! Get out of the way with that gun! I got it! Chester! Mr. Chester! Yes? Mr. Chester, now you listen to me. I can't reach you. But get away now. There's something I'm going to do. Yeah, I know, I know. Kill yourself. But you were supposed to do it where she died, weren't you? Wasn't that the agreement, Chester? To make it look good? Can you understand me, Mr. Chester? I'm all right. That's it, that's it. Just keep looking at me. It should have been the living room, though. Or were they always wrong? She was beaten, bruised. I remember they said they never found a weapon. Was it really up here that she died? Was she thrown? It would have looked the same if somebody then carried her body back to her house. I'm going to jump, you know.  No, you're not. You're too curious, Chester. This year, since Dorothy Fulman died, must have been the worst for the one who really killed her. Don't you think so, Mr. Chester? What? What do you mean? What admitting it is worse? Some people can't ever do that. They'd rather die than do that. I'm going to jump. You can't stop me.  Well, they gave you a chance, the little card drawing. You know the masked deck. The marked one would be found sooner or later. You deliberately left it behind. No, no, go away now. A world would say your confession was a fraud.  Well, any of them could have marked the cards. The high man marked them. The guilty man, Chester. All I've said is built on that. When there's a drawing, a man can't make another man take a certain card. So if he marks them, he only marks them for himself. Check. Yes, I understand. To pick his own card. But the lowest card picked tonight was a nine. If a man wanted a low card, that's not very safe, is it, with 52 cards in the deck? You know, it baffled me for a while. Until I saw that you really did want to die. She was faceless. She was bad. Get out of my way. Oh, no, you don't. Just hang on. You're going to live, Buster. You're going to write a real confession. Back to the conclusion of our let George do it adventure in just a moment. George, it did work out that way, didn't it? Yeah, yeah, Bruxy. They pieced it together again. That's why Chester went up to the bluffs instead of taking the gun. She had killed Dorothy Fulman a year back. And if the first confession had gone through, if he'd shot himself, nobody ever would have believed it. The other three would have always thought they railroaded the poor little punchy. They're private little hells for new ones. Mrs. Ames went still in love with her husband and called you here. George, isn't it? Remarkable what a woman will do for the man she loves. Remarkable. Forgive. Forget. Protect. I'll remember that. Darling. The very next time I'm suspected of murder. Oh! Good night, Bruxy. You have just heard High Card, another let George do it adventure. Robert Bailey was starred as George Valentine with Virginia Gregg as Bruxy. David Victor and Jackson Gillis wrote the story with music by Eddie Dunstetter. Now this is yours truly inviting you to another visit with Valentine when you will again hear what happens when you let George do it.


Good morning. Welcome to the OpenStack Summit. My name is Federico Lugifredi. I'm a product management director in the storage business unit at Red Hat and I'm joined by two of my colleagues, Sean Cohen and Sebastian Han. One is a manager in the OpenStack team that has been managed in storage for longer that I've known storage existed and Sebastian has straddled both groups as a principal architect. So today we're going to cover very quickly very quickly because it's a packed session how quality of service works in the public cloud, in OpenStack with SEF and then how it all comes together as a single thing. It's going to be a fairly in-depth analysis. So let's get rolling before we are already late. So the first building block is how does quality of service work in a public cloud environment? Why do we care about this? If you have been following our OpenStack and given the venue, I assume that you have been. You will have noticed that OpenStack is becoming a de facto standard in the telco environment. Now every telco workload has a database dimension to it and quality of service is an essential building block to deploying a database and therefore that's why we're here. There is an additional dimension which is capacity planning and cloud environment users expect you to add capacity to the cloud before it's needed. It's not the old days of IT where you can make them wait four months. They expect it to be there yesterday and capacity planning intersects with quality of service in a remarkable way and that's why we're going to look at it from that angle. Further, public cloud has established its model for capacity-based quality of service as a de facto standard and so we want OpenStack to be able to offer the same mechanism. Users expect it. That's what they learned about in public cloud and for those of you wondering what the movie poster is about towards the end of the second Tron movie, though as the hero is about to be defeated, he has a quote that says I fight for the user. Then he falls in the sea of simulation and is decompiled and things go very bad, but for that one second he has the right thought. Now, what's the problem statement? Some workloads need deterministic storage performance. Most typical enterprise workloads that require this are databases. Jitter sensitive workloads like video streaming are another common example. These are workloads that depend on constant latency measures to perform adequately. Variants in latency is called jitter. I expect most of you are familiar with this, but just in case. A second class of problem that QoS solves is isolating workloads from the so-called noisy neighbor. In a virtual environment, this occurs when there is contention for a shared resource. In this case, our shared storage cluster. Contention starves one of the users of the needed resource and therefore it slows down, hence jitter again. Finally, operators need to run capacity planning exercises. If you want 90s flashback, the original title for this session had a very James Carville tune to it, which was that it's all about capacity planning. Stupid. But you can actually build QoS into systems that don't have QoS just by doing appropriate capacity planning. So maybe the James Carville analysis is not that far off the mark. There are two options when it comes to virtual disk storage for your instances. Instance storage, also known as ephemeral, and persistent volumes. Once attached, these virtual disks can be formatted with your operating systems tooling and behave exactly like a standard physical disk would. Key differences stem from the fact that instant storage is physically part of the host that runs your instance, whereas persistent storage is remotely connected over the network. Instant storage offers larger volume sizes and may hold the edge in absolute performance. Certainly, it is the case with the largest public cloud vendors because of its proximity to the host. But the storage type is also lost once the instance is terminated. Hence, it's a moniker of ephemeral. Permanent persistent storage is much more featureful. In particular, it offers facilities like snapshots that dominate provisioning and backup strategies in cloud infrastructure. Now, multiple volumes of either type can be attached to an instance and you can even mix types. Ephemeral volumes can be attached only at boot time, however, while persistent storage can be attached while the instance is already running. And you can add them or remove them at your heart's content. The user can do whatever they desire. The Block Device Mapping Facility in AWS allows you to build wonderfully complicated disk topologies if that's what you need and associate them with the instance at boot time. It's even possible to attach multiple volumes to an instance and build software RAID over them. Please don't do that. As a SAF guy, I have a dim view of RAID, as you may imagine. But in the public cloud, really, you need a written note from your mom giving you permission to do RAID. And if the Y is not clear, I'm happy to take questions on that layer. There are some cases where it does make sense, but not the usual reasons why you would use RAID and it's certainly not the mainstream case. Now, in June 2012, AWS began offering SSDs as a higher-performance alternative to magnetic storage. And over time introduced multiple options with different performance levels and cost. Some instance types now include an SSD-backed instance store to deliver very high random IO performance. With types like I2 and R3 being the first two that have supported trim extensions. Instance types themselves have evolved to include high IO instances. These are the I2 type aimed at delivering high IOPS from up to eight local SSD drives. While then storage instances type D2 offered the lowest price per disk throughput in EC2 and balanced cost and performance using 24 magnetic drives. In other words, there are so many options that we can't possibly go over them. So let's focus on the essentials. Oh, and by the way, some of them have burstable IOPS just to add another dimension to the problem. So let's focus on the essentials of the AWS model. Persistent volumes are what we're interested in. And persistent storage in Amazon AWS is delivered by the EBS, Elastic Block Storage Service. You can have EBS-backed instances, meaning the EBS volume is your boot volume. And EBS can be SSD or magnetic as we have. And you can add volumes at runtime. You cannot do that with ephemeral. Critically, you can choose the volume type. How many of those volumes do you have? What IO characteristics do you want? And very important, as of 2017, you can now resize live volumes. The why this is important will become apparent in a second. Now, to complete the bits of Amazon that we need to understand for this to make sense, there are two more components. CloudWatch, which is the monitoring service for IO provisioned volumes. CloudWatch delivers automatically a set of metrics over latency, bandwidth, and IOPS that are being delivered by the volume, both read and write. And there are a few more, but these are essentially the interesting ones. And CloudWatch can fire events based on the level of these metrics. The other aspect that's important is CloudFormation. CloudFormation is an automation platform which has its own syntax. Fairly JSON-y, where you script what happens on given events, and you can provision and design your cloud infrastructure using it. Now, the example here is what happens when a volume reaches 90% full or 85% full. Whatever threshold you set, that is where your operators start getting nervous. You can set up CloudWatch to fire an event when the volume is 85% full that will then trigger a CloudFormation script that you defined that carries out a resizing of the EBS volume to a larger size. Then it will run some logic that you had to write that will stretch the file system over this volume so that the new size becomes visible to the operating system. And you're done. You are no longer running out of space. And this happened automatically with live volumes as you were reading the pager message that said you're low in space. So that is a pretty cool thing, but there are more things that you can do with this platform in the area of capacity planning, which is why we're interested. Now, here is an example of a volume in EBS. General purpose SSD. These are EBS volumes, SSD backed GP2 type. They are recommended by Amazon for boot volumes for low latency applications like bursty databases that are not always running at load. While it is interesting, the key point here is that IOPS performance of the volume is directly tied to its size, the third line in the slide. Every gigabyte adds three IOPS to the volume. If you want to provision IOPS, all you do is change the size of the volume. This is a general property across EBS volumes. With storage space comes IO performance. You can attach additional twists like capacity bursts that some volume types have, or EBS optimized DC2 instances, which have an additional dedicated network pipe, and other 125 megabits, I believe, that are dedicated to storage as opposed to the other general purpose channel that accesses all other services and the network as a whole. But when it comes back to the single combined dimension of space and provisioned IOPS, that is the core of the QoS model in Amazon. With elastic volumes, which were introduced this year, one can reprovision the size, and there is a result, the provisioned IOPS, of a live volume with a running system attached to it. You can also change the volume type, altering the formula controlling the behavior of how many IOPS you get per gig. And there are some limits to what is allowed here, like GP2 type and SC1 type can become all other types, while IO1 and ST1 can only walk to the right in that list, so IO1 can become ST1 or SC1, ST1 can only become SC1. There are some other restrictions. You can expand the volume, but you cannot shrink it. You have to take the volume offline to do a shrink. Okay, so there are some limits, but this is still pretty awesome. As of two weeks ago, now you can use CloudWatch to trigger a no halt update via cloud formation for the size, the type and the provisioned IOPS. So what I just described before, you can do again, saying this volume is running at 90% of its provisioned IOPS. It's about to get slow for an event that is going to resize the volume, add more provisioned IOPS to it. That will happen transparently. This is not scale out type of reprovisioning where you kill an instance and you bring another one in. No, you're changing the existing instance. For comparison, we have a bit of Google. Persistent disks on Google work pretty much in the same way. Google Compute Engine does not have as many options as Amazon AWS, but what it does have is always excellent. Performance is predictable and scales linearly with size until it reaches instance or volume limits. Google is using the same capacity-based model AWS pioneered. When you need more disk space or better performance, simply resize your disk to add more storage space, throughput and IOPS. Volume limits here are determined by two things. There are per volume limits in size and therefore also IO characteristics that depend on the technology that is backing the volume and there are instance limits and these are defined by the network and the network egress caps on your instance and these instance limits are shared if you're using more than one volume. They apply to volumes collectively. As you can imagine, there are differences between Amazon and Google and we're not detailing all of them here, but there are some interesting bits. For example, the instance limit changes when you have a ton of virtual CPUs. For example, if you have more than 32 virtual CPUs, the instance limit is significantly higher and I believe that there is another such step around 60 or 64 virtual CPUs, which makes sense because your SSD-based capacity needs CPU to be used. Now, why do we care? Because this is how the public cloud vendors do QoS. It's simple, effective, it's understood by the users. The admin scales in a single dimension doesn't care which the user is provisioning for. More gigabytes, more IOPS, it's just more. It flattens two different scaling factors into a single dimension. The operator needs to add capacity to add IOPS anyway. That's how the technology works and here users are coming to expect this QoS format. It's what they learn about in the public cloud. So to my closing point, we can build you a cloud like the big boys do. OpenStack Cinder will be able to set QoS limits based on provisioned capacity and I'll let my colleagues show you how we're making this possible in the OpenStack community. All right, so we see how the big boys are doing it. And just a quick raise of hands. How many of you are using, not just OpenStack, use Amazon today, use Google today? All right, 25%. You're already used to actually do things this way. You're already managing your capacity, you're already managing your quality of service for storage this way. So here we are today in OpenStack Summit in Boston, which is my hometown. And we're finally discussing multi-cloud, right? So today's talk is not just about OpenStack. As you see, we're dedicated third of our talk just to the public cloud and the reason is we're really looking at multi-cloud use case and operation and now we actually set standards and not just do it on our own on OpenStack or any other public provider. So with that, let's do a quick why we're here. So Federico already asked the questions of why, right? And we did mention some of the databases. And what we've seen is not just the telcos, it's the enterprises. Every application framework in OpenStack use a database in some manner, right? And it doesn't matter if it's the Rails or Wisa, which runs like Microsoft SQL Server, means that use MongoDB, LAMP, right? So in fact, every Java framework use persistent database. And these databases, and you can see the growth from over year and year, are not standard sized. They need different quality, right? Some of them are high performance workloads. Some of them tend to burst. How do we provide them all the relevant quality of service that they need? And we look at the trends in Cinder. So this is the latest user survey from OpenStack Foundation from last month, right? So first of all, we continue to see that SEF continues to lead the charge with 50% of all OpenStack in deployment's production, right? This is huge. Just to compare LVM, which is the red, is the default, right? So a lot of people are basically changing the default moving to another open source, which is SEF. And just if you want to compare it to the propriety storage, so it drains all the way from 1% to 10, right? In terms of what we're seeing in production. How can we offer the same class of service like the big boys with OpenStack Cinder, right? With all the vendor choices we have today, including SEF, and how we do it specifically with SEF. But before we go there, let's do a quick history lesson. Our journey with quality of service in Cinder started already back in the Grisly days, something like four years ago. And later, that was in Grisly, if there was any contributor for Grisly in the room. Later in Havana, we introduced the Cinder and the Nova Quality of Service support, the front end and back end, that I'm going to talk about more internally. Around ISIS, we finally get to a lot of backfixes and stable API for quality of service. And we started to see a lot of adoption from all of the vendors, right? The storage vendors, the writing drivers, making use of the new Quality of Service APIs. Later in June, we added the support for the Quality of Service, already in the Horizon dashboard. And we basically are able today to have volume types, classes of different storage, if you will, storage tier, that maps to them, so the administrator can go and configure the static Quality of Service volume per type. This is how it looks in Horizon, which is pretty simple, right? We have the volume types, we have Quality of Service specs. Where Quality of Service specs are used to apply performance settings. You can limit read-write operations on disk. Obviously, you need to determine the Quality of Service specs based on your supported back end. And each back end basically has a unique way of exposing Quality of Service, so it's not unified or generic. Rather, the Quality of Service specs are actually associated with the volume types as we showcase here, but during the volume creation, I have to specify the volume type with the relevant performance setting that are mapped to the Quality of Service specs that are exposed in each one of the unique drivers. And the way Quality of Service works today in Cinder, we have a front end. This is pretty much how we apply the policies from the compute from Nova, right? And you can limit by throughput, so you have a total bytes per second, read per second. We're basically limiting from the instance if you want level, right? And then we have the backup specific where each vendor can actually showcase and utilize some of this new capabilities. Keep in mind, a lot of the back ends support different Quality of Service already at the back end level with different performance tiers. So in a sense, as an OpenStack operator, actually you can select a relevant vendor which brings me the specific Quality of Service class that I need, all right, and expose it to a volume type. And as Federica mentioned, different types, different storage types, different volume types to one workload, right? So you can have the database data on one volume tier, if you will, and the log on a different one, right? You actually build for a specific workload today a Quality of Service. So when we say volume types, from a workload to a space, it's maybe many volume types, right, with different characteristics based on the need. Now, if you look at the secret, right, each one of these vendors have adding unique keys because this is where you can actually add extra specs to make use of your unique features and their array level. So, for example, HP FreePower, using added latency and priority, SolidFire had the mocks and bursts, right? You saw the bursts were in Amazon, right? So both SolidFire has that capability today. NetApp is using Quality of Service policy groups for extra specs, Iwawi priority, each one of them basically exposed a different set of specs. So, here's just an example, right? So we typically expose, this is like main IOPS, max IOPS, scale means fail max, scale burst, the amount of scale of the burst IOPS of every gigabyte additional volume size. We have all these capabilities already today, right, in the code that we have today. So we're very close to what the big boys are doing already because we are able to provision the right storage performance to our volume types. But, going back to the first line here, Quality of Service values in Cinder are currently able to set in static values, right? Keep that in mind. Some examples, SolidFire driver, right? So, in Okada, this is the latest things you can do with the latest code, right? SolidFire, Okada recognized four different Quality of Service specs to a live specify setting that can scale the size of the volume. I give the example with the scale means, scale max, very similar to what AWS performed today, very similar to what Google offers today. Scale IO in Okada, Quality of Service example, max IOPS per gigabyte, right? We already got to a point where we can actually offer very, very unique max IOPS per gigabyte, max bandwidth per gigabyte, right? So we're limited, we'll be calculated by the specified volume multiplied by the volume size. This is where we are today. In Okada, really, all right. So Quality of Service, just to summarize where we are in today's world of Block Storage and OpenStack is we are able to provision and set up this unique characteristic specs, but they're all static values, right? It's not dynamic in any fashion and it's one dimension, right? What if there's a way to derive Quality of Service limits values based on the volume capabilities, capacities, rather than just the static values? And allow me to introduce our first capacity-derived IOPS. This is a new API available in the Pike release, which is right now developing. It's a new mechanism to provision IOPS. Provolium bases with the IOPS value adjusted based on the volume size, IOPS per gigabytes, allowing basically operators to cap usage of their system and define these limits based on the space usage as well as the throughput. So you can charge your customers not just how they exceed the limits, right? The max, whatever, value set up, but actually capacity as well. Just like the big guys, we're taking several dimensions and we're flattening into one. So you need more throughput, you need more IOPS, and your volume, right? We're able to provide the same thing. Important question. Would it work just for self? No, it works for QM, it works for LVM, it works for Solidify, it works for any other backend. So in a sense, you can still use your existing extra specs and all the things that we achieved all the way now by adding this new capability into the APIs. So we can actually set new standards of Quality of Service. So our goal can be, say, 1,000 gigs at 10,000 IOPS per gigabyte, right? So we're combining the points. So how does the code API looks like? It's very elegant. So in one line, you can do read IOPS second per gigabyte. So we're adding basically capacity with IOPS. So as an example, here we have on the left side read IOPS per gigabyte and write IOPS per gigabyte. So we can start with a two gigs volume at 20 IOPS, 20K IOPS, right? And then as you move to a five gig volume, you're basically going already to 50K IOPS, right? So you're getting more capacity and you're getting more performance in one API. So with that, we basically showcased how we can scale not just linearly our storage and performance, but what are the scale consideration when we should have in mind we're actually delivering quality of service in OpenStack and how can we actually use this new capacity-driven API to help with that as well as what can we do in the future of CEPH and OpenSec in general to get more closer to what the big boys are doing. And with that, I'm going to hand it over to Sebastian. Thank you. Thank you. Okay, so now we're going to dive into storage QoS and basically what we call the universal scalability model which basically gives us a proper definition of what scalability is and also provides a model, kind of a framework to help us understanding and getting a better visualization of the scalability of our platform and also how to improve it. So if we had to take a simple example, let's say you're a client, so you get one VM and you ask for one block device and then the cloud provider just kept the volume at 100 IOPS. So you ask for one volume and then you get 100 IOPS and then what about if you want more performance then you will ask for another block device and then if you need more then you will keep on asking more and more volumes. So in the end what you should be or what you expect is to get this really linear scale where if you ask for three volumes and then you get 300 IOPS. But this really boils down to the efficiency of your own system, so of the front end first and the back end because remember the things we implemented are at the front end level. So it's the hypervisor that is responsible for doing all this throttling for all the IOPS and also for the throughput that you're asking for. But in real life you won't necessarily get this really nice linear scale mostly because the system is not as efficient as you might think it is and also because you don't also have the right and proper understanding of what the system is doing when we are asking for submitting an IOPS basically. And it's really simple to determine this. If you run two benchmarks you won't likely get two times in a row the exact same results. And by benchmarks I mean you don't really need to have tons of machines and even a distributed system. You can easily do a DD on your own machine and then you won't get twice in a row the exact same result. And this is easy to understand because basically while you're performing this operation then the system is doing something and the second time you're asking for the same operation then the system is also doing something else. This is why you're not always getting this really linear scale. Instead what you get is this linear line which is not so bad but is a little bit more realistic in real life scenarios. This is basically what you would get. And this is explained by two main things. The first one is the contention. So basically the contention happens when you get more clients and some of the work cannot be paralyzed so the ultimate speedup is really limited. The currency delay is the other part where we are limited by the system itself. So the things I explained earlier the incurrency introduced by the system itself because the system is not only doing what you're asking it to do but it's also doing other things. The kernel is doing other things. So this is the more worker you add then actually the less you get in this case. But this is perfectly normal and this is just real life. This is not something that should be... Oh, okay, this is... It's not trending really well but basically what you should see is that you have a linear scale and then it goes down and the height of each volume is different. And because the unit of height for volume is the number of IOPS that you get but then the more client you add then the less performance you will get because at some point then over here you should start seeing some kind of a plateau. So you're plateauing in terms of performance because your back end can only achieve and sustain a certain number of IOPS and once you reach that point then you don't get less performance but let's say you can achieve 10,000 IOPS from your back end and then you ask for way too more block devices and even if they are capped for 100 IOPS then the back end won't be able to sustain that. And this can be easily explained mainly because of the structure of a disk. If we use disk-based clusters then disks they have to seek and even when you run a benchmark on a single drive you will never ever get this linear scale. The beginning of the device is always faster and then once you go on the edge then it slows down. So this makes really perfect sense in our scenario. So basically we get less performance for each volume in the end but the overall performance is always attained. For SSD-based clusters it's a little bit different because they don't really have to seek so not like hard drive disks they don't seek so you can really achieve on a per disk level a purely linear scale. On the opposite they... So we have less content we still have the contention of course when we reach the plateau of the performance now it's rendered nicely over here. So once you reach the top of what's the platform is capable of then obviously you will start getting less performance but you won't have this degradation effect because you ask for more volumes for with SSDs. On the opposite side the limiting factor for always these becomes the CPU so the more threads you get the more IOPS you're asking for then the more CPU constructions you're going to get from the system. So then if you had to scale what kind of scale should you choose and how should you scale properly depending on what kind of dimension you want to use if you decide to go for IOPS limits then you don't do any QoS based on the capacity of the volume then you just apply a certain QoS of a certain volume type within Cinder and what you should go for is just to get faster media in order to be able to just sustain the IOPS that the clients are asking for. On the opposite if you're aiming for volume coders then you should be just adding more and more block devices or more and more storage nodes and actually the second one is a little bit easier obviously about capacity planning even if we don't always know how many clients are we going to have and what the size will be of the volume then if we do some kind of forecasting for capacity planning then we should be able to get the right number of machines and the right number of disks obviously the latest one is a little bit less relevant for SSDs because we don't have the performance degradation all the time because of the stick of the devices in the end when you mix both scenarios, volume coders and IOPS limit you should get something like this and you even in so it's a little bit of a mix and match obviously because you have clients asking for bigger volumes so the bigger the volume is the more performance they should get or some of them just want to have maybe tiny volumes but a lot of IOPS but they just don't care about the space usage so you get this mix and match visualization and just to be sure that this is not only a theory then we also run an experiment on an open stack platform backed by a set cluster we so we ask for more and more volumes so what we can see at the very bottom is we have all the volumes and we have the aggregated IOPS and IOPS per volume so IOPS per volume obviously is at an hundred IOPS IOPS and as we can see here we really have this sub-linear scale the one we are expecting to get obviously so non-linear scale but sub-linear scale and we also see that we get the number of IOPS we asked for but at some point we are reaching that point over here the cross over there is basically because we reached the maximum capacity the maximum performance of the cluster so at this point the cluster was capable of achieving around 40 times Android IOPS and then once we reach that point we just see that the IOPS per volume start degrading so this is just a real life example and then we also run the exact same experiment on a hyper-converged infrastructure where we just it's we mainly got the same results it's just that we've been able to create more volumes when we run the hyper-converged infrastructure one of the good things is that on a distributed system theoretically we can we can get a local heat because when you get a volume then with SAF for example you have N numbers of replicas it's kind of responsible for deciding what the object should be located so if you if you collocate storage and compute on the same machine then there is a chance that you will hit the machine you're running on and then the replicas will follow on the other ones so it's just so if you want to summarize what you should be doing if you're looking at building a SAF cluster or backing up an open stack environment with the SAF cluster that we that we are providing here basically we went with OSGs with just standard 7.0 to our KRPM drives we've read back cache enabled on the drive and also on the controller we configured with REST 0 all the drives and they were backed by SSD journals we really have to do SSD journals because then we can kind of the impact of the seek of the devices but we will still get it obviously it's just to get faster acts from the clients one rule of thumb that we and it's because we are using SSD journals to just to store the SAF journal we can fairly assume that the rule is one volume per OSD and this is 100 IOPS per volume for flash as explained it's a little bit different because we can get more IOPS but then on the opposite it's more a measurement which is CPU related instead of disk related so you should be calculating calculating this with according to the gigahertz of your own CPU so now let's discuss a little bit more about the future where we are heading in terms of QOS basically so this is kind of a summarizing what we currently have as part of OpenStack is we already discussed that with Sean and Federico but we can already achieve fixed IOPS per volume this has been just released for Pyke then the second one scale IOPS oh no it's the other way around actually we could do that already for a pretty long time applying rate limiting on a volume type no matter which size of the volume but the latest use case is bursting IOPS so burst IOPS and scale IOPS we cannot really do this at the moment just because we don't have any QOS implemented on the back end we can easily do some throttling at the hypervisor level but there is no way because the hypervisor is not the storage entity there is no way to store IOPS or burst so in this case the only way to implement this will be to have QOS at the back end level so in SAF ideally we will use SSDs for this obviously with all the advantages we just discussed with SSDs so it's a kind of a reservation style system where you are able to store and calculate the number of IOPS that you can reserve for any clients and it's you're just basically counting for IOPS that haven't been consumed and they can be asked for at the time regarding SAF and how we might be implementing this I would like to really insist in the fact that it's really complex to implement QOS in a distributed system but on SAF one of the way it's not set in stones yet but we currently are actually exploring the DM clock algorithm just to achieve the QOS on the back end we just learned the first patch was just introducing a library into the SAF code like two weeks ago and our primary focus will be on the cluster activities instead of client ones in SAF there is client activities so clients are running into the cluster but there is also back end activity we are replicating data we are backfilling data we are recovering data so SAF is really self healing all the time and there is a lot of moving parts on the back end of the cluster too so what we are currently focusing on is to achieve some kind of QOS depending on what kind of IOPS we are doing on the back end of the cluster if it's recovering, if it's backfilling, if it's replication then we could apply a certain QOS with that regard but then here is the challenge SAF is a distributed system and I would say it's fairly easy there are a lot of vendors claiming to, well not claiming but having support for QOS but usually it's easier to do because they have one big array so it's just a really big and monolithic system so there is no distributed fashion involved whereas when you do distributed systems it's definitely really hard because this really means you have some kind of consensus between all the entities of the cluster, this is something that we already have but this is also as part of the QOS, this is something we will have to implement things like knowing what the hardware is capable of making sure that there is no degradation over time, we all know that there are degradation over time so it's really complex to implement and this is basically some kind of a research project at the moment so if anyone looking for a PhD or just a research project I believe you can easily go that path because it's a huge effort and with that I will just hand it over to Sean Thank you Sebastian Alright so with the few minutes we have left, let's talk about what we are and I'm going to talk about some of the open stack existing tools we have today and some of the gaps so you've seen what cool tools big guys are using for example the AWS CloudWatch that is really a combination of some of the tools we actually have in-house but we have not yet took their potential out of this use case so for monitoring telemetrys are alarming and monitoring service in open stack and today you can have a gnocchi plugin for Grafana to actually generate very cool statistics of your quality of service usage and your provisioned IOPS QM itself that we're using in the generic API has what we call the info block that's command that you can poke it's currently exposed in livered but not yet in open stack so that's another approach as a community if you're interested in taking it and bringing it into open stack we can obviously Sebastian talked about self tools the RB decline statistics socket is another area we can pull monitoring and the key interesting part for me is event triggering automation since the ability to see hey this volume has already reached the 90% IOPS it's actually going to take a slope in terms of performance heat how we utilize this not just monitoring when it happens think about the burst examples we gave earlier so database like you have this is a cloud service we have more user suddenly consuming our application workloads do you have more performance happening in real time how can we trigger a real time event to actually add more quality of service in real time so you add more capacity derived quality of service you get more throughput you get more capacity in real life so basically today we have a static picture in open stack we would like to see how we can actually change volumes types limits so today if you want to use the capacity derived quality of service we showcased earlier that is now new in Cinder if I need now to resize that volume I cannot do it online obviously Amazon has limitations they can not even shrink the volumes but we can not even resize for us it's basically you need to detach the volume right change the volume type retype it and connect it back so it's really ugly so but we are able to automate a lot of these pieces because we are already able to automate the quality of service we can automate the volume types there are things we can do today obviously there are gaps that we need as a Cinder community to see what will be the right approach to do it but this is clearly the direction we should go if you want to offer that level of service consistently across our multi-clouds this is not just open stack as I said in my opening this is to be able to manage your hybrid clouds public and private in the same manner and lastly I want to be able to reconfigure them in runtime so my workload is running right now in production I want to provide that workload seamlessly with the quality of service changes on the flyage with Christ because application workload has a life cycle we need to be able to address the life cycle including burst in real time rather than yeah let's provision a new volume let's create the static specs in advance and think what will happen when we go live before I don't know Christmas shopping craziness going it doesn't work that way we need to be much more agile in the way we provision storage so to summarize we can build you a cloud like the big boys already open stack Cinder is already able to set quality of service limits now with the addition of the based on provision capacity we're able to flatten these two scale factors into a single dimension so we simplified the capacity planning for the operator as well as allowing the operator to increase the available capacity by adding more and more distributed back end right so more nodes more IOPS fixed increasing capacity while maintaining the quality this is where we already got to this point so we have a few minutes left because we have another session kicking in so I want to invite back Sebastian Federico and maybe two questions and we will be available obviously after this session and you can follow us on Twitter as well we have two mics so please use them and if you need any assistance we can provide one of these alright any questions can you open that mic yeah we can't hear you Sebastian you mentioned earlier you had a recommendation of a rule of thumb for 100 IOPS per volume but I'm assuming that's for a specific size of volume because I mean it would depend on the scale of your cluster how many IOPS you had per volume yeah it's basically you always have to calculate how many IOPS you want to provide to infrastructures you based on that calculation if you say I want to provide 10,000 IOPS then you plan a platform accordingly obviously so it's more about like in this case it's more like hardware sizing because I think you're referring to this as the scenario right right so yeah it's more about hardware sizing so that was a pretty small cluster you were testing on where you were saying 100 IOPS okay so that wasn't like a rule of thumb you should always go by it's like that's really like you need to scale it I mean you need to start somewhere I guess and yeah so this with this like simple recommendation this is what we recommend yeah alright thank you any additional questions alright if not thank you very much enjoy the rest of the summit thank you