Automate Mysql with Puppet
Puppet, based on my personal experience is a great technology that allows new ways in DevOps environments and automation. With this technology people can code and manage the complete IT infrastructure from a central location, or a within a cloud infrastructure. It has completely changed the way on providing IT services and managing the same. Some cool features like role based access control and activity login allow people to define stable management strategy.
To get started, I created a simple Client / Server based puppet scenario in which we will automate Mysql server implementation in a linux environment. Puppet master server is configured to provide modules, manifests and classes to the agent servers in the complete infrastructure.
After installing the puppet master server the users can use the following folder etc/puppet/manifests to develop and write some code for deploying the services to the agent servers.
First, on the puppet master server we should download and install the package module for the Mysql server using the following command:
sudo puppet module search mysql
After the successful installation you should verify that the folder mysql exists in the /etc/puppet/modules folder with the source installation of mysql server.
After the validation of folder existence , the source file are located there. Now we have to define the site.pp file inside the /etc/puppet/manifests as a manifest file that will send the code execution of installing the mysql server on an agent server. The content of the file should look like the following:
node 'agent_node01' { include mysql::server }
This line of code defines the agent_node01 will look for the installation of mysql server inside the mysql server module installation on the puppet master server. The next step is to connect to the agent node and start the puppet agent service.
sudo /etc/init.d/puppet start
After restarting the service I will initiate the agent test command to force the pulling the package and the module from the puppet master.
As we can see the catalog is finished and the Mysql server service is up and running. The allow_virtual parameter can be ignored as that is a deprecation warning by default.
Feel free to test and comment.
To get started, I created a simple Client / Server based puppet scenario in which we will automate Mysql server implementation in a linux environment. Puppet master server is configured to provide modules, manifests and classes to the agent servers in the complete infrastructure.
After installing the puppet master server the users can use the following folder etc/puppet/manifests to develop and write some code for deploying the services to the agent servers.
First, on the puppet master server we should download and install the package module for the Mysql server using the following command:
sudo puppet module search mysql
After the successful installation you should verify that the folder mysql exists in the /etc/puppet/modules folder with the source installation of mysql server.
After the validation of folder existence , the source file are located there. Now we have to define the site.pp file inside the /etc/puppet/manifests as a manifest file that will send the code execution of installing the mysql server on an agent server. The content of the file should look like the following:
node 'agent_node01' { include mysql::server }
This line of code defines the agent_node01 will look for the installation of mysql server inside the mysql server module installation on the puppet master server. The next step is to connect to the agent node and start the puppet agent service.
sudo /etc/init.d/puppet start
After restarting the service I will initiate the agent test command to force the pulling the package and the module from the puppet master.
As we can see the catalog is finished and the Mysql server service is up and running. The allow_virtual parameter can be ignored as that is a deprecation warning by default.
Feel free to test and comment.
