Version information
Start using this module
Add this module to your Puppetfile:
mod 'puppetlabs-mysql', '0.5.0'
Learn more about managing modules with a PuppetfileDocumentation
Mysql module for Puppet
This module manages mysql on Linux (RedHat/Debian) distros. A native mysql provider implements database resource type to handle database, database user, and database permission.
Description
This module uses the fact osfamily which is supported by Facter 1.6.1+. If you do not have facter 1.6.1 in your environment, the following manifests will provide the same functionality in site.pp (before declaring any node):
if ! $::osfamily {
case $::operatingsystem {
'RedHat', 'Fedora', 'CentOS', 'Scientific', 'SLC', 'Ascendos', 'CloudLinux', 'PSBM', 'OracleLinux', 'OVS', 'OEL': {
$osfamily = 'RedHat'
}
'ubuntu', 'debian': {
$osfamily = 'Debian'
}
'SLES', 'SLED', 'OpenSuSE', 'SuSE': {
$osfamily = 'Suse'
}
'Solaris', 'Nexenta': {
$osfamily = 'Solaris'
}
default: {
$osfamily = $::operatingsystem
}
}
}
This module depends on creates_resources function which is introduced in Puppet 2.7. Users on puppet 2.6 can use the following module which provides this functionality:
http://github.com/puppetlabs/puppetlabs-create_resources
This module is based on work by David Schmitt. The following contributor have contributed patches to this module (beyond Puppet Labs):
- Christian G. Warden
- Daniel Black
- Justin Ellison
- Lowe Schmidt
- Matthias Pigulla
- William Van Hevelingen
- Michael Arnold
Usage
mysql
Installs the mysql-client package.
class { 'mysql': }
mysql::java
Installs mysql bindings for java.
class { 'mysql::java': }
mysql::python
Installs mysql bindings for python.
class { 'mysql::python': }
mysql::ruby
Installs mysql bindings for ruby.
class { 'mysql::ruby': }
mysql::server
Installs mysql-server packages, configures my.cnf and starts mysqld service:
class { 'mysql::server':
config_hash => { 'root_password' => 'foo' }
}
Database login information stored in /root/.my.cnf
.
mysql::db
Creates a database with a user and assign some privileges.
mysql::db { 'mydb':
user => 'myuser',
password => 'mypass',
host => 'localhost',
grant => ['all'],
}
mysql::backup
Installs a mysql backup script, cronjob, and priviledged backup user.
class { 'mysql::backup':
backupuser => 'myuser',
backuppassword => 'mypassword',
backupdir => '/tmp/backups',
}
Providers for database types:
MySQL provider supports puppet resources command:
$ puppet resource database
database { 'information_schema':
ensure => 'present',
charset => 'utf8',
}
database { 'mysql':
ensure => 'present',
charset => 'latin1',
}
The custom resources can be used in any other manifests:
database { 'mydb':
charset => 'latin1',
}
database_user { 'bob@localhost':
password_hash => mysql_password('foo')
}
database_grant { 'user@localhost/database':
privileges => ['all'] ,
# Or specify individual privileges with columns from the mysql.db table:
# privileges => ['Select_priv', 'Insert_priv', 'Update_priv', 'Delete_priv']
}
A resource default can be specified to handle dependency:
Database {
require => Class['mysql::server'],
}
Types in this module release
2012-08-23 - Version 0.5.0
- Add puppetlabs/stdlib as requirement
- Add validation for mysql privs in provider
- Add
pidfile
parameter to mysql::config - Add
ensure
parameter to mysql::db - Add Amazon linux support
- Change
bind_address
parameter to be optional in my.cnf template - Fix quoting root passwords
2012-07-24 - Version 0.4.0
- Fix various bugs regarding database names
- FreeBSD support
- Allow specifying the storage engine
- Add a backup class
- Add a security class to purge default accounts
2012-05-03 - Version 0.3.0
- #14218 Query the database for available privileges
- Add mysql::java class for java connector installation
- Use correct error log location on different distros
- Fix set_mysql_rootpw to properly depend on my.cnf
2012-04-11 - Version 0.2.0
2012-03-19 - William Van Hevelingen blkperl@cat.pdx.edu
- (#13203) Add ssl support (f7e0ea5)
2012-03-18 - Nan Liu nan@puppetlabs.com
- Travis ci before script needs success exit code. (0ea463b)
2012-03-18 - Nan Liu nan@puppetlabs.com
- Fix Puppet 2.6 compilation issues. (9ebbbc4)
2012-03-16 - Nan Liu nan@puppetlabs.com
- Add travis.ci for testing multiple puppet versions. (33c72ef)
2012-03-15 - William Van Hevelingen blkperl@cat.pdx.edu
- (#13163) Datadir should be configurable (f353fc6)
2012-03-16 - Nan Liu nan@puppetlabs.com
- Document create_resources dependency. (558a59c)
2012-03-16 - Nan Liu nan@puppetlabs.com
- Fix spec test issues related to error message. (eff79b5)
2012-03-16 - Nan Liu nan@puppetlabs.com
- Fix mysql service on Ubuntu. (72da2c5)
2012-03-16 - Dan Bode dan@puppetlabs.com
- Add more spec test coverage (55e399d)
2012-03-16 - Nan Liu nan@puppetlabs.com
- (#11963) Fix spec test due to path changes. (1700349)
2012-03-07 - François Charlier fcharlier@ploup.net
- Add a test to check path for 'mysqld-restart' (b14c7d1)
2012-03-07 - François Charlier fcharlier@ploup.net
- Fix path for 'mysqld-restart' (1a9ae6b)
2012-03-15 - Dan Bode dan@puppetlabs.com
- Add rspec-puppet tests for mysql::config (907331a)
2012-03-15 - Dan Bode dan@puppetlabs.com
- Moved class dependency between sever and config to server (da62ad6)
2012-03-14 - Dan Bode dan@puppetlabs.com
- Notify mysql restart from set_mysql_rootpw exec (0832a2c)
2012-03-15 - Nan Liu nan@puppetlabs.com
- Add documentation related to osfamily fact. (8265d28)
2012-03-14 - Dan Bode dan@puppetlabs.com
- Mention osfamily value in failure message (e472d3b)
2012-03-14 - Dan Bode dan@puppetlabs.com
- Fix bug when querying for all database users (015490c)
2012-02-09 - Nan Liu nan@puppetlabs.com
- Major refactor of mysql module. (b1f90fd)
2012-01-11 - Justin Ellison justin.ellison@buckle.com
- Ruby and Python's MySQL libraries are named differently on different distros. (1e926b4)
2012-01-11 - Justin Ellison justin.ellison@buckle.com
- Per @ghoneycutt, we should fail explicitly and explain why. (09af083)
2012-01-11 - Justin Ellison justin.ellison@buckle.com
- Removing duplicate declaration (7513d03)
2012-01-10 - Justin Ellison justin.ellison@buckle.com
- Use socket value from params class instead of hardcoding. (663e97c)
2012-01-10 - Justin Ellison justin.ellison@buckle.com
- Instead of hardcoding the config file target, pull it from mysql::params (031a47d)
2012-01-10 - Justin Ellison justin.ellison@buckle.com
- Moved $socket to within the case to toggle between distros. Added a $config_file variable to allow per-distro config file destinations. (360eacd)
2012-01-10 - Justin Ellison justin.ellison@buckle.com
- Pretty sure this is a bug, 99% of Linux distros out there won't ever hit the default. (3462e6b)
2012-02-09 - William Van Hevelingen blkperl@cat.pdx.edu
- Changed the README to use markdown (3b7dfeb)
2012-02-04 - Daniel Black grooverdan@users.sourceforge.net
- (#12412) mysqltuner.pl update (b809e6f)
2011-11-17 - Matthias Pigulla mp@webfactory.de
- (#11363) Add two missing privileges to grant: event_priv, trigger_priv (d15c9d1)
2011-12-20 - Jeff McCune jeff@puppetlabs.com
- (minor) Fixup typos in Modulefile metadata (a0ed6a1)
2011-12-19 - Carl Caum carl@carlcaum.com
- Only notify Exec to import sql if sql is given (0783c74)
2011-12-19 - Carl Caum carl@carlcaum.com
- (#11508) Only load sql_scripts on DB creation (e3b9fd9)
2011-12-13 - Justin Ellison justin.ellison@buckle.com
- Require not needed due to implicit dependencies (3058feb)
2011-12-13 - Justin Ellison justin.ellison@buckle.com
- Bug #11375: puppetlabs-mysql fails on CentOS/RHEL (a557b8d)
2011-06-03 - Dan Bode dan@puppetlabs.com - 0.0.1
- initial commit
Dependencies
- puppetlabs/stdlib (>= 2.2.1)
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.