Podcasts about K10

Jason Pak and Carl Poppe, the senior director and director of business development for land systems at Hanwha Defense USA who are both West Point graduates and retired US Army artillerymen, join Defense & Aerospace Report Editor Vago Muradian to discuss the recent conclusion of the US Army's trails as the service seeks a new, more mobile self-propelled howitzer; nature of the test conducted by the five entrants; how the Ukraine war has changed now land forces will use artillery; role of unmanned air systems to better direct and coordinate fires as well as technologies that will increasingly automate future howitzers and resupply systems; attributes of the the K9 Thunder howitzer and its K10 resupply vehicle; ways to increase artillery round production; integrating new munitions like long-range projectiles and better ballistics computers into future systems; the merits of wheeled and tracked self-propelled howitzers and Hanwha's drive to develop a wheeled offering; and whether tariffs, retirements and personnel cuts have impacted program execution to date.

On this episode, Chris is joined by Dan Hogan, Founder and CEO, Hogan Built and Hogie Shines.  They chat about how Chevrolet K5 and K10 trucks have become the new "Blue Chip" collector vehicles and Dan's evolution from body shop laborer to founding and growing Hogan Built, the preeminent investment quality GM truck restoration and modification shop.  They also discuss a few hallmark and in process builds. Move over coach built Duesenbergs and low production Ferraris, Action Line (1967-1972) restored modified Chevrolet K5s and K10s are the new top dollar "Blue Chip" collector vehicles.  With modern custom chassis, LS powertrains, coil spring suspensions, six piston disc brakes and all the creature comforts of a modern vehicle, these trucks perform like new while looking classic.Based in Pheonix, AZ, quality is paramount at Hogan Built. For nearly a decade, they've gained a reputation for producing only the highest quality restored modified GM trucks and they strive to continually raise the bar.Follow, Like and subscribe to the podcast on Instagram, Facebook, YouTube and your podcast listing platform. Check out our website at classic4x4.com and reach out if we can help you sell your classic, vintage or collector truck or 4x4. Thanks for listening!

For review.1. Hezbollah attacks Northern Israel with missiles and drones in retaliation for strike on senior commander.2. US SEC DEF:  2 x US Carriers to Remain in CENTCOM AOR.With the USS Abraham Lincoln (CVN-72) and the USS Theodore Roosevelt (CVN-71), there will now be 2 x aircraft carriers and their warships available for US Central Command.3. US Israel - Hamas Hostage Negotiations.A US official says that the hostage talks held in Cairo the past several days have been “constructive.” Notably, US officials appear to be the only party in the talks who sound hopeful about their trajectory.4. Norway and NAMMO collaborate to increase 155mm munition production domestically and in Ukraine. Norwegian Prime Minister Jonas Store: “This government has taken several measures to increase the production of artillery ammunition in Norway. At the same time, we see that it is important to strengthen the Ukrainians' ability to produce modern artillery ammunition in Ukraine."5. Turkey opens the world's largest submarine floating dock with 3,000-ton lifting capacity. The dock is expected to be used as submarine maintenance and overhaul floating facility.6.  North Korea Demonstrates Loitering Munitions that Curiously Resemble Israeli Design. Experts said the drones in the images released by state media looked similar to the Israeli-made “HAROP” suicide drone and Israeli “HERO 30.”7.  Chinese Y-9 Aircraft Violates Japanese Airspace.According to Japanese officials. a Chinese Y-9 electronic intelligence aircraft carried out a two-minute violation of the airspace over Japan's territorial waters at the Danjo Islands in the East China Sea on Monday.8. Hanwha (South Korea) opens new Redback Infantry Fighting Vehicle production plant in Geelong, Victoria (Australia).  The facility will also support the manufacturing of Huntsman AS9 self-propelled howitzers and K10 armored ammunition resupply vehicles. Following its opening, the site is expected to support 2,100 jobs,  

One of our favorite go-fast guys returns to the podcast to update us on his land speed record truck, his propensity for prowling Facebook marketplace with a fistful of cash, and his most recent acquisition that will blow your mind, as well as the 42-inch mud-tires that adorns it. The Truck Show Podcast is proudly presented by Nissan in association with Banks Power, AMSOIL, and EGR USA.

Measurement-based care is gaining popularity, but which questionnaire should you use and what do the data really mean? Psychometric assessment encompasses everything from neuropsychological testing to self-report questionnaires like the K10. Clinical Psychologist Dr Peter Baldwin takes us through how self-report questionnaires work, how to choose a questionnaire, and how to quickly and effectively interpret the scores. He also busts some common myths about mental health questionnaires and share insights from his research and clinical practice.Peter is joined by Dale Skinner, who lives with bipolar II. Dale is determined to provide a better understanding of mood disorders and in this webinar will share his own experience of navigating self-report questionnaires. Panel:Dr Peter Baldwin, academic clinical psychologistDale Skinner, who lives with bipolar II Moderated by: Dr Phoebe Holdenson-KimuraAccess resources from this podcast here: https://d34ery7y7ckzql.cloudfront.net/3cb2dc2e-f580-4584-973a-0f95f04b43ff/Public/Resources/Webinar%2065%20Resources.pdf?448

Fundada em 2009, a Kapitalo é uma gestora de recursos que adota o modelo multi-gestor e multi-estratégias. A gestora possui, ao todo, 12 núcleos independentes e atua com estratégias em Multimercados e Ações. Juros, Câmbio, Ações e Commodities? Brasil ou Mundo? A resposta para estas questões e uma análise sobre o atual cenário doméstico e mundial é feita por Bruno Cordeiro, sócio da gestora Kapitalo, e responsável pela gestão do fundo K10 da casa.Assista ao episódio em vídeo: https://www.youtube.com/watch?v=NHW83SDGR50Investir com a XP Investimentos é fácil, basta criar o seu cadastro e em minutos você já pode começar a investir: http://bit.ly/41SHHkA Acompanhe todos os conteúdos da XP em https://t2m.io/ZAqGh0uParticipe do canal do Telegram para estar sempre atualizado: https://t.me/xp_investimentosConfira mais conteúdos também através do nosso Instagram: https://www.instagram.com/expertxp/

Infomaniak partage les valeurs de Tech Café : éthique, écologie et respect de la vie privée. Découvrez les services de notre partenaire sur Infomaniak.comAaaaah, l'IFA, pour celles & ceux qui ne connaissent pas, c'est un salon sur les produits tech qui a pu apporter son lot de rêve pour les technophiles que nous sommes. C'était il y a quelques années parce que, force est d'avouer que ces derniers temps, il n'y a plus l'excitation d'avant. Mais on a quand même fait le travail de vous restituer ce que la presse a identifié de remarquable : des smartphones peut-être ? De l'affichage ? Du son ? De la domotique ? Ou encore peut-être dans les nombreuses batteries qui ont été habilement mises en valeur par Julien, du blog ça-sert-a-quoi. ❤️ Patreon

In this episode, Fk and jollz have a chat with Koye Kekere Ekun also known as K10 . A lawyer, an actor and a man of many talents. He takes us through his many experiences, having to make tough career choices and living life as a creative.Listen to the full episode for all the tea!. Make sure you rate, share and leave a comment wherever you listen to the podcast telling us how much you enjoyed the episode!. Better Ratings mean even more people find out about the podcast!.Don't forget to use the hashtag ISWISPodcast to let us know what you think of the episode, we love hearing from you!.Follow us on Instagram @isaidwhatisaidpodPlease check out the Link for flutterwave Flutterwave.com Hosted on Acast. See acast.com/privacy for more information.

Bret and Matt welcome Michael Cade, the field CTO at Kasten by Veeam. If you've been around servers for a while, you probably have heard of Veeam. It made its debut back in the late 2000's when virtual machines and implementations of VMs were big. I first found out about them back in those days, because it was a great free product for small virtual machine environments and data centers. They've made tons of additional backup and recovery products over those years, and now they have Kasten K10, which is a Kubernetes backup and restore/recovery product. Michael discussed with us the origins of K10 and some of the major features. We get into some demos, which you can check out in the original YouTube live show. Live recording of the complete show from June 1, 2023 is on YouTube (Ep. #219). Includes demos.★Topics★Kasten K10 websiteK10 free for 5 nodesKanisterKasten K10 Walkthough Project on GitHubKasten K10 install configKastenByVeeam YouTube channel Support this show and get exclusive benefits on Patreon, YouTube, or bretfisher.com!★Join my Community★Get on the waitlist for my next live course on CI automation and gitops deploymentsBest coupons for my Docker and Kubernetes coursesChat with us and fellow students on our Discord Server DevOps FansGrab some merch at Bret's Loot BoxHomepage bretfisher.comCreators & Guests Bret Fisher - Host Cristi Cotovan - Editor Beth Fisher - Producer Matt Williams - Host Michael Cade - Guest (00:00) - Intro (02:23) - Introducing Michael Cade (03:30) - Veeam: then and now (07:38) - How Kasten came to be (14:11) - Complexity and Recovery (19:04) - Backup litmus test (23:02) - Demo (24:26) - Navig8: an open source visualizer for Helm Chart (28:44) - Kanister: an open source project for data management on Kubernetes (31:39) - Incremental backups (36:44) - Label-based backup policies (41:39) - Location profiles (43:56) - Infrastructure profiles (49:52) - Integrate your backup into you GitOps pipeline (51:43) - What about security? (54:57) - Getting started (01:02:13) - Miami conference

Michael Cade, Veeam Global Field CTO for Cloud Native Solutions, joins us to discuss containers, Kubernetes and K10 by Kasten. We cover why partners should be interested in this conversation, and who you should be talking to when prospecting. Some good advice around getting started in the world of K8s is shared as well.

Los bancos centrales robaron el futuro de una generación con los tipos de interés al 0. El dinero no tuvo un coste temporal y esto estimuló el consumo, olvidando el ahorro y la inversión para el día de mañana. Nos reímos pero la situación es dramática. Manel Berga, que es es pesimista con los políticos y los reguladores y optimista con la creatividad en el mercado, se protege comprando oro y desarrollando capital humano. El capitalismo es avaricia y cambio constante. Con mención especial a Gordon Gekko.Kapital Temporada 1:K10. Manel Berga. El padre rico de Kiyosaki.Índice:0.32. Rosling era optimista con el futuro del planeta.8.08. ¿Por qué fijar el precio en el 2%?19.31. Halcones, palomas, toros, osos... y el búho de Atenea.24.36. El confuso mandato del Banco Central Europeo.44.13. Nos robaron el futuro con los tipos a 0.1.03.25. El burbujómetro de Manel.1.11.18. Con inflación toda deuda es más barata.1.23.07. Se encienden las luces de la discoteca.1.42.58. Tu productividad viene condicionada por tu entorno.2.07.32. El tronco del brócoli es mejor indicador que el IPC.2.12.23. ¿Qué hago para salir adelante?Apuntes:Monetary policy. European Central Bank.Factfulness. Hans Rosling.60 minutes. Christine Lagarde.The pretense of knowledge. Friedrich von Hayek.Wall Street. Oliver Stone.Padre rico, padre pobre. Robert Kiyosaki.El hombre más rico de Babilonia. George S. Clason.El fundador. John Lee Hancock.Civilization. Niall Ferguson.El cisne negro. Nassim Nicholas Taleb.

