Podcasts about Mesosphere

Tobi Knaup (@superguenter, VP/GM of Cloud Native @Nutanix) talks about the evolution of the cloud-native ecosystem, the intersection of AI and Kubernetes, and expectations of the next few years.  SHOW: 931SHOW TRANSCRIPT: The Cloudcast #931 TranscriptSHOW VIDEO: https://youtube.com/@TheCloudcastNET CLOUD NEWS OF THE WEEK:  http://bit.ly/cloudcast-cnotwNEW TO CLOUD? CHECK OUT OUR OTHER PODCAST:  "CLOUDCAST BASICS" SPONSORS:[VASION] Vasion Print eliminates the need for print servers by enabling secure, cloud-based printing from any device, anywhere. Get a custom demo to see the difference for yourself.[US CLOUD] Cut Enterprise IT Support Costs by 30-50% with US CloudSHOW NOTES:Nutanix Cloud NativeThe Cloudcast #211 - Mesosphere DCOSTopic 1 - Welcome to the show! Full disclosure for everyone out there, I worked for Tobi at Nutanix. Give everyone a brief introduction and a little about your background.Topic 2 - This is a throwback for our long-time listeners. We had Ben Hindman on episode #211 almost 10 years ago, when D2IQ was Mesosphere, and we also spoke to Dave Lester, who was at Twitter back in 2014.  I'm not going to ask you to catch everyone up on 10 years of your company and the history… but I will encourage everyone to go back and listen to that podcast. It is an excellent snapshot of the early days of cloud native and containers. Today, we will talk a bit about the state of cloud native. The most recent KubeCon EU was a few months ago. What were your thoughts around the event and the current state of the industry? Topic 3 - What are the most prominent challenges organizations face today with Cloud Native adoption?  You hear about the complexity, you hear about Kubernetes is a platform to build platforms… still true?Topic 4 - Where do you think Cloud Native goes in the next 2-3 years? What technologies or design patterns (besides AI, we'll talk about that later) evolve, and where does the next round of adoption come from?Topic 5 - Let's talk about storage and data services quickly. Data services for K8s is messy, really messy at times. Give everyone an overview of the problem at scale and the challenges, especially in multi-cloud environments, which I'm finding more and more.Topic 6 - I'd be remiss if I didn't mention AI and its impact in the space. AI came along and sucked all the air out of the room for a time. How do you think about AI today, now that the dust has settled a bit? Is it just an “app” to run on top? How will AI impact cloud native longer term?FEEDBACK?Email: show at the cloudcast dot netBluesky: @cloudcastpod.bsky.socialTwitter/X: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

On this Screaming in the Cloud Replay, we're revisiting our conversation with Tobi Knaup, the current VP & General Manager of Cloud Native at Nutanix. At the time this first aired, Tobi was the co-founder and CTO of D2iQ before the company was acquired by Nutanix. In this blast from the past, Corey and Tobi discuss why Mesosphere rebranded as D2iQ and why the Kubernetes community deserves the credit for the widespread adoption of the container orchestration platform. Many people assume Kubernetes is all they need, but that's a mistake, and Tobi explains what other tools they end up having to use. We'll also hear why Tobi thinks that multi-cloud is the future (it is the title of the episode after all).Show Highlights(0:00) Intro(0:28) The Duckbill Group sponsor read(1:01) Memosphere rebranding to D2iQ(4:34) The strength of the Kubernetes community(7:43) Is open-source a bad business model?(10:19) Why you need more than just Kubernetes(13:13) The Duckbill Group sponsor read(13:55) Is multi-cloud the best practice?(17:31) Creating a consistent experience between two providers(19:05) Tobi's background story(24:24) Memories of the days of physical data centers(28:00) How long will Kubernetes be relevant(30:18) Where you can find more from TobiAbout Tobi KnaupTobi Knaup is the VP & General Manager of Cloud Native at Nunatix. Previously, he was the Co-Founder and CTO of D2iQ Kubernetes Platform before Nutanix acquired the company. Knaup is an experienced software engineer focusing on large scale systems and machine learning. Tobi's research work is on Internet-scale sentiment analysis using online knowledge, linguistic analysis, and machine learning. Outside of his tech work, he enjoys making cocktails and has collected his favorite recipes on his cocktail website.LinksTobi's Twitter: https://twitter.com/superguenterLinkedIn URL: https://www.linkedin.com/in/tobiasknaup/Personal site: https://tobi.knaup.me/Original Episodehttps://www.lastweekinaws.com/podcast/screaming-in-the-cloud/multi-cloud-is-the-future-with-tobi-knaup/SponsorThe Duckbill Group: duckbillgroup.com 

On The Space Show for Wednesday, 22 May 2024: Planet Earth: How space technology helps us understand our home planet — S4E62 The PREFIRE (Polar Radiant Energy in the Far-InfraRed Experiment) satellites: Measuring the full spectrum of polar radiant energy The GRACE-Continuity and their predecessors' findings, GRACE and GRACE-Follow-on The end of the AIM (Aeronomy of Ice in the Mesosphere) mission Satellite observations of the Hunga Tonga - Hunga Ha'apai eruption and a sonification of Aeolus data Plans for the Libera satellite to succeed the CERES instrument on the Terra satellite, which is nearing the end of its life.

Albert's role as CTO & SVP of Engineering at Rippling is marked by an impressive blend of technical expertise and leadership experience. In discussion with host Aydin Mirzaee, Albert delves into the diverse experiences that have shaped his career, including pivotal positions at Segment, Mesosphere, and Cloudflare. His journey from engineering roles to top-tier management illustrates his deep commitment to hands-on leadership and continuous improvement. A cornerstone of Albert's leadership philosophy is fostering an environment where both innovation and quality are prioritized. He highlights Rippling's strategic planning processes, including the importance of setting clear, actionable goals and maintaining flexibility to adapt to new information. Albert also touches on the future of HR software, emphasizing the integration of AI and the critical role of understanding employee data to drive better business outcomes. In episode 6 of season 2, Albert emphasizes the significance of effective project management through mechanisms like blitz meetings, which streamline decision-making and ensure efficient execution of critical initiatives. His insights into leadership, team dynamics, and the evolving landscape of HR technology provide listeners with valuable strategies to implement in their own organizations. Tune in to explore Albert's techniques and insights that have contributed to Rippling's success as a fast-growing technology company, valued at over $13 billion.  This episode offers a wealth of actionable advice for leaders looking to drive innovation, maintain quality, and lead with intention and impact. . . . Like this episode? Be sure to leave a ⭐️⭐️⭐️⭐️⭐️ review and share the podcast with your colleagues. . . . TIME-STAMPED SHOW NOTES: [03:26] Advice for aspiring leaders [07:09]  The importance of being hands-on leader [11:58] Planning and prioritization in a rapidly growing company [19:03] Utilizing Quality Weeks [29:50] Strategic planning and setting goals [34:48] The future of HR software and the role of AI [40:40] Underrated leadership advice  

Sign up for our next LLM in production conference: https://go.mlops.community/prodiii #180 with LLMs in Production Conference part 2 Ux of a LLM User Panel, Misty Free, Dina Yerlan, and Artem Harutyunyan hosted by Innovation Endeavors' Davis Treybig. // Abstract Explore different approaches to interface design, emphasizing the significance of crafting effective prompts and addressing accuracy and hallucination issues. Discover some strategies for improving latency and performance, including monitoring, scaling, and exploring emerging technologies. // Bio Misty Free Misty Free is a product manager at Jasper, where she focuses on supercharging marketers with speed and consistency in their marketing campaigns, with the power of AI. Misty has also collaborated with Stability and OpenAI to offer AI image generation within Jasper. She approaches product development with a "jobs-to-be-done" mindset, always starting with the "why" behind any need, ensuring that customer pain points are directly addressed with the features shipped at Jasper. In her free time, Misty enjoys crocheting amigurumi, practicing Spanish on Duolingo, and spending quality time with her family. Misty will be on a panel sharing her insights and experiences on the real-world use cases of LLMs. Davis Treybig Davis is a partner at Innovation Endeavors, an early-stage venture firm focused on teams solving hard technical & engineering problems. He personally focuses on computing infrastructure, AI/ML, and data. Dina Yerlan Head of Product, Generative AI Data at Adobe Firefly (family of foundation models for creatives). Artem Harutyunyan Artem is the Co-Founder & CTO at Bardeen AI. Prior to Bardeen, he was in engineering and product roles at Mesosphere and Qualys, and before that, he worked at CERN. // MLOps Jobs board https://mlops.pallet.xyz/jobs // MLOps Swag/Merch https://mlops-community.myshopify.com/ // Related Links ⁠Website: https://www.angellist.com/venture/relay Foundation by Isaac Asimov: https://www.amazon.com/Foundation-Isaac-Asimov/dp/0553293354 AngelList Relay blog: https://www.angellist.com/blog/introducing-angellist-relay --------------- ✌️Connect With Us ✌️ ------------- Join our slack community: https://go.mlops.community/slack Follow us on Twitter: @mlopscommunity Sign up for the next meetup: https://go.mlops.community/register Catch all episodes, blogs, newsletters, and more: https://mlops.community/ Connect with Demetrios on LinkedIn: https://www.linkedin.com/in/dpbrinkm/ Connect with Davis on LinkedIn: https://www.linkedin.com/in/davistreybig/ Connect with Misty on LinkedIn: https://www.linkedin.com/in/misty-miglorin/ Connect with Dina on LinkedIn: https://www.linkedin.com/in/dinayerlan/ Connect with Artem on LinkedIn: https://www.linkedin.com/in/artemharutyunyan/

Timothy Chen is the founder and general partner at Essence Ventures, a VC firm that specializes in data infrastructure and developer tools. Prior to Essence, he was the SVP of Engineering at Cosmos, a popular open source blockchain SDK. He cofounded Hyperpilot with Stanford Professor Christos Kozyrakis to disrupt the enterprise infrastructure space, which later exited to Cloudera. He was an early employee at Mesosphere and CloudFoundry. He is also active in the open source space as an Apache member.In this episode, we cover a range of topics including: - Using LLMs for devops work - Open source AI - How to spot open source investment opportunities - Data infrastructure opportunities - AI infrastructure opportunities - Security and privacy Timothy's favorite book: Behind The Cloud (Author: Marc Benioff)--------Where to find Prateek Joshi: Newsletter: https://prateekjoshi.substack.com Website: https://prateekj.com LinkedIn: https://www.linkedin.com/in/prateek-joshi-91047b19 Twitter: https://twitter.com/prateekvjoshi 

Tim Chen is the Managing Partner at Essence VC, an early-stage fund focused on data infrastructure and developer tool companies. He has over a decade of experience leading engineering in enterprise infrastructure and open source communities and companies. Prior to Essence, Tim was the SVP of Engineering at Cosmos, a popular open source blockchain SDK. Prior to Cosmos, Tim co-founded Hyperpilot with Stanford Professor Christos Kozyrakis, leveraging decades of research to disrupt the enterprise infrastructure space, which later exited to Cloudera. Prior to Hyperpilot, Tim was an early employee at Mesosphere and CloudFoundry. He is also active in the open source space as an Apache Software Foundation core member, maintainer of Apache Drill and Apache Mesos, and CNCF TOC contributor. --- Send in a voice message: https://podcasters.spotify.com/pod/show/startupproject/message

On this episode of Astronomy Daily, Tim and Halle bring you latest on the Gemini North Telescope's capture of a supernova aftermath and other space news. In this episode, you will be able to: · Stay ahead with groundbreaking astronomy news that will pique your curiosity. · Uncover the spellbinding secrets behind Planet Hat-P 32 b's disappearing act. · Get a rare glimpse into the spectacular phenomenon of Noctilucent clouds found in Earth's atmosphere. · Experience the powerful aftermath of a supernova through the lens of the Gemini North Telescope. · Demystify the complexities of solar wind and its implications on our solar system with help from Parker Solar Probe. Get ready to be captivated by Hallie, our skilled AI reporter with a knack for breaking down complex celestial concepts for everyone to enjoy. Over her career, Hallie has established a strong reputation in the field for her thorough research on deep-space phenomena, including supernovae, galaxies, and black holes. Today, she's here to discuss the groundbreaking capture of a supernova aftermath by the Gemini North Telescope, shedding light on how technology is helping us understand the universe. Join Hallie and Tim to explore the wonders of the cosmos and learn more about this awe-inspiring observation. The resources mentioned in this episode are: · Visit Airbus' website to learn more about Roxy, the system that extracts oxygen and metals from lunar regolith. · Check out the Frownhoffer, the German Research Institute, and Boston University websites to see their collaboration with Airbus on the Roxy project. · Explore the European Space Agency's website to learn more about the Mars Express Orbiter and its mapping of the Martian surface. · Visit SpaceNuts.io to listen to the SpaceNuts podcast with Steve Dunkley on Mondays and Astronomy Daily with Tim Gibbs on Fridays. · Look up at the Northern Hemisphere's northern skies an hour or two after sunset and before sunrise over the next few months to see rare noctilucent clouds with the naked eye. · Follow SpaceWeather.com to stay updated on sightings of noctilucent clouds. · Read the journal Science Advances to learn more about the discovery of the giant tails of helium escaping from the planet Hat P 32 b. · Check out the University of Texas at Austin's McDonald Observatory website to learn more about the Hobby Eberley Telescope. · Follow NASA's Sunkissing Parker Solar Probe mission to stay updated on its findings about the solar wind. · Visit the D Noctilucent Clouds: The highest, driest, coldest, and rarest clouds on Earth. Noctilucent clouds (NLCs) are unique and intriguing atmospheric phenomena found in the Mesosphere, a layer above the stratosphere and below the thermosphere, around 47 to 53 miles above Earth's surface. Formed when water vapor freezes into ice crystals that attach to dust and particles left by meteors, NLCs offer a valuable opportunity for observing changes in Earth's atmosphere. These spectacular clouds are best visible around the summer solstice in late June through the end of July, making them a fascinating subject for skywatchers and scientists alike. As Tim Gibbs and Halle discuss noctilucent clouds in the episode, they touch upon the importance of understanding these rare clouds to study Earth's atmosphere and the effects of climate change. The friendly conversation drives home the point that these mesmerizing natural wonders truly deserve our attention and study. Supernova in the Pinwheel Galaxy: The discovery of the supernova SN 2023 IX by an amateur astronomer and how the Gemini North Telescope will allow astronomers to study it. Amateur astronomer Koichi Itagaki's discovery of supernova SN 2023 IX in the Pinwheel Galaxy is a testament to the passion and curiosity of stargazers worldwide. The aftermath of this supernova serves as a fantastic example of celestial phenomena that can be detected and studied by both professional and amateur astronomers. The Gemini North Telescope's observations of SN 2023 IX will enable astronomers to analyze how the supernova's light fades over time and how its spectrum evolves, shedding light on the complex physics of stellar explosions. Tim Gibbs and Halle's conversation about the discovery of SN 2023 IX leads them to highlight the importance of amateur astronomers contributing to the scientific community. By sharing this inspiring story, they encourage listeners to stay curious and participate in the vast and fascinating world of astronomy. Learn how the Gemini North Telescope captures supernova remnants and deepens our understanding of the universe. The Gemini North Telescope, after a seven-month hiatus, is back in action and it captured the stunning aftermath of a supernova in the Pinwheel Galaxy. Supernovae are massive explosions of stars, which provide valuable information about the history and evolution of the universe. By observing supernova remnants, scientists can gain insights into the formation of heavy elements and the rate of expansion of the universe. This knowledge can also contribute to our understanding of stellar life cycles and the overall structure of galaxies. During the episode, Tim Gibbs and Halle discuss the discoveries made by the Gemini North Telescope, as well as the story of amateur astronomer Koichi Itagaki, who found the supernova named SN 2023 IX. The discussion highlights the importance of such observations in helping astronomers study the light spectrum of these explosions, and how this data can enhance our understanding of the physics behind supernovae. Giant Tails of Helium: The dramatic jets of helium escaping from the planet Hat P 32 b. The planet Hat P 32 b has captured the attention of astronomers due to its dramatic jets of helium, which extend more than 50 times the planet's radius. These remarkable tails of gas make it an exceptional case in the realm of exoplanets. The study of these tails can provide insights into the process and mechanisms of atmospheric escape, wherein lighter gases like helium are stripped away from a planet by the radiation and stellar wind coming from its host star. This understanding can shed light on the evolution and history of exoplanets' atmospheres. In the episode, Halle shares details about the fascinating discovery of Hat P 32 b's incredible helium tails, which were observed by a team of astronomers using the Hobby Eberly Telescope at the University of Texas at Austin's McDonald Observatory. The friendly discussion between Tim Gibbs and Halle emphasizes the significance of this finding in the field of exoplanetary research. Source of Fast Solar Wind: NASA's Parker Solar Probe discovers that the fast solar wind comes from coronal holes in the Sun's atmosphere and how this information can help predict solar storms. NASA's Parker Solar Probe has made groundbreaking discoveries regarding the source of fast solar wind – the charged particles that stream from the Sun's corona at incredible speeds. The probe's close approach to the Sun revealed that fast solar wind originates from coronal holes in the Sun's atmosphere. This information is crucial for understanding how solar storms and space weather events are generated, which can have significant impacts on communication and power systems on Earth, as well as create stunning auroras. In the episode, Tim Gibbs and Halle share their excitement about the Parker Solar Probe's findings and the importance of understanding solar wind's origins. Their conversation highlights how studies of solar activity can help us better predict and respond to potential space weather events, safeguarding our planet's interconnected systems.

In this episode I talk with Miska Kaipiainen, VP Engineering, Strategy & Open Source Software at Mirantis. Mirantis helps organizations ship code faster on public and private clouds. They provide a public cloud experience on any infrastructure from the data center to the edge. Miska focuses in on Lens which empowers a new breed of Kubernetes developers by removing infrastructure and operations complexity and providing one cohesive cloud experience for complete app and DevOps portability. We also cover the current state of Kubernetes adoption and how focusing on developers with Lens as a Kubernetes IDE has seen tremendous growth for the product, which is Open Source. Mirantis was founded in 1999 and is headquartered in Campbell, California. ☑️ Technology and Technology Partners Mentioned: Kubernetes, Mesosphere, Docker Enterprise, Docker Swarm, OpenStack, Open Source ☑️ Raw Talking Points: Container Orchestration Kontena days Origin of Lens Mirantis Len acquisition Strong community support Operations vs Development Why is a Kubernetes IDE important Where is Kubernetes uptake today Enterprise Adoption OpenSource - Organic growth Community stop marketing Service and Support K0s DevOps Care Team Spaces Managed Dev Cluster Multi-Cluster manangement Multi-platform ☑️ Web: https://www.mirantis.com/ https://k8slens.dev/ ☑️ Interested in being on #GTwGT? Contact via Twitter @GTwGTPodcast or go to https://www.gtwgt.com☑️ Music: https://www.bensound.com

This episode features an interview with Joseph Jacks, Founder and General Partner of OSS Capital. OSS Capital is the first and only COSS (Commercial Open Source Software) company investor that focuses on supporting early-stage COSS founders. Joseph, also known as JJ, has worked at Mesosphere, TIBCO Software, and Talend in various sales, engineering, and strategy roles. In this episode, JJ and Sam weigh the trade-offs of open and closed core companies and discuss how each can go public. JJ also dives into the misconception of trust equating privacy within tech. Guest Quote [25:14]: “There's a societal recognition that if you use technology to automate some part of your life and you use that regularly, you have to be able to trust it. And I think gradually, consumers are becoming more and more aware that one of the most effective ways of checking the trust box is answering the question, ‘Is the technology I'm using open source at the core, yes or no?' And if the answer is no, I think it's very difficult and a lot harder to achieve the levels of trust that you can if the answer is yes.” – Joseph Jacks Time Stamps [12:59]: The difference between open and closed core companies [17:23]: Understanding the trade-off between open and closed source [18:23]: Trends within open source data companies [20:21]: Is it possible to go public as a closed source database? [22:35]: Leveraging the automation opportunity of open source systems [23:47]: How can consumers trust the technology they're using? [34:01]: Advice for those starting open source projects Links LinkedIn - Connect with JJ LinkedIn - Connect with OSS Capital Twitter - Follow OSS Capital Visit OSS Capital See omnystudio.com/listener for privacy information.

If haven't already hit "play", what are you waiting for? This is a highly entertaining one as our returning champ goes against Julia Geschke. Oh, and don't forget to order your 2022 desk calendar at triviacalendar.net! CARD 1 CLUE: Like a cake or an onion CATEGORY: Layers of the atmosphere ANSWERS: Exosphere, Thermosphere, Mesosphere, Stratosphere, Troposphere, Ozone, Ionosphere CARD 2 CLUE: Not McDuck CATEGORY: Things associated with a Christmas Carol ANSWERS: Dickens, Grumpy, Scrooge, Spirit, Past, Present, Future CARD 3 CLUE: Puff you up CATEGORY: Types of pastry ANSWERS: Pie, Strudel, Baklava, Croissant, Danish, Empanada, Roll CARD 4 CLUE: He belongs in a museum CATEGORY: Things associated with Harrison Ford ANSWERS: Star Wars, Fugitive, Indiana Jones, Witness, Han Solo, Calista Flockhart, Blade Runner CARD 5 CLUE: That's cold CATEGORY: Things associated with hockey ANSWERS: Ice, Rink, Goal, Fans, Jersey, Pads, Pucks CARD 6 CLUE: Yer a wizard CATEGORY: Things associated with Harry Potter ANSWERS: Dumbledore, Hermione, Hagrid, Hogwarts, Magic, Azkaban, Weasley

