I am terrible at getting these out on schedule.
Another busy month with a whole bunch of stuff going on, internally and
externally. The main highlights of the month are the recently rewritten
puppetlabs-mysql and puppetlabs-postgresql modules. Both have had huge
overhauls internally and are now (hopefully) vastly more useful for end
users.
*What did you guys do to my databases?*
*
*
I'm going to selfishly talk about puppetlabs-mysql first as I'm about to
refactor in my changes today. Over the last month I've done two large
things for the MySQL module.
First, I've written replacement types and providers for the venerable mysql
providers that have been floating around for Puppet modules for years now.
(First provider I ever modified for internal use, in the distant past)
These replacements are called mysql_grant, mysql_user, and mysql_database
and hopefully represent a reasonable set of improvements. The major thing
I wanted was to allow them to work with puppet resource so that from the
cli you can do:
# puppet resource mysql_user blah@host ensure=absent and have things work.
This was mostly for selfish reasons as I can never remember the syntax to
add users.
Second, I've refactored the module substantially. Previously we relied on
enormous numbers of parameters in an attempt to manage /etc/.my.cnf and we
constantly received pull requests to add new parameters. The new module
blows all this away and allows you to do:
mysql::globals {
override_options => { 'mysqld' => 'max_connections' => '256' }
}
You can feed it any my.cnf options you want and they will magically appear.
It has some downsides in that we can't validate what you put into my.cnf
by allowing you to set any keys, but there's a few thousand possible
entries to my.cnf and it's not realistic for us to handle them all.
I'm thinking long term we'll pull certain key values out into parameters
like before and just merge those into the hash used to write out .my.cnf.
*And postgresql?*
*
*
Ken Barber completely rewrote this to be much more flexible than before and
to use a type/provider to build up the configuration, allowing you to just
drop in configuration resources easily. I won't talk as much about this
here as I don't have a full a picture of it as I do for mysql but it's in
the master branch of puppetlabs-postgresql right now and available for
testing.
*What modules did you release since the last update?*
*
*
http://forge.puppetlabs.com/puppetlabs/ntp/2.0.1
http://forge.puppetlabs.com/puppetlabs/apache/0.9.0
http://forge.puppetlabs.com/puppetlabs/postgresql/2.5.0
http://forge.puppetlabs.com/puppetlabs/pe_upgrade/2.0.0
http://forge.puppetlabs.com/puppetlabs/git/0.0.3
http://forge.puppetlabs.com/puppetlabs/firewall/0.4.2
http://forge.puppetlabs.com/puppetlabs/apt/1.3.0
And some from other teams worth mentioning:
http://forge.puppetlabs.com/puppetlabs/reboot - a type/provider to schedule
reboots (windows only for now)
http://forge.puppetlabs.com/puppetlabs/registry/0.1.2
http://forge.puppetlabs.com/puppetlabs/java_ks/1.2.0
*What else are you guys up to?*
*
*
Lots of little things! I've been working on documentation, understanding
data-in-modules, testing (updating the vcsrepo spec tests from rspec1 to
rspec2). Hunter's working on a huge amount of stuff from beaker
(acceptance testing) to scaling guides to more work on the apache module.
I'm sure I've missed a bunch of stuff we're doing but as always swing by
#puppet and shout at ashp (or hunter) if you want anything module related
or just want to throw us your worst "I can't figure out how to.." problems.
Thanks,
--
Ashley Penney
ashley.pen...@puppetlabs.com
Module Engineer
*Join us at PuppetConf 2014, September 23-24 in San Francisco*
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
