Quickly Deploy MySQL with Puppet Enterprise Supported Module Puppetlabs-MySQL
With the launch of Puppet Enterprise 3.2, Puppet Labs now provides full support for a handful of Forge modules within the Puppet Labs namespace. This list of supported modules will continue to grow, and we encourage all our Puppet Enterprise customers to upgrade to 3.2, to enjoy the benefits of module support (and all the other benefits of the new release, too).
Among the newly supported modules is puppetlabs-mysql, which lets you both configure and manage your MySQL installation, plus manage MySQL resources such as
Managing a MySQL deployment, whether it be the simple installation of the MySQL client or a full-on server deployment, is a pretty common use case for Puppet and Puppet Enterprise. With puppetlabs-mysql, you can take what was once a complex or extensive MySQL deployment and streamline the process into something far simpler and more manageable.
You can expect the puppetlabs-mysql module, and all other supported modules, to function as they should on all supported platforms. You can also expect support in all our usual channels. You can see the (growing) list of supported modules on the Puppet Forge.
In this post, I’ll show you how to easily deploy and configure a MySQL server using our supported module, as well as demonstrate how to quickly deploy a simple MySQL client.
For the following example, we have three separate nodes, all running the most current release of Puppet Enterprise 3.2, and all running CentOS 6.4. The first node is our all-in-one master with the hostname
master.puppetlabs.vm. The second node will act as our MySQL server with the hostname
db.puppetlabs.vm, and the third node acts as the MySQL client machine with the hostname
To get started, we first need to get the module installed. You can use the Puppet Module Tool, included in Puppet Enterprise, to install the module on our puppet master.
Deploying MySQL Client
Deploying the MySQL client is very straightforward: just include the class in (
That was easy enough! By default, the MySQL client class, ensures the MySQL package is present and determines the package name, depending on the node's OS.
Deploying MySQL Server with Puppetlabs-MySQL
Deploying your MySQL server can be as simple as including the MySQL server class. In most cases, however, this will not suffice, as it uses all the default options. We will want to change some of these options. In the case below, we are going to change the max connections and root password.
You maybe asking yourself, “what is this
override_options paramater?” The
override_options parameter allows us to override options that are traditionally set in our
my.cnf. As you can see, we used the
override_options parameter to set our max connections to 1024. Traditionally, this would appear in configuration file as:
override_options parameter uses a hash format and allows us to do things like pass in an array. Something like this:
Traditionally this would appear in the
my.cnf configuration as:
The example class above is enough to get a MySQL server deployed. In the next section, I will discuss how you would go about deploying a custom database.
Creating a Database with Puppetlabs-MySQL
Though standing up a MySQL server is important, the server alone means nothing without any databases. In this example, I will create a database called
mydb and configure the user, password and host:
At this point, we have a MySQL server deployed with a database
mydb, but it doesn't have any data. Let’s create a new database called
statedb, so when the database is initially created we use a SQL script to populate the database.
Before we continue, let’s stop using
site.pp and move all our work so far into our own module, called
blogpost. We do this to avoid making any direct edits to the puppetlabs-mysql module itself once we begin adding any files Puppet needs to serve up, and to simplify our node definition in
First, let’s create a directory named
/etc/puppetlabs/puppet/modules/ and build all the necessary subdirectories for the module to function properly. We will create both the directories
For the purposes of this example, and in the interest of time, I decided to pull down a SQL script that creates a table of states from statetable. I am going to put the
.sql file in the
files directory of the module named
/etc/puppetlabs/puppet/modules/blogpost/files/states.sql), and lay the file down via the file resource.
After the file is laid down, we will be able to use it to populate the data in the database. In the example below we will have Puppet execute this script upon creating the database for the first time.
Now we have MySQL deployed, a database created, and a table of states, but we are not quite done. As you probably guessed, we need to configure users and grants, so we are able to grant permissions to the states table we created. In this example, we will allow the user
bob to access the table, but throttle the user’s access.
Now for the grants:
Now we officially have a MySQL server deployed, configured, and have put some sample data in a table. Let's take a look at the whole thing in the form of the
blogpost module (
At this point all we need to do is change our
db.puppetlabs.vm node definition in (
/etc/puppetlabs/puppet/manifests/site.pp) to include the
This is a pretty basic introduction and demonstration of how you can use and configure the puppetlabs-mysql module. As you can see, the module is extensive, with many configuration options. For more information and parameters, check out the documentation for the puppetlabs-mysql module.
Jay Wallace is a support engineer at Puppet Labs.