Anatoly Yakovenko (00:12):Hey folks, this is Anatoly, and you're listening to The Solana Podcast. And today I have Jonathan Schemoul with me, who's the founder of the Aleph.im project. Really awesome to have you.Jonathan Schemoul (00:22):Thank you very much. I'm really happy to be here today.Anatoly Yakovenko (00:25):Cool. We usually start these with a simple question, how did you get into crypto? What's your story? What's the origin story?Jonathan Schemoul (00:36):Well, into crypto it's a long story. I started way back in time, a bit on Bitcoin then I stopped because it was only money back then. And that wasn't the end game for me. Then I came back into crypto in 2015, 2016, and I started doing a bit of development because I saw that I really wanted to be part of Web 3, to do nice things with it. I started developing as an open-source developer for a few projects. One of these is the newest project which is Chinese blockchain layer one. I'm not really involved with it anymore.Jonathan Schemoul (01:16):But working with them as a community open source developer, I saw that there was some missing links somewhere that you couldn't decentralize all the stack with just layer one, it is not the one that they were building back then. So that's how the Aleph.im project is born. For me, besides that, I've been developing for a lot of companies before in the IOT space and also for big banks sometime ago. I've been a developer for a lot of years.Anatoly Yakovenko (01:48):That's great. I mean, that's a great background. The thing that you're focusing on with Aleph is this idea that Web 3 is just a small part of the piece, but you still need UI front-ends, business logic and things sitting on top of the blockchain. How does that work?Jonathan Schemoul (02:09):The idea is that, okay, now you can have smart contracts on Solana, that's great. You can even do way much more on like just money on smart contracts, that's great. Now, you need to have a front-end. So you need to have storage for that front-end. That's not all because a smart contract, a program doesn't have all the data that you need. So you will need some kind of indexing to get history. You will need a back-end for that.Jonathan Schemoul (02:37):Most of the DeFi application that we see have some centralized back-end behind them. They're running on AWS, sometimes on dedicated servers or stuff like that that is still centralized. If a government, and we just saw something about it today, wants to shut down the DeFi protocol that is organized like that, they can. With Aleph.im what we are trying to do is decentralize the last mile, because for that last mile most projects are using AWS, so we need to decentralize AWS.Jonathan Schemoul (03:11):So we provide storage, as in file storage for the front-end files, database storage, because most applications are just databases and also an equivalent to Amazon Lambda, where you start small functions that will be launched on a decentralized cloud, where there is place for them and will get you a return value, and these can be written in any language and connects the web and also a PC from blockchains here at Solana obviously.Anatoly Yakovenko (03:42):Got it. Super Cool. So this is a storage mechanism. Does it guarantee consistency? How's it decentralized? What happens if you nuke it? Yellowstone flows up, the current set of servers from Aleph get destroyed in the volcano. How do I move, switch, what state do I lose? Those are the hard distributed systems question.Jonathan Schemoul (04:08):Yeah. It's a really good question. Aleph.im is not a blockchain at all. We don't have a blockchain. There are enough already. We just accept messages from blockchains. All the supported blockchains are accepted on the network, that means that that message that is signed by a material address is accepted on network, a message that is signed by a certain address is accepted on the network. All our network, hence the name .im, dot instant messaging, the whole system works with messages on the network.Jonathan Schemoul (04:45):Those messages are organized by channels, just like you would go on telegram channels and get the history of them. The network keeps track of those messages and when you start a new node, you get the history of messages, not directly from the other nodes, you will connect two blockchains to specific smart contracts on blockchain. Look at past events, for example, on the Ethereum or on Solana. You look at past events for the synchronization of the network and you look, okay, there has been all these events, okay, let me ask the whole network what those messages were. Then you resync, when there are missing parts you leave them apart and then you get a view on the channels on the messages.Anatoly Yakovenko (05:31):So you write your software, your Lambda hook as if it's a re-entrant, right? So you're kind of recording your progress potentially on Solana as you're processing it.Jonathan Schemoul (05:43):For the Lambda it's a bit different. Here I was explaining how the network works for the messaging on the global state. For the state of pure application, you could either get your state from a blockchain here at Solana. For example, all the indexing effort that we are doing is using Solana as a source of synchronization for these Lambda. But then you can have multiple kind of volumes because since it's Linux Micro VM machine, everything is a volume.Jonathan Schemoul (06:18):So we have local storage volume that is local to the running host. And then the Lambda kind of issue messages on a decentralized database of data and project or under storage, and then raising to the local file system and then issue messaging, et cetera. And we are also working on another kind of phase system that is distributed, where any of them that can write in it on the overall receive the changes, which is kind of tricky.Anatoly Yakovenko (06:48):Is the database, the Aleph database, distributed database? Is that a Byzantine fault-tolerant database? Is it designed with that in mind?Jonathan Schemoul (06:58):Yeah. The idea is that when you send a message on the network, it gets stored by all the over nodes that are interested in your channel. And then there are synchronization node that go and write hashes of the data and signatures inside messages that they push on blockchains. So that when overcome, they can synchronize it and replicate all the data. So that even if one part of the network gets totally disconnected, you can have one part that gets reconnected to the other therefore the peer to peer network for blockchain, for APFS. We have multiple kind of different connectivity solutions so that they can reconnect on resync.Anatoly Yakovenko (07:42):So the Aleph database, if it's Byzantine fault tolerant, I mean, doesn't that make it a blockchain? Is there a token? Is crypto economically like fault tolerant?Jonathan Schemoul (07:56):Yeah. So we have a token, but the token is living on multiple blockchain, Ethereum, Solana, and a few others, but those are the most used today. We have a token, you need a token for your data to stay there. If you don't have any more your data gets garbage collected. But we don't have a blockchain because we go and write on over layer ones. We are technically a layer two database which is computing pre storage.Anatoly Yakovenko (08:23):But the data storage, like the Aleph distributed database, what is that backed by? Or can I pick my own blockchain to use it as a common interface or something like that?Jonathan Schemoul (08:34):Well, currently it writes on Ethereum, we're working on making it write on Solana. For this we need our indexer to be super powerful. So we'll get it writing on Solana very soon. Basically you can write on multiple blockchains and use it as a source of proof.Anatoly Yakovenko (08:53):Got it. That's pretty interesting. So it really doesn't have its own blockchain and you're just using the fault tolerance of the chains you're connected to.Jonathan Schemoul (09:04):Exactly.Anatoly Yakovenko (09:06):Awesome. Yeah, that's really cool. So the other challenge I think is like how do you deal with domains and the web? Where do you run these executed nodes? How do you connect all those pieces?Jonathan Schemoul (09:20):It's a really good question. To connect all the pieces together, we didn't develop some really fancy stuff like proof of space and time and things like that to verify that the data is really stored. We are using something much more low-tech, which is just a quality control. We have core channel nodes, which are the controllers of the network, which needs to keep some Aleph have stakers on such economics. They are verifying that other core channel nodes are behaving well. And that also the resource nodes are behaving well. Then the resource nodes are really doing the work of storing data, providing computing, et cetera. And they're continuously controlled by the core channel nodes.Anatoly Yakovenko (10:09):That's great. So they're basically like a tokenized health check, right?Jonathan Schemoul (10:14):Yeah.Anatoly Yakovenko (10:14):I can spin this up and they can continuously monitor whether this computation is making progress, right?Jonathan Schemoul (10:21):Exactly.Anatoly Yakovenko (10:21):Is that verification, is that programmable? Can me as an app developer, can I kind of code up my own apps, specific health checks or an interface or something like that?Jonathan Schemoul (10:35):It's a really good question. That's what we are working on exactly right now.Anatoly Yakovenko (10:40):I'm leaking all the features. My imagination is going.Jonathan Schemoul (10:44):No, no worry. Well, it's really interesting because to understand if an application behaves well on one host, you need to understand what the application is doing. So yes, we will give some kind of health check, which is kind of a unit test of how the app should work. So you will be able to provide unit tests for your app basically.Anatoly Yakovenko (11:11):That's really Cool. What about domains? Like actual DNS?Jonathan Schemoul (11:17):Yeah.Anatoly Yakovenko (11:20):I'm asking all the hard questions.Jonathan Schemoul (11:22):Yeah. These questions will be answered if I explain how we handle access to this virtual machine. Because for DNS, for just IPFS, there is already quite a few solution, that's not an issue. But then if you want to make a domain point to one micro VM, you want your micro VM to be able to serve your data. How we do first the load balancing because that's the important question. For load balancing we have two ways, one, which is a regular cloud load balancing, which could be blocked by government, could be censored, because that's what can happen when you have centralized point of control.Jonathan Schemoul (12:07):We will run it ourselves and a few of our partners might run some of the cloud load balancers that basically you can just point your domain to the cloud load balancer. And then the cloud load balancer will create certificates and stuff like that. It will work. We will run one instance. Ubisoft will likely run another. And like many of our partners. Well, for Ubisoft it's not sure, just some talks about it. But perhaps over partners could run cloud load balancers that we'd go on point on specific micro VM host to see where your app is running and point it to them, that might work.Jonathan Schemoul (12:48):Now What happens if a government says, "This app shouldn't work, this domain shouldn't work." Then you have two solutions, you either put the front-end inside IPFS, use some IPFS gateways, et cetera. And then the back-end is on the VM network. But then what happens if a government blocks the specific DNS inside the micro VM global.aleph.sh .aleph.cloud Whatever. Then we have a decentralized load balancing that comes into play.Jonathan Schemoul (13:24):The idea of the decentralized load balancing is that your browser will connect to the IPFS network using leap peer to peer, just leap peer to peer, find Pi Aleph nodes running, contact them directly then ask Pi Aleph node, "What micro VM host are running this software?" And then you can contact them directly. We are working on the JavaScript library that will do all this work on the client side so that you can have your front-end in IPFS that will then go and find all the back-end hosts that could answer your request.Anatoly Yakovenko (13:58):That's super cool. You guys are working on some really hard problems. I think it should be fairly easy to kind of have basically a resolver that points to ENS in the system, right. That's fairly straightforward. And basically you should be able to use any kind of like name, system, command any blockchain.Jonathan Schemoul (14:25):Yeah, clearly.Anatoly Yakovenko (14:26):Do you think that this is something that browsers are starting to recognize as standardizable? Is there a future where you think this technology could start percolating to the UI level where the end user can pick like blockchain based DNS resolver that kind of like connects all the pieces, right? From the human to this decentralized one.Jonathan Schemoul (14:51):I think that something that could come, I think that those that could really help in this is Mozilla foundation, I think that they would be the one to talk with. We aren't in talk with them because we don't really take that step right now. We have a lot on our plate. But in the future I'm pretty sure it's the way to go. We will connect to any effort in that area and we will recognize it. I know that for IPFS for example, IPFS, IPNS, there are some efforts on some browser extension that you can install to have it, et cetera.Anatoly Yakovenko (15:29):How does like certificate chaining play with us? What happens if I need to have a cert on my service and things like that.Jonathan Schemoul (15:38):A certificate on your service? Yeah.Anatoly Yakovenko (15:41):Like their sign or whatever.Jonathan Schemoul (15:43):Well, we use the one that everyone uses, which is-Anatoly Yakovenko (15:48):Let's Encrypt. The EFF one.Jonathan Schemoul (15:49):Yeah, exactly. We're using this one, we used the discovery with the content, so that we switch to a specific content when Let's Encrypt connects, then we serve this content, then we get a valid certificate, we can serve the good content.Anatoly Yakovenko (16:07):Can you unpack that a little bit?Jonathan Schemoul (16:10):Yeah. Well, Let's Encrypt has multiple ways to certify that you have a certain domain, for sub domains of .aleph.sh and .aleph.cloud, It's easy, we are using wildcard certificates. For custom domains that you could make point to your content directly, what we do is that you put a key inside your DNS to say, this is the virtual machine that should be mapped to that domain. Then you do a CNAME to our cloud load balancer and then the VM host when they get a request for this one, they go and check the DNS to see what VM they should serve on the generator certificate using Let's Encrypt for that domain and they start serving it.Anatoly Yakovenko (16:59):Oh man, this would be really cool. But if we could have like an ENS where in my ENS registry I set my Let's Encrypt domain, and then I run a local DNS server on my home machine where I run my browser and point that as a resolver, you could kind of tie these knots together and get-Jonathan Schemoul (17:23):Yeah, it could work.Anatoly Yakovenko (17:24):That's really cool. What happens if these instances die, where do you guys get more hardware? How does that process work?Jonathan Schemoul (17:36):Well, an instance can just stop, then the load balancing system will find another instance to run your code. Then what happens when an instance get a request for a code that doesn't have for the micro VM network. I mean, it goes on the network, checks, okay, what is the database entry that is in front? It takes the database entries. Has there been any upgrades to it? Okay. I get the upgrades. I subscribe using web socket to the upgrades of this database entry basically because it's a document about database entry.Jonathan Schemoul (18:14):And then it looks, okay, so this is the root FS that I should load. Do I have it? I have it, could I use it? If not, I download it from the network. I applied that root FS, where is the code? Okay. What volume does it needs and it builds and retransits and gets you the answer. For a cold start with no root FS or whatever, it can take a few seconds. But in general you use the same root FS as others. So you can get the code start. If you don't have the code, it's less than a second. If you already have the code of the application is like 150 millisecond for a cold start.Anatoly Yakovenko (18:53):Got It. And is the coordination to decide where to start this particular instance? Does that occur over the underlying chain, like Solana or Ethereum or whatever?Jonathan Schemoul (19:08):Again, that's something that we're working on. At start it's on the cloud load balancer. So the cloud load balancer are semi centralized for that. The idea is that each micro VM running node that starts running one will register a message, which is a database entry with a reference to say, "I am running this one." And then the cloud load balancer looks at the uptimes of the available micro VMs and say, "Okay, this micro VM has it ready." I'm forwarding it to it.Jonathan Schemoul (19:40):And then if there is none, then it could just route it to like a random one that has a good uptime. And then this one, the next time kind of like be choosing automatically because it is already serving it. If there is a lot of requests, it will provision multiple ones.Anatoly Yakovenko (19:59):Interesting. Got it. And you anticipate that you'll basically be able to move if the underlying chain is cheap and fast enough you should be able to move the coordination and kind of like start this instance, pull this volume. This would be really cool with like Arweave backed storage volumes. Because you could almost then see the lifetime, the life cycle of the application as its business logic is evolving, right? That state is very useful to developers who are being able to go back to a checkpoint effectively at any given time too.Jonathan Schemoul (20:38):Well, right now we are using our own storage engine, which is APFS compatible. But in the future we will allow to choose other storage engine and we will also develop gateways with like Arweave, Filecoin and other.Anatoly Yakovenko (20:53):Super cool. I used to work at Mesosphere so I don't know if you've heard of them, like D2iQ, this was kind of Kubernetes competitor, trying to build this decentralized operating system using Mesos as the jobs kind of Q-engine. There's a lot of similar challenges there, and this is really cool that you guys are building this in a decentralized web application that's kind of hosted in the real cloud, the mythical cloud.Jonathan Schemoul (21:28):Yeah. Well, there's a saying, there is no cloud, it's just other people computers. Here it's really other people computer. So it's pretty good because then you don't trust those computers because you know it's other people computers.Anatoly Yakovenko (21:44):How do you guys ensure the integrity of the computation itself? How do I know that the virtual machine, the execution environment that's running isn't malicious.Jonathan Schemoul (21:54):It's a really good question. There is multiple questions there. How can I ensure that this computation isn't returning a bad result because it knows who is on the other end. The load balancing system ensures that you don't really see who is in the other end, so you don't know who is making the request. So you don't know if it's a quality control call or if it's a real call. It goes back to your question of the testing of the application. And there is another one there which is the question of the secrets, because you might need secrets. If you want to do push notification based on a smart contract event on Solana, let's say, because that's something that we are working on right now, thinking about it.Anatoly Yakovenko (22:48):That's super cool.Jonathan Schemoul (22:48):So you would need secrets. You will need to story a secret to being able to go back to this device and send these device and notification. So you either store secrets in the local storage of the instance, but then if the instance dies, you can get it back or you try to get shared secrets between multiple hosts. We are working on it. We don't have a total answer on that. What we are working on is using free shirt cryptography, so that multiple host defined by the developer come under these secrets. And then you go back to a question of trust, which is problematic.Anatoly Yakovenko (23:30):By the threshold cryptography, is this like an MPC to compute, or are you guys thinking like BLS or like Schnorr aggregation?Jonathan Schemoul (23:42):More like you encrypt something that can be decrypted by multiple private keys.Anatoly Yakovenko (23:47):Got it.Jonathan Schemoul (23:48):And then if they want to send a message, it needs to be signed by at least x of y.Anatoly Yakovenko (23:54):Right. Got it.Jonathan Schemoul (23:57):Because this micro VM I mentioned can also send messages on the network. These messages on the network will be database entries that in the end might end up also on-chain using all records or whatever. Because these micro VM can read from on chain data and the idea is that we are working so that they can also write on chain as well. So then you might need some kind of trust somewhere. So one developer could say, I trust this host this host this host, but they need at least to do that calculation three times, let's say. But it's a bit problematic and we are still working on it. It's not finished yet, so yeah.Anatoly Yakovenko (24:40):That's what I mean, that's a really hard problem.Jonathan Schemoul (24:41):Yeah.Anatoly Yakovenko (24:43):Really cool. Yeah, the secrets thing is really challenging. I guess, what's your vision for this? You guys are tackling on some really hard problems, you get all of them done in the next year.Jonathan Schemoul (25:01):I hope so.Anatoly Yakovenko (25:06):What happens then? What is the vision for Aleph?Jonathan Schemoul (25:08):Well, here we are only speaking about a few crypto issues. We aim at bigger than just the crypto ecosystem. What we really want to do is decentralize the web, so getting bigger, way, way bigger, that's the goal. We are working with a few bigger partners who are part of the Ubisoft entrepreneurial labs, for example. We want to have a lot of hosting partners in the game that start providing resources so that I want it to be as easy as spinning up AWS server or whatever, you would just spin up VMs under the .im network. I want it to be as easy as using Firebase, using Amazon Lambda, et cetera.Jonathan Schemoul (25:51):And we have another big project going on, which is the indexing on Solana, where we are indexing data for a few protocols, currently Raydium, we might have another already soon. Well, I can say the name. We are working a lot on Orca, on port finance right now, and a lot of others actually that I can't really talk yet. But the idea is to have all these data available, have all these data feed coming up so that you can have events based on them, also do off-chain computation and things like that.Jonathan Schemoul (26:29):I really want DeFi to be totally resilient because until it's totally decentralized, you can stop DeFi. When it's totally decentralized, you can't. And if there is only the smart contracts that are decentralized, you can still stop it.Anatoly Yakovenko (26:48):Yeah. That's definitely a fair point. I think the UX issues around building also just like push notifications and all these other things for projects are really hard to overcome if it's a decentralized project, because who's going to host those servers, right, to connect to mobile and everything else. Yeah. You guys have a lot of work set out and it's pretty exciting. What do you think is missing? If you guys had like another, somebody else was building this other piece that you think is missing in the Web 3, what would it be?Jonathan Schemoul (27:26):What is missing today in the Web 3 ease of use for all this. We are trying to tackle this, but we have so much on our end. So this is a big issue, ease of use for developers, ease of use for users. Well, Phantom is already doing a great work on that end on Solana. But yeah, this and also I think that there is some kind of breaks between the ... In DeFi, if you want to move money into the real world, it gets hard really fast because there has been some kind of complications that have been put in place by regulators, by banks, by whatever. If we could just get all these parts simpler, it could be great. Some kind of link between FinTech and crypto that would work everywhere in the world, including Europe, USA, et cetera. It would be great. There are a lot of people working on it, but that's something that is missing as well.Anatoly Yakovenko (28:28):Yeah. Identity and like having those easy ramps is still hard. What about DNS? Just straight up resolving, do you think that's tackleable from a Web 3 perspective.Jonathan Schemoul (28:45):The issue is the way DNS is done. DNS protocol is great, but it implies centralization points, a lot of centralization points, which are problematic. Then you will need another standard on DNS. But if you have another standard on DNS, then you have the issue that the network right now is done, is not done for it and the browser don't understand it, et cetera, and operating system don't understand it. We would need gateways for that. I think it's doable. It's definitely doable, but it's a lot of work. And you would need multiple root servers, even virtual root servers, like what you said, local DNS server that would resolve your request, it could work.Jonathan Schemoul (29:38):If Let's Encrypt could understand it in the same way, it would work. Or we could even have something different than the root certificate that we have today, because with blockchain, we already have private keys. We already have signature. So if you sign your content with your private key, then you can verify it on the other end. And you don't really need all these chains of certificates that are here today. So that could also be another solution, but it would need another way, because right now we have roots certificate, children's certificate, et cetera. And it all goes back to central authority. The whole DNS on certificate system today goes with authority. With blockchain we are trained to remove authorities.Anatoly Yakovenko (30:33):Yeah. Do you guys see this as becoming developer facing, or maybe someday eventually kind of like client facing and want these decentralized applications running for me, kind of my own instances. Or is this always going to be here I am, team Orca, go to this domain as a user.Jonathan Schemoul (30:56):It's a good question as well. It's always the issue between hosted components, locally run components and kind of pragmatic on that. At start I would really like to, everything runs inside my browser, everything works. That's great. In reality, you have mobile phones, you have tablets, you have computers, you have a lot range of devices that can be running all the time. So real peer to peer application can't really work that well, unless you go and say, "Okay. While you are waiting for me, please send it to my friend, that will forward the data for me, et cetera.Jonathan Schemoul (31:40):Blockchains are really helping there is that we have a centralized authority, which is the blockchain that you can trust and that can hold data for you and can even encrypt it for you or store it on aleph.im, whatever, and only you can decrypt it. I think that the mix between the two would be good, like self hosted data and remotely hosted data on the decentralized cloud, a good mix of the two could be good. And the efforts by the leap peer to peer team, with the javascript leap peer to peer. And there are a few of us like that helps, because once you have access to a peer-to-peer network directly from your browser, you can cut middlemen. You can cut central authorities, et cetera, if you're the blockchain that serves as a central authority.Anatoly Yakovenko (32:28):What kind of loads have you guys seen or been able to test this out, in terms of like users request per second, kind of WebSocket connections per second.Jonathan Schemoul (32:39):It depends because when it's per server, that's not that much of an issue because the micro VM supervisor just forwards the request to the underlying software. If you don't choose local persistent volume, the supervisor can run as many instances of your program as needed, then you can spawn multiple one even inside the same supervised cluster. And then the network, if it sees that this one has issues adding the request load you can load new ones.Jonathan Schemoul (33:18):I don't think that there is really a limit on the request per second for that. So it's not really the issue that we have. And then on the database part, same, if you access one API server and you give it 500,000 requests per second, it would go down, because it's a server. If you target multiple API server, you are good. So that's also where the decentralized load balancing helps because if you use a cloud load balancer obviously even this cloud can go down. But if you contact a peer to peer network to know what host can answer, then you can contact multiple host. And all our core channel nodes, we are currently 54 of them are also API servers that users can connect to to get the data, which will be certified by our core channel node.Anatoly Yakovenko (34:10):Cool. As a whole, how many, I guess, do you have an idea of how many users per second or humans per second have you guys served in some peak times?Jonathan Schemoul (34:21):We don't, because we don't store metrics currently, we should. We don't have it because we didn't want to have any kind of log or whatever on the users, but we should add it, that's actually a good point, we will.Anatoly Yakovenko (34:37):Yeah. I mean, I think you got to be really aware of privacy and how that impacts some applications. But really interesting to see how this works. Caching is another one of those things, basically having a distributed cache around the world for often queried data. And this is an issue that I think doesn't have a good solution in Web 3 right now. You do all this work, set up a purely thin client, that's like loads from code, only talks to the chain and then you got to go fetch assets. And if you're using centralized ... Yeah, they can basically inject whatever they want.Jonathan Schemoul (35:25):Yeah, that's the main issue. And the good part is that if you also randomize where the request of the users go, if there is one bad actor, it will only inject bad data once in a while you don't even know where. Once there is a quality control it will detect it, so that can also be a solution. It's not a silver bullet either, but it can definitely help. So like for Solana what we are doing right now, for Raydium for example, is that we have an indexer that talks to multiple RPC of Solana then get the transaction history, store it inside the level DB, inside the micro VM, and then index the data.Jonathan Schemoul (36:09):Then we can get data on the pool's latest trades and stuff like that. The idea is that if there is too much request on one index, it will start another index or another index or another index, or et cetera, so that when you do a request, it reroutes you randomly to multiple hosts that have the same index.Anatoly Yakovenko (36:28):How fast is that?Jonathan Schemoul (36:31):Not fast enough currently. Well, it's fast enough for Raydium.Anatoly Yakovenko (36:35):Okay.Jonathan Schemoul (36:36):It works really well.Anatoly Yakovenko (36:40):Raydium gets a ton of hits. I mean, some of their IDOs have seen half a million requests per second-Jonathan Schemoul (36:48):Yeah. So for the Raydium data, it handles it well, like all the trades, whatever, it handles it pretty well. We don't get behind blocks in the indexing, so it works well. For Serum it's a bit more problematic because you need to watch, event cue all the time. I really hope they will have some kind of flux in the future. I think that they are working on it. So that would really help us either to get history even when we aren't watching their event cue.Anatoly Yakovenko (37:23):Yeah. So not half a million per second, half a million total, which is quite different, but yeah, they see some really good traffic.Jonathan Schemoul (37:30):Yeah.Anatoly Yakovenko (37:32):Cool. I mean, that's really cool. I think really hard part I think in designing these systems, one, is the problem is difficult, but then once you build the first version of it and you start hitting real traffic, there's a lot of parts that fit together that break under load. So what is your debugging like? How do you guys actually monitor like debug, like PagerDuty, what do you guys use as a team?Jonathan Schemoul (38:01):Right now our team is still small. We are growing a lot. Right now we are like 10 developers. A few months ago we were only three. A year ago I was alone. So we are growing really fast and we are putting all these things into place. Right now everyone monitors and checks what happens and it helps. There is Hugo who is on the micro VM side, Ali was mostly on the indexer side, myself we can get everything. But we are putting really real stuff in place right now to have it, because we are a growing startup so it takes time to get everything in place.Anatoly Yakovenko (38:43):Yeah, for sure. Do you envision a PagerDuty team for this?Jonathan Schemoul (38:48):Yes. I think that we will need one. Once we have more application that are using it, we will need one. So yes, if you have advices on that day, I'm really happy to get them.Anatoly Yakovenko (39:00):I mean, it's just part of life. It's not complicated. It's just work. This is I think that like response team I think is a difficult thing to set up in a decentralized community. If you guys are building a decentralized network with providers that are supplying hardware and all this other stuff, those are the folks that we found to be really responsive and have a lot of stake in growing this. How do the economics work for all the people actually supplying the hardware and bandwidth, et cetera?Jonathan Schemoul (39:36):Again, the research and economics aren't live yet. We are working on them. The core channel nodes economics is already there for like a year, now it works well. For the core channel node you need to have 200,000 Aleph to start a node and 500,000 Aleph, staked on a node, so that it can start to run. And then all the node operator get a share of a global envelope daily for all the nodes. All the stakers get a part of the envelope for stakers. The more nodes active, the bigger the envelope for staker is. But then for each node, they will earn a bit less if there are more nodes because it's a global envelope. So it helps stakers grow the number of nodes that are active, so that's for the core channel nodes.Jonathan Schemoul (40:25):For the resource nodes, to get storage or computing on network, there is two ways to get it. One that is already live, which is hold X amount of Aleph and get that amount of storage, hold X amount of Aleph and have the ability to start one VM with X megabyte of RAM, X virtual CPU, et cetera. And then the multiplier, and all that gives you the total count of micro VM I mentioned that can be running on your network based on your balance. The good part with that is that partner project could use a lending protocol to borrow Aleph where depositing their own token to get service. They would get the service for free just paying interest in their token, inside the borrowing protocol.Anatoly Yakovenko (41:14):Got it.Jonathan Schemoul (41:15):So that's a way for protocols to get it, but it's quite expensive because they don't directly pay for it. So for this way of using it, Aleph.im network is paying for them from the incentive pool, which right now it's one fifth of the supply, and we are changing it in the next few months, we'll change a bit of economics. It will be nearly half of the supply that would be dedicated to pay for that. Because since you lock a part of the supply, then you can release a bit inside circulating because of this new use. So that's for the hold X Aleph tokens.Jonathan Schemoul (41:51):And then there is another way that isn't developed yet that we will likely use Solana for, because it's fast enough for micro-payments in that area. It's like pay per action, pay X Aleph per gigabyte per month. You as a provider, you can say, "I am okay to be paid at least that much." And then users will say, "I want my data to be replicated at least four time. And I'm okay to pay at most that much for this." Then you get divided by those who provide service and the payment is done as micro payments. And same for the micro VM you pay per CPU per hour, et cetera.Anatoly Yakovenko (42:32):Got it. That's really cool. Well, this has been awesome to have you on the show. I mean, we got into I think the really deep, deep tells of how Aleph works, so I had a blast because it really reminds me of the spending, working on the stuff for centralized systems. It's really cool to see this kind of built ground up for decentralized ones as well. So appreciate the work you're doing. Thank you, Jonathan.Jonathan Schemoul (43:00):Thank you very much for having that call. It was really great talking with you.Anatoly Yakovenko (43:04):Awesome. And good luck to you guys. I mean, startups are blood, sweat and tears, so just keep working on the vision. You'll get there.Jonathan Schemoul (43:11):Thank you very much.Anatoly Yakovenko (43:13):Cool. Take care.

Anatoly is the creator of Solana. He led development of operating systems at Qualcomm, distributed systems at Mesosphere, and compression at Dropbox. He holds 2 patents for high performance Operating Systems protocols, was a core kernel developer for BREW which powered every CDMA flip phone (100m+ devices), and led development of tech that made Project Tango (VR/AR) possible on Qualcomm phones.—————————————————————— Registration for SALT New York is now open! Join us September 13-15, 2021 and sign up at https://register.salt.org/event/411f76d9-c215-4719-9bc4-8dfac6cfacdd/summaryWatch this video on YouTube: https://www.youtube.com/c/SALTTube/videosFor podcast transcripts and show notes, visit https://www.salt.org/Moderated by Anthony Scaramucci. Developed, created and produced by SALT Venture Group, LLC.

Best wel vrij moderne muziek dit uur, van Ramon Humet en Aart Strootman, een nieuwe single van Poulson SQ. en marimba-bewerkingen door marimbist Arjan Jongsma. Eigentijds is heus niet alleen maar huiswerk (alsof we dat niet allang wisten) (maar toch). 23.04 CD Light Llum (Ondine ODE 1389-2) Ramon Humet: Llum - 6. Engrumes de Llum (Luminous Crumbs) Lets Radio Koor olv Sigvards Klava 11'29” 23.17 CD Obscure Atlas (TRPTK TTK 0068) Aart Strootman: Obscure Atlas - 3. Mesosphere - 4. Stratosphere - 5. Troposphere - 6. Crust - 7. Core Helena Basilova [piano]; Konstantyn Napolov [slagwerk, stem]; Maya Fridman [cello] 12'31” inclusief infade in track 3 23.30 CD Zes vrouwelijke componisten (BFO Centre Netherlands Music BFO A 18) Iet Stants: Strijkkwartet nr 2 (1922) Dufy Kwartet 9'01” 23.40 eigen opname musici Anthony Fiumara; Mathijs Leeuwis: Kosmic Headroom Poulson Sq. 4'13” 23.50 CD New Perspectives for marimba (Aliud Records ACD OB 115-2) Maurice Ravel, ar.. Arjan Jongsma: Pianoconcert voor de linkerhand Arjan Jongsma [marimba], Colori Ensemble 12'18”

Abstract of the talk… As an engineer, should I consider getting a certification? What makes a certification valuable to me or my employer? How do I pick which one to get? Will these really help me build stateful applications on Kubernetes? In this talk, we will discuss the relative value of certifying on different technologies, with a specific focus on CNCF certifications for administration of k8s and developing Kubernetes-native applications. In this session we will discuss: - The pros and cons of getting certified - Why your current and future employers might care about your certifications - What are other things you can do to make yourself a more attractive candidate in this cloud-native landscape And of course, since Keith is a long-time database geek, we'll talk about how these might help you (or not) build stateful applications on Kubernetes. Bio… Keith McClellan is the Director of Partner Solutions Engineering at Cockroach Labs. He is responsible for building CockroachDB-based solutions with our largest technology partners, including Kubernetes and the broader open-source ecosystem. He spearheaded Cockroach Labs' Kubernetes operator project, acting as the technical lead on the project and being a primary contributor to making that the best way to run CockroachDB on Kubernetes. Prior to Cockroach Labs, Keith has held technical leadership positions in cloud-native and big data companies including DataStax, Mesosphere (now D2IQ), and Platfora.

Guests:Anatoly Yakovenko (twitter.com/aeyakovenko)Dankrad Feist (twitter.com/dankrad)Host:Richard Yan (twitter.com/gentso09)Today's motion is “Security is about maximizing the minimum set of colluding miners.”This is a mouthful. The minimum set of colluding miners is the smallest cartel of dishonest block producers you need to attack a network. Maximizing that set is about increasing the size of such a successful cartel, essentially making it harder for block producers to collude. Note this debate statement leaves out full nodes. And that's the essence of this debate: Are they important in securing the network?So, to get more context on this, take a look at a recent blogpost by Vitalik Buterin on limits to blockchain scalability. This article instigated the sparring between our guests on Twitter, and led to today's debate. In his article, Vitalik argued that the ability for consensus nodes to collude and do bad things should be held in check by full nodes. And therefore, there's a strong need for regular users to be able to run full nodes. Today's debate is essentially an examination of the validity of that statement. Is security about maximizing the minimum set of colluding miners (aka increasing the smallest number of consensus nodes required to censor or collude), or should we also worry about making sure to onboard more full nodes?The two debaters today are from Solana and ETH 2, respectively. When it comes to ensuring security of the network, they disagree on how important it is to make it easy to run full nodes.The debate took a major detour. The two debaters were very passionate about their respective projects and went down the rabbit hole several times pointing out potential weaknesses they see in each other's designs. I decided to keep all of that in, because one way or another, those discussions found their way back to the topic at hand.If you're into crypto and like to hear two sides of the story, be sure to also check out our previous episodes. We've featured some of the best known thinkers in the crypto space.If you would like to debate or want to nominate someone, please DM me at @blockdebate on Twitter.Please note that nothing in our podcast should be construed as financial advice.Source of select items discussed in the debate (and supplemental material):Multicoin article on Solana's decentralization: https://multicoin.capital/2021/05/25/technical-scalability-creates-social-scalability/Solana's dashboard for validators and full nodes: https://solanabeach.io/Dankrad Feist article on full nodes: https://dankradfeist.de/ethereum/2021/05/20/what-everyone-gets-wrong-about-51percent-attacks.htmlVitalik Buterin's article on the limits of blockchain scaling: https://vitalik.ca/general/2021/05/23/scaling.htmlGuest bios:Anatoly is founder and CEO of Solana, a layer-1 public blockchain built for scalability without sacrificing decentralization or security, and in particular, without sharding. He was previously a software engineer at Dropbox, Mesosphere and Qualcomm.Dankrad Feist is a researcher at the Ethereum Foundation, working on ETH 2.0. He was previously an engineer for Palantir, and co-founded a healthcare startup named Cara Care.

On this episode of the Humans of DevOps, Jason Baum is joined by Ravi Lachhman (@ravilach), Evangelist at Harness and frequent SKILup Day speaker.

Guest Mr Paul de Paula of YoungCTO Rafi Quisumbing An accomplished Web Developer with more than 12 years experience in the IT industry, from Software Development, Digital News and Media, Airline Services to US Government Platforms. https://www.linkedin.com/in/pauldepaula/ An influential opensource advocate to students, developers, stakeholders from various schools, universities and private organizations locally and abroad. Hes been doing his advocacy for the last 10 years. His topics are ranging from JS Frameworks, Python, PHP, Mysql Database to CMS using Drupal as a major platform, Mobile Development, Data Visualizations, DevOps, Drupal and WordPress Performance and Scalability, Mapping, Third Party API integration and E-commerce. Specialties: • Software Engineering • OS: Windows 95/98/2000/XP/Vista/Win8, Linux Rhel/Centos/Fedora/Ubuntu/LinuxMint/OpenSuse, iOS 10.x • Programming Lingo: PHP, Python, Javascript, BASH/Shell, • CMS: Drupal, Wordpress • Drupal Tools : Drush • Frameworks: Symfony • Web Servers: IIS7,IIS8, NGINx, Apache, Tomcat • Proxy Stuff: Varnish, Pound, HAproxy, Squid • Databases : MS SQL, PosgreSQL, MySQL, MongoDB, Azure Table Store, Redis • Web Service : RESTful JSON, XML-RPC • Cloud Platform: Rackspace, Linode, Amazon AWS, Windows Azure, Open Stack, Google Cloud Platform • Drupal Specific Cloud Platform: Acquia Dev Cloud, Pantheon, Platform.sh, Barracuda • DevOps Tools: Vagrant Chef, Puppet, Docker, Kubernetes, MesoSphere, Terra Form

In this episode I talk with Sirish Raghuram, , CEO and Co-Founder at Platform9. Platform9 provides SaaS based Managed Kubernetes, Openstack and Serverless for public, private and edge platforms. They deliver cloud-native technologies with SaaS simplicity that are easy to install, operate and scale, while supporting broad cloud capabilities that run on any infrastructure. Sirish and I talk about his early days working as one of the early VMware Engineers and how the paradigm of what cloud was lit the fire to join up with his co-founders and start Platform9. We discuss VMware Cloud Director, the early days of OpenStack, Docker and Kubernetes and how the latter won the container manager race, has matured, but is not quiet there yet in terms of mass adoption. Platform9 was founded in 2013 and is headquartered in Mountain View, CA, USA. Technology and Technology Partners Mentioned Kubernetes, OpenStack, CloudStack, VMware, VMware Cloud Director, Docker, Containers, KVM, Mesosphere, Docker Swarm, Linux Web: https://platform9.com/ Platform9 Free Tier: https://platform9.com/signup-flow/?sandbox Interested in being on #GTwGT? https://launch.gtwgt.com Music: https://www.bensound.com

Abstract of the talk… Open source observability should not be hard. What companies package as their enterprise offering should be available to anyone who wants to monitor their systems. Opstrace is a complete monitoring platform designed for the end user instead of the expert. It's goal is to be as easy to use and operate as a hosted SaaS provider but within ones own cloud account. This is not only up to 10x more cost-efficient but also allows full control over ones data. Bio… Sebastien Pahl is the co-founder and CEO of Opstrace, an open source alternative to services like Datadog, SignalFx, and others... Previously he has worked at Cloudflare, Mesosphere and Red Hat in San Francisco. Building teams and projects. Co-founded Docker, a Y-Combinator startup. Passionate about large scale platforms, developer tools, automation, open source, distributed systems, cooking and photography.

Show notes: https://phys.org/news/2021-02-explore-levitate-discs-mesosphere.html --- Support this podcast: https://anchor.fm/newszombie/support

In the Presales Edition of The 33 CXOs we explore the crucial role of the presales organisation in what is regarded as the greatest success story in software sales.   When John McMahon took the reins at BladeLogic, he had a clear vision to create a sales and presales organisation that was in complete unison. What transpired became a sales rhythm which remains the gold standard for best practice within the most successful technology companies in the world.   The effects of a value-driven, technical sales function transcended the boundaries of presales. The playbook has helped trailblaze best practice within Customer Success, Value Engineering, Professional Services and even Product Management.   We uncover the stories and playbooks of the most talented technical sales leaders in the industry who are driving the technology companies of the future.  Episode 3 features James Hollinger, VP of Pre-Sales Engineering at Domino Data Labs. James was one of the founding members of the BladeLogic software engineering team. He joined the company in 2001 during the early start-up phase and was instrumental in designing and building their product from the ground up. He then transitioned into pre-sales, and at this point, James' career began to scale at an extraordinary pace. Positioned at the forefront of the SaaS world, his increasing expertise and ability to communicate value, led him to senior management roles at the likes of BMC, Sumo Logic and Mesosphere. This exposed him to systems and people that continuously expanded his focus and presented opportunities that have enabled his progression from sales engineer through to leader and mentor.  “People might think of the sales engineers as just geeks who want to be doing technology and that's actually not the case. Sales engineers want to win. We want to close business and we want to make money. We are salespeople first and foremost.”  As a skilled software developer with a natural talent for articulating technology and value, James transitioned smoothly into the notoriously competitive SaaS sales arena, surrounded by intelligent A-Player “Bulldogs.” His background in building automation tools for operations and data centres gave him a unique insight into problems that needed to be solved in the industry, but the leadership and mentoring he received at BladeLogic enabled him to excel in his role. He became an integral cog in the BladeLogic sales machine and used ground-breaking methodology and processes to close deals at an enviable rate.   “I think of the playbook like a golf swing. The more unnatural it feels, the more it's actually going to work. It's not intuitive, you're going to have to fight your instincts and there's nothing harder for a salesperson to do than “qual out a deal”. You have to make unnatural decisions and that comes down to your coach. If you have a swing coach who is showing you when to make changes, it might feel unnatural, but if you do 70 swings, then another 70 tomorrow etc, the next thing you know, it starts feeling more and more natural. It's the same thing from the sales methodology perspective.”  In this vodcast you will discover:  How to scale you career in presales  How MEDDIC enabled James to transition from sales engineer to manager, director and beyond  What raw materials are needed to make a great presales engineer  James' playbook - how presales plugs in to the sales organization as a whole    Programmed to win, James is an exceptional leader with a unique ability to define and execute growth strategy. He has a maniacal focus on developing the right processes, behaviours and methodologies to drive revenue and customer value. His enthusiasm to continue to learn and remain at the forefront of cutting-edge technology is inspirational for anyone aspiring to succeed in this ever-advancing industry. We discuss the role and potential prospects for presales engineers, past, present and future and ask James what area of innovation he thinks is going to have the biggest impact on business in the next 10 years. This motivating discussion is essential listening for those with an interest in a presales career, as well as anyone with a passion for the technology space. 

Guests:Evan Shapiro (@evanashapiro)Anatoly Yakovenko (@aeyakovenko)Host:Richard Yan (@gentso09)Today's motion is “Today's blockchains can't increase TPS without taking a hit on decentralization.”This is a follow-up debate, or you can think of it as a re-match. Previously Emre from O(1) Labs also debated Anatoly from Solana on this very topic on the show. So make sure to check that out if you're interested.Here are some of the topics we covered:* the inherent shortcoming of proof-of-stake in guaranteeing the canonical chain for a new full node* why some chains have been designed to disallow rollback beyond certain point* How Evan thinks faster synching process for new full nodes will allow further decentralization* Why Anatoly thinks trustless synching doesn't solve the Byzantine Generals ProblemIf you're into crypto and like to hear two sides of the story, be sure to also check out our previous episodes. We've featured some of the best known thinkers in the crypto space.If you would like to debate or want to nominate someone, please DM me at @blockdebate on Twitter.Please note that nothing in our podcast should be construed as financial advice.Source of select items discussed in the debate (and supplemental material):Solana: https://solana.com/Coda: https://www.codaprotocol.com/Weak subjectivity explained: https://academy.binance.com/glossary/weak-subjectivityLong range attacks: https://blog.positive.com/rewriting-history-a-brief-introduction-to-long-range-attacks-54e473acdba9Coda article on mental model of Scalability-per-unit-of-Decentralization: https://codaprotocol.com/blog/solving-the-scalability-trilemmaByzantine general's problem: https://medium.com/coinmonks/a-note-from-anthony-if-you-havent-already-please-read-the-article-gaining-clarity-on-key-787989107969Debater bios:Evan is CEO of O(1) labs which operates Mina protocol, previously known as Coda protocol. He used to be an engineer at Mozilla and Personal Robotics Lab at Carnegie Mellon University.Anatoly is founder and CEO of Solana, a layer-1 public blockchain built for scalability without sacrificing decentralization or security, and in particular, without sharding. He was previously a software engineer at Dropbox, Mesosphere and Qualcomm.

