User:David/GTALUG July 14th puppet

From Federal Burro of Information
Jump to navigationJump to search

based on http://www.example42.com/tutorials/PuppetTutorial/#slide-0

time goal: 40 minutes.

Abstract

Puppet is a tool for doing configuration management. This talk will go over what puppet is, what it can do and how to do it. There is more than one way to do it, some lessons have been learned in the field and from the community. The talk will be based on Alessandro Franceschi's fine http://www.example42.com/tutorials/PuppetTutorial/ . Note all slides will be discussed (developer oriented slides) , and some topics not mentioned in the URL will be added (work flow topics). I intend for this talk to be a dialog and support "engaged" learning, feel free to interrupt.

Slides / Notes

1. What is Puppet

2. Configuration Management advantages

3. References and Ecosystem
also see : #puppet

4. Software related to Puppet:

5.Installation

6. Puppet Versions

  • why use the ditros version?
  • why use puppetlabs version?
  • PE ? Puppet enterprise.

7. Puppet Language

8. Resource Types (Types)
9. Simple samples of resources
10.More Complex examples of resources

11. Resource Abstraction Layer

12. Classes

13. Defines HOMEWORK

14. Variables

15. User Variables

16. Nodes - Default classification

17. Nodes - Alternative approaches

  • On an External Node Classifier (ENC)
  • With hiera_include HOMEWORK

18. The Catalog

19. Operational modes

  • Masterless - puppet apply
  • Master / Client - puppet agent

talking topics:

  • push v pull
  • dev versus test versus prod.

20. Masterless setup

21. Master / Client Setup

22. Certificates management

23. Certificates management - First run

24. Puppet configuration: puppet.conf

25. Main configuration options

26. Common command-line parameters

27. Useful paths

28. Other configuration files: HOMEWORK

29. Online documentation on types

30. Inline documentation on types

EXAMPLES

31. Managing packages
32. Managing services
33. Managing files
34. Executing commands
35. Managing users

36. Puppet language style 37. Resource references

Reference material

To be spliced in

(missing in the borrowed talk)

A. work flow. day to day work.

B. Puppet file / Librarian, module management , r10k.

C. Do it yourself or modules?

Future talks

I. Configuration management

II. Ansible