Let's go through the withdrawals for the women's tournament before we start. So here we go, 2021 US Open withdrawals for the WTA we have. Sevilla Kennan, she is out of the US Open with COVID. So she's out, Sigmund is also out, Teague is also out. We've got Wong also pulling out, Serena Williams. She's out with a hamstring injury. She is the biggest name for the women to pull out along with her sister Venus, who also has a leg problem. And then also we've got Zhang and Zhu, who have also pulled out for unknown reasons. I didn't find out if they were injured or if they just didn't come over to the US Open, but they're not playing. Here we go. So here is the top of the draw, Ash Bhati, the world number one. She takes on Svona Raver in the first round. Svona Raver was a great player 10 years ago. So it's an interesting first round matchup. Winner of that match takes on either Boral or Talzin in the second round. Then we've got Battle of the Americans with Roger versus Bregel. Winner of that match takes on either Cristea or the 29th seed Kudamatova. Then we've got the 22nd seed Mukava versus Tormo in the first round. Circle that one is one to watch because they're both dangerous players and they could pose a problem because they're both beaten Bhati on hard courts this year. Winner of that match takes on either Shay or Liu in the second round. Then we've got the wild card Baptist versus Zhang. Winner of that match takes on either the qualifier or number 13 seed Brady in the second round. Look, Bhati's got an easy draw. Like an easy first couple of rounds, let's say. But I've got to admit, fourth round is going to get dicey. We're going to watch after Ash Bhati, of course. World number one in great form. Clearly the best player on the planet at the moment. Also got to keep an eye on Mukava. As I said, beat Naomi Sarkron Clay and beat Ash Bhati at the Australian Open earlier this year. So keep an eye on her. And also Brady, who made the Australian Open final, got to keep an eye on her as well, especially because last year she made the US Open semifinals. Next part of the draw, we've got Benchich, the number 11 seed and the gold medalist at the Olympics. She takes on Russ in the first round. Winner of that match takes on either Treveson or the wild card Vandaway in the second round. Then we've got Dui versus the wild card Sanders. Winner of that match takes on either Potipova or the 23rd seed Pagula in the second round. Then we've got the 28th seed Contivate versus Sam Stoza, former champion of this event in the first round. Winner of that match takes on either a qualifier or Taikman in the second round. Then we've got Ferro versus Abini. Winner of that match takes on either a qualifier or the number seven seed Fiontech. So look at the tough matches in this one, potentially as the rounds, as the seeds collide. We've got to watch out for us Fiontech, obviously French Open champion of last year. Hasn't got the consistency yet on the hard courts for me, but we'll see how she does at this event. She's got a pretty good draw in terms of the first couple of rounds. Benchich got to keep an eye on her. Gold medalist at the Olympics. See if she can back it up, played well here two years ago, got to the semifinals in 2019, whilst on Drescu in the end. I'm more interested to see how Taikman does. I want to see if Taikman can back up the result that she had last week. I think she was in great form last week. She beat a lot of good players and lost to Barty in the end, but Barty's the best player on the world, so not a big loss. But Taikman, I want to see how she can back up another potential chance. She's got a pretty good draw if she can get through her first couple of rounds and place Fiontech in the third. So we've got the third section of the draw. We've got the number four seed Pliscava. Takes on the wild card McNally. Winner of that match takes on either Diaz or Anissa Mova in the second round. Then we've got Tomi Anovic versus Voli Nets, the wild card. Winner of that match takes on either a qualifier or the 30th seed Martich in the second round. Then we've got the 24th seed Podosa taking on Van Udvank. Winner of that match takes on either Gracheva or a qualifier in the second round. Then we've got another qualifier in this part of the draw taking on the wild card Kruger. Winner of that match takes on either Risk or the 14th seed Pavlochenkova in the second round. So the players will watch out for, obviously you've got to watch out for Pliscava in this part of the draw being pretty good the last couple of weeks, made, you know, back to back semifinals on hardcourts and also made the USA, what am I saying, Wimbledon final a couple of months ago. So got to keep an eye on her. Also keep an eye on Podosa. Very, very good player. Beat Sabalenka last week in a tournament in the Cincinnati tournament. So keep an eye on Podosa and also Pavlochenkova. I want to see how she can do on hardcourts. She obviously made the French open final, had a great run there a couple of months ago, but hasn't really backed it up. So I want to see how she does in this event. All right, Petri Kravitava. Number 10 seed takes on her cog in the first round. Winner of that takes on either Kovnich or a qualifier in the second round. Sevastova versus Sinyakova. Winner of that match takes on either Kostjak or the 17th seed Sikari in the second round. Then we've got the 27th seed OstaPenko taking on Podoroska. Winner of that match takes on either Sampsonova or a qualifier in the second round. Then we've got Davis versus another qualifier. Winner of that match takes on either Golubic or the number eight seed Andrescu who is defending points from two years ago. So a lot of big names in this one, but still a wide open part of the draw for me. Obviously got to keep an eye on Andrescu. Played well here two years ago. Didn't play last year. So let's see how she can play in America, especially with the crowds. She was a crowd favorite two years ago. Kovnitava, former world number one, Grand Same Champion, got to keep an eye on her in every draw that she plays. And also Sikari. I want to see how Sikari does because it feels like she had a great start to the year and hasn't done much since. So I want to see what Sikari can do. And who knows, the draw might open up for her and she might be able to do something crazy. All right, so the top half of the bottom, so the top section of the bottom half, we've got the number five Seeds Fetalina. She takes on a qualifier in the first round. Winner of that match takes on either another qualifier or Bogdan in the second round. Then we've got Vondresova who's a very tough opponent. Watch out for her. Very dangerous. She gets a qualifier in the first round. Winner of that match takes on either Parankova who's a 25th seed Kazakina in the second round. Then we've got the number 19 Seed Rabakina taking on Sancinovich. Winner of that match takes on either Garcia or the qualifier in the second round. Then we've got Lee versus another qualifier. And winner of that match takes on one of the best first round matches going around. Georgie, the Canadian Open Champion against Samona Halep, the 12th seed of fire matchup. Circle that one as one to watch very tough matchup for Samona Halep. But players watch out for, obviously you've got to watch out for Halep. She is a very dangerous player when she's playing well. She's the Grand Slam Champion, world number one, at her best. Got to watch out for her. And also Svetalina. She made the semi-finals here two years ago, lost to Serena in the end. Got to watch out for her, the number five seed. And got a couple of qualifiers potentially in the first couple of rounds. And also Vondresova. I think she, you know, semi-finalists, sorry, not semi-finalists. Silver medalist at the Olympics. Got to watch out for her. I think she's a very dangerous player and she's proven that she could beat anyone on any day. All right, let's go to the next section of the draw. We've got Kerber. She takes on Yastremska. So 16 seed Kerber taking on Yastremska in the first round. That is a tough first round matchup for Angelique Kerber. Winner of that match takes on either a qualifier or Kalanina in the second round. Then we've got a repeat of a previous US Open final from a few years ago. Keynes versus Stevens. Circle that one as one to watch. Gonna be very fun to watch that one. Winner of that match takes on either Lynette or the 21st seed Goff in the second round. So that is gonna be a nightmare for all those players, to be honest. Then we've got the 31 seed Puttenseva taking on Kanepi. Winner of that match takes on either Fernandez or a qualifier in the second round. Then we've got the Wildcard Parks taking on a qualifier. Winner of that match takes on either Buscova or the third seed Osaka, who is of course the defending champion as well. So players watch out for Nami Osaka. We're all watching out for her. Can she back it up and can she win another US Open? She's got two already. Can she go back to back in consecutive years? Also, Angelique Kerber. Had a pretty good couple of months, made obviously the semi-finals of Wimbledon. Let's see if she can back it up on this court. And of course, Toge Goff. Gotta keep an eye on her, especially with the crowds coming back to New York. She's gonna have a lot of crowd support. So keep an eye on Goff during this tournament for sure. Okay, Kredge Kober. Number 18, she takes on a qualifier in the first round. Winner of that match takes on either the Wildcard Navarro or McNally in the second round. Battle of the Americans. Then we've got Mladjanovic vs. Konsar. Winner of that match takes on either Irani or the 32nd seed Alexandrova in the second round. Then we've got the number 18 seed and the finalist of last year, Azarenka, taking on Martin Kober. Winner of that match takes on either Polini or Svedova in the second round. Then we've got Pekovic vs. Bogu. Winner of that match takes on either Vekic or the number nine seed Mugaruta in the second round. So players to watch out for, Kredge Kober, French Open Champion. Got to watch out for her. Has proven that she can play on hardcourts as well the last couple of months. Won a title on hardcourts a couple of weeks ago. Mugaruta, got to keep an eye on her as well. Obviously Grand Samp Champion, former World No. 1, always got to keep an eye on them. And Azarenka, hasn't had a great year this year, has been injured a lot in 2021, but she has a lot of points to back up and made the final here back in 2020. Lost to Osaka actually won the first set against Osaka pretty easily. So keep an eye on Azarenka. She has played well here in the last year or so. And the final section of the draw we have, Lise Mertens, number 15 seed takes on Pedersen. Winner of that match takes on either a qualifier or Blinkova in the second round. Then we've got Jorovic vs. Serrano. Winner of that match takes on either Kornay or the 20th seed Jabor in the second round. Then we've got the number 26 seed Collins taking on Suarez Navarro in the first round. Winner of that match takes on either Watson or Juvan in the second round. Then we've got Perra vs. Zedenszek. Winner of that takes on either Stojanovic or the number two seed Sabalenka in the second round. So players to watch out for, clearly Sabalenka. New world number two. She's officially the number two in the world. High ranking for her, highest in her career. Gotta watch out for her. Also keep an eye on Collins. Had a very, very good couple of weeks. Won her first two titles. One on Clay Court, one on a Hard Court over the last couple of weeks and beat Simone Heller a couple of weeks ago. So keep an eye on Danielle Collins and of course Jabor. Another player that is a very dangerous player. So gotta keep an eye on her as well and has a pretty good draw and who knows. She could take out Sabalenka in the fourth round if they do end up playing. Man, man, man. All right.


