Podcasts about puppet labs

It's all good news, we promise! The Forge has always been the go-to spot for Puppet users to find, download, and update content and modules. On this episode, we're revealing a few of the exciting changes that are going to make the Forge even easier and more valuable for all Puppet users, like personalization, filters, and features to track module versions and updates against your Puppet file.As of today, there are 7,508 modules on the Puppet Forge – some active, some deprecated, some created and supported by Puppet Labs, some by community groups like Vox Pupuli. While it's become a hub for all Puppet users, we've heard feedback on ways it could be even better. We see a brighter future for the Forge – one built for and shaped by users like you! Join Ben Ford as he talks to Forge Product Manager Saurabh Karwa about what the Forge is today, the subtle changes that are already in the works, the near-term roadmap, and the long-term vision for the Forge.Speakers:Ben Ford, Community Lead at Puppet by PerforceSaurabh Karwa, Product Manager at Puppet by PerforceHighlights:Introducing Saurabh, the Product Manager for the Puppet ForgeWhat the Forge is today and what it needs to become THE place for Puppet usersThe role of the Puppet Community in shaping the future of the ForgeAdding personalization, new filters, and features to track module versions and updatesWhy you should join our new Ecosystem Advisory BoardLinks:Join the Puppet Community SlackTell us what you think of the Forge and PDK with the Ecosystem Advisory Board surveyEmail Saurabh at skarwa@perforce.com

Today's guest is Kelsey Hightower, a distinguished engineer and developer advocate at Google and speaker known for his work with Kubernetes, open source software and cloud computing.As a curious and motivated self-learner, Kelsey dropped out of College and taught himself the skills required to start his career as an independent contractor for BellSouth – a telecoms company in Atlanta helping the community to get online. From there, Kelsey set up his own business – an electronics store before becoming involved in the open source world, working at New Relic, CoreOS, Puppet Labs, and most recently at Google.A self-taught developer, Kelsey's work on Kubernetes and at Google, from which he just retired, is well-known* so I wanted to focus our conversation on his life - how he got into tech, his love of learning, what drives him, what it means to be hopeful and the one piece of advice he would offer a younger Kelsey.I know I am not meant to have favourites – these conversations are like children - but I have to say this is up there with one of my most loved conversations. I learned so much from Kelsey and I think you will too.Enjoy!Kelsey on TwitterDanielle Twitter / Instagram / NewsletterPhoto of Kelsey is part of the Faces of Open Source Project by Peter Adams*If you want to learn more about Kelsey's work history, give this episode  from Ardan Labs a listen.

