We have released the following cookbooks today:
- database (v1.3.2)
- mysql (v1.3.0)
- postgresql (v1.0.0)
A huge thank you and cookbook release MVP goes to Jesse Howarth and Jamie Winsor of RiotGames for their comments, feedback, and of course, pull requests.
Also, thank you to everyone else who participated in the discussions on the mailing list or in IRC. We appreciate everyone’s patience during the process. It turns out that the problem is very tricky to resolve, and I think the solution is going to be the best general case for the broadest audience.
The theme of the major changes in these releases is around the installation of the RubyGems “mysql” and “pg”. That is, the client recipes in both cookbooks will no longer install the RubyGems by default. That has been moved to the ruby recipe in each cookbook. The database cookbook now has postgresql and mysql recipes that will include the appropriate ruby recipe, as a matter of convenience. This was tracked under the ticket COOK-1441.
Please be aware that if you are using an Omnibus installation of Chef, the “pg” gem does not install properly without a huge amount of compilation hassle. This issue is tracked under ticket COOK-1406.
The following attributes are arrays that contain the package names based on the platform of the node.
These were namespaced under client and server to make them clearer and easier to parse programmatically. If you wish to install the native package for the rubygems your platform (if it has one), you can simply modify the attribute, and Chef will handle that for you.
A side benefit of the mysql attributes is that Percona should be a “drop in” replacement by simply populating the attributes with the Percona package names.
Joshua Timberman, Technical Program Manager
IRC, Skype, Twitter, Github: jtimberman