Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master

This branch is 0 commits ahead and 0 commits behind master

Fetching latest commit…

Cannot retrieve the latest commit at this time

README.rdoc

DESCRIPTION:

Installs and configures MySQL client or server.

REQUIREMENTS:

Platform:

Best tested on Ubuntu 9.04,9.10. On EC2, requires platform that supports -o bind option for the 'mount' command.

Cookbooks:

Requires Opscode's openssl cookbook for secure password generation.

Requires a C compiler and Ruby development package in order to build mysql gem with native extensions. On Debian and Ubuntu systems this is satisfied by installing the “build-essential” and “ruby-dev” packages before running Chef. See USAGE below for information on how to handle this during a Chef run.

RESOURCES AND PROVIDERS

The cookbook contains a LWRP, mysql_database which can be used to manage databases through calls to the MySQL API. The mysql gem is installed to make this usable. The provider currently supports three actions:

  • flush_tables_with_read_lock - sends the sql command “flush tables with read lock”, used for setting up mysql master/slave replication.

  • unflush_tables - sends the sql command “unflush tables”, used for setting up master/slave replication.

  • create_db - specify a database to be created.

For example see the USAGE section below.

ATTRIBUTES:

  • +mysql[:server_root_password]+ - Set the server's root password with this, default is a randomly generated password with +OpenSSL::Random.random_bytes+.

  • +mysql[:server_repl_password]+ - Set the replication user 'repl' password with this, default is a randomly generated password with +OpenSSL::Random.random_bytes+.

  • +mysql[:server_debian_password]+ - Set the debian-sys-maint user password with this, default is a randomly generated password with +OpenSSL::Random.random_bytes+.

  • +mysql[:bind_address]+ - Listen address for MySQLd, default is node's ipaddress.

  • +mysql[:datadir]+ - Location for mysql data directory, default is “/var/lib/mysql”

  • +mysql[:ec2_path]+ - location of mysql datadir on EC2 nodes, default “/mnt/mysql”

Performance tuning attributes, each corresponds to the same-named parameter in my.cnf; default values listed

  • +mysql[:tunable][:key_buffer]+ = “250M”

  • +mysql[:tunable][:max_connections]+ = “800”

  • +mysql[:tunable][:wait_timeout]+ = “180”

  • +mysql[:tunable][:net_write_timeout]+ = “30”

  • +mysql[:tunable][:net_write_timeout]+ = “30”

  • +mysql[:tunable][:back_log]+ = “128”

  • +mysql[:tunable][:table_cache]+ = “128”

  • +mysql[:tunable][:max_heap_table_size]+ = “32M”

USAGE:

On client nodes,

include_recipe "mysql::client"

This will install the MySQL client libraries and development headers on the system. It will also install the Ruby Gem mysql, so that the cookbook's LWRP (above) can be used. This is done during the compile-phase of the Chef run.

r = package ... do
  action :nothing
end

r.run_action(:install)

This creates a resource object for the package and does the installation before other recipes are parsed. You'll need to have the C compiler and such (ie, build-essential on Ubuntu) before running the recipes, but we already do that when installing Chef :-). If you want to be able to access a MySQL database via Ruby within another recipe, you could do so, like so:

Gem.clear_paths # needed for Chef to find the gem...
require 'mysql' # requires the mysql gem

mysql_database "create application_production database" do
  host "localhost"
  username "root"
  password node[:mysql][:server_root_password]
  database "application_production"
  action :create_db
end

This will connect to the MySQL server running on localhost as “root” and password as +mysql[:server_root_password]+ attribute (see below) and create the database specified with the database parameter. The provider will attempt to determine whether the database exists first.

On server nodes,

include_recipe "mysql::server"

On Debian and Ubuntu, this will preseed the mysql-server package with the randomly generated root password from the attributes file. On other platforms, it simply installs the required packages. It will also create an SQL file, /etc/mysql/grants.sql, that will be used to set up grants for the root, repl and debian-sys-maint users.

On EC2 nodes,

include_recipe "mysql::server_ec2"

When the ec2_path doesn't exist we look for a mounted filesystem (eg, EBS) and move the datadir there.

The client recipe is already included by server and 'default' recipes.

To make sure that a C compiler and the Ruby development libraries are installed, use the following run list in the node or in a role:

{
  "run_list": [
    "recipe[build-essential]",
    "recipe[ruby]",
    "recipe[mysql::server]"
  ]
}

The build-essential and ruby cookbooks install the packages in question during the “execution” phase of the Chef client run, rather than the compile phase when the MySQL gem is installed. To work around this for now until the build-essential and ruby packages are updated, modify your local copies of the recipes:

In the Opscode build-essential default recipe:

%w{build-essential binutils-doc}.each do |pkg|
  p = package pkg do
    action :nothing
  end
  p.run_action(:install)
end

And the ruby recipe to have the following:

extra_packages.each do |pkg|
 p = package pkg do
   action :nothing
 end
 p.run_action(:install)
end

These cookbooks aren't strict dependencies, and not if the installation process already included installing build-essential and ruby1.8-dev (e.g. RubyGems installation).

For more infromation on the compile vs execution phase of a Chef run:

http://wiki.opscode.com/display/chef/Anatomy+of+a+Chef+Run

LICENSE and AUTHOR:

Author

Joshua Timberman (<joshua@opscode.com>)

Author

AJ Christensen (<aj@opscode.com>)

Copyright

2009, Opscode, Inc

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.

Something went wrong with that request. Please try again.