What's up everyone it's your girl Kinsey here from Layton Sports Cards and I'm ripping 2022 Panini Prison Football. I'll have you 12 box full case break number nine random divisions. Again here's a look at the random results. You can always find these at LaytonSportsCards.com under the results tab. Link's also right in chat for you. Look at this here for a second so everyone can see their divisions. All right here we go. Good luck. Good luck. Come on colorblast or manga. I'll take either one. I kind of want a color blast though. I pulled a couple mangas already. Good luck everybody. All right good luck. Good luck. We've got Silver Drake London on the flashback. Another nice London coming out today NFC South. We've got Jalen Tolbert Red Wave to 149 NFC East. Willis Ruckey and Jeremy Ruckert. Gold vinyl already. We've got Emergent Malik Willis AFC South. Pull from the back here Kyle Hamilton. We've got A James Cook Redskins. So it's going to be a throwback here for Washington NFC East. We've got a Sean Taylor. Wow that's sick. Three out of five. Who's got them? NFC East. That's going to Jeffrey S. That's nasty. We'll mag that one for you Jeffrey. Six at heart. Silver Jared Goff. First auto up is to 149 Red Wave Color Match John Mechie III AFC South. Kobe Dean and Kyle Phillips. Silver Mike Evans. Next auto we've got a Marcus Allen for the Raiders. Marcus Allen on the Silver AFC West. Demian Harris on the Hyper to 175 for the Patriots. AFC East Dulich and Ekbeke. Justin Jefferson was just upside down. Brilliance Jamar Chase AFC North. Purple Power is going to be a Bobby Wagner for the Rams. Four out of 49 NFC West. Got Sauce Rookie. Nick Bonito. Blackboards Cards here. Gannon and Jay Z Jones. Purple Ice to 225. Boye Mafe. Seahawks NFC West. Washington and Christian Watson NFC North. Got Silver Brilliance of Jonathan Taylor AFC South. Blue Ice to 99. Geno Smith Seahawks NFC West. Jordan Davis. Tyquan Thorin. Prison Break Rookie. Kenny Pickett AFC North. They've got Orange Quitty Pay for the Colts out of 249. AFC South. Gordon and Rashawn White. And a Navy Camo back there. Silver Rookie. Carson Strong NFC East. Blue Camo is going to be a Christian Kirk. That one is six out of 25. AFC South. Kenny Pickett Rookie AFC North and Walker NFC West. Sub Jeff. Congrats on that Taylor. That's sick. Oh I think I see Gold. Javonte Williams. Set that down. Wanda Robinson. Trent McDuffie. Gold. Cowboys who's got them. NFC East. Again, Jeffrey. Gonna be a Michael Parsons on the second year. Nice true gold. That one is nine out of 10. Grats on that one. Magda. Oh it's coming out. Fireworks. Russell Wilson. We've got Logan Hall on the blue way for the Bucks to 199. NFC South. Pickett Rookie and Mafe. Last Pack Bucks one. Silver and Mark Jones Drew. Got Green Scope to 75. Chris Jones. Chiefs AFC West. Alger Rookie and Ritter Rookie. Wow. Great first boxer. Logs two. Is it really? Who's Otto? Silver Munoz. Our first Otto up is gonna be a Silver Rookie Otto of Tariq Woolen. Jackson. Seahawks. Tariq Woolen. NFC West. Sine and Romeo Dobbs Rookie. Brilliant Silver. Dolvin Cook Vikings. NFC North. We've got Orange Ken Anderson for the Bengals to 249. AFC North. Anderson Pacheco. Emergent Rookie. Alec Pierce. Blue Ice to 99. Tariq Woolen. NFC West. Jackson. Skylar Thompson Rookie. Silver J. Jeff. J. Genesis. We've got Purple Ice. Aaron Jones to 225. NFC North. Johan Dotson and Stanley. Silver Dallas Goddard. Otto. We've got a Jerry Judy for the Barracos. What is Judy there? Denver. AFC West. Blonte Taylor. Malcolm Rodriguez. Hype. Trey Lance. We've got Orange. Harold Landry to 249. Titans. AFC South. London and Iquanwood. Orange. Wave to 60. Josh Jacobs. One out of 60 there for the Raiders. AFC West. Isaiah Spiller. Logan Hall. Hype. Silver. Justin Fields. NFC North. Purple. Jared Goff for the Lions. 81 of 125. NFC North. Starting heat up here. Calvin Austin III. Jack Jones. Got Brilliance to a Tiger Viola. Red Wave of Kavon. Tibido. There you go. Giants. 14 of 149. NFC East. Brock Purdy. Rookie Base. Jameson Williams. Silver. Xamir White for the Raiders. AFC West. Red Wave. Brian Burns. Panthers. 34 out of 149. NFC South. David Bell and Bristor. Chris Jones. Chiefs. We've got Blue Wave. Reggie Wayne for the Colts. 55 out of 199. AFC South. Leland and Carson Strong. Rookie Base. Last pack. Box two. Drake London on the prison break. Purple Ice. Christian McCaffrey. There you go. Niners. 72 out of 225. NFC West. A lot. Box three. Got Silver all out. Deontay Johnson. AFC North. Hyper to 175. Nick Bonito 29. 29 of 175. AFC West. Watson Rookie. Jordan Davis. Brilliant. Jonathan Taylor. Got Blue Wave. Geno Smith for the Seahawks. NFC West. Thornton and Goodwin. Goodwin. Gordon. Silver. Marcus Marriota. We've got Jalen Naylor. NFC North for the Vikings. On the Redway. 57 of 149. Rashad White. Chris Olave. Hype. Silver. Jamar Chase. AFC North. We've got Blue Wave of Chris Godwin for the Bucks. NFC South to 199. Strong Jr. in McCreary. A couple today. Not too too many, Timmy. Not too many. Emergent. Kenneth Walker. The third. NFC West. We've got Cracked Ice. Daniel Jones on the Purple. 128 of 225. NFC East. Trayvon Walker. Andre Jackson. Got Silver Rookie. Zimir White. AFC West. Justin Simmons for the Broncos. 9 of 249. AFC West. Skylar Thompson. Anna Latte. Taylor. Got Silver. Jeffrey Simmons. Next auto up to 125. A Mike Singletary on the Sensational Signatures. NFC North. We've got Awu Ware. AFC North. Or NFC North. Sorry 149. Traylon Berksbrookie. And Kavon Tibido. Fireworks CD. Marcus Marriota on the Hyper to 175. 37 to 175. NFC South. McBride and Ebner. Nice Brock. Purdy on the Purple. I 65 of 225. NFC West. That is Chris G. Congrats on that one, Chris. We'll mag this for you. Nice Purdy. Garrett Wilson and Evan Neal. Silver Emergent of Kenneth Walker. The third NFC West to 225. Purple Ice. Jordan Poyer. 99 of 225. NFC East. Cross and Hassan Haskins. New recruits rookie of Breece Hall. AFC East. Blue Wave. Romeo Dobbs. Nice one there. NFC North. NFC North. Heating up here. Neil P. to 199. Fitry and Hutch. Rookie. Last back. Boss three. Got Silver. Rashawn Slater. Orange. Rashawn Bateman. AFC North. 249. Brian Cook and Khalil Shakir. And y'all more group rates tonight with Sam starting at five. And then personals to follow after that. Crawley the color. The color blasts. Kawame for sure. Silver Matt Ryan. We've got Orange to 249. Emmett Smith. Cowboys. NFC East. Jelani Woods. Skymore. Silver. Scary Terry. We've got Eagles. Fletcher Cox Otto. NFC East. Ilam. David Ajavo. Brilliant. Jamar Chase. Got Blue Ice to 99. Andre Johnson. Texans AFC South. Jerome Ford. Matt Corral. Rookie. Purple. Trayvon Walker for the Jags. It's 26 out of 125. You got AFC South. Auton and Davis Price. Silver. New recruits. Garrett Wilson. Jets AFC East. We've got Julian Love for the Giants. 55-125. NFC East. Fonsey Wyatt. Kate York. Rookie. Prison Break. Kenny Pickett. Rookie. Got Hyper of Jeffrey Simmons for the Titans. AFC South. Naylor and Matchy the third. Silver Rookie. Kate Auton for the Bucks. NFC South. Red Wave of Miko Harman Jr. 133 of 149 on the color match AFC West. Williams. Kenneth Walker the third. NFC West. Silver Justin Herbert Flashback.  I love these flashbacks. AFC West. Nice one there for you Kevin. Isaiah Likely Orange to 249. AFC North. Johnson the second. Vilas Jones Jr. Mergent Rookie of Malik Willis. AFC South. Blue Wave. Dak Prescott. NFC East. Five of 199. One off that Jersey number. Fashel and Durant. Got Silver. Trey Hendrickson. Auto. We've got Washington. Sam Howell Rookie Otto. There you go Commanders. Nice one there. NFC East. Bailey Zappy and Isaiah Likely. Prison Break. Silver Kenny Pickett. AFC North. Zach Wilson on the Purple Ice to 225. AFC East. Robinson Jr. Carol Atlas. Last pack. Box four. Fireworks Russ. We've got Rookie. Green Scope. Wando Robinson. NFC East. 70 of 75. Danny Gray and A of Reese Hall Rookie. Box five. We've got Mojo. Got a Mojo. Mojo Jojo. Oh come on. AFC North. Joe Scheiste. 13 of 20. Joe Burr. Heck yeah. That is sick. Very nice hit there. We'll mag that one. Nick Bonito Purple Ice. 153 of 255. AFC West. Robinson McDuffie. Nice cards coming out of this case. Sure. Those Mojos are definitely hard pulls. Silver on Oh. Wearing. Kittle on the Orange. 186 of 249. NFC West. Pickens Rookie. Moffay. Silver Drew Brees. We've got 235. Reggie Wayne on the Purple Power Sensational Signatures. That's nasty. NFC South. Neil P. That one's cool. 20 of 35. Algiers and Ritter Rookies. We've got Forest Camo now. Emergent Alec Pierce. Forest Camo. Commanders. NFC East. Show me Rookie. Not a rookie that Chase Young. Chase Young for the Commanders on the Forest Camo. One out of 15. Still a nice one there. Dulich and Egbeckity. Blue Ice to 99. Chris Jones. AFC West. Sauce Rookie. Bonito. Silver Rookie. Emergent of Damian Pierce. AFC South. To 175. Cam Jordan for the Saints. NFC South. Washington and Christian Watson Rookie. Hype. Tray Lantz. Orange. Hassan Haskins. There you go Titans. AFC South. 101 of 249. Jordan Davis Thornton. Silver Nick Bonito. Broncos. AFC West. Russell Wilson on the Blue Wave. AFC West. 52 of 199. Corden Rashad White. We've got Miles Garrett on the Lockdown. Orange. H. A. Brown Eagles. NFC East to 249. Kenny Pickett Rookie. Chris Olavi Rookie. Cans 2. We've got Orange Wave Nelson Aguilar. That is 19 out of 60. AFC East. Cross and Hassan Haskins. River DJ Moore. Next Auto Up. Going to the Panthers. Silver Rookie Auto. Matt Corral. Matt Corral. NFC South. Allen K. Vitry and Hutch. Last Pack Box 5. We've got Hype Rashad Bateman. Silver. Bernie Kosar. That is 21 to 125. AFC North. Cook and Shakir. Halfway Mark here. Just about. Rookie Emergent. Kenneth Walker III. NFC West. Purple Issa 225. Brian Cook. AFC West. McDuffie and Pickens Rookie. Silver Brandon Cooks. We have George Kittle on the Blue Wave to 199. AFC West. Moffay and Algier. Silver Shack Barrett. Our Auto is going to be a Gus Ferrati. Sensational Signatures. NFC East. Blue Ice. Ritter Rookie. Glitch. Hype Jamarches. Purple Ice. 225 of Aaron Donnell. NFC West. Egg Baguette and Sauce Rookie. Orange Quinnan Williams. That one is 26 of 249. AFC East. Benito, Washington. Silver Rookie Emergent of Traylon Burks. AFC South. Red Wave. Damien Harris. AFC East. Watson and Jordan Davis. Williams of Najee Harris. Orange, Ty Chandler. NFC North to 249. Like on Thornton. Tyler Gordon. Silver, Kate Aughton for the Bucks. NFC South. Tyler Conklin for the Jets. 31 of 175. AFC East. Sean White. Kenny Pickett. Rookie Base. Got Rookie. Flashback. Chris Olave. Nice word. The London and now the Olave. There you go. NFC South getting both of those actually. DK Metcalf on the Blue Wave. Seven of 199. NFC West. Olave and Cross. Rookie. Prison Break. Olave. Purple Ice of Shaq Leonard for the Colts. 225. St. Haskins and Pitree. Silver, Rondell Moore. Next Auto Up. We've got a Jameson Williams. There you go. NFC North. Nice one there. Allen V. AFC North. Hutch Rookie. Brian Cook. Last pack there. Silver Hype. Zach Wilson. Orange Tom Brady. That's 16 of 249. NFC South. Nice one there for you, Allen. Shakir and Traylon Burks. Alrighty. Halfway through now. Let's do this. Halfway through. Take a quick sip of water actually. Second half. Very solid first half. We haven't seen an RPA or a snakeskin case hit yet so let's see when we get out of this second half. Did get a gold and a gold vinyl. Drake London to 225. Purple Ice. There you go. NFC South starting to heat up here. Nick Bonito. Washington. Wave to 199. Captain Kirk. NFC North. Olave. Cross. Silver. Fireworks. Debo. Purple Ice to 225. James Cardinal. James Cardinal. James Connor for the Cardinals. NFC West. Haskins. Pitchery. Fireworks. Drake London Rookie. Hyper to 175. JK Dobbins. AFC North. Evner and Garrett Wilson Rookie. Silver. Budabaker. Auto for the Colts. It's going to be an Alec Pierce. Silver Rookie Auto. Alec Pierce. AFC South. Neil and Strong Jr. Rookie Silver of Grease Hall. AFC East. Goddannel Driver. NFC North 199. McCreary and Walker. Brilliance Echler. Hyper to 175. Devon Duvernay. AFC North. White and Kenny Pickett. Silver John Lynch. Next Auto Up. There's going to be a Fatrian. Mathis. Washington. NFC East. Commanders. Thornton and Gordon. Silver. Zay Jones. We have Purple. Wes Welker. That is going to be 60 out of 125. AFC East. Watson Rookie. Jordan Davis. New recruits. Bailey Zappi. First set. One of the first Zappis we've seen today for the AFC East. Snoop Connor. 223 of 249. AFC South. Hutch and Brian Cook. Silver. Jake Ferguson. NFC North. Or NFC East. Sorry. Jamison Winston. Jamison Winston to 249. For the Saints. NFC South. Shakir and Shreylen Burks. Last pack here. Lockdown. Miles Garrett. Red Wave of Brian Burns. That's going to be 27 out of 149. NFC South. Tibodeau and McBride. Here we go. Good look. Silver. Chase Claypool. We've got 600 points to ran them off. Let's do that at the end. Blue Wave. Duke McAllister to 199. For the Saints. NFC South. Olin and Carson Strong. Rookie. Rookie. Prison Break. Chris Alave. Purple. Ice of Alex Heismith. For the Steelers. 225. AFC North. Ferguson. Zemir White. Blue. Ice to 99. Of Iguanu. Panthers on the color match. Nine of 99. NFC South. Sine and Dobs. Maple. Prison Break. Silver of Chris Alave. Orange. Going to the Saints as well. Duke McAllister to 249. NFC South. Troy Anderson and Pacheco. Purple Power. Firework. Chris Alave. 49 is going to be a Andre Johnson. 38 out of 49. AFC South. Devin Lloyd. Tolbert. Blue is signed on the Silver Rookie. NFC North. Green Scope. It's going to be Max Crosby. That is 18 out of 75. AFC West. Mathis and Ty Chandler. Silver all out. Austin Eckler. We've got a Devonte Wyatt Orange. NFC North to 249. Rodriguez Stingley Jr. Hype Jamar Chase. Orange Wave of Ronnie Lotz. That one is 26 out of 60. NFC West. London and Iguanu. Silver Vaughn Miller. A Jalen Tolbert to 49 on the Purple Power. Rookie Otto. NFC East. Tolbert. Spiller and Logan Hall. Silver Brilliance. Najiharis. AFC North. We've got Geno Smith. That is 87 out of 125. NFC West. Calvin Austin. Jalen Branson. Najih. We've got Purple Scope. Ty Chandler. NFC North. Brock Purdy. Ricky Bates. Jamison Williams. Rookie. William Silver. Brett Fabry. Red Wave. Dalvin Cook. NFC North. David Bell. And Briskern. NFC North. Sorry. So many North, South, East, West. What's going on in my head right now? All right. Some box 8, 9, 10, 11, 9. 10, 10, 11, 12. Box. Box 9. It's illusion after a while. Big case breaks. All right. Here we go. Ken, y'all do appreciate you so much getting all these breaks built up for the daytime. More with Sam tonight. Starting at 5. Silver Fireworks. Seedy Lamb. Adam Thielen on the Blue Ice to 99. NFC North. Dulich and Egg Baguetti. Givante Williams. Purple of Quitty Pay. That's going to be 119 out of 125. AFC South. Drake Jackson and Sauce Rookie. Silver Rookie. Jake Ferguson. NFC East. Rich Gannon. Hyper. 92 of 175. AFC West. Bonito, Washington. Silver Joe Namath. We have a Michael Vick to 75 on the Flashback Autos. That's sick. Nice sit there. NFC South. That one is Alan Kay. Nice hit, Alan. That's cool. I like that. I haven't seen too many of those horizontal autos. Rich Gannon. 162. 25. AFC West. Wondell Robinson. McDuffie. Emergent Skymore. We've got Marlon Humphrey. Orange to 249. AFC North. Pickens. Mafé. Purple of Akim Iwanu. That is 40 of 125. NFC South. Algier and Ritter. John Dodson. Fireworks. Purple, I'm sorry. Greenscope of John Lynch. 29 to 75. NFC South. Here in Trelin, Berks. Yeah, Sam Serpent tonight. Silver Jalen Johnson. We have a Cade York to 149 on the Redway Ricciotto. AFC North. Rodriguez. Conner. New recruits. Silver Breeze Hall. AFC East. Richie Grant. 72 of 149. NFC South. Well equal as rookie Jeremy Ruckert. We've got Purple Power and a Navy Camo. Good luck. Rookie. Emergent. AFC East. Breeze Hall. Nice one there. That one is 26 of 49. Then we've got a Cade Auton. That is 13 to 25. Rookie for the Bucks. NFC South. Nice back there. James Cook. Kyle Hamilton. Silver Dante. Culpepper. We've got Michael Carter. 105 of 199. AFC East. Kobe Dean. Kyle Phillips. Flashback. Silver. Derek Henry. AFC South. Bailey Zappie on the Orange. Nice one there. AFC East. 176 of 249 on the Zap Attack. And Kenny Pickett. Solid box. All right. Box 10. Still no RPA or Snakeskin yet. New recruits. Breeze Hall. Red Wave on the Color Match. Nick Bosa. NFC West to 149. Johnson Jones. Here's our RPA. It's coming. Silver. Josh Allen. Paschale and Durant. Out of 49. It's going to be a Purple Power RPA. A Christian Watson. Wow. There you go. NFC North. NFC North. That is Neil P. Gratz on that. We'll mag that one for you. Very nice. 32 of 49. Back there. Fireworks Drake. London. NFC South. Miles Garrett. Blue Wave to 199. AFC North. Zappie Rookie. Isaiah Likley. Brilliant. Jonathan Taylor. Orange Wave. Rookie to 60. Jordan Davis. NFC East. 35 to 60. Bellinger and Pierce. Silver and Malik Willis. There you go. Titans. AFC South. We've got another Camo. Navy Camo for the Eagles. NFC East. It's going to be a Devonte Smith. Nice second year one there. 425. NFC East with some nice cards. Jeffrey S. Hill and Azucanma. What a nice color coming out of that. Out of that division. Miles Garrett. We've got a green scope of Jarvis Landry. NFC South. Flams and Walker the Third. Got blue ice to 99 of Raheem Mostert. AFC East. Tolbert and Mathis. New recruits. Silver. Bailey Zappie. AFC East. Orange. Kareem Hunt to 249. AFC North. Ty Chandler. Sam Howell Rookie Base. Emergent Rookie Sky Moore. Purple Ice. Tyler Algier. There you go. NFC South. 202 to 225. Sam Williams. Rookie to 249. NFC East. Zimmer White. Silver. Tony Boselli. We've got NFC North Jalen Johnson to 175. Signed Romeo Dobbs. Silver. Rashon Latimore. Our auto is going to be Eli Manning. That is two 15 on the sensational signatures. NFC East again. We've got a gold vinyl after this too. We got two gold vinyls this case. Nice. Going to the AFC South. We've got a Kevin Byrd. Kevin Byrd for the Titans. That one is 205. Three minus one is two Jersey number. eBay one of one. Anderson and Jameson Williams. Rookie. Last pack box 10. Shaq Barrett for the Bucks. That one is 16 of 49. NFC South. Pacheco and Devon Lloyd. 11. Still looking for the snakeskin. Again, it's not a guaranteed case hit, but it is usually per case. Brilliant Stramar Chase. We've got Eli Mitchell Hyper to 175. NFC West. Pierce and Booth Jr. Silver Damian Pierce Rookie. Blue Wave of Amari Cooper. AFC North. Snoop and Malik Willis. Silver Leonard Fournette. We've got J.K. Dobbins. AFC North. Silver Otto. Matt Corral Rookie. Kate Otten Rookie. Brooks Russell Wilson. Marshall Faulk on the purple for the Rams. 48 out of 125. NFC West. Davis Price. Devonte Wyatt. Got our snakeskin. Got Orange Kyle Hamilton Rookie to 249. AFC North. Kate York and Jalen Naylor. Come on, Big Rookie. Big Rookie's are definitely hard pulls here. Oh, Bangles. AFC North. Got Anthony Muñoz. Anthony Muñoz. Bangles on the snakeskin. Silver New Recruits of Jahan Dotson NFC East. Red Wave. Brian Burns. 125 out of 149. NFC South. Mechi and Kway Walker. Emergent Rookie Malik Willis. Purple Ice to 225. Jalen Tolbert. NFC East. Elam Sky Four. Silver Rashaun Gary. We've got Quinn and Williams for the Jets to 249. AFC East. Ajaubo and Jerome Ford. Silver Lockdown. Bired Purple Power. Calvin Austin the third. There you go, Steelers. AFC North. That one is two out of 49. And Cook. Interested in that one, Allen. If you're looking to move that, Austin. Got Prison Break. Kenny Pickett. Purple Ice. Tony Boselli. That one is 221 out of 225. AFC South. Hamilton and Nacobi Dean. Silver Rondale Moore. We've got it. Aiden Hutchinson. Silver Rookie Otto. NFC North. Nice Hutch. Phillips and Wanda Robinson. Silver Fireworks. Devo. Orange Joe Burrow. AFC North. 226 of 249. McDuffy and Pickens Rookie Base. All right, last box, y'all. Last box. Good luck. I'm going to do a recap. I do have 600 points to random off. First, New recruits. Bailey Zappy. AFC East. Ryan Tannenhill on the Hyper to 175. AFC South. Moffay. Algier Rookie. Silver Trey McBride Rookie. NFC West. Cooper Cup on the Blue Wave to 199. Also NFC West. Ritter and Doolitch. Silver John Lynch. Our Autos. Going to the AFC North. A. Kareem Huntz. Kareem Huntz. Rucker and James Cook. Austin Eckler. We've got a Forest Camo for the Browns. Another AFC North heating up here at the end. A. Leroy Kelly. No one is 14 out of 15. AFC North. Hamilton and Nicoby Dean. What do we have here? So we have another case hit. Instant Impact Drake London. NFC South. Nice. That is Alan Kay. First one of these that I've seen. Nice short print hit. We'll bag that. Egg Baguette on the Red Wave to 149. NFC South. Phillips and Wandaille Robinson. Silver Brilliant. Jonathan Taylor. Blue Ice. Jamal Adams for the Seahawks. NFC West to 99. McDuffie and George Pickens. Ricky Bates. We've got another Mojo here. Blue Ice. NFC West. Charles Cross to 99. Alec Pierce. Booth Jr. Mojo. Cowboys. NFC East. Rookie is going to be at Jalen Tolbert. Nice. Honda Mojo. That one is 14 of 25. NFC East. Jeffrey Killin' It. Nice hit there. Silver Devonte Adams. Orange Eli Mitchell. That is 242 out of 249. NFC West. Snoop Connor. Malik Willis. Rookie. Silver Joey Boso Lockdown. Blue Wave of Ebner for the Bears. 134199. NFC North. Ike Baguette and Sauce. Fireworks London. Got Emmett Smith. Orange to 249. NFC East. Bonito in Washington. Jalen Johnson. Last one. How about A. Garrett Wilson for the Jets. On the Silver Rookie Auto. Here you go. AFC East. Watson and Davis. Last pack. New recruits. Breeze Hall. Orange Wave. Bill's going to be a Jim Kelly. That's a nice one. 38 of 60. Bill's Mafia there. NFC East. Thornton and Kyler Gordon. All right. One second. Again, I do have 600 points to random off here. See you everybody. 600 points. We've got all eight divisions here. I'm going to roll the dice. Whatever division is on top, we'll take home these 600 points. Snake Eyes is a re-roll. Eight times. Here we go. One, two, three, four, five, six, seven, eights. AFC South. AFC South taking home the points. All right. Let's do a recap here. Short prints and lower numbered stuff. We have the Munoz on the Snake Skin for the AFC North. Kevin Byard on the Gold Vinyl. AFC South. Garrett Wilson, Silver Auto. AFC East. Kareem Hunt. AFC North. Aiden Hutchinson. NFC North. We had JK Dobbins. AFC North. Sensational Signatures. Eli Manning. This is to 15. NFC East. Kade York. AFC North. The Michael Vick Flashback Auto. That says 75 on the green scope for the Falcons. NFC South. Jalen Tolbert. NFC East. Fadrian Mathis. NFC East. Alec Pierce for the AFC South. Jameson Williams. NFC North. Sensational Signatures of Gus Forretti. NFC East. Matt Corral. Panthers. NFC South. Reggie Wayne on the Sensational Signatures out of 35. AFC South. Sam Howe. NFC East. Fletcher Cox. NFC East. Sensational Signatures of Mike Singletary. NFC North. Jalen Naylor. NFC North. Jerry Judy. AFC West. Tariq Woolen of NFC West. Marcus Allen. AFC West. John Mechie III for the AFC South. Ann R. Magdcards. We had the SSP Instant Impact of Drake London. Nice one there. NFC South. We had the Purple Ice Brock Purdy. That one was 65 out of 225 for the NFC West. The Joe Burrow Flashback Mojo to 25. AFC North. That was 13 of 25. We had the Gold Micah Parsons. Second year NFC East. Nine of 10. A Sean Taylor Gold Vinyl.  NFC East. Three of five. And then we had the Christian Watson Purple Power RPA. NFC North. 32 of 49. Alrighty, that'll do it for the break. Thanks again, everyone. We got F1 coming right up.


