all posts tagged puppet-shorewall
I’ve been afraid of RPM and package maintaining  for years, but thanks to Kaleb Keithley, I have finally made some RPM’s that weren’t generated from a high level tool. Now that I have the boilerplate done, it’s a relatively painless process!
In case you don’t know kkeithley, he is a wizard  who happens to also be especially cool and hardworking. If you meet him, be sure to buy him a $BEVERAGE. </plug>
A photo of kkeithley after he (temporarily) transformed himself into a wizard penguin.
The full source of my changes is available in git.
If you want to make the RPM’s yourself, simply clone the puppet-gluster source, and run:
make rpm. If you'd rather download pre-built RPM's, SRPM'S, or source tarballs, they are all being graciously hosted on download.gluster.org, thanks to John Mark Walker and the gluster.org community.
These RPM's will install their contents into
/usr/share/puppet/modules/. They should work on Fedora or CentOS, but they do require a
puppet package to be installed. I hope to offer them in the future as part of a repository for easier consumption.
There are also RPM's available for puppet-common, puppet-keepalived, puppet-puppet, puppet-shorewall, puppet-yum, and even puppetlabs-stdlib. These are the dependencies required to install the puppet-gluster module.
Please let me know if you find any issues with any of the packages, or if you have any recommendations for improvement! I'm new to packaging, so I probably made some mistakes.
 package maintainer, aka: "paintainer" - according to semiosis, who is right!
 wizard as in an awesome, talented, hacker.
Oh, hi there.
In case you’re interested, I’ve just made a first release of my puppet-shorewall module. This isn’t meant as an exhaustive shorewall module, but it does provide most of the usual functionality that most users need.
In particular, it’s the module dependency that I use for many of my other puppet modules that provide firewalling. This is probably where you’re most likely to consume it.
In general most modules just implement shorewall::rule, so if you really don’t want to use this code, you can implement that signature yourself, or not use automatic firewalling. The shorewall::rule type has two main signatures, so have a look at the source, or a simple example if you want to get more familiar with the specifics. Using this module is highly recommended, specifically with puppet-gluster.
Please keep in mind that since I mostly use this module to open ports and to keep my other modules happy, I probably don’t have advanced traffic control features on my roadmap. If you’re looking for something that I haven’t added, contact me with the details and consider sponsoring some features.