Podcasts about OpenStack

AI agents hold the promise of continuously testing, scanning, and fixing code for security vulnerabilities, but we're still progressing toward that vision. Startups like Aptori are helping bridge the gap by building AI-powered security engineers for enterprises. Aptori maps an organization's codebase, APIs, and cloud infrastructure in real time to understand data flows and authorization logic, allowing it to detect and eventually remediate security issues. At Google Cloud Next, Aptori CEO Sumeet Singh discussed how earlier tools merely alerted developers to issues—often overwhelming them—but newer models like Gemini 2.5 Flash and Claude Sonnet 4 are improving automated code fixes, making them more practical. Singh and co-founder Travis Newhouse previously built AppFormix, which automated OpenStack cloud operations before being acquired by Juniper Networks. Their experiences with slow release cycles due to security bottlenecks inspired Aptori's focus. While the goal is autonomous agents, Singh emphasizes the need for transparency and deterministic elements in AI tools to ensure trust and reliability in enterprise security workflows.Learn more from The New Stack about the latest insights in AI application security: AI Is Changing Cybersecurity Fast and Most Analysts Aren't ReadyAI Security Agents Combat AI-Generated Code RisksDevelopers Are Embracing AI To Streamline Threat Detection and Stay AheadJoin our community of newsletter subscribers to stay on top of the news and at the top of your game.

Discover how Rackspace Spot is democratizing cloud infrastructure with an open-market, transparent option for cloud servers. Kevin Carter, Product Director at Rackspace Technology, discusses Rackspace Spot's hypothesis and the impact of an open marketplace for cloud resources. Discover how this novel approach is transforming the industry. TIMESTAMPS[00:00:00] – Introduction & Kevin Carter's Background[00:02:00] – Journey to Rackspace and Open Source[00:04:00] – Engineering Culture and Pushing Boundaries[00:06:00] – Rackspace Spot and Market-Based Compute[00:08:00] – Cognitive vs. Technical Barriers in Cloud Adoption[00:10:00] – Tying Spot to OpenStack and Resource Scheduling[00:12:00] – Product Roadmap and Expansion of Spot[00:16:00] – Hardware Constraints and Power Consumption[00:18:00] – Scrappy Startups and Emerging Hardware Solutions[00:20:00] – Programming Languages for Accelerators (e.g., Mojo)[00:22:00] – Evolving Role of Software Engineers[00:24:00] – Importance of Collaboration and Communication[00:28:00] – Building Personal Networks Through Open Source[00:30:00] – The Power of Asking and Offering Help[00:34:00] – A Question No One Asks: Mentors[00:38:00] – The Power of Educators and Mentorship[00:40:00] – Rackspace's OpenStack and Spot Ecosystem Strategy[00:42:00] – Open Source Communities to Join[00:44:00] – Simplifying Complex Systems[00:46:00] – Getting Started with Rackspace Spot and GitHub[00:48:00] – Human Skills in the Age of GenAI - Post Interview Conversation[00:54:00] – Processing Feedback with Emotional Intelligence[00:56:00] – Encouraging Inclusive and Clear Collaboration QUOTESCHARNA PARKEY“If you can't engage with this infrastructure in a way that's going to help you, then I guarantee you it's not up to par for the direction that we're going. [...] This democratization — if you don't know how to use it — it's not doing its job.”KEVIN CARTER“Those scrappy startups are going to be the ones that solve it. They're going to figure out new and interesting ways to leverage instructions. [...] You're going to see a push from them into the hardware manufacturers to enhance workloads on FPGAs, leveraging AVX 512 instruction sets that are historically on CPU silicon, not on a GPU.”

KubeCon Europe 2025 in London has wrapped up, and we're bringing you all the highlights, trends, and behind-the-scenes insights straight from the show floor!In this special recap episode, I'm joined by two CNCF Ambassadors and community powerhouses: Kasper Borg Nissen, the Co-Chair of this KubeCon as well as of the KubeCon 2024 editions, and a Developer Relations Engineer at Dash0; and William Rizzo, Consulting Architect at Mirantis and Linkerd Ambassador.Together, we unpack the major themes from the event—from platform engineering and internal developer platforms, to open source observability, and where Kubernetes is headed next. We also chat about the vibe of the community, emerging projects to watch, and important trends in European tech sphere.Whether you missed the conference or want to catch up on important updates you might have missed, this episode gives you a curated take straight from the experts who know the cloud-native space inside out.The episode was live-streamed on 22 April 2025 and the video is available at https://www.youtube.com/watch?v=JyxJOmOEBvQYou can read the recap post: https://medium.com/p/740258a5fa46OpenObservability Talks episodes are released monthly, on the last Thursday of each month and are available for listening on your favorite podcast app and on YouTube.We live-stream the episodes on Twitch and YouTube Live - tune in to see us live, and chime in with your comments and questions on the live chat.⁠⁠https://www.youtube.com/@openobservabilitytalks⁠  https://www.twitch.tv/openobservability⁠Show Notes:00:00 - intro03:28 - KubeCon impressions09:59 - Backstage turns 518:56 - CNCF turns 10 and CNCF annual survey27:22 - Sovereign cloud in Europe and the NeoNephos initiative33:55 - CI/CD use in production increases36:52 - OpenInfra joins the Linux Foundation40:16 - Cloud native local communities, DEI and the BIPOC initiative 51:11 - Observability query standardization SIG updates59:36 - outroResources:CNCF 2024 Annual Survey https://www.cncf.io/reports/cncf-annual-survey-2024/NeoNephos initiative for sovereign EU cloud: https://www.linkedin.com/feed/update/urn:li:share:7313115943075766273/ OpenInfra Foundation and OpenStack join The Linux Foundation: https://www.linkedin.com/feed/update/urn:li:share:7307839934072066048/ Backstage turns 5: https://www.linkedin.com/feed/update/urn:li:activity:7318163557206966272/ Kubernetes 1.33 release: https://www.linkedin.com/feed/update/urn:li:activity:7321054742174924800/Socials:Twitter:⁠ https://twitter.com/OpenObserv⁠YouTube: ⁠https://www.youtube.com/@openobservabilitytalks⁠Dotan Horovits============Twitter: @horovitsLinkedIn: www.linkedin.com/in/horovitsMastodon: @horovits@fosstodonBlueSky: @horovits.bsky.socialKasper Borg Nissen===============Twitter: https://www.twitter.com/phennexLinkedIn: https://www.linkedin.com/in/kaspernissen/BlueSky: https://bsky.app/profile/kaspernissen.xyz⁠William Rizzo===========Twitter: https://twitter.com/WilliamRizzo19LinkedIn: https://www.linkedin.com/in/william-rizzo/BlueSky: https://bsky.app/profile/williamrizzo.bsky.social

Cloud native patterns and open source developments were on display at the KubeCon + CloudNativeCon Europe conference. The biannual gathering was showing how the container ecosystem continues to mature and analysts Jean Atelsek and William Fellows join host Eric Hanselman to explore their insights. The Cloud Native Computing Foundation (CNCF), part of the Linux Foundation, continues to expand the event and advance the maturity of the open source projects that are part of its purview. Day 2 operations have been gaining focus and the pre-conference FinOps X event was an indication of the emphasis on operational controls as it digs into infrastructure cost management. The opening “Day 0” events at KubeCon, which have been the forum for specialized project meetings, have become a key part of the conference, with over 6,000 attendees, almost half of the reported 13,000 total.  The Kubernetes container management project is now over ten years old and one of the other signs of technology evolution was the integration of the OpenInfra Foundation, which managed the OpenStack project and other infrastructure elements, into the Linux Foundation. Open source projects are gaining wider adoption and one of the messages from projects and vendors at KubeCon, was the hope that it could offer alternatives to enterprise infrastructure stalwart, VMware. The CNCF is expanding its investments in improving security across the projects under its umbrella. There was also continued development of platform engineering initiatives. Bounding the expanding world of open source projects to create consistent development and operational tool chains for enterprise is one more sign of maturity in the container world. More S&P Global Content: AWS, Microsoft Azure and Google Cloud enter the FinOps vortex For S&P Global subscribers: Kubernetes meets the AI moment in Europe with technology, security, investment Data management, GenAI, hybrid cloud are top Kubernetes workloads – Highlights from VotE: DevOps Kubernetes ecosystem tackles new technical and market challenges Kubernetes, serverless adoption evolve with cloud-native maturity – Highlights from VotE: DevOps Credits: Host/Author: Eric Hanselman Guests: Jean Atelsek, William Fellows Producer/Editor: Adam Kovalsky Published With Assistance From: Sophie Carr, Feranmi Adeoshun, Kyra Smith