MLOps community meetup #43! Last Wednesday, we talked to Nathan Benaich, General Partner at Air Street Capital and Timothy Chen, Managing Partner at Essence VC about The MLOps Landscape. // Abstract: In this session, we explored the MLOps landscape through the eyes of two accomplished investors. Tim And Nathan shared with us their experience in looking at hundreds of ML and MLOps companies each year to highlight major insights they have gained. What do the ML infrastructure and tooling landscape look like at the moment? Where have they been seeing patterns emerge? What do they expect to see happen within the market in the next couple of years? What current tools out there are the most interesting to them? And last but not least how do they go about selecting which companies to invest in. // Bio: Nathan Benaich is the Founder and General Partner of Air Street Capital, a venture capital firm investing in early-stage AI-first technology and life science companies. The team’s investments include Mapillary (Acq. Facebook), Graphcore, Thought Machine, Tractable, and LabGenius. Nathan is Managing Trustee of The RAAIS Foundation, a non-profit with a mission to advance education and open-source research in common good AI. This includes running the annual RAAIS summit and funding fellowships at OpenMined. Nathan is also co-author of the annual State of AI Report. He holds a PhD in cancer biology from the University of Cambridge and a BA from Williams College. Timothy Chen is the Managing Partner at Essence VC, with a decade of experience leading engineering in enterprise infra and open source communities/companies. Prior to Essence, Tim was the SVP of Engineering at Cosmos, a popular open-source blockchain SDK. Prior to Cosmos, Tim cofounded Hyperpilot with Stanford Professor Christos Kozyrakis which later exited to Cloudera. Prior to Hyperpilot, Tim was an early employee at Mesosphere and CloudFoundry. Tim is also active in the open-source space as an Apache member. // Final thoughts Please feel free to drop some questions you may have beforehand into our slack channel (https://go.mlops.community/slack) Watch some old meetups on our youtube channel: https://www.youtube.com/channel/UCG6qpjVnBTTT8wLGBygANOQ ----------- Connect With Us ✌️------------- Join our Slack community: https://go.mlops.community/slack Follow us on Twitter: @mlopscommunity Sign up for the next meetup: https://go.mlops.community/register Connect with Demetrios on LinkedIn: https://www.linkedin.com/in/dpbrinkm/ Connect with Nathan on LinkedIn: https://www.linkedin.com/in/nathanbenaich/ Connect with Tim on LinkedIn: https://www.linkedin.com/in/timchen

 Episode Summary In this episode of Masters of MEDDICC, Andy talks to Chief Revenue Officer at Imply, Travis Patterson, about hiring, sales, and recruiting. Travis has over 20 years of experience working in enterprise sales, having taken up roles at Opsware, Aviso, SignalFx, IronKey, PTC, BladeLogic, and Mesosphere. Today, we explore what makes a good seller, how Travis goes about finding these sellers, the importance of good leadership, and the emphasis on constantly learning. Key Takeaways “Through the course of your career, you're trying to over index for learning. I want to learn. I want to be in a situation where you're not the smartest person in the room.” “It only feels like it was a fun experience after it's over and you get to read the book, but when you're in it, it's a lot of work, stress, and focus.” “Bad people don't tend to stick together; only good people.” “Part of the pride of you getting to a certain point in your career is that you've worked with a lot of good people, and you've been able to help people further their career as well.” “We can go recruit all we want, but the really great sales people that we want to hire have to want to work with us.” “Intelligence allows you to be creative. It's a really important thing that you can't fix as a leader. If the person you hire doesn't have it, there's not much that you're going to be able to impart.” “If you're smart and you work hard, but you don't take feedback, it's going to be hard to grow in the way that we need you to grow.” “You want a competitive team. Everyone in your team wants to be number one, but they want whoever is in second place to be just $1 behind them.” Learn more about MEDDICC at https://www.meddicc.com .Subscribe, Comment, And Share: Website: https://www.meddicc.com Facebook: MEDDICC Facebook Twitter: MEDDICC Twitter Instagram: MEDDICC Instagram YouTube: MEDDICC YouTube Channel Podcast: MEDDICC Podcast Page Masters of MEDDICC is a show where the world's best sales professionals are interviewed about all things enterprise sales and in particular relating to the MEDDIC framework, including MEDDICC and MEDDPICC.

This is a special episode of The Solana Podcast - we took a recent panel for the Solana Wormhole Hackathon and converted into audio format for you! Enjoy this deep dive into all things DeFi with industry leaders. Sam Bankman-Fried Sam Bankman-Fried is the CEO of crypto derivatives exchange FTX and Alameda Research. He majored in Physics at the Massachusetts Institute of Technology and graduated in 2014. Stani Kulechov Stani is the founder and CEO of Aave and ETHLend. He is a seasoned entrepreneur with extensive experience developing technology in the crypto, blockchain, and fintech space. Michael Egorov Michael is the CEO of Curve and a physicist and scientist from the Moscow Institute of Physics and Technology. Anatoly Yakovenko Anatoly is the creator of Proof of History and co-founder of Solana. He led development of operating systems at Qualcomm, distributed systems at Mesosphere, and compression at Dropbox. Jeremy Musighi Head of Growth at Balaner Tarun Chitra Founder and CEO of Gauntlet Networks, a research company aiming to make crypto networks and their governance interpretable and statistically sound

€170 million for European deep tech startups: Serial entrepreneur Florian Leibert shares the masterplan for the new fund called 468 Capital that he set up with former Rocket Internet executives Alexander Kudlich & Ludwig Ensthaler in this week's conversation with Bits & Pretzels' Editor-in-Chief Britta Weddeling. Florian has 10+ years career in Silicon Valley, as the co-founder of California based cloud container company Mesosphere that secured funding of more than $250 million, and alumnus of Airbnb and Twitter. In this podcast he's providing a rare glimpse into what he and his 2 partners are up to –  how the team secured the million Euros funds to bridge the innovation gap between Europe and the US despite the economic uncertainty caused by the Covid-19 pandemic – and why he thinks the time to act for European tech founders is right now. More to explore: Stay updated on news & insights from us about founders, startups in Bavaria, Austria & Switzerland at www.bitsandpretzels.com. Signup for our media newsletter to get the next episode of this podcast delivered right to your inbox: www.bitsandpretzels.com/media-signup. Hosts: Britta Weddeling (@bweddeling), Editor-in-Chief of Bits & Pretzels (@bitsandpretzels) Featuring: Florian Leibert (@flo), General Partner at 468 Capital (@468Capital), founder of Mesosphere (@mesosphere). Former Tech Lead at Airbnb (@airbnb) and Twitter (@twitter) Follow us: Twitter: @bitsandpretzels Linkedin: https://www.linkedin.com/company/bits-&-pretzels If you like the show, please let us know by leaving a review. You can also send us feedback at podcast@bitsandpretzels.com. Production: professional-podcasts.com (Regina Körner, Migo Fecke), Sophie Dechansreiter

Anatoly is the creator of Solana. He led the development of operating systems at Qualcomm, distributed systems at Mesosphere, and compression at Dropbox. Notwithstanding the man loves to surf and for someone as intelligent as he is, he's remarkably easy to speak with.

Florian Leibert ist einer der erfolgreichsten Gründer im Valley. Nach verschiedenen Stationen als Entwickler bei Startups wie Twitter und Airbnb gründete er zusammen mit Tobias Knaub und Benjamin Hindman 2013 Mesosphere (heute D2iQ). Mehr als 252 Millionen USD haben die 3 an VC Funding in verschiedenen Runden geraised. Seit Anfang des Jahres konzentriert sich Florian vor allem auf seinen neuen VC Fund 468 Capital, wo er als General Partner zusammen mit Alexander Kudlich und Ludwig Ensthaler über 170 Millionen USD in Startups investiert. Im Podcast sprechen wir über seinen Weg ins Valley, seine verschiedenen Stationen bei Firmen wie Airbnb oder Twitter, beleuchten warum mit der Chipherstellung ein wichtiger Grundstein für den Erfolg im Valley gelegt wurde und besprechen, wie er mit seinem neuen Fund eine Brücke zwischen Berlin und dem Valley baut. Flo ist ein wahnsinns Typ und trotz des Erfolgs total auf dem Teppich geblieben - unbedingt anhören und sagt mir am besten über LinkedIn, wie es Euch gefallen hat!

Toutes les ressources de Kubernetes peuvent être considérées comme des objects accessibles au travers d'une API et dont l'état est maintenu par un contrôleur. Lorsque vous créez un déploiement par exemple, c'est au contrôleur de s'assurer que l'état que vous désirez est celui présent dans le cluster. Mais Kubernetes n'a qu'un nombre limité d'objets, comme les pods, les déploiements ou les statefulsets. Cependant, Kubernetes nous permet d'étendre cette API en créant de nouveaux objets au travers de ressources personnalisées dont l'état devra être maintenu par un contrôleur dédié. Ces nouveau objets vont par exemple vous permettre de déployer un cluster Kafka ou Elastic dans Kubernetes.Mais en plus, vous pouvez également implémenter un savoir faire opérationnel dans ces contrôleurs, et leur donner la possibilité d'agir en autonomie en réaction à un évènement, comme la création d'un nouveau cluster Kafka, la perte d'un noeud du cluster, ou une demande de backup. Un contrôleur doté d'une logique opérationnelle est appelé un opérateur. Et il existe différents frameworks pour en faciliter la création.Dans cet épisode, j'ai le plaisir de recevoir Denis Jannot. Denis est sales engineer pour D2iQ, anciennement connu en tant que Mesosphere, et il nous explique les problématiques des différents frameworks, et pourquoi D2iQ a fait le choix de créer KUDO, un framework destiné à faciliter la création d'opérateurs.Notes de l'épisodeLe site de KUDO : https://kudo.dev/L'opérateur KUDO sur Github : https://github.com/kudobuilder/kudoLes opérateurs développés pour KUDO : https://github.com/kudobuilder/operatorsSupport the show (https://www.patreon.com/electromonkeys)

This week in TNS, D2IQ co-founder Tobi Knaup wrote about the growing problem of container sprawl, a by product of more companies running containers in production, and as a result, there is a loss of efficiency on the part of the DevOps teams managing them. https://thenewstack.io/container-sprawl-is-the-new-vm-sprawl/ In this episode, we will speak with Ben Hindman, D2IQ co-founder, and CTO, about this issue of container sprawl, and how it hampers “Day 2 Operations” as D2IQ (formerly Mesosphere) calls it. We also will discuss the company's recent Cloud Native Virtual Summit, its recently released KUDO tool https://thenewstack.io/kudo-automates-kubernetes-operators/ , the 6th Anniversary of Kubernetes, and the latest on Mesosphere and the DCOS. TNS editorial and marketing director Libby Clark hosted this episode, alongside TNS Senior Editor Richard MacManus, and TNS Managing Editor Joab Jackson.

This week in TNS, D2IQ co-founder Tobi Knaup wrote about the growing problem of container sprawl, a by product of more companies running containers in production, and as a result, there is a loss of efficiency on the part of the DevOps teams managing them. https://thenewstack.io/container-sprawl-is-the-new-vm-sprawl/ In this episode, we will speak with Ben Hindman, D2IQ co-founder, and CTO, about this issue of container sprawl, and how it hampers “Day 2 Operations” as D2IQ (formerly Mesosphere) calls it. We also will discuss the company's recent Cloud Native Virtual Summit, its recently released KUDO tool https://thenewstack.io/kudo-automates-kubernetes-operators/ , the 6th Anniversary of Kubernetes, and the latest on Mesosphere and the DCOS. TNS editorial and marketing director Libby Clark hosted this episode, alongside TNS Senior Editor Richard MacManus, and TNS Managing Editor Joab Jackson.

Welcome to another episode of Develomentor. Today's guest is Michael Hausenblas. BiographyMichael started his career in academia as a PhD academic researcher. These days, Michael is a Developer Advocate at AWS. He is part of the container service team, focusing on container security. Michael shares his experience around cloud-native infrastructure and apps through demos, blog posts, books, and public speaking engagements as well as contributes to open-source software. Before AWS, Michael worked at Red Hat, Mesosphere,MapR and in two research institutions in Ireland and Austria.Episode Summary“I found that industry overall is way less stressful than academic research. If it’s weekend or if I’m on PTO or whatever, I’m offline.““I’m a developer advocate. Basically, it's kind of like a guinea pig. We’re the first ones who get to play around with software and give feedback. It’s like, the UX here is great or here the UX sucks. So we are guinea pigs representing for the customer.”“I just love to be on-site with customers discussing things, trying things. The greatest part is being with actual users of the software that you’re producing and going over that in 400 level details.”—Michael HausenblasKey MilestonesWhat led Michael into academia and academic research at the start of his career?After about 4 years doing research focused work, Michael left for a startup and took a role doing pre-sales work. That’s a pretty far cry from doing research. What led to that change and what went into his decision process? What does a sales engineer do?Now Michael is in a dev advocate role, how does that compare with being a sales engineer?What attracted Michael to more public-facing roles like developer advocacy?Who is Ted Dunning? And why was he such a big influence for Michael?Additional ResourcesConnect with Ted Dunning on LinkedIn – https://www.linkedin.com/in/teddunning/Support Us at Develomentor – https://develomentor.com/support-us/You can find more resources in the show notesTo learn more about our podcast go to https://develomentor.com/To listen to previous episodes go to https://develomentor.com/blog/Follow Michael HausenblasLinkedIn: linkedin.com/in/mhausenblas/Twitter: @mhausenblasFollow Develomentor:Twitter: @develomentorFollow Grant IngersollTwitter: @gsingersLinkedIn: linkedin.com/in/grantingersoll

Anima is the Orion Spacecraft Simulations Lab Manager & xEMU Spacesuit Engineer at the NASA Johnson Space Center.  Anima recently moved to Texas after 20 years in California to pursue her dream to become a NASA astronaut. Her journey has been a long one, but always determined, driven, sometimes sacrificing, and never wavering. Her steadfast and unyielding approach has finally come to fruition with a formal astronaut application when NASA opened the applications and invited candidates to apply for a 30 day window in March.     Since she was a young child, Anima wanted to be an astronaut. Growing up in India, a clear path toward achieving her dream was just not available. So she moved, and made her own path towards the stars…  Anima came to the US as a software engineer in 2000. Becoming a U.S. Citizen was a 12 year endeavor. She just finished her 3rd Masters Degree.  Anima explains her MANY NASA adventures and endeavors, including looking for life on other planets (exoplanets), how Kepler worked, and Anima believes there is life in the universe and we are capable of finding it.    “I don’t want to die thinking, ‘what if I tried?’ I want to die with the satisfaction knowing I tried!. If I get selected (to be a NASA astronaut), I would be the happiest person on this Earth. It will be like my life has come full circle. All my life I’ve worked towards this goal, and it would be all worth it!”-Anima from Casual Space Podcast  Advice for young students and want-to-be astronauts: “I don’t know how far I will get, but I am enjoying the journey! Have a career you see yourself doing every day and enjoy it!”  About Anima:  Anima Patil-Sabale is an Aerospace, Software and Human Factors Engineer, currently working at NASA’s Johnson Space Center for Jacobs as Orion Spacecraft Simulations Lab Manager and xEMU Spacesuit Engineer. Prior to this she has worked on NASA’s Kepler Mission and in NASA’s Intelligence Systems Division at NASA’s Ames Research Center. She worked in the software industry for 14 years before coming to work for NASA.  Anima has a Master’s in Aerospace Engineering, Master’s in Space Studies - Human Factors, Master’s in Computer Applications and a BS in Physics.  While Anima aspires to be a NASA Astronaut and is preparing herself for the same, she is also a Scientist-Astronaut Candidate for commercial spaceflight research projects during her off-work hours. After selection and training, Anima has been participating in upper-atmospheric and bioastronautics research as a Scientist-Astronaut Candidate for Project PoSSUM. She has trained in the topics of Mesosphere and Lower Thermosphere Environment, Fundamentals of Remote Sensing, Remote Sensing and Aerospace Cinematography, Spaceflight Simulation and Operations, Hypoxia Awareness and Mitigation, Spacesuit Operations, High-G Analog and Mitigation Methods, Introduction to Aerospace Physiology and Life Support Systems, and Celestial Navigation and Atmospheric Scattering. She has flown several parabolas aboard a Falcon 20 aircraft while participating in the testing of a commercial spacesuit in zero-G. She has also flown a high-altitude mission in a Mooney aircraft to study noctilucent clouds.    She has been in a 6-inch head-down tilt position for a NASA Simulated Microgravity Fluid Loading study.    She has spun in a centrifuge and experienced up to 6-G's as she contributed to a Federal Aviation Administration study.    Anima has been a Commander for NASA’s HERA VII in 2015, an analog mission to an asteroid.  In April 2018 she has been a Commander for a Martian Analog Mission at the Mars Desert Research Station. She has also been a First Tier Support Engineer for the Hi-SEAS Analog and Simulation missions since 2014. She has been participating and contributing towards the research required for long-duration space missions.   She is a certified scuba diver, and a student pilot (105 hours logged).   She has also completed the following trainings: Land and Sea Survival, Spacecraft Emergency Egress, Hypoxia Awareness and Mitigation, Spacesuit Operations, High-G Analog and Mitigation Method in addition to several others.    Anima loves working with the younger generation the most, to provide them the guidance she missed out on growing up. She is an Assistant Scout Master and a STEM-NOVA mentor for the BoyScouts of America. She is a NASA Girls Mentor and a NASA Speakers Bureau member. She’s also been a First Lego Robotics team coach. She has delivered several talks in the US and in India including a TEDx talk while she pursues her motto to Inspire, Guide and Motivate the younger generation.  Her work has been recognized and appreciated by people everywhere. She has received the Silicon Valley Business Journal’s Women of Influence 2017 award and is a “Forty Woman Over Forty To Watch Out For” honoree. Rocket-women.com, Silicon Valley Business Journal, TriValley Journal are just a few of the several publications that have published a feature on Anima’s journey to share her story to inspire and motivate young and old, alike. Here is the rocket-women.com feature: https://rocket-women.com/2016/05/meet-a-rocket-woman-anima-patil-sabale-nasa/   She’s also a choreographer, dancer, singer, poet artist, and a model. But above all she is a Mom to her two handsome boys.    Learn More About Anima!   http://www.facebook.com/animpatilsabale http://www.animapatilsabale.com  Watch Anima’s Ted Talk!!! https://www.youtube.com/watch?v=tZv9TBPrKp0  

Tobi Knaup is the co-founder and CTO of D2iQ, an enterprise-grade cloud platform provider that helps customers build cloud-native applications. In his spare time, he doubles as continuity advisor at Y Combinator. Previously, Tobi worked as a tech lead at Airbnb, signing on as the fourth engineer and helping scale the company’s product to millions of users around the world. He also co-founded Knaup Multimedia, a company that built websites for small- and medium-sized businesses, when he was 15. Join Corey and Tobi as they discuss why Mesosphere rebranded as D2iQ and what that new name means; why the Kubernetes community deserves the credit for the widespread adoption of the container orchestration platform; how D2iQ helps customers build end-to-end data pipelines with tools like Kafka, Cassandra, and Spark; how D2iQ solves one industrial IoT use case with a mini edge cloud; how many people assume Kubernetes is all they need, why that’s a mistake, and what other tools they end up having to use; why Tobi thinks that multi-cloud is the future; what it was like for Tobi to grow up in Germany and hear about Silicon Valley; joining Airbnb as the company’s fourth engineer; and more.

Er ist einer der wenigen Deutschen, die als Gründer im Silicon Valley wirklich erfolgreich sind: Der Mitgründer des Start-ups D2iQ, das bis vor Kurzem noch Mesosphere hieß. Leibert kommt aus Schweinfurt, half dann die technische Basis von Twitter zu retten und baut in den USA nun das viel beachtete Unternehmen auf, das Unternehmen den Weg in die Cloud erleichtern will. Dafür haben er und seine Mitgründer unter anderem eine Art Betriebssystem entwickelt, mit dem sich Tausende Rechenzentren steuern lassen. Leibert will damit eine wesentlich günstigere Alternative zu großen Cloud-Anbietern wie Amazon oder Microsoft bieten. Und die Idee kommt an. Schon kurz nach der Gründung konnte er einige der bekanntesten Risikoinvestoren gewinnen, darunter Kleiner Perkins, ein früher Google-Investor und Facebook-Finanzier Andreessen Horowitz. Aber wie kommt ein junger Unternehmer von Schweinfurt in die USA? Was bedeutet es, im Silicon Valley ein Unternehmen aufzubauen? Wie hat er Kunden wie Apple, Netflix, SAP und verschiedene große Autohersteller als Kunden gewonnen? Das erklärt Florian Leibert diese Woche im Podcast Handelsblatt Disrupt. Florian Leibert bei Twitter: @flo Haben Sie Fragen, Kritik oder Anregungen? Dann treten Sie unserer Handelsblatt Disrupt LinkedIn-Gruppe bei und schreiben Sie uns unter: https://www.linkedin.com/groups/8836249/. Sie können Sebastian Matthes auch bei Twitter (@smatthes) oder per Mail (matthes@handelsblatt.com) kontaktieren. +++ Anzeige +++ Der global tätige Investment Manager Schroders wurde dieses Jahr mit dem Goldenen Bullen als Fondsgesellschaft des Jahres in Deutschland ausgezeichnet und überzeugt mit einer breit aufgestellten Produktpalette und nachhaltigen, innovativen Investment Lösungen. Mehr zur Global Investor Study finden sie hier: Schroders.de/GIS. Informationen zum Gewinner des Goldenen Bullen hier: Schroders.de/Gewinnertypen.