I have to tell you, I am surprised at just how well the government is actually working together to take crypto and digital assets down a peg. And quite honestly, I didn't think they had a hidden. So today, we're going to take a look at what's happening on the state level, on the federal level, and we'll take a look at different branches that are really causing a little bit of havoc in our space. But before we talk about these things, and of course, it is a little bit negative, but you have to remember that nothing is permanent. You have to remember that right now, as time is moving on, we've actually been doing pretty good for this month itself. I know September has been historically, we talked about this many a time, how it's been not the greatest month for crypto in our market, also in the traditional finance space as well. September has been a pretty awful month, and so far, it's pretty good, 3.27% up for the month of September. And historically speaking, over like 13, 14 years, we can see that usually it's a red month. So when we talk about these things, take it with a grain of salt, and just think about it, about how much effort and control the government has put into these efforts to cause disturbance in our market and where we're actually at right now. And also, I need you to remember one important thing, and that is that be attentive to the individuals and the groups that are really working out against you.  There are the people that are taking billions upon billions from you, the Ponzi artists, the schemers, and the people that are just really causing a lot of problems. And there's the people behind the power in the shadows that are really taking a big chunk out, and those are the atrociousness that is out there. So just remember that in the crypto space, we seem to want to fight a lot, but just remember who the real people behind the power actually are. And then also, I need you to remember that everything starts at the top. I know we talk about these agencies, we're going to talk about the state level and judicial and executive and legislative branches, but you have to understand that crypto right now is not looked favorably upon from the top. And the top is the White House. And the White House right now is controlled by Democrats. I'm not a big political person, but that's just how it is right now. And there's been a couple of reports that have been put out. We've done a couple of videos on them. One of those being climate energy change. This is back September 2022, just about a year ago. And more recently, the Biden administration's roadmap to mitigate crypto's risks. They talk about just how awful it is. And this was on January of this year. So just remember that, that everything starts with the top. And moving forward, it's not going to change until some things change at the top. And that's really what it's going to come down to. So let's start off with the state level. So the state level in the U.S., the New York Department of Financial Services, they just put out a guideline, a ruling, pretty much delisting a couple of different cryptos for New York State. Now, why is this so important? It's not important for the general government in general. This is only has to do with New York State. However, with the problems that are going on in the branches of government and people dragging their feet and not giving regulatory clarity, some state has to step up. And unfortunately, that's New York and they're going to kind of put a hindrance on things. Here's what's happened. So the New York Department of Financial Services updated guidance includes tightening risk assessment standards and additional requirements to its coin delisting and listing policies. Requirements tied to the NYDFS requires VC entities to delist or otherwise limit New Yorkers access to coins that are not included on the green list. What's that? I'll tell you in a second. The green list is a DFS controlled list of cryptos that can be listed by companies without prior DFS approval. Essentially, they can say, look, we can put whatever we want here as long as it's on this fantastic list. And the list itself previously included 25 tokens. Approved for custody listing or both. Those include Bitcoin, Dogecoin, Ethereum, Litecoin, Ripple, and a new PayPal dollar. For some reason, PayPal dollar got on there. And we're going to see it right here, that this was the old version of what was actually able to be listed without going through a lot of hoops and hoolas for crypto. And approved for custody, they had Binance, it's at one point. Binance USD, Bitcoin, Bitcoin Cash, Ethereum, Gemini dollar, Ethereum classic, Litecoin, Pax Gold. And of course, for listing Binance, Bitcoin, Bitcoin Cash, Ethereum, Litecoin, Pax Gold, and now they are reducing that down to just a handful, which is this. Now it's just eight. And it's pretty much Bitcoin, Ethereum, Gemini dollar, PayPal dollar, Pax, Pax Gold, couple stable coins. That's it. So they're really just going, look, we don't know what's going on with crypto. We don't want to deal with it. And we're going to move in the direction of safety and not allow these to be listed evergreen. And of course, for the delisting process, we'll take a little bit of an account there. And you can just see that as time goes on, things just shrink and shrink and shrink. And again, I think everything comes up from the top. Now, how does it, how is this affected crypto in general? Like, I'm pretty good. Right now, everything's up.  Dogecoin, which I guess is some issue, still up 1% today. Swann, Tron, Polkadot, where's Litecoin? Litecoin's up 5%, 14%. So again, when all these things that are happening and you worried about it and you're going to hear these articles and you're going to hear these things talk about it and you need to get some type of reference to what's happening, you have to understand the government has its job. They try to do this thing. But in all honesty, crypto is inevitable moving forward. Things that concerns me is things like operation chokepoint 2.0 and those types of things. So that takes a look at the state level. Now let's take a look at the federal level. And we'll take a look at the legislative branch. The legislative branch of the government. There's three branches. You got legislative, which makes the laws. Executive, which carries out the laws and judicial, which evaluates. So legislative, the ones that makes the laws, that would be Congress. I know Gary Gemsler thinks he actually makes the laws. He does not. He's supposed to carry them out. And judicial evaluates the laws, such as like the Supreme Court executive being in the White House. So when this came out, and this is going to be another shock to the system, people are like, oh my God, no, this is awful. Nine U.S. senators publicly back Elizabeth Warren's crypto bill. Look, I don't know what the problem is with Elizabeth Warren and crypto. I know that she has an issue with centralized exchanges. So do I. And I think so do you. I don't think we like the centralized exchanges that commingle their funds and screw us over to reform Ponzi schemes, like with SPF and FTX. Of course, there was also the Voyager, the Celsius and the Blockfies out there. So I think on that page, we totally are on track. The problem is I don't see the rationale for what she's talking about as far as like Bitcoin, we have to get rid of it. And it's just awful. So you're going to see these articles, you know what's happening. So there's a press release and Warren's official Senate webpage, and they named Democratic Party. And I want you to understand why I say this and why it's written here. Democratic Party senators, Democratic Party senators, birds of a feather, ruled together. And that's what Democrats usually do. That's what Republicans do. They're in their group and their system. So when they come together, of course, they're going to stick together. So you got nine. You got Gary Peters, Durbin Smith, Shahan Casey, Blumenthal, but I don't know. I don't even know these people. Along with independent senators, Angus King is those who joined the bipartisan coalition supporting the bill. To be quite honest, it talks about how awful it is and it's going to really be a shock to the system. But you have to remember something. You need a majority vote. And for senators in the United States, we have 50 states still. And you get two senators per state. And if then to the majority, you got to hit 50 if my math is correct. And of course, on those 50, the person that breaks that vote would be the vice president if there is a stalemate, which there is right now. Because right now, the majority party is Democrats with 48 seats. Minority Republicans are 50 seats. And there's two independents, the ones that we just, and one of them we just named right there, but they all caucus, so they all vote with the Democrats. Save honor. So right now, yes, Senator Elizabeth Warren does have, for some reason, nine people in her pocket. And she's going to come out and talk about an anti-crypto army. But we'll see how it all plays out. And you have to understand as time is going on, I don't think people are very trusting of some of the things that are being said by certain senators and moving forward. And also remember that next year, specifically November 2024, we're going to have an election. And I don't know which way that election will go, but I know that Congress, assuming the House of Representatives is already controlled by Republicans, and I might suspect that also it'll fall from the Democrats as well. So we'll see if this actually goes through, if she can get a majority. But again, you have to understand there are minutiae in different parts of this. And just because she has more people who she has picked up, doesn't mean that everybody wants this to actually happen. And that would take care of parts, the legislative. Now let's go talk about the executive, Gary in the SEC. Gary's got a problem, and Gary keeps losing cases. And Gary has missed a lot. We all know that. And Gary so far, the only thing he's really protected us from so far is staking with Kraken. So good job for you, Gary. I get it. But now he's going to dump a dead horse with this Binance US. And I have no problems with this. I honestly don't have a problem. But it just seems like because you sat down with SPF, you sat down with FTX, you have a lot of things that are in the closet with those entities. And now it's all about, we're going to protect you from this way. And we're going to protect you from influencers. And we're going to protect you from this. And I'm like, where were you before? What were you doing? Anyhow, SEC rips into Binance US over shaky asset custody. I just want to ask a question. Does anybody use Binance US here? Does anybody use it? Does anybody look into you to use it? Does anybody like, I got to get into that? Well, whatever it is, right now the SEC is trying to tear apart Binance US. Thanks. And I could read the whole article, but it's quite boring. What really comes out of this, the regulator SEC accused Binance SEC of inconsistent representations about key facts, slow rolled small productions of documents and information, installed walled on entire categories of info that would likely shed light in its shaky assertions concerning the custody of customer assets. Really what it would come down to is this. The SEC says, look, there's no way you guys resolve it. And we're going to prove it. And we're going to ask for depositions. And we're going to grind you to a halt.  I could care, I couldn't care less. And then they'll probably go after CZ Binance in some way, shape, or form. I will say this though. And before anybody says that's fine, that's fine, that's fine. It may be, I don't know. I don't have any insider information on Binance US, but it is interesting. This is a list of key execs to live, to leave Binance in 2023. And I know Binance has a lot of people working for it. So I'm not talking about the volume of people, it's the people and the positions that have left. On July 6th, he had Matt Price, Senior Director of Global Investigations and Intelligence of Binance. He's gone. July 6th, Steve Milton, Global Vice President of Marketing. Also July 6th, Han, General Counsel, left. Patrick Hillman, Chief Strategy Officer. July 7th, Steve Christie, Senior VP for Compliance. August 31st, Leon Fung, Head of Asia Pacific. September 4th, Mayor Kamat, Product Lead. And then some other people out of nowhere, they are. And then also just a couple of days ago, the CEO stepped down.  I mean, sure, I guess that's what happened. When CEOs and Head of Global Strategy starts stepping down and the main guy's like, it's okay. I mean, I don't know. It just looks a little suspicious. And we'll see how it all plays out. Maybe even wrong. Maybe, you know, CZ is just like, this is just fun and whatever it is. But, you know, I've, I'm quite a cynic these days. Behind every cynic is a broken optimist. And that would be me. And then lastly, congratulations to BitBoy. I just, this just came across my desk. I thought that was quite interesting that Ben Armstrong was dismissed from the FTX case. And then there's three celebrities that settled down. I want you to notice that he was dismissed from the case. He didn't settle. He was dismissed. And I don't really know what's happening. But I think on this situation, I remember watching some of Ben's videos about him talking about FTX and what had happened and the things that he got behind it for months and months and months before it actually happened. So, I mean, there's that. So, I guess that's a step in the right direction for Ben and what's happening. But just to sum all this up and to say very, very easily. Over the next couple of months and things that are going to happen, it's going to be kind of a roller coaster ride. And it's going to be very bumpy. It's going to be kind of crappy, I'll be honest with you. But, you know, when I got in 2017 and 2018, the White House wasn't talking about crypto. There were no major institutions getting into digital assets. There wasn't a massive fund talking about how Bitcoin is digital gold. There wasn't legislation that was actually being approved in different parts of Europe and Southeast Asia. There was a lot of things that could have gone wrong that didn't. And these days, I know that we look at these things, we're like, ah, this will never come back. But in all honesty, everything we just talked about look at the things that are being built and the different price action. Actually, that's doing pretty well. And all things are progressing forward. I have no doubt where things are going. They still don't know when we'll get there. And that's it for today. So look, if you like today's video, give it a thumbs up, consider subscribing. Everything we talk about is time sensitive, all that good stuff. Now, if you'd like to stick around, we'll answer all your questions, the best of my abilities, and we'll go from there.  Thanks for stopping by. And that is it.