Hello, I'm Angela Monroe, and I am one of the bariatric coordinators with the Michigan Health Surgical Weight Management Program. While weight loss surgery may not be for everyone, it can provide hope to individuals who have been unsuccessful in the past with traditional weight loss methods. To qualify for bariatric surgery, individuals must meet strict physical and psychological criteria before becoming a candidate. Learn more from one of our bariatric surgeons. So who is it that qualifies for weight loss surgery? Well, that's typically here on the end the class 2 and class 3 are morbidly obese patients. Those patients are going to stand to benefit the most based on the risks of surgery. However, the bariatric surgery benefits are profound. Over 96% of the health problems related to obesity are completely resolved and reversed usually within days to months after surgery. Again, there's huge physical and emotional benefits. Looking at some of these disease processes that we help improve. Depression, there's actually 47% reduction that. There can be a 46% improvement in migraine headaches. 25 to 66% control diabetes. 42 to 66% resolution of high blood pressure. There's a disease that a liver that is tied to obesity called non-alcoholic fatty liver disease, and there's a 37% resolution of that. Arthritis and joint pain, 41% resolution. Stress incontinence, 50% resolution. There's a 39% improvement in asthma. Sleep apnea, 45 to 76% resolution. So again, significant improvements that we can make for patients with various comorbidities related to obesity. In addition to physical and psychological requirements, some insurance companies have specific weight loss requirements prior to surgery. Our insurance video will provide a brief overview of the basic criteria you must meet to qualify for surgery.