I'm joined by James Douma and guests K10, Matt Smith and Nicolas Gibbs, as we watch Tesla's FSD presentation (part 1) at Tesla AI Day 2 and ask questions. Jump to 2:09:41 to hear summary thoughts from guests James Douma on Twitter, https://twitter.com/jamesdouma James Douma on AI playlist, https://www.youtube.com/playlist?list=PLfibpgBinf9R7KIedEU3y-YjrA63LSKHX K10 on Twitter: https://twitter.com/Kristennetten Matt Smith on Twitter: https://twitter.com/MatchasmMatt Nicolas Gibbs, Investing Against the Grain: https://www.youtube.com/channel/UC3K6_4IDtnBekVuWuH91uSg Full Tesla AI Day presentation: https://www.youtube.com/watch?v=ODSJsviD_SU Social

1. पुणे में लॉन्‍च हुई भारत की पहली हाइड्रोजन और हवा से चलने वाली बस2. Sony ने लांच किया नया Soundbar3. अब चैट लिस्ट में स्टेटस दिखाएगा वॉट्सऐप4. ऑल्टो K10 लॉन्च, कीमत 3.99 लाख रुपए5. OnePlus के फ्लैगशिप स्मार्टफोन की कीमत में भारी कटौती6. Android Smartphone में Software Update कैसे करें? जानें पूरा तरीकाSee omnystudio.com/listener for privacy information.

Rachel de Sá, chefe de economia da Rico, e Lucas Collazo, especialista em alocação e fundos, fazem uma analise sobre a recessão, juros, inflação e muito mais no Macro Pickers, com participação de Bruno Cordeiro, gestor e sócio do fundo K10 da Kapitalo.

Widely admired and a leader of the Tesla community, you might think you know Kristen aka K10 but yeah you probably don't :) K10 is more than just co-founder of Tesla Third Row, an OG FSD Beta Tester and early Tesla advocate...much much more! Follow K10 on Twitter: @kristennetten Follow me on Twitter: @teslaherbert Known as "the $TSLA Milestones Guy" join me as a 3 time startup founder with a product background to get to know the community better, highlight key $TSLA milestones that are coming next, and record the events as they happen. Timestamps: 00:00:00 What was 6 yo Kristen like? 00:04:10 What topics have you been studying the last 5 years? 00:07:30 Her love for rocks (geology)! 00:10:45 What was the first thing that blew your mind about Tesla? 00:12:28 Her relationship with Maye Musk 00:16:02 Why do you think Rome fell? 00:22:42 Is Elon a good storyteller? 00:24:31 Does Kristen get that she has a first row to history? 00:28:37 Do you think Elon's a genius? 00:33:00 Have you always been a positive person or is this recent? 00:35:46 When did you discover Tesla? 00:40:42 Third Row Tesla - the full story! 00:55:59 Herbert tells the story how he met Kristen at CyberRodeo 01:03:18 Kristen's impression of CyberRodeo 01:05:41 What do your friends think about your obsession with Tesla? 01:07:09 Kristen might start her own podcast! 01:08:40 Elon's purchase of Twitter 01:10:48 Master Plan Part 3 01:12:36 Will you be buying a Tesla Bot? 01:16:10 Kristen's new Model Y 01:17:46 How would you design a Robotaxi? 01:21:24 What will the world look like in 5 years? 01:22:29 Funversation questions If you like this content I would greatly appreciate your likes and shares! https://youtube.com/c/brighterherbert --- Support this podcast: https://podcasters.spotify.com/pod/show/brighter-tesla-herbert/support

Live from Valencia, it’s KubeCon EU! Craig talks to conference co-chair and CERN computer scientist Ricardo Rocha about the event, and what it’s like to be in a room full of people again. Do you have something cool to share? Some questions? Let us know: web: kubernetespodcast.com mail: kubernetespodcast@google.com twitter: @kubernetespod Chatter of the week 9am Karaoke News of the week CNCF news from KubeCon EU: SlashData survey 800 members Boeing Coinbase Prometheus Certified Associate Google Cloud improves GitOps usability with Config Sync and Porch kpt Other Google news from KubeCon Tetragon from Isovalent Envoy Gateway Infra Ask HN with the creators Cloud Foundry launches Korifi SUSE NeuVector is open source CloudNativePG from EnterpriseDB All the other options Assured Open Source Software from Google Cloud Recent Guest news: Akuity announces $20m Series A (episode 172) Komodor raises $42 million Series B (episode 153) Deepfence launches Deepfence Cloud (episode 173) Lightning Round Armory announced public early access to their new Continuous Deployment-as-a-Service product Aserto announces its ”better together” approach to authorization by bringing together OPA, OCI, and Sigstore Bunnyshell Introduces support for multi-repository Terraform with full-stack drift management and GitOps Calyptia announces the General Availability of Calyptia for Fluent Bit, CAST AI introduces advanced Autoscaler for AKS Clastix launches Kamaji, a new open source tool for Managed Kubernetes Service CloudCasa by Catalogic expands to support Microosft AKS Codenotary combines Community Attestation Service with background vulnerability scanning CodeZero Launches Surf, a new developer tool for observability in pre-production Kubernetes environments CrateDB introduces Logical Replication D2iQ Partners with GitLab DataCore Bolt container-native storage software now GA; built on their acquisition of Mayadata Datadog launches Application Security Monitoring and support for OpenTelemetry Protocol in the Datadog Agent, Deepfactor partners with Synopsys to help developers resolve cloud native supply chain security risks env0 enables full-stack IaC deployment and management with native Kubernetes support Era Software introduces EraStreams Fairwinds Insights unifies DevSecOps with additional shift-left enhancements GitLab free tier adds pull-based Kubernetes deployments Google announced a new low-cost, high-usage pricing tier for Google Cloud Managed Service for Prometheus HCL Technologies launches Kubernetes migration platform Kasten by Veeam launches K10 v5.0 released Runecast adds CI/CD integration and image scanning Lacework introduces new Kubernetes Audit Logs monitoring Loft Labs announces a Cluster API provider for vcluster NetFoundry embeds zero trust into Prometheus New Relic introduces low-overhead Kubernetes monitoring and Pixie plug-in framework Pure Storage’s new Database as a Service platform is GA Replicated introduces community licensing and pre-flight checks SphereEx releases DB-Plus Suite Snapt announces security package to run Kubernetes in public cloud SPIRE now runs on Windows Sysdig launches new Advisor and Sysdig Open Source leverages Falco plugins SysEleven unveils MetaKube Operator Timescale announces OpenTelemetry Tracing support for Promscale Vultr Kubernetes Engine now Generally Available Zesty Disk for Kubernetes introduced Links from the interview Episode 62 Lukas Heinrich Clemens Lange CERN LHC Computing Grid Large Hadron Collider Kubeflow Data on Kubernetes Community CNCF Research User Group CNCF TOC Volcano moves to incubation KubeCon EU 2022 Episode 165, with Jasmine James Selection process report for KubeCon EU KubeCon China 2021 Research track Puppies at KubeCon NA 2019 Code, mountains and flying Kubernetes on an F/16 Ricardo Rocha on Twitter and on the web

Diversity Matters with Oscar Holmes IV Season 3 Episode 1 Episode Title: The Standardized Testing Problem Guest: Mr. Akil Bello   Diversity Matters with Oscar Holmes IV is a podcast that explores all things diversity, equity, and inclusion (DEI) related. In each episode, Oscar and his guests have lively discussions around DEI topics, explore the latest research on the topic, and discuss the implications so that listeners will be more knowledgeable about the topics and be able to apply the insights to their lives.   Show Summary: “Even if the score has improved, it's the same kid; it's the same person with almost the same knowledge.”   Test or exam preparation is what students go through to increase their performance on standardized tests, usually for college university admissions. While the fair test is an advocacy organization that advocates for more limited, more reasonable & transparent use of standardized assessments, from K10 through 16. The movement supports the push not to administer standardized tests during a pandemic, to help students get better results on their exams.   As we all know, the test measures performance under intense pressure, influenced by some sampling of the things learned from K 10. Sadly, the test isn't decoupling one's actual knowledge and abilities from the secondary elements, which are time pressure & societal pressure. And that negatively affects someone's performance during the test.   That's why Mr. Akil Bello, an educator, entrepreneur, and testing expert, deep dives into why he is a big critic of the test preparation industry while being a test consultant & a fair test advocate at the same time. In this episode, he talks to us about the most significant issues with standardized testing, specifically for college university admissions. And he shares what institutions can do in higher education to make admissions more equitable.   3 Exceptional Highlights:   If you isolated any particular part of basketball, let's say free throw shooting, would you use free throw statistics as the way to choose your NBA franchise? That's what essentially everyone who puts significant weight on the test is doing. All highly speeded high pressure, high stakes, standardized tests have something in common & that is there is a signal-to-noise ratio, which is unclear at best. And I would argue there's more noise than signal for many constituencies. Varsity blues is a representative of where we've reached in higher education. And it's part of the problem. Every day, families are doing variations of Varsity blues on different scales. Show Highlights:   How Mr. Akil Bello got into the test prep consulting industry   2:27 Mr. Akil Bello   My entry into test prep was motivated by poverty & supported by nepotism. As a poor college kid, I needed money. I was studying architecture, but I wanted a part-time gig. So I went to my aunt and asked her if she could help me out. She pointed me to the Princeton Review and told me to use her name, and I got a job. That led to a total of 17 years working with them.   You are known for calling elite, highly selective schools like Harvard and Stanford “highly rejective.” Can you explain why using this language and new framing is important to you?   19:13 Mr. Akil Bello   One of the biggest problems in education is conflating historical advantage and wealth with educational quality. Just like your casual use of the word elite right now, I never use the word elite because it yields the position of power and respect to these institutions.     You were an expert contributor on Netflix's Operation Varsity Blues, a documentary highlighting the elite college admissions scam. Please help us understand why and how something like this can occur.   28:31 Mr. Akil Bello   CAPITALISM and AMERICA. To me, the entire scam is interesting. Because you have families who have a disposable X, hundreds of 1000s of dollars, this was money available for bribes. This is disposable income that was somehow, rather than giving it to the child to invest or giving it to them in a trust fund, it was worth spending this money to get this particular university sticker on the back of your car.   Why should the general public care about not getting into their top-choice school or some highly rejective school they wanted to go to?   21:16 Mr. Akil Bello   Oh, they shouldn't care. I think that the Stanfords of the world command far too much attention and brand recognition. I think that far too much attention these places receive is the country club effect. It's the exclusion that creates the aura of "Oh, we want to join." And I think that that's the problem. And I would never join a country club.   What should we do in higher education to make admissions more equitable?    35:07 Mr. Akil Bello   Interrogate your policies for historical bias.   Are the policies and the requirements of my admissions process those that advantage students with wealth and access?   Is it a necessary component of the process that helps select the most prepared students?   And I would argue that in most cases, these policies aren't.   Legacy admissions are problematic. How about we just get rid of that?   Important Links:     Call to Action: Subscribe to Diversity Matters and get exclusive access to all episodes of Beyond the Mill, which is my live diversity dialogues talk show that I host on campus at Rutgers University-Camden.   Episode Sponsor Links:     Producer Links:   Host Social Media Links:   Subscribe to Diversity Matters Apple | Google | Spotify | Stitcher  

