Introduction to Puppet EnterpriseThe shortest path to better software.

Agenda

Meet our speakers

Introduction to Puppet Enterprise

Puppet Enterprise live demo

Now what?

Q+A

Welcome and Introductions

Ian McNaughtonSales Associate

Mike SmithTechnical Solutions Engineer

Digital transformationDevOps initiatives Container adoption

Shifting budgetsTool proliferationModernization

Cloud migration

Technical debt

Skill gapsSecurity

Compliance

Agile IT

AutomationShadow IT

Deliver better software, faster.

Broker to the future?Dot com property • mobile apps • everything new

Keeper of the past?ERP system • legacy infrastructure • vendor contracts

to the new wayfrom the old way

A massive shift is required

• Automatic, standard & scalable

• Delivering at will

• Inherent security

• Constantly modern

Ad hoc, manual & error prone

Infrequent delivery

Security in silos

Legacy platforms

deliver infrequentlydo things manuallysucceed in isolation

It will not work to

Know what you have

Control it and enforce consistency

Secure it and keep it compliant

Modernize it

An automatic way to …

Using a common languageAcross everything, no matter where it runs

Doing it right delivers results

212%Increase in

deployment speed

170%

Fewer outages

76%

Less security fix time

150%More frequent deployments

5.4%

Reduction in IT Opex

180%Increase in

successful audits

Source: ESG Economic Value Validation Report. Results are avg of >200 Puppet Enterprise customers.

Unique approach: define once, automate endlesslyUnparalleled enterprise scaleProven customer successDatacenter standardBridge to the future

Puppet

Leading platform. Datacenter standard.

Experience Founded in 2005

Scale More than 10 million nodes managed

Ecosystem Deep partnerships with datacenter titans

Customers 1,200+ enterprise customers

Community 4,700+ community-contributed modules

Users 35,000+ organizations using Puppet

Backing

Ready to see it in action?

Infrastructure as CodeDescribe the ideal environment with a simple, commonly understood language

building { 'home': ensure => 'clean', front_door => 'closed', keys => 'key_hook', jacket => 'closet', floor => 'vacuumed’, litter_box => 'empty', remote => 'coffee_table',}

Puppet Workflow

1. Define your desired state

2. Simulate configuration

4. Report

3. Enforce configuration

service { ‘ntpd’: ensure => running,}

nodes ask for new config every 30 mins

2. Catalog3. Report

1. Facts

Master

Agent(s)

Abstraction is powerful

vs

Where to start with automationStart with core infrastructure and work up

ProvisioningBare metal ● Virtual environments ● Cloud ● Containers

Application infrastructureSQL server ● Tomcat ● WebSphere ● IIS ● MySQL

Core infrastructureOperating system ● NTP ● DNS ● SSH ● Firewall ● Users ● Groups

Application orchestrationCustom apps ● COTS ● Share services

Next Steps

• Contact Sales to see how Puppet can help you: puppet.com/company/contact-sales

• Get Puppet Enterprise trial for 10 nodes: puppet.com/download-puppet-enterprise

• Check out our Learning VM: puppet.com/download-learning-vm

• View our self-paced trainings: learn.puppet.com

• Search the Forge: forge.puppet.com

Questions?