Bonjour tout le monde, bienvenue à l'infrastructure week-end de GeneKins. Nous sommes le 3 octobre 2023. Aujourd'hui, à la table, nous avons moi-même Taman du Portal, Marc White, Stephen Merle, Bruno Verrarten et Kevin Martin. Nous ne pourrions probablement pas pouvoir attendre, il a un point médical. Ok, on commence avec l'annoncement et des éléments plus grands. Donc, le week-end de 2.426 est out, à moins le monde, les packages et l'image du docteur. Je ne suis pas absolument sûr pour l'image du docteur, parce qu'il y a un problème avec les machines virtuelles sur Azure, depuis plus tard aujourd'hui. C'est un deuxième élément que je vais attendre immédiatement. Je ne suis pas sûr d'y comprendre, donc vous ne serez pas sûrs si les containers sont construits. Oui, je crois que l'image Linux pourrait déjà être touchée au docteur, mais les images des windows n'est pas encore là. J'y crois, je l'ai même vérifié. Je vais vérifier mon autre écran. Je peux vérifier, parce que j'ai un processus. C'est encore construit. Les agents de contrôleurs et des agents de CCH sont attendus depuis minutes et heures. Donc, l'image du docteur, Linux, ok, les windows sont attendus. Je le vois. J'assume que le autre item de change log sera fait plus tard. Un change log est déjà fait. Il mérite et l'a publié. Merci à Kevin. Il a fait un excellent travail. Et ensuite, j'ai fait quelques extraits après. Le change log mérite. Je crois que ça devrait être visible maintenant, parce que ça mérite 10 ou 15 minutes plus tard. C'est un bon travail, les gens. Oui, c'est un bon travail. Il y a deux grands changements. Vous l'avez écrit, donc j'assume que c'est pour les infrastructures. Oui, l'une est la removal de prototype JS. Le library JS que nous avons commencé à la removal en mai 2023, est maintenant en train de se retirer de la week-end. Nous avons été parmi les plugins de plusieurs 100, pour faire sure que ce soit retiré de eux. Et une spéciale grâce à Basel Crow et Tim Jacomb pour un excellent travail pour se retirer tout au long de l'end. Il n'y aura pas de week-end, il ne sera pas visible sur ci.jankins.io jusqu'à novembre 15, avec la prochaine phase. C'est pour l'infrastructure, nous devons être careful de l'infrastructure.ci, qui va utiliser weekly. Et nous allons avoir weekly.ci.jankinsio updated. Donc, c'est nécessaire de checker, les cas de minimum de utilisation sur cet instance public. Et qu'est-ce que la deuxième major change? C'est aussi... Container images qui ne spécifient pas le JDK sont maintenant utilisées en Java 17. Donc, si vous utilisez la plus tardée, je sais que les amis ne veulent pas que les amis utilisent la plus tardée. Mais si vous utilisez la plus tardée, vous allez avoir Java 17 maintenant, plutôt que Java 11. Parfois, si vous utilisez Alpine, ce qui est une plus tardée, c'est la plus tardée, vous allez avoir Java 17. Si vous utilisez Slim, vous allez avoir un container Java 17 maintenant, si je vous le rappelle correctement. Donc, si vous vous demandez pour un container et pas spécifier le JDK dans le label, vous allez avoir Java 17. Ok. L'important, c'est que ce change sera reposé à la prochaine release LTS. Quelle sorte de LTS c'est, parce que ce change n'est qu'une reposition d'image doc. C'est-à-dire pour tout le monde? Je pense que c'est excellent. C'est-à-dire que Kevin doit être sûr que quand il crée le change log pour la prochaine release LTS, et la prochaine release LTS devrait être disponible demain. Je crois que c'est la date pour ça. Il va avoir des prévues de la prochaine release, et on doit être sûr que c'est inclus. Mais il est déjà dans la semaine, donc il doit se remercier pour pouvoir sortir du week-end et couper le change log. Cool. Thanks for the details. Congrats for that work. Is there something else on that new weekly? Those were the two big ones then, yeah. There certainly are others, Pour l'infrastructure, nous n'avons pas été impactés par ce changement parce que nous avons déjà stické à GDK17, donc, oui. Mais ça veut dire que nous allons bientôt pouvoir commencer le GDK21 stické. Donc, un second annoncement. Ça ressemble à ce que nous avons cette semaine sur les issues Azure VM. D'hier, le VPN a été downé. Le premier site, c'est qu'il y avait un upgrade automatique grube qui a failé. Un failage grube. Donc, le système a dû rouler le bootloader. Et quand nous venons de la machine de marche, nous devons finir l'upgrade par nous-mêmes. Mais ça indique un issue d'underlay. Ce n'est pas un issue sur le système Azure. Mais ce n'est rien sur le statut de Jenkins. Donc, on a pensé que peut-être que c'est seulement notre VM. Mais depuis cette nuit, depuis dix heures, plus ou moins, l'allocation des machines virtuelles est parfois sur notre subscription. Mais seulement le Windows 2019. Donc, Windows 2019, l'allocation de VM est flacquée. Ok, je suis désolé d'interrompre. Mais par exemple, j'ai eu un bâtiment qui a été installé depuis 21 heures parce qu'il n'y a pas de machines virtuelles. Est-ce qu'il est linked ? Oui, c'est flacqué. Donc, ci.g, trusted.ci.g, answered.ci.g are impacted. So, yeah. Since 24 hours. Yesterday, we delivered a new version of the Packer image. So that could be related. But the issue here is that some of the virtual machines are working and building and some aren't allocated with Timeout from Azure API. So that's why there is something word here. It's still not sure the real root cause. So, gotta check. But yeah.  We're waiting for Docker-Windows. I believe we should be able to open a status page after that meeting and had a message on top of CI Jenkins.io To let you know. Which explains why the container images for Windows are slow to build because it takes time and it reached Timeout of the builds. Need status Jenkins.io Message Container images Slow to builds That's all for the Azure Virtual Machine Issues. Is there anything else on that topic? Do you have question or action? No. Okay. So Java 17 is the new default GDK on container. So that's why we... That's the second major change. Is that okay for everyone? One last announcement then. I will replace the third point. Is that we had services done during a few days last week. So I don't remember. We had PluginLscore Incremental Publisher and Reports.Jenkins.io So the third one had impact on the plugin developers. The reason is the person currently speaking. We have wrote issues with postmortem but I wanted to put it on top of the items just to let you know. Because I've learned a lesson on the way Kubernetes manage links between objects when you want to delete some objects. So let's say the summaries first remove the link and then do a second upgrade on garbage collect object and don't do both on the same upgrade. That doesn't work. That was an opportunity for us to improve the monitoring because these services weren't. That's all for the announcement. Do you have other announcements? Ok. So let's have a look at the upcoming calendar. The next week is next week as usual. We will be the third ten. I don't know when is the next LTS planned. 2.414.3 2023 10.18 18 40 42 4.14.3 Ok. Thanks. Release candidate tomorrow. No, no, that's a different thing. Or no, is that? No, no, you're right. Release candidate tomorrow. Nice one. Jenkins security advisory. We don't have Jenkins security advisory. Right. Cool. Next major events. So we had 2 DevOps world where Mark was present. As far as I can tell. And next is in Santa Clara, October 18th. Santa Clara. DevOps World Santa Clara. October 18th. 18 et 19, yes. 1. February 2024, as usual. And they've actually announced the specific dates, right? I think it's four and five or three and four. Yes, that first week. Three and four. Cool. So an opportunity to meet the team member. Any questions so far? Ok, so let's start with the work we were able to finish. So we can thank our survey team for solving that issue about one of our plugins a contributor maintaining a plugin was complaining that despite them changing everything to have the GitHub documentation shown on plugins Jenkins. The old wiki documentation was still used. So no abuse error. No build error when the plugin website is is changed. By by phishing informations we were able to check that the update center generator has an override capability. Most of the time it's because security or emergency infrastructure changes and that plugin was inside these overrides. So whatever value was set up for the plugin was overridden every 15 minutes when the update center index is generated which forced the documentation to be used to the wiki URL instead of the auto detected GitHub. So after learning that mechanism and removing the override we were able to update the whole system and now everything is going fine as usual. And that override file is inside the update center? Absolutely. Let me open the issue. Ok, no need. I'm sure. That's just quite the surprise. Yep, that's the wiki override.properties file inside the resources there and here we have a lot of plugins. So if you see a plugin that looks like it it follow every recommendation and still the wiki is still shown on plugin Jenkins IO then check if the plugin isn't overridden here. So thanks everyone. So the plugin will score one of the free services that was down. So I've tried to write down a post mortem after fixing it. So thanks Adrien Le Charpentier for pointing, for removing this to our attention. So thanks Adrien Le Charpentier for pointing out how to fix it and in order to avoid reproducing that issue we had it monitoring. We had monitoring but the monitoring was checking only a redirect from HTTP to HTTPS. And the thing is that with our Kubernetes system the funny part is even if the backend is down the redirect. So yeah we added a probe. So now if the service goes down for whatever reason we will be alerted and we will be able to avoid waiting 5 days. By the way that could be the reason why the previous plugin not only had an issue with the documentation but also was there in illscore probe because I believe if they change elements during that outage I'm not sure how is the system working on details but that was bringing to Adrien attention that maybe we need to recalculate a few plugins. I don't know what the frequency is but that could be related or it's just me, my Jain. Any question? Ok, same thing for rating the Jainkins.io So that one was fixed and Airbay was run. Same reason exactly. So Airbay was able to add also same fix it wasn't monitored so now it's fixed and nothing else to add here we should be able to catch this issue next time. We had a user who lost access to their repository so like most of the time they had an issue with their Maven configuration in that case that was a subtle one. I think it's worth sharing it with you folks. I'm not really sure of the root cause but we use two different ideas on the POM and POM parent and example and documentation for plugin developers we tend to have what I call the download repository so the repository on Maven POM XML file that describe where to get the build dependencies and the project dependencies and that one tend to be marked with an idea of repojenkins.io.org I'm opening an example here you can see we have repository with that ID and the POM parent that helps developer not having to care to define all the dependency management is defined to Maven the Jenkins.io.org I believe it's something from the past that has been kept because change on parent is not an easy thing some plugins are update often some are not updated since years so changing this one is way more difficult but I realized that since they wanted to publish a new plugin manually which I consider myself a bad practice we have a CD process for that and the human shouldn't be responsible for pushing and deploying a release but in that case you have to be careful in the way you configure your settings XML I believe the documentation is up to date because they follow carefully the documentation so I'm opening the documentation page which say you have to configure your server XML with the same ID so the credential shown here will match however there might be a word behavior where Maven check the URL of both repositories and say oh it's the same and sometimes repo is forced and sometimes Maven is forced so my proposal is maybe we should update the documentation here and tell them oh don't use the settings XML from Artifactory as it but instead change it copy and past this one and create a second server and tree with the same username same password but you must use repo.jankinci.org as ID for a second one so now but I thought that maven.jankinci.org was the preferred just because of the history that repo is is used in URLs but not in okay I'm clearly not understanding I'll need to ask you some more questions later Damian okay no problem but I believe we should be able to improve documentation here I'm not sure if it was the real problem of the user they say this worked after I gave them this instruction so maybe it's a misconfiguration of their plugin but for me it will be worth it to say okay we need to set up credential for both the takeaway for us is that any developers with that set up will start choosing the LDAP account to authenticate the request to Artifactory so in any case that will be easier for us to track the usages of these developers so in any case it's a good thing does it looks good for everyone that means that the LDAP will start to get more more work but that's not a lot and we still have so much more gene for this yeah that's all but that was worth sharing okay next issue unless you have a question no question Archive Genkin Sayo that service is now running on Digital Ocean instead of Oracle Cloud virtual machine has been moved I haven't checked yet the impact on the outbound bandwidth cost on Digital Ocean itself I haven't monitored this one we can afford 500 GB outbound per month before starting to pay for it that's the threshold so yeah worth checking because that is a public web server so that one has been done properly that was really easy the most complicated part was to find the areas where that machine was accessed through SSH but yeah I don't have anything else to add on this one everything including Runbook has been updated is there any question on this one no I'm pleased to note that the cost from Oracle Cloud for October 1 and October 2 were zero dollars yes which means we have cleaned up properly thanks for confirming next issue is a minor one TFSEC which is a static analyzer for Terraform files started to show warning and important messages that the organization developing it was focusing and shifting the effort to trivie their own made commonline static analysis which cover the same features as TFSEC but also had other things it can scan container images and chart and bunch of stuff so that's why we decided to move our Terraform analysis maybe we could benefit from the other features in the future but right now it was only for Terraform project so the shift has been done TFSEC has been removed from all of our assets and trivie is available instead any question ok we had the account issue but the person never answered so thanks Mark for taking care of this one now let's move to the work in progress issues that were started and we that on which one we worked or at least should have worked during the past milestone and for each one we will decide of course if we continue working it on the next milestone move them to backlog or stop working on them first one access to get up packages in the plugin that one is interesting so we have a plugin developer who open to work at Redats to build a plugin that require Java dependency on the plugin a Genf file which is not on Maven Central or public Maven repository but on a GitHub packages repository so of course that mean you cannot access publicly without a GitHub access token to these packages as you can see on my screen here the documentation is really useful they say add dependency et cetera but only inside a GitHub environment with a GitHub token of course when we build on CI Genkin SIO or when a contributor builds on the machine they cannot because it requires and mandates having a GitHub account so they ask the question what would be the solution and the possibilities one of the possibilities they ask what can we move these dependencies to the Genkin's public artifactory which technically will solve their problem we tend to have that policy that say hey if we host it we have the code and the properties and the legals because if we need to update an emergency for security or legal reason the binary that mean we need to have un actionable or lever somewhere my belief my belief is that they don't use a public artifactory or maven central for legal reason or license reasons so that's why they are using GitHub package so that's why I've proposed the solution but yeah there has been discussion, no feedback since 4 days to use the same pattern as other plugin developers they can store the JAR file on the source code of their plugin so it's their responsibility modulo the license but I mean we have license check and if someone from the security team on Genkin's discover that there is a license thing they will just remove the dependency and stop the plugin and if they have the JAR they can control the update process so a given maven file like the callis callis plugin can reference the local repository so let's wait from a feedback from them if they don't give us a feedback end of milestone we close this issue next week is that okay for everyone? yes I'm the thought of checking binaries into git repository scares me but done it before yes it can work that's what we have to do same for me but I mean that's a solution for them if they want to continue building their plugin as team propose they can also try to publish on maven or other public repository or host their own next issue goss the test framework alas server spec for our packer images in order to define the images for the virtual machine container linux and windows virtual machines that we use on our controllers so we have a contributor who started to help us which trigger a lot of exchanges between stefan high and that contributor which led to a let's increase the test coverage by shifting to sanity checks that are run on part of our provision in script to something else that say hey let's connect as Jenkins user and check that tool, that tool, that tool this acceptance test would use goss which is a framework that can work on both windows and linux that you can use with a wrapper named digoss on containers so that's really easy with this one it's already installed on the machine so we could run a set of tests which are easier to maintain than bats or power shell pester or whatever framework and it has been changed and updated by stefan to cover linux we cover all gdk and 3v so now if i understand correctly stefan the next step will be to move all the sanity check to that acceptance test orness except if we have some specific ones or most of them at least yes ok and start to do the same on both windows and linux exactly the main challenge sorry go ahead that's probably what you will say because i think it's in the comment down exactly good catch the main challenge here i say challenge but that's a big word is that that means instead of we want only check that we can execute the binary we will run the binary through goss and check for the version or something from the std out for instance we will check that java-version answer 11 and soon 17 by default that opete bin java gdk 21 bin java answered 21 on its output which mean each time we have an automated pull request that update dependency we have to also set it up so that it also update the goss checks otherwise it will fail that's the challenge it's more temporal challenge than really a technical challenge and that's why using the new key in the goss file with i think the step is exact make it easier to track in the agacy line manifest believe we have an example here and let's see what does the file looks like let's see the new file now is here so goss testernes is described with that yaml syntax we are only testing for command we can test for files, users, packages and other technical elements we have files in 1932 true I forgot about this one that's a way for us to check that it's a contract between us the builders and provider of the images and the consumers at least on ci is the tool available for all the architectures we support including the rather obscure ones like system 390 I haven't checked but it's go long so it is really easy to build it great, excellent at minimum it's available for ARM all the ARM platforms and the Intel platforms Linux ARM and Intel is out of the box Windows and macOS both for macOS Intel and IRM is still experimental you need to set up a special flag or environment variable for what we do commands are easy and work out of the box so Stefan do you think you should be able to continue working on this I will try of course yes so we'll move this to the next milestone I on my side is also working on the windows ghost part for further things so yeah let's continue working with this one we have an issue Oracle cloud project and tools so that was a joint work from Mark and Hai so I have the pleasure to say that as Mark confirm with the billing we don't have any resources running on Oracle cloud so now the two last steps are administrative we need to ensure that all the builds are paid and that the account is closed Mark and Hai still have access to the account but the rest of the SSO integration with Azure all the leftovers have been removed the action item is now actually in Oracle's billing team they made a change that made it so I can't actually pay them for three of the invoices but then they said please pay us and I said I can't and now they're working to try to find a way so that they can make it so that we can pay them but it's their action item worst case they could sponsor us and say hey it's ok they could just say it's a donation I'm ok with accepting their donation as well the time spent with the accountants might be worth depending on something else that is a financial decision they get to make that is not our concern they get to decide how they spend their financials yes absolutely so is that ok Mark do you approve that issue on the next milestone considering that's only for reporting yes yeah no objection to put it in the next milestone and at some point we may close it just to get it out of our list even if it's not resolved because it's outside of what any of us can do anything about yep I propose we had a full milestone before taking that decision is that ok for you yes I like that the next topic the next topic is speed up the docker image library to create push tags at the same time that one was put on hold during last milestone am I correct I was sick I'm sorry do you feel like you could work on this during the upcoming milestone Stéphane I will try yes ok so I'm keeping it on the next milestone nothing specific to say here we need it to be sure that we publish images faster with less complexity that's cheaper yes that should be cheaper because less builds good point next issue remove account request field from Jira login page I need help from Jira administrator or someone who know their way on Jira I understand the issue it's changing something on the popup but I'm too scared to try things on Jira that want to break everything so yeah I will need help on that topic I'm not sure who I could ask for help on this one I believe Tim has access right Daniel Beck Tim Jacomb are the two people that I would entrust that one to Basel Crow could probably do it as well but he would have to watch while you did it because I don't think he's actually a Jira admin but he's done Jira admin before ok I will start with Tim since he might had issue but it was one month ago so I will double check with him then so I put it here thanks Marc Stéphane can you give us heads up on the HA properties of the replicated services yes it's between 2 différents it's anti affinity on one side and pod disruption budget on the other one sorry we are almost there I think there's only 4 services to go and then we will be able to go back to the IRM64 migration to remember it's the way we handle the repartition of the pods between nodes and to make sure that when we recycle or reboot or kill a node in the services under it and the pods still have pods somewhere else to handle the load and we are not out in the blue that's anti affinity and pod disruption budget to make sure of the anti affinity and tons of view test because we love it yeah I'm driving Stéphane to dream about write the test then write the code then refactor even for elm charts or have nightmares that's night too test driven development is a thing keep going that's exactly that you wrongly spelled nightmare driven development but yeah who am I to judge thanks need help from Tim or Daniel we almost done 2 free services left we saw interesting interesting let's say behaviors because the way we have set up the HA we had it anti affinity that say hey I'm a replicated service and I see there is already a replica running on that machine which tend to trigger quite often the autoscaler so combine with the pods the pod disruption budget that say hey you must always have one running pod the behavior we tend to see is that it auto-scale up the virtual machine start a new machine start the pod on it and only when it started then it remove one and then everything start to to change which keeps the high availability as we expect but our deployment takes a bit longer and we have to wait 10 minutes before the autoscaler dynamically reschedule everything properly and scale down to the minimum amount of machines so that mean the auto-scale up and down on Azure is still really efficient and dynamic second funny thing is that we discovered that some of our charts or installation or services we install tend to have either too much replicas which we decreased for instance jenkins.io because we are fast in front so we don't need five pods running to our absolutely okay we decrease these usages and some as bleak and genix ingress tend to have different kind of deployments with different roles the kind of genix you have one reverse proxy deployment with two replicas for high availability and we have a deployment of back end web server that serves some 404 pages when we have a 404 and all of this one are currently mixing each other with the anti-finity so we have three pods which mean we have three virtual machines under we can't shrink down the usage it's temporary it cost a few bucks but no more than 100 bucks per month on the projection I made we will fix this element but we weren't aware of these behaviors so we need to fine tune in order to optimize the resource consumption on the other hand when we have always free machines that mean the auto scale up scale down we started to see at the beginning won't exist anymore because we will always have a third machine available when deploying a service so that's for outcomes yeah if we have two records couldn't maximum if we have three or four it's dead with only three nodes it's just because the count of pods we ask for is too so yeah that one is doesn't look like much but we learned a lot on the behaviors of the scheduler and the behavior of our application as a reminder as a reminder we need this issue to be finished before starting the work for Kubernetes 1.26 upgrade any question no next one then Matomo we were able to work on Matomo so the MySQL instance is now started created and we have an empty database running inside our private network on the public cluster and the Docker images is now built for and released for both Intel and IRM64 and it's built so the next step now is to start bootstrap the first installation on the public cluster with the custom image and the database we created so that require using and setting up the Elm chart, the official Matomo M-Short and installing it and then we will start being able to run the service so we are making good steps and I believe we should have something to test next week is there any question mage ok ok, so then next step M-Short initial installation artifactory bandwidth reduction option mark it was on your area so let's list it as done I received the final logs from JFrog unfortunately log format changed and I'm not willing to do the effort to deal with the change log format we're just going to say yes it's done as logs format change will see result measured by JFrog ok, makes sense that's the simplest approach I'm just accepting that it's not a good investment of my time at least to adapt for only one analysis of log files it's just not worth it can I ask you then to close the issue with a message explaining this I will do that to of us will schedule the meeting with JFrog I actually I don't even think we need a meeting they've I think said we're done so I don't think they've asked for any additional meetings I think we are just done if they ask for a new meeting we can certainly schedule it cool so then I'm moving that issue on the done steps and I will let you close it I will do that thanks Mark so Artifactory is done yes I'm sure remove jen kinsayo pages aren't accessible and indexed anymore that issue was put on hold because the survey wasn't available to work on it he focused on updates jen kinsayo but he still search and saw a lot of things he did a backup of jen kinsayo and I believe he communicated with you folks from the documentation team about the other results so I believe that is going to plan operation eventually next week unless there is a blocker we have backup and snapshots so the goal will be to say hey let's snapshot at a given moment deploy the new version which removes the hold pages and see the result and if we start to have issues that we can catch or user opening issue on community or ldesk or jen kinsayo trackers saying hey that page is gone or whatever then we can start either cherry picking on short term from the backup and then fix the rebuild or if we see it's catastrophic then we restore the backup and we go back to the former things and just remove the to be deleted pages manually if you want to solve the other issues that cause that one makes sense for you folks so airway will communicate once ready I'm not sure if you will be able to run this one this week since he's still focused on updates jen kinsayo but I will see with him if we can share the burden on updates jen kinsayo by default I will move it to the milestone and I will let him either remove it if he feels like he won't be able to walk and we will add it back in one week or when he will be ready any question ok next updates jen kinsayo which is our top priority hence it's the last issue here so I can tell that we successfully managed an air2 bucket in Cloudflare in our Cloudflare sponsorship and we were able to use it and use it as a mirror so we have a mirror bits test instance only for updates jen kinsayo running in production and publicly available and if you use the proper URL you can have that mirror serving the files now the work in progress the survey is working on is going to update at least two scripts which are critical in order to copy the updates in the update center json file not only on the current update jen kinsayo but also on the two locations we use for that new system under what we call the reference as your bucket which is where the mirror bits is watching the files and the changes and on the air2 cloudflare which mean we will have free location with the real life changes happening every 15 minutes it should not have any impact on the current update jen kinsayo but that will allow us to start testing for real the new service copying the update json not only to pkgvm but also to azure bucket and air2 bucket under the hoods that will mean installing s3 command line and azure command line on the trusted stat permanent agent which is managed with poupette and then adding credentials on trusted cian kinsayo for both buckets which are different from the existing credentials tests that we can copy random files from dumi build on trusted cian kinsayo running on the agents and finally open the pull request on update center 2 for copying the update center json but also something that air2 cooked on the crawler the crawler job is a job that once a week generates the jen kins tools installer metadata and the crawler is also copying files to updates jen kinsayo under the slash updates sub directory so good catcher on this one because i totally missed it personally and yep so we should be able to report last week the next step for him is once this is done once we have the same content we will try your live controller to request that new service is there any question on that status so of course we will continue working on that issue um let's check the new issue if we have some and the new topics that if you have some to bring do you have new topics on your own then for me ok so let's look all together on the issue we see here oh not able to login so that one will be on the triage later gira email status from send grids stefan can you explain and help us triage on that issue i forgot this one and that's um daniel request to be able to get access to the send grid dashboard of the account corresponding of the gira configuration in order to be able to have data about the mail that are not going through to the jinkins developers plugin developers because he got one maintainer of a plugin that said that one of his email wasn't receiving the emails but the jmail one was and he would like us to be able to have more information on that so if i understand correctly it's on send grid it's not on gira right in fact gira is using a send grid account to send the email so it's on send grid that we will have all the smtp logs that we should have ok so that mean we we will have to have that issue we have access to send grid account i don't i never remember yeah otherwise we will need to ask access there is one that erve and haie asked one of the email systems that we have access to and i believe it's send grid but i'm not completely sure so go to check ok thanks for the explanation it's clear for me and i'm adding it to the milestone i will create and that will be on erve and haie check the send grid access share it with mark and stefan if it's not the case and then from there stefan you should be able to take over and fulfill the request with daniel is that ok yeah perfect thank you um migrate terraform state from awss free to azure buckets so that one is one i created we have in order to manage the terraform state of our project which are sensitive data you can see that has database for terraform where that database has the history of all the changes that went through the infrastructure as code management so of course it has credentials and it's sensitive we use these states um on shared storage that are private and some of our project are started with s free buckets private s free buckets that that host this terraform states and some of all the project were using azure buckets uh in the efforts of moving away as much resources as possible from aws that mean the project with the terraform states hosted on s free buckets needs to be moved on azure buckets so we need to create the azure buckets migrate the state check that the job are still performing without destroying the infrastructure and then remove the leftover s free buckets so it's just that yeah we have to communicate when we do these elements but that shouldn't be something complicated there is a lot of documentation and there is a command that is able that should be able to migrate states to the new systems so I'm I'm willing to work on this one anyone interested can pair with me or take over some I think we only have two or three project on the six we have so that should be easy one of them was oracles and it has been deleted so it's one less to to execute is there any question on this one no okay I believe we have one that should be started but no pressure on finishing it though Kubernetes 1.26 because now that's Stefan has almost finished the ability topic I believe we can start on the next milestone with upgrading at least the kubectl binaries and starting the process of checking the changelog the goal will be once the HA is finished we can start discussing a date for Kubernetes 1.26 upgrade is that okay for you okay I will add afterwards the the link to the issue yeah so anyone interested can contribute it's Octoberfest so if you want to try things upgrading Kubernetes 1.26 shouldn't be that complicated of course if it is or if you want to discover because if you don't know you don't know please ask the team on IRC I will mark the associated issue as a good first issue on the proper location I got two topics I'm not sure to work on them but I want to mention them first one on the area of Packer Windows container so I'm mentioning it because in fact I already started to work on it as a submarine but the whole goss is one of the foundation required for that the goal is to also build windows containers with Packer that's one of the only elements we don't we don't use Packer 4 and that should be technically possible now I successfully build it on my local machine and on standalone machine and now I'm dealing with word pipeline behavior that I don't understand I believe I want to wait for the world goss project and the work that Stefan started around improving the pipeline for Packer but that one is coming I also have the old pull request of the parallelization of Packer that is in the back too yep so that one optimization the goal as a reminder is to have a faster feedback loop when we open the pull request on Packer image and less failures we have the windows container and finally one that can be started and I act over fast again that one should be not easy but absolutely available for a newcomer to replace the last docker dash something images that we use on infrascii for instance docker dash elm file where kubectl 1.26 will be we have few tools like elm file etc the goal is to make sure that these tools are installed on Packer we have a list already available Packer image repo I believe creating one issue labeled act over fast and good first issue will be a good action call because once the Packer image for Linux has all of these tools then we can start trying to swap the docker images and so that means less maintenance for us in the future and the whole in one exactly docker elm file chicop so that's the first let's say top level things that we work on not as part of the milestone it's a long running process but we could benefit from the act over fast the second one are the major upgrade we have pipette 7 and we need to start thinking about this one so because we have at least 14 modules on pipette that we cannot update anymore because pipette 6 is deprecated so that one start to be important I propose to wait after Kubernetes 1.26 but yeah we have to think about this one ends me mentioning it after kube 1 background task act over fast ok is there any other topics you want to bring to this meeting ok so that mean we can stop and I will publish all notes and recording as usual once available so for everyone watching us see you next week bye bye