In India, we believe that teachers are superior to God. Teachers help children grow and thus help in building the nation. But due to some of the obsolete methods and inefficiencies in the Education System, the mental level of the students are falling collectively. To fight this situation, our guest for today Dr. Trishta Ramamurthy founded The Ekya Schools in 2010. The Ekya Schools is a chain of dynamic schools designed with the aim of bringing pedagogically sound researched-based learning experiences to India. Dr. Trishta spearheads K10 and K12 initiatives under the CMR Group. She brings cutting-edge educational advancements to Ekya Schools from her experiences of exposure to the principles of Project Zero Classroom from Harvard University, inquiry-based learning from the Regio Avila approach from Italy and design thinking from the Standard Design School. --- Support this podcast: https://anchor.fm/tbcy/support

In this episode, Fk and jollz have a chat with  Koye Kekere Ekun also known as K10 . A lawyer, an actor and a man of many talents. He takes us through his many  experiences, having to make tough career choices and living life as a creative.Listen to the full episode for all the tea!. Make sure you rate, share and leave a comment wherever you listen to the podcast telling us how much you enjoyed the episode!. Better Ratings mean even more people find out about the podcast!.Don't forget to use the hashtag ISWISPodcast to let us know what you think of the episode, we love hearing from you!.Follow us on Instagram @isaidwhatisaidpodPlease check out the Showmax linkhttps://bit.ly/3xk3wZQPlease check out the Link for flutterwave Flutterwave.com

Naš gost v nedeljski kmetijski oddaji je bil Stanko Tomšič, direktor kmetijske zadruge Trebnje-Krka, ki je minuli teden postal tudi direktor Zadružnega gospodarsko interesnega združenja K10+.

A analista de fundos Juliana Machado recebe Bruno Cordeiro, sócio da Kapitalo Investimentos e gestor do fundo K10, para uma conversa sobre como esse multimercado livre se aproveita dos ciclos de commodities para obter rentabilidade e quais os maiores desafios de operar com matérias-primas no mercado financeiro. O gestor também explica qual a tese do K10 ao longo de 2021 e o que mudou no posicionamento do fundo para o último trimestre deste ano.

This week I caught up with Mitch Johnsen, he is up in sunny QLD building a 1972 K10 Longbed pickup. The K10 is a rare beast here in Australia and Mitch is giving it a well-deserved rebirth. Have a listen and hear the history of this project, and the progress so far. You can check out Mitch's work via his instagram, @chevy.k10   The podcast is sponsored in part by Classic Pickup Supplies. Please support them if you need parts for US build Ford and Chevy vehicles. www.classicpickupsupplies.com.au Please consider supporting the podcast with a monthly donation, via our Patreon page https://www.patreon.com/classicpickuppodcast To get in contact with me please email me at classicpickuppodcast@gmail.com Thank you for listening. Whipps.

Discussing the latest version of FSD after 5 days of testing w/ FSD Beta testers: John, K10, Earl, Kim, Eli, Brandon, Chuck, Raj, and Rafael. Download the Callin app for iOS and Android to listen to this podcast live, call in, and more! Also available at callin.com

"The Airin' It Out Podcast" welcomes back K10 to the show for a third visit to chat about EV company Tesla and its founder, billionaire space cowboy Elon Musk. She and  Dustin discuss Tesla's morphing crypto policies, Musk's recent SNL appearance, and our shift away from fossil fuels. Finally she'll break down new social media platform "Clubhouse" and discuss where online industry is heading. Looking for more?Airin It Out Live - YouTube ChannelFollow KristenTwitter - K10Podcast -The Third Row Tesla PodcastFollow DustinTwitter - The Airin It Out PodcastInstagram - The Airin It Out PodcastTik Tok - The Airin It Out PodcastIf you enjoyed the show, and are think about starting a podcast. You would like to signup using my reference code you will receive a  $20 Amazon gift card if you sign up for a paid plan. You will be able to purchase some equipment like, SD cards, XLR cables for your mics and helps support the show.The Show Code: www.buzzsprout.com/?referrer_id=821557I uses Buzzspout and it's amazing. Buzzsprout helps me gets my show listed in every major podcast platform. The team at Buzzsprout is passionate about helping you succeed. Join over a hundred thousand podcasters already using Buzzsprout to get their message out to the world. Podcasting isn't hard when you have the right partners. You'll get a great looking podcast website, audio players that you can drop into other websites, detailed analytics to see how people are listening, tools to promote your episodes, and more. If you want to upgrade, Buzzsprout has tons of guides to help you find the right equipment at the right price.

Lass uns gemeinsam beten!

Thank you to K10 and Brooks of Drag Times for joining us on the Tesla Geeks show. #Tesla​ #TSLA​ #TeslaEarnings​K10:https://twitter.com/Kristennetten​Drag Times: https://www.youtube.com/user/DragTimes

This is a special podcast where my friend, Kristen, known as K10 in the Tesla Twitter community, and I talk about gems and minerals. She shared her love of diamonds and how her grandfather used to take her rockhounding. You can support Kriston on Patreon here and follow her on Twitter here.

On this episode Laila sits with the very talented and very funny K10. Listen and Enjoy

Boy oh boy is this an overpacked podcast. In this episode I try to talk about too many things to come up with a good title. I jump from talking about the Redcat Kaiju and Gen8 V2, to winning monster truck races, then racing 2wd buggy at Coastal RC, the end of RC Conspiracies as we know it, the RC Amigos Sleigh Smash, and new products from JConcepts.  Here are links I said I'd give in the episode.   Visit Bitgo Hobby: https://bit.ly/bitgohobbyRedcat Gen8 V2: https://bit.ly/Gen8V2Redcat Kaiju: https://bit.ly/RC-Kaiju  RC Amigos Instagram: https://www.instagram.com/rc_amigos/  Coastal RC Indoor Speedway: https://coastalrcspeedway.com/TRL 22 5.0 AC 2WD Buggy: https://bit.ly/TLR22-5ACLosi LMT RTR Grave Digger or Son-uva Digger:  https://bit.ly/LosiLMT  JCONCEPTS USA-1 BuildUSA-1 K10 edition body: https://bit.ly/1970USA-1Rollbar: https://bit.ly/USA1-RollbarLightbar: https://bit.ly/USA1-lightbarRegulator Axles: https://bit.ly/Regulator-AxlesRegulator Chassis: https://bit.ly/JC_RegulatorRegulator BTA Steering: https://bit.ly/JC_ServoMt  

Link to bioRxiv paper: http://biorxiv.org/cgi/content/short/2020.11.19.390336v1?rss=1 Authors: Jamieson, D., McLoughlin, L. T., Beaudequin, D. A., Shan, Z., Boyes, A., Schwenn, P., Lagopoulos, J., Hermens, D. F. Abstract: Background: Adolescence is an important period for developing ones sense of self. Social connectedness has been linked to a sense of self which in turn has links to resilience in mental disorders. Adolescence is also a period of increased risk of chronic sleep deprivation during a time of ongoing white matter (WM) maturation. The complex relationship between these variables and their relationship with the onset on mental disorders during adolescence remains largely unexplored. Methods: N = 64 participants aged 12 years (M = 12.6) completed the Pittsburgh Sleep Quality Index (PSQI), Social connectedness scale (SCS) and a diffusion weighted Magnetic Resonance Imaging (MRI) scan to investigate the relationship of these variables to predict psychological distress via the Kessler psychological distress scale (K10) in early adolescents. Multiple regression analysis was used with K10 entered as the dependent variable and SCS, PSQI, and values of white matter integrity as the predictor variables. Results: Results showed that while all four variables collectively accounted for a significant proportion of the variance in K10 (41.1%), SCS and PSQI were the only predictors that accounted for a significant proportion of variance uniquely. Conclusions: These findings suggest interventions aimed at increasing levels of social connectedness and sleep quality during adolescence may reduce psychological distress. Future longitudinal reporting of this combination of variables is suggested. Copy rights belong to original authors. Visit the link for more info