Our topic in today's great episode is how we think jobs in software engineering have changed since the advent of cloud native computing. We begin by giving our listeners an idea of our jobs and speak more to what a job in cloud native would look like as well as how Kubernetes fits into the whole picture. Next up we cover some old challenges and how advances in the field have made those go away while simultaneously opening the gateway to even more abstract problems. We talk about some of the specific new developments and how they have changed certain jobs. For example, QA has not disappeared but rather evolved toward becoming ever more automated, and language evolution has left more space for actual development instead of debugging. Our conversation shifts toward some tips for what to know to get into cloud native and where to find this information. We wrap up our conversation with some thoughts on the future of this exciting space, predicting how it might change but also how it should change. Software engineering is still in a place where it is continuously breaking new ground, so tune in to hear why you should be learning as much as you can about development right now. Follow us: https://twitter.com/thepodlets Website: https://thepodlets.io Feeback: info@thepodlets.io https://github.com/vmware-tanzu/thepodlets/issues Hosts: Carlisia Campos Bryan Liles Nicholas Lane Key Points From This Episode: • The work descriptions of our hosts who merge development, sysadmin, and consulting.• What a cloud native related job looks like.• Conceptualizing cloud native in relation to development, sysadmin, and DevOps.• A cloud native job is anything related to building software for other people’s computers.• Kubernetes is just one way of helping software run easily on a cloud.• Differences between cloud native today and 10 years ago: added ease through more support.• How cloud native developing is the new full stack due to the wide skillset required.• An argument that old challenges are gone but have introduced more abstract ones.• Advances making transitioning from testing to production more problem-free.• How QA has turned into SDE, meaning engineers now write software that tests.• Why jobs have matured after the invention of cloud native.• Whether the changes in jobs have been one of titles or function.• How languages like Rust, Go, and Swift have changed developer jobs by being less buggy.• What good support equates to, beyond names like CRE and company size.• The many things people who want to get into cloud native should know.• Prospective cloud native workers should understand OSs, networking, and more.• Different training programs for learning Kubernetes such as CKA and CKAD.• Resources for learning such as books, YouTube videos, and podcasts.• Predictions and recommendations for the future of cloud native. • Tips for recruiters such as knowing the software they are hiring for. Quotes: “What is the cloud? The cloud is other people’s computers. It's LPC, and what is Kubernetes? Well, basically, it’s a way that we can run our software on other people’s computers, AKA the cloud.” — @bryanl [0:07:35] “What we have now is we know what we can do with distributed computing and now we have a great set of software for multiple vendors who allow us to do what we want to do.” — @bryanl [0:10:03] “There are certain challenges now in cloud native that are gone, so the things that were hard before like spinning up a server or getting the database are gone and that frees us to worry about more complicated or more abstract ideas.” — @apinick [0:12:58] “The biggest problem with what we are doing is that we are trailblazing. So a lot of the things that are happening, like the way that Kubernetes advances every few months is new, new, new, new.” — @bryanl [0:36:11] “Now is the literal best time to get into writing software and specifically for cloud native applications.” — @bryanl [0:42:22] Links Mentioned in Today’s Episode: Azure — https://azure.microsoft.com/en-us/ Google Cloud Platform — https://cloud.google.com/ AWS — https://aws.amazon.com/ Amazon RDS — https://aws.amazon.com/rds/ Mesosphere — https://d2iq.com/ Aurora — https://stackshare.io/stackups/aurora-vs-mesos-vs-mesosphere Marathon — https://mesosphere.github.io/marathon/ Rails Rumble — http://blog.railsrumble.com/ Terraform — https://www.terraform.io/intro/index.html Swift — https://developer.apple.com/swift/ Go — https://golang.org/ Rust — https://www.rust-lang.org/ DigitalOcean — https://www.digitalocean.com/ Docker — https://www.docker.com/ Swarm — https://www.santafe.edu/research/results/working-papers/the-swarm-simulation-system-a-toolkit-for-building HashiCorp — https://www.hashicorp.com/ Programming Kubernetes on Amazon — https://www.amazon.com/Programming-Kubernetes-Developing-Native-Applications/dp/1492047104 The Kubernetes Cookbook on Amazon — https://www.amazon.com/Kubernetes-Cookbook-Building-Native-Applications/dp/1491979682 Kubernetes Patterns on Amazon — https://www.amazon.com/Kubernetes-Patterns-Designing-Cloud-Native-Applications/dp/1492050288 Cloud Native DevOps with Kubernetes on Amazon — https://www.amazon.com/Cloud-Native-DevOps-Kubernetes-Applications/dp/1492040762 Kubernetes in Action on Amazon — https://www.amazon.com/Kubernetes-Action-Marko-Luksa/dp/1617293725 Managing Kubernetes on Amazon — https://www.amazon.com/Managing-Kubernetes-Operating-Clusters-World/dp/149203391X Transcript: EPISODE 14 [INTRODUCTION] [0:00:08.7] ANNOUNCER: Welcome to The Podlets Podcast, a weekly show that explores Cloud Native one buzzword at a time. Each week, experts in the field will discuss and contrast distributed systems concepts, practices, tradeoffs and lessons learned to help you on your cloud native journey. This space moves fast and we shouldn’t reinvent the wheel. If you’re an engineer, operator or technically minded decision maker, this podcast is for you. [EPISODE] [0:00:41.3] NL: Hello and welcome back. This week, we’ll be discussing the thing that’s brought us all together, our jobs. But not just our jobs. I think we’re going to be talking about the difference kind of jobs you can find in cloud native land. This time, I’m your host, Nicolas Lane and with me are Brian Liles. [0:00:57.1] BL: Howdy. [0:00:58.0] NL: And Carlisia Campos. [0:00:59.6] CC: Hi everybody, glad to be here. [0:01:02.6] NL: How’s it going you all? [0:01:03.7] CC: Very good. [0:01:05.4] NL: Cool. To get us started, let’s talk about our jobs and like what it means to have a job and like the cloud native land from our current perspective. Brian, you want to go ahead and kick us off? [0:01:17.8] BL: Wow, cloud native jobs. What is my job? My job is – I look at productivity of developers and people who are using Kubernetes. My job is to understand cloud native apps but also understand that the systems that they are running on are complex and whether they’d be Windows or Linux or Mac based, being able to understand those too. Really, my job is the combination of a senior developer, composed with a senior level admin. Whether it be Windows or Linux. Maybe I am the actual epitome of DevOps. [0:01:58.5] NL: Yeah you seem to be kind of fusion of the two. Carlisia? [0:02:03.3] CC: My job is – so I’m mainly a developer but to do the job that I need to do, I need to be a bit of a DevOps person as well because as I’ve talked many times here on the show, I work on an open source too called Valero that does backup and recovery for Kubernetes clusters. I need to be able to boot up our cluster at least with three main providers. Azure, Google Cloud Platform, and AWS. I need to know how to do that, how to tweak things, how to troubleshoot things and I don’t think when we think of just a straight up developer, that usually is not part of the daily activity. In that sense, I think, I’m not sure how we would define the cloud native job but I think my job, if there is such a thing, my job definitely is a cloud native job because I have to interact with these cloud native technologies, even beyond what I – the actual app that I’m developing which runs inside a Kubernetes cluster so it all ties in. You Nick? [0:03:16.0] NL: My job is I’m a cloud native architect or a Kubernetes architect, I’m not sure what we’re calling ourselves these days honestly. What that means is we work with customers to help them along their cloud native journey. Either that means helping them set up like a Kubernetes cluster and then getting them like running with certain tools that are going to make there life easier or helping them develop tools in their cloud environments to help make the running of their jobs easier. We kind of run the gamut of developers and sys. admins a bit and consultants. We kind of touch a little bit of everything. Let’s take a step back now and talk about what we think a cloud native job looks like? Because for me, that’s kind of hard to describe. A cloud native job seems to be any job that has to do with some cloud native technology but that’s kind of broad, right? You could have things from sysadmins, people who are running their cloud infrastructure for the company who are like managing things like, you know, rights access, accounting, that sort of thing, to people who are doing development like yourselves, like Brian and Carlisia, you guys are doing this type of work. Is there anything that you think is like unique to a cloud native job? [0:04:35.2] CC: Yeah, it’s very interesting to talk about I think because especially in relation to if you don’t have a cloud native job, what do you have and how is it different? I wonder if the new cloud native job title is the new full stack developer for developers because, I think it’s easier to conceptualize what a cloud native job is for a systems admin or dev ops person. But for developer, I think it’s a little more tricky, right? Is it the new full stack? Is it now that the developer even if you’re not doing – for example, my application runs inside Kubernetes, it’s an extension of Kubernetes but some applications just run on Kubernetes as a platform. Now, are we talking about developers with a cloud native title like ‘cloud native software engineer’ and for those developers, does it mean that they now have to design, code and deploy consistently? You know, in my old days, when I – before doing this type of work, I would deploy apps but it was not all the time. There was a system, every single job I had, the system was different. The one thing that I love about Kubernetes is that if I was just a regular app developer, again as supposed to like extending Kubernetes, right? If I was building apps that would run on Kubernetes as supposed to extending Kubernetes, and if I had to deploy them at Kubernetes, if I move jobs and they were working with Kubernetes, this process would be exactly the same and that’s one really cool thing about. I wouldn’t mind – in other words, I wouldn’t mind so much if I had to do deployment in the deployment, the process was the same everywhere. Because it’s really painful to do like a one off deployment here and there, each place was different, I had to write a ton of notes to make sure, you know – it was like, 200 stacks and if anyone of them, you had to troubleshoot and I’m not a systems admin so it will be a struggle. [0:06:44.6] BL: Yeah. [0:06:45.8] CC: Because each system – it’s not that I couldn’t learn but each system would be different and I make – anyway, I think I went off on a tangent. [0:06:53.1] NL: No worries. [0:06:54.1] CC: But I also wanted to mention that I searched on LinkedIn for cloud native in the jobs section and there are a ton of job titles, job postings with cloud native in the title like a lot of it is architect but there is also product manager, there is also software engineer, I found the one that was senior Kubernetes engineer. It’s definitely a thing. [0:07:21.0] BL: All right. What is the question here? [0:07:25.6] NL: It was what do we think a cloud native job looks like essentially? [0:07:29.6] BL: All right. I’m going to blow your mind here. Basically, what is the cloud? The cloud is other people’s computers. It's LPC and what is Kubernetes? Well, basically, it’s a way that we can run our software on other people’s computers, AKA the cloud. Kubernetes makes running software in the cloud easier. What that really breaks down to is if you are writing software on other people’s computers or if you were designing software that runs well on clouds, well, you’re a cloud native person. Actually, the term is basically been co opted for marketing purposes by who knows who.Basically, everyone. But what I think is, as long as you are working on software that runs on modern infrastructure which means that nodes may go away, you might not own all of your services, you might use a least database server, you know, something like RDS from Amazon. Everyone working in that realm, working with software that may go away with things that aren’t theirs, was doing cloud native work. We just happen to be doing on Kubernetes because that’s the most popular option right now. It isn’t the only option and it probably won’t be the final option. [0:08:48.7] CC: Do you see any difference between what is required for a job like that today? Versus maybe 10 years ago or five years ago? Brian? [0:08:58.0] BL: Yeah, actually, I do see some differences. One of the biggest differences is that there’s a lot more services out there that are provided to help you do what you need to do and so 10 years ago, having a database provider would be hard because one, the network wouldn’t be good enough and you’re hosting company probably didn’t have that unless you were at AWS and even they didn’t have that. Now, what we get to take advantage off is things are just easier, it’s easier to fire up databases, it’s easier to add nodes to our production. It’s easier to have multiple productions, it’s easier to keep that all in order. It’s easier to put automated configuration around that than it was 10 years ago. Now, five years ago, back in 2014, I would actually say that the way that we progressed since then is that we became more mature. I remember when Kubernetes came out and I thought it was going to win but Mesosphere was, mesosphere with Aurora, or marathon was actually better than Kubernetes, just it worked out of the box, for what we thought we could do with it but now, what we have now is we know what we can do with distributed computing and now we have a great set of software for multiple vendors who allow us to do what we want to do. That’s the best part about now versus five years ago. [0:10:17.7] CC: Yeah, I have to agree with that, it’s definitely easier. As a developer, I’m not going to tell you it’s easy but it’s easier. As an example. I remember when that was Rails Rumble maybe 10 years ago, I don’t know. [0:10:31.3] BL: Yeah, I remember. [0:10:34.0] CC: You did a video showing step by step how to boot up a Linux server to run apps on that server. I don’t remember why we needed to boot up from scratch. Remember that Brian? [0:10:46.9] BL: I do remember that. That was 2007 or eight? It was a long time ago. [0:10:53.0] CC: That was one of the place that made me very impressed about you because I followed all the steps and at the end it worked. You just was – you were right on with – as far as the instructions went. I think doing that, I think it took me about two hours, I remember it took a long time and because this again, these are things that I do once in a while, I don’t do these things all the time. Now, we can use a Terraform script and have something running in a matter of 15 minutes if you have. [0:11:26.9] BL: Side bar. Quick side bar. Yeah, we can use Terraform. I use Terraform for even all my personal infrastructure so things that are running in my house use Terraform. All my work stuff uses Terraform. But still, it’s sometimes easier to just write a script or type in the commands on the command line or click something. We’re still not to the point where using things like Terraform actually makes us not want to do it manually. That’s how I know that we’re not to our ultimate level maturity yet. But, if you want to, the options are there and they’re pretty good. [0:12:01.8] CC: Yeah. [0:12:03.6] NL: Carlisia, you said something that kind of reminded me and maybe kind of get down this path. While we’re talking about like there are certain challenges that we aren’t faced anymore in a cloud native land like things are easier, there are certain things that are easier, not to say that our jobs are easy, like you’re saying Carlisia. But it was something along the lines of like a developer now needs to be – like a cloud native job is now the full stack kind of job or full stack developer. That was the name of the game back in the day, now, it’s a cloud native job. I actually kind of agree with that in a sense where a cloud native developer or anyone in the cloud native realm has to exist not just in their own silo anymore. You need to understand more of the infrastructure that you’re using to write your code on someone else’s computer better. I actually kind of like that. [0:12:56.6] CC: Exactly. [0:12:58.0] NL: Yeah, there are certain challenges now in cloud native that are gone so the things that were hard before like spinning up a server, you know, getting the database, these things are gone and that now that frees us to worry about more complicated or more abstract ideas like how do we have everyone agree on the API to use and thus rises Kubernetes. [0:13:19.1] CC: Yeah, I see that as a very positive thing. It might sound like – it’s a huge burden to ask developers to now have to now this but again, if we stick to the same stack, the burden diminishes really quickly because you learn it once and then that’s it. That’s been a huge advantage. If it works out this way, I mean, I’m all for like you know, the best technology should win. But there is that advantage. If we remain using the same container orchestrator, you know, we use containers, we can run our code as if we were running any machine. One advantage that I see is that I’ve had cases where you know, these was working on my computer (™) and it will be deployed and one little stupid thing wouldn’t work because the way the URL was redirected, didn’t work, broke things, I got yelled at. I’m like, “Okay, you want me to do this right? Give me a server.” Back then, good luck, “I’m going to give you a server, no way.” It was just so expensive, developers will be lucky to get a tasking of our staging environments. And, even when you get there, you had to coordinate with QA and there was a process. Now, because I have access to my own servers here, right? I can just imagine if I were a developer, building apps to run Kubernetes, admin could just say, “Okay, you have these resources, go for it.” I’ll have my own name space and I could run my code as if it was running and a production environment and I’ll have just more assurance that my code works basically. Which is to me so satisfying. It’s one less thing to worry about if I deploy something to production, I have already tested it. [0:15:17.3] NL: Yeah, that’s great. That’s something I really do cherish about the current landscape. We can actually test these things out locally and have confidence that they’ll work at least fairly well in production, right? [0:15:30.2] CC: It’s not just running things locally, you can actually get access to like a little slice of let’s say an AWS server and just shift your things there and test it there. But because these system admins people, they can just carve out that little one slice for your team of even in the per person basis, maybe that’s too much but it’s relatively uncomplicated to do that and not very costly. [0:15:56.9] NL: Yeah. You mentioned a team and the name of a team that I haven’t heard of in quite some time which is QA. How do we think the rise of cloud native have affected jobs and also kind of tangential to that, what were jobs like prior to cloud native because I haven’t heard of a QA team in many of the organizations that I’ve touched. Now, I’m not touching their like production dev team that they actually make this, I just haven’t heard of that name in a while and I’m wondering if like jobs like that have kind of gone away with the rise of cloud native. [0:16:27.7] BL: No, I’m going to end that rumor right here, that is a whole untruth. [0:16:33.8] NL: That was not a rumor, I’ve just conjecture I my part, literally unfounded. [0:16:38.7] BL: We got to think what does QA do? QA is supposed to be responsible for the quality of our applications and when they first started, there wasn’t a lot of good tooling so a lot of our QA people were manual testers. They started the app, they clicked on everything, they put in all the inputs until it came back and they were professional app breakers. I’d say, over a decade ago, we got more automated tools and moving into now, you can automate your web browser, you can actually write software to do all the actions that a human would do. What we found is that QA as profession has actually matured and you can see that because Google, I don’t think they even have QA, they have, what do they call them? Software engineers under test or SDE’s. What they do are – they’re developers in their own right but they write software that makes it easier for developers to write code that works well and a code that can be tested. I think that the roll has matured and has taken another angle in a lot of cases but even where we work. There are QA engineers in our group and we still need them because you’ve seen the meme where you talk about unit testing and it would be like a door that had all the right parts but it didn’t fit in it’s casing or too hot handles on a sink. The pieces work right? They both put out hot water but together they didn’t work. We still have that, it just looks a little bit different now. Also, a lot of software is not written in a huge monolithic cycle where we would take six months to release anew version or a year or a year and a half. Now, people are trying to turn around a lot of software quicker so QA has had to optimize how they work to work in those processes. They’re still there though. [0:18:37.8] CC: I would hope so. I mean, I can’t answer the question if the question is do we have as much QA efforts out there as before. I don’t know, but I hope so because if you don’t have a QA, if you’re not QAing your apps, then you’re users are. That’s not good. For my team for example, we do our own QA but we do QA. We don’t have separate people doing it, we do it ourselves. It might be just because it’s pretty special, I mean, we are a small team to begin with and what we do is very specialized. It will be difficult to bring someone in and teach them and if they’re just running QA, I don’t know, maybe – I don’t think it will be that difficult, we can just have constructions, you know. “Run this command, this is what the output should be” – I don’t’ think it would be that difficult, take that back, but still, we do it ourselves. [0:19:31.7] NL: The question was more – less in line with like, “What happened to QA?” It was more like, how do we think that cloud native has affected jobs and the job market and it sounds like, that jobs have changed because of cloud native, they’ve matured as we were just discussing with QA where people aren’t doing the same kind of drudgery or the same kind of toil that they were doing before. Now, we’re using more tooling to do our jobs and kind of lifting up each position to be more cloud native-y, right? More development and infrastructure focus at the same time. At least, that’s what I was getting from it. [0:20:09.8] BL: Yeah, I think that is true but I think all types of development jobs, especially jobs that are in the cloud native space have changed. One good example would be, with organizations moving to cloud native apps, we’re starting to see, and this is all anecdotal, I have no evidence to back this up, that there are more developers who are on call for the software they write because one, they know it better than anyone else and they’re closer to it. And two, because having an ops group that just supports app isn’t conducive to being productive because there’s no way that one group can understand all apps. What we’re finding is that in this new cloud native era that jobs are maturing and they’re getting new functionality, they’re losing some functionality, some jobs are combining but it’s still at the end of the day, it’s the same thing we were doing 20 years ago but it all just has new titles and we use new software to do it. Which is good. Because on some of these ideas that we came up with, 20, 30 years ago are still good ones today. [0:21:15.5] NL: Yeah, that’s actually an interesting question. Do you think that it’s just the titles that are changing or are the functions changing, right? It’s like sys admins used to be sys admins, now they’re CREs, well then there are dev ops for a while and now they’re CRE’s, more SRA’s I should say. Our support team are now CREs, Customer Reliability Engineering. Is that just a title change or are there functional differences? I’m inclined to believe that they’re functional differences. [0:21:43.9] BL: I think it’s both, I think it’s the same reason why all engineers after two years in the field are somehow senior engineers. People feel like they have progress when they get new titles even though you’re the most junior engineer on this team, how can you be a senior engineer? And then also the same thing with CRE, shout out to Google for making that term popular but really, what it comes down to is maybe the focus changed but maybe it didn’t. Maybe we were already doing that, maybe we were already doing resilience engineering with our customers and maybe we already had great customer support or customer success team. But I do think that there has been some changes in jobs because what we’re finding is that with modern languages that people are using so teams are moving away from C++ to things like Swift and Go and Rust. We’re finding that because our software is easier to write, we actually don’t have to think about some of the things that we did before. With Go, technically, you don‘t have to worry about memory access. With Rust, 100%, you don’t have to worry about null pointer exceptions, they don’t exist. Now that we freed our developers to do more development rather than more debugging, then what we can find is that the jobs will actually change over time. But at the end of the day, and even where we work right now and then all over the place, people are devs, they do ops stuff, they do security stuff or they’re pointing here at Boston. I challenge anyone listening to this to find something where I am not telling the truth, we might do both or more than one thing but at the end of the day, we can still break it down to what people do. [0:23:24.8] NL: Yeah, Carlisia, any thoughts on that? [0:23:26.1] CC: No, I think that was nice with me, sounds right. [0:23:29.8] NL: Yeah, I agree. I think that there are some functional changes. I think that support versus CRE isn’t just like getting tickets received and then going to a ticket queue and filing those things. I think there are some changes with like, I know from our CRE team they are actively going out and saying like, “Here’s our opinion based on these technologies and this is like why we validated these things,” that are reevaluating their support model constantly and just making sure that they’re like abreast of everything that’s going on so they can more resiliently engineer their customer support. [0:24:04.5] BL: But hold on, one second though. That’s what I’m talking about with the marketing because guess what? It is supported, a good support team would be doing all those things whether it’s called customer reliability engineering or whatever, it’s support, it’s customer success, it’s getting in front of our customer’s problems and having the answers before they even ask the question, that’s good support. Whenever we label things like CRE, that’s somebody and some corporate marketing center who thought that that was a good idea. But it doesn’t mean because you don’t call that CRE, it’s not good support because I will tell you in the past, DigitalOcean, we did that and the term CRE didn’t even exist yet but we were out there in front of problems whenever we could be and we thought that was good for our customers. What we’re finding is that people have the capabilities now with the progress of whatever technologies we have that we can actually give our customers good support, and you don’t have to be a Google sized company to do that anymore, that’s the plus. [0:25:02.9] NL: Yeah, I agree with that. [0:25:05.5] CC: I want us to talk a little bit about for people who are not working in a cloud native space but they see it coming or they want to move towards doing something more in that area, what should they be looking at? What should that be brushing up on their learning or incorporating into their what they are currently doing and of course different roles and so it will be different for each different role. We have developers we have DevOps or SRE or admins or operators, managers, recruiters. It changes a little bit for everybody. [0:25:47.5] BL: Well I will hop in here first and say it is all code at the end of the day. When it comes down to what we are doing in cloud native for ops, it doesn’t really matter. You could take a lot of the same principles and do them on prem or wherever else you happen to be. I mean I am not trying to diminish the role of anyone that we work with or anyone in our industry whenever I say this though but when it comes down to it, what I see is people understand the operating system, mostly Linux. People understand public key encryption so they understand PKI, you know we deal with a lot of certs. They understand networking, they can tell you how many IPs are in a 23 and if I am giving you side or numbers out there. These are things that people know. I don’t think there is anything specific for cloud native other than learning Kubernetes itself or Mesosphere or Docker, Swarm or whatever or the tool from HashiCorp that always escapes me whenever I have to say it out loud. But it is all the same thing. What you need to know and to be good at any job where you are doing ops, you need to understand the theory of operating computers. You need to understand operating systems, networking and how that all works and then all things around and some security. For developers now, it is a little bit interesting because a lot of the apps that we are writing these days are more stateless. So for a developer you need to think more about my app may crash. So anything that I am holding a memory that is important can go away at any given time. So either, one, I need to store it on more than one thing, I need to have it in a restrictive fashion or, two, I need to store it in the database instantly And I would once again challenge anyone to say that if you are a developer who can actually understand those topics, you would be able to apply for a cloud native job in this space because frankly a lot of developers, a lot of cloud native developers writing apps working cloud native, two years ago they were doing something else. [0:27:50.1] CC: Yeah that sounds right. I think for developers where you said I think focusing on authentication, how do you handle secret keys and the question of row authentication and row authorization and if you can even be well-versed in developing clients and servers and handling certs for that interaction and I guess it comes down to being well-versed in distributed systems development is what this whole cloud native is all about and on top of that I think being well-versed on how to push your apps into containers. You know create images, creating containers, pushing them into repository, pulling them from the repository and manipulating and creating containers in different ways and then on top of that maybe you want to learn Kubernetes and we can talk about that too but I wanted to give Nick a chance to talk about his aspects. [0:28:59.0] NL: I agree with pretty much everything you guys have said. I think the only thing I would add is like really understanding how to use and work with an API and an API driven environment because that is what a lot of cloud native is, right? It is using someone else’s computer so how do you do that? It is via an API like we’re talking about containers and orchestration, those are all done hopefully within API. Luckily, if you are using Kubernetes, which likely you are. It is all API driven. And so using an API, I think, and getting familiar with that. Most developers I think at some point are familiar with that but just that would be the main thing I would think too, outside of what you and Brian have already said are what is needed to do like a cloud native job. [0:29:40.2] CC: Yeah. Now if someone wanted to learn Kubernetes, well there is the Kubernetes Academy. [0:29:47.5] NL: There is a Kubernetes Academy. [0:29:49.4] CC: That is pretty awesome but do you think going through the certification would help? [0:29:55.3] NL: I think that is a good place to start. So the current certification that exists is the CKA, the Certified Kubernetes Administrator and I think that is a good starting place, especially for someone who is not really touched Kubernetes before. If they’re like, “How do I know the basics of Kubernetes?” going through that certification process I think will be a huge step forward because that really covers most of what you are going to touch on day to day basis for Kubernetes. [0:30:21.6] CC: And there is the CKAD as well, which is for developer. The CKAD is Certified Kubernetes – [0:30:29.7] BL: Application Developer. [0:30:31.7] CC: Application Developer and the other one is Certified Kubernetes Admin. [0:30:34.9] NL: Yeah I was like, “administrative developer?” like. [0:30:38.2] CC: If you are brand new I think it is worth while doing the developer first because it is mostly the commands. You go through the commands just so you have a knowledge of how to interact with Kubernetes and the admin is more like how you manage and how do you troubleshoot a cluster and how do you manage cluster. So it is more involved I think. You need to know more but in any case, I agree with you that it would help because it serves as a syllabus for what to learn. It is like, “Okay, these other things that if you know these things, it would help you a lot if you had to do anything with Kubernetes.” [0:31:14.6] NL: Yeah, I don’t think that you need to have a certification to do a job. I really don’t think so unless it is like required by law like you have to. [0:31:23.2] CC: No, yeah not at all what I am saying but if you don’t know anything at all and you’re like, “Where do I start?” I would recommend that. That is not a bad place to start or if you know some things but you feel like you don’t know others and you want to fill in the gaps and you don’t know what your gaps are, also same idea. What do you think Brian? Do you think having this certification would be useful? [0:31:46.5] BL: I don’t know, some people need it but I am also barely graduated from high school and I don’t have a college degree. So I have always leaned on myself for learning things on my own schedule, in my own pace on my own terms but some people do need the structure provided to them by certifications and I’ve only heard good things of people taking those tests. So I think for some people it is actually really good but for others, it might be a waste of time because what will actually happen if you get that certification? If you work at some large companies, I do know this for a fact by getting your AWS certificates actually had a money thing behind it but in a lot of places I don’t know but it couldn’t hurt. That is the most important piece. It can’t hurt. [0:32:36.3] NL: Yeah, I totally agree. You learn at least something even when I am taking a certification exam for something that I was already pretty aware of, I always learned at least one thing by taking like an examination. The last good question that you likely have never even thought off but I also agree with Brian where it is like I don’t have my CKA and I think I am a pretty damn good expert of Kubernetes. So I don’t think anything would change for me to take the exam. [0:33:00.2] CC: Oh yeah. I work with so many people who have none of those sort of certifications and they are absolutely experts. I was talking about like it would help me. I want to take those two certifications because it helped me fill in the gaps and I know there is a lot that I am going to learn especially with the admin one. So it is using the curriculum as a guide for what I need to learn and then testing, did I really learn and also it made me feel good but other than that, I don’t think it has any – I don’t know, I don’t think it is bad either. [0:33:33.4] BL: And that is the most important piece, what you just said, it made you feel good because you take certifications to test your knowledge against yourself in a lot of cases. So I think it is good. I just realized you can – I mean people cannot see behind me. I don’t think I have as many books as Carlisia’s up there but I have read all mine except for like four of them. [0:33:52.6] CC: Yeah, I did not read all of these books. I mean a lot of these books are school related books that I kept because they are really good and books that I have acquired and I have read ome but not all the entire book. Some things I use for reference but definitely have not read. Don’t be impressed, I have not read all of these books. Hopefully one day when I retire maybe. Anyway – [0:34:17.7] BL: I think that one interesting thing would be the amount of study that you need to do to gain a certification when you are not working in the space actually gives you that little bit of push that you need to make sure that you understand that you know what you need to know. So if you organically came to cloud native as I did, as I’ll explain in my story, you know I am not really interested in that certification. But if I wanted to change, and maybe I wanted to change my focus to doing more graphic stuff and there was a certification for this, maybe I would think about it just to make sure that I knew I was eligible for these jobs that I am trying for, so. [0:34:57.8] CC: Yeah. [0:34:58.8] NL: Yeah, that makes sense. Also, my books are over there and I have read most of the way through many of my books but not all the way through because a lot of them are boring. [0:35:09.5] BL: But I will say and since we are talking about books and talking about getting yourself into Kubernetes land, right now is actually the best time to buy books because there is lots of them and I am not actually saying that these books are super awesome but some of them are. Notably this Programming Kubernetes book is pretty awesome and the reason it is so awesome is because my quote is on the back of it. [0:35:33.3] NL: I was going to say. [0:35:34.4] BL: Yeah, my name is on the back of it and then another book that I just picked up lately is called The Kubernetes Cookbook and it is for building cloud native applications from O’Reilly and the reason that I like it is because I have always, since I mean 20 years ago, I love creating O’Reilly cookbooks because small problem, answer with an exclamation, and then there is another one called Kubernetes Patterns, which I just started and I think it is pretty good too. And just to say that these are not endorsements but this is what I am reading right now. It is like a thousand pages here. The things that I am trying to get through right now to keep up to date with what we are trying to do because actually the biggest problem with what we are doing is that we are trail blazing. So a lot of the things that are happening, like the way that Kubernetes advances every few months is new, new, new, new. So there is not a lot of higher art in what we are doing that is public. So what you need to do is turn yourself into someone who actually understands the theory of what we are doing rather than the practical application of it. Understand that piece too but you got to understand the theory, which is why I said I’ve literally doing the same thing for the last 25 years because I learned how to program and I learned a Unix and then I learned Linux and then I learned networking. Take all of those lessons and I can apply them all the time. So that is actually the most important part about any of this. [0:36:56.9] CC: Yeah, I agree with you like going through the fundamentals helps so much more than going through the specifics and in fact, trying to learn specifics without having fundamentals it can be very painful but then you try to learn the fundamentals and then you go, “Oh yeah, it totally makes sense. I have been trying to listen to YouTube lectures on the server systems and I have a lot of moments of, “Ah that is why Kubernetes works this way to address this problem.” And I have that programming book, which is not in my office. I have to find it but yes that is a very good book, I have this. [0:37:37.9] BL: Oh Cloud Native DevOps with Kubernetes. That is another good book. [0:37:43.5] CC: Yes. [0:37:44.3] BL: I have it too. [0:37:46.3] CC: I have like that as one? [0:37:47.6] BL: Yes. [0:37:48.2] CC: Good book and this, I haven’t gotten through it yet. [0:37:52.7] BL: It is called Kubernetes in Action. [0:37:54.3] CC: Yes, thank you for saying the name because if you are not in the video you wouldn’t know. [0:37:58.5] BL: So really what we are saying now – [0:37:59.7] CC: People say great things about the Kubernetes in Action, this one. [0:38:02.9] BL: So I actually want to bring up another thing and say, I read a lot. I like to read. I read a lot of blog posts and here is another crazy thing, the YouTube videos from like KubeCon every year or every few months, we publish a 180 talks for free and there is some good lessons in those. So the good thing about getting into cloud native is that you can get into it for cheap because all of this information out here Kubernetes source is free. Go read it. I mean 5,000 developers have worked on it. I am sure you will get a lot out of that, go do that but like YouTube talks, blog post, just following your favorite SIGK’s, Special Interest Group for Kubernetes, their community meetings. You can learn so much about how this space works and really how to write software in it without spending a dime other than have a computer and Internet. [0:38:55.5] CC: Yeah and I am going to give a tip for people that I actually caught on not too long ago. I subscribed to YouTube premium, which I think is $5 a month. It is the best $5 I have ever spent because really I don’t have time to sit in front of a video unless it is very special and just watch something and reading is also very – after I spend a whole day reading codes, my mind doesn’t want to read anything else. So I love podcasts and I listen to a lot of podcast. And now the YouTube videos are even have been more educational to me because the premium version of YouTube is if your phone locks it will still play. [0:39:40.2] BL: And you can download the videos. [0:39:42.0] CC: You can download the videos too. Yeah if you go on a camping trip or airplane you have them so it’s been fantastic. I just put my headset, my little Bluetooth headset and as I am doing laundry or as I’m cooking or anything, I am always listening to something. There goes the tip. [0:40:01.9] NL: Yeah, I totally agree. I love YouTube premium. No ads as Brian said is the best. I am going to throw out a book recommendation, one written by my colleague and a good friend, Craig Tracy, or co-written called Managing Kubernetes and it is actually like I was saying that these tech books are kind of boring, this one is actually a lot of fun to read. It is written well in a way that I found I kept turning at the page. So I really liked it. [0:40:26.3] BL: Yeah, it is only 150 pages too. [0:40:29.3] NL: Yeah that is pretty short. [0:40:30.5] BL: And the software that Carlisia writes is the last chapter of it, the next to last chapter so. [0:40:37.6] NL: Oh shoot, all right throw it out then. [0:40:40.4] BL: Well no, I am just saying it is another good book and I like the way you bring this up because this information is out there but I know were coming close to the end and I had one thing that I want to talk about today. [0:40:50.3] NL: I was just about to bring that up, please take us away. [0:40:52.3] BL: All right, so we talked about where we come from and we talked about things in the space about the jobs, how we keep up to date but really, the most important piece is what happens in the future. You know Kubernetes is only five years old so theoretically cloud native jobs are only a few years old. So how does cloud native move in the future and I do have some thoughts on this one. So what we are going to see is what we have seen over the last two decades is that our stacks will get more complex, we will run more apps, we will have more CPU’s and more networking and it is not even Morris Law stuff. We’ll just have more stuff. So what I find is that in the future, what we need to think about are things like automation. We need to think about better resilience. Apps that can actually take care of themselves. So your app goes down, what happens? Well nothing because it brought itself back up. So I see that the jobs that we have now are just going to evolve into better versions of what we have right now. So developers will still be developing. The more interesting piece is that we are going to have more developers because more people are taking these boot camp courses, more people are going into computer science in school. So we are actually going to have more developers out there. So all that means is that we are just going to have more problems to solve at least for the next few years. The generation from now, I couldn’t tell you what is going to happen. Maybe we will all be out of work. I will be retired so I probably won’t care but just think about this. Now is the literal best time to get into writing software and specifically for cloud native applications whether you are in operations or you are writing applications that run on clouds or anything like this. This is the best time because it is still beginning and there is more work to do than we have people and if you look through jobs postings you’ll realize that wow, everyone is looking for this. [0:42:48.3] CC: Yeah and at the same time, there is a sufficient amount of resources out there for you to learn even if you don’t want to – if you want to or you can’t pay. We now are so much at the beginning that there is nothing so it is a very good time. [0:43:04.6] NL: Yeah, the wealth of knowledge is out there that is for free is unheard of. It is unprecedented and yeah, I totally agree that this is the best time. Brian, if we go by your thesis throughout this entire episode, basically we are going to be doing the same thing in 20 years as we are doing now. It is the same thing we did 20 years ago. So it is probably going to be like you said, developers are going to develop-ate, sys admins are going to sys administrate. [0:43:28.6] CC: I love that. [0:43:30.1] BL: And security people are going to complain about everything. [0:43:33.4] NL: That is how we are going to change. So we are just going to be running on like quantum applications in 20 years but they are still going to be if/else statements. [0:43:41.1] CC: My prediction is that we are going to have greater server access, like easier server access, and especially developers and there will be more buttons to press and more visual tools so you don’t have to be necessarily logging into a server to command lines that we have more tools abstracting all of that detailed work that develops. [0:44:07.0] BL: So more abstractions on top of abstractions. [0:44:10.1] CC: Yeah that is my prediction. Why not? [0:44:13.3] BL: Well you know what? I mean if that is true because that is what we have been doing forever now so we are going to continue on doing this thing. [0:44:20.0] CC: Because it is what people want. [0:44:22.0] BL: Because it works. [0:44:23.0] CC: Yeah, it makes life easier for some people. I don’t see why we wouldn’t move in that direction but before we wrap up, unless you guys want to make predictions too, I really wanted to touch base on the hiring side of things. The recruiters and hiring managers before interviewing, I can’t imagine there is a whole bunch of people out there who need to recruit people to do these cloud native jobs and how can we help them? Like can we give them some tips? How can they attract people? What should they be looking for? [0:45:03.4] NL: Well, I guess my thought is that I really feel like recruiters need to start learning the technology that they are hiring for. I don’t think that they can hide behind the idea that they’re recruiters and they don’t need to know. If you want to hire good people, if you want to weed out the bad people or whatever it is that you are trying to do, you need to actually learn the technology that you are hiring for and I think like we are saying, there is now a wealth of knowledge that is free for you to access, please look. [0:45:32.9] CC: I am not going to disagree with that. [0:45:34.3] BL: And the interesting thing is when he says learn it, he doesn’t mean that you have to be able to produce it but you should understand how it works at the minimum. [0:45:42.8] NL: Yeah and also know when someone’s BS-ing you in the text screen. [0:45:48.2] CC: But it is not easy because you might be going in the direction with the intention of learning and you might misunderstand things and you know how deep do you have to go to not misunderstand the technology? [0:46:06.1] BL: You know what? I don’t think there is an answer for that. I think it is just you don’t know and there is something in between being an expert. You need to be something in between where if you’re hiring for cloud native in Kubernetes, you can’t offer a job that wants 10 years of Kubernetes experience. First of all, Kubernetes is huge and no one has all Kubernetes experience throughout the whole stack and second of all, Kubernetes is only five years old. So please don’t do that to yourself as well. So you should know how old it is and at least know the parts and what your team is going to be working on but for managers, wow, actually I don’t have a good answer for that. So I am just going to I’ll plan on that one. [0:46:45.1] CC: Well, how would it be different? Actually it is going to sound like I asked a loaded question but I just now had this realization. I don’t think it would be different from what we were saying in regards to giving tips for people to prepare themselves, to make a move into this space if they are not working with any of this stuff. It will be the same, like try to find people who know distributed systems, they can debug well. I am not even to go into working well with people. That is such a given. Let’s just keep it to the text stack and all of those things that we recommended for people to learn, I don’t know. [0:47:26.0] BL: Yeah, it sounds good to me. [0:47:28.1] NL: All right, well I think that just about wraps it up for this week of the podcast, the Kubelets Podcast. I thought this was a really interesting discussion. It was cool to talk about where we were and where we are going and you know, and what brought us all together as I said. [0:47:44.2] CC: Nick, do you want to share with us what your tagline for this episode was? [0:47:48.1] NL: Yeah, the tagline for this episode is CREAM: Cash Rules Everything Around Me. [0:47:53.3] BL: Dollar-dollar bills you all. [0:47:55.8] CC: Ka-ching, ka-ching, ka-ching [0:47:58.8] NL: All right, thank you so much. Thank you Brian, thanks for joining us. [0:48:03.9] BL: Thank you for having me. [0:48:05.3] NL: Yeah and thank you Carlisia. [0:48:07.6] CC: This was really good, thank you. [0:48:09.7] NL: Yeah, I had a lot of fun. Bye, y’all. [0:48:13.5] BL: Bye. [0:48:14.1] CC: Bye. [END OF EPISODE] [0:48:14.8] ANNOUNCER: Thank you for listening to The Podlets Cloud Native Podcast. Find us on Twitter at https://twitter.com/ThePodlets and on the http://thepodlets.io/ website, where you'll find transcripts and show notes. We'll be back next week. Stay tuned by subscribing. [END]See omnystudio.com/listener for privacy information.

Wonder what Mesosphere has been up to? Find out on the second installation of our #KubeCon 2019 series, where we’ll talk about some of their new products—and their why they rebranded themselves to D2iQ.

Today's guest is Benjamin Hindman, Co-Founder of D2iQ (formerly Mesosphere). After founding a company with buddies from high school, would you undertake a CEO search and an entire company rebrand? If you did, here's what you'd learn: Why founding a company with high school buddies is a great and terrible idea What it's like to search for a CEO The process of rebranding Listen to this and all of The Founder Formula episodes at Apple Podcasts, Spotify, or our website.