Good to see you, sir. Everybody, can we get over here? Yes, sir. All righty. Good morning, everybody. Well, Secretary Carter, I want to give my thanks for you taking the time this morning to come to the US Naval War College at Newport Road Island and answer some hard questions from our officers here who've come to ask those. I want to prime the pump with a couple of questions that we've gotten in order to get the ball going. I know you want to immediately hear from them. Yeah, can I just, first of all, thank you. Wow, thanks very much. I appreciate your leadership of this place, centrally important place to us. And so I'm grateful to you and the dean and all the other leadership. Continuing education, continuing self-improvement is more and more a part of life in the United States and around the world in general. So organizations are finding it necessary to help people stay up, keep up, stay competitive in the course of their career. So what is done here is, to me, centrally important to my force of the future thinking, which is trying to look generations down the line and making sure that we're state of the art and how we handle people as well as state of the art in terms of how we handle work craft and technology and all the rest that goes in. This is a really important place for me, and I'm grateful to have the opportunity to be here. Just wanted to say that. All right, I appreciate that. My first question has to do with a national security strategy. Here at the War College in our strategy and policy court, our senior officers have been looking at long-term competition. And one of the examples we draw from is the British experience with overstretch or overreach in the late 19th and early 20th century. So given our current budget constraints, aggression with Russia, continued conflict in the Middle East, our international terrorism threat, how can we afford what are the costs and the risks associated with continuing a balance or a pivot toward East Asia and the Pacific? Well, the reality is we've got to do it all. And your question is, can we do it all? But let me just remind you what all is, because yes, there's the long-term competitive situation. That's the only word you can use for it, with Russia and China, which is a position they have chosen but one that we need to meet with steadiness and strength and deterrence. And since they're at the higher end and have generally greater geographic reach than others, that is a stretch for our capabilities. But we're investing a lot in them. And the Asia Pacific, especially important, because it's the single place in the world, single region of the world of the most consequence, simply by dint of the fact that it has half the population and half the global economy. So it's going to be a big deal for the United States. Then you get to what I'll call the hardy perennials, North Korea and Iran. And a little bit lower down the line, but still quite worrisome both behaviorally and in terms of capabilities that they're developing themselves or getting from somewhere else. And then you've got ISIL, which we're going to beat, but that takes a certain amount of resources to defeat them. And I'm certain we'll do that. But there's a certain amount of preoccupation that goes with conducting that war and winning it. So those are the five things that are currently on the plate. And then you always have to have in the back of your mind that our historical record is perfect in never having it right what's the next big thing. And so staying agile, flexible, wide area field of view, excellent keeping the edge, all that is essential for what might come down the road. Now, can we do it all? Well, we can do it all. Obviously, talking about resources, you'd always like to have more resources. My biggest concern is not with the right now, but in the years ahead, I think we have the right mindset. We have determination. We have public support. I was at ROTC, at Yale, where when I went to college, I'll tell you, the climate was so different, not for me, but for most of the people I went to school with. And ROTC wasn't welcome, and it was a big deal. So we have the support of our society. We have the fact that we're attracted to a lot of people around the world like to work with us.  Many of them are here. We like working with other people. We're effective partners. We treat people decently. We represent things that other people want and they want to associate with. So we kind of have all the friends and the allies, and our enemies don't have any. Our opponents don't have any, and nobody likes them. Nobody wants to work with them. So we've got a lot of strengths. The biggest concern I have down the road is at this particular moment, in terms of budget and resources, is I hope that we're not going to see the collapse of the bipartisan budget agreement. If we've got to have some budget stability, we can manage within. We understand we're not going to get everything we want. Nobody ever gets everything they want. But we need stability. We need stability to plan. Our industries need stability. Our people need to know what their future is. Our friends need to know that we're with them. Our enemies need to know we're strong. And so that kind of stability. And we had a two-year budget deal which was done in the right way, which is Washington getting out of gridlock, coming together, both parties, putting the whole smear on the table. Not just discretionary spending, but revenues and entitlements. Because remember, they're the lion's share. You can't balance the budget on the backs of us. It's just the money's not there. So it just doesn't work. So you've got to have everything. And there it was. And it was supposed to be a two-year budget deal. Now, six months into it, they're passing bills that call into question whether that is going to collapse or not. That worries me a lot, because on the other side of that is $100 billion of sequester cuts. That's what happens if the budget deal collapses and we go back to sequester. So that's my principle worry. Strategically, we know what we're doing. Obviously, we'd like to have more. We always like to have more. But we can do what we need to do. But I can't pretend that I know we've figured out how to do that with $100 billion less in coming years. That I don't doubt is going to be possible. OK. Well, I'm going to follow up one question, then open it up to the floor. Since you were talking about budget, over a week ago, you spoke at the Navy's League Sea Air and Space Expo. And you pushed back a little bit on recommendations from the Senate Armed Services Committee in the National Defense Authorization Act with reference to acquisition reform. And given your long service and expertise and acquisition, I wanted to give you an opportunity to amplify, as well as you talked a little bit. If you give us some comments, you talked about the balance with Congress in terms of providing oversight versus micromanagement of defense. Well, first of all, there are some good things in there. And there are many well-intentioned things in these bills. To get to your second point, however, these bills are now 1,000 pages long. They have hundreds of provisions. And in one year, they add boxes to our organization chart. And the next year, they take boxes away. Just on principle, I believe that that kind of micromanagement is not helpful. Lots of reports require that kind of thing. And I think our leadership is the best source of good management ideas. That's why we're here. Like us, they can find another crowd of us. But the management of the place ought to manage the place and not be micromanaged. That said, we've got to work with our committees at the end of the day. They had the final say on our money and on the law. And I appreciate the spirit behind much of what is going on. I understand very well the frustration with acquisition because I share it. I understand the desire to keep pushing us to think about how we're organized and structured. That's fair enough. I'm OK with that. But I do have problems with parts of it. I hope we're able to work this out, but we'll see. The one you specifically reference is a proposal that is not quite clear to me, but has the effect, if I understand it right, of separating research and engineering from procurement, which is sort of like violating the third law of thermodynamics or something. If anything, we have a problem perennially of connecting the research and development enterprise to the production area. The last thing in the world we need is bureaucrat. To me, there's way too much of that. So it was a proposal that was bringing them together further. It would make more sense to me. So I'm still trying to make sense of it. We'll talk to them. We'll try to get somewhere better in that regard. But I couldn't support something that enforced that separation. I just know better. And our history over time, and I've been doing this a long time, as Admiral Howell referenced, I go back to Harold Brown was my first boss, also a physicist, by the way. But in Harold's day, and Harold been director of research and engineering. And that meant the buying guy, too. I mean, it meant it was AT&L. It's just we renamed it over time. So that one I really can't support. And there are other ones that I can't support in there. And I would respectfully appeal to the committees to stick to the big things and not have a lot of little move this around and move that around. It's almost impossible to believe that from that remove, they can have a better perspective on what we need to manage ourselves. That's not that there's anything wrong with them. And it's not that they don't understand many things. But we're right in the thick of it. And I think that our senior leadership, our chiefs, our service chiefs, our service secretaries, myself, ought to have the latitude to organize our environment and not have it organized for us. OK, appreciate that. We'll take questions. I remember to use the mic because this has been broadcast. You have a question there in the middle? Yes, sir. Good morning. Erica Jordan with the Defense Contract Management Agency. In the past, reducing oversight of defense contractors has been less than successful. One prime example will be the future combat systems. Why do you think that increasing their in-value management system threshold will result in better defense contract management as well as reduce it? I'm sorry, increasing. I just missed the last part. In-value management system threshold. Well, first of all, DCMA is a great organization and a very essential one. And I think the question I don't know whether everybody could hear was basically about, I'll put it in these terms, the balance between ceding to the contractor a lot of control over program execution rather than keeping tight control and oversight on the government side. That's a difficult balance. You're right. Future combat systems was an example where we outsourced the systems engineering, configuration control, everything. And that was the rage at the time. Let industry do it. They'll have the expertise to do it. Well, that didn't work almost all the time. It failed. And so you're right. The pendulum needs to come back. Now, not all the way back because I do want there to be shared responsibility and shared expertise in industry. And also, I need to be careful about what we can take on because to be blunt about it, our acquisition system is uneven. Some parts of it are up to that job. And other parts we need to work on and get up to that job. DCMA is an inestimable help in all this, I should say. Say that. So it's something that I think where the pendulum has swung back in the direction of more direct government involvement. But there's a consequence to that, which is we've got to get better at it on the government side. That's the civilian side and the uniform side. And that's related to something else that comes up in the Goldwater-Nickels discussion of acquisition, which is the role of the services and the service chiefs in acquisition. And I think that's very important. That's an area also where the pendulum swung too far. And the service chiefs basically didn't have anything to do with acquisition for 15, 20 years or so, or not nearly enough. And I think that was the pendulum going too far. I'd like to see it get back the other way, but I've told the chiefs, in order to do that, you have to educate yourselves. Because most of you and most of the senior leadership by now in all the services have gotten there, not because of their expertise and acquisition. That was the way it was when I started out in the Cold War. That was the time we never actually did anything. We just got ready to do things. And so over the decades, being good at getting ready to do things was what made you proficient in your service. And so acquisition executives rose to the top. That nodded, and there's nothing wrong with this. But we've had a more operational set of decades. And so we tend to have more operators at the top. And so these guys need to get in the game. But I'm telling you, you need to be humble about what you really understand. We need your understanding of what the requirements are. We need your management and leadership acumen. But you're also going to have to understand how to manage big programs, how to deal with technology, and so forth. And that's not something that is in your background. Next question. They're in the back. Yes? Sir, good morning. Ashley Pap, despite my new England draw line from the Royal Australian Navy. Most of us are about to embark on the perhaps the next phase of our careers at very senior levels. Some of my compatriots are about to be promoted to admiral, of course, when they get back. But you talk about half the population and half of the trade in Asia, the Western Pacific. We're seeing, though no one has figured out the algorithm yet, we're seeing a new model of pushing the boundaries of a global rules-based order, particularly by Russia, through the Ukraine, et cetera, and in the Black Sea. And then China in not only the South, but the East China Sea and further out into the Blue Continent. What's the tipping point that forces the international community to say, hey, that's enough without boxing an adversary into a corner where they have to come out swinging. We're about to go and live very complex and volatile environment where the ones are gonna have to untangle these threads that are becoming more and more tightly twisted. What's your advice for perhaps your countrymen and also your allies on where that needs to go, where that tipping point exists when saying enough is enough, doing something about it? Good question. First of all, let me just salute our Aussie friends everywhere around the world, including at this very moment. In the places you know about and a number of places we can't talk about here, but you probably individually know about, we're like this with the Australians in so many ways. And it's a country that like the United States who has great credit regards itself as having a responsibility for the global order. And then that gets to your question. Then there are some who evidently don't either wanna challenge that or have an intensely self-absorbed view of how to conduct themselves internationally. And in their very different ways, Russia and China fit that general description. My view is that just looking at the leadership of those two countries and their current inclination, this isn't gonna change soon. And now it's having the effect of isolating them because everybody, you're talking Europe, it's the NATO side and in the Asia Pacific almost all countries are reaching out. And look at Vietnam and the United States just in the last few days with the president. Why is that? It's because they know that stability and security is what's created the Asian miracle. And that it could be threatened by this kind of instability and they wanna be on the side of keeping a system that has the trade values and the human values that have made that part of the world work. So I think you gotta look at this as a long, I don't see there being a barring something, sort of some sort of instability in those two countries which I also don't see happening. Given the current leadership, I think this is gonna be the trend for quite a while and we need to be in it for the long term. So this is gonna be a long campaign of firmness and gentle but strong pushback for probably quite a number of years in both places. Now I also believe that the internal logic as was true with the Soviet Union over those many decades and again a different situation but only similar in this respect. The internal logic which suggests that this isn't really what's in the interest of the Chinese or the Russian people in the long run but that will prevail at some point but that's almost academic at this point because their leadership is way on the other side of that equation right now. So I think we have to brace in for the long run. That's certainly our approach. Our rebalance isn't a couple year thing or do this for a little while and try it out kind of thing. This is a long term commitment. After all we've been at it for 70 years. And we'll stay at it because we have been the pivot to all military power in the region and the linchpin of security and stability in that part of the world. We're gonna keep it that way. That's what the rebounds is about for a long time. Okay last question over there in the back. Good morning Sir Major Dylan Patterson from the Air National Guard. A couple years ago your predecessor former Secretary Hagel was here not at the War College but he was speaking to a group in the industry and he made some comments regarding the proliferation of advanced weapons into adversaries of both state and non-state actors. When you look at some of those weapons a lot of it is unmanned systems, stuff in the cyber domain and the nature of development in that area seems to be a lot faster along Moorslock progressing every 18 months, two years as opposed to building capital ships which take years and years to develop. An example might be Nigeria where we have some students here from Nigeria that are procuring unmanned systems from China instead of us. So when we look at the ability for competing defense systems to develop stuff very fast how does our process whether it's the PPBE process or our defense foreign military cells recognizing that's probably Secretary Kerry's question but if you answer that I won't tell him. I don't understand his line. It's actually both of our questions. How do we align our acquisition and development process and getting that to our partner nations so our equipment, our tools and our partner's tools can keep pace with an adversary? Good question. Two things. First of all, we're too slow and that's a problem and if you really want to go after acquisition you don't take research and engineering and separate it from acquisition. That was my point earlier. They've got to come together faster because the future is going to go to those who are agile, creative up to date, competitive. And yeah, there are some things like capital shifts that naturally go on longer time scales but unfortunately a lot of the reflex of our acquisition system is to operate on that kind of time scale which as you point out is completely inappropriate when it comes to things like drones when it comes to things like cyber. And so that's a very big preoccupation of mine and it's the central reason why you see me pushing so hard to connect us with the tech community and rebuild those bridges that were so strong when I started out in this business between the technical community in the country at large and the defense world. That was a union bred in this country in World War II. It lasted for a few generations thereafter including mine and now it's just not a natural thing. People they don't know us and our problems they don't know how to work with us as easily. We have to, but it's also no longer true as it was when I started out that all technology or most technology of consequence originated in the United States and originated in the defense or government environment. That's just not true anymore. So we have to have a different model where we're connected. That's why you see me on Silicon Valley up in Boston out in Austin and so we're trying to get the most vibrant parts of our tremendously innovative country harness to the United States. Now these guys want to do it. You talk to them, they're patriotic.  They know they can't, that everything they do has no meaning if there's no security. They're people who like to make a difference. They like to do things that matter. They like to do things that are consequential and they know that what we do is consequential. So I find the uptake is really great but I've gotta work real hard on that and I urge all of you to do the same. We just can't sit back and expect that it's all gonna come to us anymore. That's long in the past and we can't expect that we can do things on 10 and 15 year time scales. The export control system I don't even want to get started on.  And so you're right, so we're frequently behind and it would be better given that country X is gonna have a certain system but it would be better if they got it for us because at least we'd be in there and it would be part of our partnership and so forth but to stand back and say, well, we don't wanna do that. So we're gonna let somebody else sell the identical item into that, I don't mean any sense to me, that's cutting off our nose just by our face and yet we do that again and again and again. So it's a serious problem and I did when I was AT&L, a number of things to speed us up. We're still too slow but we're a lot faster now. We have basically fast tracks for stuff but then we do wait for the diplomatic approval and I respect my diplomatic colleagues and their views and so forth but the results here don't add up, they don't make sense, it's not a sensible system but I think that is in all fairness secondary to our need to pull our own socks up and get faster and more agile. Otherwise we are gonna be left behind, we can be generations behind just believe me, there are areas right now where we're way behind, we're trying to catch up or two or three generations behind and the enemy, just take ISIL for example, ISIL's quite agile in the net, they're barbarians but they're good with the internet. Now we're trying to eliminate that capability from them, that's what I've got cybercom doing which would be our first real cyber campaign in Iraq and Syria and take that freebie that command and control freebie away from them and make that part of crushing them in Iraq and Syria but you know, 10 years even, certainly 20 years ago, that wouldn't have been an aspect of the conflict, it's gotta be an aspect of the conflict now and we gotta get in the game and be good at it. All right, well thanks for taking time today, you have any final comments before? Well, I just to say how much I appreciate that the, yeah, I don't know what it feels like to you all to be here in terms of your overall careers but I'm gonna tell you how it looks to me and this is to my international friends as well, to the international people here, thank you for being with us, we don't take it for granted, I think at our best, working together, we represent the civilized, no other way to say it, world, protecting itself, protecting its people, letting them do what they deserve to do which is live their lives and dream their dreams and have peace and that is a wonderful thing so thank you for those who are not American here for being with us and for the folks from the American military and our civilian counterparts as well, all our DOD family. Your being here represents your awareness that in today's world, we're never out of school, we're never out of school, this idea that you graduate from school when you're 16 years old or 20 years old and then that's it and you live with the rest of your life, that's gone now, everybody needs to be constantly and learning constantly changing because we all individually need to be competitive as well as collectively be competitive so I need people that have that edge because I need the best because in the end of the day our military is the best in the world because our people are so good and I can't count on people like you generation after generation after generation. I've got to work hard just like I have to work hard at connecting the technology base, I have to work hard at connecting to the population and getting them to join us, getting once they've joined us to stick with us and when they've decided to stick with us, continuing to give them opportunities to grow and change, assume more responsibility by having more capability, that's what this place represents us, it's an extremely important institution to me, it's a highly successful one and I look forward a little bit later, I'm gonna try to learn from you what your scholars and what you're thinking can provide me in the way of advice but it's principal purpose is to educate people who are already highly successful and give them that sort of extra jet pack to go further and it's extremely valuable, it's an incredible part of improving the readiness and the prowess of our force so congratulations on being here. Well thank you very much for the interview. Thank you. Thank you.