When you think of Kubernetes or Docker, I bet empathy is not the first word that comes to mind. Today, I am joined by, Kelsey Hightower whose passion it is to bring empathy to work everyday and we talk about how to reframe our approach to building tools for humans, learning from the physical world, config management, containerization and more. Kelsey earned his CompTIA A+ certification and began his career working at BellSouth installing DSL. He has worked at Puppet Labs, Monsoon Commerce (where he wrote his open source config management library Conf'd ), and currently he is a Distinguished Engineer, Google Cloud.  He is a leading expert and advocate in Kubernetes and is known in the tech community as the explainer and chief of Kubernetes having spoken at many many conferences and even co-founding the Kubernetes-focused KubeCon conference. He is also a published co-author of the book Kubernetes: Up & Running. He likes to say he is a SysAdmin who can code and a big part of his day is spent elevating people. Enjoy our conversation! Connect with Kelsey: Twitter Show notes and helpful resources: Meet Kelsey Kelsey's book: Kubernetes: Up & Running “If there is a problem do what is necessary to solve it no matter what” “You do your best work when you are at your best” Brian Grant - Chief architect of Kubernetes Kim Bannerman - People first empathetic leader “A 10x engineer can make 10 people better - level up the people around you” “Always seek to understand why you do what you do” “Continue to grow by observing the world around you and make adjustments so you can make an impact” Building something cool or solving interesting problems? Want to be on this show? Send me an email at jointhepodcast@unfilteredbuild.com Podcast produced by Unfiltered Build - dream.design.develop.

When you contribute to open source projects, Dawn Foster makes it abundantly clear that even if “you’re there on behalf of [a] company, you need to do the right things for the community.” In this episode of Community Signal, Dawn outlines the principles that she follows and shepherds as the director of open source community strategy at VMware’s Open Source Program Office. These principles foster projects and communities that are collaborative and encouraging, but of course, it does not always pan out that way. Dawn discusses how documentation and education, having a clear commitment from the company managing the open source project, and balancing for collaboration instead of number of contributions can all help to build healthy open source communities. Unlike social platforms that optimize for getting everyone to contribute an infinite amount, open source projects rely on spreading knowledge and contributions amongst the group. “In some cases we have open source projects [where] almost all of the contributions are made by a single individual. What happens if that individual wins the lottery and leaves VMware, and doesn’t want to work on this project anymore?” That’s a great question for all of us that manage communities. If our top contributors left tomorrow, who would pull the community forward? Patrick and Dawn also discuss: Evaluating open source community health The tools and documentation that help with governance Evaluating the risk of contributing to an open source project Our Podcast is Made Possible By… If you enjoy our show, please know that it’s only possible with the generous support of our sponsors: Vanilla, a one-stop shop for online community and Localist, plan, promote, and measure events for your community. Big Quotes Good documentation begets good contribution practices (7:00): “Even though I’ve been contributing to open source projects for years, every time I pop up in a new community, I still have to read the contribution docs because there will [always] be something that project does in a very specific and nuanced way that the last project I worked on didn’t do. In a lot of cases, people just make mistakes and they don’t really think about what they should have been doing. They just need a little more education.” –@geekygirldawn Illustrating contributor risk (18:37): “Some of these big open source projects are maintained by fewer people than you might think. The biggest example I can think of was OpenSSL. There was a huge security vulnerability in OpenSSL. It’s a technology that almost every single company in the world relies on. This vulnerability was going to require a lot of time and effort to fix. What we quickly realized was that OpenSSL was maintained part-time by two people, none of whom were being paid to work on it.” –@geekygirldawn To truly be open source means to cede a bit of control (23:20): “You don’t, as a company, want to dominate the entire [open source] project because if you do that, you might as well never have open sourced it. You might as well have kept it proprietary. The whole purpose of open sourcing it is you collaborate together, and you innovate, and you get ideas that you wouldn’t have otherwise had as a company.” –@geekygirldawn Open source thrives through collaboration (26:41): “Some of the more social platforms, it’s like the more social, the better. Collaboration doesn’t necessarily work that way. You don’t get more collaboration because I did more stuff. You get more collaboration because you got more people involved, and you gave them some space to contribute.” –@geekygirldawn The benefit of neutral foundations for open source projects (29:42): “What you get by putting [an open source] project into these neutral foundations is some assurance that everybody’s working together on a level playing field. If I want to contribute to a Linux Foundation project, I can rest assured that I can participate on the same field as everybody else. Whereas, if the project is owned by a particular company and they have their own agenda that may or may not align with the community’s best interest, they may take things in a different direction. They may not accept your contribution because it competes with something that they have.” –@geekygirldawn About Dawn Foster Dawn Foster is the director of open source community strategy within VMware’s Open Source Program Office. She is on the board of OpenUK, an organization committed to developing and sustaining UK leadership and open technology. Dawn is on the governing board and is a maintainer for the Linux Foundation’s CHAOSS project and the board of advisors for Bitergia. She has 20-plus years of experience at companies like Intel and Puppet Labs, with expertise in community building strategy, open source software, metrics, and more. Dawn holds a PhD from the University of Greenwich, along with an MBA and Bachelors in Computer Science. She has spoken at dozens of industry events, including many Linux Foundation events, OSCON, SXSW, FOSDEM, and more. Related Links Sponsor: Localist, plan, promote, and measure events for your community Sponsor: Vanilla, a one-stop-shop for online community Dawn Foster on Twitter VMware’s Open Source Program Office OpenUK Fast Wonder, Dawn’s blog Pivotal, which was acquired by VMWare The Social Dilemma Tristan Harris Dirk Hohndel, VMWare’s Chief Open Source Officer The Linux Foundation The Apache Software Foundation Transcript View transcript on our website Your Thoughts If you have any thoughts on this episode that you’d like to share, please leave me a comment, send me an email or a tweet. If you enjoy the show, we would be so grateful if you spread the word and supported Community Signal on Patreon.

Many companies see the benefits of diversity and inclusion but don’t know that their own policies and culture are often the reason that women and people of color don’t come on board. James Turnbull, VP of Engineering at Glitch, is passionate about this issue and offers advice on how he advises companies to bring on more diverse talent.James also talks to Peter about how he approaches growing individual contributors to team lead positions and why he would never stay at the same company for ten years. [00:20] - Moving up the hierarchy in early-stage startups[02:41] - Leading cross-functional teams at Puppet Labs[04:47] - Growing the engineering team at Kickstarter[11:50] - Getting people to think about their work differently[13:30] - Stepping out of the comfort zone[15:27] - Attracting the best engineers[18:46] - Building a pipeline of diverse talent with an inclusive culture[22:43] - Communicating with teams as they start to scale[25:17] - Developer advocacy, education, and hiring[29:19] - Do more listening than talkingCTO Connection is where you can learn from the experiences of successful engineering leaders at fast-growth tech startups. Whether you want to learn more about hiring, motivating or managing an engineering team, if you're technical and manage engineers, the CTO Connection podcast is a great resource for learning from your peers!If you'd like to receive new episodes as they're published, please subscribe to CTO Connection in Apple Podcasts, Google Podcasts, Spotify or wherever you get your podcasts. If you enjoyed this episode, please consider leaving a review in Apple Podcasts. It really helps others find the show.This podcast episode was produced by Dante32.

How we tame Google Cloud resources with R2D2. We had some episodes on the cloud already. Now it's time to discuss how bol.com combines the promises of the cloud and their requirements for Reproducibility and Reliability.What this episode coversFor instance, balance infinite resources and ultimate autonomy with security.Within bol.com we developed R2D2. R2D2 stands for our Reproducible Resource Deployment Definition tool which combines the functions of Terraform, Cloud SDK and Puppet Labs.It helps us to ensure Recovery, Security, Self-service, Stability and Scalability in our move to the cloud.The reason we think we need to secure these aspects: Bol.com has over 100 scrum teams innovating our IT-landscape with over 500 services. We must secure our 10 million customers' data and the data of our 23.000 sellers.GuestsJeroen Schutrup; Site Reliability Engineer in the team that develops the R2D2.Quiran Storey; Site Reliability Engineer - just like Jeroen solving operation problems with software solutions.NotesOverview of the R2D2 architecture(Image: https://cdn.sanity.io/images/qxrxmo3r/techlab-prd/cd7a5b48d10ef97931e5f3b4b6e6fcd816114ff3-569x380.jpg)Google Cloud (GCP)Google Cloud SDKThe main orchestration tool PuppetTerraformPythonOther cloud episodes and blogs:Redesign for the CloudCloud enables data-drivenMove data in the cloud with StanleyShopify's story during SRE 2018 in Dusseldorf

GUEST BIO: Kelsey Hightower has worn every hat possible throughout his career in tech, and enjoys leadership roles focused on making things happen and shipping software. Kelsey is a strong open source advocate focused on building simple tools that make people smile as well as an occasional conference speaker. EPISODE DESCRIPTION: In this episode Phil speaks to Kelsey Hightower, who is known in the industry as an innovator who makes things happen. He strongly believes in the power of the community, so works on bringing people and motivating them to produce products that truly work. He is currently working on the GoogleCloud project and is a popular technical workshop speaker and teacher, who believes in and advocates the use of Open Source products. KEY TAKEAWAYS: ­­­ (00.59) – So Kelsey, you can I ask you to expand on that brief summary and tell us a little bit about yourself? Kelsey explains that he has been in tech for about 14 years with various companies including Puppet Labs and Chrome OS. He is currently working at Google making sure that all elements of the Google Cloud work together. Kelsey says he is working on the computer side of the house, on everything from Kubernetes to the Google service platform. He now describes himself as a generalist. Phil described Kelsey’s role as creating “seamless integration from a user perspective” (2.00) – Phil asks Kelsey for a unique IT career tip. Surprisingly, Kelsey’s tip is to “write it down”. In IT we tend to do things on the fly. Often, we do this because we are trying to minimize outage time. Sometimes it is because we want to implement change and feel we need to move quickly to keep everyone on board. Operating like this means that, often, we do not come up with the right solution. In the long-term this can turn out to be a big problem. It is important to stop, sit down and capture all the facts and consider the pros and cons of your proposed solution. You also need discuss the idea with others. For this a document acts as a great reference point. It also enables you to look back and understand why you made the decisions you did. (3.25) – Phil asks - Do you see that as an iterative process, as well? Kelsey agrees often these projects can span many years. Over that time, things will change so the objective or goal can also evolve. But, that document you created captures the current situation. It does not mean that you should never change your opinions and the direction you take. (4.24) – Phil asks - do you see it as a problem in IT generally that people don’t necessarily think too far ahead in terms of what the future might look like? In IT people tend not to take the time to document why things are done the way they are. Plus, they do not always work to push things forward. When someone asks them to change, their immediate response is that “it is not possible”. But, when you ask them to explain why the change is not viable, they do not really know. They just know that things have always been done that way and can be resistant to change. (5.31) – Kelsey is asked to share his worst career moment with the audience. For Kelsey it was the moment that he realized that to be able to make progress on a project you have to convince people that things need to happen. The realization put out a flame for him. Prior to that, he believed that he could just make things happen. He was a bit disappointed to realize that he had to overcome people’s resistance to get things done. But, he soon adjusted and learned to do both. So, in the end his worst career moment resulted in a positive change for Kelsey. (7.10) – Phil asks Kelsey what his best career moment was. Kelsey explained it was the day he first spoke publically at a meetup in Georgia Tech. He did a lot of preparation for that event, so that he could make his points concisely and take the entire audience, including the newcomers, with him. It went really well and he got great feedback. That day inspired him and set the scene for the rest of his IT career. Today, he enjoys seeing the light bulbs going on as the audience “gets it”.   (10.11) – Phil asks Kelsey what excites him about the future of the IT industry. Kelsey responds “the potential”. Today, it is possible for a newcomer or new business to come along and use some of the existing systems to get what needs to be done. They do not have to worry about legacy systems and integrations. It is possible to install a modern system that just works and takes care of the basic functions, leaving the new firm to focus on growing their business.   (11.55) – What attracted you to a career in IT? When Kelsey started his IT career, you did not need a college degree and you could earn very good money. Both of these facts attracted him to the field. Working in IT is a great way to connect with others, make a difference and be rewarded financially for your efforts. (12.46) – What is the best career advice you have been given? Definitely, “write it down.” If you believe something is the solution write down why you think that is the case. Doing so allows you to see things clearly and makes it easier for others to consider your proposal and challenge it if necessary. This greatly improves your ability to identify and implement the right solution for the situation. (13.48) – If you were to start your IT career again, right, now, what would you do?  Kelsey said that it is important to understand that the fundamentals are more important than the products. If you dive deep and learn the fundamentals of a product you can operate well in most environments. Phil summed it up by saying the technologies may not last but the fundamentals are always of value. (15.05) – Phil asks Kelsey what he is currently focusing on. Kelsey says he is just working on being a little better every day.  Each day he pauses and spends a little time analyzing what happened and how he can improve. He is also focused on building up his technical ability and becoming a real expert in certain areas. Kelsey is now willing to go deep. He is not just taking the “happy path” and learning what can be done with his chosen technologies he is also studying its limitations, so he can recognize when not to use it. (16.22) – What would you consider to be your most important non-technical skill? Kelsey says his genuine positivity keeps him excited about the projects he is working on and what he is learning. He is able to pass that positivity on to others, which motivates them. Making people feel good about themselves inspires them and pushes them to be more effective. (17.19) – Phil asks Kelsey to share a few final words of career advice. In IT you need to push yourself, to think outside of the box and over deliver. Kelsey explained that he has come across people who just take a task and do exactly the task. They do not look beyond it and never ask themselves if they could come up with something even better than what is being asked for. As a result, they stagnate and do not really grow. They end up spending 15 years in a role, but only accrue the equivalent of one year’s experience. Don’t be afraid to “automate yourself out of a job”, there will always be more work to do, better work. You need to be creative and innovative when you work in IT not just someone who blindly does a list of tasks. BEST MOMENTS:  (5.22) KELSEY –"Noone is really sure why the process exists. There's no clear place with the processes defined, so we know how to improve it. I think that's one of the biggest problems we see today."   (6.49) KELSEY - "A lot of cases, you would actually spend more time doing the convincing than the actual solution takes." (9.09) KELSEY - "You can see the light bulb go off for some people for the very first time and you know that those communication skills are working." (9.53) KELSEY - “You have to learn how to create the light bulb moment for yourself before you can create them for other people." (15.05) - Phil – “The technologies won't last but the fundamentals are always of value.” (15.18) KELSEY – “Just be a bit wiser every day.” CONTACT KELSEY HIGHTOWER: Twitter: https://twitter.com/kelseyhightower @kelseyhightower

Interview with Sanvy Sabapathee, Sales Engineer @ Puppet Labs. Sanvy describes the Puppet architecture for delivering automation across the Enterprise and Cloud. We define infrastructure as code & compare Puppet with other automation platforms.

Today we have another great bonus episode featuring Glenn Winokur, Senior Advisor to Healthbox. Before Glenn came on board with Healthbox, he was Co-founder and CEO of Syapse, a company which he Incubated from an idea in a Stanford class to a market leading venture funded start-up that provides a precision medicine data platform enabling healthcare providers to use molecular profiling to diagnose and treat patients. Under Glenn’s leadership over an 8 year period, Syapse raised over $40m in venture funding. Prior to Syapse, Glenn was the CEO of Scalix and Chief Operating Officer of NetIQ, respectively. In addition to Healthbox, Glenn is an advisor to the University of Illinois, Stanford University, and UCSF. And with all this experience, Glenn has become an angel investor with investments including Puppet Labs, Cloud Sherpas (now part of Accenture), SchoolMessenger (now part of West Corp), Syapse, and Panthenon. In today’s episode we cover: Glenn’s background and  role with Healthbox The story behind Glenn’s first investment and how did he arrived at the financial position to do so What draws Glenn to investing in Healthcare and why The key things Glenn wants to see if a company that he invests in How important Glenn’s background scaling companies and acting as CEO has been in his investing strategy What Glenn thinks entrepreneurs should consider about when raising from angels Connect with Glenn: LinkedIn Twitter Connect with Healthbox Follow us on Twitter and @ChuckFeerick Subscribe and leave a review in iTunes Have guest suggestions or topic ideas for the podcast? Send them to us at ideas@healthbox.com Listen to this episode on iTunes, SoundCloud, or Libsyn

James Turnbull joins John and Damon to chat about monitoring, automation, and the changing art of operations. In addition to his current work as a practitioner (Kickstarter) and past as vendor (Puppet Labs), you might also have read some of James's popular books on Monitoring, Puppet, Logstash, Docker, and Linux.

Special guest Eric Sorenson of Puppet Labs chats with Matt about all the new hotness with Puppet, including Application Orchestration. Plus, Matt and Eric put on their pundit hats and talk about the acquisition of Ansible by Red Hat.

Special guest Eric Sorenson of Puppet Labs chats with Matt about all the new hotness with Puppet, including Application Orchestration. Plus, Matt and Eric put on their pundit hats and talk about the acquisition of Ansible by Red Hat.

V druhém díle natáčeném v kancelářích Puppet Labs jsme si povídali pouze o technologickém pozadí toho, co v Plzni řeší. Zkoušeli jsme kluky zatáhnout do diskuse na téma konkurenčních nástrojů, ale nenechali se :) Pokud chcete tedy trošku hlouběji nakouknout do technické kuchyňky, ve které se vaří Puppet Enterprise, zastavte se s námi na šálek kávy.

V tomto díle jsme zavítali do kanceláří Puppet Labs v Plzni. Čekali nás tam Michal Růžička, Michal Bryxí, Filip Hrbek, kteří nám pověděli něco o tom, jak v Čechách otvírali první světovou pobočku americké firmy Puppet Labs. Povídali jsme si o tom, jak se vyvíjí Puppet Enterprise a co to vlastně znamená pracovat na dálku pro podobnou společnost.

Where is your DevOps practice at? Richard catches up with Gene Kim, the godfather of DevOps, to recap 2014 and talk about what DevOps in 2015 is going to be like. But you can't look into the future without being informed by the past, and Gene points to Puppet Labs 2014 State of DevOps Report as a way to understand the impact DevOps has had so far, and where things are going. The discussion also digs into the DevOps Enterprise Summit held in October 2014, you can see the sessions on YouTube at www.youtube.com/user/DOES2014. The DevOps Movement is progressing - are you coming?

In this episode of the Blacks In Technology podcast, Greg and Ayori are joined by CIO/VP of Operations at Puppet Labs, Nigel Kersten. Listen as we talk about the Puppet configuration management tool, diversity and hiring practices in technology, DevOps and much more. Follow Nigel at @nigelkersten

In this episode of the Blacks In Technology podcast, Greg and Ayori are joined by CIO/VP of Operations at Puppet Labs, Nigel Kersten. Listen as we talk about the Puppet configuration management tool, diversity and hiring practices in technology, DevOps and much more. Follow Nigel at @nigelkersten

Aaron and Brian talk with Nick Weaver (Office of CTO, EMC), Dan Hushon (Distinguished Engineer, EMC), Teyo Tyree (Founder, Puppet Labs) and Nigel Kersten (CTO, Puppet Labs) about the “Razor Project”, a new open source project for Cloud Automation between EMC and Puppet Labs.