In this episode, we dive into the exciting world of container orchestration in Kubernetes. We have all heard about container orchestration, but to truly understand this concept, we have to first understand what containers are and why they started! From definitions of containers and how they fit into the bigger cloud landscape, down to the nitty-gritty’s of managing and scaling container orchestration; this episode gives you strong foundation to better understand the functions and impacts of container orchestration today. Container orchestration in Kubernetes is so popular today but it can be difficult to how whether container orchestration is right for you. These are just some of the questions and topics we get into today, and if you’re looking for a solid base to begin your container orchestration process or enquiry – this is the episode for you! Note: our show changed name to The Podlets. Follow us: https://twitter.com/thepodlets Website: https://thepodlets.io Feeback: info@thepodlets.io https://github.com/vmware-tanzu/thepodlets/issues Hosts: Carlisia Campos Josh Rosso Nicholas Lane Key Points From This Episode: • Discover why container orchestration first came about.• Find out exactly what a container is and how it functions.• Using a container versus a virtual machine or process.• Managing container orchestration on a large scale.• Learn how container orchestration acts on information.• Managing actual state and expected state in container orchestration. • The key benefits of adopting container orchestration.• The key difference between container orchestrators.• A declarative way to approach resource limiting.• How to distinguish between the project and the product.• What is it that makes Kubernetes so popular today?• How to make an informed decision about using Kubernetes.• Find out when you should not be using container orchestration. Quotes: “The orchestration part is really just dictating behavior and state.” — @carlisia [0:05:43] “If you already use Kubernetes that would be like trying to plow the field with a nuclear bomb.” — Nicholas @apinick [0:42:10] Links Mentioned in Today’s Episode: Velero — https://github.com/vmware-tanzu/veleroYoutube Premium — https://www.youtube.com/premiumKubeCon China — https://01.org/events/2019/open-source-summit-china-kubecon/ cloudnativeconSteven Wong — https://twitter.com/cantbewongCloud Native Social Hour — https://www.youtube.com/watch?v=wxBxcdeMOYEKube Janitor — https://github.com/theMagicalKarp/kube-janitorDocker — https://www.docker.com/Mesosphere — https://d2iq.com/Red Hat — https://www.redhat.com/enKubernetes VS Docker Swarm — https://thenewstack.io/kubernetes-vs-docker-swarm-whats- the-difference/Kubernetes Slack Channel — http://slack.k8s.io/Kubelets Cloud Native Podcast — http://cloudnativepodcast.com/The Podlets on Twitter — https://twitter.com/thepodlets Transcript: EPISODE 02 [INTRODUCTION] [0:00:08.7] ANNOUNCER: Welcome to The Podlets Podcast, a weekly show that explores Cloud Native one buzzword at a time. Each week, experts in the field will discuss and contrast distributed systems concepts, practices, tradeoffs and lessons learned to help you on your cloud native journey. This space moves fast and we shouldn’t reinvent the wheel. If you’re an engineer, operator or technically minded decision maker, this podcast is for you. [EPISODE] [0:00:41.3] NL: Hello and welcome back to The Podlets Podcast, Episode Two, Container Orchestration. My name is Nicholas and joining me today this week are Carlisia and Josh. [0:00:50.9] CC: Hello. [0:00:50.9] NL: Hello. [0:00:52.0] CC: Good to be here again. [0:00:53.7] NL: Yeah. How was your week, everyone? [0:00:55.6] CC: Very good, lots of work. [0:00:57.3] NL: Yeah, anything exciting happening in the world of Velero? [0:01:00.1] CC: Yes, we just got our alpha release for version 1.0 and we are looking for testers, yeah, we want testers. [0:01:08.2] NL: Awesome. [0:01:09.2] JR: I’ve been traveling a lot but it’s been good, we’re doing a lot of interesting work with some Kubernetes cluster running in an on premise datacenter which is something we see less and less, now that the cloud providers are kind of taking on their different offering. So it’s cool to hop back to kind of the bare metal and virtualization space and play around there. [0:01:27.6] NL: That’s cool. I’ve actually got a question for you guys, kind of irrespective of container orchestration, but how do you guys manage travel, right? How do you keep yourself entertained, how do you keep yourself happy while you’re traveling? For me, it’s a lot of podcasts which is great, now that I’m doing a podcast. [0:01:43.0] CC: Yeah, I do podcasts. I signed up for YouTube premium so I can download videos. I watch the movies on the plane, I have a kindle with lots of books. [0:01:56.2] NL: Yeah, that’s nice. [0:01:57.4] CC: Or I just sleep. [0:01:59.0] NL: I wish I could. [0:01:59.9] JR: Yeah, sleep is always the first goal, but I also signed up for YouTube Premium and the offline feature is fantastic so there’s so much good info on YouTube, you know? It’s great to like – go to the KubeCon Playlist and just choose offline and then you have all that time in the plane to really sift through talks and what not. It’s been really cool. [0:02:18.9] CC: Exactly. [0:02:19.8] NL: That’s a great idea. I’ve actually not used YouTube Premium for that. I’ve only ever used it for like meditation tracks, to use on the airplane. I spend some time in the plane kind of just in my own head a little bit kind of doing some internal self-care if you will. [0:02:34.0] CC: Nice. [0:02:34.7] NL: But that gets boring.EPISODE 02 [INTRODUCTION] [0:00:08.7] ANNOUNCER: Welcome to The Podlets Podcast, a weekly show that explores Cloud Native one buzzword at a time. Each week, experts in the field will discuss and contrast distributed systems concepts, practices, tradeoffs and lessons learned to help you on your cloud native journey. This space moves fast and we shouldn’t reinvent the wheel. If you’re an engineer, operator or technically minded decision maker, this podcast is for you. [EPISODE] [0:00:41.3] NL: Hello and welcome back to The Podlets Podcast, Episode Two, Container Orchestration. My name is Nicholas and joining me today this week are Carlisia and Josh. [0:00:50.9] CC: Hello. [0:00:50.9] NL: Hello. [0:00:52.0] CC: Good to be here again. [0:00:53.7] NL: Yeah. How was your week, everyone? [0:00:55.6] CC: Very good, lots of work. [0:00:57.3] NL: Yeah, anything exciting happening in the world of Velero? [0:01:00.1] CC: Yes, we just got our alpha release for version 1.0 and we are looking for testers, yeah, we want testers. [0:01:08.2] NL: Awesome. [0:01:09.2] JR: I’ve been traveling a lot but it’s been good, we’re doing a lot of interesting work with some Kubernetes cluster running in an on premise datacenter which is something we see less and less, now that the cloud providers are kind of taking on their different offering. So it’s cool to hop back to kind of the bare metal and virtualization space and play around there. [0:01:27.6] NL: That’s cool. I’ve actually got a question for you guys, kind of irrespective of container orchestration, but how do you guys manage travel, right? How do you keep yourself entertained, how do you keep yourself happy while you’re traveling? For me, it’s a lot of podcasts which is great, now that I’m doing a podcast. [0:01:43.0] CC: Yeah, I do podcasts. I signed up for YouTube premium so I can download videos. I watch the movies on the plane, I have a kindle with lots of books. [0:01:56.2] NL: Yeah, that’s nice. [0:01:57.4] CC: Or I just sleep. [0:01:59.0] NL: I wish I could. [0:01:59.9] JR: Yeah, sleep is always the first goal, but I also signed up for YouTube Premium and the offline feature is fantastic so there’s so much good info on YouTube, you know? It’s great to like – go to the KubeCon Playlist and just choose offline and then you have all that time in the plane to really sift through talks and what not. It’s been really cool. [0:02:18.9] CC: Exactly. [0:02:19.8] NL: That’s a great idea. I’ve actually not used YouTube Premium for that. I’ve only ever used it for like meditation tracks, to use on the airplane. I spend some time in the plane kind of just in my own head a little bit kind of doing some internal self-care if you will. [0:02:34.0] CC: Nice. [0:02:34.7] NL: But that gets boring. [0:02:36.0] CC: I meditate too, it’s great. [0:02:38.2] NL: Yeah, it’s good. All right, anything interesting in the cloud native space that you guys have found in the last week? [0:02:43.6] CC: I have a talk that was accepted for KubeCon China. [0:02:47.4] NL: Awesome, congratulations. [0:02:49.6] JR: Congrats. [0:02:50.6] CC: Yeah, it’s a joint talk with Steven Wong also from Thea Moore. We’re going to talk about data recovery, data protection, recovery, migration in Velero. [0:03:03.9] NL: That’s great. He’s been coming to the Cloud Native Social Hour pretty regularly. That’s awesome to see some more cross interaction. [0:03:11.6] CC: Yeah, he is awesome, so knowledgeable. [0:03:14.0] NL: Great. And Josh? [0:03:15.5] JR: Very cool. I was actually looking this week since I’m in kind of the Kubernetes mindset, for something that can kind of add a TTL to any Kubernetes resource. So think of something like a service account in Kubernetes and I want to attach a TTL to it such that in four hours, it effectively got swept up and is no longer existent in the system. There’s some interesting ways that actually Kube ADM, one of the bootstrapping tools, does this. I was trying to kind of replicate that for their tokens, there’s a project by one of these Landau folks. Jacobs, I don’t know if that’s his last of first name, sorry in advance for butchering it, but he’s got a project called Kube Janitor that does effectively that. With annotations, you can put a TTL on them, your resources and then Kube Janitor will just come through and sweep that up. Which I thought a really cool idea. That was an interesting thing that I saw, it’s no new news, I think it’s been around for a while but it’s the first time that I had run into it. [0:04:07.6] NL: Nice. For me, our cohost Duffy, turned me on to a tool called Chaos Blade. Recently, I’ve been getting more and more into Chaos engineering and this is apparently an easy to use Chaos engineering toolkit. Something I’ve only just started looking at but I’m pretty excited. I’ll probably play around with that a bit more. [0:04:25.2] JR: Cool, awesome. [0:04:26.9] NL: Yeah, this week on the podcast, we are talking about container orchestration and kind of what that is, right? For me, container orchestration is the idea that you need your workloads to run somewhere but you don’t necessarily need to care where they’re running and the way that this has been done traditionally, prior to container orchestration, was like scheduling VM’s or making sure these processes run on certain computers, right? There’s a lot of automation around that like, when containers came around, we needed some way to make sure that they’re running and it also enabled us to not need to care so much about how things get started in all that. Everything was kind of packaged in a container I think. They need to just be some way to run them. That’s kind of where container orchestration came in, is that kind of your guys’ take on that as well? [0:05:18.3] CC: Yeah, basically, when we say we are orchestrating containers, we basically tell them how to behave, right? For example, I have this container here and I’m going to declare that if it fails, I want it to come back up in this container over there, if you fail just keep that state, don’t do anything and then I might say hey, I want two of you, three of you, I want to – the orchestration part is really just dictating behavior and state. [0:05:48.6] NL: Yeah, absolutely. [0:05:49.9] JR: Yeah. I think one interesting thing that came with the advent of containers is, we used to have this notion of you know, what server is my application going to land on or then eventually, you know, what virtual machine is my app eventually going to land on and we think kind of in this units of virtual machines and the paradigm shift a bit, at least in my experience has been now that you have the container unit and you can run many of those on one virtual machine, right? Your concern about orchestration is not just putting it on machine A and putting it on machine B but it’s kind of like packing multiple of this containers, perhaps on the same virtual machine or same host. The orchestration notion is beyond just the conventional system construct of a different host each time, it’s really interesting. [0:06:34.0] NL: Yeah, I think it might be important for us actually to take a step back. I realized I kind of jumped right into it, but we should probably settle what a container is, right? Before we can talk about how we can orchestrate them. A container is basically just a tar ball honestly. That is a packaged application with the instructions for it to run on any system that can accept that tar ball. Containers are broken down into a couple of Linux constructs, C groups and name space, so C groups four, making sure the process runs in its own dedicated memory and then or just like isolated memory. Then name spaces for things like network isolation. So that the network traffic that’s going on in the container doesn’t cross over to other processes. Very controlled process initiation based on these instruction. That’s kind of what a container is, a lot of people think that they’re like, kind of like a VM, I’ve heard that a few times where like, “Oh how do I deploy it?” What’s the VMDK for a container? It’s just a process that runs on a computer in a very controlled fashion, that’s literally it. [0:07:43.9] JR: Yeah, it’s kind of interesting to think like, at what point in which we kind of started using containers and seeing containers. I’d be curious for either two of you, Carlisia especially, what was your first exposure to the unit of a container and why were you starting to consider using a container versus just a virtual machine or a process? [0:08:03.0] CC: Frankly, I don’t remember. My first time seeing a container has been a long time but I don’t remember. But probably maybe trying to do some application like some toy application that – an example application. I remember that I was working on an application that we had the option to stuff it into a container as well, but I personally didn’t make the development. I wasn’t using it for development. My first usage of container really was about three years ago when I was working for CDN and a CDN as you might imagine has many different parts, so it has very low-level software running to higher level software, right? Really, sometimes, well, not sometimes, it has kernel level applications in systems, and it has API level system. For you to develop one part of it is it was really handy to be able to stuff our different systems into containers and have containers stuck to each other. We weren’t using the introduction. This was for development, but it was amazing, it was fantastic, we would have applications developed and go. Different systems that needed to talk to each other and we would have applications in C and I think that is to remember but it was amazing. Everything in containers and then we have a tool as well, they were sort of like Kubernetes, it wasn’t Kubernetes. It was developed in house. That orchestrated all of these things and you know, we simply failed, bringing back up and did a bunch of other things as well. I cannot explain the difference of working like that. It’s so much faster and so I could be a lot more autonomous, being able to run everything myself. I didn’t depend on having access to its server. I ran everything on my laptop, it was fantastic. [0:10:17.6] NL: Awesome. The first time I ran into a container was back when I was working for Red Hat, right when Open Shift Three CEO came out, that’s when Open Shift kind of moved from the in-house version of Open Shift to adopting Kubernetes. I had been working mostly in the virtualization like infrastructure world like doing a Red Hat enterprise virtualization manager, which is kind of like a Red Hat take on B Sphere, you know, kind of. I was very used to virtualization and spinning things up. There is some aspects of creating a VM and creating a container that were very similar. It took me awhile for my brain to click. Once I started using open chip to kind of click into like, “Oh this is how they’re different, right?” Whereas, if you’ve just started looking at it, “Well what’s kind of the difference?” They’re all just like, in my command line, they all just come up as like lists of units, right? This is a processing unit, that’s a processing unit right there. They’re kind of similar but once you start really getting into the use of it, it was so much different. I had heard like during this process of switching over to these two tools, I had heard of Docker and I was like, it’s something I’ll take a look at and finally, by shifting over to it, I finally was starting to – like oh this is what docker is, this is how we use these and then like, kind of digging into containers there. It was an interesting switch from an infrastructure standpoint to like, this is how people use containers and then that kind of actually started getting me into development. Now that I didn’t have to care about all this overhead of like where do I put my application, if I want my application around on my computer versus your computer, how do I make sure that the packages are the same bubble? Once there was that easy way to kind of say, I just want this run everywhere, no matter what, hopefully, that really just like, fascinated me and it kind of took off from there. Josh, what about you? [0:12:11.6] JR: Yeah, my experience wasn’t to dissimilar. What was interesting is the space I was working in was a lot of legacy Java applications, so we kind of came into containers probably a little bit later than what some of you all did. What was always interesting about it is, you know, we started to really see the value of containers just like Carlisia was saying, we started packaging these apps up and they ran the same in every environment and just really changed our workflow around. Initially, it was just like, let’s figure out a way to simply start these containers on different hosts, whether it be like Answerable or even someone going out a host and typing Docker Run, you know, that was how we got these processes to start. As the adoption of containers grew and more and more containers started to come to life in this company, the need for orchestration finally became obvious, right?I had heard about this project called Kubernetes, I’d heard a bit about Swarm, Mesos and it was always just like I don’t understand why you’d ever need something this complex, right? But eventually you hit this like inflection point where it just becomes insanely obvious, that your life is potentially going to be just chaos without something that can actually figure out, hey, you need to run this container, let me figure out where to put it and make sure that it starts. I thought that was like a really interesting progression. It used to be really hard also to navigate the options because there were a lot of options and there still are, there’s Swarm Kubernetes, Open Shift, Mesos, so on and so forth. [0:13:31.9] NL: Yeah, that’s actually a good point to what I’m talking about is that, container orchestration, it seems like we’re all kind of building up to the same point where when containers were kind of taking off, everyone started to see like this is great. But how do I do this at scale? Even like remotely at scale. A bunch of people started doing their own thing. So there was Kubernetes, which is the open source version aboard with some changes to make a more friendly for other people, there’s Docker, Docker Swarm and then Mesos, Rancher. But then, Carlisia, your team had their own orchestration, a lot of other companies have their own orchestration as well so it’s not just – you don’t need like this project to do or any of these projects to do container orchestration. You can do it on your own if you need to, right? For example, you could take a look at Uber, they aren’t using a project, they’ve rolled their own container orchestration at scale and I think that’s the same, that’s crazy to me but that’s awesome for them to have pulled that off, right? [0:14:29.4] CC: Yeah, absolutely. When I think of container orchestration, there is the management part and the scaling part because when you think about management for example, I might need a whole set of services to be up and running before I can run the set of services. The orchestration is going to manage that for me. Make sure that the services come up, they’re up and now this set gets kicked off. If I don’t need to scale, I still need to do this, right? There is usually some sort of dependency. Then in the scaling part which is also – I mean, it’s important for a lot of companies but it’s not important for a lot of companies smaller sized companies, right? [0:15:18.7] JR: Maybe we can talk a bit about what kind of information container orchestration works with to determine what it should do, if that sort of makes sense? Like what kinds of things are we telling these systems about and then what is it doing to act on that information? [0:15:38.0] NL: Yeah, please, go ahead and dive into that a bit more. [0:15:41.0] JR: Yeah, I guess it seems like the common approach that we run into, at least with Kubernetes and I think it’s true for a lot of these different systems, is the notion of reconciling state, right? We start of kind of with declarative definition if you will of what we want the world to look like and that could be some app running with some amount of replicas and you want it to have a certain amount of CPU and memory available. Then, these orchestrators usually can just take that declarative notion and sort of act on it, right? I know Nicholas, you’re really close to Kubernetes, would you want to speak to like how exactly it acts on those things like when you give it that declarative API object? What it’s going to do behind the scenes? [0:16:24.6] NL: Yeah, in Kubernetes, there’s a couple of different systems at play. This is something that I find really fascinating. There’s a lot of reconciliation loops in many different places. In Kubernetes when you first declare to Kubernetes that you want something to happen, you talk to the API server. The API server then modifies the etcd data store, right? The data store is just, simply ley value pair brain, it’s like the brain of your Kubernetes, right? Only the API server, as far as I’m aware and remembering off the top of my head, that’s the only thing that actually directly communicates to the etcd server. That might be incorrect but for the purpose of this – [0:17:04.3] CC: I think that’s correct. [0:17:06.8] NL: Okay, good. I was suddenly second guessing myself. The API directly can be considered sort of make the changes. Then the controller manager is in a reconciliation loop, saying like, here’s what I think the world looks like and if the world changes based on what etcd is saying, the controller manager maintains actual state and etcd controls expected states. This is where we want to be. If actual state and expected state are different, the controller manager reconciles that. Either it will delete something or add something to the cluster at large to make sure that that state exists. [0:17:47.6] CC: Based on what’s in the etcd database? [0:17:50.4] NL: Yes, exactly. It will – the controller manager, based on all the many controllers that are just themselves reconciliation nubs, if any of them are you know, different, it will then kick of something to the schedule which will then inform the various nodes in the cluster, what changes they need to do to reconcile state. Those changes occur, control managers sees that actual state matches expected state and everyone’s fat, dumb and happy. [0:18:17.3] CC: We actually didn’t talk much about other container orchestrators other than Kubernetes but I’m wondering because I’m not familiar with any others, but others come to mind, Docker, Swarm and Mesosphere, do they operate in the same way? [0:18:36.7] NL: Josh, I think you had some more experience than I did with at least, I believe it was Mesosphere? [0:18:41.8] JR: No, unfortunately not. [0:18:43.1] NL: I thought – okay, I thought that you had used in your previous life, you’d use at least one other? [0:18:49.0] JR: No, we did some small proof of concepts on Swarm but we never go very far along with it. [0:18:54.1] NL: Yeah, I actually, to be honest, I don’t really know much of the difference between like Rancho Lab, Mesosphere and Docker Swarm. I believe that they all act very similarly to Kubernetes but in slightly different way and this is something that I meant to take a look at before, talking about it but I just ran out of time, I’ll be honest. [0:19:12.8] CC: I guess we’re going to need Part Two to this episode. [0:19:15.7] NL: This is a big topic, we’ll definitely have to come back and kind of launch on this a bit more. I think they’re all orchestration and all these orchestrators work in the same function, right? Or the same fashion. There’s what you want to happen, what actually exists, how do we get that change to occur, right? [0:19:33.8] CC: Was that what you meant, Josh? [0:19:35.4] JR: Yeah, exactly. I think the one thing to add too is the systems are generally making like really informed decisions when trying to reconcile desired state. By really informed decisions, I mean, they’re obviously aware of a lot about the compute resources available to them. One big benefit that adopting container orchestration gives you is things like the scheduler are able to look into the system and understand, hey, based on resources I have available in this area, it would be smarter for me to start more containers over here versus over here, right? When you have these larger complex things and you’re trying to kind of think of all your resources as kind of like a sea of compute. The container orchestration is not only able to get you to a desired state but also to do it in a way that is, at least in most cases, as desirable as possible, right? As far as using resources effectively and a term that we often times throughout there, which is Vin Packing, right? The idea of ensuring that we can know the resources a container needs and pack them together really tightly, so that we’re utilizing the potential hardware or cloud resources that we’re paying for every month. A lot of times, the adoption of container orchestration is this really elegant way to move our workloads around but at the same time, it’s a way to really utilize the things we’re paying for and potentially cut costs over time as well. [0:20:57.5] CC: Yeah, this is one thing that I find fascinating with at least Kubernetes because I haven’t used the other orchestrators. We can boot up let’s say, four machines, and four instances of a machine and deploy Kubernetes on it and tell Kubernetes, “I want these many nodes, these many pods and have this container with apps obviously, or services running in the containers.” I don’t need to specify even where anything’s going to go. It just spreads the load and keeps managing and monitoring and managing what needs to go where to better utilize the instances. [0:21:46.2] NL: I think that’s actually an important distinction between the different container orchestrators that exist out there. If I recall correctly, I believe that Mesosphere has a mechanism that can kind of better load balance your containers that are running in the cluster. At least better than – it can make a kind of a more informed decision on like the state of the cluster and where it took place things than Kubernetes does and that might be one of the key differences between the two. That’s something that I hear a lot in the Kubernetes community. Someone’s like, “I noticed that all of my resources are kind of being put on to one computer and then the rest of them aren’t even being utilized at all, what’s up with that?” I think there’s something there that’s important to understand which is the Vin packing that Josh was talking about. Also, I pointed like that because on my screen, Josh is right next to me but that might not be the case so I might just look like I’m pointing out from the space.vIt’s important to know that from the capacity of at least in Kubernetes and like most of these orchestrators, if there are resources to be utilized, the orchestrator doesn’t care for the most part. Mesosphere has the ability to kind of load balance, as I said but as long as the resources that are available on one computer are the same as any other computer. If one of them is getting like super utilized and the other ones aren’t, it doesn’t really matter, it doesn’t affect the functionality of the cluster at all, right? One meg here and one meg there, essentially the same. [0:23:11.7] CC: What does the orchestrator do when let’s say I have four instances and I have what I have, I stuffed a bunch of consigners in there and I’m thinking, for this instance, this will give me plenty of memory but I have a leaky app and all of a sudden, my RAM blows up. What happens? [0:23:34.1] NL: This actually ties into why I look into an orchestration from a cloud native perspective. This is kind of where, container orchestration is cloud native. It takes into account the elastic nature of your resources. If you have this application that’s blowing up, either you can have limits to how many resources the application can utilize, or you can use auto scaling. In Kubernetes, we have something called Horizontal Plot Auto Scaling and some of the other tools, I’m sure they have the same, but the idea is like, as you’re using more and more resources in the pod, it is taking up this much memory. It then needs to create a new pod, right? Or a new container, right? So a new container needs to get orchestrated and then another one, another one, another one. Now, if you have a really aggressive application that is acting kind of maliciously that’s not great because it will take up all the resources in your cluster and that’s not good. But if you just have a very spiky application, it could grow with its needs and then come back down, and no one has to know about it essentially. Your orchestrator can make that happen for you. I think that is really cool. [0:24:40.9] CC: It is and what if I am reaching the limits of my resources. I mean there are only so many pods that can stuff in four instances or two instances. So what if I am reaching the limits of my resources? What happens then? How is an orchestrator going to help me? [0:24:58.6] JR: Yeah, the nice thing is we can – and most of these orchestrators set some type of parameter around potential CPU that we want to make available in memory, that we want to make available for the app and what is nice about this is at least speaking to Kubernetes, and I am sure it is similar for others, just using some of the underlying technologies that are existent in Linux like Nicholas has mentioned C groups. We have the ability when CPU gets too high to potentially throttle it and slow it down or at least limit the amount of CPU it can use in given cycles and with memory, if we start over committing, we now have the ability to potentially kill the application if it is starting to take up more memory than it actually should be allowed to take up. What’s interesting about Kubernetes and other orchestrators is their self-healing model is that sometimes when apps are doing really bad things, like leaking memory all over the place, you might not detect it right away, right? Because it is actually going to potentially limit or kill the app and self-heal it by bringing it back up. So it might seem like your app is still online and you don’t necessarily realize that under the hood, Kubernetes was actually restarting it and trying to continually bring it to a state of health, right? So you have a lot of abilities. It is like everything that Nicholas just said about reading how much information or resource the app is taking and potentially scaling based on that, or even setting like hard limits to say, “I want to throttle my app or even potentially kill my app if it starts to act badly and use up more than it should.” So it is a really cool kind of declarative way to approach resource limiting. [0:26:29.2] NL: And that is actually something that I don’t think a lot of people including myself work on that much is the throttling aspect, right? Most people are like, “Okay, well whatever. Just take up as many resources as we need.” That’s what it’s there for but maybe you shouldn’t always be doing that. Not every application needs to expand horizontally or vertically, if it’s safe or said. It could be that the application is acting poorly, and they need to be like, “No, you actually don’t need that many resources.” [0:26:56.4] CC: So let us say any or all of these things are happening, throttling and self-healing, how could I know? I mean I am asking this question, but I know the answer. I mean what tools do people actually use to be informed and notified of these events? [0:27:15.9] NL: So this is something I think we are going to get on another episode but just to come breach this into something that – I am also very excited. I am just a very excitable person really, I’m like, people say I’m just like a puppy and they’re not wrong. [0:27:27.1] CC: That’s why you’re here Nic. [0:27:29.0] NL: What? Me? Who said that? Is observation or observability. So monitoring, alerting, inflecting into your cluster to know what is happening, right? So you could, as Josh was saying like under the hood these things could be happening and the orchestrator is reconciling your cluster and your resource utilization for you and you might not know it but if you have observation and you have monitoring going on, you could see like, “Oh hey this pod is like restarting every 20 minutes.” Like it shouldn’t, it doesn’t need to restart every 20 minutes, like clearly the application is still running. So that is not a bad thing but maybe we should fix that, right? So you can be aware of what’s going on, right? [0:28:10.3] CC: And I know that there are tools that provide monitoring and observation but Kubernetes itself doesn’t provide that, right? Those are things that we hook into Kubernetes. [0:28:21.0] NL: Yes. Yeah that is correct because Kubernetes, and like any of these other orchestraters, are doing what they should be doing, which is being the best orchestrator they could. Having like that package now that you are getting into something that is more like a product and there is nothing wrong with products but that is not what these projects are here to be, right? [0:28:40.2] CC: How do you distinguish between the project and the product? [0:28:43.0] NL: Now that is interesting. Josh, you want to take this one? [0:28:45.7] CC: You opened the door. [0:28:47.0] JR: Yeah, I’ll start and then I actually think Nicholas, you might be the best one to speak to this with your background in Open Shift quite frankly, right? So it is kind of like these orchestrators are primitive in a way for how we eventually build a platform and that platform is a larger thing that includes potential monitoring, maybe plugins to continuous integration and continuous delivery. There’s a lot of groups or companies that have kind of that whole story or at least parts of that story, packaged up together, right? I mean we do it at the MWare with some of our enterprise offerings around TKS and then Open Shift, at least in my mind, it does that as well. Maybe Nicholas you can speak to that a little bit? [0:29:27.3] NL: Yeah, so from an Open Shift perspective at least when I was using it, it was trying to be everything you would need to monitor, or to not monitor, but to run a container orchestration system, right? So it has a Docker registry built it. It has monitoring built it. It has some rudimentary charge built in, Ingress, all of these things that don’t necessarily come with Kubernetes like the option Kubernetes. It has a solution around that. And I think that is the difference between like project or just an orchestrator and a product. A product is trying to solve a grander enterprise problem versus a project or in this case, an orchestrator, is going to solve one problem and that problem is how do I get these containers to run in a way that my customers – not my customers really, my users expect them to run. [0:30:18.3] CC: Yeah, fair enough. [0:30:19.5] NL: And what do you think on the topic, Carlisia? [0:30:22.0] CC: Oh it sounds an awful lot to me like a product is you get money for it and the projects you don’t. [0:30:28.1] NL: That is actually very – you’re right, honestly that is really the main distinction. One of them is money based. [0:30:34.6] CC: But your description, the descriptions you make for it are very valid – it is very valid because a project by itself may not have enough value for let’s say companies and bundling this project with that project and the other project, which ultimately you’re building the product with a purpose, right? You will have a purpose with that product to have a specific audience for their product set of users. So it is very distinct from taking one part of that product and calling it a product because maybe it is not enough to address and solve problems. [0:31:20.3] JR: Yeah, I think that is an important distinction. It is almost like what Nicholas and I were talking about was more about the distinction between what an orchestrator is and what a full platform would be, right? And I think to Carlisia’s point about how we plug in the monitoring and stuff is really important because just like we were talking about with the cloud native landscape in our last podcast, Kubernetes is just one piece of the overall puzzle. Kubernetes isn’t your whole platform start to finish, right? It is just the container orchestration portion and you have a lot to build and hook into that to make it a full platform that your company might be onboarding developer workloads onto it. It is just really one piece of that overall puzzle. [0:32:01.0] CC: That is beautifully put Josh. [0:32:02.9] NL: Yeah, very nicely put. So I’ve got a question for you guys. We’ve been beating around the bush as it were but to me, it seems apparent that in the world of container orchestration, Kubernetes has come out on top. That isn’t to say that it’s the end, right? There could be something that comes out that actually beats Kubernetes, right? But for now, it seems like everyone is looking at Kubernetes and I am curious why it is that you think that – you all might think that Kubernetes took the top space. [0:32:32.7] CC: I am scratching my chin. [0:32:35.1] NL: Scratching chin emoji. [0:32:38.3] JR: Exactly, one thing for sure is I just think Kubernetes did the community thing really, really well and not that it is all about community. It is obviously about technical choices and things of that nature but I think they did, not to say they’re perfect, but they did a really good job of being very inclusive and getting people to join this community and give feedback and the structure of the special interest groups where people get together and focus on various areas of Kubernetes, like scheduling or cluster life cycle and things like that. And it is interesting because the community just grew so quickly in my mind, that it just made this massive push into the market because there were so many humans behind it pushing it along. So I think at least among other things, community was one of the biggest. [0:33:24.0] CC: I can’t say that I was paying attention in monitoring that space so I don’t know. Of course, I can make guesses, what Josh just said sounds very plausible that he had Google behind it. I am sure it didn’t hurt. Not that we need to be fan boys and fan girls of Google but having a company like that sponsor and put resources behind the project gives a signal that “Okay, this is going to be here for a while.” Even though Google has a reputation of discontinuing things, but at the same time, I think that is significant. What else? Definitely the community. I didn’t follow the community from the beginning so only this last year and something, almost two years that I have been working with Velero, that I get to see how the community is and it’s amazing. It’s crazy, so organized. Yeah and it is not perfect, nothing is perfect but it’s incredible. The enthusiasm and the organization and the transparency, it is amazing. [0:34:36.6] NL: Yeah, absolutely and I agree with actually both of your points. It’s corporate sponsorship not just Google I mean, I’ll get to this in a second and the community as well and also some of the functionality. But it was both the corporate sponsorship of Google and Red Hat in the early days and not to tap my old you know, “Yeah we did it.” But it Red Hat had a big play into early Kubernetes as a supporter and so what that did is establish, “Hey, Kubernetes is at least enterprised.” An enterprise perspective project, right? It is not just, “Hey, this is some open source project. It may or may not work. If it doesn’t, you are on your own.” If you had a company like Google and Red Hat who are both endorsing this project, suddenly enterprises were more interested in taking it onboard, like it was more of a viable concept. [0:35:29.4] CC: I’m glad you are here Nic to correct me and make that addition. [0:35:34.4] NL: Oh well, yeah I was not correcting you at all. I think – [0:35:37.2] CC: No because I didn’t clue into the fact that – I mean I see Red Hat all over the place but I don’t know the dimension of involvement that they had from the beginning, because at the beginning, I was an outsider to all of this. [0:35:50.8] NL: Yeah, so for perspective, Open Shift 300, which is when I first started getting into it, is based on Kubernetes 1-2, which is pretty early. They were big like they put a lot of resources into the development of the community and for the development of the functionality that exists, right? The horizontal pod auto-scale that we still use today is due in the large part to the contributions of Red Hat, right? The engineering at Red Hat is responsible for that piece, among other things. And so with them at play, kind of getting their community and Google’s community coming together and then able to organize this community that I think is a big piece of what took this off or what allowed Kubernetes to take off. That is how grammar works. There is also some pieces of functionality that I think were novel to Kubernetes in the early days, things like Ingres. The way the Kubelet worked was actually kind of unique, like how low level the commands that are being issued by the Kubelet were pretty unique. And so it allowed for people to adopt it like the things that were happening from the Kubelet perspective like changes to your IP tables, running a container, changing the C groups and all of these things, those are all well known by people at the time and so there wasn’t anything like arcane happening. It was just, “Hey, this process just runs these commands and that is how it reconciles say, right? And so I think that that kind of functionality really got people to trust what was happening. And so, you know it’s like I think the trust and transparency are the big things that people keyed into. The trust comes from the enterprise sponsorship, and also the fact that what was happening from a rudimentary standpoint was pretty simple and so people could wrap their heads around it and then transparency was having this community. Everything happens in the open, everything is recorded and accessible by everyone, right? It wasn’t just like some behind the scenes things happened. [0:37:50.7] JR: Yeah and I think that piece is super important, like Nicholas and I, we came from Coreless or our lineage around like open source Kubernetes is not too dissimilar. We spend a lot of time working with customers in pure upstream open source Kubernetes and actually taking some of their issues and requirements to the community and then helping shape the direction of Kubernetes in micro kind of ways, but still important ways to that company. And I think companies seeing through the CNCF and seeing through just community leadership and involvement that the things that they care about aren’t just going through a single vendor to make a decision as to whether that thing should be included, but it is being part of a larger community discussion, breeds a lot of confidence in this project in the long term. I think at the end of the day, we started with there will be container orchestrator that many of us use. Or maybe there will be a couple, right? There is no question, we need to solve container orchestration as an overall problem and companies are at this point where they are still placing a bet on what they want to use and because of the community, because of the involvement, because of the ability to adopt the project to potential business requirements, I feel like more large and small medium organizations are willing to put their money on Kubernetes as a whole. And I don’t think they felt as confident finding some other projects, like Open Stack and then historical Masos perhaps. I am just projecting based on conversations I’ve had but that is why I think a lot of folks are really excited about the future for Kubernetes. [0:39:21.3] NL: Yeah that is an excellent point. [0:39:23.0] CC: Let’s stick with the theme of projecting in the future and we are going to have to wrap up soon otherwise it is going to be a two hour, I mean this could be a two-hour show. But let’s not make our audience go through that. We’ll have part two. What about, we talk all the time, and people who are in this area, we talk about all the time how everybody knows Kubernetes and da-da-da, but I want to challenge you two, do you think that everybody knows Kubernetes? Everybody knows the purpose of Kubernetes, everybody knows if they should be using Kubernetes or not, how are people able to make an informed decision if they should be using Kubernetes? Because I don’t think everybody knows Kubernetes. I think the majority of companies, in terms of volume, because smaller companies I would guess they outnumber the bigger companies and technologists – I think a lot of people are not clear on what this is. That’s why we are here but what do we tell them? We have to have an episode to discover that, now that I am thinking about it, but we could wrap this up with some seed ideas for that. [0:40:46.9] NL: So that is a great idea and something that I’ve been playing around with introducing myself, is when do you not use container orchestration, right? Just because container orchestration exists doesn’t mean necessarily – [0:40:58.0] CC: If you don’t have containers. [0:40:59.1] NL: Yeah, one, if you don’t have containers. That is another starter. [0:41:02.5] CC: It is a real legit thing to say because some people ask me, “Should I start with Kubernetes or containers?” that’s the level of education that we must provide. [0:41:15.5] NL: Yeah, absolutely and that is something we actually run into a lot in the field is when we are engaging with our customers, part of our job is to help containerize their applications if they are not already there. Trying to help them do that in a logical manner. But for instance, to give an example, my fiancé’s company uses Docker, but they don’t use Kubernetes or any kind of orchestration because they don’t need to. Like the amount of the resources that they are going to be using and the amount of and the type of work that they are doing, it doesn’t make sense to use an orchestrator. I have actually talked to some of the engineers about it because they were like, “Oh tell me about this Kubernetes thing” and I’m like, “This is what it is” blah-blah-blah. I finally came up with a metaphor where it’s like your company uses the containers as a shovel. If we brought it into like, let us say we’re ploughing a field, right? You’ve got a plow, if you already use Kubernetes that would be like trying to plow the field with a nuclear bomb. It is way more complicated than you need to do. Sure, you can clear a lot of land with a giant bomb but that is way more than you guys need, right? And I think that for me that’s the drawing line. It is like if the complexity makes sense for you to do like, if you’re trying to all of a sudden, establish a farm. Not to say that you should use a bomb to plow land but hey, if you need to clear a lot of land a bomb can work, right? That is a terrible metaphor, I am sorry. That went off the rails really fast. [0:42:41.3] CC: It wasn’t too bad. [0:42:43.8] NL: I actually think that. [0:42:46.7] JR: I think, one thing that I will say and this is coming from experience working with organizations is let’s assume that you have justified Kubernetes for yourself, and by the way, I super echo everything that Nicholas just said, you have to be really careful and determine do you actually need to take this thing on? Because it is so hard to do in a lot of ways, right? But let us assume you have taken it on. I think an interesting thing to have empathy about as often times infrastructure dev ops people is you might know Kubernetes really, really well. But that doesn’t mean your thousands and thousands of developers have any idea what Kubernetes is at all and that is a massive disconnect we see in organizations all the time where they are trying to onboard folks onto Kubernetes, and they haven’t fully abstracted Kubernetes away, which some companies do and that could be a really good pattern too. Like developers deploy their apps, they don’t even know Kubernetes are running them under the hood. That is a really neat pattern as well. But assuming they are just trying to bring developers onto Kubernetes, they don’t really have the same amount of empathy for them and they just think like, “This should be really easy. It is just a bunch of yemel files, you’ll figure it out,” but they totally forget about all of the complexities that they originally learned about. Like how does pod to pod networking work and things like that. I just think that to your question Carlisia, it is interesting because one massive group in a company can know a lot about Kubernetes and forget what it was like to learn how something like Kubernetes or container orchestration worked. I think a lot of that is bridging the gap and really having some amount of education to bring everyone up to speed, even in the same organization. [0:44:21.2] CC: I am dying to have an episode on just that alone because it is quite challenging. When you are faced with Kubernetes, I mean the very first thing is that there are terminologies that you haven’t seen before and they’re like, “How does that map to what I already know?” and then sometimes it doesn’t map. It is completely new so. [0:44:43.1] JR: Yeah and when the benefits aren’t super obvious to you, it is really hard to get bought in and be willing to invest your own time and energy into it, right? And we forget that it is just not super obvious why Kubernetes makes sense for a lot of folks. [0:44:56.6] NL: Yeah, absolutely. That is a good point that even I sometimes forget like when someone says, “Well, why would I want Kubernetes?” I’m like, “Why wouldn’t you want Kubernetes?” like duh, it works so well in my brain why don’t you get it? But it is good to take a step back out of yourself and you know, be empathetic to the people you’re talking about in the community. I think Carlisia, you mentioned that we should be wrapping this up pretty soon and I think I totally agree. Before we go, I want to say if you want to contribute to any container orchestration about Kubernetes in specific since that is the one we want to work with the most, we totally encourage you to start contributing to these projects. Like with Kubernetes, we have the Kubernetes-Kubernetes Repo that has a lot of information on how to start contributing. I believe that Mesosphere has their own repos and the information online available for them. And I don’t know, I am not sure if there is much in a way of Docker or Swarm anymore that you can contribute to. I am not sure, but for Kubernetes, we have the Kubernetes-Kubernetes Repo and the Kubernetes Slack channel K8S at slack.k8s.io. Please join us and start talking about your container orchestration journey. [0:46:08.6] CC: And Kates by the way is K8S and I am going to say that because at some events and some people were up in the stage and they’re like, “Kates this, Kates that” and I am sitting with someone in the back and I’m like, “Who’s Kate?” [0:46:24.3] NL: Or I have seen people who are like, “K-eight-S” is the acronym and what that means is that there is eight letters between K and S in Kubernetes. That is all that means. I have seen some people do K8 and it drives me up every wall. I actually start constructing walls and it continues to drive me up them. I am in an infinite regression of walls. [0:46:44.6] CC: All right everybody, thank you for listening. It’s great that you are here, and we are going to be back with more cloud native goodness. [0:46:53.8] NL: Yeah, absolutely. All right, cheers. [0:46:56.0] JR: Thanks. [0:46:56.8] CC: Goodbye. [END OF INTERVIEW] [0:46:58.7] ANNOUNCER: Thank you for listening to the Podlets Cloud Native Podcast. Find us on Twitter @thepodlets and on the Podlets.io website where you will find transcripts and show notes. We’ll be back next week. Stay tuned by subscribing. [END] [0:02:36.0] CC: I meditate too, it’s great. [0:02:38.2] NL: Yeah, it’s good. All right, anything interesting in the cloud native space that you guys have found in the last week? [0:02:43.6] CC: I have a talk that was accepted for KubeCon China. [0:02:47.4] NL: Awesome, congratulations. [0:02:49.6] JR: Congrats. [0:02:50.6] CC: Yeah, it’s a joint talk with Steven Wong also from Thea Moore. We’re going to talk about data recovery, data protection, recovery, migration in Velero. [0:03:03.9] NL: That’s great. He’s been coming to the Cloud Native Social Hour pretty regularly. That’s awesome to see some more cross interaction. [0:03:11.6] CC: Yeah, he is awesome, so knowledgeable. [0:03:14.0] NL: Great. And Josh? [0:03:15.5] JR: Very cool. I was actually looking this week since I’m in kind of the Kubernetes mindset, for something that can kind of add a TTL to any Kubernetes resource. So think of something like a service account in Kubernetes and I want to attach a TTL to it such that in four hours, it effectively got swept up and is no longer existent in the system. There’s some interesting ways that actually Kube ADM, one of the bootstrapping tools, does this. I was trying to kind of replicate that for their tokens, there’s a project by one of these Landau folks. Jacobs, I don’t know if that’s his last of first name, sorry in advance for butchering it, but he’s got a project called Kube Janitor that does effectively that. With annotations, you can put a TTL on them, your resources and then Kube Janitor will just come through and sweep that up. Which I thought a really cool idea. That was an interesting thing that I saw, it’s no new news, I think it’s been around for a while but it’s the first time that I had run into it. [0:04:07.6] NL: Nice. For me, our cohost Duffy, turned me on to a tool called Chaos Blade. Recently, I’ve been getting more and more into Chaos engineering and this is apparently an easy to use Chaos engineering toolkit. Something I’ve only just started looking at but I’m pretty excited. I’ll probably play around with that a bit more. [0:04:25.2] JR: Cool, awesome. [0:04:26.9] NL: Yeah, this week on the podcast, we are talking about container orchestration and kind of what that is, right? For me, container orchestration is the idea that you need your workloads to run somewhere but you don’t necessarily need to care where they’re running and the way that this has been done traditionally, prior to container orchestration, was like scheduling VM’s or making sure these processes run on certain computers, right? There’s a lot of automation around that like, when containers came around, we needed some way to make sure that they’re running and it also enabled us to not need to care so much about how things get started in all that. Everything was kind of packaged in a container I think. They need to just be some way to run them. That’s kind of where container orchestration came in, is that kind of your guys’ take on that as well? [0:05:18.3] CC: Yeah, basically, when we say we are orchestrating containers, we basically tell them how to behave, right? For example, I have this container here and I’m going to declare that if it fails, I want it to come back up in this container over there, if you fail just keep that state, don’t do anything and then I might say hey, I want two of you, three of you, I want to – the orchestration part is really just dictating behavior and state. [0:05:48.6] NL: Yeah, absolutely. [0:05:49.9] JR: Yeah. I think one interesting thing that came with the advent of containers is, we used to have this notion of you know, what server is my application going to land on or then eventually, you know, what virtual machine is my app eventually going to land on and we think kind of in this units of virtual machines and the paradigm shift a bit, at least in my experience has been now that you have the container unit and you can run many of those on one virtual machine, right? Your concern about orchestration is not just putting it on machine A and putting it on machine B but it’s kind of like packing multiple of this containers, perhaps on the same virtual machine or same host. The orchestration notion is beyond just the conventional system construct of a different host each time, it’s really interesting. [0:06:34.0] NL: Yeah, I think it might be important for us actually to take a step back. I realized I kind of jumped right into it, but we should probably settle what a container is, right? Before we can talk about how we can orchestrate them. A container is basically just a tar ball honestly. That is a packaged application with the instructions for it to run on any system that can accept that tar ball. Containers are broken down into a couple of Linux constructs, C groups and name space, so C groups four, making sure the process runs in its own dedicated memory and then or just like isolated memory. Then name spaces for things like network isolation. So that the network traffic that’s going on in the container doesn’t cross over to other processes. Very controlled process initiation based on these instruction. That’s kind of what a container is, a lot of people think that they’re like, kind of like a VM, I’ve heard that a few times where like, “Oh how do I deploy it?” What’s the VMDK for a container? It’s just a process that runs on a computer in a very controlled fashion, that’s literally it. [0:07:43.9] JR: Yeah, it’s kind of interesting to think like, at what point in which we kind of started using containers and seeing containers. I’d be curious for either two of you, Carlisia especially, what was your first exposure to the unit of a container and why were you starting to consider using a container versus just a virtual machine or a process? [0:08:03.0] CC: Frankly, I don’t remember. My first time seeing a container has been a long time but I don’t remember. But probably maybe trying to do some application like some toy application that – an example application. I remember that I was working on an application that we had the option to stuff it into a container as well, but I personally didn’t make the development. I wasn’t using it for development. My first usage of container really was about three years ago when I was working for CDN and a CDN as you might imagine has many different parts, so it has very low-level software running to higher level software, right? Really, sometimes, well, not sometimes, it has kernel level applications in systems, and it has API level system. For you to develop one part of it is it was really handy to be able to stuff our different systems into containers and have containers stuck to each other. We weren’t using the introduction. This was for development, but it was amazing, it was fantastic, we would have applications developed and go. Different systems that needed to talk to each other and we would have applications in C and I think that is to remember but it was amazing. Everything in containers and then we have a tool as well, they were sort of like Kubernetes, it wasn’t Kubernetes. It was developed in house. That orchestrated all of these things and you know, we simply failed, bringing back up and did a bunch of other things as well. I cannot explain the difference of working like that. It’s so much faster and so I could be a lot more autonomous, being able to run everything myself. I didn’t depend on having access to its server. I ran everything on my laptop, it was fantastic. [0:10:17.6] NL: Awesome. The first time I ran into a container was back when I was working for Red Hat, right when Open Shift Three CEO came out, that’s when Open Shift kind of moved from the in-house version of Open Shift to adopting Kubernetes. I had been working mostly in the virtualization like infrastructure world like doing a Red Hat enterprise virtualization manager, which is kind of like a Red Hat take on B Sphere, you know, kind of. I was very used to virtualization and spinning things up. There is some aspects of creating a VM and creating a container that were very similar. It took me awhile for my brain to click. Once I started using open chip to kind of click into like, “Oh this is how they’re different, right?” Whereas, if you’ve just started looking at it, “Well what’s kind of the difference?” They’re all just like, in my command line, they all just come up as like lists of units, right? This is a processing unit, that’s a processing unit right there. They’re kind of similar but once you start really getting into the use of it, it was so much different. I had heard like during this pr

