Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Puppet Client: Puppet 4 and Beyond
Search
Kylo Ginsberg
February 02, 2015
0
39
Puppet Client: Puppet 4 and Beyond
Puppet Client: Puppet 4 and Beyond, 2015-02-02
Kylo Ginsberg
February 02, 2015
Tweet
Share
More Decks by Kylo Ginsberg
See All by Kylo Ginsberg
Under the Hood - C++ at Puppet Labs
kylog
0
320
Automating Docker Containers with Puppet
kylog
0
45
Featured
See All Featured
Measuring & Analyzing Core Web Vitals
bluesmoon
7
530
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
770
A better future with KSS
kneath
238
17k
Building Adaptive Systems
keathley
43
2.7k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
21
1.4k
Building a Scalable Design System with Sketch
lauravandoore
462
33k
The Straight Up "How To Draw Better" Workshop
denniskardys
235
140k
Why Our Code Smells
bkeepers
PRO
337
57k
Designing Experiences People Love
moore
142
24k
Thoughts on Productivity
jonyablonski
69
4.8k
Bootstrapping a Software Product
garrettdimon
PRO
307
110k
Scaling GitHub
holman
461
140k
Transcript
Puppet Client Kylo Ginsberg @kylog irc: kylo
[email protected]
Puppet 4
and Beyond
Puppet 4
All-in-one agent Path changes URL changes Puppet language
All-in-one agent
puppet-agent package • puppet • facter • native facter •
hiera • mcollective • ruby • … and dependencies
puppet-agent versioning • Not tied directly to puppet versions •
E.g. version 1.0.0 will include: • puppet 4.0.0 • facter 2.4.0 • ruby 2.1.5 • … • Component bumps major: puppet-agent bumps major
Why all-in-one? One package: easier on-ramp for new users Everyone
benefits from latest ruby Reduces the test matrix, reduces support questions Open source puppet and PE use the same package
Path changes
Top-level directory name changes /etc/puppetlabs ~/.puppetlabs
Separate code and config /etc/puppetlabs/agent/code manifests modules environments hieradata hiera.yaml
/etc/puppetlabs/agent/config puppet.conf device.conf …
URL changes
Versioned and Namespaced URLs Puppet 3: /production/catalog/my_node /production/certificate/my_node Puppet 4:
/puppet/v3/catalog/my_node?environment=production /puppet-ca/v1/certificate/my_node?environment=production
Compatibility Puppet 4 is not backwards compatible on the network
with Puppet 3. puppet-server 2.0.0 package depends on puppet-agent 1.0.0 package.
Puppet 4: the Puppet language
From reference implementation to language specification
puppetlabs/puppet-specifications
Optional types
None
Iteration and lambdas
None
None
Test in Puppet 3.7.4 Default in Puppet 4.0 puppet apply
—parser=future puppet apply
None
puppet-on-the-edge.blogspot.com
After Puppet 4
Going Native Facter 3 Tiered Providers
Going native
None
None
Does your programming language run on AIX?
Does your programming language run on hardware switches?
Performance Memory usage Installed footprint Dependencies
Native puppet agent …
Facter 3
None
None
None
Tiered Providers
The sad story of nagios
Extract “tier 2” types and providers as modules • Developed
and released independently • Packaged with puppet-agent for a “batteries included” experience
Get Involved!
Gareth Rushgrove puppetlabs.com/download-learning-vm
puppetlabs.com/community/participate
Test pilots logo Gareth Rushgrove
Questions? And thanks for listening