This 2016 Chevy Silverado 3500 Crew Cab Long Box dual rear wheel is stock number 12174Z. We are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used heavy-duty truck headquarters. This 2016 Chevy Silverado 3500 has the 6.6 liter Duramax diesel with the LML engine. It pumps out 397 horsepower. This truck has been fully safety and inspected by our service shop. Has a fresh oil and filter change. All the fluids have been checked and topped off per the state of Wisconsin inspection process. And this truck is 100% ready to go. Summit White is the color. We shoot all of our videos in 1080p, 60 frames per second. So if you have HD capabilities on your computer, tablet, smartphone or television, turn them on right now, because it is definitely your best way to check out the quality, condition and options of the truck before seeing it in person. And if you like the truck and like the video, want to see more videos like it, you can subscribe to our YouTube channel in the lower right hand part of the screen. Click the subscribe button, and then click the bell notifications, you'll get updates on the videos we do each and every day of our new and used inventory here at Summit Auto. Next one comes with the polished aluminum rims. Nice wheel simulators or end caps on there. Has Michelin LTX LT 23580R17 tires, and these tires have right around half the tread left on them. Frame and underbody is in really nice, clean condition. Very little corrosion on there. Front fender is in excellent shape. And if you see any major dents or dings, you get the projector lamp headlamps, the factory fog lights, and the front bumper parking sensors. No major dents or dings on that front bumper. Headlight lenses are nice and clear, and it does come with the chrome trimmed grille. The hood is in very nice shape as well. Pastner side front fender is in excellent shape too. No dents or dings on there. And the passenger side rim, no major scuffs or scrapes. As you go down this side of the truck, take note of how clean the body is, how reflective and mirror-like that paint is. We take these HD videos so if you are far away or even if you're close by and just cannot make the trip down, but you're still interested in purchasing the truck, you can see the truck, hear the truck, and have confidence in the vehicle that you're looking at before you even get here. So when you do get here, there's no surprises, and you can make a smart and informed buying decision from wherever you may be watching this video or checking out our ad. Dualy tub looks really good. This back rim is in pretty nice shape, and the back tires have just as much tread as the front tires. Once again, frame and underbody, you always want to look at those box rails for any corrosion very clean on this truck, just a little bit of light dirt on there. Has all the remaining factory exhaust, so it hasn't been altered in any way. Lower rockers all look really good on this truck, and it does come with the factory chrome step bars. Coming around to the back of the vehicle, rear bumper is in nice shape. No major dents or dings on there. It does have the backup parking sensors, the rear bumper steps, full towing package which includes a receiver hitch, four pin and seven pin wiring. The tailgate's in pretty nice shape. Does have a locking tailgate and a backup camera. Also has the shock down assist tailgate so it's never going to slam down on you. Spray and bed liner, goose neck hitch, and it does have seven pin wiring back here as well. Tailgate shuts nice and solidly, and as you go down the driver's side, just as clean as I pass on your side, no major dents or dings on the box here. For full disclosure, this back rim is in nice shape as well. And down the rest of the side of the truck looks really good. You do get the telescopic tow mirrors, built in directional signals, LED side lights. They do telescope out like that and fold in, I'm guessing these power fold in. Inside the LTZ package gives you the tan leather interior, there are no rips, there are no tears on the seats, they're in really nice condition. Both of these front seats are power, heated, and cooled. Auto headlamps turned off four wheel drive, factory brake controller. You get tilt and telescopic steering wheel, power windows, power locks, power mirrors, steering driver's seat, and those mirrors do power fold in. I always like showing both sides so that you know that all the options are working properly on the truck you're looking at. This one does have the Bose sound system as well. We'll hop inside, take a look at the miles and the radio, and everything that the interior has to offer. 27,911 miles on this truck, instrument cluster is very nice and clean. You get the heated leather wrap steering wheel, Bluetooth and information center controls on the right, cruise controls, forward collision warning controls, and heated steering wheel buttons on the left. Once again no rips or tears on there, does have the Allison six speed automatic transmission with the optional tap shift, the Chevy MyLink system with AM FM and Sirius XM radio capabilities as well as the factory navigation system on here. This also has projection manager where you can project your cell phone to the screen via Android Auto or Apple CarPlay so you can project your cell phone up there if you've got a different navigation system that you like better than the factory one. You can do that or just to play music and stuff through the radio, you can do that as well.  Power pedals, stability control, that's for your LED lighting. Also for your LED side lights on your mirrors and the cargo lamps, parking sensors, lane departure warning and factory exhaust brake. You get two USBs, two 12 volt power points, 110 volt, 150 watt plug-in right there. Passenger side format and seat are in excellent condition, no rips or tears on there, looks really good. Smells very clean inside this truck, I don't think it's ever been smoked in. The headliner is in nice shape, I didn't see any rips or tears up there. Up here you get your power sliding rear window button, your home link buttons for your garage door security systems and lighting systems, map lights and on-star and SOS capabilities in the rear view mirror. We'll take a quick look at the back seats and then we'll start it up and check out under the hood. It does have the wireless cell phone charge pad as well. Back seats are just as clean as the front seats, no rips or tears back here. It does have the latch child safety system for any child car seats you may want to put back here. Power sliding rear window with the built-in rear defrost and once again no rips or tears back here, very nice. And clean, these seats do fold up, carpeting is in excellent condition, get all weather formats back here as well and side curtain airbags. Bottoms of the doors all look really good on this truck. We'll start it up, I'll show you that backup camera and then we'll check out under the hood. Starts right up, no check engine lights or anything like that. There's your backup camera working good. I would personally like to thank you for checking out the video today and hopefully from this HD video, there are those LED side lights. Hopefully from this HD video you will have been able to verify the quality and condition of the truck inside and out so you can have confidence in your next purchase. Under the hood we have the 6.6 liter Duramax diesel LML engine, it's a 397 horsepower engine base, very clean, runs very smooth. Once again this truck has been fully safe and inspected by our service shop, has a fresh oil and filter change, all the fluids have been checked and topped off.  And I would highly recommend this truck from a quality and condition standpoint and to see more pictures of this truck or one of our other 450 new and used cars, trucks, SUVs, minivans, Wranglers, half tons, three quarter tons, one tons, you name it, we got to go to that website right there, www.summitauto.com, full pictures and descriptions of every single vehicle from two locations, all at www.summitauto.com, if you'd like to check out more HD videos you can go to www.youtube.com slash www.summitauto.com, remember to like, subscribe and share on this video and all the videos that you see there. Click the bell notifications, you'll get updates on the videos we do each and every day here at Summit Auto, in fact in a second you will see a link to subscribe to our YouTube channel in the upper left, a link to more Chevy Silverado 3500 truck videos like this one in the upper right, a link to this vehicle on our website in the lower left, and a link to one of our latest YouTube videos in the lower right. Click those, check us out, we're super excited to help you with this Ultra Clean 2016 Chevy Silverado 3500 Crew Cab Long Box Dually LTZ in Summit White Clear Coat, thanks again for checking out the video.