KUDO is the Kubernetes Universal Declarative Operator, a toolkit for writing operators for Kubernetes. Gerred Dillon works on KUDO at D2IQ, formerly Mesosphere, and joins Craig and Adam to discuss KUDO, how Mesos frameworks relate to Kubernetes operators, and taking care of chickens. 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 Little Free Libraries Top moments of 50 years of the Internet by Vint Cert Television network news in NZ 50 years old History of TV in NZ News of the week Sysdig container usage report Longhorn donates to the CNCF Crossplane 0.4 Helm v3.0.0-rc.2 Episode 11 with Vic Iglesias CloudEvents reaches 1.0 Data Center Knowledge: What service meshes are, and why Istio is leading the pack Backyards 1.0 Contour 1.0 Envoy 1.12 New encryption options for Google Kubernetes Engine Azure services now run anywhere with new hybrid capabilities: Announcing Azure Arc ZDNet and TechCrunch coverage Brendan Burns’ explainer videos CNCF news: AlphaSense case study TiKV on building a distributed storage system CNCF meetup program SIG Docs survey results Better Kubernetes networking with Knative by Ahmet Alp Balkan Episode 66, with Luk Burchard and Ahmet Alp Balkan Why you don’t have to be afraid of Kubernetes by Scott McCarty Brad Childs has passed away Links from the interview D2IQ (formerly Mesosphere) Apache Mesos Mesos frameworks Marathon DC/OS DC/OS Commons KUDO Controllers Operator pattern Kubebuilder Operator SDK Omakase: Japanese for “I will leave that up to you” Tasks Getting started with KUDO Metacontroller Proposal to move under Kubebuilder Vitess operator Tekton Helm D2IQ’s Konvoy distribution of Kubernetes Operators using KUDO: Kafka Cassandra Spark OpenEBS operator Lightbend templates for Akka KUDO proposed to the CNCF CNCF SIG Application Delivery Gerred’s KUDO webinar for the CNCF Contributing to KUDO KUDO Slack Gerred’s bio Dry brining a chicken Gerred Dillon on GitHub

SHOW: 412DESCRIPTION: Brian talks with Brandon Whichard (@bwhichard, Co-Host of Software Defined Talk podcast) about the tech/cloud trends that have shaped the first half of 2019.SHOW SPONSOR LINKS:Digital Ocean HomepageGet Started Now and Get a free $50 Credit on Digital OceanDatadog Homepage - Modern Monitoring and AnalyticsTry Datadog yourself by starting a free, 14-day trial today. Listeners of this podcast will also receive a free Datadog T-shirt[FREE] Try an IT Pro ChallengeGet 20% off VelocityConf passes using discount code CLOUDCLOUD NEWS OF THE WEEK:VMware announces Project Pacific - unified vSphere and KubernetesVMware announced "Tanzu" multi-cloud Kubernetes management framework SHOW INTERVIEW LINKS:Software Defined Talk PodcastSHOW NOTES:Topic 1 - Welcome to the show. I’ve been listening to your show, Software Defined Talk, for quite a while. Tell us about your show, your co-hosts and the types of things you discuss on the show?Topic 2 - What are some of the biggest trends you’ve seen (or been discussing) so far in 2019? Anything really surprise you?Big IPOs in 2019 - AirBnB, Uber, Lyft, Pinterest, WeWork, Zoom, etc. - the GigEconomyThe rise of Kubernetes, the decline of Cloud FoundryPivotal getting acquired -- Mesosphere now D2IQ going KubernetesDocker gets a new CEOOSS licensing warsVMware seems to be acquiring a new company every weekVMware + Heptio + Pivotal + Bitnami= ?VMware now has a managed offering in AWS, Azure, IBM Cloud, GCP, AlibabaTopic 3 - AWS has continued to be the leading public cloud for a decade now. Do you see anything slowing AWS down?Topic 4 - There were lots of articles earlier in the year about big public cloud contracts between web companies and the public cloud (hundreds of millions in cloud spending). Many of those companies are now struggling as they have gone IPO. If they struggle to make revenue (and subsequently their cloud payments), do you see this having any effect on sentiment about public cloud? Topic 5 - There is starting to be some noise in the news and the markets about a potential economic slowdown. How much do you think about what that might mean to the tech industry, and subsequently buyers and users of tech? Sometimes in slower times, we see the creativity of new tech emerge (2001 - mass websites; 2007/8 - AWS and iPhone, 2019/2020 - ??)FEEDBACK?Email: show at thecloudcast dot netTwitter: @thecloudcastnet and @ServerlessCast