Continuación de las noticias desde finales de agosto, en este caso las terrestres y de drones. Recordad que tenemos abierto un Patreon para apoyar el crecimiento de la comunidad: https://www.patreon.com/portierramaryaire. Tras el corte, el guión y minutado: NoticiaPosición4utube La Infantería de Marina de los EE.UU. le otorga un contrato a Kongsberg para estaciones de armas remotas XM9140:00:0-16 La adquisición por parte de Pakistán del nuevo carro de origen chino VT4 se confirmó ayer desde la Agencia de Prensa de Pakistán0:11:32 Futuro AS-9 australiano basado en el K9 thunder0:15:55 Sabra light ofertado para Filipinas0:20:12 Noruega recibió doce obuses K9 de 155 mm y tres vehículos de suministro K10 la semana pasada0:26:10 El Ministerio de las Fuerzas Armadas francesas encarga un segundo lote de tanques Griffon y Jaguar0:27:15 El Ministerio de Defensa polaco ha firmado un contrato para 60 vehículos de la serie Rosomak-S 8x8 por un costo de más de 28 millones de dólares. Están diseñados para llevar #SPIKE #ATGMs.0:36:59 El Patria AMVXP ha sido seleccionado para la segunda fase del programa de adquisición de vehículos para el ejercito búlgaro0:43:01 El contrato del 8x8 blinda a la industria militar española 0:46:37 La nueva generación de vehículos de combate rusos Kurganets-25 retrasado indefinidamente0:59:59 El Ministerio de Defensa de Polonia confirmó que el primer lote de 3 #Leopard2PL #MBT modernizados fue entregado a la 1ª Brigada Blindada de Varsovia, elemento de la 18ª División Mecanizada.1:02:57 todos los tanques rusos T-72 se actualizarán al nivel T-72B3M1:06:02 Russian Army start receive the upgraded BMP-1AM.1:11:07 Rumores sobre la retirada parcial o incluso total del Challenger II Británico1:18:38 Haenel gana el concurso alemán de sustitución del G-361:26:42 H&K prepara acciones judiciales vs. la elección del Haenel MK5561:41:02 Guardia Civil compra MP51:42:57 Northrop Grumman XM913 de 50mm para los futuros IFV del US Army1:50:17 Se comprarán hasta 700 VAMTAC a Urovesa1:59:13 Merkavás encontrados sin vigilancia por excursionistas en el Golán2:01:00 La empresa alemana Flensburger Fahrzeugbau Gesellschaft (FFG), ha presentado su nuevo demostrador de tecnología de vehículos blindados 8x8 llamado Genesis, equipado con un sistema de propulsión diésel-eléctrico totalmente híbrido.2:03:06 Tactical Airborne Laser Pod de LM https://www.flightglobal.com/fixed-wing/lockheed-martin-aims-to-put-laser-weapon-on-aircraft-in-five-years/140204.article2:10:20 Turquía entregó en pleno conflicto a Azerbaijan 6 drones Bayraktar TB2.2:17:31 Las unidades de ingenieros rusas recibirán sistemas robóticos Uran-142:30:33 GDLS muestra un nuevo chasis con orugas para un robot militar de 10 toneladas2:40:57 Tarnów Mechanical Plant ZMT, está llevando a cabo pruebas de campo del vehículo autónomo de reconocimiento y combate Perun2:44:09 Países Bajos y Estonia compran juntos 4 y 3 UGV Milrem TheMis respectivamente2:53:27 India podría adquirir 30 MQ-9B por 3.000 millones de dólares.2:58:22 Empiezan a presentar propuestas para sustituto del Predator/Reaper para 20303:01:03 Bonita foto de F-5 y Predator B lado a lado en Talavera:3:07:21 Turkish UAV Aksungur flies 28 hours with 12 mini smart munitions3:08:56 SENER desarrolla j pod para el Predator/Reaper y un demostrador COMINT para drones tipo MALE3:14:08 La Guardia Civil recibirá 30 RPAS por 84k y 25 sistemas antidrón por 400k, los dos para despliegues3:14:37 GA-ASI presenta el SparrowHawk, el UAV del UAV3:21:35 Primer vuelo del Protector inglés, SkyGuardian3:23:27 Georgia recibió el primer lote de drones de reconocimiento españoles, ala fija y helicóptero. 3:26:13 Obvio: Lockheed propone un abanico de drones, y no uno único, para cubrir el programa "NQ-Next", 3:30:55 Entrevista con el capitán Redondo y la sargento Sandra Huerta, piloto y operadora de sensores de Predator B 3:33:15 La USAF inicia la fase 2 de su programa "Skyborg", 3:35:30 La USAF dobla la capacidad de carga de misiles Hellfire del Reaper, hasta 83:44:41 El USArmy demuestra la coordinación entre no tripulados ("Unmanned-Unmanned Teaming, UUT") 3:45:40 Aerovironment desvela una versión de su drón suicida (loitering) Switchblade, la versión 600, contrablindados:3:58:10 el orbiter 1k. 75K por disparo. está muy bien:4:01:22 VUQ-10 primer escuadrón de la US Navy para operar el MQ-25 Stingray4:05:14 Haciendo de abogado del diablo: 4:14:26 Japón desarrollará un drón acompañante (loyal wingman) para su futuro caza F-X4:25:11 Boeing Australia nos recuerda que el ATS (Air Teaming System), 4:28:10 Ya ha empezado la feria de drones española UNVEX online4:30:58

In today's podcast, Jeremy & Matt discuss the meanings of all of the weight ratings on that door sticker of your vehicle. Gross Vehicle Weight Ratings (GVRW), Payload, Curb Weight, etc. They also discuss what a disaster GM squarebody truck names became in the late 1980's. C10, C1500, K25, R20, V30, Half ton, 1 ton. What is all this stuff?! Why did general motors do this to us? They wrap up with a listener question that questions that best way to improve your MPGs.  Is it better to swap your engine? Transmission?  Or add some kind of forced induction like a turbo or supercharger?   Listen to this fantastic Engine Noise Podcast episode to learn more!

Episode #185 is brought to you by these Rad Ass Sponsors.  www.dakotadigital.com - Upgrade that interior with the best gauges around, Dakota Digital offers multiple options for you and your build.  www.vintageair.com - Your AC, if you have it is 40 years old! Vintage Air offers modern tech with a retro look - the obvious choice is Vintage Air. psiconversion.com/c10talk - When you are ready to upgrade that power plant to an LS or LT based motor, PSI Conversion has EVERYTHING you need. Use "C10 Talk" at check out and save 5% off your order.  www.classicperform.com - New X10 Spindles, Coil Over Set up, Big Brakes, Fuel cells, you name it, CPP has what you need for your build. Use "C10 Talk" at check out and save 10% off your total order.  Greg Ingold is the Associate Editor of the Hagerty Price Guide. Greg and his team work hard at setting a baseline for what classic cars and trucks are worth. So I reached out and we chatted about how they come up with their values and of course how much are beloved C10's/K10's/K5's and many other are worth. Whats Next? What is a car or truck that has come out of now where? And many more.  Enjoy C10 Nation, and please remember to share, subscribe, and rate the podcast. Ronnie

Dr Ben Buchanan is a psychologist and Co-founder & Director of NovoPsych, an Australian healthtech company providing software for administering psychological, remote and online questionnaires to patients. As a trained clinical psychologist, Ben is passionate about clinicians evaluating their own practice through the use of routine outcome monitoring, which is why he created NovoPsych. In this episode, Ben explains why outcome measurements should focus on Australian requirements, and how the recent and sudden transformation towards telehealth can be easily adapted to using NovoPsych. Ben provides some guidance on what a telehealth workflow could look like, and how to implement automation with remote symptom monitoring of patients between visits or after treatment.   Key takeaways: In Australia, one of the most widely used assessments to measure mental health outcomes is called the K10 — also known as the ‘Kessler Psychological Distress Scale’. Australia regulations of mental health practitioners require some outcome monitoring to occur. NovoPsych has been tailored to fit the exact purpose that Australian mental health conditions need. Healthcare is a service industry, in which it’s just as important to provide a service that the client is happy with as it is to improve clinical outcomes. One of the number one predictors of treatment success for mental health patients is the ‘therapeutic alliance’, i.e. the relationship between the psychologist and the client. If the client trusts the psychologist then that is a serious predictor of later outcomes. Practitioners often have to rely on their intuition to get a sense about whether the client is benefitting from the treatment. However, the research evidence shows that trained professionals are terrible at using intuition to accurately measure how their clients are going. Within NovoPsych there are therapeutic alliance measures that can tell the psychologist from the get-go whether they're reaching their client or not, so adjustments can be made in the early stages of treatment.   Resources and links: https://novopsych.com.au/   Connect: Listen to other episodes of Reimagining Healthcare Connect with Yianni Serpanos on LinkedIn Follow HealthTechX on LinkedIn Follow HealthTechX on Instagram Follow HealthTechX on Meetup

Off Road Design has been a stalwart in the full-size wheeling scene for decades and owner and Truck Show listener Stephen Watson tells the story from startup to trusted off-road expert in GM trucks. Holman shares his recent misadventures on Craigslist and the guys catch up on your 5-star Hotline calls to find out if Canadian bacon is more American than Canadian and get schooled on the difference between a bull and a steer.