Okay, welcome. We're going to talk a little bit about what's new in OpenShift serverless and some updates about the community. So my name is William Marketo Oliveira. I'm a product manager at Red Hat, and I have here with me, I'm Paul Mori. I lead our serverless engineering team at Red Hat and I'm on Canada Steering. Nice. So let's dive in. But before we go to deep here, let's review some of the first principles that we really use to guide everything we do as far as product and in Red Hat, especially on the cloud team. So of course, we really focus on the openness and working with communities and open standards and driving development with those communities. And you're going to hear some updates about that regarding recent developments in the K-native community. And then on the right side, you have, of course, the hybrid aspect, which is really key for everything we're doing, making sure that the experience that we deliver for those projects as products, they have a great experience on public and on private cloud. And of course, work really well anywhere you want to run OpenShift. Today, we're going to focus on K-native for the most part, like I said. And just to quickly recap what K-native is, again, K-native comes with three main modules. So serving, which is really focused on request-driven compute. So it's a way for you to scale applications up and down, even to zero, based on demand, based on number of requests. Then you have another module called eventing, which is really focused on the infrastructure to send and receive events to, again, start those applications. And then you have, of course, a CLI client, which allows you to interact and build applications using scripts or using your most favorite terminal. Now, the main difference here in where OpenShift serverless is going, right? So we take those bits from K-native, and we extend that with two things for the most part. So one is the ability to write functions as well, which is not something that you have available in K-native per se. I get something that we are doing with OpenShift serverless. And we also package all that with an operator that allows you to install, upgrade, and configure really K-native inside OpenShift so that you can leverage other services from the platform as well. Things like logging, metering, monitoring, all of those other services. That's the main, again, difference when you think about OpenShift serverless and K-native. Now, I'll pass the ball to Paul to talk a little bit about some of the updates from the K-native community. Yeah, so let's talk about a subject that's probably important to some extent, at least to almost everybody in this room, which is open governance. If you follow the K-native project, you're probably aware that open governance within K-native is something that we've been working on for quite a while. Earlier this year, we moved to an elected model for the Technical Oversight Committee, or TOC, and had the first elections. And I want to just take a second here and thank everybody that participated in that election process, everybody that ran, and congratulate everybody that was elected. We now have a TOC that is elected and composed of folks from IBM and Red Hat, VMware, and Google. And since that time earlier this year, where we moved to that elected model for the TOC, we have been working toward adopting a similar model in the Steering Committee. And actually, I have good news because I'm here to talk about the specifics of that new model that we've adopted in a new charter. So for context, before we adopted this charter, the Steering Committee had been in a bootstrap phase for quite a while since early 2019. And the model was basically that there were appointed representatives from some specific companies that were most active at the time when the Steering Committee had been formed. So we had some representatives from Google, from IBM, from Red Hat, and VMware. Google had a majority of seats within the Steering Committee, and members of this committee serve as representatives of their employer, as opposed to serving as individual. So additionally, there were no rules or guidance for how new members would be added to Steering and how we would maintain that committee over time. And one of the things that we heard from folks that were interested in engaging in the project was that the lack of clarity around how you would kind of lifecycle this committee in a way sort of encumbered the project because there wasn't a clear way to develop influence at the level of steering. So in the new charter, we adopted some changes that, I think, address those concerns. So before I talk about those, remember, overall the Steering Committee's job is to develop the community and to help grow the project and grow the organization that evolves around that project within the community. So we have moved to a new model where steering will be elected and where no vendor can hold a majority of seats on the Steering Committee. This may sound familiar if you follow Kubernetes governance. In fact, the Kubernetes governance scheme was one of the things that we looked at a lot for inspiration as we came to arrive at this new model. The size of the Steering Committee is five currently, but we will probably add seats next year if the project continues to grow. So in our new model, members of the committee serve as individuals instead of representing their employer, which is also like a very strong principle within Kubernetes governance. And this allows us when we're in the community and we're serving on steering to act with our community hats on, as opposed to our vendor hats, and allows us to just be centered in the fact that we're participating as individuals rather than having to represent necessarily our employer's interests. So in this first year, and we've literally just in the last couple of weeks adopted this new charter. So we're, this is sort of a work in progress to execute it now, but we will have nominations open soon and elections later this year to begin to cycle toward that elected community-based model. We'll have two seats up this year, and there will be at least three seats up for election next year. And that is sort of the TLDR of the steering changes. One of the things that came up in our community discussions around this, and there were a lot of great discussions within the community. In fact, you can go and watch some of the videos online if you would like. But one of the things that came up as we kind of worked through adopting this model in the community was that the question around what is in scope for the Knative trademark is maybe a better fit for a committee with a slightly different organizational scheme, since trademark is probably most important to vendors. So what we did, and I will just go ahead and advance the slide now, is we have moved the trademark concern into a new committee called the Knative Trademark Committee, or KTC. And this committee is going to govern the scope of the trademark, which currently contains the serving and eventing projects. The seats on the KTC are held by vendors, and members of this committee represent their employers. And currently this committee looks sort of similar to the bootstrap steering, in that we have Google represented as the owner of the project. We have IBM and Red Hat represented and VMware represented. Going forward, the KTC will consider adding new members every year. So this is something else that I wanted to make sure that we touched on in this update, because it helps to address that concern of clarity around how can you, as an individual or as someone making choices about where you spend your developer's open source time, engage with the Knative project and help to develop influence. So going back to the KTC, when they look at adding new members, they'll consider contributions that any particular vendor has made. And there's also a process that allows vendors to articulate maybe some contributions that they've made that are hard to count, because not every open source contribution is easy to quantify. It's sort of easy to think about counting commits. It's less easy to think about things that don't touch GitHub or that are maybe harder to count, like influencing a design discussion, that type of thing. So in the event that you're thinking about engaging with the project, just know that when we consider membership in the trademark committee, that any contribution counts and can be counted. And there's a process for folks that, like if you feel like maybe you did more of things that didn't touch GitHub than things that did, you can articulate that with the exception process. So. Go ahead, William. Yes. So for example, so examples, documentation, or even just participating in some of these meetings that we host publicly upstream, those all count as contributions, right? Absolutely, yeah. And since we know that it's one hard to count some types of contributions, and it's also hard to even foresee all types of contributions, that in the event that there's something you want to make sure the trademark committee considers, you can write up a blurb, articulating what you feel your organizational contributions are. Nice. That's awesome. So the key takeaways I want to leave folks with around governance is that we have significantly improved clarity around the governance in these two different dimensions around the steering committee and trademark committee's composition of those committees, elections for steering and who can serve clarity around how vendors can get a seat on the trademark committee. And of course, great community participation during this process. I really want to just take a second here and thank everybody that participated, both my colleagues at Red Hat and my open source colleagues in the community. I'm really happy to be able to give you all this update today, and I think that community participation was really key to making that happen. So thanks everybody that participated, and if you're really interested in how this particular sausage was made, you can go and watch the videos online if you search for Knative Steering Committee. Nice, yeah, definitely. So elections and everything going on this year, not only in the US, but I guess then also in open source projects. That's awesome, great. Yes. So let's do a quick recap on serving now. And again, the idea here is really just to do a brief recap and Paul and I here, we'll talk a little bit about some of the main components that are part of serving, starting with service. So what's a service, Paul? What's a Knative Service? That's a good question, and don't let the name fool you. It's different from the Kubernetes resource called Service. It's not the name I would have personally chosen. In fact, there was a long drawn out process of arriving at this name in the community that the project had at the time. But when you think of what a Knative Service is, it is basically a very high level resource that is similar in certain ways to a Kubernetes deployment in the sense that it generates these other resources that actually go to do the work. So configuration is basically like the highest level container that we have, no pun intended, from an API standpoint that encapsulates the configuration for the serverless service that you're deploying and the routes that bring traffic into it. So moving down into what those mean, there's a resource called configuration, and its job is to generate immutable snapshots of an application called revisions that the routes that are also specified in the service bring traffic into. So you can think about that service as sort of a serverless flavor of deployment where you can specify both the things that you'd expect to specify in a normal Kubernetes deployment as well as information about how traffic should go into those revisions that are created and how the traffic should be split. Yeah, what I really like about revisions and this idea of snapshot is really this ability to enforce some best practices as far as, again, every time you push a new change to either configuration or code to your application, that snapshot is going to be generated. And that allows you, for example, to do things like maybe you want to generate a preview URL for that particular version of the application, but you don't want all the production traffic to go to that particular version of your application, right? Maybe you want to do what they call a dark launch. So it's just people that know the URL, so it's going to automatically be generated a random URL for that revision. You can influence that, of course, if you want. But that's one of the patterns that I see that is really useful for revisions here. And then another one, of course, is the usual A-B split or canary deployments and whatnot. But this idea of doing live previews of a code that, again, you may not want all the production traffic to consume yet. I think it's really, really powerful, right? And one thing also... Absolutely, yeah. ...is that that traffic split, it can happen, like all this functionality is provided out of the box just with K-Native. But you can also extend that with a service match, right? You can use a service match if you want as well. But that's an option. It's not something that we are imposing in order to perform that traffic split, right, Paul? Yep, yep, and I agree that the ability to just get traffic splitting out of the box is really, really powerful. If I think about my previous industry experience around we want to test some alpha feature and we want to send maybe 1% of traffic to that and just see what happens. I have spent time writing infrastructure to do that, so getting it out of the box is pretty wild. Pretty cool. Yep, yep. One thing also that we are working internally as far as experiences in OpenShift is to make sure that there is an easier path for you to generate those snapshots, those revisions, using pipelines, right? For example, Tecton. So now you have a CI pipeline that can from a Git project build and deploy a new version of your application and automatically generate a preview URL for your app. And maybe you want to post that back, for example, in your PR so that the engineering team or maybe your designers they can see the layout, they can interact with it, and then only after that you eventually promote that application to broad, right? It's really, really interesting. Cool, so that's essentially serving in a nutshell and then of course one thing that we did not touch as far as APIs, but that's just inherent of this model is the ability to scale up and down based on requests, right? So that's what's really triggering this application here and those requests, again, they can be HTTP, of course, but they can also be cloud events, right? They will be wrapped in HTTP requests but the payload itself can be a cloud event which really leads us into the next section here about eventing, waiting for my slides to reload. There you go. Which eventing is really the module that we want to talk more about today because, again, serving was already considered GA in OpenShift serverless since March, I believe, and now we are finally taking into consideration eventing as well and considering eventing a GA module, right? And with eventing, you essentially have the ability to connect external systems to your application, right? So maybe you want to cover some of those APIs then. Absolutely, yes. So let's start with sort of the earlier generation APIs which are single-tenant. In this earlier regime that was developed early in the project's life cycle, early in the project's lifetime, there are event sources and you can think of these as the on-ramps for events to come into the system. There's a variety of these for different cloud services for different middleware brokers. I probably shouldn't have used the term broker or maybe we should have used the term broker in eventing, but when I say broker here, I mean like MQ broker type thing or Kafka. So there are a number of different event sources that are the on-ramps for events to come into the system and of course you can build your own if the exact one that you want doesn't exist. Inside the system, using that like transportation analogy, there's something called a channel and you can think of this as a channel is the road that an event that's come on to that on-ramp travels through the system using and these are basically forwarding and eventing persistence layer. There's an in-memory implementation that's maybe more suitable for development but then there are also flavors backed by different durable stores like active MQ or Kafka and again these are the roads that events travel over and continuing that analogy to just one final API resource subscriptions are what connects events that are traveling in channels to their consumers. So like maybe you can think about the subscription is like the garage door. So you get in through the on-ramp, you travel along the road to where your destination is by passing through that subscription garage door. And the receiver on the other end of that subscription can be a K-native service but it can also be a normal deployment or something else. So those are kind of the first generation eventing resources. More recently we've got what you might call eventing mesh APIs and the whole thing there that we'll talk about is the broker. The broker is an entity that can send and receive messages from multiple sources and subscribers. Brokers work with triggers where the trigger sits between the broker and the receiver of the event and implements filtering. So if you don't want every event that's going into a broker to be received by a particular receiver you can use a trigger to filter those events out. And then there are some additional higher level APIs and we're thinking here about patterns of enterprise integration. There's a sequence that allows you to wire an ordered series of subscribers and sort of generates the channel and subscriber setup that you need to pass from A to B to C to D. And then there's another variant called a parallel that allows you to wire a fan out to multiple subscribers and associate filters with all of those. Nice. So kind of drawing a diagram with those APIs you would get this diagram here where again you see at the top the broker again you're seeing you're seeing all the different sources and the multiple event types going so two one and three there should be a three. But then you see that the broker then is doing the filtering and say hey these types of events I'm sending to this application that's represented by a sync and then this other type of event I'm filtering right and sending to a different sync that this this built-in routing and filtering mechanism is again it's really powerful and it can implement it can be used to implement many of these EIPs and then the channel again just adding a diagram to that the idea here is that you essentially could have multiple sources sending different event types but that channel now will carry that event send all of those events to the subscribers right that's where the subscription comes into play and your application would be a sync there but keep in mind again as Paul said that the sync could be a K-native service it could be a URI right and it could be just a Kubernetes deployment as well so this is what's coming as far as GA and we're going to see a little demo of that as well toward the end but there's another thing that OpenShift Server also does to K-native I would say we extend K-native with functions and functions is something that people often associate whenever they hear the word serverless but what we want to make sure that people understand and one of the key differences between just serverless containers and serverless functions is really what goes inside the container that your application will be running right so whenever you're doing a serverless container or building a serverless container you're responsible for what goes inside that container right we don't we have some very small requirements there for example we want to send those events through an HTTP request but those applications can still receive of course cloud events as part of the payload or just any HTTP request so this is a very good way for you to package or reuse current microservices that you have or any containerized application that you might have that fits this model and run that application as serverless so now that application can scale up and down can receive events etc etc and you can use of course any programming language of choice you can package whatever you want inside that container now when you transition to this serverless functions model that's where you get this extra piece of code that is the function runtime and the function runtime really helps you as far as implementing this HTTP server this wrapper around how you're going to receive those events and how those events are going to be sent to your user code and also because we are in control of that function runtime we can be a little bit more opinionated about it so for example maybe there's something specific that we want to do as far as tracing we can package that tracing capability in our function runtime where in a container you can still of course have some choices and decide to choose your own implementation or go in a different route there so that would be the difference here now looking at most solutions in the market today I would say that again quite often you have to choose between one or the other and they have completely different user experiences I think the main difference that openshift serverless is bringing here is this idea of running serverless containers and functions in the same experience right you have the same exact user flow you can go back and forth you may start with a container and you may see a good fit for benefiting from a function or vice versa you can start with a function and say you know what I actually want to do certain things that I don't have a function runtime for I want to run that application as a container now so you can choose to go either way yeah and I think that's a great quality for us to have because if we look at how folks tend to use functions and microservices that like it's very common to have a spectrum of things that maybe you've got some microservices that that evolve out of functions and maybe some microservices that you already had that you want to you want to get the benefit of event activating those things and scale to and from zero but you also have things that you're implementing as functions so it's nice that we treat them similarly because there is that interplay and back and forth and evolution of systems that we maybe start out using functions and evolve to microservices or decompose a microservice into functions yeah that's super powerful so essentially what we are doing with with functions then right we want to make sure that you inherit and benefit from everything K native already provides so what we are doing is really providing a plug-in to K and K and as a C Li for K native and that plug-in we are calling it fast for now that plug-in allows you to have a local developer experience super important if you want to iterate really fast and you may not have access to a cluster or to the cloud all the time so again you can have a local build experience and iterate but when you build we want to make sure that the way you are producing those containers is also standardized so we are leveraging build packs for that and we are already providing build packs for three run time so park with node and go but that list of course will extend as we progress on our journey from developer preview to technology preview but once you build those containers using the fast C Li you can then of course deploy and when you deploy they become K native services right that's again all the things that we talked about here for serving or eventing they apply and some of the things that you see as well as far as developer experience they still apply as well and then another important aspect like we said is that you may want to build web apps just vanilla web apps you can do that with functions too it's a very common pattern you can implement single page apps or things of that nature but one of the most powerful use cases for functions and servers of course is to deal with events so you can receive cloud events with your functions as well and we're going to see a little bit of that experience in the demo now that I pre-recorded I pre-recorded to make sure I could talk and speak I could talk and not be concerned with typing at the same time let me start sharing my screen here and I will walk through that and then if we have enough time I can do also like a little live demo of our console as well so I'll hit play here so I have an empty directory and the very first command we're going to do let me do a quick pause there is KNFES init and I'm going to specify what type of function that is so that the template that the tool will generate is already configured for that particular type so it could be events again it's going to then receive cloud events or HTTP and then the dash L is going to be used to specify what programming language you want to use for the runtime in this case we're picking so now triggering a build again is KNFES build notice that of course I'm not specifying any particular details about a docker file there is nothing like that that we're requiring a developer to do and here below you can see the template the function itself that got generated and because I selected cloud events you see that the context is sending your application to a cloud event that's kind of how you can extract the cloud event and the data from that context inside your function but this is all the code that you have now in order to process a cloud event not that the build is done I'm just going to perform a deploy and on the left side you see the open shift console so here I already have 2k native services running one part was one and another spring application and they are connected to a channel remember that Paul explained that a channel is this path that is going to carry events from event sources to your application so here I have 2 event sources just for the sake of demo I'm using a Jira event source and a pink source which is kind of a timer just to keep sending events to those applications but now I just deploy the function and as you can see it's going to land in that topology view inside just like any other application and now I can just wire that application literally drag and dropping I mean I can use a CLI as well for that KN provides a few commands that you can use to do the same thing and subscribe to a channel and subscribe to an event source but here I'm literally just drag and dropping using the UI and now I'm going to subscribe that function to that same channel so now every update on Jira or every event that this timer will trigger they will land on this microservice that is built in orcas on this spring application that is also another microservice and on this function that we just deployed using the function functionality of OpenShift server which is built in JavaScript so again very short very simple but still it's a very very interesting and very powerful now one of the things that I want to just call attention to if we can just pause this here is that if you look at the channel that has a little binary type of text on it you'll notice that's an in-memory channel and that is something that is probably workable for you as a developer in production where you don't want to have the chance of lost events you'd probably be backing that with something like a Kafka yeah so let's take a look at the topology view and now I'm going a little bit off script here but just to show you a live cluster as well we recorded that so I could probably talk and do the demo at the same time but first thing here so this experience this visualization that you're seeing here is really the way we are showing multiple revisions for one application and in this case you can see that this application this particular revision has 100% of the traffic and then I have this other applications here that are essentially representing PRs the number of the PR that was triggered that was sent and then triggered a pipeline that built this container as a revision here they all have 0% of the traffic but as I hit those URLs you see that they will start from 0 but they all have unique URLs so again this is the 14 PR 14 this is the PR 15 but if I hit of course the main URL for the service that is going to trigger the one that has 100% of the traffic now for this experience again you can of course click the traffic split using the CLI but we also offer a way to do that using the UI as well so I can say you know what I think this one here will take 50% of the traffic and I want the latest PR that's the one I think it's good to take 15% of the 50% of the traffic and now you see so now if I hit the URL the main URL I'll have a 50% chance to hit any of these particular versions of my application now as far as the venting and to to build on what Paul just said whenever you are creating a channel we offer an experience where again you can just select in memory and that's going to create a one in memory channel or you can select Kafka right and now you need to inform of course what Kafka broker you want to use that was already pre-configured for the venting installation in this cluster and you can literally just specify the name of the broker here so let's say my broker and that's going to be then backed by a Kafka channel for a durable and more reliable persistency right when sending in receiving events and the last piece of share very briefly here is the event source experience as well these are some of the event sources that we have out of the box again you can select Kafka that's of course one very popular one you can just point to the bootstrap server and start receiving events you can pick any of the event sources powered by Camo K so let's say I can pick SQS you provide the configuration here for now this experience is YAML we are working on that to make sure that we have forms auto-generated for event sources as well but it's in a very simple configuration just of course your keys and the Q name for SQS hit create and that's going to create the event source for you so I'll do one for Kafka of course one thing that I have already running in my OpenShift cluster pick the consumer group and here I'm going to select so I could use a URI so this could be any destination any URI it can receive that Kafka message or an application in this case I'm just going to select the previous application that I built and hit create you see that now I have a Kafka source connected to this server application to send and receive events now one of the things that I thought would probably be good to just disambiguate in case there was any question is that when we talk about the Kafka source this would be something that you would use to consume events that were in a Kafka topic so as opposed to Kafka backing a channel where the Kafka topic is a durable store for events this is if you actually wanted to consume events that were in a Kafka topic right William right that's correct as just demonstrating how the experience would be again if you want to connect now your in-memory channel to your application and then eventually land the event source to this channel here as well now I am running 4.5 nightly 4.6 nightly build so maybe there's something here that my drag and drop is not doing properly but you get the idea right I'll go back to the slides now I guess one brief thing that I would just point out is this integration that we did with pipelines as well which again it allows you to produce a pipeline out of the box whenever you're importing an application from Git and I'll just very quickly show you that I know we are getting close on time but let's say I'll pick one particular application here so I'll pick this vanilla spring application from upstream select Java select Knative service and now here I can select add a pipeline so this is going to generate a tact on pipeline that can be used to build my application and you see that again I had not to create this pipeline from scratch this was just part of the in part flow from Git when I hit create it's going to then start a build and eventually you see the build is new the build will be updated to running and your application will be completed here and when I go to pipeline you see that there is a new pipeline that was created and you can still configure that pipeline if you want using either the pipeline builder adding more steps to your pipeline if you want or editing the YAML so very very interesting experience and again very easy to get started as well let me go back to the slides stop sharing my screen real quick so this is pretty much all we had anything else you want to talk about today or is this interesting enough update for folks today well I always have trouble calibrating to that it doesn't get easier when there's no heads nodding in the room that you can kind of look at but I think we've hit folks with a lot of information so I'll just say thanks a lot for watching our session everybody and hope that you can check out OpenShift Serverless and the Knative project we'd love to have you contribute love to have you involved in the Knative community thanks a lot thank you very much and if you have any questions don't hesitate to reach both of us on Twitter thank you folks, bye