Renaming to align with kunernetes and JEDI master Trump. Buy Coté’s book dirt cheap (https://leanpub.com/digitalwtf/c/sdt)! And check out his other book that this guy likes (https://www.linkedin.com/feed/update/urn:li:activity:6559881947412340736/). Mood board: Have either of you ever eaten dog meat? He easily slides into meataterian. Skype would be terrible if it weren’t so great! Follow the foot-stones Going up the well I like dogs, what I don’t like is additional responsibility. My life is mostly avoiding more responsibility Sorry about your dog… Oyster and Opals. Dogs and trains Once you get to Atlanta, trains be like, fuck that shit. I’m going to write that down and look at it when I’m depressed. Who put kubernetes in my Mesosphere? Not investment advice. 2 to 3 yards of J2EE books. If you put it into a container, you’ll probably be OK. Relevant to your interests Mesosphere changes name to D2IQ, shifts focus to Kubernetes, cloud native (https://techcrunch.com/2019/08/05/mesosphere-changes-name-to-d2iq-shifts-focus-to-kubernetes-cloud-native/) IBM fuses its software with Red Hat’s to launch hybrid-cloud juggernaut (https://www.networkworld.com/article/3429596/ibm-fuses-its-software-with-red-hats-to-launch-hybrid-cloud-juggernaut.html#tk.rss_all) After Trump cites Amazon concerns, Pentagon reexamines $10 billion JEDI cloud contract process (https://www.washingtonpost.com/business/2019/08/01/after-trump-cites-amazon-concerns-pentagon-re-examines-billion-jedi-cloud-contract-process/) Your multicloud strategy is all wrong (https://www.infoworld.com/article/3428682/your-multicloud-strategy-is-all-wrong.html) A Technical Analysis of the Capital One Hack (https://blog.cloudsploit.com/a-technical-analysis-of-the-capital-one-hack-a9b43d7c8aea?gi=85e88964a741) Dynatrace S-1 Analysis — Tracing a Transition (https://medium.com/memory-leak/dynatrace-s-1-analysis-tracing-a-transition-3c92896e8d29) NetApp Stock Is Tumbling After the Company Warned That Tech Spending Was Slowing (https://www.barrons.com/articles/netapp-stock-tumbles-after-warning-of-slowing-tech-spending-51564761782) Will Uber ever make money? Day of reckoning looms for ride-sharing firm (https://www.theguardian.com/technology/2019/aug/04/uber-ride-share-lyft-ipo-earnings) It’s the end of the big-data era: HPE to acquire MapR’s assets (https://siliconangle.com/2019/08/05/end-big-data-era-hpe-acquire-maprs-assets/) Microsoft launches Azure Security Lab, expands bug bounty rewards (https://www.zdnet.com/article/microsoft-announces-azure-security-lab-azure-bug-bounty-expansion/) Nonsense Alabama teen wins PowerPoint World Championship (https://www.al.com/news/huntsville/2019/08/alabama-teen-wins-powerpoint-world-championship.html) Airlines are finally fixing the middle seat (https://www.fastcompany.com/90377949/airlines-are-finally-fixing-the-middle-seat) Why is called an Oyster Card? (https://en.wikipedia.org/wiki/Oyster_card) Sponsors SolarWinds Papertrail (https://papertrailapp.com/?utm_source=podcast&utm_medium=direct-link&utm_campaign=sdt) TrackJS (https://trackjs.com/sdt/) Conferences, et. al. August 12th to 15th - Cloudbees DevOps World and Jenkins World (https://www.cloudbees.com/devops-world/san-francisco), San Francisco - use the code GOLOCAL for a discount. Also in Lisbon, Dec 3rd to 5th (https://www.cloudbees.com/devops-world/lisbon). August 30th - Agile Scotland, Glasgow (https://www.agilescotland.com/august) - Coté giving 90 minute workshop (https://www.agilescotland.com/august#comp-jwjlafj0__item1inlineContent-gridWrapper). Use the code AS-SPEAKER-MICHAEL for a discount: from £70 to £56.13. Sep 26th to 27th - DevOpsDays London (https://devopsdays.org/events/2019-london/welcome/) - Coté at the Pivotal table, come get free shit. Oct 7th to 10th - SpringOne Platform, Oct 7th to 10th, Austin Texas (https://springoneplatform.io/) - get $200 off registration before August 20th, and $200 more if you use the code S1P200_Coté (make sure to use the accented e). Come to the EMEA party (https://connect.pivotal.io/EMEA-Cocktail-Reception-S1P-2019.html) if you’re in EMEA. Oct 9th to 10th - Cloud Expo Asia (https://www.cloudexpoasia.com/) Singapore, Oct 9th and 10th Oct 10th to 11th - DevOpsDays Sydney 2019 (http://devopsdays.org/events/2019-sydney/), October 10th and 11th December - 2019, a city near you: The 2019 SpringOne Tours are posted (http://springonetour.io/): Toronto Dec 2nd and 3rd (https://springonetour.io/2019/toronto), São Paulo Dec 11th and 12th (https://springonetour.io/2019/sao-paulo). December 12-13 2019 - Kubernetes Summit Sydney (https://events.linuxfoundation.org/events/kubernetes-summit-sydney-2019/) SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/) or LinkedIn (https://www.linkedin.com/company/software-defined-talk/) Listen to the Software Defined Interviews Podcast (https://www.softwaredefinedinterviews.com/). Check out the back catalog (http://cote.coffee/howtotech/). Brandon built the Quick Concall iPhone App (https://itunes.apple.com/us/app/quick-concall/id1399948033?mt=8) and he wants you to buy it for $0.99. Use the code SDT to get $20 off Coté’s book, (https://leanpub.com/digitalwtf/c/sdt) Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Recommendations Brandon: Hard Knocks (https://www.hbo.com/hard-knocks) and Last Chance U (https://www.netflix.com/title/80091742). Matt: Tim Hecker: An Imaginary Country (https://www.youtube.com/watch?v=HuXxwXWPz2Y). Coté: Slouching Towards Bethlehem (https://www.goodreads.com/book/show/424.Slouching_Towards_Bethlehem), Joan Didion. Outro: “Depreston,” (http://youtube.com/watch?v=1NVOawOXxSA) Courtney Barnett.

Conversation with Dayna Rothman, the author of “Lead Generation for Dummies,” the VP of Marketing at Mesosphere, and she's a subject matter expert at revenue-driven demand generation and content

Amelia explains how best to manage agency & contract recruiters to ensure great candidate experience, how recruiters should think about specialization, and how to assess talent for remote work.

There’s lots of monitoring and systems management M&A and funding this week, so we talk about the cycle of systems management companies. It seems like Atlassian is starting up and operations product line with the OpsGeniue acquisition, and PagerDuty has a whopping valuation at $1.3bn. With rumors that Adobe might buy Marketo, Coté recounts the RIA days and how Adobe ended up doing a good job surviving, despite RIA Relevant to your interests Americano coffee vs long black (http://coffeeofday.com/coffee-answers/americano-vs-long-black/). “Mo’ digital, mo’ problems” - With Emerging Technology Comes Emerging Data Problems (https://www.cmswire.com/information-management/with-emerging-technology-comes-emerging-data-problems/?utm_source=cmswire.com&utm_medium=web-rss&utm_campaign=cm&utm_content=all-articles-rss) Enterprise hits and misses - blockchain is a paradox; AI is a customer service automater (https://diginomica.com/2018/09/06/enterprise-hits-and-misses-blockchain-is-a-paradox-ai-is-a-customer-service-automater/) Oracle president Thomas Kurian is taking time away from the company (https://www.cnbc.com/2018/09/05/oracle-president-thomas-kurian-taking-time-off.html) New Cloud Unicorn: PagerDuty Scores $1.3 Billion Valuation In $90 Million Round (https://www.forbes.com/sites/alexkonrad/2018/09/06/pagerduty-funding-billion-dollar-valuation/#2fcdfb4c411d) Atlassian to pay $295M for Boston-based OpsGenie (https://www-bizjournals-com.cdn.ampproject.org/c/s/www.bizjournals.com/boston/news/2018/09/05/atlassian-to-pay-295m-for-boston-based-opsgenie.amp.html) Nancy Gohring and co analyze the deal (https://clients.451research.com/reportaction/95616/Toc). No, Operations Isn’t Going Anywhere, But it's Going to Look Different (https://www.enterprisetech.com/2018/09/05/no-operations-isnt-going-anywhere-but-its-going-to-look-different/): “The work of operations is changing and the skills required to do that work are changing. The platforms and tools involved are evolving (but don't forget the decades of legacy code that isn't!). Organizational silos are breaking down, and developers and operators are co-mingling as peer engineers.” Jenkins: Shifting Gears (https://jenkins.io/blog/2018/08/31/shifting-gears/) - Coté: recently, I don’t think I’ve heard any one say “yay! Jenkins!” What’s the deal with it? Is Jenkins now bad? Vapor IO Raises PE Funding, Buys Out Nascent Edge Colocation Business from Crown Castle (https://www.datacenterknowledge.com/vapor-io/vapor-io-raises-pe-funding-buys-out-nascent-edge-colocation-business-crown-castle) In a Few Days, Credit Freezes Will Be Fee-Free (https://krebsonsecurity.com/2018/09/in-a-few-days-credit-freezes-will-be-fee-free/) Adobe in talks to buy marketing software firm Marketo - sources (https://www.reuters.com/article/us-marketo-m-a-adobe-systems-exclusive/exclusive-adobe-in-talks-to-buy-marketing-software-firm-marketo-sources-idUSKCN1LT0EK) “Adobe, which has a market capitalization of $130 billion, has topped analysts’ profit and revenue estimates for the past eight quarters, driven by strength in its digital media business, which houses its flagship product Creative Cloud.” Johnny Leadgen is interested. Adobe really pulled off a successful strategy. Geoffrey More’s systems of interaction (‘member that?), some CMS/marketing analytics engines, and then moving CS to SaaS. Pretty amazing, considering all the other road-kill out there. Verizon, AT&T, T-Mobile and Sprint team up to kill passwords (https://www.fiercewireless.com/tech/verizon-at-t-t-mobile-and-sprint-team-up-to-kill-passwords) Sysdig raises $68.5 million to boost security and performance for containers and cloud-native apps (https://venturebeat.com/2018/09/12/sysdig-raises-68-5-million-to-boost-security-and-performance-for-containers-and-cloud-native-apps/) Packet Raises $25M Series B, Starts Deployment of Edge Computing Cloud (https://www.datacenterknowledge.com/startups/packet-raises-25m-series-b-starts-deployment-edge-computing-cloud) What Is the Point of Mozilla? (https://www.linuxjournal.com/content/what-point-mozilla) - “in 2016 various deals with search engines brought in an astonishing $520 million.” Linus Torvalds taking break (https://lore.kernel.org/lkml/CA+55aFy+Hv9O5citAawS+mVZO+ywCKd9NQ2wxUmGsz9ZJzqgJQ@mail.gmail.com/) Google is killing Fabric in mid-2019, pushes developers to Firebase (https://venturebeat.com/2018/09/14/google-is-killing-fabric-in-mid-2019-pushes-developers-to-firebase/?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) Path is shutting down (https://path.com/about?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) Mesosphere revenue, new CEO, etc. (https://mesosphere.com/blog/a-new-chapter-for-mesosphere/) - “Last year in Q4 we issued news about hitting a $50m+ run rate and this year’s Q2 marks our biggest quarter ever, beating our numbers over the last 14 quarters. In fact, according to a recent report from Inc, we are the third fastest-growing software company in the U.S. with a revenue growth of 7,507 percent.” Slow down, Pony Boy! You could round that 7 off the growth percent. Google making private cloud stuff (https://www.ciodive.com/news/the-information-google-to-take-on-microsoft-with-cloud-capabilities-for-on/532526/): ‘Google is responding to enterprise computing needs by making custom-designed computers to run in organizations' own data centers, reports The Information. The computers include server, storage and networking functions specifically for "a handful of large customers," according to two sources close to the project in the report.’ Wut. Sponsored by DataDog This episode is sponsored by Datadog and this week Datadog wants you to know about Watchdog. Watchdog automatically detects performance problems in your applications without any manual setup or configuration. By continuously examining application performance data, it identifies anomalies, like a sudden spike in hit rate, that could otherwise have remained invisible. Once an anomaly is detected, Watchdog provides you with all the relevant information you need to get to the root cause faster, such as stack traces, error messages, and related issues from the same timeframe. Sign up for a free trial (https://www.datadog.com/softwaredefinedtalk) today at https://www.datadog.com/softwaredefinedtalk and tell them your friends at Software Defined Talk sent you. Conferences, et. al. Coté isn’t going to see his family until Christmas. GRIND AND STACK. Sep 24th to 27th - SpringOne Platform (https://springoneplatform.io/), in DC/Maryland (crabs!) get $200 off registration with the code S1P200_Cote. Also, check out the Spring One Tour - coming to a city near you (https://springonetour.io/)! Oct 1st to 2nd - New Relic (aka “Not Datadog”) FutureStack London (https://newrelic.com/futurestack/london), Coté on a partner panel on Oct 1st, also, come see The Governor (https://twitter.com/monkchips) in action at FutureStack on the 2nd. Oct 2nd, London! Coté talking metrics at the NO NAME Pivotal Meetup (https://connect.pivotal.io/london-meetup-oct18.html). Oct 4th - ITQ Transform (https://itq.nl/transform/#transform_1), Utrecht - Coté talking. Oct 16th - DevOpsDays Paris (https://www.devopsdays.org/events/2018-paris/welcome/) - Coté at a table. Pivotal will have a raffle! Oct 17th - JDriven Managers summit (https://www.jdriven.com/events/) - near Amsterdam - Coté talking. Oct 10th to 11th - Cloud Expo Asia (https://www.cloudexpoasia.com/cloud-asia-2018) - Matt’s presenting! Oct 11th to 12th - DevOps Days Singapore (https://www.devopsdays.org/events/2018-singapore/) - Matt’s keynoting & igniting! Oct 31st - Coté speaking at New Relic’s FutureStack Amsterdam (https://web.cvent.com/event/23ce37e7-6077-42f5-8015-4a47a0cee30d/summary). Nov 3rd to Nov 12th - SpringOne Tour (https://springonetour.io/) - all over the earth! Coté will be MC’ing Beijing Nov 3rd, Seoul Nov 8th, Tokyo Nov 6th, and Singapore Nov 12th (https://springonetour.io/2018/singapore). Nov 14th to 16th - Devoxx Belgium (https://devoxx.be/), Antwerp. Coté’s presenting on enterprise architecture (https://dvbe18.confinabox.com/talk/ASN-9274/Rethinking_enterprise_architecture_for_DevOps,_agile,_&_cloud_native_organizations). Dec 12th and 13th - SpringTour Toronto (http://springonetour.io/2018/toronto), Coté. Listener Feedback Eoin from Wellington, New Zealand got a sticker. He thanks us for taking the time and energy to make the show. SDT websites are now secure. The annoying security warning is should be gone SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Subscribe to Software Defined Interviews Podcast (http://www.softwaredefinedinterviews.com/) - Cote on Tech Evangelism (http://www.softwaredefinedinterviews.com/75) CashedOut.coffee podcast (http://www.cashedout.coffee/). Buy some t-shirts (https://fsgprints.myshopify.com/collections/software-defined-talk)! All T-Shirts $5.50 T-SHIRTS GONE IN SEPTEMBER Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you a sticker. Brandon built the Quick Concall iPhone App (https://itunes.apple.com/us/app/quick-concall/id1399948033?mt=8) and he wants you to buy it for $0.99. Recommendations Matt: Anthony Bourdain’s Kitchen Confidential (https://www.amazon.com/Kitchen-Confidential-Adventures-Culinary-Underbelly/dp/158234082X/); Secret City (https://www.imdb.com/title/tt4976512/). Brandon: Amazon Alexa Shopping List (https://www.amazon.com/gp/help/customer/display.html?nodeId=201549900). Coté: Bikes. They get you places.

On this edition of The Predictable Revenue Podcast, co-host Collin Stewart welcomes David Hong, Vice President of Field Operations at San Francisco's Mesosphere. David is an accomplished sales operations leader. Prior to leading the team at Mesosphere, he held high ranking sales ops positions at notable Bay Area companies such as Lookout, PagerDuty, OpenDNS, and Meraki.  Throughout the pod, Collin and David discuss everything from David's professional philosophy to effective qualification methods to detailed Salesforce processes. Highlights include: David's definition of sales operations (10:54), the varied projects David has worked on (21:15), Mesosphere's MEDDPICC process (35:04), sales operations advice (49:18), and cold call Collin (54:13).

On this edition of The Predictable Revenue Podcast, co-host Collin Stewart welcomes David Hong, Vice President of Field Operations at San Francisco's Mesosphere. David is an accomplished sales operations leader. Prior to leading the team at Mesosphere, he held high ranking sales ops positions at notable Bay Area companies such as Lookout, PagerDuty, OpenDNS, and Meraki.  Throughout the pod, Collin and David discuss everything from David's professional philosophy to effective qualification methods to detailed Salesforce processes. Highlights include: David's definition of sales operations (10:54), the varied projects David has worked on (21:15), Mesosphere's MEDDPICC process (35:04), sales operations advice (49:18), and cold call Collin (54:13).

Today's episode has two for one :) The first part is episode 373 of The Space Shot and part 2 is the latest Cosmosphere Podcast. Enjoy! Welcome to season 2! The podcast is shifting to a weekly format with longer in-depth episodes covering historical topics, book reviews, interviews, and more. Make sure to stay subscribed because the content for this season is going to be phenomenal. I have incredible guests lined up, and I'm looking forward to sharing their stories and expertise with all of you! A huge shout out to all the new fans of The Space Shot on Facebook! Welcome to the podcast, I'm glad you could join us! Let me know if you have any questions, email me at john@thespaceshot.com. Send questions, ideas, or comments, and I will be sure to respond to you! Thanks for reaching out :) Thank you for making me part of your daily routine, I appreciate your time and your ears! You can send me questions and connect with me on Facebook, Instagram, or Twitter, by clicking one of the links below. Facebook (https://m.facebook.com/thespaceshot/) Instagram (https://www.instagram.com/johnmulnix/) Twitter (https://twitter.com/johnmulnix) I've also got a call in number that I'm going to be testing here soon, so keep an eye out for that! Episode Links: VSS Unity- Virgin Galactic (https://www.virgingalactic.com/articles/Into-the-Mesosphere-at-Mach-2) New Shepard Test Nine- NASAspaceflight.com (https://www.nasaspaceflight.com/2018/07/blue-origin-new-shepard-nine-test/) Blue Origin- News (https://www.blueorigin.com/news) SpaceX Second Launch in Three Days- SpaceflightNow.com (https://spaceflightnow.com/2018/07/25/spacexs-second-launch-in-three-days-lofts-10-more-iridium-satellites/) NASA Commercial Crew Announcement- Space.com (https://www.space.com/41288-nasa-will-announce-commercial-crew-astronauts.html) Mars' South Pole May Hide a Large Underground Lake- Space.com (https://www.space.com/41272-mars-liquid-water-below-ice-cap.html) Adult Astronaut Adventure (http://cosmo.org/education/camps/adult-astronaut-adventure) MOCR Delivery- Cosmosphere Blog (http://cosmo.org/blog/view/mocr-part-1-a-very-special-delivery) A huge thank you to Benoit Darcy, from Paris France for allowing us to use music from the album "Apollo" for the podcast. The song in the podcast titles is called "Hypergolic" and is available through streaming services as well as iTunes. Apollo - EP Away From Earth (http://smarturl.it/apolloEP)

Дмитрий Рожков aka Senior Software Vlogger, tech lead в компании Mesosphere, в гостях у Андрея Смирнова из Frontend Weekend. Хочешь поддержать Frontend Weekend, переходи на http://frontendweekend.ml ;) - Почему в своё время заинтересовался разработкой? 00:33 - Как после красноярских веб-студий пришла мысль о фриланс-зимовке в Таиланде? 03:44 - Почему не получилось с созданием собственного агентства и чем фриланс лучше веб-студий? 06:50 - Как после Таиланда пришла идея переезда с семьёй в Германию? 08:44 - Почему никто не вычитал страницу блога «Обо мне»? 11:50 - Почему для переезда были выбраны именно Германия и США и что не получилось с Америкой? 13:50 - Как внутри Гамбурга менялись места работы и в какой момент перешёл во frontend? 17:03 - Действительно ли снисходительно относишься ко frontend'у или это игра на публику? 20:24 - Как был придуман и с какой целью создан канал Senior Software Vlogger? 22:21 - Почему придумал именно такое название и какого уровня программистом себя считаешь? 24:27 - Зачем смешивать серьезный контент с влогами и какая вообще цель у канала? 27:12 - Сколько людей заплатило на Патреоне деньги за личные беседы и зачем это было введено? 29:13 - Зачем обычные текстовые посты скрывать за paywall'ом в 1 доллар? 32:01 - Почему выбраны такие «цены» на Патреоне и много ли уже купили рекламы? 35:42 - Откуда так много подписчиков под таким контентом и почему при этом мало просмотров? 37:28 - Зарабатываешь ли больше с проекта, чем с основной работы? 40:58 - Какие есть особенности переезда в Германию? (язык, диплом) 42:43 - Зачем ставить аффилированные ссылки на какие-то курсы и т.д.? 48:04 - Кем бы хотел быть, если бы не стал разработчиком? 50:05 - Какая справедливая зарплата для frontend-разработчика в Гамбурге? 51:06 - React, Angular, Vue или Ember? 52:44 - Готовим вместе с frontend-разработчиком 53:46 - Совет от Димы 55:07 Ссылки по теме: 1) Посоветованный курс на Coursera – https://ru.coursera.org/learn/learning-how-to-learn 2) Канал Senior Software Vlogger – https://youtube.com/user/rojkovdima 3) Frontend Weekend Patreon – https://patreon.com/frontendweekend

Дмитрий Рожков aka Senior Software Vlogger, tech lead в компании Mesosphere, в гостях у Андрея Смирнова из Frontend Weekend. Хочешь поддержать Frontend Weekend, переходи на http://frontendweekend.ml ;) - Почему в своё время заинтересовался разработкой? 00:33 - Как после красноярских веб-студий пришла мысль о фриланс-зимовке в Таиланде? 03:44 - Почему не получилось с созданием собственного агентства и чем фриланс лучше веб-студий? 06:50 - Как после Таиланда пришла идея переезда с семьёй в Германию? 08:44 - Почему никто не вычитал страницу блога «Обо мне»? 11:50 - Почему для переезда были выбраны именно Германия и США и что не получилось с Америкой? 13:50 - Как внутри Гамбурга менялись места работы и в какой момент перешёл во frontend? 17:03 - Действительно ли снисходительно относишься ко frontend’у или это игра на публику? 20:24 - Как был придуман и с какой целью создан канал Senior Software Vlogger? 22:21 - Почему придумал именно такое название и какого уровня программистом себя считаешь? 24:27 - Зачем смешивать серьезный контент с влогами и какая вообще цель у канала? 27:12 - Сколько людей заплатило на Патреоне деньги за личные беседы и зачем это было введено? 29:13 - Зачем обычные текстовые посты скрывать за paywall’ом в 1 доллар? 32:01 - Почему выбраны такие «цены» на Патреоне и много ли уже купили рекламы? 35:42 - Откуда так много подписчиков под таким контентом и почему при этом мало просмотров? 37:28 - Зарабатываешь ли больше с проекта, чем с основной работы? 40:58 - Какие есть особенности переезда в Германию? (язык, диплом) 42:43 - Зачем ставить аффилированные ссылки на какие-то курсы и т.д.? 48:04 - Кем бы хотел быть, если бы не стал разработчиком? 50:05 - Какая справедливая зарплата для frontend-разработчика в Гамбурге? 51:06 - React, Angular, Vue или Ember? 52:44 - Готовим вместе с frontend-разработчиком 53:46 - Совет от Димы 55:07 Ссылки по теме: 1) Посоветованный курс на Coursera – https://ru.coursera.org/learn/learning-how-to-learn 2) Канал Senior Software Vlogger – https://youtube.com/user/rojkovdima 3) Frontend Weekend Patreon – https://patreon.com/frontendweekend

So we start with Twitter news (change your password) to then dive into exciting news this month. There are a couple of notable IPOs and Aquisition including , and . (Congrats!). We then take a detour onto Mesosphere raising $125 million (and talk...

So we start with Twitter news (change your password) to then dive into exciting news this month. There are a couple of notable IPOs and Aquisition including @pivotal, and @smartsheet. (Congrats!). We then take a detour onto Mesosphere raising $125 million (and talk about if all these valuations feel right?) to then see Cambridge Analytica disbanded. Oh, and think twice about naming something with "Java" in your app as Oracle seems to flexing more Copyright muscle. Lastly we see a new play from IBM where they will provide support for OpenJDK's OpenJ9. What does this mean for Oracle and their commercial support? Only time will tell. But that doesn't stop us from speculating about it! So take a listen to a fully charged Java OffHeap!   We thank DataDogHQ for sponsoring this podcast episode   DO follow us on twitter @offheap Twitter Password Issue Java Mission Control Open Sourced Mesosphere Raises 125 million Intel has 8 more Spectre-Class vulnerabilities Cambridge Analytica shuts down Oracle IOS app Takedown IBM Providing support to OpenJDK OpenJ9 to keep LTS versions current Net Neutrality Vote

Conference season is upon us so we recap all the announcements from Google I/O and Microsoft Build. We also discuss the Mesosphere funding and attempt to deceiver what exactly they are doing with DC/OS. Finally, we have recommendations for Mother’s Day gifts, making kid lunches and some talk of the Lego Millennium Falcon. Relevant to your interests Mesosphere Scores $125M in Funding to Target IoT, Geo Expansion (https://www.sdxcentral.com/articles/news/mesosphere-scores-125m-in-funding-to-target-iot-geo-expansion/2018/05/?utm_source=feedblitz&utm_medium=FeedBlitzRss&utm_campaign=sdxcentral) more coverage from George Leopold (https://www.enterprisetech.com/2018/05/07/mesospheres-investors-bet-on-multicloud/). Twitter signs for Google cloud at list price of about $10m a month (https://www.theregister.co.uk/2018/05/04/twitter_adopts_google_cloud_for_hadoop_and_cloud_storage/) Oath to Use More AWS Cloud as It Expands Video Play (http://www.datacenterknowledge.com/amazon/oath-use-more-aws-cloud-it-expands-video-play) Microsoft Build 2018: Top Five Takeaways (https://go.forrester.com/blogs/microsoft-build-2018-top-five-takeaways/) (https://go.forrester.com/blogs/microsoft-build-2018-top-five-takeaways/)from Jeffery Hammond at Forrester (https://go.forrester.com/blogs/microsoft-build-2018-top-five-takeaways/) RedHat OpenShift running on Azure Stack and Azure (https://www.theregister.co.uk/2018/05/08/microsoft_azure_redhat_openshift/), partnership. See also the RedHat/IBM partnership along the same lines (https://www.zdnet.com/article/ibm-red-hat-couple-containers-for-hybrid-cloud-deployments/#ftag=RSSbaffb68), plus nifty history of the two collaborating. Miniature ponies (https://twitter.com/bridgetkromhout/status/993557979336065027)! CoreOS folded into Red Hat product suite (https://coreos.com/blog/coreos-tech-to-combine-with-red-hat-openshift), the old “reverse integration.” The 10 biggest announcements from Google I/O 2018 (https://www.theverge.com/2018/5/8/17328828/google-io-keynote-summary-highlights-news-recap-2018) 15 Google I/O announcements (http://www.businessinsider.com/google-io-announcements-highlights-2018-5). Serverless Survey: +77% Delivery Speed, 4 Dev Workdays/Mo Saved & -26% AWS Monthly Bill (https://hackernoon.com/serverless-survey-77-delivery-speed-4-dev-workdays-mo-saved-26-aws-monthly-bill-d99174f70663) Related, Serverless to take over like space carpets (https://twitter.com/swardley/status/994333147130220549). Azure at Microsoft Build Announcements| Microsoft Azure (https://azure.microsoft.com/en-us/build/announcements/) JEDI mind tricks: Brakes slammed on Pentagon's multibillion cloud deal (https://www.theregister.co.uk/2018/05/08/house_slams_the_brakes_on_pentagons_big_cloud_deal/) AWS numbers reveal extent of Aussie growth (https://www.itnews.com.au/news/aws-numbers-reveal-extent-of-aussie-growth-490694) IBM bans all removable storage, for all staff, everywhere (https://www.theregister.co.uk/2018/05/10/ibm_bans_all_removable_storage_for_all_staff_everywhere/) This episode brought to you by: Datadog! This episode is sponsored by Datadog, a monitoring platform for cloud-scale infrastructure and applications. . Sign up for a free trial (https://www.datadoghq.com/ts/tshirt-landingpage/?utm_source=Advertisement&utm_medium=Advertisement&utm_campaign=SoftwareDefinedTalkRead-Tshirt) at www.datadog.com/sdt (http://www.datadog.com/sdt) Datadog wants you to know about there upcoming conference DashCon, in NYC on July 11th-12th (https://www.dashcon.io/?utm_source=Advertisement&utm_medium=GoogleAds&utm_campaign=GoogleAds-Dash&utm_content=Dash&utm_keyword=%2Bdatadog%20%2Bconference&utm_matchtype=b&gclid=CjwKCAjw8r_XBRBkEiwAjWGLlH3LXgGYu4iPzwOh8gkrY5NAQ1B9dWqB2OukaISujKyVCU4_5sUUchoCfT8QAvD_BwE). You can register to attend at https://www.dashcon.io/ DevOpsDays MINNEAPOLIS - JULY 12-13, 2018 Get a 20% discount for one of the best DevOpsDays on the planet, DevOpsDays Minneapolis. It's July 12th to 13th, and you can bet it'll be worth your time. If you're new to DevOps you'll get an idea of what it is, how it's practices, and how to get started. If you're an old pro, you'll dive down into topics and catch-up with all the other old hands. Code: SDT2018 Nonsense Google Duplex making an appointment on the phone (https://www.youtube-nocookie.com/embed/bd1mEm2Fy08) Lego Millennium Falcon, enterprise edition (https://shop.lego.com/en-AU/Millennium-Falcon-75192). Conferences, et. al. NEXT WEEK! May 15th to 18th, 2018 - Coté talking EA at Continuous Lifecycle London (https://continuouslifecycle.london/sessions/the-death-of-enterprise-architecture-defeating-the-devops-microservices-and-cloud-native-assassins/). May 16 to 17, Matt presenting at Cloud Expo Hong Kong (https://www.cloudexpoasiahk.com/) May 22 to 25, ChefConf 2018 (https://chefconf.chef.io/), in Chicago. June 1st, 2018 - Coté speaking (https://voxxeddays.com/singapore/program/) at Voxxed Days, Singapore (https://voxxeddays.com/singapore/). June 7th, 2018 - DC Cloud Native Meetup, “Beyond ‘Survival is Not Mandatory.’” (https://www.meetup.com/DC-Cloud-Native-Meetup/events/250543895/) Sep 24th to 27th - SpringOne Platform (https://springoneplatform.io/), in DC/Maryland (crabs!) get $200 off registration with the code S1P200_Cote. SDT news & hype Check out Software Defined Interviews (http://www.softwaredefinedinterviews.com/), our new podcast. Pretty self-descriptive, plus the #exegesis podcast we’ve been doing, all in one, for free. Keep up with the weekly newsletter (https://us1.campaign-archive.com/home/?u=ce6149b4008d62a08093a4fa6&id=5877922e21). Join us in Slack (http://www.softwaredefinedtalk.com/slack). Buy some t-shirts (https://fsgprints.myshopify.com/collections/software-defined-talk)! DISCOUNT CODE: SDTFSG (20% off) Send your name and address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you a sticker. If you run into Matt he’ll give you one too! Recommendations Matt Ray: New phone, Sony Xperia XZ1 Compact (https://www.engadget.com/2018/01/24/sony-xperia-xz1-compact-impressions/). Brandon: Postal Service - Against All Odds (https://www.youtube.com/watch?v=8jWYJrycJC8) & A Quiet Place (https://www.rottentomatoes.com/m/a_quiet_place_2018/) Coté: Chasing Hillary, (https://www.audible.com/pd/Nonfiction/Chasing-Hillary-Audiobook/B079F31QY1?ref=a_search_c3_lProduct_1_1&pf_rd_p=e81b7c27-6880-467a-b5a7-13cef5d729fe&pf_rd_r=MS4QEGZS6C7BGEP2CCDQ&) Amy Chozick. (https://www.audible.com/pd/Nonfiction/Chasing-Hillary-Audiobook/B079F31QY1?ref=a_search_c3_lProduct_1_1&pf_rd_p=e81b7c27-6880-467a-b5a7-13cef5d729fe&pf_rd_r=MS4QEGZS6C7BGEP2CCDQ&) Photo Credit Bridget Kromhout (https://twitter.com/bridgetkromhout/status/993557979336065027)

Florian Leibert is the Founder & CEO @ Mesosphere, the most flexible platform for containerized, data-intensive applications. They are trusted by some of the world's leading companies from Yelp to Yammer to Verizon and have raised over $120m in VC funding from the likes of a16z, Kleiner Perkins, Khosla, Data Collective and then incumbents such as Microsoft and Hewlett Packard. Prior to founding Mesosphere, Florian spent time with Twitter and Airbnb, both as a tech lead and if that was not enough, Florian also has a stellar angel portfolio including the likes of Away, Cockroach Labs, Drift and Buoyant. In Today’s Episode You Will Learn: 1.) How Florian came to found Mesosphere? What were the big takeaways for him from his more formative years at Twitter and Airbnb? 2.) Why does Florian believe that sometimes "you should not listen to your investors"? What is the right way to communicate this disagreement to them? What supporting evidence is required to substantiate your thoughts? What method would Florian prefer to receive such feedback? 3.) What are the biggest benefits of having strategics such as Microsoft and Hewlett Packard on the cap table? What are some potential drawbacks? What advice would Florian give to founders contemplating taking strategic investment? When is the right time for these staretgics to insert themselves? 4.) With the scaling of Mesosphere, how have Florian's thoughts and approach to sales execution changed? What have been the core struggles? Why does Florian think it is imperative to build the sales team slowly? 5.) At what point does Florian think that operational efficiency must be front and centre for founders scaling their companies? What has Florian found to be the most challenging personally in achieving such operational efficiency? Items Mentioned In Today’s Show: Florian’s Fave Book: Alchemist: A Fable about Following Your Dream Florian's Fave Blog: Seeking Alpha As always you can follow Harry, The Twenty Minute VC and Florian on Twitter here! Likewise, you can follow Harry on Snapchat here for mojito madness and all things 20VC. NatureBox Unlimited snack plans offer all you can eat snacks for one fixed price per employee. Naturebox use simple ingredients you can trust to create bold flavors you can’t find anywhere else. All NatureBox snacks are free from artificial junk and variety is endless with options from sweet or savory to vegan or gluten-free. Simply choose the plan that fits your team’s unique snacking habits and select any of NatureBox’s time-saving add-on’s. And beyond Unlimited snacks, you’ll receive perks such as free kitchen setup, no contracts, a dedicated account manager and more. Simply click here to and use the offer code VC20 to get 20% of your first Naturebox month. Leesa is the Warby Parker or TOMS shoes of the mattress industry. Leesa have done away with the terrible mattress showroom buying experience by creating a luxury premium foam mattress that is ordered completely online and ships for free to your doorstep. The 10-inch mattress comes in all sizes and is engineered with 3 unique foam layers for a universal, adaptive feel, including 2 inches of memory foam and 2 inches of a really cool latex foam called Avena, design to keep you cool. All Leesa mattresses are 100% US or UK made and for every 10 mattresses they sell, they donate one to a shelter. Go to Leesa.com to start the New Year with better nights sleep!

The DevOps kids have decided to come up with a new term “observability.” We get to the bottom of the WTF barrel on what that is - it sounds like a good word-project. Also, there’s a spate of kubernetes news, as always, and some interesting acquisitions. Plus, a micro-iOS 11 review. Meta, follow-up, etc. Patreon (https://www.patreon.com/sdt) - like anyone who starts these things, I have no idea WTF it is, if it’s a good idea, or if I should be ashamed. Need some product/market fit. Check out the Software Defined Talk Members Only White-Paper Exiguous podcast over there. Join us all in the SDT Slack (http://www.softwaredefinedtalk.com/slack). Is “observability” just “instrumentation”? Write-up (https://medium.com/@copyconstruct/monitoring-and-observability-8417d1952e1c) from Cindy Sridharan. This guy (https://medium.com/@steve.mushero/observability-vs-monitoring-is-it-about-active-vs-passive-or-dev-vs-ops-14b24ddf182f): “Thinking directionally, Monitoring is the passive collection of Metrics, logs, etc. about a system, while Observability is the active dissemination of information from the system. Looking at it another way, from the external ‘supervisor’ perspective, I monitor you, but you make yourself Observable.” So, yes: if developers actually make their code monitorable and manageable…easy street! It’s a good detailing of that important part of DevOps. Cloud Native Java (http://amzn.to/2jPJHcv) has a good example with the default “observability” attributes for apps, and then an overview of Zipkin tracing. Weekly k8s News Heptio gets funding (https://www.geekwire.com/2017/heptio-raises-25m-series-b-funding-round-kubernetes-takes-world/), now “has raised $33.5 million in funding to date.” I think we’ll cover this press release in a WP episode. Also, something called “StackPointCloud” now with the Istio (https://thenewstack.io/stackpointcloud-drops-istio-service-mesh-integration/). Mesosphere adding K8s support (https://techcrunch.com/2017/09/06/mesosphere-says-its-not-bowing-to-kubernetes/) - “Guagenti also noted that he believes that Mesosphere is currently a leader in the container space, both in terms of the number of containers its users run in production and in terms of revenue (though the company sadly didn’t share any numbers).” "I think it’s fair to call Kubernetes the de facto standard for how enterprises will do container orchestration,” Derrick Harris (http://news.architecht.io/issues/with-oracle-on-board-kubernetes-has-to-be-the-de-facto-standard-for-container-orchestration-73880). Is Kubernetes Repeating OpenStack’s Mistakes? (https://www.mirantis.com/blog/is-kubernetes-repeating-openstacks-mistakes/) - Boris throwing bombs Meanwhile, an abstract of a containers penetration study (https://redmonk.com/fryan/2017/09/10/cloud-native-technologies-in-the-fortune-100/), from RedMonk: "Docker, is running at 71% across Fortune 100 companies. Kubernetes usage is running in some form at 54%, and Cloud Foundry usage is at 50%” This update from the Cloud Foundry Foundation (https://www.cloudfoundry.org/update-containers-2017-research-shows/) is a little more, er, “responsible” in pointing out flaws. Instead it just says there’s lots of growth and tire-kicking: 2016/2017 y/y shows those evaluating containers went up from 31% to 42%, while “using” ticked up a tad from 22% to 25%, n=540. Oracle’s in the CNCF (https://techcrunch.com/2017/09/13/oracle-joins-the-cloud-native-computing-foundation-as-a-platinum-member/) club! K8s on Oracle Linux, K8s for Oracle Public Cloud. “At this point, there really can’t be any doubt that Kubernetes is winning the container orchestration wars, given that virtually every major player is now backing the project, both financially and with code contributions.” James checks in on Red Hat (http://redmonk.com/jgovernor/2017/09/21/red-hat-is-pretty-good-at-being-red-hat/). (https://techcrunch.com/2017/09/13/oracle-joins-the-cloud-native-computing-foundation-as-a-platinum-member/) Acquisitions & more! Rackspace acquires Datapipe (https://techcrunch.com/2017/09/11/rackspace-acquires-datapipe-as-it-looks-to-expand-its-managed-cloud-business/) “The reason we’re buying them is that we want to extend our leadership in multi-cloud services,” Rackspace chief strategy officer Matt Bradley told me. “It’s a sign and signal that we’re going for it.” Bradley expects that the combined company will make Rackspace the largest private cloud player and the largest managed hosting service. Datadog acquires Logmatic.io to add log management to its cloud monitoring platform (https://techcrunch.com/2017/09/07/datadog-acquires-logmatic-io-to-add-log-management-to-its-cloud-monitoring-platform/) Puppet Acquires Distelli (https://www.geekwire.com/2017/puppet-acquires-distelli-bolster-cloud-computing-automation-platform/), known for their Kubernetes dashboard. Jay Lyman at 451 (https://451research.com/report-short?entityId=93381). Sizing Puppet: “The company has grown to more than 500 employees, and has estimated annual revenue in the $100m range.” Coverage from Susan Hall: “What we haven’t had up to this point is all the requisite automation for moving infrastructure code and application code through any kind of automated delivery lifecycle” and now they gots that. https://thenewstack.io/puppet-will-extend-infrastructure-automation-capabilities-distelli-acquisition/ “In May, the company launched its Kubernetes dashboard K8S. It allows users to connect repositories, build images from source, then deploy them to that Kubernetes cluster. You can also set up automated pipelines to push images from one cluster to another, promote software from test/dev to prod, quickly roll back and do all this in the context of one or more Kubernetes clusters… The Kubernetes service is offered as a hosted service or in an on-prem version. It provides notifications through Slack.” Google pays $1.1 billion for HTC team and non-exclusive IP license (https://www.axios.com/login-2487682498.html?rebelltitem=2&utm_medium=linkshare&utm_campaign=organic#rebelltitem2) Security Corner The Apple Effect? — Why BMW might get rid of car keys (http://www.autonews.com/article/20170915/OEM06/170919789/why-bmw-might-get-rid-of-car-keys) Don’t blame Apache — EQUIFAX OFFICIALLY HAS NO EXCUSE (https://www.wired.com/story/equifax-breach-no-excuse/) Is there anything to do here? Setup layers of credit cards? Require Touch ID (etc.) approval of all financial decisions and transactions in your “account”? Food & Safety like inspectors for security? Hackers respond to Face ID on the iPhone X (http://bgr.com/2017/09/21/iphone-x-release-date-soon-hackers-eye-face-id/) iOS 11 Coté has been running the beta. It seems fine. There’s the usual Re-arrangement of how some gestures work that’s jarring at first, but after using it for awhile, you forget what they even are. The extra control center stuff is nice. The Files.app is interesting, but not too featureful. The new photo formats are annoying because, you know, non-Apple things need to support it (which they seem to?) Bonus Links Coté gives up on defining DevOps, and more Interview about DevOpsDays Auckland (https://www.infoq.com/news/2017/09/michael-cote-devops-days-nz). (https://techcrunch.com/2017/09/13/oracle-joins-the-cloud-native-computing-foundation-as-a-platinum-member/) Is Solaris dead yet? Strongly confirmed rumors that Oracle is shutting it down (http://www.zdnet.com/article/sun-set-oracle-closes-down-last-sun-product-lines/). This guy has written a big Solaris-brain to Linux-brain manifesto/guide (http://www.brendangregg.com/blog/2017-09-05/solaris-to-linux-2017.html), plus: “[n]owadays, Sun is a cobweb-covered sign at the Facebook Menlo Park campus, kept as a warning to the next generation.” SICK BURN! Layoffs and more (http://dtrace.org/blogs/bmc/2017/09/04/the-sudden-death-and-eternal-life-of-solaris/): “In particular, that employees who had given their careers to the company were told of their termination via a pre-recorded call — “robo-RIF’d” in the words of one employee — is both despicable and cowardly.” HPE We Can See The New Hewlett Clearly Now, Says CEO Whitman (http://blogs.barrons.com/techtraderdaily/2017/09/05/hpe-we-can-see-the-new-hewlett-clearly-now-says-ceo-whitman/?mod=BOLBlog) - AI in storage arrays, Docker in OneView. Clearly (http://www.marketwatch.com/story/hp-enterprise-has-yet-another-confusing-plan-to-simplify-itself-2017-09-05)? Making money (https://www.cnbc.com/2017/09/05/hpe-earnings-q3-2017.html). They bought CTP!? (https://www.cloudtp.com/doppler/hewlett-packard-enterprise-to-acquire-cloud-technology-partners/) Selling hardware to cloud providers is rough (https://www.nextplatform.com/2017/09/06/prospects-leaner-meaner-hpe/). Huawei New board (http://talkincloud.com/cloud-services/chinas-huawei-braces-board-revamp-western-markets-beckon). Microsoft app support. We can all agree on food Someone has to pay attention to this real world stuff (http://www.nationalgeographic.com/magazine/2017/09/holland-agriculture-sustainable-farming/). This Tiny Country Feeds the World More on VMware/AWS The possible failures in the partnership (https://www.bloomberg.com/news/articles/2017-09-01/how-vmware-s-partnership-with-amazon-could-end-up-backfiring) - sort of an odd article in that the larger point is “maybe it won’t work.” Meanwhile, Matt Asay does some loopty-loops on it all (https://www.theregister.co.uk/2017/09/11/kubernetes_envy/). JEE Code put in github (http://go.theregister.com/feed/www.theregister.co.uk/2017/09/06/oracle_java_ee_java_se_github/). They’re giving it over to the Eclipse Foundation (https://blogs.oracle.com/theaquarium/opening-up-ee-update). Probably a good idea. VMware’s OpenStack Little report form 451 (https://451research.com/report-short?entityId=93303&type=mis&alertid=693&contactid=0033200001wgKCKAA2&utm_source=sendgrid&utm_medium=email&utm_campaign=market-insight&utm_content=newsletter&utm_term=93303-VMware+sheds+free+version+of+its+OpenStack+distribution). “Going forward, users pay a onetime $995-per-CPU socket license fee, in addition to ongoing support.” Recommendations Brandon: Prophets of Rage (http://prophetsofrage.com/). Matt: American Gods (https://en.wikipedia.org/wiki/American_Gods_(TV_series)), the TV show. Zero History (https://www.amazon.com/Zero-History-Blue-William-Gibson-ebook/dp/B003YL4AGC/): finale(?) to William Gibson’s Blue Ant trilogy LOT (https://www.lot2046.com/): a subscription-based service which distributes a basic set of clothing, footwear, essential self-care products, accessories, and media content. Engineering the End of Fashion (https://www.ssense.com/en-gb/editorial/fashion/engineering-the-end-of-fashion) Coté: Rick & Morty (http://amzn.to/2xrHo3L). These cultural guides (http://www.commisceo-global.com/country-guides) are fucking awesome! See America (http://www.commisceo-global.com/country-guides/usa-guide), Australia (http://www.commisceo-global.com/country-guides/australia-guide), and Latvia (http://www.commisceo-global.com/country-guides/latvia-guide) (no one sang at the meals I was at!). Cardenal Mendoza (https://www.thewhiskyexchange.com/p/996/cardenal-mendoza-brandy-solera-gran-reserva), brandy de jerez (https://en.wikipedia.org/wiki/Brandy_de_Jerez). And, you know, cognac/brandy in general - be a fucking adult already, you damn kids.

We interview Mesosphere co-founder and CEO Florian Leibert about his company being named a World Economic Forum Technology Pioneer and about the role Mesosphere and its Data Center Operating System fit in the vision of an interconnected future, where cars drive themselves and where data from every device is collected and put to use.

Stathy Touloumis (@stathyinc), Technology Director at Mesosphere (@mesosphere) joins us live on The Hot Aisle during Day 3 of Dell EMC World 2017 to talk Mesosphere DC/OS, REX-Ray from {code} by Dell EMC (@codeDellEMC), and Dell EMC ScaleIO Ready Nodes as a reference architecture for your next generation data center.  Your hosts Brent Piatti (@BrentPiatti) […]

Are Docker and Kubernetes friends? Maybe. Are they partners? Definitely. Many tech companies have a shared interest in promoting the successful adoption of cloud-native technologies. As Diane Mueller, Red Hat's Director of Community Development for OpenShift recently wrote on Twitter, “Everyone and everything is connected, nothing wrong with cross-community collaboration #everybodywins.” On today's episode of The New Stack Analysts, Scott Ottaway, Research Director for DevOps, Cloud Application Platforms and Open Source at IDC joins Alex and Lawrence to discuss partnerships and alliances in the cloud-native ecosystem. Scott provides context into how and why companies enter into relationships with larger cloud providers. Deep into the conversation, Scott thinks about the relative position of Kubernetes, Mesosphere and Docker's orchestration capabilities. Scott is very diplomatic but we all laughed when he said “There's a whole bunch of dogs that won't hunt when you see joint press releases.”

Kenny Tran is a passionate writer and coder. He chose to forego college and instead pursued his personal projects and his love of writing. After reading a post on Hacker News about App Academy, he decided to apply and learn how to code, joining the first Ruby on Rails cohort. He also attended Hack Reactor and built a cool project, PurifyCSS, that went viral on GitHub and Hacker News. He eventually joined Mesosphere, an infrastructure startup, serving as a front end engineer but is soon leaving this job in order to focus more on his upcoming personal projects. In this episode, Kenny talks more about his bootcamp journey, his job search experience, the life lessons he learned along the way, and the awesome projects he created.

In this Around the Storage Block podcast, we talk about the joint technology from HPE and Mesosphere to power customer transformation to Hybrid IT.

Damien Chazelle's La La Land is a good movie. It is so good, in fact, that you'll be hard-pressed to find anything negative said about it on this snob. In fact, we are finding it difficult to say anything about it in this description. Like trying to describe the "True Snob," attempting to describe this film has a way of making words disappear. That is because its images transcend words. It is an exuberant expression of emotion and possibility tinged with a realistic portrayal of human beings and the inevitable struggles of real-life relationships, no matter how fantastical they may be at first. Throughout this early snob of 2017, we discuss stuff as far-reaching as The Last Temptation of Christ, the music video for "Cool" by Gwen Stefani, (500) Days of Summer, George Clooney's stardom and "smuggy" Oscar acceptance speech, (John) Legend, I Am Legend, Joseph Campbell and Christopher Vogler, Neo's dive-bomb into Hugo Weaving's chest, and the necessity of struggles in following one's dreams. General Snobbery was most inspired by this film to continue living its dream to #LetUsWriteID3, a dream for whose actualization we are willing to travel through the deepest pangs of suffering. This path of life leads such grand and unexpected places. Who would have anticipated that a conversation beneath the Cincinnati stars would eventually yield an interview with DeObia Oparei, a truly wonderful man? Who can predict where this snobbing journey may lead? We cannot, listener, and neither can the great Damien Chazelle. All we know is that we must not submit to any blockades, regardless of how many Twitter followers we lose for inexplicable reasons. In words penned by the great Roland Emmerich, delivered by the great @BillyPullman, "We're going to live on!" In the words of the late great Freddy Mercury, "I'm having a good time, having a good time, I'm a shooting star leaping through the sky... There's no stopping me." Let us continue to ride these waves into the vast reaches of the Stratosphere, transcending the Mesosphere into the land where dreams reside, into the shimmering tesseracts of "La La Land", a place of infinite bliss and possibility. Yay.

Join the Acquired Limited Partner program! https://kimberlite.fm/acquired/ (works best on mobile)   Topics covered include: Brian’s history working across “both sides of the aisle” as both a startup founder and corporate development leader at a big company, how perspective from each informs the other, and the importance of learning “customer empathy”  How Microsoft approaches M&A from an organizational perspective, and the importance of fit with the company’s product roadmap  How Brian approaches strategic investments at Microsoft, and the evolution over time of the Microsoft (and large technology companies as a whole) perspective on investing in other companies Balancing the tension between partnering and investing, and what criteria Brian thinks about when evaluating companies  Microsoft’s investment in Facebook in 2007 (at a then-crazy-seeming $15B valuation), and more recently Foursquare, Mesosphere, CloudFlare and others The current state of the tech M&A landscape, and the emergence of private equity as tech company acquirers  Potentially changing corporate and foreign tax structures and how they impact acquirers’ thinking around deals (or not!)  How Microsoft tracks and evaluates success of acquisitions over time, and lessons learned from successes and failures  The increasing number of operating companies (technology and otherwise) looking to invest in startups, and how that landscape has evolved over time    Followups: Snap Inc.’s rumored IPO filing — and bonus discussion of how VC’s and other investors think about “exiting” their investments in companies that have gone public   Hot Takes: Amazon Go!   The Carve Out: Ben: OK Go - The One Moment  David: UC Berkeley Oral History with Sequoia Capital founder Don Valentine Brian: Om Malik’s recent piece in the New Yorker: Silicon Valley Has an Empathy Vacuum

We discuss possible effects that the Trump presidency will have on the tech world. The ideas are more or less known, but the details and whether they'd be enacted are sketchy and unreliable. Before that, of course, we talk about containers. This episode features Brandon Whichard (https://twitter.com/bwhichard), Matt Ray (https://twitter.com/mattray), and Coté (https://twitter.com/cote). Mid-roll Matt: Dec 1st and 2nd - DevOps Days Australia 20% discount code - SDT2016 (https://ti.to/devopsaustralia/2016-sydney/discount/SDT2016). Coté: Nov 16th - Cloud Native Roadshow in Omaha, next week (https://pivotal.io/event/cloud-native-workshop/omaha). Coté: Various dates - Pivotal Cloud Native Roadshows (https://pivotal.io/event/pivotal-cloud-native-roadshow) - Cincinnati - Nov 10 (https://pivotal.io/event/pivotal-cloud-native-roadshow/cincinnati); St. Louis - Nov 14 (https://pivotal.io/event/pivotal-cloud-native-roadshow/stlouis); Hartford - Nov 16 (https://pivotal.io/event/pivotal-cloud-native-roadshow/hartford); Denver - Nov 18 (https://pivotal.io/event/pivotal-cloud-native-roadshow/denver); New York - Nov 22 (https://pivotal.io/event/pivotal-cloud-native-roadshow/newyork); Los Angeles - Nov 28 (https://pivotal.io/event/pivotal-cloud-native-roadshow/losangeles). K8s Operators Stateful applications for K8s, a shot at Mesos (https://coreos.com/blog/introducing-operators.html)? Prometheus & etcd first examples (spark? hadoop?) This begs the broad question: so, what’s CoreOS’s business posture now? Azure Container Service, now with K8s Those Microsoft folks will just put anything that looks tasty in their cloud (https://azure.microsoft.com/en-us/blog/azure-container-service-the-cloud-s-most-open-option-for-containers/) - what a reversal from the Microsoft we grew up with. Docker in Production: A History of Failure From this dude’s perspective (https://thehftguy.wordpress.com/2016/11/01/docker-in-production-an-history-of-failure/): a failure of product management and stable releases. Bugs, documentation spotty, cleanup scripts, kernel support (Debian!?), aufs & overlay & overlay2, 7-hour outage with no post-mortem “Docker only moves forward and breaks things” “The docker hype is not only a technological liability any more, it has evolved into a sociological problem as well.” A retort… that mostly agrees (https://patrobinson.github.io/2016/11/05/docker-in-production/) “boring tech is what makes money” shiny tech makes resumes? Mesosphere Jay Lyman on the momemtum (https://451research.com/report-short?entityId=88226): “Mesosphere does not disclose its number of paying clients, but says it has dozens of large enterprise customers, its primary target. The company says its experience supporting software deployments in production is among its key differentiators, helped by the use of Apache Mesos by companies such as Twitter, Netflix, Airbnb, PayPal and Yelp, which was featured in a 451 User Deployment Report. Mesosphere says its focus is customer deployments of 500-1,000 nodes per day in production. It also says the bulk of its customers are licensees with professional services accounting for less than 10% of its clients, which tend to move to its subscription software.” TrumpTech, aka, “Putting the 400 lbs hackers on diets.” Turns out there is some marginally clear policy, just not McKinsey title mode versus white papers (http://www.vox.com/2016/11/10/13584390/donald-trump-first-100-days). Jonathan Shieber@Tech Crunch (https://techcrunch.com/2016/11/09/what-does-a-president-elect-trump-mean-for-silicon-valley-nothing-very-good/): "The biggest question facing millions of Americans this Wednesday is: just how much of what Donald Trump said on the campaign does he intend to actually try to make happen." (For example, Korea (http://www.vox.com/world/2016/11/10/13585524/donald-trump-phone-call-south-korea-park-geun-hye).) Dave Lee, at the BBC has a good laundry list: “Uncertainty, frustration and an increased fragility for the global home of tech innovation. Mr Trump certainly won't want to go down as the president who destroyed Silicon Valley, but the concern here is that of the few policies that have been explained in detail, some seem directly at odds with each other.” 10% repatriation program (http://blogs.barrons.com/techtraderdaily/2016/11/09/apple-adobe-cisco-citi-focuses-on-big-techs-big-trump-tax-windfall/) - tech companies have tons of cash abroad: Historic rates (http://www.investopedia.com/terms/r/repatriation.asp): “At the highest tax rate, corporations must pay 35% to repatriate capital, minus local taxes charged by countries in which the funds are held.” Hardware: “AAPL (93% of $230bln), CSCO (91% of $64.6B), IBM ($8.2B total cash, undisclosed % of cash held overseas but note 58% of earnings are from non US operations), HPE ($10.0B total cash, undisclosed % of cash held overseas but 65% of earnings are from non US operations), HPQ ($5.6B total cash, undisclosed % of cash held overseas but 65%-70% of earnings are from non US operations), JNPR (94% of $3.2B).” Software: “Specifically, some of the mid and large cap companies that have large cash balances “trapped” offshore are likely to benefit from being able to return a portion of this cash to shareholders. We note companies with high gross cash balances trapped offshore include: ADBE (85% of $4B – from 2015 10-K), ADSK (86% of $2.1B), CA (76% of $2.7B), CTXS (80% of $2.45B), FTNT (38% of $1.2B), ORCL (76% of $56B – pre-N), MSFT (96% of $113B – pre-LNKD purchase), RHT (42% of $2.0B), SYMC (93% of $5.6B – post-BC), VMW (77% of $7.5B), VRSN (68% of $1.9B). We believe the chances increase of a larger share repurchase or (lesser chance) dividend from these companies.” Apple & Amazon are not in a good situation (http://www.theregister.co.uk/2016/11/09/tech_trump_silicon_valley/) - they’ll be a good test of WTF happens. Meanwhile, tech stocks dropping a bit (http://www.marketwatch.com/story/tech-stocks-plunge-for-second-straight-day-after-trump-win-2016-11-10). Ovum has a shit ton of quick analysis, all free (https://www.ovum.com/us-presidential-election-2016/): Fear of US public cloud companies, globally (https://www.ovum.com/will-trump-presidency-mean-public-cloud-computing-2-2/). Remember the freak-out from NSA stuff? Same idea. I think the Gemans got over it. Outsources (https://www.ovum.com/providers-prepare-trump-presidency-potential-impact-global-delivery-2/): “A massive curtailing of H-1B visas, for example, will mean providers will need to make immediate shifts in what they’re able to offer customers locally, unless or until they’re able to compensate with talent.” “For providers, there’s also the unanswered question of the impact on US government spending.” [Education](https://www.ovum.com/trumping-expectations-now-us-public-sector-2/ - some proposals for de-centralizing, meaning fragmentation of IT spend. Government talent, regulations, and spending (https://www.ovum.com/trumping-expectations-now-us-public-sector-2/) - “If there is a large exodus of high-caliber and skilled staff, how will departments fill the gap? It also raises the question of funding for programs aimed at modernizing tech in the federal government such as F18 and FedRAMP. Trump might reduce the barriers to swapping out tech and push down expenditure that way. Certainly, the high cost and length of time needed to get Authority to Operate (ATO) under FedRAMP has been a barrier to uptake.” Telcos (https://www.ovum.com/trumps-victory-will-affect-us-telecoms-market/) - other than him stating he’d stop the AT&T/TimeWarner merger, telco stuff is very unclear. No one’s sure what the traditional Republican +/- Trump equals, or what the formula is. M&A from Brenon@451 (https://451research.com/report-short?entityId=90759&type=mis&alertid=211&contactid=0033200001wgKCKAA2&utm_source=sendgrid&utm_medium=email&utm_campaign=market-insight&utm_content=newsletter&utm_term=90759-In+Trump%2C+an+M%26A+watchdog+with+more+bite): “Chinese buyers probably won't be shopping as freely in the US in the coming years.” They spent $14bn this year, I think. Chinese buyers have recently picked up Ingram Micro, which swings nearly $50bn worth of tech gear and services each year, 25-year-old printer maker Lexmark and even a majority stake in the gay dating app Grindr." Also see shorter blog post with chart of Chinese M&A spend (https://blogs.the451group.com/techdeals/investment-banking/in-trump-a-tech-ma-watchdog-with-more-bite/). Snowden for Head of NSA! (https://twitter.com/realDonaldTrump/status/346998236776640513). Follow-up That’s how you do it! (https://twitter.com/simonmcc/status/794951901720805376) We got actual comments (http://www.softwaredefinedtalk.com/77#disqus_thread)! BONUS LINKS! Not covered in episode Matt wrote up an Amazon ECS thing The blog entry (https://blog.chef.io/2016/11/07/habitat-amazon-elastic-container-service/) Doing Business in Japan Not new, but a good primer (http://www.kalzumeus.com/2014/11/07/doing-business-in-japan/). Recommendations Brandon: New season of The Startup podcast (https://gimletmedia.com/episode/shadowed-qualities-season-4-episode-3/) Matt: TransferWise (https://transferwise.com/u/matthewr9) for transferring money abroad. A16Z on TransferWise (https://a16z.com/2016/01/29/a16z-podcast-when-banking-works-like-my-smartphone/). Coté: “Tighten Up.” (https://open.spotify.com/track/2pBgtxhgqevCHEnJ7W5UKI), Archie Bell & The Drells - once you’re done being depressed, get your shit back together. HSAs. Meanwhile, this “pastrami burger” (https://www.instagram.com/p/BMpHcIhDJkk/) at 3 Greens Market (http://3greensmarket.com/) in Chicago is AMAZING.

“Serverless computing,” at the time of this writing, is an emerging ideal that's past the embryonic stage, yet not quite fully formed. It has a variety of advocates, some of whom make more sense than others. But what does the term “serverless” mean, exactly? We speak with two such advocates who put forth the most sensible cases thus far: Michael Hausenblas, a developer and developer advocate at Mesosphere, and author of a recent New Stack article entitled, “Making Sense of Serverless Computing”; and Chad Arimura, the CEO of Iron.io and a previous guest of our podcasts with Alex Williams. Our conversations with Hausenblas and Arimura were separate, but they made much the same case: specifically, for eliminating the appearance of dependencies between software currently under development, and its underlying resources and infrastructure. If you remember the era where you turned on your personal computer, saw a “READY” prompt, and everything you'd ever need to reference was on a memory map — it's like the modern evolution of that. When we started the whole cloud-native development paradigm, it was with the idea that the cloud could mask the details of deployment and implementation from the developer. Then when we started the whole container orchestration business, it was with this notion that the developer was the person doing the deployment and implementation. Arimura and Hausenblas suggest that, if the details of software implementation can be condensed to a more basic form, a developer could conceivably produce a draft that meets a basic requirement of a service-level agreement. This way, an automated deployment pipeline could test its container, fail it or pass it, and in the latter case, re-attach the necessary details and deploy it to production. Imagine an operator petitioning a developer for an app that performed a function whose performance rated, say, a 7 on a 10-point scale. The developer wouldn't need to know why, just that the performance level sits about mid-way between average and maximum. It's not so much “serverless,” therefore, as “less server-ish.” Maybe we should attach an asterisk to “serverless,” followed by a footnote: “May contain some traces of server.” The bigger question, though, is whether this is really “DevOps.” That is to say, does server-less-ness suggest that developers and operations professionals collaborate, or just participate in the same pipeline?

Shannon Williams (@smw355) & Sheng Liang (@shengliang), Co-Founders of Rancher Labs (@Rancher_Labs) join us this week on The Hot Aisle to talk about some more of that hot hot hot container stuff and how Rancher integrates your Docker ecosystem with automated deployments of Swarm, Kubernetes, and Mesosphere. Public cloud? Private Cloud? Don't care – they gots! […]

Brian talks with (@kelseyhightower; Kubernetes Lead @GoogleCloud) about confusion in the marketplace around Docker “compatibility”. Show Links: Get a free book from O'Reilly media or use promo code PCBW for a discount - 40% off Print Books and 50% off eBooks and videos Kelsey’s Github Page (code, training, workshops, demos) Kelsey on The Hot Aisle (podcast) Kelsey on Kubecast (podcast) Kelsey on Google Cloud Platform (podcast) Show Notes: Topic 1 - Welcome to the show. For anyone that doesn’t know you, tell us about your current role with Google Topic 2 - This tweet created quite a storm yesterday, https://twitter.com/kelseyhightower/status/758790198603845632. It felt like it started as an acknowledgement of the breadth of the ecosystem, but then went sort of sideways. Topic 3 - Break down some of the concepts in play for us - Container Format, Container Runtime, Open Container Initiative (OCI), etc. Topic 4 - Help explain some of this in laymen’s terms for us - isn’t the Docker code open source? Are we getting close to a point where people will have to fork this if they want to use other schedulers? Topic 5 - Shifting gears a little bit - Kubernetes for beginners - where to start? Feedback? Email:show at thecloudcast dot net Twitter:@thecloudcastnet YouTube:Cloudcast Channel

Fredrik talks to James Turnbull of Kickstarter, Docker and several other companies. Topics range from switching between types of companies and solutions to writing books, documentation and contributing to software in ways other than code. Of course, we also discuss Docker, whether it’s succeeded in various ways and where it might be going. Who should be thinking about Docker? How to start thinking about it? Where do you start picking on your monolith to start bringing it into the container future? This episode was recorded during the developer conference Øredev 2015, where James gave a presentation on Orchestrating Docker. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We are @kodsnack, @tobiashieta, @oferlund och @bjoreman on Twitter, have a page on Facebook and can be emailed on info@kodsnack.se if you want to write something longer. We read everything you send. If you like Kodsnack we would love a review in iTunes! Links James Turnbull Docker - the company and the software solution Puppet labs Public-benefit corporation Immutable infrastructure Docker swarm Docker compose Kubernetes Mesos Mesosphere Elasticsearch Memcached Redis Amazon cloudformation James' books William Gibson Dennis Ritchie Daniel Friedman Vagrant Jekyll Titles A lot of similar paralells The unit of the container A unit of compute I want my code to run somewhere where it makes me money A new way of thinking about architecture On the periphery of the monolith Useful information trapped in the heads of smart people My commits tend to be more documentation than code Aspects of being an engineer A higher level of tolerance and precision

Derrick Harris of Mesosphere talks with us about how data is changing the way businesses operate. The ability to capture data at quantity and analyze it at speed has enabled companies to create much more personalized experiences and develop competitive ad Learn more about your ad choices. Visit megaphone.fm/adchoices

Four years ago, the virtualization industry was blown wide open by the arrival of Docker — a format which made it possible to stage workloads and scale them without the overhead of VMware, Xen, or KVM virtual machines. Last year, Docker Inc. graciously donated its container standard to the Open Container Initiative, run by the Linux Foundation — a neutral governing party. The idea was to end all the bickering over what the container format should be. Instead, what's happening is a fresh re-opening of the debate over why there should be just one. “I think, a couple of years down the road, people are going to be talking less and less about containers, and people are going to be talking more and more about applications again,” said Ben Hindman, the founder and lead engineer of Mesosphere. What a bank in New York City really wants, said Hindman, is the opportunity to test an application on its data center the same way one of its executives tries out an e-mail client on her laptop. If data center apps became more analogous to mobile or desktop apps, the entire business of serving large enterprises could be revolutionized. “At the end of the day, what people care about. . . is being able to run these sophisticated, distributed applications. At least what I hope, in five years' time from now, everyone is talking about that as an ecosystem.” What we've been calling “container architecture” deals primarily with the packaging and constitution of containers — small, firmly packed virtual machines without the hypervisor. Up to now, a lot of folks thought container architecture and container orchestration were the same topic. They're not. The critical issue that data centers are facing today is how to network their workloads. In a container network, each container has its own address. Natively, Docker creates a subnet of containers, each of which has its own port number. For data centers where port numbers have specifically designated purposes — like port 80 for Web traffic — that won't work. They'd already be violating compliance frameworks just for trying this. That's why Kubernetes and Mesosphere and Docker have all adopted different means of orchestration, where each container is given its own IP address. There are different ways of doing this through network overlays, some of which scale better than others. But this does solve the problem with Docker's native networking. However, it also solves a broader class of problem, because VMs have their own IP addresses too. As long as IP addresses provide a layer of abstraction between virtual components and their orchestrators, the substance to the argument in favor of a single container format, disappears.

In another dynamic chat with Michael Hauselblas (@mhausenblas), a self-described Distributed Systems Jester, who is also a Developer and Cloud Advocate for Mesosphere.   Michael brings a very interesting background to the field, and we are able to touch on some very interesting topics in the open source product development lifecycle as a result.  I hope that you enjoy the chat as much as I did being a part of it. 

In this episode of The New Stack Analysts embedded below, The New Stack hosted a pancake breakfast at MesosCon in order to find out from some of the community's experts more about how Mesosphere and Intel are positioning their organizations for the future, and what developers interested in open source can do to help. Founder Alex Williams and co-host Benjamin Ball spoke with Murali Sundar, Principal Engineer in Intel's Software Defined Infrastructure Group, Ben Hindman, Mesosphere Founder & Chief Architect, and Jessica Frazelle, Mesosphere Software Engineer. Watch on YouTube: https://youtu.be/BrkDtVNiBwA Learn more at: https://thenewstack.io/abstraction-mesoscon-2016-pancake-breakfast/

Coding boot camps are a subject of controversy. Critics of boot camps defend the conventional university system, and argue that boot camp graduates do not have enough experience to write quality software. But the reality is that some boot camp graduates have found success from this new educational path. After graduating high school, Kenny Tran The post Boot Camps, Mesosphere, and Open-Source with Kenny Tran appeared first on Software Engineering Daily.

Coding boot camps are a subject of controversy. Critics of boot camps defend the conventional university system, and argue that boot camp graduates do not have enough experience to write quality software. But the reality is that some boot camp graduates have found success from this new educational path. After graduating high school, Kenny Tran The post Boot Camps, Mesosphere, and Open-Source with Kenny Tran appeared first on Software Engineering Daily.

The trio is back to talk about troubleshooting, how much fun it can be, and how to approach it, but first they share their widely respected opinions *scoff* about the ‘Race for the Container Space’, using DNA as your tier-4 storage media, and the promise of autonomous taxis. Newsy News Microsoft, Cisco, HPE love Mesosphere … Continue reading "Episode 5: Troubleshooting" The post Episode 5: Troubleshooting appeared first on Infotrek Podcast.

Earlier this week, Mesosphere announced the open source Datacenter Operating System, and NetApp is extremely excited to be a launch partner with them. Built on Mesos, the DC/OS uses open source technology fostered by Mesosphere to provide an environment for running containerized applications with ease. It provides a platform which current and next-generation applications can take advantage of—whether the application is built with microservices through and through, or uses big data analytics. This week we welcome a large crowd to the podcast to talk about the DC/OS launch.

This week we were thankful to have our good friend Will Freiberg join us on the Bowery Capital Startup Sales Podcast to discuss "Building The Open Source Sales Machine." Will is currently the Chief Business Officer at Mesosphere and was the first business hire into the company almost 2 years ago. He was highly influential in setting up the the sales, partnerships, and operations infrastructure teams and today heads up all of those efforts for the company. He came on to chat about how to build an open source sales machine and what has worked and not worked for his company. 

This week we were thankful to have our good friend Will Freiberg join us on the Bowery Capital Startup Sales Podcast to discuss "Building The Open Source Sales Machine." Will is currently the Chief Business Officer at Mesosphere and was the first business hire into the company almost 2 years ago. He was highly influential in setting up the the sales, partnerships, and operations infrastructure teams and today heads up all of those efforts for the company. He came on to chat about how to build an open source sales machine and what has worked and not worked for his company. 

We talk with Aaron Williams and Bruno Terkaly about Mesosphere, Docker and containers, the most important topic we've ever had on the show. Java developers are the saddest. Carl is a hipster.

In this Intel Chip Chat audio podcast with Allyson Klein: In this livecast from the Structure Conference in San Francisco Florian Leibert, CEO & Founder of Mesosphere talks about how he helped to build the next generation Twitter platform on an Apache Mesos project creating one of the first open platforms for turning a data […]

In this livecast from the Structure Conference in San Francisco Florian Leibert, CEO & Founder of Mesosphere* talks about how he helped to build the next generation Twitter* platform on an Apache Mesos project creating one of the first open platforms for turning a data center into a high performance and easy-to-use private cloud. He outlines how Mesosphere was started in order to help make Apache Mesos easier to use allowing users to deploy, manage and scale services, organizing their entire infrastructure as if it was a single computer. Florian highlights Mesosphere’s new Data Center Operating System (DCOS) that allow users to bring many data center services and applications onto a private or public cloud while avoiding vendor lock in. Florian also calls out the deep collaboration between Intel and Mesosphere including the Cloud For All initiative and other work that enhances Mesos and makes it more usable for a wide variety of use cases and workloads. To learn more, follow Mesosphere on Twitter https://twitter.com/mesosphere or message info@mesosphere.com.

Thomas Rampelberg, Project Manager at Mesosphere (@mesosphere) joins us this week on The Hot Aisle to talk about Mesosphere's Data Center Operating System (DCOS) and how it was created to enable your Public & Private Cloud to be more efficient, resilient, and automated. Your hosts Brent Piatti (@BrentPiatti) and Brian Carpenter (@intheDC) break down Apache Mesos (@ApacheMesos), […]

“The business of technology and the technology of technology are kind of converging if you ask me. And there is definitely a space for some publications that don’t have decades of technical debt in the software space.” Continue reading… The post Mesosphere and Tech Journalism with Derrick Harris appeared first on Software Engineering Daily.

Apache Mesos is an open-source cluster manager that enables resource sharing in a fine-grained manner, improving cluster utilization. Michael Hausenblas is a developer and cloud advocate with Mesosphere, which builds the Datacenter Operating System (DCOS), a distributed OS that uses Apache Mesos as its kernel. Questions Can you give the historical context for cluster computing? The post Mesos and Docker in Practice with Michael Hausenblas appeared first on Software Engineering Daily.

Description: Aaron and Nick Weaver (@lynxbat) talk with Derrick Harris (@derrickharris, Senior Research Analyst @mesosphere) about the latest in both the big data and cloud native apps using Mesos. Check out O-Reilly's new initiative: Learning Paths. Show Links: The Data Center Show Podcast SCALE Blog Topic 1 - Many of us know you for the excellent work you did at GigaOm. How did you end up at Mesosphere and what are you working on these days? Topic 2 - You write an excellent publication called “SCALE”, which is focused on large scale data centers and data analytics. What trends or new ideas are really interesting to you these days? Topic 3 - Big Data is an area that you’ve covered for a while. The data science skills are really difficult to find. Are you seeing anything that’s making it easier for companies to engage big data technologies? Topic 4 - Let’s get back to Mesosphere and Mesos. Is this a technology that we’ll see lots of customers using (large # of customers), or is it a smaller # of customers but with really large usage models? Topic 5 - Sometimes we wonder about revenue models for companies that are based on open-source projects. Did you understand this when you were an independent analyst, and how do you view it differently now that you’re at a vendor?

Aaron talks with Ben Hindman (@benh; Co-creator of ApacheMesos, Founder of @mesosphere) about his time at Twitter, building Mesos, understanding problems at scale, how Mesos compares to Kubernetes, Mesosphere DCOS and the recent announcements with Microsoft. Interested in growing your career and networking with professionals in the Data Center and Cloud industry? Attend John Troyer's The Reckoning event, in Half Moon Bay, CA on September 13-14. Cloudcast listeners can get $100 discount by entering promo-code: CLOUDCAST. Interested in the O'Reilly Velocity NYC? Want a chance at a free pass for VelocityConf NYC? Send us your interesting journey in Web-Scale Operations to show@thecloudcast.net by Friday July 10th and we'll pick a winner! Want to register for Velocity Conference now? Use promo code 20CLOUD for 20% off Check out the Velocity Schedule Free eBook from O'Reilly Media for Cloudcast Listeners! Links from the show: Dave Lester from Twitter/ApacheMesos on #155 Understanding Mesos Kenneth Hui’s Series on Apache Mesos Microsoft / MesoSphere Announcement Thanks for the MesosCon folks for having us! - MesosCon Homepage Topic 1 - Give us some of your background and how you went from working on Apache Mesos at Twitter to becoming involved with Mesosphere? Topic 2 - It’s been about a year since we talked about Mesos on the show. We’ve talked about Kubernetes a few times. Can you give us the basics of each of those technologies because sometimes people confuse them or think they are interchangeable or overlapping. Topic 3 - Let’s talk about Mesosphere and DCOS (Data Center Operating System). People talk about “durable and declarative” infrastructure for applications. How does DCOS accomplish this? Topic 4 - Mesosphere includes not only systems and schedulers for the underlying container infrastructure, but also application-level schedulers. What are the differences, and how does a development team vs. an ops team interact with Mesosphere? Topic 5 - What types of applications are you seeing Mesosphere customers running in this new environment? One thing we heard at VelocityConf was that there is work within Apache Mesos to look at adding support for stateful applications or stateful data - what’s the status of that?

Tobi Knaup, co-founder & CTO of Mesosphere joined the show to talk about the datacenter operating system, and all the open source around it.

Tobi Knaup, co-founder & CTO of Mesosphere joined the show to talk about the datacenter operating system, and all the open source around it.

Das Kamhout, Principal Engineer and SDI Architect at Intel joins us to announce Intel’s launch of the Cloud for All initiative founded to accelerate cloud adoption and create tens of thousands of new clouds. He emphasizes how Intel is in a unique position to help align the industry towards delivery of easy to deploy cloud solutions based on standards based solutions optimized for enterprise capability. Das discusses that Cloud for All is a collaborative initiative involving many different companies including a new collaboration with Rackspace and ongoing work with companies including CoreOS, Docker, Mesosphere, Redapt, and Red Hat.

Aaron talks to Cole Crawford (CEO/Founder of Vapor.io, Founding executive director of Open Compute project and Co-founder of OpenStack) about momentum for Open Compute, rethinking how Data Center racks are designed, and the Vapor.io stack - OpenMist OS, Open DCRE and CORE. Interested in the O'Reilly OSCON? Want to register for OSCON now? Use promo code 20CLOUD for 20% off Details to win an OSCON pass coming soon! Check out the OSCON Schedule Free eBook from O'Reilly Media for Cloudcast Listeners! Check out an excerpt from the upcoming Docker Cookbook Links from the show: Vapor Homepage - http://www.vapor.io/ Topic 1 - Tell us about your background. It’s very extensive in both open source (software) and open hardware. Topic 2 - The company is described as “the first hyper converged and truly data defined data center solution”. Please translate that for us :) Topic 3 - For a small company, you have some large (conceptual) offerings - common hardware, rack-level provisioning, and this unique new rack model. Just how ambitious are you guys? (hardware with API’s!) Topic 4 - OpenMist OS (just launched). Let’s talk about each of the core pieces - Open DCRE (Data Center Runtime Environment). Is this an open BMC (Board Management Controller)? Topic 5 - Vapor CORE - This seems like RAID (Storage) meets BGP / HSRP (Networking) and compute scheduling (vCenter) all mashed together, with APIs to higher-level services (eg. Mesosphere or Docker) Topic 6 - Vapor Chamber - at first glance, this seems like The Big Green Egg (grill) for data center equipment. Fair analogy? Music Credit: Nine Inch Nails (nin.com)

What does an operating system for today's datacenter look like? Why do we even need one, and how does it function? Mesosphere's Benjamin Hindman, the co-creator of Apache Mesos, joins Steven Sinofsky for an all-OS discussion. The views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. This content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments and certain publicly traded cryptocurrencies/ digital assets for which the issuer has not provided permission for a16z to disclose publicly) is available at https://a16z.com/investments/. Charts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.

What if your laptop asked you which core you would like to run Word in today? Sounds archaic, but that's the current state of the art with server infrastructure. You still have to pick with virtual machine you want to put your Rails app in. Florian Leibert's mission at Mesosphere is to create a smart infrastructure mesh that lets developers no longer have to think about which piece of code should run where. Hear how he plans to do this on this week's episode.

Peter Levine goes deeper into the changing nature of the data center with Yoram Novick, CEO of Maxta, and Florian Leibert, CEO of Mesosphere. Does ARM architecture, the foundation of the chips in practically every mobile phone, have what it takes to displace X86 processors in the data center? Is the private cloud --- effectively a company operating its own data center -- dead, or will a hybrid public/private cloud model dominate? Given all the upheaval in the data center how do startups fit into the equation, and how are they competing today with legacy technologies and companies? The views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. This content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments and certain publicly traded cryptocurrencies/ digital assets for which the issuer has not provided permission for a16z to disclose publicly) is available at https://a16z.com/investments/. Charts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.

Tune in LIVE with radio hostess Sandra LONDON of Playtime With Sandra Radio tonight at 8pm Pacfic Standard Time. Tonight's features include: A live reading of  travel essay AmsterDamn ... and perhaps a few other travelogues, as well as the latest in current events, news, LiveAndGrind happenings and stratospheric meteorites!    Talk To You Soon, Sandra LONDON of LIVEANDGRIND

Episode #012 | Revive 012 with music from 9b0, Wrexx, Mesosphere, Orzels Machine, B-Phreak, 4Kuba, Ways & Means, Kultur and Colombo and Flack.Su! In the second hour you can listen to Home Alone's exclusive guest mix. PART 1 - RETROID 01.Stefan Anion - Imagine (9b0 Remix) [Silk] 02.Mesmer - Cubes (Wrexx Remix) [Scarcity] 03.Tarrentella - Saturn (Mesosphere Mix) [Whoop!] 04.Orzels Machine - Torque Is Cheap (Original Mix) [Trick Music] 05.B-Phreak - Bulletproof (Original Mix) [Dusted Breaks] 06.4kuba - Lonedog (Original Mix) [High Grade] 07.Ways & Means - Electronic [Bombtraxx] 08.PREAMP - Koi Fish (KULTUR COLOMBO Remix) [Metamorph Muzik] 09.Andy Craze - Lipsync (Wrexx Remix) [Optimal Records] 10.Flack.su - No Cure (Original mix) [Glack Audio] PART 2 - HOME ALONE 01.Run Riot - Everybody Needs A Bassline 2 (Original Mix) [We Are Live] 02.Ek - Exit Enlightenment (Kraymon Remix) [Dead Famous] 03.Home Alone - Asshole (Original Mix) [Ego Shot] 04.Home Alone - The Playground (Original Mix) [Ridiculoud] 05.Yadek - Believe In Me (Retroid Remix) [Ego Shot] 06.Home Alone - The Sound (Breakz Mix) [V.i.m. Breaks] 07.Home Alone - Visitors (Original Mix) [V.i.m. Breaks] 08.Robosapiens - Bodies (Hedflux Remix) [Dead Famous] 09.Leuce Rhythms - Headroot (Your Love) [Scarcity] 10.Ways And Means - Kik A Hole (Original Mix) [Dusted Breaks] 11.Home Alone - Drop It (Original Mix) [Dead Famous] 12.Mr. B - Little Acid People (Peo De Pitte Remix) [Rogue Industries]