In this episode of The Podlets Podcast, we are talking about the very important topic of recovery from a disaster! A disaster can take many forms, from errors in software and hardware to natural disasters and acts of God. That being said that are better and worse ways of preparing for and preventing the inevitable problems that arise with your data. The message here is that issues will arise but through careful precaution and the right kind of infrastructure, the damage to your business can be minimal. We discuss some of the different ways that people are backing things up to suit their individual needs, recovery time objectives and recovery point objectives, what high availability can offer your system and more! The team offers a bunch of great safety tips to keep things from falling through the cracks and we get into keeping things simple avoiding too much mutation of infrastructure and why testing your backups can make all the difference. We naturally look at this question with an added focus on Kubernetes and go through a few tools that are currently available. So for anyone wanting to ensure safe data and a safe business, this episode is for you! Follow us: https://twitter.com/thepodlets Website: https://thepodlets.io Feeback: info@thepodlets.io https://github.com/vmware-tanzu/thepodlets/issues Hosts: https://twitter.com/carlisiahttps://twitter.com/bryanlhttps://twitter.com/joshrossohttps://twitter.com/opowero Key Points From This Episode: • A little introduction to Olive and her background in engineering, architecture, and science. • Disaster recovery strategies and the portion of customers who are prepared.• What is a disaster? What is recovery? The fundamentals of the terms we are using.• The physicality of disasters; replication of storage for recovery.• The simplicity of recovery and keeping things manageable for safety.• What high availability offers in terms of failsafes and disaster avoidance.• Disaster recovery for Kubernetes; safety on declarative systems.• The state of the infrastructure and its interaction with good and bad code.• Mutating infrastructure and the complications in terms of recovery and recreation. • Plug-ins and tools for Kubertnetes such as Velero.• Fire drills, testing backups and validating your data before a disaster!• The future of backups and considering what disasters might look like. Quotes: “It is an exciting space, to see how different people are figuring out how to back up distributed systems in a reliable manner.” — @opowero [0:06:01] “I can assure you, careers and fortunes have been made on helping people get this right!” — @bryanl [0:07:31] “Things break all the time, it is how that affects you and how quickly you can recover.” —@opowero [0:23:57] “We do everything through the Kubernetes API, that's one reason why we can do selectivebackups and restores.” — @carlisia [0:32:41] Links Mentioned in Today’s Episode: The Podlets — https://thepodlets.io/The Podlets on Twitter — https://twitter.com/thepodletsVMware — https://www.vmware.com/Olive Power — https://uk.linkedin.com/in/olive-power-488870138Kubernetes — https://kubernetes.io/PostgreSQL — https://www.postgresql.org/AWS — https://aws.amazon.com/Azure — https://azure.microsoft.com/Google Cloud — https://cloud.google.com/Digital Ocean — https://www.digitalocean.com/SoftLayer — https://www.ibm.com/cloudOracle — https://www.oracle.com/HackIT — https://hackit.org.uk/Red Hat — https://www.redhat.com/Velero — https://blog.kubernauts.io/backup-and-restore-of-kubernetes-applications-using- heptios-velero-with-restic-and-rook-ceph-as-2e8df15b1487CockroachDB — https://www.cockroachlabs.com/Cloud Spanner — https://cloud.google.com/spanner/ Transcript: EPISODE 08[INTRODUCTION] [0:00:08.7] ANNOUNCER: Welcome to The Podlets Podcast, a weekly show that explores Cloud Native one buzzword at a time. Each week, experts in the field will discuss and contrast distributed systems concepts, practices, tradeoffs and lessons learned to help you on your cloud native journey. This space moves fast and we shouldn’t reinvent the wheel. If you’re an engineer, operator or technically minded decision maker, this podcast is for you. [EPISODE] [00:00:41] CC: Hi, everybody. We are back. This is episode number 8. Today we have on the show myself, Carlisia Campos and Josh. [00:00:51] JR: Hello, everyone. [00:00:52] CC: That was Josh Rosso. And Olive Power. [00:00:55] OP: Hello. [00:00:57] CC: And also Brian Lyles. [00:00:59] BL: Hello. [00:00:59] CC: Olive, this is your first time, and I didn’t even give you a heads-up. But tell us a little bit about your background. [00:01:06] OP: Yeah, sure. I’m based in the UK. I joined VMware as part of the Heptio acquisition, which I joined Heptio way back last year in October. The acquisition happened pretty quickly for me. Before that, I was at Red Hat working on some of their cloud management tooling and a bit of OpenShift as well. Before that, I worked with HP and Fujitsu. I kind of work in enterprise management a lot, so things like desired state and automation are kind of things that have followed me around through most of my career. Coming in here to VMware, working in the cloud native applications business unit is kind of a good fit for me. I’m a mom of two and I’m based in the UK, which I have to point out, currently undergoing a heat wave. We’ve had about like 3 weeks of 25 to 30 degrees, which is warm, very warm for us. Everybody is in a great mood. [00:01:54] CC: You have a science background, right? [00:01:57] OP: Yeah, I studied chemistry in university and then I went on to do a PhD in cancer research. I was trying to figure out ways where we could predict how different people will going to respond to radiation treatments and then with a view to tailoring everybody’s treatment to make it unique for them rather than giving the same treatment to different who present you with the same disease but were response very, very different. Yeah, that was really, really interesting. [00:02:22] CC: What is your role at VMware? [00:02:23] OP: I’m a cloud native architect. I help customers predominantly focus on their Kubernetes platforms and how to build them either from scratch or help them get more production-ready depending on where they are in their Kubernetes journey. It’s been really exciting part of being part of Heptio and following through into the VMware acquisition. We’re going to speak to customers a lot at very exciting times for them. They’re kind of embarking on their Kubernetes journey a lot of them. We’re with them from the start and every step of the way. That’s really rewarding and exciting. [00:02:54] CC: Let me pick up on that thread actually, because one thing that I love about this group for me, because I don’t get to do that. You all meet customers and you know what they are doing. Get that knowledge first-hand. What would you say the percentage of the clients that you see, how disaster recovery strategy, which by the way is a topic of today’s show. [00:03:19] OP: I speak to customers a lot. As I mentioned earlier, a lot of them are like in different stages of their journey in terms of automation, in terms of infrastructure of code, in terms of where they want to go for their next platform. But there generally in the room a team that is responsible for backup and recovery, and that’s generally sort of leads into this storage team really because you’re trying to backup state predominantly. When we’re speaking to customers, we’ll have the automation people in the room. We’ll have the developers in the room and we’ll have the storage people in the room, and they are the ones that are primarily – Out of those three sort of folks I’ve mentioned, they’re the ones that are primarily concerned about backup. How to back up their data. How to restore it in a way that satisfies the SLAs or the time to get your systems back online in a timely manner. They are the force concerned with that. [00:04:10] JR: I think it’s interesting, because it’s almost scary how many of our customers don’t actually have a disaster recovery strategy of any sort. I think it’s often times just based on the maturity of the platform. A lot of the applications and such, they’re worried about downtime, but not necessarily like it’s going to devastate the business in a lot of these apps. I’m not trying to say that people don’t run mission critical apps on things like Kubernetes. It’s just a lot of people are very new and they’re just kind of ramping up. It’s a really complicated thing that we work with our customers on, and there’re so many like layers to this. I’m sure layers that we’ll get into. There are things like disaster recovery of the actual platform. If Kubernetes, as an example, goes down. Getting it back up, backing up its data store that we call etcd. There’s obviously like the applications disaster recovery. If a cluster of some sort goes own, be it Kubernetes or otherwise, shifting some CI system and redeploying that into some B cluster to bring it back up. Then to Olive’s point, what she said, it all comes back to storage. Yeah. I mean, that’s where it gets extremely complicated. Well, at least in my mind, it’s complicated for me, I should say. When you’re thinking about, “Okay, I’m running this PostgreS as a service thing on this cluster.” It’s not that simple to just move the app from cluster A to cluster B anymore. I have to consider what do I do with the data? How do I make sure I don’t lose it out? Then that’s a pretty complicated question to answer. [00:05:32] OP: I think a lot of the storage providers, vendors playing in that storage space are kind of looking at novel ways to solve that and have adapted their current thinking maybe that was maybe slightly older thinking to new ways of interacting with Kubernetes cluster to provide that ongoing replication of data around different systems outside of the Kubernetes and then allowing it to be ported back in when a Kubernetes cluster – If we’re talking about Kubernetes in this instance as a platform, porting that data back in. There’re a lot of vendors playing in that space. It’s kind of an exciting space really to see how different people are figuring out how to back up distributed systems in reliable manner, because different people want different levels of backup. Because of the microservices nature of the cloud native architectures that we predominantly deal with, your application is not just one thing anymore. Certain parts of that application need to be recovered fairly quickly, and other parts don’t need to recover that quickly. It’s all about functionality ultimately that your end customers or your end users see. If you think about visually as like a banking application, for example, where if you’re looking at things like – The customer is interacting with that and they can check their financial details and they can check the current stages of their account, then they are two different services. But the actual service to transfer money into their account is down. It’s still a pretty functional system to the end user. But in the background, all those great systems are in place to recover that transfer of money functionality, but it’s not detrimental to your business if that’s down. There’ll be different SLAs and different objectives in terms of recovery, in terms of the amount of time that it takes for you to restore. All of that has to be factored in into disaster recovery plans and it’s up to the company and we can help as much as possible for them to figure out which feats of the applications and which feats of your business need to conform to certain SLAs in terms of recovery, because different feats will have different standards and different times in and around that space. It’s a complicated thing. It definite is. [00:07:29] BL: I want to take a step back and unpack this term, disaster recovery, because I can assure you, careers and fortunes have been made on helping people get this right. Before we get super deep into this, what’s a disaster and then what’s a recovery for that? Have you thought about that at a fundamental level? [00:07:45] OP: Just for me, if we would kind of take it at face value. A physical disaster, they could be physical ones or software-based ones. Physical ones can be like earthquakes or floodings, fires, things like that that are happening either in your region or can be fairly widespread across the area that you’re in, or software, cyber attacks that are perhaps to your own internal systems, like your system has been compromised. That’s fairly local to you. There are two different design strategies there. Physical disaster, you have to have a recover plan that is outside of that physical boundary that you can recover your system from somewhere that’s not affected by that physical disaster. For the recovery in terms of software in terms of your system has been compromised, then the recovery from that is different. I’m not an expert on cyber attacks and vulnerabilities, but the recovery from there for companies trying to recover from that, they plan for it as much as possible. So they down their systems and try and get patches and fixes to them as quickly as possible and spin the system backups. [00:08:49] BL: I’m understanding what you’re saying. I’m trying to unpack it for those of us listening who don’t really understand it. I’m going to go through what you said and we’ll unpack it a little bit. Physical from my assumption is we’re running workloads. Let’s say we’re just going to say in a cloud, not on-premise. We’re running workloads in let’s say AWS, and in the United States, we can take care local diversity by running in East and West regions. Also, we can take care of local diversity by running in availability, but they don’t reach it, because AWS is guaranteed that AZ1 and AZ3 have different network connections, are not in the same building, and things like that. Would you agree? Do you see that? I mean, this is for everyone out there. I’m going to go from super high-level down to more specific. [00:09:39] OP: I personally wouldn’t argue that, except not everybody is on AWS. [00:09:43] BL: Okay. AWS, or Azure, or Google Cloud, DigitalOcean, or SoftLayer, or Oracle, or Packet. If I thought about this, probably we could do 20 more. [00:09:55] JR: IBM. [00:09:56] BL: IBM. That’s why I said SoftLayer. They all practice in the physical diversity. They all have different regions that you can deploy software. Whether it’s be data locality, but also for data protection. If you’re thinking about creating a planet for this, this would be something you could think about. Where does my rest? What could happen to that data? Building could actually just fall over on to itself. All the hard drives are gone. What do I do? [00:10:21] OP: You’re saying that replication is a form of backup? [00:10:26] BL: I’m actually saying way more than that. Before you even think about things when it comes to disaster recovery, you got to define what a disaster is. Some applications can actually run out of multiple physical locations. Let’s go back to my AWS example, because it’s everywhere and everyone understands how AWS works at a high-level. Sometimes people are running things out of US-East-1 and US-West-2, and they could run both of the applications. The reason they can do that is because the individual transactions of whatever they’re doing don’t need to talk to one another. They connect just websites out of places. To your point, when you talk about now you have the issue where maybe you’re doing inventory management, because you have a large store and you’re running it out of multiple countries. You’re in the EU and you’re somewhere on APAC as well. What do you do about that? Well, there are a couple of ways that – I could think about how we would do that. We could actually just have all the database connections go back to one single main service. Then what we could do with that main service is that we could have it replicated in their local place and then we can replicate it in a remote place too. If the local place goes up, at least you can point all the other sites back to this one. That’s the simplest way. The reason I wanted to bring this up, is because I don’t like acronyms all that much, but disaster recovery has two of my favorite ones and they’re called RPO and RTO. Really, what it comes down to is you need to think about when you have a disaster, no matter that disaster is or how you define it, you have RTO. Basically, it’s the time that you can be down before there’s a huge issue. Then you have something called DPO, which is without going into all the names, is how far you can go since your last backup before you have business problems. Just thinking about those things is how we should think about our backup disaster recovery, and it’s all based on how your business works or how your project works and how long you can be down and how much data you have. [00:12:27] CC: Which goes to what Olive was saying. Please spell out to us what RTO and RPO stand for. [00:12:35] BL: I’m going to look them up real quick, because I literally pushed those acronym meanings out. I just know what they mean. [00:12:40] OP: I think it’s recovery time objective and recovery data objective. [00:12:45] BL: Yeah. I don’t know what the P stands for, but it is for data. [00:12:49] OP: Recovery. [00:12:51] BL: It’s the recovery points. Yeah. That’s what it is. It is the recovery point objective, RPO; and recovery time objective, RTO. You could tell that I’ve spent a lot of time in enterprise, because we don’t even define words. The acronym means what it is. Do you know what the acronym stands for anymore? [00:13:09] OP: How far back in terms of data can we go that was still okay? How far back in time can we be down, basically, until we’re okay? [00:13:17] CC: It is true though, and as Josh was saying, some teams or companies or products, especially companies that are starting their journey, their cloud native journey. They don’t have a backup, because there are many complicated things to deal with, and backup is super complicated, I mean, the disaster recovery strategy. Doing that is not trivial. But shouldn’t you start with that or at least because it is so complex? It’s funny to me when people say I don’t have that kind of a strategy. Maybe just like what Bryan said why utilizing, spreading out your data through regions, that is a strategy in itself, and there’s more to it. [00:14:00] JR: Yeah. I think I oversimplified too much. Disaster recovery could theoretically be anything I suppose. Going back to what you were saying, Brian, the recovery aspect of it. Recovery for some of the customers I work with is literally to stand on a brand-new cluster, whatever that cluster is, a cluster, that is their platform. Then redeploy all the applications on top of it. That is a recovery strategy. It might not be the most elegant and it might make assumptions about the apps that run on it, but it is a recovery strategy that somewhat simple, simple to kind of conceptualize and get started with. I think a lot of the customers that I work with when they’re first getting their bearings with distributed system of sorts, they’re a lot more concerned about solving for high availability, which is what you just said, Carlisia, where we’re spreading across maybe multiple sites. There’s the notion of different parts of the world, but there’s also the idea of like what I think Amazon has coined availability zones. Making sure if there is a disaster, you’re somewhat resilient to that disaster like Brian was saying with moving connections over and so on. Then once we’ve done high-availability somewhat well, depending on the workloads that are running, we might try to get a more fancy recovery solution in place. One that’s not just rebuild everything and redeploy, because the downtime might not be acceptable. [00:15:19] BL: I’m actually going to give some advice to all the people out there who might be listening to this and thinking about disaster recovery. First of all, all that complex stuff, that book you read, forget about it. Not because you don’t need to know. It’s because you should only think about what’s in scope at any given time. When you’re starting an application, let’s say I’m actually making a huge assumption that you’re using someone else’s cloud. You’re using public cloud. Whenever you’re in your data center, there’s a different problem. Whenever you’re using public cloud, think about what you already have. All the major public clouds had a durable object storage. Many 9s of durability and then fewer 9s, but still a lot of 9s of availability too. The canonical example there is S3. When you’re designing your applications and you know that you’re going to have disaster issues, realize that S3 is almost always going to be there, unless it was 2017 and it goes down, or the other two failures that it had. Pretty much, it will be there. Think about how do I get that data into S3. I’m just saying, you can use it for storage. It’s fairly cheap for how much storage you can get. You can make it sure it’s encrypted, and using IM, you can definitely make sure that people who have the right pillages can see it. The same goes with Azure and the same goes with Google. That’s the first phase. The second phase is that now you’re going to say, “Well, what is a relational database?” Once again, use your cloud provider. All the major cloud providers have great relational databases, and actually key value stores as well. The neat thing about them is you can actually set them up sometimes to run in a whole region. You can set them up to do automated backups. At least the minimum that you have, you actually use your cloud provider for what it’s valuable for. Now, you’re not using a cloud provider and you’re doing it on-premise, I’m going to tell you, the simple answer is I hope you have a little bit of money, because you’re going to have to pay somebody either one of Kubernetes architects or you’re going to pay somebody else to do it. There’s no easy button for this kind of solution. Just for this little mini-rant, I’m going to leave everyone with the biggest piece of advice, the best piece of advice that I can ever leave you if you’re running relational databases. If you are running a relational database, whether it’d be PostgreS, MySQL, Aurora, have it replicated. But here’s the kicker, have another replica that you delay and make it delay 10 minutes, 15 minutes, not much longer than that. Because what’s going to happen, especially in a young company, especially if you’re using Rails or something like that, you’re going to have somebody who is going to have access to production, because you’re a small company, you haven’t really federated this out yet. Who’s going to drop your main database table? They’re just going to do it and it’s going to happen and you’re going to panic. If you have it in a replica, that databases go in a replica, you have a 10-minute delay replica – 10 minutes to figure it out before the world ends. Hopefully someone deletes the master database. You’re going to know pretty quickly and you can just cut that replica out, pull that other one over. I’m not going to say where i learned this trick. We had to employ it multiple times, and it saves our butts multiple times. That’s my favorite thing to share. [00:18:24] OP: Is that replica on separate system? [00:18:26] BL: It was on a separate system. I actually don’t say, because it will be telling on who did it. Let’s say that it was physically separate from the other one in a different location as well. [00:18:37] OP: I think we’ve all been there. We’ve all have deleted something that maybe – [00:18:41] CC: I’m going to tell who did it. It was me. [00:18:45] BL: Oh no! It definitely wasn’t me. [00:18:46] OP: We mentioned HA. Will the panel think that there’s now a slightly inverse relationship between the amount of HA that you architect for versus the disaster recovery plan that you have implemented on the back of that? More you’re architecting around HA, like the less you architect or plan for DR. Not eliminating ether of them. [00:19:08] BL: I see it more. Mean, it used to be 15 years ago. [00:19:11] CC: Sorry. HA, we’re talking about high availability. [00:19:15] BL: When you think about high availability, a lot of sites were hosted. This is really before you had public cloud and a lot of people were hosting things on WebHost or they’re hosting themselves. Even if you are a company who had like a big equinox of level 3, you probably didn’t have two facilities at two different equinoxes or level 3, which probably does had one big cage and you just had diversity in the systems in there. We found people had these huge tape backups and we’re very diligent about swapping our tapes out. One thing you did was we made sure that – I mean, lots of practice of bringing this huge system down, because we assumed that the database would die and we would just spend a few hours bringing it back up, or days. Now with high availability, we can architect systems where that is less of a problem, because we could run more things that manage our data. Then we can also do high availability in the backend on the database side too. We can do things like multi-writes and multi-reads. We can actually write our data in multiple places. What we find when we do this is that the loss of a single database or a slice of processing/webhosts just means that our services degraded, which means we don’t really have a disaster in this point and we’re trying to avoid disasters. [00:20:28] JR: I think on that point, the way I’ve always thought about it, and I’ll admit this is super overly simplified, but like successful high availability or HA could make your lead to perform disaster recovery less likely, can, maybe, right? It’s possible. [00:20:45] BL: Also realize that everybody is running in public cloud. In that case, well, you can still back your stuff up to public cloud even if you’re not running in public cloud. There are still people out there who are running big tape arrays, and I’ve seen them. I’ve seen tape arrays that are wider. I’m sitting in an 80-inch wide table, bigger than this table with robotic arms and takes the restic and you had to make sure that you got the text right for that particular day doing your implementation. I guess what I’m saying is that there is a balance. HA, high availability, if you’re doing it in a truly high available way, you can’t miss whole classes of disaster. But I’m not saying that you will not have disaster, because if that was the case, we won’t be having this discussion right now. I’d like to move the conversation just a little bit to more cloud native. If you’re running on Kubernetes, what should you think about for disaster recovery? What are the types of disasters we could have? How could we recover them? [00:21:39] JR: Yeah. I think one thing that comes to mind, I was actually reading the Kubernetes Best Practices book last night, but I just got an O’Reilly membership. Awesome. Really cool book. One of the things that they had recommended early on, which I thought was a really good pull out is that since Kubernetes is a declarative system where we write these manifests to describe the desired state of our application and how it should run, recommending that we make sure to keep that declarative state in source control, just like we would our code so that if something were to go wrong, it is somewhat more trivial to redeploy the application should we need to recover. That does assume we’re not worried about like data and things like that, but it is a good call out I think. I think the book made a good call out. [00:22:22] OP: That’s on the declarative system and enable to bring your systems back up to the exact way they were before kind of itself adds comfort to the whole notion that they could be disaster. If they was, we can spin up backup relatively quickly. That’s back from the days of automation where the guys originally – I came from Red Hat, so fork at Ansible. We’re kind of trying to do the infrastructure as a code, being able to deploy, redeploy, redeploy in the same manner as the previous installation, because I’ve been in this game long-time now and I’ve spent a lot of time working with processes in and around building physical servers. That process will get handled over to lots of different teams. It was a huge thing to build these things, to get one of these things built and signed off, because it literally has to pass through the different teams to do their own different bits of things. The idea that you would get a language that had the functionality that suited the needs of all those different teams, of the store team, could automate their piece, which they were doing. They just wasn’t interactive with any of the other teams. The network people would automate theirs and the application install people would do their bit. The server OS people would do their bit. Having a process that could tie those teams together in terms of a language, so Ansible, Puppet, Chef, those kinds of things try to unite those teams and it can all do your automation, but we have a tool that can take that code and run it as one system end-to-end. At the end of that, you get an up and running system. If you run it again, you get all the systems exactly the same as the previous one. If you run it again, you get another one. Reducing the time to build these things plays very importantly into this space. Disaster is only disaster in terms of time, because things break all the time. How that affects you and how quickly you can recover. If you can recover in like seconds, in minutes and it hasn’t affected your business at all, then it wasn’t really a disaster. The time it takes you to recover, to build your things back is key. All that automation and then leading on to Kubernetes, which is the next step, I think, this whole declarative, self-healing and implementing the desired state on a regular basis really plays well into this space. [00:24:25] CC: That makes me think, I don’t completely understand because I’m not out there architecting people’s systems. The one thing that I do is building this backup tool, which happens to be for Kubernetes. I don’t completely get the limitations and use cases, but my question is, is it enough to have the declarations of how your infrastructure should be in source control? Because what if you’re running applications on the platform and your applications are interacting with a platform, change in the state of the platform. Is that not something that happens? Of course, ideally, having those declarations and source control of course is a great backup, but don’t you also want to back up the changes to state as they keep happening? [00:25:14] BL: Yeah, of course. That has been used for a long-time. That’s how replication works. Literally, you take the change and you push it over the wire and it gets applied to the remote system. The problem is, is that there isn’t just one way to do this, because if you do only transaction-based. If you only do the changes, you need a good base to start with, because you have to apply those changes to something. How do you get that piece? I’m not asking you to answer that. It’s just something to think about. [00:25:44] JR: I think you’ve hit a fatal flaw too, Carlisia, and like what that simplified just like having source control model kind of falls over. I think having that declarative kind of stamped out, this is the ideal nature of the world to this deployment and source control has benefits beyond just that of disaster recovery scenario, right? For stateless applications especially, like we talked about in the previous podcast, it can actually be all lead potentially, which is so great. Move your CI system over to cluster B. Boom! You’re back up and running. That’s really neat. A lot of our customers we work with, once we get them to a point where they’re at that stage, they then go, “Well, what about all these persisted volumes?” which by the way is evolving on a computer, which is a Kubernetes term. But like what about all these parts on like disk that I don’t want to lose if I lose my cluster? That it totally feeds into why tools like the one you work on are so helpful. Maybe I don’t know if now would be a good time. But maybe, Carlisia, you could expand on that tool. What it tries to solve for? [00:26:41] CC: I want to back up a little though. Let’s put aside stateful workloads and volumes and databases. I was talking about the infrastructure itself, the state of the infrastructure. I mean, isn’t that common? I don’t know the answer to this. I might be completely off. Isn’t that common for you to develop a cloud native application that is changing the state of the infrastructure, or is this something that’s not good to do? [00:27:05] JR: It’s possible that you can write applications that can change infrastructure, but think about that. What happens when you have bad code? We all have bad code. Our people like to separate those two things. You can still have infrastructure as code, but it’s separated from the application itself, and that’s just to protect your app people from your not app people and vice versa. A lot of that is being handled through systems that people are writing right now. You have Ansible from IBM. You have things like HashiCorp and all the things that they’re doing. They have their hosted thing. They have their own premise thing. They have their local thing. People are looking at that problem. The good thing is that that problem hasn’t been solved. I guess good and bad at the same time, because it hasn’t been solved. So someone can solve it better. But the bad thing is that if we’re looking for good infrastructure as code software, that has not been solved yet. [00:27:57] OP: I think if we’re talking about containerized applications, I think if there was systems that interacted or affected or changed the infrastructure, they would be separate from the applications. As you were saying, Brian, you just expanded a little bit [inaudible 00:28:11] containerized or sandboxed, processes that were running separate to the main application. You’re separating out what’s actually running and doing function in terms of application versus systems that have to edit that infrastructure first before that main application runs. They’re two separate things. If you had to restore the infrastructure back to the way it was without rebuilding it, but perhaps have a system whereby if you have something editing the infrastructure, you would always have something that would edit it back. If you have the process that runs to stop something, you’d also have a process that start at something. If you’re trying to [inaudible 00:28:45] your applications and if it needs to interact with other things, then that application design should include the consideration of what do I need to do to interact with the infrastructure. If I’m doing something left-wise, I have to do the opposite in equal reaction right-wise to have an effectively clean application. That’s the kind of stuff I’ve seen anyway. [00:29:04] JR: I think it maybe even fold into a whole other topic that we could even cover on another podcast, which is like the notion of the concern of mutating infrastructure. If you have a ton of hands in those cookie jars and they’re like changing things all over the place, you’re losing that potential single source of declarative truth even, right? It just could become very complicated. I think maybe to the crux of your original point, Carlisia. Hopefully I’m not super off. If that is happening a lot, I think it could actually make recover more complicated, or maybe recovery is not the way to put it, but recreating the infrastructure, if that makes sense. [00:29:36] BL: Your infrastructure should be deterministic, and that’s why I said you could. I know we talked about this before about having applications modify infrastructure. Think about that. Can and should are two different things. If you have it happen within your application due to input of any kind, then you’re no longer deterministic, unless you can figure out what that input is going to be. Be very careful about that. That’s why people split infrastructure as code from their other code. You could still have CI, continuous integration and continuous delivery/deployment for both, but they’re on different pipelines with different release metrics and different monitoring and different validation to make sure they work correctly. [00:30:18] OP: Application design plays a very important role now, especially in terms of cloud native architecture. We’re talking a lot about microservices. A lot of companies are looking to re-architect their applications. Maybe mistakes that were made in the past, or maybe not mistakes. It’s perhaps a strong word. But maybe things that were allowed in the past perhaps are now best practices going forward. If we’re looking to be able to run things independently of each other, and by definition, applications independent on the infrastructure, that should be factored in into the architecture of those applications going forward. [00:30:50] CC: Josh asked me to talk a little bit about Velerao. I will touch up on it quickly. First of all, we’d love to have a whole show just about infrastructure code, GitOps. Maybe that would be two episodes. Velero doesn’t do any backup of the infrastructure itself. It works at the Kubernetes level. We back up the Kubernetes clusters including the volumes. If you have any sort of stateful app attached to a pod that can get backed up as well. If you want to restore that to even a different service provider, then the one you backed up from, we have a restic plugin that you can use. It’s embedded in the Velero tool. So you can do that using this plugin. There are few really cool things that I find really cool about Velero is, one, you can do selective backups, which really, really don’t recommend. We recommend you always back up everything, but you can do selective restores. That would be – If you don’t need to restore a whole cluster, why would you do it? You can just do parts of it. It’s super simple to use. Why would you not have a backup? Because this is ridiculously simple. You do it through a command line, and we have a scheduler. You can just put your backup on scheduler. Determine the expiration date of each backup. A lot of neat simple features and we are actively developing things all the time. Velero is not the only one. It’d be fair to mention, and I’m not a super well versed on the tools out there, but etcd itself has a backup tool. I’m not familiar with any of these other tools. One thing to highlight is that we do everything through the Kubernetes API. That’s for example one reason why we can do selective backup or restores. Yes, you can backup etcd completely yourself, but you have to back up the whole thing. If you’re on a managed service, you wouldn’t be able to do that, because you just wouldn’t have access. All the tools like we use to back up to the etcd offers or a service provider. PX-motion. I’m not sure what this is. I’m reading the documentation here. There is this K10 from [inaudible 00:33:13] Canister. I haven’t used any of these tools. [inaudible 00:33:16]. [00:33:17] OP: I just want to say, Velero, the last customer I worked on, they wanted to use Velero in its capacity to be able to back up a whole cluster and then restore that whole cluster on a different cloud provider, as you mentioned. They weren’t thoroughly using it as – Well, they were using it as backup, but their primary function was that they wanted to populate the cluster as it was on a brand-new cloud provider. [00:33:38] CC: Yeah. It’s a migration. One thing that, like I said, Velero does, is back up the cluster, like all the Kubernetes objects, because why would we want to do that? Because if you’re declaring – Someone explain to everybody who’s listening, including myself. Some people bring this up and they say, “Well, I don’t need to back up the Kubernetes objects if all of that is declared and I have the declaration is source control. If something happens, I can just do it again. [00:34:10] BL: Untrue, because just for any given Kubernetes object, there is a configuration that you created. Let’s say if you’re creating an appointment, you need spec replicas, you need the spec templates, you need labels and selectors. But if you actually go and pull down that object afterwards, what you’ll see is there is other things inside of that object. If you didn’t specify any replicas, you get the defaults or other things that you should get defaults for. You don’t want to have a lousy backup and restore, because then you get yourself into a place where if I go back this thing up and then I restore it to a different cluster to actually test it out to see if it works, it will be different. Just keep that in mind when you’re doing that. [00:34:51] JR: I think it just comes down to knowing exactly what Brian just said, because there certainly are times where when I’m working with a customer, there’s just such a simple use case at the notion of redeploying the application and potentially losing some of those factors that may have mutated overtime. They just shrug to it and go, “Whatever.” It is so awesome that tools like Velero and other tools are bridging that gap, and I think to a point that Olive made, not only just backing that stuff up and capturing it state as it was in the cluster, but providing us with a good way to section out one namespace or one group of applications and just move those potentially over and so on. Yeah, it just kind of comes to knowing what exactly are you going to have to solve for and how complex your solution should be. [00:35:32] BL: Yeah. We’re getting towards the end, and I wanted to make sure that we talked about testing your backup, because that’s a popular thing here. People take backups. I’ve done my backups, whether I dump to S3, or I have Velero dumping to S3, or I have some other method that is in an invalid backup, it’s not valid until someone comes and takes that backup, restore it somewhere and actually verifies that it works, because there’ll be nothing worse than having yourself in a situation where you need a backup and you’re in some kind of disaster, whether small or large, and going to find out that, “Oh my gosh! We didn’t even backup the important thing.” [00:36:11] CC: That is so true. I have only been in this backup world for a minute, but I mean I’ve needed to backup things before. I don’t think I’ve learned this concept after coming here. I think I’ve known this concept. It just became stronger in my mind, so I always tell people, if you haven’t done that restore, you don’t have a backup. [00:36:29] JR: One thing I love to add on to that concept too is having my customers run like fire drills if they’re open to it. Effectively, having a list of potential terrible things that can happen, from losing a cluster to just like losing an important component. Unlike one person the team, let’s say, once a week or one a month, depending on their tolerance, just chooses something from that list and does it, not in production, but does it. It gives you the opportunity to test everything end-to-end. Did your learning fire off? When you did restore to your points, was the backup valid? Did the application come back online? It’s kind of a lot of like semi-fun, using the word fun loosely there. Fun ways that you can approach it, and it really is a good way to kind of stress test. [00:37:09] BL: I do have one small follow up on that. You’re doing backups, and no matter how you’re doing them, think about your strategy and then how long to keep data. I mean, whether it’s due to regulation or just physical space and it costs money. You just don’t backup yesterday and then you’d backup again. Backup every day and keep the last 8 days and then, like old school, would actually then have a full backup and keep that for a while just in case, because you never know. [00:37:37] CC: Good point too. Yeah. I think a lot of what we said goes to what – It was Olive I think who said it first. You have to understand your needs. [00:37:46] OP: Yeah, just which bits have different varying degrees of importance in terms of application functionality for your end user. Which bits are absolutely critical and which bits can buy you a little bit more time to recover. [00:37:58] CC: Yeah. That would definitely vary from product to product. As we are getting into this idea of ephemeral clusters and automation and we get really good at automating things and bringing things back up, is it possible that we get to a point where we don’t even talk about disasters anymore, or you just have to grow, bring this up cluster or this system, and does it even matter why [inaudible 00:38:25]. We’re not going to talk about this aspect, because what I’m thinking is in the past, in a long, long time ago, or maybe not so long time ago. When I was working with application, and that was a disaster, it was a disaster, because it felt like a disaster. Somebody had to go in manually and find out what happened and what to fix and fix it manually. It was complete chaos and stress. Now if they just like keep rolling and automate it, something goes down, you bring it back up. Do you know what I mean? It won’t matter why. Are we going to talk about this in terms of it was a disaster? Does it even matter what caused it? Maybe it was a – Recovery from a disaster wouldn’t look any different than a planned update, for example. [00:39:12] BL: I think we’re getting to a place – And I don’t know whether we’re 5 years away or 10 years away or 20 years away, a place where we won’t have the same class of disaster that we have now. Think about where we’ve come over the past 20 years. Over the past 20 years, be basically looked at hardware in a rack is replace. I can think about 1988, 1999 and 2000. We rack a whole bunch of servers, and that server will be special. Now, at these scales, we don’t care about that anymore. When a server goes away, we have 50 more just like it. The reason we were able to do that across large platforms is because of Linux. Now with Kubernetes, if Kubernetes keeps on going in the same trajectory, we’re going to basically codify these patterns that makes hardware loss not a thing. We don’t really care if we lose a server. You have 50 more nodes that look just like it. We’re going to start having the software – The software is always available. Think about like the Google Spanner. Google Spanner is multi-location, and it can lose notes and it doesn’t lose data, and it’s relational as well. That’s what CockroachDB is about as well, about Spanner, and we’re going into the place where this kind of technology is available for anyone and we’re going to see that we’re not going to have these kinds of disasters that we’re having now. I think what we’ll have now is bigger distributed systems things where we have timing issues and things like that and leader election issues. But I think those cool stuff can’t be phased out at least over the next computing generation. [00:40:39] OP: It’s maybe more around architectures these days and applications designers and infrastructure architects in the container space and with Kubernetes orchestrating and maintaining your desired state. You’re thinking that things will fail, and that’s okay, because it will go back to the way it was before. The concept of something stopping in mid-run is not so scary anymore, because it would get put back to its state. Maybe you might need to investigate if it keeps stopping and starting and Kubernetes keeps bringing it back. The system is actually still fully functional in terms of end users. You as the operator might need to investigate why that’s so. But the actual endpoint is still that your application is still up and running. Things fail and it’s okay. That’s maybe a thing that’s changed from maybe 5 years ago, 10 years ago. [00:41:25] CC: This is a great conversation. I want to thank everybody, Olive Power, Josh Rosso, Brian Lyles. I’m Carlisia Campos singing off. Make sure to subscribe. This was Episode 8. We’ll be back next week. See you. [END OF EPISODE] [0:50:00.3] KN: Thank you for listening to The Podlets Cloud Native Podcast. Find us on Twitter at https://twitter.com/ThePodlets and on the http://thepodlets.io/ website, where you'll find transcripts and show notes. We'll be back next week. Stay tuned by subscribing. [END]See omnystudio.com/listener for privacy information.