middle there and we've touched on a few earlier in terms of things like beavers where there's a complex way of how we manage those they have up conservation concerns so we should be able to use the support framework to help farmers support and host to those species but at the same time use the other tools available such as licensing and to manage individual animals so that I think we should try and articulate that in the framework and you know just coming down to us where we could actually have the new measures two big ones to help us ease this language change one is trees on farms and I say that deliberately compared to woodland because you know current woodland is considered down to sort of like 200 stems per hectare but actually there's a huge amount of woodland expansion we could do through much much lower densities and stitching trees into farm land and that could be very much part of the support framework rather than a separate forestry grand scheme the way we currently do it and the other one is deer on that species framework deer at the bottom at the bottom end is a utilisable resource that is abundant and is causing hindering all those aspects of land exchange, peatland restoration within the expansion so we could have anuvertly deer incentive there. I certainly support those comments about trees on farms and deers but I was just going to answer any terms of thinking about additional schemes of support I think I mentioned earlier that there doesn't appear to be provision in schedule one for kind of payments for a facilitation for collaborative management for landscape scale under the previous rule development programme there was supposed to be an environmental corporation action fund which never got off the ground but we need to make sure that's part of the future policy and the provisions are there for that and I just wanted to pick up briefly on Davies point about the less favoured area support scheme the financial memorandum suggests that in this context the budget for tiers one and two would include the less favoured area support scheme budget of 66 million actually if you add that into the pot then the amount of money spent on those two tiers would be 89% of the budget not the 79% that I mentioned before nonetheless if that's the case then we would suggest that that needs to be retained within tier two and we've made a case for a specific high nature value farming and crofting support we've got the indicator we know that about 40% of Scotland is what we would class as high nature value farming and crofting predominantly in the highlands and islands that get a very poor deal from the current system but that's also the areas where we have a high proportion of our most important wildlife sites also carbon stores so there's real merit in ensuring those smaller farms and crops which are environmentally important but quite economically fragile and vulnerable can be supported going forward and get a fair deal from the system thank you Allister my apologies I meant to bring you in earlier that's all right thank you actually no i'm going to echo what Ross said I think on deer absolutely would support that a lot of the work on deer currently is looking at deer in the uplands on largest states there's been some progress there but it's really tricky in lowland scotland and therefore I think the opportunity to resource landowners and farmers to do that well in the lowlands a lot of that's going to require the kind of collaboration that vicki mentioned I think that's definitely an area to look at and I just wanted to add a little bit of colour to ross's comment on trees on farms and just reinforce the point that the forestry grant scheme is there to create woodland and forests but there's a huge opportunity to put trees into farms in other ways and and I want to specifically mention hedges vicki kicked off with that we lost 6000 miles of our hedros in scotland in the last century these have opportunities to create biodiversity super highways across some of our most our least biodiversity land sepa have looked at water quality identified 175,000 hectares of of river and water stream corridor where we need to put trees back in again there's opportunities to do that through fgs but a lot of that can be done outside of that and davie's sitting behind a lovely photograph of I think a protected water margin that he and I looked at fairly recently opportunities to integrate trees into that space are very significant and then lastly coming to grazing which which is a huge part of scotland's agriculture we need to put trees into that space not in in woodland but as individual trees small coops is to create the shade and the shelter that's going to be absolutely fundamental to livestock wellbeing and to productivity going forward and actually is perhaps one of the biggest opportunities for boosting biodiversity in that landscape that will never be funded through the foreshore grant scheme and we've got to find creative ways to put that in here we're working with soil association scotland at the moment to look at the details of that and recognising that those schemes don't just need to cover the capital costs and the maintenance costs but we also want to look at what a realistic payment for ecosystem services would be through that so just a flag I'm keen to hear from many colleagues who might be interested in connecting with me on that later on because that's something we want to be publishing towards the summer this year. Thank you. We're going to move on to our final theme, the power to provide for CPD. I'm going to bring in Beatrice Wishart. Thanks, convener, and it's been quite an interesting session so far. I'm sorry, I'm not in the room with you. On the CPD issue and I might go to Kirsty first since she raised the issue early on in the session to ask about the power to provide CPD and whether there's any particular areas that should be required or particularly encouraged. And Kirsty, you mentioned there was a knowledge and skills gap and I wonder if you could expand on that. Yeah, I mean I think the CPD aspect of this bill is going to be incredibly important but I think it'll be how we actually implement that's going to be incredibly important as well because obviously we want farmers and crofters and growers to want to do it, not to feel they have to do it. It's got to work in with their systems and their farms as we know every farm and every croft and every market garden is very unique and the needs will be different. The way I've been working within this knowledge transfer world is looking at peer-to-peer and how actually farmers and crofters can learn from each other and that knowledge transfer that's that work. From what I've seen over the last three years that works really well. There's a level of trust and there's something in actually seeing something to believe it. When we talk about you know these are big, big changes that we're asking farmers and crofters and growers to do in an environment that isn't really set up that makes sense for them at the moment. There's no particular market routes or you know it is quite a that will develop the supply chain will develop that will push change on to farmers and crofters but at the moment they're kind of doing it against the grain so I think there's a level of trust there. We would I think what's really important at farmers and crofters and growers have the options to choose and to choose what fits them and what what they need at a particular time. So yeah I think it's a very important part of the bill but again you know it shouldn't be imposed upon it should be something that's seen as useful within their businesses to actually do and I think that's going to be important how we rule this out. I think you know CPD is obviously going to be incredibly important as the vision for agriculture is delivered and may or must is a very important sort of comment in this in this section and there are questions to be asked in that exactly how it's applied and as Kirsty said we have to be clear on what the benefits are to the business for engaging with CPD and we know that will directly affect the uptake. A lot of these a lot of solutions that we need will require very similar activity but the reason for doing it for a business will will be different and we need to we need to acknowledge that but I think before we impose any kind of CPD requirement we need to ensure we actually have enough advisors and trainers and we simply don't for what was currently delivered. I think there needs to be a qualification as to what constitutes CPD so it's okay to have varying levels of CPD but a monitor farm meeting attendance is very different to my basis integrated pest management qualification or the livestock handling course held by a vet these are different things and they will need to be sort of slightly viewed differently they all achieve something very important and there's also an element of not not just choosing the cheapest option to tick the box and that's critical to ensure that this is remotely meaningful. We expect there needs to be some level of equivalence granted to the existing professional qualifications so your institute of agricultural valuers, agricultural management basis that there's a whole stream of them that can be listed and must be recognised in this if CPD is to be required. There also I think needs to be something within this section on the availability and accessibility of the information so we've heard it from RSAPI that approximately 25% of farmers are thought to be dyslexic we know that with a higher proportion of farmers being men they're more likely to be colourblind for instance and older populations most likely to have hearing issues how they access information will entirely depend on whether or not they use it and if it's not accessible it will not be used no matter how much you impose upon them and the same thing applies when we look at barriers to entry for women and new entrants and general equipment availability so things need to be delivered you know this is very important content it has to be delivered in a multitude of ways and that makes things expensive and that needs to be factored in when we're looking at the CPD requirements that yes we will need some on-farm meetings for particular regions if you're wanting to create catchment area change there will need to be in-person meetings but there will need to be an online offering as well and all these things add to the complexity there also needs to be a measure of quality for the person delivering the information particularly with Regen ag I think we are seeing a worrying increase of professionals giving anecdotal data that has no scientific rigour to it at all and they are very expensive and potentially deliver nothing of benefit but the minute you get caught out by it you're kind of put off doing anything else in the future so we we need to get this right knowledge exchange is key but there needs to be an engagement with the sector as to what's already out there what professional qualifications already exist that will interact with this and at the moment there is nothing in this section about consultation with the sector okay thank you divry thanks and Kirsty and Eleanor have covered that really well the thing I'd emphasise Eleanor was talking about we need more advisers you need more capacity and I completely agree with that but they also need this CPD the CPD they receive to reflect the urgency of this but also that the breadth and depth of it and I think that that's potentially a huge enabler just in terms of that that phase one to one when you're doing your IX return having an advisor who knows who can explain this can explain this discussion we've had this morning but actually what the bill is what the measures are that big list that's quite a big ask of them but I think that's the kind of thing they should be asked to do but it comes back to resource that needs to be resourced properly and that's not a small part and vicky made the point about how that kind of tier 4 budget doesn't match what is required in terms of that CPD and that support through advisers thank you I've got you and then Davey yeah a whole host of difficulties with the current advisory capacity have been raised I think we need to recognize that that is a real wealth of knowledge already out there you know to pardon the pun there are organic networks growing like the nature friendly farming network there's the I believe it's the southwest regenerative farming network and those skills that have already been fostered across farms and crops whether they're part of those networks or just in the mainstream system operating on their own need to really be utilised because there is a vast resource there we've seen and I would encourage the committee to look at kative work on these kind of farmer to farmer crofter to crofter clusters you know where they are geographically closely located obviously there are problems when it comes to the highlands and islands of just getting around the area but they have been really really important in helping to upskill farmers and crofters and introduce them to potentially new nature friendly farming techniques I'd also like to go back to Vicky's point on the funding I would echo everything that she said about the funding allocation being insufficient there is a particular ring fence around tier 4 funding and we see that as you know the budget allocation is subject to periodic uncertainties and there's also climate change shocks and things the knowledge transfer is going to be so so key to weatherproofing farms from both economic and climate shocks Jim you got a question on that point you and it's to all of you but just specifically on the point that you just made there you're talking about there is so much knowledge transfer out there absolutely in favour of that but it's called continuous professional development are you saying that these organisations that are doing that have to be professionally registered and if so with who if they aren't then the scrutiny of the government's ability to deliver its objectives will then come back to it well who did you ask to deliver it and where did the knowledge come from so I can potentially see that there'll be an issue there further down the line if we don't have some kind of process to make sure that what we're asking people to do is delivered by the right people on the basis of something that the government is then answerable to I wouldn't feel confident responding now so I will write to you following up on that point thank you I've now got a davie and then ross lily thank you and thank you for your question Beatrice just a number of things and with regard to it and kirstie name checked me earlier in today's at least mornings conversation when she was talking not just about cvd cpd but about why there education and training and I think it's important as we've also identified here that the bill has lots of linkages to other policies national environment bill etc etc etc it's important that we also recognise that the scale of change that we are looking to achieve in the land management in Scotland and only an element of that can actually be achieved in terms of skills development can be achieved through the cpd that's been talked about here within the agricultural framework bill and so a wider education and skills delivery within scotland needs to be a greater alignment with what we actually need going forward I potentially with the education skills teams that I have with the NSRUC I could potentially create a a 2d course or a week-long course tomorrow to fill a skills gap but if it comes to a sort of a year-long hnc or three or four year long degree that takes a lot longer slower burn to actually change because it's not just in my gift to actually do that it's within the gift of Scottish funding councils and skills development Scotland to actually also agree that we can support those type of things going forward so there is a need for us to actually think carefully about what are the skills that we need both on our farms and for individuals to actually help our farmers and crofters going forward and how we might actually seek to facilitate that across Scotland going forward. Upskilling and reskilling is going to be vital not just for farmers and existing farmers and crofters or those new entrants but others to actually help them on that way. With regard to cpd itself then certainly cpd in all its guise is important but it's not an outcome in itself it's not it shouldn't be you know you have to actually do a certain amount of cpd three hours of cpd per every six months to actually continue to qualify for your eligibility of payments or a thing but it's just a tick box exercise that achieves nothing cpd whatever it is needs to actually have a clear relationship a clear outcome to what the farmer or the crofter needs to actually achieve on their farm or croft how relevant it actually is to helping them actually do that. I've already mentioned the scale of the change that's actually needed others have mentioned there's a there's limited existing knowledge for many of these multiple outcomes we're now going to be looking for from farms and crofts not just amongst the farmers and crofters themselves but amongst those who are currently advising them so it's not just a low number of advisors that's currently available it's a low number a low proportion of those currently available advisors can also now give appropriate training or advice on the range of activities that we that we're seeing is important going forward and certainly with regard to Jim's point then we have to look at some level of sort of accreditation going forward if we want to actually achieve the the real degree of uplift in knowledge and understanding amongst farmers and crofters going forward and the final thing I just wanted to say is we also need to think outside the box a number of people have already mentioned it peer-to-peer learning advisors to farmer crofter learning can be important but we also have to think how else it's going to be more effective at actually more effective at achieving those sort of outcomes and as a number of people have already mentioned some level of sort of facilitation going forward for some groups groups of farmers maybe akin to producing a better outcome even if it's more expensive to achieve. KTF has already been mentioned but if we look to the Republic of Ireland we're doing nothing like the scale of KTF type projects that the Republic of Ireland have done from a bottom up sort of perspective putting facilitation in place and then just to bring it full circle you know CPD is not just about upscaling individuals in terms of the knowledge and understanding there's a big role to play there in terms of we mentioned data we mentioned technology having a big role to play going forward we need to ensure that that's on the table and we and our farmers and crofters get sufficient training to allow them to understand what's actually happening on their on their farms and crofts where they currently are to benchmark where they are and know what's best to actually do to actually move them forward. Thank you I've got Ross Lillian then Ross McLeod. I'll just thank you, Lady, but not repeating, that it's more important to focus on the diversity of knowledge and expertise that is across the industry and the advisory network and those of us within specialist organisations and facilitate that rather than focus particularly on CPD at the stage there is a standard organisation the Chartered Institute of Environmental Managings is a good baseline for a lot of the stuff we've been talking about to to clear on climate and biodiversity and as other chartered institutes particularly forestry that can come in here in terms of sitting up a standard but I think the point thing is tier four the way it's framed at the moment can be better framed as being a cross cutting tier rather than the fourth tier is actually the first tier before tier one, tier two, tier three and then cuts across those three and in procurement of publicly supported advice and guidance and so on out there let's diversify that and so it unlocks that expertise that sits amongst farmers and crofters and as much as the academic institutions out there rather than focuses on a one-end institution providing that advice. Thank you. Ross McLeod followed by Alasdor Seaman. Thank you convener. Well I don't think I come close to Davey's description of CPD and what's required there I think the only thing I would add is looking at the nature advice given to farmers at the moment it will need to balance the focus on productive efficient farming with biodiversity and I'm not sure that the skill sets of those advisors at the moment are sufficient for that purpose and that's really really important because as farmers try to grapple with where they could make some sacrifices in order to to maintain a biodiversity outcome that's going to be critical Ellen I think points to this as well so just that important making sure we balance those two competing requirements productivity and biodiversity is essential for those advisors to have those skill sets. Alasdor and then David Harley. Three things yes to farm advisory service really crucial and recognising that we need to support them so I'd like to see a plan to upskill them. Agree with Davey's point having graduated from SRUC about a million years ago the sad reality is that there's now less input into my specialist area of integrated trees on farms today than there was 30 years ago and so we've got to see that change I think there are a number of us in this room who'd be really keen to be a productive part of supporting that journey we've got real skills and expertise to bring to that and we'd like to find a way to do that. I think peer-to-peer learning is absolutely crucial here because we need to recognise this isn't just about skill and knowledge it's really about a lot of this is about culture and a lot of this is about fear and safety and therefore making sure that we're putting farmers who are already doing this right in front of that is really crucial we're running really effective crofter network gatherings and we don't do the teaching we get crofters to do that so I think that's got to be really important and then lastly I think you asked the question Jim around the sort of official certification versus informal route I'd really encourage you to go and look at what teachers are doing I worked in education for quite a while and they've got a really nice balance of a mixed economy where there's really high quality academic certified stuff but also a really rich range of other things that people can just pick up and do at their own pace and in their own way including that peer-to-peer learning which I think is really fundamental so some good lessons we can potentially learn from teaching provision thank you David and then vicki thanks yeah just building on the last four or five contributions completely agree that cpd has a role but not at the expense of that dedicated farm farm level advice our experience in regulating the sector is that that advice been given by people who understand farming far and farmers is absolutely crucial and I think that culture point that allister raised is really at the heart of this I think it's not so much about it's not so much about much about education or information provision it's really around that culture and that's that's a very sophisticated and something we need to really invest in be happy for a conversation around that thank you vicki thanks I mean clearly this is a we can talk a lot about this is a clean important issue and how you go about delivering this is really matters and there's a whole diversity of approaches and very sort of farmer centered approaches but I just wanted to add something which is about the need for this and the sort of evidence base around that so in a paper the Scottish government submitted to the just transition commission and the figures are a little bit a while ago but the vast majority of farmers farm based on practical agricultural experience and of course that's important so about 72 percent but only 28 percent had any formal agricultural training and just over 1 percent of those managing farms in Scotland this was in 2016 said they had undergone any kind of vocational training in the last 12 months if we compare that with countries like Germany and the Netherlands where 70 percent of farmers have had formal training 60 in France and it just highlights how much there is to do and we're increasingly asking farmers to do more diverse and more complex things and I think we're doing them a disservice if we don't put in place the mechanisms the investment that the ways of helping them through that process and upscaling on whether that's through mandatory or whether that's voluntary or all of those kind of mix of approaches but the need for it is absolutely essential I think. Thank you, Jim. That's more a question for the cabinet sectors to be honest. Okay, that's just arrived at the end of our session very much on time so I very much appreciate. I wonder how many multi-zards I get for becoming 15 seconds of our deadline but thank you all very much for your valid contributions and that will help us for my views when we move towards stage 1 report. I'm now going to suspend the meeting for 10 minutes to allow witnesses to leave and give members a short comfort break. Our third item of business is consideration of two UKSI consent notifications the movement of goods Northern Ireland to Great Britain, animal feed and food, plant and health etc regulations 2024 and the amendment to the definition of qualifying Northern Ireland goods EU exit regulation 2020. Do any members have any comments on either of these notifications? Nope. Are members content to agree with the Scottish Government's decision to consent to the provision set out in the notifications being included in the UK rather than Scottish subordinate legislation? That concludes our business in public. I move into private session.