Join Carl Caum, Puppet’s senior product manager, as he takes you through the challenges and complexities of managing a complex infrastructure that various organizations are facing, especially when you have a huge team with conflicting initiatives, such as ops team v.s security teams v.s. business teams.
2. Agenda
• Part 1
• Introducing Puppet
• Current state of managing infrastructure
• Challenges and complexities
• Solutions built for scale
• Part 2
• Solution overview
• Capabilities and features
• Demo
2
3. Experience Pioneer in DevOps, founded in 2009
Scale More than 10 million nodes managed
Community 6,000+ community-contributed modules, 7.5M lines of code
Users 40,000+ organizations
Locations Offices in Belfast, London, Portland, Singapore, Sydney, and Timisoara
Investors
About Puppet
We have a strong business foundation.
4. 30,000+ people contribute to the
State of DevOps report; millions
benefit from the learnings.
It’s one of the longest running
and the largest body of DevOps
knowledge globally.
We are a leader in DevOps…
5. Current state of managing infrastructure at scale
Balancing act to move fast and move safe
• Risk vs. speed to deliver added value
Siloed teams with different priorities/requirements
• Roles, objections and key focus areas may differ
Delays in business initiatives
• Bottlenecks result in delays
5
6. Deliver value
to customers
Deliver new
features
Ensure system
stability
Ensure
software
quality
Ensure
app
security
Security
teams
Quality
teams
Business
Dev teams Ops teams
Conflicting
incentives
6
7. Challenges and complexities our customers face
● Multiple teams and business units own and
operate disparate infrastructure
● Inefficient processes and business initiatives that
never happen
● Silos between Ops teams and specialist Ops
teams (application and deployment)
● Different approaches to coordinate change and
information sharing
● Increased number of task-based automation
“collisions”
7
8. IT teams need a holistic
approach to managing
infrastructure at scale.
8
9. Continuous Delivery for
Puppet Enterprise
Deliver changes faster and more reliably
• Eliminate silos
• Accelerate deployment timeframes
• Enforce confidence
9
10. Scale with Continuous Delivery for Puppet Enterprise
10
● See the impact of proposed code changes, avoid collisions with team
workflows and deliver automation safely across multiple IT teams at scale
● Confidently scale their IT organization’s ability to contribute to infrastructure
configuration changes
● Protect the infrastructure from unplanned or unwanted changes by analyzing
the potential impact of a change before pushing
● Codify and measure the delivery pipeline to continuously improve code
deployment
● Test infrastructure changes prior to deployment and eliminate common
bottlenecks within the software delivery lifecycle process
11. Manages hundreds of thousands
of nodes with Puppet automation.
With Continuous Delivery for
Puppet Enterprise, they’ve
enabled testing at scale and
reduced risk while pushing
massive changes across their
infrastructure.
— Retail customer
Standardized with Puppet to
expand their operation model
across their entire infrastructure
state including public cloud. With
Puppet automation, they have the
right strategy to succeed at global
scale.
— Financial Services
customer
With multiple authors across the
organization and company
boundaries, they expanded their
commitment with Puppet to
reduce risk and help automate
complex workflows to meet their
new standards for code
deployment processes.
— Tech customer
11
Customer Success with Puppet at Scale
13. Continuous Delivery for
Puppet Enterprise
provides a simple,
prescriptive way to build,
test, promote and deploy
infrastructure code.
13
14. Key Capabilities of
Continuous Delivery for
Puppet Enterprise
14
Build high-trust and high-velocity IT
organizations
Safely decentralize Puppet automation
across multiple teams
Safely deliver Puppet code changes by
inspecting the potential impact of a
proposed change
15. 15
Impact
Analysis
Know what’s going to
happen before you merge it.
Impact Analysis assesses
what nodes and
configurations will have their
desired state changed should
you merge and deploy a
change.
16. 16
Simple
Deployment
Policies
Anyone in your organization
should be capable of
shipping infrastructure
changes. Built-in and custom
deployment policies abstract
away the complexities of
delivering change.
17. 17
Workspaces
Provide CD for PE as a
service for other departments
to own and manage their
own infrastructure
automation without having to
manage the tooling.
18. 18
Module
Pipelines
Empower service owners to
own their own the authoring,
validation, and delivery of the
automation content for their
service without blocking or
being blocked by others.