Jacked up on K10, the team continues their murder spree with little concern for their personal safety and no concern for subtlety

In this episode, Anna Clare Harper finds out about construction apprenticeships in London with Paul Ruddick, Co-founder of K10, London's largest construction-specific Apprenticeship Training Programme (ATA). Anna and Paul are joined by Peter Bannister, Senior Apprenticeship Programme Manager and George, an apprentice Site Manager on the scheme. Anna and Paul discuss why apprenticeships are vital to address the current construction skills crisis, which is a factor limiting the supply of new buildings. Peter explains how K10's approach offers a win/win solution for contractors and apprentices and George outlines how the K10 programme has put him on track for a £60-70k salary within seven years. Highlights include: How 40% of the construction workforce is due to retire within the next decade. Why taking on apprentices makes commercial sense and has a positive social impact. How the construction sector should see the industry skills shortage as an opportunity. Resources: https://www.k-10.co.uk/ LinkedIn: https://www.linkedin.com/company/k10 Facebook: https://www.facebook.com/K10socialimpact/ Instagram: @k10apprenticeships Twitter: @K10socialimpact

durée : 00:12:45 - Scarlatti 555 - Trois nouvelles sonates du compositeur italien Domenico Scarlatti : la K 10, K 11 et K 12 sous les doigts agiles des clavecinistes Béatrice Martin et Kenneth Weiss.

