Project

puppetize

0.0
No commit activity in last 3 years
No release in over 3 years
Puppetize is a tool that can generate complete modules from systems
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Runtime

>= 1.0
>= 2.0
 Project Readme

puppetize

Preface

If you are a sysadmin or a developer that as a daily job has to create and mantain multiple puppet modules, this is the tool for you.

Package maintainers work hard and take a lot of shit. You can't please everyone. So, if you're a maintainer: Thanks for maintaining packages!

State

This is alpha beta unstable dev ultra unstable all together software at the moment, I would say is more like a proof of concept to see how useful this module would be.

USE IT AT YOUR OWN RISK... which is pretty high :-)

What is puppetize?

Puppetize is an automated puppet module generation tool.

It helps you build puppet modules quickly and easily formats).

FUNDAMENTAL PRINCIPLE: IF PUPPETIZE IS NOT HELPING YOU MAKE PUPPET MODULES EASILY, THEN THERE IS A BUG IN PUPPETIZE.

puppetize will collect every detail about your system. You then can start to work on installing your RPMs, tune your configuration files and start or stop the necessary services... as you would do in the old good days.

puppetize will then catch all those differences and build a standard puppet module. It'll use the standard puppet structure from puppet forge and it will finally write the manifests using the best practices out there.

Get with the download

Install dependencies,

yum install -y git rubygems puppet

NOTE: You'll need extra repositories from puppetlabs to install puppet:

You can install puppetize with gem:

gem install puppetize

Collect the initial system state:

puppetize init

Build the module:

puppetize build

This will create a new puppet standard module under /root/puppetize-module with all the necessary resources to implement the changes between the initial state and now.

Finally you can reset the state and start over doing:

puppetize reset

Example:

[root@test-vm ~]# puppetize init
[root@test-vm ~]# yum install -y telnet httpd
[root@test-vm ~]# vim /etc/httpd/conf/httpd.conf 
[root@test-vm ~]# puppetize build
[root@test-vm ~]# find /root/puppetize-module/
/root/puppetize-module/
/root/puppetize-module/spec
/root/puppetize-module/spec/spec_helper.rb
/root/puppetize-module/Modulefile
/root/puppetize-module/files
/root/puppetize-module/files/httpd.conf
/root/puppetize-module/manifests
/root/puppetize-module/manifests/init.pp
/root/puppetize-module/manifests/config.pp
/root/puppetize-module/manifests/install.pp
/root/puppetize-module/templates
/root/puppetize-module/templates/httpd.conf.erb
/root/puppetize-module/tests
/root/puppetize-module/tests/init.pp
/root/puppetize-module/README

Known issues

  • At the moment puppetize will only create:

package file -> files file -> directories

  • It won't create empty directory definitions.

  • Only supports Redhat base distributions

TODO:

Implement every other resource like: mount service etc...

Need Help or Want to Contribute?

All contributions are welcome: ideas, patches, documentation, bug reports, complaints, and even something you drew up on a napkin.

It is more important to me that you are able to contribute and get help if you need it..

More Documentation

None yet