Hi [[ session.user.profile.firstName ]]

Puppet

  • Date
  • Rating
  • Views
  • The DevOps Playbook: How to Start, Scale, and Succeed
    The DevOps Playbook: How to Start, Scale, and Succeed
    Alanna Brown, Nigel Kersten & Andi Mann Recorded: Jun 19 2019 58 mins
    Real-world guidance from the 2018 State of DevOps Report.

    Over the past few years, Puppet’s annual State of DevOps Report has shown that DevOps practices have a positive impact on business results, improving speed, agility, security, and stability. This link is widely acknowledged; what’s less clear is how to achieve these results.

    Our 2018 State of DevOps Report is a prescriptive guide to achieving DevOps success: from building the foundation to scaling across teams. Based on the experiences of over 3,000 survey respondents, we’ve mapped distinct phases of the evolution and the key practices needed to advance to each stage.

    In this webinar, the report’s authors discuss findings from the report, the five stages of DevOps evolution, and how they apply to your organization.
  • Puppet Product Announcements
    Puppet Product Announcements
    Deepak Giridharagopal, CTO & Chief Architect at Puppet Recorded: Feb 26 2019 44 mins
    Deepak Giridharagopal, CTO & Chief Architect at Puppet, shares the latest product announcements from Puppet. Learn how to expand your automation from infrastructure to application delivery.
  • Ops Hates Containers. Why?
    Ops Hates Containers. Why?
    Martin Alfke, CEO, example42 GmbH Recorded: Feb 26 2019 25 mins
    “Docker, Docker, Docker, Docker…”

    Developers really love Docker. One might think configuration management is no longer needed due to the ease of spinning up the platform on a laptop with a low-resource footprint. But how do you deploy laptops in data centers? This talk will give you an insight into how we (more Ops then Dev) started to learn (and love) containers, the issues we saw when running them in larger scale, how Ops people should start dealing with Container technologies, and why Puppet is still needed.
  • Building a DevOps Pipeline with AWS
    Building a DevOps Pipeline with AWS
    Mark Rambow, Software Development Manager, Amazon Recorded: Feb 26 2019 25 mins
    This session will walk you through building your DevOps pipeline with the AWS Development and Management tools. We will leverage AWS CodePipeline to create a setup that allows us to automatically test and promote infrastructure changes to production. We will use AWS CloudFormation for resource provisioning, AWS OpsWorks for Puppet Enterprise for on-instance configuration, and AWS OpsWorks for Puppet Enterprise and AWS Config for monitoring and compliance. With these tools we will be able to create a fully automated pipeline to deploy, manage, and scale the AWS environment.

    We'll cover how to:

    - Employ DevOps practices and treating infrastructure as code makes it easy to share, test, and enforce changes across AWS
    - Discover the benefits of automation when creating, scheduling, and reviewing releases for environment change
    - Gain situational awareness and drive change with confidence
    - Orchestrate changes to infrastructure and applications
    - Continually enforce your desired state and remediate any unexpected changes
    - Get real-time visibility and reporting to prove compliance
  • We're in This Together: Lessons from Growing a Collaborative Culture
    We're in This Together: Lessons from Growing a Collaborative Culture
    Martin Jackson, Distinguished Systems Engineer, Walmart Recorded: Feb 26 2019 28 mins
    How does one of the largest companies in the world scale automation and DevOps practices across their enterprise? At Walmart, we started small with a 3-person team of engineers, automating one resource at a time across tens of thousands of servers. We learned that small changes can have a big impact, and three years into our journey, we’ve automated tens of millions of resources across almost one hundred thousand servers spanning stores, data centers and distribution centers around the world. But the real victory has been helping other teams adopt automation and building an internal community of Puppet users which has helped us scale our automation efforts beyond what our small core team of developers could do alone.

    In this session you’ll learn:

    - The practices that were critical to scaling our success, including some overlooked practices like documentation
    - How we measure success, especially for things that are hard to measure, like culture
    - Lessons learned throughout the journey and how to apply them to your business, including some mistakes we made along the way
    - How we plan to expand automation to more teams in the future
  • Puppet + Google Cloud: Migrating to the Cloud with Puppet
    Puppet + Google Cloud: Migrating to the Cloud with Puppet
    Alex Stephen and Nathan McKinley, Software Engineers, Google Recorded: Feb 26 2019 23 mins
    The easiest tool to use is the tool you already understand. As you migrate to the cloud, the quickest route to building a scalable, complex deployment is using the same pipelines and tooling that you use on-premises. Google + Puppet have been building out a series of modules that allow you to construct your cloud infrastructure quickly using Puppet. You will learn how these modules will help you migrate quickly to the cloud, help you effortlessly scale your workflows, and leverage your institutional Puppet knowledge.
  • Why Kubernetes Won't Save Your Application
    Why Kubernetes Won't Save Your Application
    Carl Caum, Product Manager, Puppet Recorded: Feb 26 2019 25 mins
    Modern packaging and deployment technologies won't make great applications. This talk will focus on how to build reinforcing cultures of experimentation and learning to better meet your customers' needs.
  • The Hows and Whats of Service Monitoring at CERN
    The Hows and Whats of Service Monitoring at CERN
    David Moreno García, DevOps Engineer, CERN Recorded: Feb 26 2019 22 mins
    The CERN IT infrastructure is spread across different countries providing different resources for physics computing, analysing the petabytes of data from the Large Hadron Collider and other experiments. We have approximately 40k Puppet managed nodes and more than one hundred virtual machines providing the necessary infrastructure to support this. Monitoring has become a key aspect of our daily operations, allowing us not only to identify problems in real time but also to narrow down the causes of them. In the long term it is also a key asset in the planning for the future and the improvement of the efficiency of the team.

    This session is focused on showcasing how we monitor our Puppet infrastructure (using tools like ElasticSearch, collectd, Flume, Kibana and Grafana among others), and how this has helped us in real situations.
  • Postmodern Puppet: Puppet Enterprise 2019 and Puppet 6
    Postmodern Puppet: Puppet Enterprise 2019 and Puppet 6
    Eric Sorenson, Director of Product Management, Puppet Recorded: Feb 26 2019 29 mins
    Learn about the brand new version of Puppet Enterprise, PE2019. It's built on the latest open source Puppet 6 Platform and includes a host of new features, usability improvements, performance enhancements, and bug fixes.
  • Scaling DevOps Success Before Cynicism Takes Over
    Scaling DevOps Success Before Cynicism Takes Over
    Michael Stahnke, Director of Engineering, Puppet Recorded: Feb 26 2019 27 mins
    You’re winning with DevOps, now what? For the last decade we’ve seen case studies on high-performing teams who’ve implemented DevOps practices. How does this scale beyond the team? How do we influence skeptics? Let’s look at scaling out success when the point of reference is larger than the team. Success using DevOps practices has been unevenly distributed. Some teams claim success while their colleagues and peers struggle with basic technology delivery. For the organization as a whole, continuing to improve optimized areas results only in local gains. The true promise of DevOps was to globally optimize technology delivery. How do you scale? How do you influence others teams, or a whole department? How do you overcome blockers that were originally seen as beyond your scope of control?

    This discussion will walk through scaling DevOps practices beyond the team or small number of teams by upleveling the discussion to focus on department or org-level patterns. This scaling will cover grass-roots expansion of success, the trade-offs of a top-down mandate, and forcing functions to steer multiple groups of people on their aligned goals. There are still metrics to use when looking at DevOps from a larger perspective, and those are covered as well.

Embed in website or blog