Episode #124  - Interviews from Barrett Jackson Live is brought to you by these rad ass C10 Sponsors - Please support those that support us.  www.dakotadigital.com When you need to upgrade those old gauges - Dakota Digital. azproperformance.com Upgrade from stock - thing Pro Performance! www.classicperform.com Save 10% - Use code "C10 Talk" at check out and Save Big! www.accuair.com The Leaders in Automotive Air Management. I spent a few days running around Barrett Jackson Scottsdale 2019 and grabbed a few interviews along the way.  Dan Hogan - @hogieshine - sold two trucks, a 1964 C10 Longbed with 9.1 original miles "Lambrecht Trucks" and a 1968 K10 that was a completely fresh build Dan and his son built.  Todd Carpenter  - @bigfishgarage - sold tow trucks as well. A 1986 K10 short bed - fresh build, and a GMC Crew Cab Dually with an "Indy Hauler' theme to it.  Mike Blackwelder - @67patriach  - sold his Custom 1967 C10    It was fun to see a few of the fellas throughout the week and there was no shortage of C10 Trucks (91 - on my count) this year at Barrett Jackson. The Top Seller was a 1969 K10 - that sold for $137,500 with fees. Damn Son!!  

On this special episode of The Awesome With C.O.D.Y., Cody is joined by John Giang concept artist and all around awesome dude.If you are in the Chicago Area you can meet John at his booth K10 in Artist Alley at C2E2 the weekend of April 6-8, 2018.Also check out his Facebook fanpage for other conventions near you.JOHN GIANG    |    ORBITAL HARVEST    |    CONCEPT ART & ILLUSTRATION    |    PORTFOLIO    |    FANPAGE    |    INSTAGRAMiTunes: http://tinyurl.com/kqkgackFacebook: http://tinyurl.com/myovgm8Tumblr: http://tinyurl.com/m7a6mg9Twitter: @ComesNaturalPodYouTube: http://tiny.cc/5snxpyBlogTalkRadio: http://www.blogtalkradio.com/comesnaturally