This week, we discuss Google acquiring Wiz, the rise of Vibe Coding, and what really counts as legacy software. Plus, Coté runs a post-acquisition all-hands meeting. Watch the YouTube Live Recording of Episode 511 (https://www.youtube.com/live/ok8lLHFCCRY?si=aos-m8eR1iYcR12v) Runner-up Titles Tattoo “BUSINESS AS USUAL” on the inside of your eyelids BUSINESS AS USUAL One billion a month Turns out they're gonna put lions in the product. Vibe coding is outcomes-focused. Cote's AI Thunderdome Don't make me learn Think About Time VibeCOBOL I don't like the no-head Rundown Google in Fresh Talks to Buy Cybersecurity Startup Wiz for $30 Billion (https://www.wsj.com/business/deals/alphabet-back-in-deal-talks-for-cybersecurity-startup-wiz-41cd3090?mod=tech_lead_story) Intel board announces Lip-Bu Tan as new CEO (https://www.theregister.com/2025/03/12/intel_lip_bu_tan_new_ceo/) Vibe Coding AI IDEs Need Moats (https://materializedview.io/p/ai-ides-need-moats?ref=dailydev) AI coding assistant refuses to write code, tells user to learn programming instead (https://arstechnica.com/ai/2025/03/ai-coding-assistant-refuses-to-write-code-tells-user-to-learn-programming-instead/) Github Coploit does have an agent mode (https://github.com/features/copilot) AI coding assistant Cursor reportedly tells a 'vibe coder' to write his own damn code (https://techcrunch.com/2025/03/14/ai-coding-assistant-cursor-reportedly-tells-a-vibe-coder-to-write-his-own-damn-code/) Vibe Coder job listing (https://getcoai.com/careers/vibe-coder-frontend-developer-role/) Legacy Software Relevant to your Interests Saudi Arabia Buys Pokémon Go, and Probably All of Your Location Data (https://www.404media.co/saudi-arabia-buys-pokemon-go-and-probably-all-of-your-location-data/) Open R1: Update #3 (https://huggingface.co/blog/open-r1/update-3) Sonos has canceled its streaming video player (https://www.theverge.com/tech/628297/sonos-pinewood-streaming-box-canceled) ServiceNow releases no-code, low-code AI agent builder (https://www.ciodive.com/news/servicenow-yokohama-agentic-ai-low-code-development-tool/742275/) Meta Seeks to Block Further Sales of Ex-Employee's Scathing Memoir (https://www.nytimes.com/2025/03/12/technology/meta-book-sales-blocked.html) AirPods Getting Live Translation Feature Later This Year (https://www.macrumors.com/2025/03/13/airpods-live-translation-ios-19/) Clouded Judgement 3.14.25 - Authentication in the Age of AI Agents (https://cloudedjudgement.substack.com/p/clouded-judgement-31425-authentication?utm_source=post-email-title&publication_id=56878&post_id=159023089&utm_campaign=email-post-title&isFreemail=true&r=2l9&triedRedirect=true&utm_medium=email) Google allows users to personalize their Gemini conversations with new features (https://www.cnbc.com/2025/03/13/google-now-allows-users-to-personalize-their-gemini-conversations.html) Undergraduate Upends a 40-Year-Old Data Science Conjecture (https://www.wired.com/story/undergraduate-upends-a-40-year-old-data-science-conjecture/) Job Seekers Hit Wall of Salary Deflation - WSJ (https://archive.ph/Gn0F9) Something Is Rotten in the State of Cupertino (https://daringfireball.net/2025/03/something_is_rotten_in_the_state_of_cupertino) OpenStack comes to the Linux Foundation | TechCrunch (https://techcrunch.com/2025/03/12/openstack-comes-to-the-linux-foundation/?trk=feed-detail_main-feed-card_feed-article-content) Accusations of Corporate Espionage Shake a Software Rivalry (https://www.nytimes.com/2025/03/17/business/dealbook/rippling-deel-corporate-spy.html?smid=nytcore-ios-share&referringSource=articleShare) IBM Mergers: Closing on HashiCorp and Intent to Acquire Data (https://redmonk.com/rstephens/2025/03/14/ibm-hashicorp-datastax/)S (https://redmonk.com/rstephens/2025/03/14/ibm-hashicorp-datastax/)tax (https://redmonk.com/rstephens/2025/03/14/ibm-hashicorp-datastax/) Nonsense The Problem with Time & Timezones - Computerphile (https://www.youtube.com/watch?v=-5wpm-gesOY&t=7s) Southwest Airlines CEO Video via WFAA (https://www.tiktok.com/@wfaach8/video/7480585081753537835?_t=ZT-8ufHaixEbks&_r=1) Southwest Airlines Just Broke the $5 Chicken Rule, and There Goes What Once Made It Great (https://www.inc.com/bill-murphy-jr/southwest-airlines-just-broke-the-5-chicken-rule-and-there-goes-what-once-made-it-great/91161331). Conferences SREday London (https://sreday.com/2025-london-q1/), March 27-28, Coté speaking (https://sreday.com/2025-london-q1/Michael_Cote_VMware__Pivotal_Platform_Engineering_for_Private_Cloud). 10% with code LDN10 Monki Gras (https://monkigras.com/), London, March 27-28, Coté speaking. Cloud Foundry Day US (https://events.linuxfoundation.org/cloud-foundry-day-north-america/), May 14th, Palo Alto, CA NDC Oslo (https://ndcoslo.com/), May 21-23, Coté speaking. KubeCon EU (https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/), April 1-4, London. SDT News & Community Join our Slack community (https://softwaredefinedtalk.slack.com/join/shared_invite/zt-1hn55iv5d-UTfN7mVX1D9D5ExRt3ZJYQ#/shared-invite/email) Email the show: questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com) Free stickers: Email your address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) Follow us on social media: Twitter (https://twitter.com/softwaredeftalk), Threads (https://www.threads.net/@softwaredefinedtalk), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com) Watch us on: Twitch (https://www.twitch.tv/sdtpodcast), YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured), Instagram (https://www.instagram.com/softwaredefinedtalk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk) Book offer: Use code SDT for $20 off "Digital WTF" by Coté (https://leanpub.com/digitalwtf/c/sdt) Sponsor the show (https://www.softwaredefinedtalk.com/ads): ads@softwaredefinedtalk.com (mailto:ads@softwaredefinedtalk.com) Recommendations Brandon: Severance (https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://tv.apple.com/us/show/severance/umc.cmc.1srk2goyh2q2zdxcx605w8vtx&ved=2ahUKEwiJ95mBjZeMAxXo4skDHWOrJ3gQFnoECGwQAQ&usg=AOvVaw06Jqv4WAF89UKW2fy4RaHx) ** Matt: Geoff Huntley's blog (https://ghuntley.com/) Coté: Barthes: A Very Short Introduction (https://academic.oup.com/book/28389), Coté — When Shit Hits the Fan (https://overcast.fm/+AAxlGT9_-n8). Photo Credits Header (https://unsplash.com/photos/people-sitting-on-chairs-watching-a-game-6vAjp0pscX0)

In this episode, Henrik Blixt, a product manager at Intuit and Argo maintainer, shares his experiences and insights into managing platform engineering teams that handle Kubernetes, service mesh, API gateways, and more. He emphasizes the importance of product management within platform engineering and discusses his involvement with the CNCF's end user technical advisory board. Henrik also highlights the significance of open source in his professional journey and details the ongoing initiatives and advancements within the Argo project.   00:00 Introduction and Guest Welcome 00:53 Discussion on Argo and Developer Tools 01:41 Open Source Community Involvement 02:06 CNCF End User Technical Advisory Board 03:11 Reference Architectures and Initiatives 08:18 Challenges and Solutions for End Users 13:20 Argo Project Insights 16:03 The Importance of Product Management 17:16 Conclusion and Final Thoughts   Guest: Henrik Blixt leads a Product Management team responsible for the Intuit core platform, where he defines the strategy and direction that has shaped Intuit's cloud native platform based on CNCF projects like Kubernetes, Envoy, Istio, Prometheus, Argo (and many more!) that's used by 7000 developers and serving over 100M users. Being a passionate member of the open source community for almost 30 years, from Linux through OpenStack and Kubernetes, Henrik is currently focused on the Argo project as a core maintainer. He also represents Intuit across other committees, like the CNOE project and the broader Linux Foundation, where he shares experiences and best practices from Intuit's use of open source, making sure end users are heard and their pain points understood. He loves engaging with the community and has been a prolific speaker and event program committee member across ArgoCon, GitOpsCon, Kubecon over the years. A native of Sweden, earning his B.Sc in information systems from the University of Gothenburg, he now resides in California with his family.    

Thomas Hatch has spent years building and scaling infrastructure, from the early days of SaltStack to watching Kubernetes and microservices reshape the industry. In this episode, he shares how automation has changed operations at scale and why some companies are rethinking their cloud strategy.About the GuestThomas is currently the CEO of a stealth startup developing the next generation infrastructure management platform. He is the creator of the Salt open source software project and founded the company SaltStack which he sold to VMware in 2020. He has spent his career writing software to orchestrate and automate the work of securing and maintaining enterprise IT infrastructure from core data center systems to the very edge of the network and IoT. Thomas built fully automated, secure IT environments for the U.S. intelligence community in addition to decades of experience implementing global infrastructures for the largest businesses in the world. He has shared his knowledge of IT security and management automation with tens of thousands of practitioners at more than 100 industry events. Thomas and SaltStack have been recognized with numerous awards ranging from open source community growth to innovation in automation and cybersecurity. For his work on Salt, in 2012 Tom received the Black Duck “Rookie of the Year” award and was named to the GitHub Octoverse list in both 2012 and 2013 for leading a project with the highest number of unique contributors, rubbing shoulders with projects from Android, Mozilla, and OpenStack. More recently, SaltStack SecOps was chosen by CSO Magazine as one of the hottest new products at RSA Conference 2019.

Jeramiah Dooley (he/him) leads the advocacy team focused on Enterprise customers, making sure that the product and content are aligned for organizations who are using GitHub every day. For more than 19 years he has spent his career at the intersection of 'enterprise' and 'what's next' and is excited to focus on bringing the best experience possible to developers and platform teams. Prior to GitHub, Jeramiah led the advocacy efforts around serverless container services at AWS, and was a Principal Cloud Advocate in Azure Engineering, leading the team that supported Enterprise Platforms and Tools. Jeramiah was also the Manager of NetApp's Global Technical Pursuit team, focusing on helping customers and partners architect next generation solutions using their entire portfolio, focusing on VMware, OpenStack, and container integrations. Jeramiah also has worked in the healthcare, legal and service provider industries. You can find Jeramiah on the following sites: Bluesky LinkedIn GitHub PLEASE SUBSCRIBE TO THE PODCAST Spotify Apple Podcasts YouTube Music Amazon Music RSS Feed You can check out more episodes of Coffee and Open Source on https://www.coffeeandopensource.com Coffee and Open Source is hosted by Isaac Levin --- Support this podcast: https://podcasters.spotify.com/pod/show/coffeandopensource/support

Jónas Helgi Pálsson has worked at Redpill Linpro for 16 years, focusing on operations and virtualization. Today, he works with OpenStack, which is used to operate solutions on Redpill Linpro's own cloud, RLNC – used both for internal needs and for customers. Want to know how the world's largest cloud service works? Don't forget to listen to this episode of IT Talks!

The National Institute of Standards and Technology (NIST) facces ongoing challenges regarding its backlog of security vulnerability reports. Despite some progress, NIST missed its September 30th deadline to restore processing speeds to pre-February levels, leaving over 17,000 Common Vulnerabilities and Exposures (CVEs) unprocessed. This backlog poses significant risks to organizations, as they may remain unaware of vulnerabilities that are actively being exploited. The episode highlights the importance of effective risk management in cybersecurity and encourages organizations to pressure vendors to participate in disclosure programs.The episode also delves into the rising concerns surrounding cloud security threats, which have become the top worry for executives, according to a recent PwC report. The report identifies hack and leak operations, third-party breaches, and ransomware as leading threats, with organizations feeling least prepared to address cloud attacks. Additionally, Microsoft has informed customers about a software bug that affected log data collection for key security products, emphasizing the need for robust security measures and incident response planning.Host Dave Sobel shifts focus to the impact of Broadcom's acquisition of VMware, which has led many users to explore alternatives like OpenStack. The latest version of OpenStack, codenamed Dalmatian, is experiencing a resurgence as former VMware users migrate to its platform, benefiting from improved tools and a stable ecosystem. Meanwhile, Microsoft has announced a 10% price increase for its System Center management tool set for 2025, raising questions about potential challenges for the product in the competitive landscape.Finally, the episode addresses the stagnation in IT leadership diversity, revealing concerning statistics from a recent survey. The data shows that 89.6% of IT leaders are white and 79% are male, with minimal changes from previous quarters. The Society for Human Resource Management's recent decision to remove equity from its diversity, equity, and inclusion strategy has sparked controversy, as critics argue it undermines commitments to fostering a diverse workplace. Sobel emphasizes the importance of gender diversity in IT, citing research that indicates diverse teams outperform homogeneous ones, ultimately enhancing business efficiency and customer satisfaction.Four things to know today00:00 NIST Faces Vulnerability Report Backlog as Cloud Threats Dominate Cybersecurity Concerns04:02 VMware Users Flock to OpenStack Amid Acquisition Uncertainty, While Microsoft Ups System Center Pricing for 2025 05:36 Apple Addresses macOS Sequoia Cybersecurity Bugs Ahead of Major AI Launch with iOS 18.106:38 IT Leadership Diversity Stagnates as DEI Efforts Face Scrutiny   Supported by:  https://www.huntress.com/mspradio/https://www.coreview.com/msp  Event: www.smbTechFest.com/Go/Sobel   All our Sponsors: https://businessof.tech/sponsors/ Do you want the show on your podcast app or the written versions of the stories? Subscribe to the Business of Tech: https://www.businessof.tech/subscribe/Looking for a link from the stories? The entire script of the show, with links to articles, are posted in each story on https://www.businessof.tech/ Support the show on Patreon: https://patreon.com/mspradio/ Want our stuff? Cool Merch? Wear “Why Do We Care?” - Visit https://mspradio.myspreadshop.com Follow us on:LinkedIn: https://www.linkedin.com/company/28908079/YouTube: https://youtube.com/mspradio/Facebook: https://www.facebook.com/mspradionews/Instagram: https://www.instagram.com/mspradio/TikTok: https://www.tiktok.com/@businessoftechBluesky: https://bsky.app/profile/businessoftech.bsky.social

This week, we discuss Dell's growth in AI servers, GEICO's transition from VMware to OpenStack, and the concept of Kingmaking. Plus, plenty of thoughts on USB hubs. Watch the YouTube Live Recording of Episode (https://www.youtube.com/watch?v=n8Y7WI3BU0c) 484 (https://www.youtube.com/watch?v=n8Y7WI3BU0c) Runner-up Titles You just put it in a different USB port I am just going to repeat thing you say A Decade of Aftershow Happy Anniversary Whatever :43 it is for you Cascading hubs not supported anywhere. Mac Dongle Pro Getting DevOps to work on Intel Enterprise Gaming PCs. Brian Cantrell as Elon Musk Computers are awesome Matt and JJ can always go to GIECO. I'll take the more. Really good surfers Rundown Dell Dell's AI Server Business Now Bigger Than VMware Used To Be (https://www.nextplatform.com/2024/08/30/dells-ai-server-business-now-bigger-than-vmware-used-to-be/) There's a lot of private cloud out there (https://newsletter.cote.io/p/theres-a-lot-of-private-cloud-out) OpenStack US insurer GEICO drops VMware for OpenStack (https://www.theregister.com/2024/08/28/geico_vmware_openstack_migration/) VMware Migration to OpenStack (https://www.openstack.org/vmware-migration-to-openstack) King Making (https://cloudedjudgement.substack.com/p/clouded-judgement-9624-king-making?utm_source=post-email-title&publication_id=56878&post_id=148500331&utm_campaign=email-post-title&isFreemail=true&r=2l9&triedRedirect=true&utm_medium=email) Relevant to your Interests Nvidia CEO Jensen Huang Surprised by Skeptics (https://www.bloomberg.com/news/newsletters/2024-09-02/nvidia-ceo-jensen-huang-surprised-by-skeptics) Nvidia Has Held Discussions About Joining OpenAI's Funding Round (https://www.bloomberg.com/news/articles/2024-08-29/nvidia-has-held-discussions-about-joining-openai-s-funding-round) Anthropic launches Claude Enterprise plan to compete with OpenAI (https://techcrunch.com/2024/09/04/anthropic-launches-claude-enterprise-plan-to-compete-with-openai/) What's Behind Elastic's Unexpected Return to Open Source? (https://thenewstack.io/whats-behind-elastics-unexpected-return-to-open-source/) The startup teaching your computer how to smell (https://thehustle.co/news/the-startup-teaching-your-computer-how-to-smell) Automatically summarize Word documents with Copilot (https://techcommunity.microsoft.com/t5/microsoft-365-insider-blog/automatically-summarize-word-documents-with-copilot/ba-p/4231202) Intel's Lunar Lake Looks Like a Home Run (https://finance.yahoo.com/news/intels-lunar-lake-looks-home-112000963.html) AT&T sues Broadcom for refusing to renew perpetual license support (https://arstechnica.com/information-technology/2024/09/att-sues-broadcom-for-refusing-to-renew-perpetual-license-support/) Red Hat Enterprise Linux AI (https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux/ai) The Self-Destruction of Open Source Software (https://lunduke.substack.com/p/the-self-destruction-of-open-source) Confluent acquires streaming data startup WarpStream (https://techcrunch.com/2024/09/09/confluent-acquires-streaming-data-startup-warpstream/) There are almost no IPOs. (https://x.com/chrisfralic/status/1833651875046105302?s=46&t=zgzybiDdIcGuQ_7WuoOX0A) Amazon congratulates itself for AI code that mostly works (https://www.theregister.com/2024/09/05/amazon_q_developer_gartner/) Charles Schwab Adopts PostgreSQL (With VMware Tanzu) (https://thenewstack.io/charles-schwab-adopts-postgresql-with-vmware-tanzu/) Sponsor Nasuni: Head to nasuni.com/software (https://bit.ly/3MvMDoY) and see how it can revolutionize your data infrastructure today! Nonsense Delta, Other Airline Loyalty Programs Are Being Probed by US (https://www.bloomberg.com/news/articles/2024-09-05/delta-dal-american-aal-airline-loyalty-programs-under-investigation) The 35-Year-Old CEO Plotting Red Lobster's Comeback (https://www.wsj.com/business/hospitality/the-35-year-old-ceo-plotting-red-lobsters-comeback-3c79d1a3) New Starbucks CEO Brian Niccol outlines priorities to end coffee chain's slump (https://www.cnbc.com/2024/09/10/new-starbucks-ceo-brian-niccol-outlines-plans-for-business.html) Historic Newspaper Uses Janky AI Newscasters Instead of Human Journalists (https://www.404media.co/historic-newspaper-uses-janky-ai-newscasters-instead-of-human-journalists/) Conferences SREday London 2024 (https://sreday.com/2024-london/), Sept 19–20, 2024. Coté speaking, 20% off with code SRE20DAY. Cloud Foundry Day EU (https://events.linuxfoundation.org/cloud-foundry-day-europe/), Karlsruhe, GER, Oct 9, 2024, 20% off with code CFEU24VMW. VMware Explore Barcelona (https://www.vmware.com/explore/eu), Nov 4-7, 2024. Coté speaking. SREday Amsterdam (https://sreday.com/2024-amsterdam/), Nov 21, 2024. Coté speaking (https://sreday.com/2024-amsterdam/Michael_Cote_VMwarePivotal_We_Fear_Change), 20% off with code SRE20DAY. SDT News & Community Join our Slack community (https://softwaredefinedtalk.slack.com/join/shared_invite/zt-1hn55iv5d-UTfN7mVX1D9D5ExRt3ZJYQ#/shared-invite/email) Email the show: questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com) Free stickers: Email your address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) Follow us on social media: Twitter (https://twitter.com/softwaredeftalk), Threads (https://www.threads.net/@softwaredefinedtalk), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com) Watch us on: Twitch (https://www.twitch.tv/sdtpodcast), YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured), Instagram (https://www.instagram.com/softwaredefinedtalk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk) Book offer: Use code SDT for $20 off "Digital WTF" by Coté (https://leanpub.com/digitalwtf/c/sdt) Sponsor the show (https://www.softwaredefinedtalk.com/ads): ads@softwaredefinedtalk.com (mailto:ads@softwaredefinedtalk.com) Recommendations Brandon: Rebel Ridge (https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://www.netflix.com/title/81157729&ved=2ahUKEwjCjfjMoLmIAxUuMdAFHW1AGn0QFnoECEMQAQ&usg=AOvVaw2-SZ5c5q-XeQL3kiJU9brc) Cloud News of the Month - August 2024 (https://www.thecloudcast.net/2024/09/cloud-news-of-month-august-2024.html) Matt: Interstellar (https://www.imdb.com/title/tt0816692/) Coté: Reino Slippers (https://finlaysonshop.com/products/reino-slippers). Photo Credits Header (https://unsplash.com/photos/people-surfing-on-waves-5__FobjBei8) Artwork (https://unsplash.com/photos/a-close-up-of-a-board-with-wires-attached-to-it-vtg8tAdoWVQ)

In this episode of the CTO Advisor Podcast, Keith Townsend and guest Jason Benedicic dive deep into the challenges and opportunities surrounding private cloud solutions. As businesses grapple with the complexity of building private clouds, this conversation covers: The evolution of cloud strategies, from OpenStack to Kubernetes and VMware. The growing role of Kubernetes in [...]

In this MOSE Short segment Stefano Maffulli, Ildiko and Phil talk about the early days of the OpenStack community.With one dominant contributing company at the beginning, it was important to put careful planning and effort into setting up the community to be able to grow and diversify. That included an open governance, and what you might expect less, a marketing budget!It is key to bring the technology and artifacts a community is working on to the people who would use them. This is where marketing plays a crucial role, that many people, communities and companies are underutilizing by not using the forums and avenues to talk directly about the open source projects. Hosted on Acast. See acast.com/privacy for more information.

Join the conversation as host Paul Spain and Seeby Woodhouse (Voyager) explore NZ Post's hydrogen-powered trucks, Trans-Tasman space research projects, the ethical implications of AI, Seeby's intriguing 5-day experience with Tesla's full self-driving capabilities on New Zealand roads, and the development of autonomous vehicles. Plus, a look at Voyager's migration to OpenStack and the competitive cloud services landscape and more. A big thanks to our show partners One NZ, Spark, HP, 2degrees and Gorilla Technology.

In this episode, more interviews from KubeCon Paris.I speak with Dinesh from CIVO, a European cloud-native hosting company, and Thierry of the Open Infrastructure Foundation, whose projects typically power data centres.This episode is powered by magic mind, a little green bottle of goodness that helps your focus and energy. Head over to magicmind.com/chinchillasqueaks and use the code "CHINCHILLASQUEAKS20" for 48% of subscriptions or 20% off one-time purchases.Want to come see me do sounds and lights for a play in Berlin?https://www.eventbrite.de/e/the-house-of-bernarda-alba-tickets-920747038177

Send us a Text Message.CERN, the European Nuclear Research Centre, is celebrating its 70th birthday in 2024 and I want to give you a glimpse of the kind of work that happens there. Meet Spyridon Trigazis, who will take us through CERN's infrastructure and how they use OpenStack and Kubernetes to "keep the lights" on. https://home.cern/ CERN homepage https://www.openstack.org OpenStackhttps://kubernetes.io Kuberneteshttps://inspirehep.net/authors/1907786 A selection of the work Spyridon has been involved withhttps://alumni.cern The CERN alumni networkhttps://home.cern/summer-student-programme the summer student programme. Applications for 2024 are closed now, but I am sure there will be another on in '25Support the Show.Thank you for listening and your ongoing support. It means the world to us! Support the show on Patreon https://www.patreon.com/codeforthought Get in touch: Email mailto:code4thought@proton.me UK RSE Slack (ukrse.slack.com): @code4thought or @piddie US RSE Slack (usrse.slack.com): @Peter Schmidt Mastodon: https://fosstodon.org/@code4thought or @code4thought@fosstodon.org LinkedIn: https://www.linkedin.com/in/pweschmidt/ (personal Profile)LinkedIn: https://www.linkedin.com/company/codeforthought/ (Code for Thought Profile) This podcast is licensed under the Creative Commons Licence: https://creativecommons.org/licenses/by-sa/4.0/

In this episode of Pathmonk Presents, we had the pleasure of hosting Lauren Morley, a marketing automation specialist from OpenMetal. OpenMetal is a pioneering company in the cloud infrastructure sector, focusing on transforming OpenStack deployment.  Lauren shared invaluable insights into how OpenMetal's innovative marketing strategies, such as content creation, organic reach, and automation, have reshaped their approach to customer acquisition.  Dive into this episode to learn how effective marketing can simplify complex cloud solutions and drive business growth.   

Mark Collier (Chief Operating Officer @ OpenInfra Foundation) talks about the advantages of open source AI and the intersection of OSS and AI transparency, safety, and potential regulations.SHOW: 821CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwNEW TO CLOUD? CHECK OUT OUR OTHER PODCAST - "CLOUDCAST BASICS"SPONSOR:See what graphs can do for you at Neo4j.com/developerSHOW NOTES:Mark's Talk at ATOEU AI Act PassesHow Tech Giants Cut Corners Harvest DataThe EU Guide Act - A Guide for DevelopersOpenInfra FoundationTopic 1 - Our topic for today is AI Safety and Regulation. I saw our guest speak at All Things Open here in Raleigh late last year and he is also a Cloudcast alumnus having been on the show previously talking about OpenStack and the OpenInfra Foundation. We'd like to welcome Mark Collier (Chief Operating Officer @ OpenInfra Foundation) for this discussion. Mark, welcome to the show.Topic 2 - There's a lot of news today about AI safety and regulation. The industry also seems to be caught up in an AI arms race of who has the bigger model, faster model, etc. OpenAI have become the early category leader but they might have started with good intentions, but, contrary to their name, they aren't open… at all.  One message in your talk is how open-source software will prevent the coming of the “AI overlords”. Tell everyone a bit of what you mean by this. What is the problem we are facing and many may not even realize it.Topic 3 - I don't want to call you old (I think we are about the same age), but you've seen some things. You've also been around OSS and foundations for a bit now. How can open source solve the problem?Topic 4 - We hear a lot about AI regulation, but this seems to be a moving target. What is both the current and future state of AI regulation? In my opinion, we haven't seen a lot of successful regulations to date. We saw recently the EU pass an AI Act. Is this the first of many? The start of a trend?Topic 5 - Let's talk about the “day job”. What's new with OpenInfra Foundation these days?Topic 6 -  OpenStack releases are still going strong and you've even run out of letters on OpenStack releases and have rolled around on the alphabet and are back to C. This is the 29th release of OpenStack. What's the news for the Caracal release?FEEDBACK?Email: show at the cloudcast dot netTwitter: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

For this special edition of TCP Talks, Justin and Jonathan are joined by Travis Runty, CTO of Public Cloud with Rackspace Technology. In today's interview, they discuss being accidentally multi cloud, public vs private cloud, and cloud migration, and best practices when assisting clients with their cloud journeys.  Background Rackspace Technology, commonly known as Rackspace, is a leading multi-cloud solutions provider headquartered in San Antonio, Texas, United States. Founded in 1998, Rackspace has established itself as a trusted partner for businesses seeking expertise in managing and optimizing their cloud environments. The company offers a wide range of services aimed at helping organizations navigate the complexities of cloud computing, including cloud migration, managed hosting, security, data analytics, and application modernization. Rackspace supports various cloud platforms, including AWS, Azure, and GCP, among others.  Rackspace prides itself on its “Fanatical Experience” approach, which emphasizes delivering exceptional customer support and service. This commitment to customer satisfaction has contributed to Rackspace’s reputation as a reliable and customer-centric provider in the cloud computing industry.  Meet Travis Runty, CTO of Public Cloud for Rackspace Technology Beginning his career with Rackspace as a Linux engineer, Travis has spent the last 15 years working his way through multiple divisions of the company, including 10 years in senior and director level positions. Most recently, Travis served as VP of Technical Support of Global Cloud Operations from 2020-2022.  Travis is extremely passionate about building and leading high performance engineering teams and delivering innovative solutions. Most recently, as a member of their technology council, Travis wrote an article for Forbes – Building a Cloud-Savvy Workforce: Empowering Your Team for Success – where he discussed best practices for prioritizing workforce enablement, especially when it comes to training and transformation initiatives.  Interview Notes: In the main show, TCP has been talking a lot about Cloud / hybrid cloud / multi-cloud and repatriating data back to on prem, and today's guest knows all about those topics.  Rackspace has had quite a few phases in their journey to public cloud – including building a data center in an unused mall, introducing managed services, creating partnerships with VMware, an attempt to go head to head with the hyperscalers, and then ultimately focusing on public cloud and instead partnering with the hyperscalers.  Rackspace has both a focus on private and public cloud; when it comes to private cloud they focus mainly on VMware and OpenStack, whereas in the public cloud side, Rackspace partners with the hyperscalers to assist clients with their cloud journey.  Quotes from today's show  Travis: “We want to make sure that when a customer goes on their public cloud journey, that they actually have a robust strategy that is going to be effective. From there, we're able to leverage our professional services teams to make sure that they can realize that transformation, and hopefully there *is* a transformation, and it's not just a lift and shift.” Travis: “A conflict that we continuously have to strike the balance of is when do we apply a cloud native solution, and where do we apply the Rackspace elements on top. The hyperscalers techno

This week, we discuss Matt Asay accusing OpenTufu of "lifting code" and recap the Google Next '24. announcements. Plus, we share some thoughts on camera placement and offer listeners a chance to get free coffee beans. Watch the YouTube Live Recording of Episode (https://www.youtube.com/watch?v=2VBJU8UdLOA) 462 (https://www.youtube.com/watch?v=2VBJU8UdLOA) Runner-up Titles Hey, I'm VP of Cables, not VP of Hubs. Well, I still have meetings. The Cote' Experience ClosedTofu Our Cloud is Huge(tm) Rundown Matt Asay vs. OpenTofu OpenTofu may be showing us the wrong way to fork (https://www.infoworld.com/article/3714980/opentofu-may-be-showing-us-the-wrong-way-to-fork.html) OpenTofu vehemently disagrees with any suggestion that it misappropriated (https://twitter.com/opentofuorg/status/1776398008558493991?s=46&t=kiCCT8LlOOqj0WYcmUddTg) Matt Asay (https://x.com/mjasay/status/1776635226124632423?s=46&t=EoCoteGkQEahPpAJ_HYRpg) Follow up Tweet Bryan Cantrill (https://x.com/bcantrill/status/1775962870762844212) calls it an extraordinarily serious accusation Adam Jacob says “incendiary claim with no actual facts backing it up. The code looks completely different. (https://twitter.com/adamhjk/status/1775663819693703674) Google Cloud Next '24 Introducing Google's new Arm-based CPU (https://cloud.google.com/blog/products/compute/introducing-googles-new-arm-based-cpu/) Google's first Arm-based CPU will challenge Microsoft and Amazon in the AI race (https://www.theverge.com/2024/4/9/24125074/google-axion-arm-cpu-ai-chips-cloud-server-data-center) Welcome to Google Cloud Next ‘24 | Google Cloud Blog (https://cloud.google.com/blog/topics/google-cloud-next/welcome-to-google-cloud-next24) Gemini for Google Cloud is here | Google Cloud Blog (https://cloud.google.com/blog/products/ai-machine-learning/gemini-for-google-cloud-is-here) Google Cloud Next '24 Opening Keynote (https://www.youtube.com/watch?v=V6DJYGn2SFk) Google Cloud Next '24 Developer Keynote (https://www.youtube.com/watch?v=KMH5OcW5UYw) Relevant to your Interests WhatsApp goes down in Meta's second big outage this year (https://techcrunch.com/2024/04/03/whatsapp-goes-down-in-metas-second-big-outage-this-year/) Alphabet is weighing an offer for $32 billion marketing tech firm HubSpot, sources say (https://finance.yahoo.com/news/exclusive-google-parent-alphabet-weighs-134439629.html) OpenStack debuts its first easy-to-upgrade release (https://www.theregister.com/2024/04/04/openstack_caracal_released/) No, Amazon Isn't Killing Just Walk Out But Rather “Pushing Hard” On It (https://www.forrester.com/blogs/no-amazon-isnt-killing-just-walk-out-but-rather-pushing-hard-in-it/) Substack Is Setting Writers Up For A Twitter-Style Implosion (https://homewiththearmadillo.blog/2024/04/02/substack-is-setting-writers-up-for-a-twitter-style-implosion/comment-page-1/#comments) Why WASI Preview 2 Makes WebAssembly Production Ready (https://thenewstack.io/why-wasi-preview-2-makes-webassembly-production-ready/) Why Broadcom may set the future of software licensing (https://www.theregister.com/2024/04/05/the_world_is_watching_broadcom/) Rust developers at Google twice as productive as C++ teams (https://www.theregister.com/2024/03/31/rust_google_c/) New York City defends AI chatbot that advised entrepreneurs to break laws (https://www.reuters.com/technology/new-york-city-defends-ai-chatbot-that-advised-entrepreneurs-break-laws-2024-04-04/) Apple opens the App Store to retro game emulators (https://www.theverge.com/2024/4/5/24122341/apple-app-store-game-emulators-super-apps) The Status of Just Walk Out, TSMC Gets CHIPS Act Grant (https://stratechery.com/2024/the-status-of-just-walk-out-tsmc-gets-chips-act-grant/) Baldur's Gate 3 Dev Larian's Publishing Director Calls Games Industry Layoffs an 'Avoidable F*ck Up' - IGN (https://www.ign.com/articles/baldurs-gate-3-dev-larians-publishing-director-calls-games-industry-an-avoidable-fck-up) Access: A New Portal for Managing Internal Authorization (https://discord.com/blog/access-a-new-portal-for-managing-internal-authorization) Android's upgraded Find My Device network is here (https://www.theverge.com/2024/4/8/24124174/android-find-my-device-network-offline-tracker-tag-chipolo-pebblebee) Gemini 1.5 Makes a Scholarly Connection that Took Me Years to Find (https://www.reddit.com/r/singularity/comments/1bkcjs4/gemini_15_makes_a_scholarly_connection_that_took/) Android's upgraded Find My Device network is here (https://www.theverge.com/2024/4/8/24124174/android-find-my-device-network-offline-tracker-tag-chipolo-pebblebee) KKR Weighs Sale or IPO for $15 Billion BMC Software (https://www.bloomberg.com/news/articles/2024-04-10/kkr-is-said-to-weigh-sale-or-ipo-for-15-billion-bmc-software?utm_source=twitter&utm_campaign=socialflow-organic&utm_content=tech&cmpid%3D=socialflow-twitter-tech&utm_medium=social&embedded-checkout=true) Nonsense Dude Perfect scores $100M+ investment from Highmount Capital (https://www.axios.com/2024/04/09/dude-perfect-investment-highmount-capital) Costco selling as much as $200M in gold bars per month, Wells Fargo estimates (https://nypost.com/2024/04/10/business/costco-selling-as-much-as-200m-in-gold-bars-per-month-wells-fargo/) Listener Feedback The first person to send their United States postal address to sdt@newinstancecoffee.com (mailto:sdt@newinstancecoffee.com) will receive a bag of Dawn Python (https://www.newinstancecoffee.com/dawn-python-v2-available/) Coffee Beans from New Instance Coffee (https://www.newinstancecoffee.com/). Conferences Open Source Summit North America (https://events.linuxfoundation.org/open-source-summit-north-america/), Seattle April 16-18. Matt's speaking. NDC Oslo (https://substack.com/redirect/8de3819c-db2b-47c8-bd7a-f0a40103de9e?j=eyJ1IjoiMmQ0byJ9.QKaKsDzwnXK5ipYhX0mLOvRP3vpk_3o2b5dd3FXmAkw), Coté speaking (https://substack.com/redirect/41e821af-36ba-4dbb-993c-20755d5f040a?j=eyJ1IjoiMmQ0byJ9.QKaKsDzwnXK5ipYhX0mLOvRP3vpk_3o2b5dd3FXmAkw), June 12th. DevOpsDays Amsterdam (https://devopsdays.org/events/2024-amsterdam/welcome/), June 19-21, 2024, Coté speaking. DevOpsDays Birmingham, August 19–21, 2024 (https://devopsdays.org/events/2024-birmingham-al/welcome/). SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us: Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk), Threads (https://www.threads.net/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: Node.js: The Documentary (https://www.youtube.com/watch?v=LB8KwiiUGy0) How A Small Team of Developers Created React at Facebook | React.js: The Documentary (https://www.youtube.com/watch?v=8pDqJVdNa44) Matt: Qatar Airlines Stopover Tour (https://www.qatarairways.com/en/offers/qatar-stopover.html) Coté: Noah Kalina YouTubes (https://www.youtube.com/@NoahKalina) (follow-up: he's three years younger than Coté (https://en.wikipedia.org/wiki/Noah_Kalina), so same cultural cohort as theorized.) Photo Credits Header (https://unsplash.com/s/photos/Coffee-Beans?orientation=landscape) Artwork (https://unsplash.com/photos/a-computer-screen-with-a-bunch-of-text-on-it-1LLh8k2_YFk)

For years, the CNCF has been the central governance body for cloud-native projects. But are there too many projects now? What if the CNCF was less governance and more like private equity?SHOW: 804CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:Want to win a Tesla Cybertruck or $100,000? Enter the WS02 Choreo Code Challenge (before August 23rd)WSO2 Choreo - Why build a platform? Just add developers insteadSHOW NOTES:CNCF LandscapeCNCF Trail MapWHY DOESN'T THE CNCF RECOMMEND A CLOUD-NATIVE STACK? Originally the CNCF was just trying to get projects to use them for governance. Many people wanted them to “define” a cloud-native stack. Defining a stack would have held back their business model - accepting projects and adding sponsorsHOW MANY PROJECTS WOULD GET “CNCF APPROVED” IF THEY TOOK A PRIVATE EQUITY APPROACH?CNCF currently has 184 projects, up 4x over the last 4 years. 14% graduates, 20% incubating, 62% sandbox Does the CNCF suffer from the “Big Tent” problem that caused so many issues with OpenStack? KubeCon keynotes are just a list of projects giving status updates - they could be an email. How many projects should the CNCF sponsor? How many categories should remain?How would a private equity group apply metrics to CNCF projects? FEEDBACK?Email: show at the cloudcast dot netTwitter: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

As the racquet meets the ball, there's more at play than just a game of tennis; there's a world of strategy, resilience, and adaptability that mirrors the high-stakes realm of tech entrepreneurship. That's something Cole Crawford, the tech entrepreneur and former tennis pro, knows all too well. Join us on an exhilarating journey where we trace Cole's footsteps from the baseline of the court to the frontline of cutting-edge technology. We cover the inception of Vapor IO and how it's redefining the internet landscape, delve into the synergy between sportsmanship and business savvy, and discuss the potential of edge computing and AI to revolutionize industries from healthcare to sports betting.Ever wondered how being an introvert shapes a leader? Get an intimate look at the intricacies of introversion as Cole and I unpack how this trait has played a pivotal role in the competitive worlds of both - tennis and business. From overcoming shyness to harnessing self-awareness as a strength, we unpack the unique challenges and advantages introverts face. We also celebrate the joy and challenges of past job roles—from Cole's days of embracing Linux to the thrill of building OpenStack—and the visionary steps that led to the foundation of Vapor IO. It's a tale of technological disruption, musical creativity, and the drive that blazes the trail in the startup landscape.Prepare to have your perspectives challenged on everything from AI's role in our daily lives to the future of immersive technology. We explore the transformative potential of edge computing, the interplay with 5G networks, and how these advancements could change the way we communicate and experience the world. Cole shares his insights on AI fall detection in healthcare, the rise of micro-betting in sports, and the human side of technology—from VR for memory preservation to mental health and bridging the educational divide. This episode isn't just a podcast; it's an invitation to explore the profound impacts of our choices and the relentless pursuit to enrich the human experience through innovation.Resources:  https://www.vapor.io/ ︱ LinkedIn ︱InstagramLEORÊVER COMPRESSION AND ACTIVEWEAR Get 10% off Loerêver Balanced Compression and Activewear to elevate your confidence and performance8 EIGHT SLEEP Save $200 on 8Sleep and get better quality and deeper sleep with automatic temperature adjustmentDisclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Thank you for listening. If you enjoyed this episode, share it with someone who may enjoy it as well, and consider leaving a review on Apple Podcasts & Spotify. You can also submit your feedback directly on my website. Follow @GrandSlamJourney on Instagram, Facebook, Twitter or join the community on LinkedIn. This content is also available on Substack and YouTube.

Now that businesses have deployed modern applications in the cloud they are starting to ask whether it might be more attractive to run these on-premises. This episode of the On-Premise IT podcast features Jason Benedicic, Camberley Bates, and Ian Sanderson discussing the pros and cons of cloud repatriation with Stephen Foskett. A recent blog post by 37 Signals got the Tech Field Day delegates talking about the reality of running modern applications in enterprise-owned clouds, whether in the datacenter or co-located. Certainly the hardware and software are available to move applications on-prem, and some workloads may be better served this way. Most of the necessary components to run modern web applications are available on-prem, from Kubernetes to Postgres to Kafka, but these can prove difficult to manage, which is one of the things as-a-service customers are paying for. Looking back to the debut of OpenStack, enterprises have wanted to run applications in-house but they found it too difficult to manage. OpenShift is much more attractive thanks to the support and integration of the platform, but many customers have financial and administrative reasons for as-a-service deployment. It might not be a mass exodus, but there are plenty of examples of repatriation of modern applications. © Gestalt IT, LLC for Gestalt IT: Cloud Repatriation is Really Happening

Now that businesses have deployed modern applications in the cloud they are starting to ask whether it might be more attractive to run these on-premises. This episode of the On-Premise IT podcast features Jason Benedicic, Camberley Bates, and Ian Sanderson discussing the pros and cons of cloud repatriation with Stephen Foskett. A recent blog post by 37 Signals got the Tech Field Day delegates talking about the reality of running modern applications in enterprise-owned clouds, whether in the datacenter or co-located. Certainly the hardware and software are available to move applications on-prem, and some workloads may be better served this way. Most of the necessary components to run modern web applications are available on-prem, from Kubernetes to Postgres to Kafka, but these can prove difficult to manage, which is one of the things as-a-service customers are paying for. Looking back to the debut of OpenStack, enterprises have wanted to run applications in-house but they found it too difficult to manage. OpenShift is much more attractive thanks to the support and integration of the platform, but many customers have financial and administrative reasons for as-a-service deployment. It might not be a mass exodus, but there are plenty of examples of repatriation of modern applications. © Gestalt IT, LLC for Gestalt IT: Cloud Repatriation is Really Happening

As Docker talks about their successes and failures after 10 years, what lessons can be learned by open source companies, projects and foundations over the past decade.SHOW: 764CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwCHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"SHOW SPONSORS:CloudZero – Cloud Cost Visibility and Savings​​CloudZero provides immediate and ongoing savings with 100% visibility into your total cloud spendReduce the complexities of protecting your workloads and applications in a multi-cloud environment. Panoptica provides comprehensive cloud workload protection integrated with API security to protect the entire application lifecycle.  Learn more about Panoptica at panoptica.appDatadog Monitoring: Modern Monitoring and AnalyticsStart monitoring your infrastructure, applications, logs and security in one place with a free 14 day Datadog trial. Listeners of The Cloudcast will also receive a free Datadog T-shirt.SHOW NOTES:Docker at 10 - Three Things we got Right, Three Things we got Wrong (TNS)Lessons Learned from Docker (Eps.505 - 2021)Lessons Learned from OpenShift (Eps. 489 - 2021)If Kubernetes is Boring, what's next? (Eps.509 - 2021)IT'S HARD TO SEE THE FOREST FOR THE TREESDocker was the transition between OpenStack (bad foundation) and Kubernetes (CNCF)Was Docker a Community or a Cult? How did Leadership work?Docker was stuck between VMware and DevelopersWHAT HAS THE INDUSTRY LEARNED FROM THE DOCKER DAYS?Customers and communities are very hesitant to adopt another single-vendor offeringCould Docker have succeeded as a “free” implementation?As much as DevOps and PlatformEngineering are happening, it's tough to have an “in between” technology (used by both Infra and AppDev)It's OK to adapt your monetization model, but it's not OK to not have oneOpen source can't be the driving force of a business. It's not a charity. If somebody offers you $3B, maybe consider taking it….FEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnet

Welcome episode 228 of the Cloud Pod podcast - where the forecast is always cloudy! This week your hosts Justin, Jonathan, Matthew and Ryan are taking a look at Magic Quadrant, Gemini AI, and GraalOS - along with all the latest news from OCI, Google, AWS, and Azure.  Titles we almost went with this week: The CloudPod wonders if Anthropic's Santa Clause will bring us everything we want in an AI Bot. The Cloud Pod recommends protection to achieve Safer Google rides the gemini rocket to AI JPB The only Copilot I need Azure, is Booze GraalOS, or what we now call ‘the noise our CFO makes when he receives the Oracle audit bills' The hosts of the Cloud pod would like to understand how to properly pronounce GraalOS Is Oracle even on the magic quadrant for cloud? RedHat Puts lipstick on the pig and calls it OpenStack A big thanks to this week's sponsor: Foghorn Consulting provides top-notch cloud and DevOps engineers to the world's most innovative companies. Initiatives stalled because you have trouble hiring?  Foghorn can be burning down your DevOps and Cloud backlogs as soon as next week.

In this episode, Woody dives into the world of cloud security using open source systems with our special guest, Susan Hinrichs.   Susan Hinrichs, Chief Scientist at Aviatrix, is a multifaceted professional with a strong background in the open source networking and security space. As a designer and implementer, she has contributed significantly to the development of distributed cloud firewall. Susan's expertise extends well beyond traditional networking, encompassing diverse areas such as cloud routing, application security, policy-based traffic engineering, and distributed systems.   Throughout this insightful conversation, Susan discusses the advantages of open source platforms, Aviatrix contributions to the open source community, and the open source DNA of the Aviatrix Distributed Cloud Firewall. Susan and Woody also explore possible directions for Distributed Cloud Firewall and the role that AI and ML could play in network security.   Learn more about Altitude and Host Woody: https://aviatrix.com/altitude/ Susan's LinkedIn: https://www.linkedin.com/in/shinrich/  Timestamps: [00:02:11] Group responsible for traffic termination and scrubbing. Used open source software and contributed back. [00:06:55] Extended Berkeley Packet Filter (eBPF) enables efficient traffic analysis in kernel space, particularly for dropping network traffic at low levels with minimal effort. It provides a more cost-effective alternative to IP tables for implementing firewall policies. [00:10:07] Approach: Not everyone is the root. All processes aren't root. Need to elevate. Complicated product made simple. [00:14:27] Open Stack's limitations revealed as enterprise-scale businesses require dedicated specialists, making it costly. Distributed cloud firewall innovates multicloud security. Scaling security in the cloud is challenging due to layer 3 and up the stack complexities. [00:16:38] Distributed firewall challenges and solutions summarized. [00:21:53] Smart groups are created with tags on VMs, subnets, and VPCs. These groups are used to create rules for traffic routing. With Aviatrix fabric, gateways are protected, and traffic routes are understood. The controller analyzes gateways and enforces rules accordingly. Rules are pushed or pulled to the gateways. [00:26:15] Security group orchestration across different cloud platforms has limitations due to varying models and rule limits. Difficulties arise when translating intermixed allows and denies into only allows, potentially causing networks to split and requiring more rules. Despite extensive work, there are cases where policy expression is not possible. Other tools, like VMware and Cisco, offer similar orchestration capabilities, but the physical enforcement points may still restrict the unified view presented to customers. [00:30:30] Moving towards intrusion protection, analytics, and service mesh for enhanced security. [00:34:05] The impact of AI and machine learning on security systems. [00:35:16] AI helps with alarm fatigue and data correlation.

In this vignette of The 5G Factor, Ron Westfall and Steve Dickens provide their perspective on Red Hat becoming the primary infrastructure platform for Nokia's Core Network Applications. The conversation focused on: Red Hat Becomes the Primary Infrastructure Platform for Nokia's Core Network Applications. Nokia and Red Hat reached an agreement to integrate Nokia's core network applications with Red Hat OpenStack Platform and RedHat OpenShift. 350 personnel at Nokia will be transferring to Red Hat as Nokia moves on from developing the platforms that host its software. The duo will jointly support and evolve existing Nokia Container Services (NCS) and Nokia CloudBand Infrastructure Software (CBIS) customers while developing a path for customers to migrate to Red Hat's platforms. We delve into the implications for the 5G ecosystem and telco cloud journeys.

Today we're going deep on software-defined networking for containers and OpenStack with sponsor Juniper Networks. Juniper has revamped its approach to secure networking for telcos and telco cloud-delivered services with Juniper's Cloud-Native Contrail Networking or CN2 software. CN2 lets you automate the creation of network connections for containers and for virtual machines while also providing routing, security, segmentation and isolation of workloads. Our guest and guide into the guts of Cloud-Native Contrail Networking, hereafter referred to as CN2, is Nick Davey. Nick is Director of Product Management for SDN and Telco Cloud technologies.

Today we're going deep on software-defined networking for containers and OpenStack with sponsor Juniper Networks. Juniper has revamped its approach to secure networking for telcos and telco cloud-delivered services with Juniper's Cloud-Native Contrail Networking or CN2 software. CN2 lets you automate the creation of network connections for containers and for virtual machines while also providing routing, security, segmentation and isolation of workloads. Our guest and guide into the guts of Cloud-Native Contrail Networking, hereafter referred to as CN2, is Nick Davey. Nick is Director of Product Management for SDN and Telco Cloud technologies. The post Heavy Networking 686: Juniper Cloud-Native Contrail Networking CN2 (Sponsored) appeared first on Packet Pushers.

Today we're going deep on software-defined networking for containers and OpenStack with sponsor Juniper Networks. Juniper has revamped its approach to secure networking for telcos and telco cloud-delivered services with Juniper's Cloud-Native Contrail Networking or CN2 software. CN2 lets you automate the creation of network connections for containers and for virtual machines while also providing routing, security, segmentation and isolation of workloads. Our guest and guide into the guts of Cloud-Native Contrail Networking, hereafter referred to as CN2, is Nick Davey. Nick is Director of Product Management for SDN and Telco Cloud technologies.

Today we're going deep on software-defined networking for containers and OpenStack with sponsor Juniper Networks. Juniper has revamped its approach to secure networking for telcos and telco cloud-delivered services with Juniper's Cloud-Native Contrail Networking or CN2 software. CN2 lets you automate the creation of network connections for containers and for virtual machines while also providing routing, security, segmentation and isolation of workloads. Our guest and guide into the guts of Cloud-Native Contrail Networking, hereafter referred to as CN2, is Nick Davey. Nick is Director of Product Management for SDN and Telco Cloud technologies. The post Heavy Networking 686: Juniper Cloud-Native Contrail Networking CN2 (Sponsored) appeared first on Packet Pushers.

Today we're going deep on software-defined networking for containers and OpenStack with sponsor Juniper Networks. Juniper has revamped its approach to secure networking for telcos and telco cloud-delivered services with Juniper's Cloud-Native Contrail Networking or CN2 software. CN2 lets you automate the creation of network connections for containers and for virtual machines while also providing routing, security, segmentation and isolation of workloads. Our guest and guide into the guts of Cloud-Native Contrail Networking, hereafter referred to as CN2, is Nick Davey. Nick is Director of Product Management for SDN and Telco Cloud technologies. The post Heavy Networking 686: Juniper Cloud-Native Contrail Networking CN2 (Sponsored) appeared first on Packet Pushers.

Today we're going deep on software-defined networking for containers and OpenStack with sponsor Juniper Networks. Juniper has revamped its approach to secure networking for telcos and telco cloud-delivered services with Juniper's Cloud-Native Contrail Networking or CN2 software. CN2 lets you automate the creation of network connections for containers and for virtual machines while also providing routing, security, segmentation and isolation of workloads. Our guest and guide into the guts of Cloud-Native Contrail Networking, hereafter referred to as CN2, is Nick Davey. Nick is Director of Product Management for SDN and Telco Cloud technologies.

Jon Toor (CMO @CloudianStorage) talks about the history and evolution of object storage, the rise of enterprise class object storage, and the changing economics of cloud storage.SHOW: 725CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotwNEW TO CLOUD? CHECK OUT - "CLOUDCAST BASICS"SHOW SPONSORS:CloudZero – Cloud Cost Visibility and Savings​​CloudZero provides immediate and ongoing savings with 100% visibility into your total cloud spendDatadog Application Monitoring: Modern Application Performance MonitoringGet started monitoring service dependencies to eliminate latency and errors and enhance your users app experience with a free 14 day Datadog trial. Listeners of The Cloudcast will also receive a free Datadog T-shirt.SHOW NOTES:Cloudian websiteTopic 1 - Welcome to the show Jon. Tell us a little bit about your background. Your career and Cloudian parallel in many ways.Topic 2 - Cloudian has been around since before object storage was cool. We first heard about Cloudian back in the OpenStack and early AWS S3 days. Object storage has come a long way. Can you help everyone frame where we were and where we are today?Topic 3 - We've seen the rise of Enterprise class, S3 compatible object storage for use cases like hybrid cloud, data sovereignty, and more recently analytics such as data lakehouses. Where are you seeing implementations these days as we've moved beyond basic, simple storage behind cloud backends.  Topic 4 - With the recent changes to the world economy, how much does economics come into conversations around the design of solutions. There's often a healthy tension between what is technically possible and what is economically feasible. How does that design conversation play out lately?Topic 5 - We used to talk about “Data Gravity” all the time. The concept for those unfamiliar is that data has a certain weight and attracts more data to existing sources and becomes hard to move over time. We haven't talked about it as much in recent years and we are seeing the rise of hybrid and multicloud solutions but folks often don't think about access to the data. Where are folks building large data sets? What are they using them for? Are they ever moving them?Topic 6 - Last question, Cloudian is well known for their partnerships, alliances and solutions. You partner with hardware companies, software companies, backup companies, public clouds, etc. It's quite a mix. Has this been a factor in Cloudian's longevity and tell everyone a little bit about how this came to be and how important you see this for the future. FEEDBACK?Email: show at the cloudcast dot netTwitter: @thecloudcastnet

Alex and Camila discuss security update management strategies after a recent outage at Datadog was attributed to a security update for systemd on Ubuntu, plus we look at security vulnerabilities in the Linux kernel, OpenStack, Synapse, OpenJDK and more.

The team are back from Prague and bring with them a new segment, drilling into recent academic research in the cybersecurity space - for this inaugural segment new team member Andrei looks at modelling of attacks against network intrusion detections systems, plus we cover the week in security updates looking at vulnerabilities in Django, Ruby, Linux kernel, Erlang, OpenStack and more.

https://fellow.app/supermanagers/nathan-trueblood-practicing-transformational-leadership-how-to-drive-change-through-influence/ Transformational leadership has a positive effect on mental health.  Leaders who adopt a transformational approach inspire others by encouraging team members to engage in creative thinking and tailoring their approach to the individual needs of each employee.   In episode #147, Nathan explains how to drive change within organizations by practicing transformational leadership.  Nathan Trueblood has many years of experience including working at companies like Box, Yahoo, EMC, Hadoop, OpenStack. He's a technologist, product leader, founder and mentor. Today, he is the founder of Trueblood Advisory.  Tune in to hear all about Nathan's leadership journey and the lessons learned along the way! . . . Like this episode? Be sure to leave a ⭐️⭐️⭐️⭐️⭐️ review and share the podcast with your colleagues. . . . TIME-STAMPED SHOW NOTES: [04:45] Distributed systems  [11:25] Delegating a problem versus task  [16:15] What is transformational leadership? [20:46] Transformational leaderships and product teams [24:17] Leading through influence [32:11] Coalition of the willing [37:46] Design alliances [40:40] Doing a calendar audit  44:57] Parting words of advice RESOURCES MENTIONED IN THIS EPISODE: Read Daisy Grewall's article Subscribe to the Supermanagers TLDR newsletter

Matt, Coté and guest host Barton George record live from KubeCon EU. They discuss the Keynotes, Amsterdam grocery stores, A.I. coverage by tech media and reminisce about OpenStack. Plus, some thoughts on the Breakfast Buffet… Runner-up Titles The CNCF invades Amsterdam So nice not to talk to anyone Kubecon EU 2023 recap Curve Fits Rundown Thanks to developer.dell.com (https://developer.dell.com) team for help with show production. KubeCon + CloudNativeCon Europe 2022 (http://KubeCon + CloudNativeCon Europe 2022) Self Scanning in Dirk (https://www.youtube.com/watch?v=6xraOeYb8po) Conferences DevOpsDays Austin 2023 (https://devopsdays.org/events/2023-austin/welcome/), May 4-5 SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Photo Credits Header (https://twitter.com/barton808/status/1648592307791314948/photo/1) Artwork (https://twitter.com/barton808/status/1649071653001785344) Special Guest: Barton George.

Ben Rometsch and Matt Althauser sit down with Shaun Campton, Principal Engineer at Tigera, who shares his experiences as a core developer on Project Calico. He talks about their origins of moving out of the era of doing forklift moves into OpenStack and down the development of network splitting, focusing more on a dynamic firewall approach. He opens up on his experiences writing their first 10,000 lines of code, their identity-based policy, and the value they are offering to clients. Shaun also provides insights on what may be next for Kubernetes and how open-source projects must get ready for any change ahead.

This week we discuss Docker's reversal, Amazon's return to office, Apple's headset, the state of the Metaverse and the rise of LLMs. Plus, Matt shares his sleep study experience and an after-show about Hawaii. Watch the YouTube Live Recording of Episode 408 (https://www.youtube.com/watch?v=VtLRMj8s_Fc) Runner-up Titles Tyranny of 16x9 College Sports of Mastodon Sleep Study NPS survey at the end Dependent on Goodwill This is best for the customer Worlds greatest employer Apple, we were counting on you Mechanized Mansplaining Rundown We're no longer sunsetting the Free Team plan (https://www.docker.com/blog/no-longer-sunsetting-the-free-team-plan/) Amazon's head of HR rejects employees' return-to-office petition (Insider) (https://artifact.news/s/-dZrO83ly0Q=) At Apple, Rare Dissent Over a New Product: Interactive Goggles (https://www.nytimes.com/2023/03/26/technology/apple-augmented-reality-dissent.html) Disney reportedly eliminates metaverse division in first round of layoffs (https://www.theverge.com/2023/3/28/23659691/disney-metaverse-job-cuts-eliminated?_hsmi=252164574) Cheating is All You Need (https://about.sourcegraph.com/blog/cheating-is-all-you-need) Relevant to your Interests Introducing World ID and SDK (https://worldcoin.org/blog/announcements/introducing-world-id-and-sdk?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) You Broke Reddit: The Pi-Day Outage (https://www.reddit.com/r/RedditEng/comments/11xx5o0/you_broke_reddit_the_piday_outage/) De-cloud and de-k8s — bringing our apps back home (https://dev.37signals.com/bringing-our-apps-back-home/) Venture Firms And Startups Are Returning To Government-Backed SVB In Droves (https://www.forbes.com/sites/emilymason/2023/03/19/vc-and-startups-are-returning-to-government-backed-svb-in-droves/?sh=783740c17dfc) OpenStack starts wrapping around the alphabet to name it's latest release. (https://twitter.com/sjvn/status/1639265814963527680) 51 Tips For Surviving in a BIG Company (https://www.linkedin.com/pulse/51-rules-how-survive-big-company-jeremy-connell-waite/) New York Times touts continued Wordle success (https://www.axios.com/newsletters/axios-login-c755db47-b0d4-471d-9f55-b8cf1218c75c.html?chunk=2&utm_term=emshare#story2) SVB Capital Owned Pieces Of Top VC Firms. With A Sale Ongoing, Their Future Is In Flux. (https://www.forbes.com/sites/alexkonrad/2023/03/24/what-happens-to-svb-capital-vc-firm-bets/?sh=596c2bedb7ef) First Citizens agrees to buy Silicon Valley Bank (https://www.axios.com/2023/03/27/first-citizens-silicon-valley-bank-sold-fdic) Databricks pushes open-source chatbot as cheaper ChatGPT alternative (https://www.reuters.com/technology/databricks-pushes-open-source-chatbot-cheaper-chatgpt-alternative-2023-03-24/) Let's Get To The News #11: 11 O'Clock Tick Tock (https://craigbox.substack.com/p/11-oclock-tick-tock) Rackspace cutting workforce in response to downturn. Amid string of losses, its stock has plummeted. (https://www.expressnews.com/business/article/rackspace-layoffs-downturn-17859129.php) Microsoft is testing a redesigned Windows 11 audio mixer (https://www.engadget.com/microsoft-is-testing-a-redesigned-windows-11-audio-mixer-224417187.html) Twilio's IoT business unit to be acquired by KORE to build first 'IoT Hyperscaler' (https://seekingalpha.com/news/3951425-twilios-iot-business-unit-to-be-acquired-by-kore-to-build-first-iot-hyperscaler) Apple Releases iOS and iPadOS 16.4 with New Emoji, Notifications for Web Apps on the Home Screen, Voice Isolation for Cellular Calls, New Shortcuts Actions, and More (https://feed.feedburster.com/macstoriesnet/redirect?url=https://www.macstories.net/news/ios-16-4-overview-emoji-notifications-web-shortcuts/) The Bank Regulators Are Disappointed (https://www.bloomberg.com/opinion/articles/2023-03-28/the-bank-regulators-are-disappointed) ChatGPT plugins (https://openai.com/blog/chatgpt-plugins?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) AI changes the software-making game (https://www.axios.com/newsletters/axios-login-660f9b08-f144-4c7f-9388-fcde9259d5d2.html?chunk=0&utm_term=emshare#story0) Google Distributed Cloud Hosted is GA | Google Cloud Blog (https://cloud.google.com/blog/products/infrastructure-modernization/google-distributed-cloud-hosted-is-ga/) Alibaba to split into 6 units and explore IPOs; shares up 14% in the U.S. (https://www.cnbc.com/2023/03/28/alibaba-says-it-will-split-into-6-units-that-can-raise-funds-and-ipo.html?_hsmi=252164574) Elon Musk: Only paid subscribers will get recommended in Twitter 'For You' feed (https://www.cnn.com/2023/03/28/tech/elon-musk-verified-only-for-you-feed?_hsmi=252164574) Zoom is adding new features to compete with Slack, Calendly, Google and Microsoft (https://techcrunch.com/2023/03/28/zoom-is-adding-new-features-to-compete-with-slack-calendly-google-and-microsoft/) How Siri, Alexa and Google Assistant Lost the A.I. Race (https://www.nytimes.com/2023/03/15/technology/siri-alexa-google-assistant-artificial-intelligence.html) Nonsense Beaver fossil named after Buc-ee's (https://phys.org/news/2023-03-beaver-fossil-buc-ee.html) The Ultimate Texas Brand Bracket Crowns Its Champion — Texas Monthly (https://apple.news/Aq4TrnlI_Sfq9hziw3ML6oQ) After Show Coté's interview with Barton (https://www.softwaredefinedtalk.com/393) Conferences KubeCon EU Amsterdam, April 18-21 (https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/) - Matt & Cote will be there DevOpsDays Birmingham, AL 2023 (https://devopsdays.org/events/2023-birmingham-al/welcome/), April 20 - 21, 2023 DevOpsDays Austin 2023 (https://devopsdays.org/events/2023-austin/welcome/), May 4-5 SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: Duo Lingo (https://www.duolingo.com) Matt: Hardcore History Addendum: Rick Rubin/Dan Carlin Conversation (https://www.dancarlin.com/addendum/) Kubernetes Cloud Cost Monitoring with OpenCost & Optimization Strategies (https://www.youtube.com/watch?v=CiqIqcM1d6o) Photo Credits Header (https://unsplash.com/photos/7ZD_JIwl410) Artwork (https://unsplash.com/photos/XzVGz2HBtK4) Special Guest: Barton George.

Waldemar Hummer, Co-Founder & CTO of LocalStack, joins Corey on Screaming in the Cloud to discuss how LocalStack changed Corey's mind on the futility of mocking clouds locally. Waldemar reveals why LocalStack appeals to both enterprise companies and digital nomads, and explains how both see improvements in their cost predictability as a result. Waldemar also discusses how LocalStack is an open-source company first and foremost, and how they're working with their community to evolve their licensing model. Corey and Waldemar chat about the rising demand for esoteric services, and Waldemar explains how accommodating that has led to an increase of adoption from the big data space. About WaldemarWaldemar is Co-Founder and CTO of LocalStack, where he and his team are building the world-leading platform for local cloud development, based on the hugely popular open source framework with 45k+ stars on Github. Prior to founding LocalStack, Waldemar has held several engineering and management roles at startups as well as large international companies, including Atlassian (Sydney), IBM (New York), and Zurich Insurance. He holds a PhD in Computer Science from TU Vienna.Links Referenced: LocalStack website: https://localstack.cloud/ LocalStack Slack channel: https://slack.localstack.cloud LocalStack Discourse forum: https://discuss.localstack.cloud LocalStack GitHub repository: https://github.com/localstack/localstack TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Until a bit over a year ago or so, I had a loud and some would say fairly obnoxious opinion around the futility of mocking cloud services locally. This is not to be confused with mocking cloud services on the internet, which is what I do in lieu of having a real personality. And then one day I stopped espousing that opinion, or frankly, any opinion at all. And I'm glad to be able to talk at long last about why that is. My guest today is Waldemar Hummer, CTO and co-founder at LocalStack. Waldemar, it is great to talk to you.Waldemar: Hey, Corey. It's so great to be on the show. Thank you so much for having me. We're big fans of what you do at The Duckbill Group and Last Week in AWS. So really, you know, glad to be here with you today and have this conversation.Corey: It is not uncommon for me to have strong opinions that I espouse—politely to be clear; I'll make fun of companies and not people as a general rule—but sometimes I find that I've not seen the full picture and I no longer stand by an opinion I once held. And you're one of my favorite examples of this because, over the course of a 45-minute call with you and one of your business partners, I went from, “What you're doing is a hilarious misstep and will never work,” to, “Okay, and do you have room for another investor?” And in the interest of full disclosure, the answer to that was yes, and I became one of your angel investors. It's not exactly common for me to do that kind of a hard pivot. And I kind of suspect I'm not the only person who currently holds the opinion that I used to hold, so let's talk a little bit about that. At the very beginning, what is LocalStack and what does it you would say that you folks do?Waldemar: So LocalStack, in a nutshell, is a cloud emulator that runs on your local machine. It's basically like a sandbox environment where you can develop your applications locally. We have currently a range of around 60, 70 services that we provide, things like Lambda Functions, DynamoDB, SQS, like, all the major AWS services. And to your point, it is indeed a pretty large undertaking to actually implement the cloud and run it locally, but with the right approach, it actually turns out that it is feasible and possible, and we've demonstrated this with LocalStack. And I'm glad that we've convinced you to think of it that way as well.Corey: A couple of points that you made during that early conversation really stuck with me. The first is, “Yeah, AWS has two, no three no four-hundred different service offerings. But look at your customer base. How many of those services are customers using in any real depth? And of those services, yeah, the APIs are vast, and very much a sprawling pile of nonsense, but how many of those esoteric features are those folks actually using?” That was half of the argument that won me over.The other half was, “Imagine that you're an enormous company that's an insurance company or a bank. And this year, you're hiring 5000 brand new developers, fresh out of school. Two to 3000 of those developers will still be working here in about a year as they wind up either progressing in other directions, not winding up completing internships, or going back to school after internships, or for a variety of reasons. So, you have that many people that you need to teach how to use cloud in the context that we use cloud, combined with the question of how do you make sure that one of them doesn't make a fun mistake that winds up bankrupting the entire company with a surprise AWS bill?” And those two things combined turned me from, “What you're doing is ridiculous,” to, “Oh, my God. You're absolutely right.”And since then, I've encountered you in a number of my client environments. You were absolutely right. This is something that resonates deeply and profoundly with larger enterprise customers in particular, but also folks who just don't want to wind up being beholden to every time they do a deploy to anything to test something out, yay, I get to spend more money on AWS services.Waldemar: Yeah, totally. That's spot on. So, to your first point, so definitely we have a core set of services that most people are using. So, things like Lambda, DynamoDB, SQS, like, the core serverless, kind of, APIs. And then there's kind of a long tail of more exotic services that we support these days, things like, even like QLDB, the quantum ledger database, or, you know, managed streaming for Kafka.But like, certainly, like, the core 15, 20 services are the ones that are really most used by the majority of people. And then we also, you know, pro offering have some very, sort of, advanced services for different use cases. So, that's to your first point.And second point is, yeah, totally spot on. So LocalStack, like, really enables you to experiment in the sandbox. So, we both see it as an experimentation, also development environment, where you don't need to think about cloud costs. And this, I guess, will be very close to your heart in the work that you're doing, the costs are becoming really predictable as well, right? Because in the cloud, you know, work to different companies before doing LocalStack where we were using AWS resources, and you can end up in a situation where overnight, you accumulate, you know, hundreds of thousands of dollars of AWS bill because you've turned on a certain feature, or some, you know, connectivity into some VPC or networking configuration that just turns out to be costly.Also, one more thing that is worth mentioning, like, we want to encourage, like, frequent testing, and a lot of the cloud's billing and cost structure is focused around, for example, hourly billing of resources, right? And if you have a test that just spins up resources that run for a couple of minutes, you still end up paying the entire hour. And we LocalStack, really, that brings down the cloud builds significantly because you can really test frequently, the cycles become much faster, and it's also again, more efficient, more cost-effective.Corey: There's something useful to be said for, “Well, how do I make sure that I turn off resources when I'm done?” In cloud, it's a bit of a game of guess-and-check. And you turn off things you think are there and you wait a few days and you check the bill again, and you go and turn more things off, and the cycle repeats. Or alternately, wait for the end of the month and wonder in perpetuity why you're being billed 48 cents a month, and not be clear on why. Restarting the laptop is a lot more straightforward.I also want to call out some of my own bias on this where I used to be a big believer in being able to build and deploy and iterate on things locally because well, what happens when I'm in a plane with terrible WiFi? Well, in the before times, I flew an awful lot and was writing a fair bit of, well, cloudy nonsense and I still never found that to be a particular blocker on most of what I was doing. So, it always felt a little bit precious to me when people were talking about, well, what if I can't access the internet to wind up building and deploying these things? It's now 2023. How often does that really happen? But is that a use case that you see a lot of?Waldemar: It's definitely a fair point. And probably, like, 95% of cloud development these days is done in a high internet bandwidth environment, maybe some corporate network where you have really fast internet access. But that's only a subset, I guess, of the world out there, right? So, there might be situations where, you know, you may have bad connectivity. Also, maybe you live in a region—or maybe you're traveling even, right? So, there's a lot more and more people who are just, “Digital nomads,” quote-unquote, right, who just like to work in remote places.Corey: You're absolutely right. My bias is that I live in San Francisco. I have symmetric gigabit internet at home. There's not a lot of scenarios in my day-to-day life—except when I'm, you know, on the train or the bus traveling through the city—because thank you, Verizon—where I have impeded connectivity.Waldemar: Right. Yeah, totally. And I think the other aspect of this is kind of the developers just like to have things locally, right, because it gives them the feeling of you know, better control over the code, like, being able to integrate into their IDEs, setting breakpoints, having these quick cycles of iterations. And again, this is something that there's more and more tooling coming up in the cloud ecosystem, but it's still inherently a remote execution that just, you know, takes the round trip of uploading your code, deploying, and so on, and that's just basically the pain point that we're addressing with LocalStack.Corey: One thing that did surprise me as well was discovering that there was a lot more appetite for this sort of thing in enterprise-scale environments. I mean, some of the reference customers that you have on your website include divisions of the UK Government and 3M—you know, the Post-It note people—as well as a number of other very large environments. And at first, that didn't make a whole lot of sense to me, but then it suddenly made an awful lot of sense because it seems—and please correct me if I'm wrong—that in order to use something like this at scale and use it in a way that isn't, more or less getting it into a point where the administration of it is more trouble than it's worth, you need to progress past a certain point of scale. An individual developer on their side project is likely just going to iterate against AWS itself, whereas a team of thousands of developers might not want to be doing that because they almost certainly have their own workflows that make that process high friction.Waldemar: Yeah, totally. So, what we see a lot is, especially in larger enterprises, dedicated teams, like, developer experience teams, whose main job is to really set up a workflow and environment where developers can be productive, most productive, and this can be, you know, on one side, like, setting up automated pipelines, provisioning maybe AWS sandbox and test accounts. And like some of these teams, when we introduce LocalStack, it's really a game-changer because it becomes much more decoupled and like, you know, distributed. You can basically configure your CI pipeline, just, you know, spin up the container, run your tests, tear down again afterwards. So, you know, it's less dependencies.And also, one aspect to consider is the aspect of cloud approvals. A lot of companies that we work with have, you know, very stringent processes around, even getting access to the clouds. Some SRE team needs to enable their IAM permissions and so on. With LocalStack, you can just get started from day one and just get productive and start testing from the local machine. So, I think those are patterns that we see a lot, in especially larger enterprise environments as well, where, you know, there might be some regulatory barriers and just, you know, process-wise steps as well.Corey: When I started playing with LocalStack myself, one of the things that I found disturbingly irritating is, there's a lot that AWS gets largely right with its AWS command-line utility. You can stuff a whole bunch of different options into the config for different profiles, and all the other tools that I use mostly wind up respecting that config. The few that extend it add custom lines to it, but everything else is mostly well-behaved and ignores the things it doesn't understand. But there is no facility that lets you say, “For this particular profile, use this endpoint for AWS service calls instead of the normal ones in public regions.” In fact, to do that, you effectively have to pass specific endpoint URLs to arguments, and I believe the syntax on that is not globally consistent between different services.It just feels like a living nightmare. At first, I was annoyed that you folks wound up having to ship your own command-line utility to wind up interfacing with this. Like, why don't you just add a profile? And then I tried it myself and, oh, I'm not the only person who knows how this stuff works that has ever looked at this and had that idea. No, it's because AWS is just unfortunate in that respect.Waldemar: That is a very good point. And you're touching upon one of the major pain points that we have, frankly, with the ecosystem. So, there are some pull requests against the AWS open-source repositories for the SDKs and various other tools, where folks—not only LocalStack, but other folks in the community have asked for introducing, for example, an AWS endpoint URL environment variable. These [protocols 00:12:32], unfortunately, were never merged. So, it would definitely make our lives a whole lot easier, but so far, we basically have to maintain these, you know, these wrapper scripts, basically, AWS local, CDK local, which basically just, you know, points the client to local endpoints. It's a good workaround for now, but I would assume and hope that the world's going to change in the upcoming years.Corey: I really hope so because everything else I can think of is just bad. The idea of building a custom wrapper around the AWS command-line utility that winds up checking the profile section, and oh, if this profile is that one, call out to this tool, otherwise it just becomes a pass-through. That has security implications that aren't necessarily terrific, you know, in large enterprise companies that care a lot about security. Yeah, pretend to be a binary you're not is usually the kind of thing that makes people sad when security politely kicks their door in.Waldemar: Yeah, we actually have pretty, like, big hopes for the v3 wave of the SDKs, AWS, because there is some restructuring happening with the endpoint resolution. And also, you can, in your profile, by now have, you know, special resolvers for endpoints. But still the case of just pointing all the SDKs and CLI to a custom endpoint is just not yet resolved. And this is, frankly, quite disappointing, actually.Corey: While we're complaining about the CLI, I'll throw one of my recurring issues with it in. I would love for it to adopt the Linux slash Unix paradigm of having a config.d directory that you can reference from within the primary config file, and then any file within that directory in the proper syntax winds up getting adopted into what becomes a giant composable config file, generated dynamically. The reason being is, I can have entire lists of profiles in separate files that I could then wind up dropping in and out on a client-by-client basis. So, I don't inadvertently expose who some of my clients are, in the event that winds up being part of the way that they have named their AWS accounts.That is one of those things I would love but it feels like it's not a common enough use case for there to be a whole lot of traction around it. And I guess some people would make a fair point if they were to say that the AWS CLI is the most widely deployed AWS open-source project, even though all it does is give money to AWS more efficiently.Waldemar: Yeah. Great point. Yeah, I think, like, how and some way to customize and, like, mingle or mangle your configurations in a more easy fashion would be super useful. I guess it might be a slippery slope to getting, you know, into something like I don't know, Helm for EKS and, like, really, you know, having to maintain a whole templating language for these configs. But certainly agree with you, to just you know, at least having [plug 00:15:18] points for being able to customize the behavior of the SDKs and CLIs would be extremely helpful and valuable.Corey: This is not—unfortunately—my first outing with the idea of trying to have AWS APIs done locally. In fact, almost a decade ago now, I did a build-out at a very large company of a… well, I would say that the build-out was not itself very large—it was about 300 nodes—that were all running Eucalyptus, which before it died on the vine, was imagined as a way of just emulating AWS APIs locally—done in Java, as I recall—and exposing local resources in ways that comported with how AWS did things. So, the idea being that you could write configuration to deploy any infrastructure you wanted in AWS, but also treat your local data center the same way. That idea unfortunately did not survive in the marketplace, which is kind of a shame, on some level. What was it that inspired you folks to wind up building this with an eye towards local development rather than run this as a private cloud in your data center instead?Waldemar: Yeah, very interesting. And I do also have some experience [unintelligible 00:16:29] from my past university days with Eucalyptus and OpenStack also, you know, running some workloads in an on-prem cluster. I think the main difference, first of all, these systems were extremely hard, notoriously hard to set up and maintain, right? So, lots of moving parts: you had your image server, your compute system, and then your messaging subsystems. Lots of moving parts, and wanting to have everything basically much more monolithic and in a single container.And Docker really sort of provides a great platform for us, which is create everything in a single container, spin up locally, make it very lightweight and easy to use. But I think really the first days of LocalStack, the idea was really, was actually with the use case of somebody from our team. Back then, I was working at Atlassian in the data engineering team and we had folks in the team were commuting to work on the train. And it was literally this use case that you mentioned before about being able to work basically offline on your commute. And this is kind of were the first lines of code were written and then kind of the idea evolves from there.We put it into the open-source, and then, kind of, it was growing over the years. But it really started as not having it as an on-prem, like, heavyweight server, but really as a lightweight system that you can easily—that is easily portable across different systems as well.Corey: That is a good question. Very often, when I'm using various tools that are aimed at development use cases, it is very clear that one particular operating system is invariably going to be the first-class citizen and everything else is a best effort. Ehh, it might work; it might not. Does LocalStack feel that way? And if so, what's the operating system that you want to be on?Waldemar: I would say we definitely work best on Mac OS and Linux. It also works really well on Windows, but I think given that some of our tooling in the ecosystem also pretty much geared towards Unix systems, I think those are the platforms it will work well with. Again, on the other hand, Docker is really a platform that helps us a lot being compatible across operating systems and also CPU architectures. We have a multi-arch build now for AMD and ARM64. So, I think in that sense, we're pretty broad in terms of the compatibility spectrum.Corey: I do not have any insight into how the experience goes on Windows, given that I don't use that operating system in anger for, wow, 15 years now, but I will say that it's been top-flight on Mac OS, which is what I spend most of my time. Depressed that I'm using, but for desktop experiences, it seems to work out fairly well. That said, having a focus on Windows seems like it would absolutely be a hard requirement, given that so many developer workstations in very large enterprises tend to skew very Windows-heavy. My hat is off to people who work with Linux and Linux-like systems in environments like that where even line endings becomes psychotically challenging. I don't envy them their problems. And I have nothing but respect for people who can power through it. I never had the patience.Waldemar: Yeah. Same here and definitely, I think everybody has their favorite operating system. For me, it's also been mostly Linux and Mac in the last couple of years. But certainly, we definitely want to be broad in terms of the adoption, and working with large enterprises often you have—you know, we want to fit into the existing landscape and environment that people work in. And we solve this by platform abstractions like Docker, for example, as I mentioned, and also, for example, Python, which is some more toolings within Python is also pretty nicely supported across platforms. But I do feel the same way as you, like, having been working with Windows for quite some time, especially for development purposes.Corey: What have you noticed that your customer usage patterns slash requests has been saying about AWS service adoption? I have to imagine that everyone cares whether you can mock S3 effectively. EC2, DynamoDB, probably. SQS, of course. But beyond the very small baseline level of offering, what have you seen surprising demand for, as I guess, customer implementation of more esoteric services continues to climb?Waldemar: Mm-hm. Yeah, so these days it's actually pretty [laugh] pretty insane the level of coverage we already have for different services, including some very exotic ones, like QLDB as I mentioned, Kafka. We even have Managed Airflow, for example. I mean, a lot of these services are essentially mostly, like, wrappers around the API. This is essentially also what AWS is doing, right? So, they're providing an API that basically provisions some underlying resources, some infrastructure.Some of the more interesting parts, I guess, we've seen is the data or big data ecosystem. So, things like Athena, Glue, we've invested quite a lot of time in, you know, making that available also in LocalStack so you can have your maybe CSV files or JSON files in an S3 bucket and you can query them from Athena with a SQL language, basically, right? And that makes it very—especially these big data-heavy jobs that are very heavyweight on AWS, you can iterate very quickly in LocalStack. So, this is where we're seeing a lot of adoption recently. And then also, obviously, things like, you know, Lambda and ECS, like, all the serverless and containerized applications, but I guess those are the more mainstream ones.Corey: I imagine you probably get your fair share of requests for things like CloudFormation or CloudFront, where, this is great, but can you go ahead and add a very lengthy sleep right here, just because it returns way too fast and we don't want people to get their hopes up when they use the real thing. On some level, it feels like exact replication of the AWS customer experience isn't quite in line with what makes sense from a developer productivity point of view.Waldemar: Yeah, that's a great point. And I'm sure that, like, a lot of code out there is probably littered with sleep statements that is just tailored to the specific timing in AWS. In fact, we recently opened an issue in the AWS Terraform provider repository to add a configuration option to configure the timings that Terraform is using for the resource deployment. So, just as an example, an S3 bucket creation takes 60 seconds, like, more than a minute against [unintelligible 00:22:37] AWS. I guess LocalStack, it's a second basically, right?And AWS Terraform provider has these, like, relatively slow cycles of checking whether the packet has already been created. And we want to get that configurable to actually reduce the time it takes for local development, right? So, we have an open, sort of, feature request, and we're probably going to contribute to a Terraform repository. But definitely, I share the sentiment that a lot of the tooling ecosystem is built and tailored and optimized towards the experience against the cloud, which often is just slow and, you know, that's what it is, right?Corey: One thing that I didn't expect, though, in hindsight, is blindingly obvious, is your support for a variety of different frameworks and deployment methodologies. I've found that it's relatively straightforward to get up and running with the CDK deploying to LocalStack, for instance. And in hindsight, of course; that's obvious. When you start out down that path, though it's well, you tend to think—at least I don't tend to think in that particular way. It's, “Well, yeah, it's just going to be a console-like experience, or I wind up doing CloudFormation or Terraform.” But yeah, that the world is advancing relatively quickly and it's nice to see that you are very comfortably keeping pace with that advancement.Waldemar: Yeah, true. And I guess for us, it's really, like, the level of abstraction is sort of increasing, so you know, once you have a solid foundation, with, you know, CloudFormation implementation, you can leverage a lot of tools that are sitting on top of it, CDK, serverless frameworks. So, CloudFormation is almost becoming, like, the assembly language of the AWS cloud, right, and if you have very solid support for that, a lot of, sort of, tools in the ecosystem will natively be supported on LocalStack. And then, you know, you have things like Terraform, and in the Terraform CDK, you know, some of these derived versions of Terraform which also are very straightforward because you just need to point, you know, the target endpoint to localhost and then the rest of the deployment loop just works out of the box, essentially.So, I guess for us, it's really mostly being able to focus on, like, the core emulation, making sure that we have very high parity with the real services. We spend a lot of time and effort into what we call parity testing and snapshot testing. We make sure that our API responses are identical and really the same as they are in AWS. And this really gives us, you know, a very strong confidence that a lot of tools in the ecosystem are working out-of-the-box against LocalStack as well.Corey: I would also like to point out that I'm also a proud LocalStack contributor at this point because at the start of this year, I noticed, ah, in one of the pages, the copyright year was still saying 2022 and not 2023. So, a single-character pull request? Oh, yes, I am on the board now because that is how you ingratiate yourself with an open-source project.Waldemar: Yeah. Eternal fame to you and kudos for your contribution. But, [laugh] you know, in all seriousness, we do have a quite an active community of contributors. We are an open-source first project; like, we were born in the open-source. We actually—maybe just touching upon this for a second, we use GitHub for our repository, we use a lot of automation around, you know, doing pull requests, and you know, service owners.We also participate in things like the Hacktoberfest, which we participated in last year to really encourage contributions from the community, and also host regular meetups with folks in the community to really make sure that there's an active ecosystem where people can contribute and make contributions like the one that you did with documentation and all that, but also, like, actual features, testing and you know, contributions of different levels. So really, kudos and shout out to the entire community out there.Corey: Do you feel that there's an inherent tension between being an open-source product as well as being a commercial product that is available for sale? I find that a lot of companies feel vaguely uncomfortable with the various trade-offs that they make going down that particular path, but I haven't seen anyone in the community upset with you folks, and it certainly hasn't seemed to act as a brake on your enterprise adoption, either.Waldemar: That is a very good point. So, we certainly are—so we're following an open-source-first model that we—you know, the core of the codebase is available in the community version. And then we have pro extensions, which are commercial and you basically, you know, setup—you sign up for a license. We are certainly having a lot of discussions on how to evolve this licensing model going forward, you know, which part to feed back into the community version of LocalStack. And it's certainly an ongoing evolving model as well, but certainly, so far, the support from the community has been great.And we definitely focus to, kind of, get a lot of the innovation that we're doing back into our open-source repo and make sure that it's, like, really not only open-source but also open contribution for folks to contribute their contributions. We also integrate with other third-party libraries. We're built on the shoulders of giants, if I may say so, other open-source projects that are doing great work with emulators. To name just a few, it's like, [unintelligible 00:27:33] which is a great project that we sort of use and depend upon. We have certain mocks and emulations, for Kinesis, for example, Kinesis mock and a bunch of other tools that we've been leveraging over the years, which are really great community efforts out there. And it's great to see such an active community that's really making this vision possible have a truly local emulated clouds that gives the best experience to developers out there.Corey: So, as of, well, now, when people are listening to this and the episode gets released, v2 of LocalStack is coming out. What are the big differences between LocalStack and now LocalStack 2: Electric Boogaloo, or whatever it is you're calling the release?Waldemar: Right. So, we're super excited to release our v2 version of LocalStack. Planned release date is end of March 2023, so hopefully, we will make that timeline. We did release our first version of OpenStack in July 2022, so it's been roughly seven months since then and we try to have a cadence of roughly six to nine months for the major releases. And what you can expect is we've invested a lot of time and effort in last couple of months and in last year to really make it a very rock-solid experience with enhancements in the current services, a lot of performance optimizations, we've invested a lot in parity testing.So, as I mentioned before, parity is really important for us to make sure that we have a high coverage of the different services and how they behave the same way as AWS. And we're also putting out an enhanced version and a completely polished version of our Cloud Pods experience. So, Cloud Pods is a state management mechanism in LocalStack. So, by default, the state in LocalStack is ephemeral, so when you restart the instance, you basically have a fresh state. But with Cloud Pods, we enable our users to take persistent snapshot of the states, save it to disk or to a server and easily share it with team members.And we have very polished experience with Community Cloud Pods that makes it very easy to share the state among team members and with the community. So, those are just some of the highlights of things that we're going to be putting out in the tool. And we're super excited to have it done by, you know, end of March. So, stay tuned for the v2 release.Corey: I am looking forward to seeing how the experience shifts and evolves. I really want to thank you for taking time out of your day to wind up basically humoring me and effectively re-covering ground that you and I covered about a year and a half ago now. If people want to learn more, where should they go?Waldemar: Yeah. So definitely, our Slack channel is a great way to get in touch with the community, also with the LocalStack team, if you have any technical questions. So, you can find it on our website, I think it's slack.localstack.cloud.We also host a Discourse forum. It's discuss.localstack.cloud, where you can just, you know, make feature requests and participate in the general conversation.And we do host monthly community meetups. Those are also available on our website. If you sign up, for example, for a newsletter, you will be notified where we have, you know, these webinars. Take about an hour or so where we often have guest speakers from different companies, people who are using, you know, cloud development, local cloud development, and just sharing the experiences of how the space is evolving. And we're always super happy to accept contributions from the community in these meetups as well. And last but not least, our GitHub repository is a great way to file any issues you may have, feature requests, and just getting involved with the project itself.Corey: And we will, of course, put links to that in the [show notes 00:31:09]. Thank you so much for taking the time to speak with me today. I appreciate it.Waldemar: Thank you so much, Corey. It's been a pleasure. Thanks for having me.Corey: Waldemar Hummer, CTO and co-founder at LocalStack. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry comment, presumably because your compensation structure requires people to spend ever-increasing amounts of money on AWS services.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Matt interviews Peter Pouliot from Ampere (https://amperecomputing.com). They discuss Peter's experience with working on OpenStack for Microsoft, developer relations in his latest role at Ampere, and how to strategically choose your conference parties to attend. Links: Ampere Altra Developer Platform (https://amperecomputing.com/systems/altra/kraken-comhpc-WS) Linux on Microsoft Dev Kit 2023 (https://blog.alexellis.io/linux-on-microsoft-dev-kit-2023/) Ampere Developer Program (https://amperecomputing.com/developers) Contact Peter: LinkedIn (https://www.linkedin.com/in/peterpouliot/) SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Photo Credits Header (https://amperecomputing.com/_next/image?url=https%3A%2F%2Fsolutions-portal-cms-prod-bucket.s3.amazonaws.com%2FAmpere_Product_Page_035d9bec1c.png&w=1920&q=75) Special Guest: Peter Pouliot.

Sponsors Bitwarden (https://bitwarden.com/tux) Linode (https://linode.com/tux) - Application of the month n8n (https://n8n.io) Support TuxDigital and the Sudo Show Patreon (https://www.patreon.com/tuxdigital) Show Notes xCat (https://xcat.org) MaaS (https://maas.io) Uyuni (https://www.uyuni-project.org/) The Foreman (https://theforeman.org/) Cobbler (https://cobbler.github.io/) BiFrost - Standalone Ironic (https://docs.openstack.org/bifrost/latest/) TinkerBell (https://tinkerbell.org/) MetalKubed (https://metal3.io/) OpenStack (https://openstack.org) OpenShift (https://openshift.com) OKD - Upstream for OpenShift (https://okd.io) Kubernetes (https://kubernetes.io) Rancher (https://rancher.com) Harvester (https://harvesterhci.io/) Mist.io (https://mist.io) ManageIQ (https://manageiq.org) oVirt (https://ovirt.org) Interact with the hosts and the community https://tuxdigital.com/community/

Leonard Pahlke is not only the Release Lead for Kubernetes v1.26, he's also a co-chair of the CNCF TAG for Environmental Sustainability and a student working toward a Master's Degree in Computer Science at the Hamburg University of Applied Sciences. In this episode, Leonard talks with us about Open Source contribution, environmental sustainability, and Kubernetes v1.26.   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 The 1.23 Release team (where Kaslin was a comms shadow) Shoutout to Kunal Kushwaha, another Kubernetes contributor who started out as a student, and who advocates for students in the community via his YouTube channel & more. KubeCon EU 2023 (which will have a student track as part of the schedule) KubeCon Diversity and Inclusion Scholarships   News of the week Kubernetes Removals, Deprecations, and Major Changes in 1.26 AWS ReInvent 2022 AWS YouTube Channel Control Plane Logs added for GKE Gateway Controller for Single Clusters reaches GA for GKE Prometheus Turns 10 Prometheus Training Prometheus Documentary by HoneyPot Move to registry.k8s.io Leak Signal Micro-waf CNCF Maintainer Track changes   Links from the interview Leonard Pahlke's Blog Leonard Pahlke blog about contribution: Start Contributing to Open Source Projects Leonard Pahlke CNCF WG Environmental Sustainablity Blog Post TAG Environmental Sustainability GitHub Specific 1.26 changes mentioned: Kubernetes 1.26: We're now signing our binary release artifacts! Kubernetes 1.26: Windows HostProcess Containers Are Generally Available CEL for Admission Control KEP In-tree Storage Plugin to CSI Migration - Azurefile In-tree Storage Plugin to CSI Migration - vSphere In-tree storage plugin removals for GlusterFS and OpenStack, and more, are outlined in the “Kubernetes Removals, Deprecations, and Major Changes in 1.26” blog Kubernetes Enhancement Proposals (KEPs) Kubernetes v1.26 Electrifying Release Blog   Links from the post-interview chat List of Kubernetes SIGs Kubernetes Release Team Shadow program

About KelseyKelsey Hightower is the Principal Developer Advocate at Google, the co-chair of KubeCon, the world's premier Kubernetes conference, and an open source enthusiast. He's also the co-author of Kubernetes Up & Running: Dive into the Future of Infrastructure.Links: Twitter: @kelseyhightower Company site: Google.com Book: Kubernetes Up & Running: Dive into the Future of Infrastructure TranscriptAnnouncer: Hello and welcome to Screaming in the Cloud, with your host Cloud economist Corey Quinn. This weekly show features conversations with people doing interesting work in the world of Cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is brought to us by our friends at Pinecone. They believe that all anyone really wants is to be understood, and that includes your users. AI models combined with the Pinecone vector database let your applications understand and act on what your users want… without making them spell it out. Make your search application find results by meaning instead of just keywords, your personalization system make picks based on relevance instead of just tags, and your security applications match threats by resemblance instead of just regular expressions. Pinecone provides the cloud infrastructure that makes this easy, fast, and scalable. Thanks to my friends at Pinecone for sponsoring this episode. Visit Pinecone.io to understand more.Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn. I'm joined this week by Kelsey Hightower, who claims to be a principal developer advocate at Google, but based upon various keynotes I've seen him in, he basically gets on stage and plays video games like Tetris in front of large audiences. So I assume he is somehow involved with e-sports. Kelsey, welcome to the show.Kelsey: You've outed me. Most people didn't know that I am a full-time e-sports Tetris champion at home. And the technology thing is just a side gig.Corey: Exactly. It's one of those things you do just to keep the lights on, like you're waiting to get discovered, but in the meantime, you're waiting table. Same type of thing. Some people wait tables you more or less a sling Kubernetes, for lack of a better term.Kelsey: Yes.Corey: So let's dive right into this. You've been a strong proponent for a long time of Kubernetes and all of its intricacies and all the power that it unlocks and I've been pretty much the exact opposite of that, as far as saying it tends to be over complicated, that it's hype-driven and a whole bunch of other, shall we say criticisms that are sometimes bounded in reality and sometimes just because I think it'll be funny when I put them on Twitter. Where do you stand on the state of Kubernetes in 2020?Kelsey: So, I want to make sure it's clear what I do. Because when I started talking about Kubernetes, I was not working at Google. I was actually working at CoreOS where we had a competitor Kubernetes called Fleet. And Kubernetes coming out kind of put this like fork in our roadmap, like where do we go from here? What people saw me doing with Kubernetes was basically learning in public. Like I was really excited about the technology because it's attempting to solve a very complex thing. I think most people will agree building a distributed system is what cloud providers typically do, right? With VMs and hypervisors. Those are very big, complex distributed systems. And before Kubernetes came out, the closest I'd gotten to a distributed system before working at CoreOS was just reading the various white papers on the subject and hearing stories about how Google has systems like Borg tools, like Mesa was being used by some of the largest hyperscalers in the world, but I was never going to have the chance to ever touch one of those unless I would go work at one of those companies.So when Kubernetes came out and the fact that it was open source and I could read the code to understand how it was implemented, to understand how schedulers actually work and then bonus points for being able to contribute to it. Those early years, what you saw me doing was just being so excited about systems that I attended to build on my own, becoming this new thing just like Linux came up. So I kind of agree with you that a lot of people look at it as a more of a hype thing. They're looking at it regardless of their own needs, regardless of understanding how it works and what problems is trying to solve that. My stance on it, it's a really, really cool tool for the level that it operates in, and in order for it to be successful, people can't know that it's there.Corey: And I think that might be where part of my disconnect from Kubernetes comes into play. I have a background in ops, more or less, the grumpy Unix sysadmin because it's not like there's a second kind of Unix sysadmin you're ever going to encounter. Where everything in development works in theory, but in practice things pan out a little differently. I always joke that ops is the difference between theory and practice. In theory, devs can do everything and there's no ops needed. In practice, well it's been a burgeoning career for a while. The challenge with this is Kubernetes at times exposes certain levels of abstraction that, sorry certain levels of detail that generally people would not want to have to think about or deal with, while papering over other things with other layers of abstraction on top of it. That obscure, valuable troubleshooting information from a running something in an operational context. It absolutely is a fascinating piece of technology, but it feels today like it is overly complicated for the use a lot of people are attempting to put it to. Is that a fair criticism from where you sit?Kelsey: So I think the reason why it's a fair criticism is because there are people attempting to run their own Kubernetes cluster, right? So when we think about the cloud, unless you're in OpenStack land, but for the people who look at the cloud and you say, "Wow, this is much easier." There's an API for creating virtual machines and I don't see the distributed state store that's keeping all of that together. I don't see the farm of hypervisors. So we don't necessarily think about the inherent complexity into a system like that, because we just get to use it. So on one end, if you're just a user of a Kubernetes cluster, maybe using something fully managed or you have an ops team that's taking care of everything, your interface of the system becomes this Kubernetes configuration language where you say, "Give me a load balancer, give me three copies of this container running." And if we do it well, then you'd think it's a fairly easy system to deal with because you say, "kubectl, apply," and things seem to start running.Just like in the cloud where you say, "AWS create this VM, or G cloud compute instance, create." You just submit API calls and things happen. I think the fact that Kubernetes is very transparent to most people is, now you can see the complexity, right? Imagine everyone driving with the hood off the car. You'd be looking at a lot of moving things, but we have hoods on cars to hide the complexity and all we expose is the steering wheel and the pedals. That car is super complex but we don't see it. So therefore we don't attribute as complexity to the driving experience.Corey: This to some extent feels it's on the same axis as serverless, with just a different level of abstraction piled onto it. And while I am a large proponent of serverless, I think it's fantastic for a lot of Greenfield projects. The constraints inherent to the model mean that it is almost completely non-tenable for a tremendous number of existing workloads. Some developers like to call it legacy, but when I hear the term legacy I hear, "it makes actual money." So just treating it as, "Oh, it's a science experiment we can throw into a new environment, spend a bunch of time rewriting it for minimal gains," is just not going to happen as companies undergo digital transformations, if you'll pardon the term.Kelsey: Yeah, so I think you're right. So let's take Amazon's Lambda for example, it's a very opinionated high-level platform that assumes you're going to build apps a certain way. And if that's you, look, go for it. Now, one or two levels below that there is this distributed system. Kubernetes decided to play in that space because everyone that's building other platforms needs a place to start. The analogy I like to think of is like in the mobile space, iOS and Android deal with the complexities of managing multiple applications on a mobile device, security aspects, app stores, that kind of thing. And then you as a developer, you build your thing on top of those platforms and APIs and frameworks. Now, it's debatable, someone would say, "Why do we even need an open-source implementation of such a complex system? Why not just everyone moved to the cloud?" And then everyone that's not in a cloud on-premise gets left behind.But typically that's not how open source typically works, right? The reason why we have Linux, the precursor to the cloud is because someone looked at the big proprietary Unix systems and decided to re-implement them in a way that anyone could run those systems. So when you look at Kubernetes, you have to look at it from that lens. It's the ability to democratize these platform layers in a way that other people can innovate on top. That doesn't necessarily mean that everyone needs to start with Kubernetes, just like not everyone needs to start with the Linux server, but it's there for you to build the next thing on top of, if that's the route you want to go.Corey: It's been almost a year now since I made an original tweet about this, that in five years, no one will care about Kubernetes. So now I guess I have four years running on that clock and that attracted a bit of, shall we say controversy. There were people who thought that I meant that it was going to be a flash in the pan and it would dry up and blow away. But my impression of it is that in, well four years now, it will have become more or less system D for the data center, in that there's a bunch of complexity under the hood. It does a bunch of things. No-one sensible wants to spend all their time mucking around with it in most companies. But it's not something that people have to think about in an ongoing basis the way it feels like we do today.Kelsey: Yeah, I mean to me, I kind of see this as the natural evolution, right? It's new, it gets a lot of attention and kind of the assumption you make in that statement is there's something better that should be able to arise, giving that checkpoint. If this is what people think is hot, within five years surely we should see something else that can be deserving of that attention, right? Docker comes out and almost four or five years later you have Kubernetes. So it's obvious that there should be a progression here that steals some of the attention away from Kubernetes, but I think where it's so new, right? It's only five years in, Linux is like over 20 years old now at this point, and it's still top of mind for a lot of people, right? Microsoft is still porting a lot of Windows only things into Linux, so we still discuss the differences between Windows and Linux.The idea that the cloud, for the most part, is driven by Linux virtual machines, that I think the majority of workloads run on virtual machines still to this day, so it's still front and center, especially if you're a system administrator managing BDMs, right? You're dealing with tools that target Linux, you know the Cisco interface and you're thinking about how to secure it and lock it down. Kubernetes is just at the very first part of that life cycle where it's new. We're all interested in even what it is and how it works, and now we're starting to move into that next phase, which is the distro phase. Like in Linux, you had Red Hat, Slackware, Ubuntu, special purpose distros.Some will consider Android a special purpose distribution of Linux for mobile devices. And now that we're in this distro phase, that's going to go on for another 5 to 10 years where people start to align themselves around, maybe it's OpenShift, maybe it's GKE, maybe it's Fargate for EKS. These are now distributions built on top of Kubernetes that start to add a little bit more opinionation about how Kubernetes should be pushed together. And then we'll enter another phase where you'll build a platform on top of Kubernetes, but it won't be worth mentioning that Kubernetes is underneath because people will be more interested on the thing above.Corey: I think we're already seeing that now, in terms of people no longer really care that much what operating system they're running, let alone with distribution of that operating system. The things that you have to care about slip below the surface of awareness and we've seen this for a long time now. Originally to install a web server, it wound up taking a few days and an intimate knowledge of GCC compiler flags, then RPM or D package and then yum on top of that, then ensure installed, once we had configuration management that was halfway decent.Then Docker run, whatever it is. And today feels like it's with serverless technologies being what they are, it's effectively a push a file to S3 or it's equivalent somewhere else and you're done. The things that people have to be aware of and the barrier to entry continually lowers. The downside to that of course, is that things that people specialize in today and effectively make very lucrative careers out of are going to be not front and center in 5 to 10 years the way that they are today. And that's always been the way of technology. It's a treadmill to some extent.Kelsey: And on the flip side of that, look at all of the new jobs that are centered around these cloud-native technologies, right? So you know, we're just going to make up some numbers here, imagine if there were only 10,000 jobs around just Linux system administration. Now when you look at this whole Kubernetes landscape where people are saying we can actually do a better job with metrics and monitoring. Observability is now a thing culturally that people assume you should have, because you're dealing with these distributed systems. The ability to start thinking about multi-regional deployments when I think that would've been infeasible with the previous tools or you'd have to build all those tools yourself. So I think now we're starting to see a lot more opportunities, where instead of 10,000 people, maybe you need 20,000 people because now you have the tools necessary to tackle bigger projects where you didn't see that before.Corey: That's what's going to be really neat to see. But the challenge is always to people who are steeped in existing technologies. What does this mean for them? I mean I spent a lot of time early in my career fighting against cloud because I thought that it was taking away a cornerstone of my identity. I was a large scale Unix administrator, specifically focusing on email. Well, it turns out that there aren't nearly as many companies that need to have that particular skill set in house as it did 10 years ago. And what we're seeing now is this sort of forced evolution of people's skillsets or they hunker down on a particular area of technology or particular application to try and make a bet that they can ride that out until retirement. It's challenging, but at some point it seems that some folks like to stop learning, and I don't fully pretend to understand that. I'm sure I will someday where, "No, at this point technology come far enough. We're just going to stop here, and anything after this is garbage." I hope not, but I can see a world in which that happens.Kelsey: Yeah, and I also think one thing that we don't talk a lot about in the Kubernetes community, is that Kubernetes makes hyper-specialization worth doing because now you start to have a clear separation from concerns. Now the OS can be hyperfocused on security system calls and not necessarily packaging every programming language under the sun into a single distribution. So we can kind of move part of that layer out of the core OS and start to just think about the OS being a security boundary where we try to lock things down. And for some people that play at that layer, they have a lot of work ahead of them in locking down these system calls, improving the idea of containerization, whether that's something like Firecracker or some of the work that you see VMware doing, that's going to be a whole class of hyper-specialization. And the reason why they're going to be able to focus now is because we're starting to move into a world, whether that's serverless or the Kubernetes API.We're saying we should deploy applications that don't target machines. I mean just that step alone is going to allow for so much specialization at the various layers because even on the networking front, which arguably has been a specialization up until this point, can truly specialize because now the IP assignments, how networking fits together, has also abstracted a way one more step where you're not asking for interfaces or binding to a specific port or playing with port mappings. You can now let the platform do that. So I think for some of the people who may be not as interested as moving up the stack, they need to be aware that the number of people we need being hyper-specialized at Linux administration will definitely shrink. And a lot of that work will move up the stack, whether that's Kubernetes or managing a serverless deployment and all the configuration that goes with that. But if you are a Linux, like that is your bread and butter, I think there's going to be an opportunity to go super deep, but you may have to expand into things like security and not just things like configuration management.Corey: Let's call it the unfulfilled promise of Kubernetes. On paper, I love what it hints at being possible. Namely, if I build something that runs well on top of Kubernetes than we truly have a write once, run anywhere type of environment. Stop me if you've heard that one before, 50,000 times in our industry... or history. But in practice, as has happened before, it seems like it tends to fall down for one reason or another. Now, Amazon is famous because for many reasons, but the one that I like to pick on them for is, you can't say the word multi-cloud at their events. Right. That'll change people's perspective, good job. The people tend to see multi-cloud are a couple of different lenses.I've been rather anti multi-cloud from the perspective of the idea that you're setting out day one to build an application with the idea that it can be run on top of any cloud provider, or even on-premises if that's what you want to do, is generally not the way to proceed. You wind up having to make certain trade-offs along the way, you have to rebuild anything that isn't consistent between those providers, and it slows you down. Kubernetes on the other hand hints at if it works and fulfills this promise, you can suddenly abstract an awful lot beyond that and just write generic applications that can run anywhere. Where do you stand on the whole multi-cloud topic?Kelsey: So I think we have to make sure we talk about the different layers that are kind of ready for this thing. So for example, like multi-cloud networking, we just call that networking, right? What's the IP address over there? I can just hit it. So we don't make a big deal about multi-cloud networking. Now there's an area where people say, how do I configure the various cloud providers? And I think the healthy way to think about this is, in your own data centers, right, so we know a lot of people have investments on-premises. Now, if you were to take the mindset that you only need one provider, then you would try to buy everything from HP, right? You would buy HP store's devices, you buy HP racks, power. Maybe HP doesn't sell air conditioners. So you're going to have to buy an air conditioner from a vendor who specializes in making air conditioners, hopefully for a data center and not your house.So now you've entered this world where one vendor does it make every single piece that you need. Now in the data center, we don't say, "Oh, I am multi-vendor in my data center." Typically, you just buy the switches that you need, you buy the power racks that you need, you buy the ethernet cables that you need, and they have common interfaces that allow them to connect together and they typically have different configuration languages and methods for configuring those components. The cloud on the other hand also represents the same kind of opportunity. There are some people who really love DynamoDB and S3, but then they may prefer something like BigQuery to analyze the data that they're uploading into S3. Now, if this was a data center, you would just buy all three of those things and put them in the same rack and call it good.But the cloud presents this other challenge. How do you authenticate to those systems? And then there's usually this additional networking costs, egress or ingress charges that make it prohibitive to say, "I want to use two different products from two different vendors." And I think that's-Corey: ...winds up causing serious problems.Kelsey: Yes, so that data gravity, the associated cost becomes a little bit more in your face. Whereas, in a data center you kind of feel that the cost has already been paid. I already have a network switch with enough bandwidth, I have an extra port on my switch to plug this thing in and they're all standard interfaces. Why not? So I think the multi-cloud gets lost in the chew problem, which is the barrier to entry of leveraging things across two different providers because of networking and configuration practices.Corey: That's often the challenge, I think, that people get bogged down in. On an earlier episode of this show we had Mitchell Hashimoto on, and his entire theory around using Terraform to wind up configuring various bits of infrastructure, was not the idea of workload portability because that feels like the windmill we all keep tilting at and failing to hit. But instead the idea of workflow portability, where different things can wind up being interacted with in the same way. So if this one division is on one cloud provider, the others are on something else, then you at least can have some points of consistency in how you interact with those things. And in the event that you do need to move, you don't have to effectively redo all of your CICD process, all of your tooling, et cetera. And I thought that there was something compelling about that argument.Kelsey: And that's actually what Kubernetes does for a lot of people. For Kubernetes, if you think about it, when we start to talk about workflow consistency, if you want to deploy an application, queue CTL, apply, some config, you want the application to have a load balancer in front of it. Regardless of the cloud provider, because Kubernetes has an extension point we call the cloud provider. And that's where Amazon, Azure, Google Cloud, we do all the heavy lifting of mapping the high-level ingress object that specifies, "I want a load balancer, maybe a few options," to the actual implementation detail. So maybe you don't have to use four or five different tools and that's where that kind of workload portability comes from. Like if you think about Linux, right? It has a set of system calls, for the most part, even if you're using a different distro at this point, Red Hat or Amazon Linux or Google's container optimized Linux.If I build a Go binary on my laptop, I can SCP it to any of those Linux machines and it's going to probably run. So you could call that multi-cloud, but that doesn't make a lot of sense because it's just because of the way Linux works. Kubernetes does something very similar because it sits right on top of Linux, so you get the portability just from the previous example and then you get the other portability and workload, like you just stated, where I'm calling kubectl apply, and I'm using the same workflow to get resources spun up on the various cloud providers. Even if that configuration isn't one-to-one identical.Corey: This episode is sponsored in part by our friends at Uptycs, because they believe that many of you are looking to bolster your security posture with CNAPP and XDR solutions. They offer both cloud and endpoint security in a single UI and data model. Listeners can get Uptycs for up to 1,000 assets through the end of 2023 (that is next year) for $1. But this offer is only available for a limited time on UptycsSecretMenu.com. That's U-P-T-Y-C-S Secret Menu dot com.Corey: One thing I'm curious about is you wind up walking through the world and seeing companies adopting Kubernetes in different ways. How are you finding the adoption of Kubernetes is looking like inside of big E enterprise style companies? I don't have as much insight into those environments as I probably should. That's sort of a focus area for the next year for me. But in startups, it seems that it's either someone goes in and rolls it out and suddenly it's fantastic, or they avoid it entirely and do something serverless. In large enterprises, I see a lot of Kubernetes and a lot of Kubernetes stories coming out of it, but what isn't usually told is, what's the tipping point where they say, "Yeah, let's try this." Or, "Here's the problem we're trying to solve for. Let's chase it."Kelsey: What I see is enterprises buy everything. If you're big enough and you have a big enough IT budget, most enterprises have a POC of everything that's for sale, period. There's some team in some pocket, maybe they came through via acquisition. Maybe they live in a different state. Maybe it's just a new project that came out. And what you tend to see, at least from my experiences, if I walk into a typical enterprise, they may tell me something like, "Hey, we have a POC, a Pivotal Cloud Foundry, OpenShift, and we want some of that new thing that we just saw from you guys. How do we get a POC going?" So there's always this appetite to evaluate what's for sale, right? So, that's one case. There's another case where, when you start to think about an enterprise there's a big range of skillsets. Sometimes I'll go to some companies like, "Oh, my insurance is through that company, and there's ex-Googlers that work there." They used to work on things like Borg, or something else, and they kind of know how these systems work.And they have a slightly better edge at evaluating whether Kubernetes is any good for the problem at hand. And you'll see them bring it in. Now that same company, I could drive over to the other campus, maybe it's five miles away and that team doesn't even know what Kubernetes is. And for them, they're going to be chugging along with what they're currently doing. So then the challenge becomes if Kubernetes is a great fit, how wide of a fit it isn't? How many teams at that company should be using it? So what I'm currently seeing as there are some enterprises that have found a way to make Kubernetes the place where they do a lot of new work, because that makes sense. A lot of enterprises to my surprise though, are actually stepping back and saying, "You know what? We've been stitching together our own platform for the last five years. We had the Netflix stack, we got some Spring Boot, we got Console, we got Vault, we got Docker. And now this whole thing is getting a little more fragile because we're doing all of this glue code."Kubernetes, We've been trying to build our own Kubernetes and now that we know what it is and we know what it isn't, we know that we can probably get rid of this kind of bespoke stack ourselves and just because of the ecosystem, right? If I go to HashiCorp's website, I would probably find the word Kubernetes as much as I find the word Nomad on their site because they've made things like Console and Vault become first-class offerings inside of the world of Kubernetes. So I think it's that momentum that you see across even People Oracle, Juniper, Palo Alto Networks, they're all have seem to have a Kubernetes story. And this is why you start to see the enterprise able to adopt it because it's so much in their face and it's where the ecosystem is going.Corey: It feels like a lot of the excitement and the promise and even the same problems that Kubernetes is aimed at today, could have just as easily been talked about half a decade ago in the context of OpenStack. And for better or worse, OpenStack is nowhere near where it once was. It would felt like it had such promise and such potential and when it didn't pan out, that left a lot of people feeling relatively sad, burnt out, depressed, et cetera. And I'm seeing a lot of parallels today, at least between what was said about OpenStack and what was said about Kubernetes. How do you see those two diverging?Kelsey: I will tell you the big difference that I saw, personally. Just for my personal journey outside of Google, just having that option. And I remember I was working at a company and we were like, "We're going to roll our own OpenStack. We're going to buy a free BSD box and make it a file server. We're going all open sources," like do whatever you want to do. And that was just having so many issues in terms of first-class integrations, education, people with the skills to even do that. And I was like, "You know what, let's just cut the check for VMware." We want virtualization. VMware, for the cost and when it does, it's good enough. Or we can just actually use a cloud provider. That space in many ways was a purely solved problem. Now, let's fast forward to Kubernetes, and also when you get OpenStack finished, you're just back where you started.You got a bunch of VMs and now you've got to go figure out how to build the real platform that people want to use because no one just wants a VM. If you think Kubernetes is low level, just having OpenStack, even OpenStack was perfect. You're still at square one for the most part. Maybe you can just say, "Now I'm paying a little less money for my stack in terms of software licensing costs," but from an extraction and automation and API standpoint, I don't think OpenStack moved the needle in that regard. Now in the Kubernetes world, it's solving a huge gap.Lots of people have virtual machine sprawl than they had Docker sprawl, and when you bring in this thing by Kubernetes, it says, "You know what? Let's reign all of that in. Let's build some first-class abstractions, assuming that the layer below us is a solved problem." You got to remember when Kubernetes came out, it wasn't trying to replace the hypervisor, it assumed it was there. It also assumed that the hypervisor had APIs for creating virtual machines and attaching disc and creating load balancers, so Kubernetes came out as a complementary technology, not one looking to replace. And I think that's why it was able to stick because it solved a problem at another layer where there was not a lot of competition.Corey: I think a more cynical take, at least one of the ones that I've heard articulated and I tend to agree with, was that OpenStack originally seemed super awesome because there were a lot of interesting people behind it, fascinating organizations, but then you wound up looking through the backers of the foundation behind it and the rest. And there were something like 500 companies behind it, an awful lot of them were these giant organizations that ... they were big e-corporate IT enterprise software vendors, and you take a look at that, I'm not going to name anyone because at that point, oh will we get letters.But at that point, you start seeing so many of the patterns being worked into it that it almost feels like it has to collapse under its own weight. I don't, for better or worse, get the sense that Kubernetes is succumbing to the same thing, despite the CNCF having an awful lot of those same backers behind it and as far as I can tell, significantly more money, they seem to have all the money to throw at these sorts of things. So I'm wondering how Kubernetes has managed to effectively sidestep I guess the open-source miasma that OpenStack didn't quite manage to avoid.Kelsey: Kubernetes gained its own identity before the foundation existed. Its purpose, if you think back from the Borg paper almost eight years prior, maybe even 10 years prior. It defined this problem really, really well. I think Mesos came out and also had a slightly different take on this problem. And you could just see at that time there was a real need, you had choices between Docker Swarm, Nomad. It seems like everybody was trying to fill in this gap because, across most verticals or industries, this was a true problem worth solving. What Kubernetes did was played in the exact same sandbox, but it kind of got put out with experience. It's not like, "Oh, let's just copy this thing that already exists, but let's just make it open."And in that case, you don't really have your own identity. It's you versus Amazon, in the case of OpenStack, it's you versus VMware. And that's just really a hard place to be in because you don't have an identity that stands alone. Kubernetes itself had an identity that stood alone. It comes from this experience of running a system like this. It comes from research and white papers. It comes after previous attempts at solving this problem. So we agree that this problem needs to be solved. We know what layer it needs to be solved at. We just didn't get it right yet, so Kubernetes didn't necessarily try to get it right.It tried to start with only the primitives necessary to focus on the problem at hand. Now to your point, the extension interface of Kubernetes is what keeps it small. Years ago I remember plenty of meetings where we all got in rooms and said, "This thing is done." It doesn't need to be a PaaS. It doesn't need to compete with serverless platforms. The core of Kubernetes, like Linux, is largely done. Here's the core objects, and we're going to make a very great extension interface. We're going to make one for the container run time level so that way people can swap that out if they really want to, and we're going to do one that makes other APIs as first-class as ones we have, and we don't need to try to boil the ocean in every Kubernetes release. Everyone else has the ability to deploy extensions just like Linux, and I think that's why we're avoiding some of this tension in the vendor world because you don't have to change the core to get something that feels like a native part of Kubernetes.Corey: What do you think is currently being the most misinterpreted or misunderstood aspect of Kubernetes in the ecosystem?Kelsey: I think the biggest thing that's misunderstood is what Kubernetes actually is. And the thing that made it click for me, especially when I was writing the tutorial Kubernetes The Hard Way. I had to sit down and ask myself, "Where do you start trying to learn what Kubernetes is?" So I start with the database, right? The configuration store isn't Postgres, it isn't MySQL, it's Etcd. Why? Because we're not trying to be this generic data stores platform. We just need to store configuration data. Great. Now, do we let all the components talk to Etcd? No. We have this API server and between the API server and the chosen data store, that's essentially what Kubernetes is. You can stop there. At that point, you have a valid Kubernetes cluster and it can understand a few things. Like I can say, using the Kubernetes command-line tool, create this configuration map that stores configuration data and I can read it back.Great. Now I can't do a lot of things that are interesting with that. Maybe I just use it as a configuration store, but then if I want to build a container platform, I can install the Kubernetes kubelet agent on a bunch of machines and have it talk to the API server looking for other objects you add in the scheduler, all the other components. So what that means is that Kubernetes most important component is its API because that's how the whole system is built. It's actually a very simple system when you think about just those two components in isolation. If you want a container management tool that you need a scheduler, controller, manager, cloud provider integrations, and now you have a container tool. But let's say you want a service mesh platform. Well in a service mesh you have a data plane that can be Nginx or Envoy and that's going to handle routing traffic. And you need a control plane. That's going to be something that takes in configuration and it uses that to configure all the things in a data plane.Well, guess what? Kubernetes is 90% there in terms of a control plane, with just those two components, the API server, and the data store. So now when you want to build control planes, if you start with the Kubernetes API, we call it the API machinery, you're going to be 95% there. And then what do you get? You get a distributed system that can handle kind of failures on the back end, thanks to Etcd. You're going to get our backs or you can have permission on top of your schemas, and there's a built-in framework, we call it custom resource definitions that allows you to articulate a schema and then your own control loops provide meaning to that schema. And once you do those two things, you can build any platform you want. And I think that's one thing that it takes a while for people to understand that part of Kubernetes, that the thing we talk about today, for the most part, is just the first system that we built on top of this.Corey: I think that's a very far-reaching story with implications that I'm not entirely sure I am able to wrap my head around. I hope to see it, I really do. I mean you mentioned about writing Learn Kubernetes the Hard Way and your tutorial, which I'll link to in the show notes. I mean my, of course, sarcastic response to that recently was to register the domain Kubernetes the Easy Way and just re-pointed to Amazon's ECS, which is in no way shape or form Kubernetes and basically has the effect of irritating absolutely everyone as is my typical pattern of behavior on Twitter. But I have been meaning to dive into Kubernetes on a deeper level and the stuff that you've written, not just the online tutorial, both the books have always been my first port of call when it comes to that. The hard part, of course, is there's just never enough hours in the day.Kelsey: And one thing that I think about too is like the web. We have the internet, there's webpages, there's web browsers. Web Browsers talk to web servers over HTTP. There's verbs, there's bodies, there's headers. And if you look at it, that's like a very big complex system. If I were to extract out the protocol pieces, this concept of HTTP verbs, get, put, post and delete, this idea that I can put stuff in a body and I can give it headers to give it other meaning and semantics. If I just take those pieces, I can bill restful API's.Hell, I can even bill graph QL and those are just different systems built on the same API machinery that we call the internet or the web today. But you have to really dig into the details and pull that part out and you can build all kind of other platforms and I think that's what Kubernetes is. It's going to probably take people a little while longer to see that piece, but it's hidden in there and that's that piece that's going to be, like you said, it's going to probably be the foundation for building more control planes. And when people build control planes, I think if you think about it, maybe Fargate for EKS represents another control plane for making a serverless platform that takes to Kubernetes API, even though the implementation isn't what you find on GitHub.Corey: That's the truth. Whenever you see something as broadly adopted as Kubernetes, there's always the question of, "Okay, there's an awful lot of blog posts." Getting started to it, learn it in 10 minutes, I mean at some point, I'm sure there are some people still convince Kubernetes is, in fact, a breakfast cereal based upon what some of the stuff the CNCF has gotten up to. I wouldn't necessarily bet against it socks today, breakfast cereal tomorrow. But it's hard to find a decent level of quality, finding the certain quality bar of a trusted source to get started with is important. Some people believe in the hero's journey, story of a narrative building.I always prefer to go with the morons journey because I'm the moron. I touch technologies, I have no idea what they do and figure it out and go careening into edge and corner cases constantly. And by the end of it I have something that vaguely sort of works and my understanding's improved. But I've gone down so many terrible paths just by picking a bad point to get started. So everyone I've talked to who's actually good at things has pointed to your work in this space as being something that is authoritative and largely correct and given some of these people, that's high praise.Kelsey: Awesome. I'm going to put that on my next performance review as evidence of my success and impact.Corey: Absolutely. Grouchy people say, "It's all right," you know, for the right people that counts. If people want to learn more about what you're up to and see what you have to say, where can they find you?Kelsey: I aggregate most of outward interactions on Twitter, so I'm @KelseyHightower and my DMs are open, so I'm happy to field any questions and I attempt to answer as many as I can.Corey: Excellent. Thank you so much for taking the time to speak with me today. I appreciate it.Kelsey: Awesome. I was happy to be here.Corey: Kelsey Hightower, Principal Developer Advocate at Google. I'm Corey Quinn. This is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on Apple podcasts. If you've hated this podcast, please leave a five-star review on Apple podcasts and then leave a funny comment. Thanks.Announcer: This has been this week's episode of Screaming in the Cloud. You can also find more Core at screaminginthecloud.com or wherever fine snark is sold.Announcer: This has been a HumblePod production. Stay humble.

This week we discuss Werner's AWS Keynote, Event-Based Architectures and the potential of ChatGPT. Plus, some thoughts on International Condiments. Watch the YouTube Live Recording of Episode 390 (https://www.youtube.com/watch?v=CRy69wGMROM) Runner-up Titles It's never stopped us before. Ranch dressing divine/Before the Big Bang, it was/Eternal condiment Three kinds of mayonnaise An aspirational architectural pattern. There's not a lot of architectural thought out there. I don't have a computer science degree. Mid-Code It's just a bunch of programming, how hard could it be? Is it a utopian Wall-E or not? Rundown AWS re:Invent 2022 - Keynote with Dr. Werner Vogels (https://www.youtube.com/watch?v=RfvL_423a-I) Amazon announces Eventbridge Pipes, a simpler way to connect events (https://techcrunch.com/2022/12/01/amazon-announces-eventbridge-pipes-a-simpler-way-to-connect-events-from-multiple-services/) Design Patterns (https://www.amazon.com/gp/product/0201633612/) book ChatGPT: Optimizing Language Models for Dialogue (https://openai.com/blog/chatgpt/) ChatGPT will replace StackOverflow? (https://twitter.com/anildash/status/1599655544486187009) Automating bullshit - OpenAI ChatGPT removes office worker toil (https://buttondown.email/cote/archive/automating-bullshit-openai-chatgpt-removes-office/) Coté doesn't need to write those survey analysis blogs anymore (https://beta.openai.com/playground/p/w2tNHzzV7DXsz63ZWQfKGpD4?model=text-davinci-003). Relevant to your Interests Elastic Earnings (https://twitter.com/jaminball/status/1598068640137428992?s=46&t=eFF6wBlhOCFaLPPQf7nSLQ) Snowflake Earnings (https://twitter.com/jaminball/status/1598348082839977984?s=20&t=3ZTOl6JnPJu8vtcP7YUC4Q) IBM and Maersk Abandon Ship on TradeLens Logistics Blockchain (https://www.coindesk.com/business/2022/11/30/ibm-and-maersk-abandon-ship-on-tradelens-logistics-blockchain/) OpenStack cloud sees explosive growth (https://www.zdnet.com/article/openstack-cloud-sees-explosive-growth/) Amazon EC2 Instance Types - Amazon Web Services (https://aws.amazon.com/ec2/instance-types/?trk=3478554f-e06b-44d5-8171-41d0ea80c8c9&sc_channel=ps&s_kwcid=AL!4422!3!544066093425!p!!g!!graviton%20processor&ef_id=Cj0KCQiAvqGcBhCJARIsAFQ5ke48NKL5fH2ETDPdMavKJxSfxS6luQdG2ZGGW51UzVtV8ev8GSxc2ucaAqoCEALw_wcB:G:s&s_kwcid=AL!4422!3!544066093425!p!!g!!graviton%20processor) HYPR, the Leader in Phishing-Resistant MFA, Raises $25M (https://blog.hypr.com/press-releases/hypr-the-leader-in-phishing-resistant-mfa-raises-25m?_ga=2.20718968.1905140386.1669908801-1738015730.1669908801) Future is quietly shutting down (https://twitter.com/robaeprice/status/1598393044503502860) Andreessen Horowitz's buzzy tech publication Future is shutting down (https://www.businessinsider.com/a16z-future-closes-staff-exit-2022-11?international=true&r=US&IR=T) AWS launches Application Composer, a low-code tool for building serverless apps (https://techcrunch.com/2022/12/01/aws-launches-application-composer-a-low-code-tool-for-building-serverless-apps/) No one seemed to see Bret Taylor stepping away from Salesforce (even Marc Benioff) (https://techcrunch.com/2022/12/01/no-one-seemed-to-see-bret-taylor-stepping-away-from-salesforce-even-marc-benioff/) Major password manager LastPass suffered a breach — again (https://www.npr.org/2022/12/01/1140076375/major-password-manager-lastpass-suffered-a-breach-again) Here's everything AWS announced in its re:Invent data keynote (https://techcrunch.com/2022/11/30/heres-everything-aws-announced-today/) Cloudflare hikes prices by a quarter (https://www.theregister.com/2022/12/01/cloudflare_price_rises_annual_exemptions/) Twitter lawsuit (https://twitter.com/AkivaMCohen/status/1598487532764798983) the only cheat sheet you need (https://github.com/chubin/cheat.sh) Google Plans to Lay Off 10,000 'Poor Performing' Employees. Why That's a Big Lie, According to Harvard Professor (https://www.inc.com/nick-hobson/googles-plan-to-lay-off-10000-poor-performing-employees-is-based-on-a-big-lie-according-toharvard-professor.html) Broadcom again tries to quash VMware price rise rumors (https://www.theregister.com/2022/12/01/vmware_broadcom_prices_nutanix_q123/) Rackspace email outage continues as migrations prove hard (https://www.theregister.com/2022/12/05/rackspace_hosted_exchange_security_update/) If Rowy has its way, if you can use Excel, you can build software (https://techcrunch.com/2022/12/05/rowy-pre-seed/) Axiom launches its automated identity and access management platform (https://techcrunch.com/2022/12/06/axiom-launches-its-automated-identity-and-access-management-platform/) The E-Mail Newsletter for the Mogul Set (https://www.newyorker.com/news/annals-of-communications/the-e-mail-newsletter-for-the-mogul-set) The EU hosted a 24-hour party in its $400,000 metaverse to appeal to young people, but pretty much no one showed up (https://www.businessinsider.com/eu-hosts-400000-metaverse-party-barely-anyone-shows-up-2022-12) mIRC ended its lifetime license agreement with all who purchased its software 10 years out (https://www.pocnetwork.net/internet-news/mirc-ended-its-lifetime-license-agreement-with-all-who-purchased-its-software-10-years-out/) Security compliance and automation platform Drata nabs $200M at $2B valuation (https://techcrunch.com/2022/12/07/security-compliance-and-automation-platform-drata-nabs-200m-at-2b-valuation/) 9 insights on real world container use (https://www.datadoghq.com/container-report/) Bret Taylor to step down as Salesforce co-CEO (https://www.axios.com/2022/11/30/bret-taylor-salesforce-ceo-step-down?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) Tableau Software CEO Mark Nelson steps down (https://www.geekwire.com/2022/tableau-software-ceo-mark-nelson-steps-down/) Confirmed: Slack CEO Stewart Butterfield stepping down in January (https://techcrunch.com/2022/12/05/report-slack-ceo-stewart-butterfield-stepping-down-in-january/) Microsoft Teams adds free communities feature to take on Facebook and Discord (https://www.theverge.com/2022/12/7/23497938/microsoft-teams-communities-feature) Nonsense Advent of Code (https://adventofcode.com/2022) The difference between a snafu, a shitshow, and a clusterfuck (https://qz.com/work/1225213/the-difference-between-a-snafu-a-shitshow-and-a-clusterfuck/) Dangerously Advanced Git (https://twitter.com/QuinnyPig/status/1598382103829544961?s=20&t=3ZTOl6JnPJu8vtcP7YUC4Q) Conferences THAT Conference Texas Speakers and Schedule (https://that.us/events/tx/2023/schedule/), Round Rock, TX Jan 15th-18th Use code SDT for 5% off New State of Open Con 2023, (https://stateofopencon.com/sponsors/) London, UK, February 7th-8th 2023 CloudNativeSecurityCon North America (https://events.linuxfoundation.org/cloudnativesecuritycon-north-america/), Seattle, Feb 1 – 2, 2023 DevOpsDays Birmingham, AL 2023 (https://devopsdays.org/events/2023-birmingham-al/welcome/), April 20 - 21, 2023 Listener Feedback Send “End of Year” listener questions to questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com). Tim recommends Stratechery (with Ben Thompson) | Acquired Podcast (https://www.acquired.fm/episodes/stratechery-with-ben-thompson) SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), LinkedIn (https://www.linkedin.com/company/software-defined-talk/) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: Large Mouse Pad (https://www.amazon.com/dp/B0788LMLZL?psc=1&ref=ppx_yo2ov_dt_b_product_details) Matt: Ze Frank's True Facts: Tarantulas (https://www.youtube.com/watch?v=EhJYtmZuhV4) Sriracha History (https://www.vice.com/en/article/zmj4ae/the-story-of-sriracha-is-the-story-of-america) Coté: CleanShot X (https://cleanshot.com/) Photo Credits Header (https://unsplash.com/photos/LOHduxdd73s) CoverArt (https://unsplash.com/photos/tGBXiHcPKrM)

This week we recap the news from AWS re:Invent and discuss application vendors mandating use of specific Kubernetes distros. Plus, some thoughts on dog boarding… Watch the YouTube Live Recording of Episode 389 (https://www.youtube.com/watch?v=h8L0QEIMvOs) Runner-up Titles Everyone gets a Graviton Instance What a Boring re:Invent Part of our brand 17 Days in the Hole Under the Stars, Under the Sea Tighten it up Don't make me pay for security Secure by default That's a great message and I don't believe it Works with Lambda Security, it keeps getting better? Rundown AWS re:Invent What's New at AWS – Cloud Innovation & News - 2022 Archive (https://aws.amazon.com/about-aws/whats-new/2022/?whats-new-content-all.sort-by=item.additionalFields.postDateTime&whats-new-content-all.sort-order=desc&awsf.whats-new-analytics=*all&awsf.whats-new-app-integration=*all&awsf.whats-new-arvr=*all&awsf.whats-new-blockchain=*all&awsf.whats-new-business-applications=*all&awsf.whats-new-cloud-financial-management=*all&awsf.whats-new-compute=*all&awsf.whats-new-containers=*all&awsf.whats-new-customer-enablement=*all&awsf.whats-new-customer%20engagement=*all&awsf.whats-new-database=*all&awsf.whats-new-developer-tools=*all&awsf.whats-new-end-user-computing=*all&awsf.whats-new-mobile=*all&awsf.whats-new-gametech=*all&awsf.whats-new-iot=*all&awsf.whats-new-machine-learning=*all&awsf.whats-new-management-governance=*all&awsf.whats-new-media-services=*all&awsf.whats-new-migration-transfer=*all&awsf.whats-new-networking-content-delivery=*all&awsf.whats-new-quantum-tech=*all&awsf.whats-new-robotics=*all&awsf.whats-new-satellite=*all&awsf.whats-new-security-id-compliance=*all&awsf.whats-new-serverless=*all&awsf.whats-new-storage=*all) Compute Amazon EC2 C7g instances – Compute –Amazon Web Services (https://aws.amazon.com/ec2/instance-types/c7g/?sc_icampaign=aware_ec2-c7gn-instances_reinvent22&sc_ichannel=ha&sc_icontent=awssm-11814_aware_reinvent22&sc_iplace=ribbon&trk=1b39069e-86fc-466c-99c7-4ab2427ddb3a~ha_awssm-11814_aware_reinvent22) Announcing Amazon EC2 M6in, M6idn, R6in, and R6idn network optimized instances (https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-ec2-m6in-m6idn-r6in-r6idn-network-optimized-instances/) Announcing Amazon EC2 Hpc6id instances (https://aws.amazon.com/about-aws/whats-new/2022/11/announcing-amazon-ec2-hpc6id-instances/) AWS Nitro Enclaves now supports Amazon EKS and Kubernetes (https://aws.amazon.com/about-aws/whats-new/2022/11/aws-nitro-enclaves-supports-amazoneks-kubernetes/) Introducing Finch: An Open Source Client for Container Development (https://aws.amazon.com/blogs/opensource/introducing-finch-an-open-source-client-for-container-development/) New – Accelerate Your Lambda Functions with Lambda SnapStart (https://aws.amazon.com/blogs/aws/new-accelerate-your-lambda-functions-with-lambda-snapstart/) Data Announcing Amazon Redshift integration for Apache Spark with Amazon EMR (https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-redshift-integration-apache-spark-amazon-emr/) AWS announces Amazon Redshift integration for Apache Spark (https://aws.amazon.com/about-aws/whats-new/2022/11/aws-announces-amazon-redshift-integration-apache-spark/) AWS announces Amazon Aurora zero-ETL integration with Amazon Redshift (https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-aurora-zero-etl-integration-redshift/) Serverless Open-Source Search Engine – Amazon OpenSearch Serverless (https://aws.amazon.com/opensearch-service/features/serverless/) Introducing AWS Glue 4.0 (https://aws.amazon.com/about-aws/whats-new/2022/11/introducing-aws-glue-4-0/) Security Introducing Amazon Security Lake (Preview) (https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-security-lake-preview/) AWS co-announces release of the Open Cybersecurity Schema Framework (OCSF) (https://aws.amazon.com/blogs/security/aws-co-announces-release-of-the-open-cybersecurity-schema-framework-ocsf-project/) Amazon GuardDuty now protects Amazon Elastic Kubernetes Service clusters (https://aws.amazon.com/about-aws/whats-new/2022/01/amazon-guardduty-elastic-kubernetes-service-clusters/) Solutions AWS CEO: The cloud isn't just about technology (https://www.protocol.com/enterprise/aws-adam-selipsky-cloud) AWS Supply Chain (https://aws.amazon.com/aws-supply-chain/) AWS Clean Room (https://aws.amazon.com/clean-rooms/) Announcing AWS SimSpace Weaver (https://aws.amazon.com/about-aws/whats-new/2022/11/aws-simspace-weaver-available/) Amazon Connect announces Contact Lens agent performance evaluation forms (https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-connect-contact-lens-agent-performance-evaluation-forms/) Introducing Amazon Omics (https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-omics-generally-available/) Corey Quinn on re:Invent (https://twitter.com/QuinnyPig/status/1597664998234345472) Ask SDT — “using a "supported platform" list to drive cross sales.” (https://softwaredefinedtalk.slack.com/archives/C6CDLDCVB/p1669255641385689) (SDT Slack) Relevant to your Interests SigmaOS raises $4 million to build a browser for productivity nerds (https://techcrunch.com/2022/11/16/sigmaos-raises-4-million-to-build-a-browser-for-productivity-nerds/) The Distributed Computing Manifesto (https://www.allthingsdistributed.com/2022/11/amazon-1998-distributed-computing-manifesto.html) Unpacking Musk's "hardcore" marching orders (https://www.axios.com/newsletters/axios-login-3bf3c6e4-d8cd-492c-942d-c7f80719e66b.html?chunk=0&utm_term=emshare#story0) Akeyless secures a cash infusion to help companies manage their passwords, certificates and keys (https://techcrunch.com/2022/11/16/akeyless-secures-a-cash-infusion-to-help-companies-manage-their-passwords-certificates-and-keys/) Vista passes halfway mark to $20bn target for latest flagship (https://www.privateequityinternational.com/vista-passes-halfway-mark-to-20bn-target-for-latest-flagship/) 1Password Will Support Passkeys Starting in Early 2023 (https://www.macrumors.com/2022/11/17/1password-passkeys-support-2023/) Passkeys: the future of authentication in 1Password (https://www.future.1password.com/passkeys/?utm_medium=sign-in-side-panel&utm_source=1password&utm_campaign=passkeys) 10,000 Google Employees Could Be Rated as Low Performers (https://www.theinformation.com/articles/10-000-google-employees-could-be-rated-as-low-performers) Resignations Roil Twitter as Elon Musk Tries Persuading Some Workers to Stay (https://www.nytimes.com/2022/11/17/technology/twitter-elon-musk-ftc.html) Hundreds of employees say no to being part of Elon Musk's ‘extremely hardcore' Twitter (https://www.theverge.com/2022/11/17/23465274/hundreds-of-twitter-employees-resign-from-elon-musk-hardcore-deadline) Security of Passkeys in the Google Password Manager (https://security.googleblog.com/2022/10/SecurityofPasskeysintheGooglePasswordManager.html) With $8.6M in seed funding, Nx wants to take monorepos mainstream (https://techcrunch.com/2022/11/17/with-8-6m-in-seed-funding-nx-wants-to-take-monorepos-mainstream/) Facebook parent Meta winding down some non-core hardware projects (https://www.reuters.com/technology/facebook-parent-meta-winding-down-some-non-core-hardware-projects-2022-11-11/) OpenStack passes 40 million cores in production use (https://www.theregister.com/2022/11/18/openstack_thriving_survey/) A note from CEO Andy Jassy about role eliminations (https://www.aboutamazon.com/news/company-news/a-note-from-ceo-andy-jassy-about-role-eliminations) Twitter is Going Great (https://twitterisgoinggreat.com/) Building Kubernetes Applications with Acorn (https://acorn.io/building-kubernetes-applications-with-acorn/) Platforms at Kubecon 2022 (https://blog.joshgav.com/posts/kubecon-platforms-review) Zoom's looming squeeze (https://www.axios.com/newsletters/axios-login-149ea16b-be11-451a-b4de-5a1e2f8f0ce7.html?chunk=0&utm_term=emshare#story0) Sony's VR headset-console integration could limit sales, but allow depth (https://www.emergingtechbrew.com/stories/2022/11/18/sony-s-vr-headset-console-integration-could-limit-sales-but-allow-depth?utm_campaign=etb&utm_medium=newsletter&utm_source=morning_brew&mid=f642abf4dca6751d0ec109d4cbc6782e) The State of Kubernetes {Open-Source} Security | ARMO (https://www.armosec.io/blog/the-state-of-kubernetes-open-source-security/) Considerations when implementing developer portals in regulated enterprise environments (https://www.redhat.com/en/blog/considerations-when-implementing-developer-portals-regulated-enterprise-environments) Broadcom's proposed $61B VMware acquisition scrutinized by UK regulators (https://techcrunch.com/2022/11/21/broadcoms-proposed-61b-vmware-acquisition-scrutinized-by-uk-regulators/) 2023 may be the year of multicloud Kubernetes (https://www.infoworld.com/article/3679752/2023-may-be-the-year-of-multicloud-kubernetes.html?utm_source=substack&utm_medium=email) Server-side WebAssembly prepares for takeoff in 2023 (https://www.techtarget.com/searchitoperations/news/252527414/Server-side-WebAssembly-prepares-for-takeoff-in-2023?utm_source=substack&utm_medium=email) Zoom shares drop on light forecast as company faces 'heightened deal scrutiny' (https://www.cnbc.com/2022/11/21/zoom-zm-earnings-q3-2023.html?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) What's coming for cloud computing in 2023 (https://www.infoworld.com/article/3680553/whats-coming-for-cloud-computing-in-2023.html) The Rise of Platform Engineering - Software Engineering Daily (https://softwareengineeringdaily.com/2020/02/13/setting-the-stage-for-platform-engineering/) IBM sues Micro Focus, claims it copied mainframe software (https://www.theregister.com/2022/11/22/ibm_sues_micro_focus_for/) How to beat the Kubernetes skills shortage (https://www.infoworld.com/article/3679749/how-to-beat-the-kubernetes-skills-shortage.html) TikTok Couldn't Ensure Accurate Responses To Government Inquiries, A ByteDance Risk Assessment Said (https://www.forbes.com/sites/emilybaker-white/2022/11/28/tiktok-inaccurate-government-inquiries-internal-bytedance-risk-assessment/?sh=7f57dc9723fe) Exclusive: Sam Bankman-Fried says he's down to $100,000 (https://www.axios.com/2022/11/29/sam-bankman-fried-100000-ftx-cftc-regulation?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axiosprorata&stream=top) Why Big Tech is not rushing to clone Twitter (https://www.axios.com/newsletters/axios-login-1cea6d1a-1428-448d-b0d3-5da3ae9425ef.html?chunk=0&utm_term=emshare#story0) Amazon Alexa is a “colossal failure,” on pace to lose $10 billion this year (https://arstechnica.com/gadgets/2022/11/amazon-alexa-is-a-colossal-failure-on-pace-to-lose-10-billion-this-year/) I analyzed 290 booths at KubeCon - here are the DevOps trends for 2023 (https://www.uptime.build/post/i-analyzed-290-booths-at-kubecon-here-are-the-devops-trends-for-2023?utm_source=substack&utm_medium=email) Nonsense Billionaires like Elon Musk want to save civilization by having tons of genetically superior kids. Inside the movement to take 'control of human evolution.' (https://www.businessinsider.com/pronatalism-elon-musk-simone-malcolm-collins-underpopulation-breeding-tech-2022-11) Australia: How 'bin chickens' learnt to wash poisonous cane toads (https://www.bbc.com/news/world-australia-63699884) A 12,000 lb. metal sculpture of Elon Musk's head on a goat body riding a rocket parked outside Tesla HQ failed to elicit a response from the billionaire (https://www.businessinsider.com/elon-musk-head-on-goat-body-riding-a-rocket-sculpture-2022-11) The leap second's time will be up in 2035—and tech companies are thrilled (https://www.popsci.com/technology/bipm-abandon-leap-second/) Conferences THAT Conference Texas Speakers and Schedule (https://that.us/events/tx/2023/schedule/). Jan 15th-18th use code SDT for 5% off CloudNativeSecurityCon North America (https://events.linuxfoundation.org/cloudnativesecuritycon-north-america/), Seattle, Feb 1 – 2, 2023 DevOpsDays Birmingham, AL 2023 (https://devopsdays.org/events/2023-birmingham-al/welcome/), April 20 - 21, 2023 Listener Feedback Sudesh shared a list of Tech Companies Hiring (https://airtable.com/shrAPDHg8apj4mnRR/tbl6Kz4KeeCp3HrSM) Send “End of Year” listener questions to questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com). SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), LinkedIn (https://www.linkedin.com/company/software-defined-talk/) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: The Complete History & Strategy of Qualcomm (https://www.acquired.fm/episodes/qualcomm) Matt: Kishi Bashi This Must Be The Place (https://www.youtube.com/watch?v=IslMHJFkIME) Carma (https://carma.com.au) car purchase: referral code: REF22-872E Photo Credits Header (https://unsplash.com/photos/K8i-gRJHT_0) CoverArt (https://twitter.com/DevchicaJasmin/status/1597874321510526978)

Today on the Tech Bytes podcast we welcome back sponsor Nokia to talk about a compelling feature in Nokia's Fabric Services System. This feature, called Connect, lets Fabric Services System integrate with platforms such as VMware, OpenStack, and Kubernetes to streamline the provisioning of network services in Top Of Rack switches when new workloads or services are instantiated.

Today on the Tech Bytes podcast we welcome back sponsor Nokia to talk about a compelling feature in Nokia's Fabric Services System. This feature, called Connect, lets Fabric Services System integrate with platforms such as VMware, OpenStack, and Kubernetes to streamline the provisioning of network services in Top Of Rack switches when new workloads or services are instantiated. The post Tech Bytes: Nokia Fabric Services System Streamlines Network Automation For Application Stacks (Sponsored) appeared first on Packet Pushers.