Caitlin assesses the girls' top 5 strengths and challenges the idea that people "need to be well-rounded"--they don't! Can you guys guess which 2/5 strengths Shailey and Katie have in common? Real-sponsored by BookThisProject.com ! Fake-sponsored by Collaboration. This episode is sponsored by: Book This Project - Use the code S&K10 for $10 off the starter kit! bookthisproject.com Want to find your strengths?! Caitlin is giving away a free assessment! Follow @shaileyandkatie on instagram to find out how to enter! If listeners want to purchase a hard copy of StrengthsFinder 2.0, which includes an assessment access code, they can do so here: StrengthsFinder 2.0 Hyperion EA https://www.amazon.com/dp/159562015X/ref=cm_sw_r_sms_awdb_vJzlzbA585PJ1 If listeners want to purchase an online access code, which gives them access to an e-book copy of StrengthsFinder 2.0, they can do so here: https://www.gallupstrengthscenter.com/Purchase/en-US/Product www.propelpeople.com

This week on WRLWND Radio, Marcello Sukhdeo talks about a predictive artificial intelligence that can tell the police whether a suspect should be kept in custody, also, he looks at what the Top 5 paid CEOs earned last year and a 3D body scanner that can measure your body parts in 30 seconds. Show Notes: AI and crime Police in the city of Durham, England are preparing to go live in the next few months with a predictive artificial intelligence system that will determine whether a suspect should be kept in custody, according to the BBC.  This system is named Harm Assessment Risk Tool or HART which has been designed to grade individuals on a low, medium, or high risk level of committing a future offense.  Tests conducted in 2013, in which suspects’ behavior were tracked for two years after an offense, generally the forecasts were 98 per cent accurate. For the high-risk level the forecasts were accurate 88 per cent of the time. The Durham police assured the BBC that Hart’s decisions will only be “advisory” during its preliminary and experimental use. Because the system will take into account factors like gender and postal code.  Highest paid CEOs of 2016 Bloomberg came up with the list of the top paid CEOs of 2016, the top four highest paid CEOs received compensation valued in the nine figures. Marc Lore, Walmart U.S. E-commerce CEO. He earned $236.8 million dollars in 2016. Tim Cook, Apple CEO with $150 million. John Weinberg, Evercore Executive Chairman. He earned a total of $123.9 million. Sundar Pichai, Google CEO at $106.5 million. Elon Musk, CEO of Tesla, with $99.7 million.  3D scanning scale ShapeScale is a 3D body scanner that was recently launched at $499. This 3D scale uses body scanning to create a 360-degree, 3D digital avatar with measurements and body composition stats. The scale is round and looks like a normal scale, but it has an arm with a camera. Standing on the scale the arm circles around you about four times, taking photos of your body.  Then by using the images and your weight, ShapeScale creates the avatar. The entire process takes about 30 seconds. The data can be useful, especially athletes but what about the normal people like you and me. If you are not exercising then of course it will not make sense to get this scale. But if you are so incline to measure your body shape quite frequently, then the ShapeScale may be just what you are looking for. Techbites Microsoft has officially released Visual Studio for Mac following an extended preview period for developers. The release corresponds with the kick off of Microsoft’s Build 2017 developer conference this week. Opera browser is trying to compete with the likes of Google Chrome by integrating messaging apps like WhatsApp, Messenger and Telegram into its sidebar so now you can chat while your browse. Talking about Google Chrome, the desktop version of Google Chrome will not be coming to Windows 10 S. Windows 10 S was announced last week which allows users to install only apps that are distributed through the Windows Store. And finally, The Oukitel K10000 Pro can confidently say that it has the longest battery life of any smartphone currently on the market. Its enormous 10000mAh is said to be able to go 10-15 days on a single charge. While a price has not been announced for the Pro yet, the previous version went for $211. The company says the K10,000 Pro will ship sometime in June and will be available in China. To get one you will have to purchase it online.