{"id":12590,"date":"2014-03-31T17:50:17","date_gmt":"2014-03-31T12:20:17","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=12590"},"modified":"2016-12-19T14:53:42","modified_gmt":"2016-12-19T09:23:42","slug":"installing-lamp-stack-through-chef","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/installing-lamp-stack-through-chef\/","title":{"rendered":"Installing LAMP stack through Chef"},"content":{"rendered":"

Chef as we all know is a Configuration Management Tool. It enables Infrastructure as Code.<\/p>\n

Recently I had to give a technical presentation on Chef<\/a> in my current organization which helped me to get some insights into how Chef works & how it eases the deployment process.<\/p>\n

In this article I would touch upon very basic entities associated with Chef & how to deploy a complete LAMP stack on Chef-solo.<\/p>\n

Chef-solo<\/strong> behaves as a standalone system, it is in itself a client & a server.<\/p>\n

Knife<\/em> is the most important part of Chef as this is the command line tool for chef all the deployment from Chef server to Chef client happens via knife. In case we want to launch instances in cloud through Chef server we will make use of knife ec2<\/strong> for AWS instances.<\/p>\n

Without wasting any more time let\u2019s move further with the installation steps. For this example I would be Ubuntu 12.04 as the OS<\/p>\n

Installing Chef<\/span><\/strong><\/p>\n

We can download chef-solo<\/strong> from github.<\/p>\n

[shell]root@ankush# curl -L https:\/\/www.opscode.com\/chef\/install.sh | bash<\/p>\n

root@ankush# chef-solo -v<\/p>\n

root@ankush# wget http:\/\/github.com\/opscode\/chef-repo\/tarball\/master<\/p>\n

root@ankush# tar -zxf master<\/p>\n

root@ankush# mv opscode-chef-repo* chef-repo<\/p>\n

root@ankush# rm master<\/p>\n

root@ankush# cd chef-repo<\/p>\n

root@ankush# ls[\/shell]<\/p>\n

Now we would specify the cookbook path under .chef directory in knife.rb file.<\/p>\n

[shell]root@ankush:~\/chef-repo# mkdir .chef<\/p>\n

root@ankush:~\/chef-repo# echo &quot;cookbook_path [ ‘\/root\/chef-repo\/cookbooks’ ]&quot; &gt; .chef\/knife.rb[\/shell]<\/p>\n

Create any cookbook via knife e.g phpapp<\/p>\n

[shell]root@ankush:~\/chef-repo# knife cookbook create phpapp<\/p>\n

root@ankush:~\/chef-repo# cd cookbooks\/phpapp<\/p>\n

root@ankush:~\/chef-repo\/cookbooks\/phpapp# ls<\/p>\n

root@ankush:~\/chef-repo\/cookbooks\/phpapp# cd ..[\/shell]<\/p>\n

Installing Apache<\/strong><\/p>\n

[shell]root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download apache2<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf apache2*<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# rm apache2*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download apt<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf apt*<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# rm apt*.tar.gzbelow line<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download iptables<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf iptables*<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# rm iptables*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download logrotate<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf logrotate*<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# rm logrotate*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download pacman<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf pacman*<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# rm pacman*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# cd phpapp[\/shell]<\/p>\n

Open metadata.rb , add below line<\/p>\n

depends “apache2”<\/em><\/p>\n

Open recipes\/default.rb , add below lines<\/p>\n

include_recipe “apache2”<\/em><\/p>\n

\u00a0apache_site “default” do<\/em><\/p>\n

\u00a0 enable true<\/em><\/p>\n

end<\/em><\/p>\n

[shell]root@ankush:~\/chef-repo\/cookbooks\/phpapp# cd ..\/..[\/shell]<\/p>\n

Create a new file called solo.rb in your text editor & make below entries<\/p>\n

file_cache_path “\/root\/chef-solo”<\/em><\/p>\n

cookbook_path “\/root\/chef-repo\/cookbooks”<\/em><\/p>\n

This file configures chef-solo, telling it where to keep its cache of files and where our cookbooks are.<\/p>\n

Now create a file called web.json & add below lines<\/p>\n

{<\/em><\/p>\n

“run_list”: [ “recipe[apt]”, “recipe[phpapp]” ]<\/em><\/p>\n

}<\/em><\/p>\n

Why have we not included the apt cookbook inside our recipe as we did with the apache2 cookbook? It’s because our PHP application requires Apache to function but we don’t necessarily want to tie our cookbook to platforms that only support apt.<\/p>\n

[shell]root@ankush#chef-solo -c solo.rb -j web.json[\/shell]<\/p>\n

Now open the page in browser it will show default page for apache.<\/p>\n

Installing mysql<\/span><\/strong><\/p>\n

[shell]root@ankush:~\/chef-repo# cd cookbooks<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download mysql<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf mysql*<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# rm mysql-*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# cd mysql\/recipes\/<\/p>\n

root@ankush:~\/chef-repo\/cookbooks\/mysql\/recipes# ls<\/p>\n

root@ankush:~\/chef-repo\/cookbooks\/mysql\/recipes# cd ..\/..\/phpapp[\/shell]<\/p>\n

Open metadata.rb, add below lines<\/p>\n

depends “mysql”<\/em><\/p>\n

Open recipes\/default.rb , add below lines<\/p>\n

include_recipe “apache2”<\/em><\/p>\n

include_recipe “mysql::client”<\/em><\/span> —- This to be added<\/strong><\/p>\n

include_recipe “mysql::server”<\/em><\/span>\u00a0\u00a0 —- This to be added<\/strong><\/p>\n

apache_site “default” do<\/em><\/p>\n

\u00a0 enable true<\/em><\/p>\n

end<\/em><\/p>\n

Run chef-solo again<\/p>\n

[shell]root@ankush:~\/chef-repo\/cookbooks\/phpapp# cd ..\/..<\/p>\n

root@ankush:~\/chef-repo# chef-solo -c solo.rb -j web.json[\/shell]<\/p>\n

You will now get errors like<\/p>\n

FATAL: Stacktrace dumped to \/root\/chef-solo\/chef-stacktrace.out<\/em><\/strong><\/p>\n

FATAL: Chef::Exceptions::CookbookNotFound: Cookbook build-essential not found. If you’re loading build-essential from another cookbook, make sure you configure the dependency in your metadata<\/em><\/strong><\/p>\n

Open cookbooks\/mysql\/metadata.rb & specify the dependencies<\/p>\n

depends “openssl”<\/em><\/p>\n

depends “build-essential”<\/em><\/p>\n

[shell]root@ankush:~\/chef-repo# cd cookbooks<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download openssl<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf openssl*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# rm openssl*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download build-essential<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf build-essential-*.tar.gz&gt;<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# rm build-essential-*.tar.gz[\/shell]<\/p>\n

Now we’ve fulfilled those dependencies let’s try and re-run chef-solo!<\/p>\n

[shell]root@ankush:~\/chef-repo\/cookbooks# cd ..<\/p>\n

root@ankush:~\/chef-repo# chef-solo -c solo.rb -j web.json[\/shell]<\/p>\n

Again we have an ERROR<\/strong><\/p>\n

FATAL: You must set node[‘mysql’][‘server_debian_password’], node[‘mysql’][‘server_root_password’], node[‘mysql’][‘server_repl_password’] in chef-solo mode. For more information, see https:\/\/github.com\/opscode-cookbooks\/mysql#chef-solo-note<\/em><\/strong><\/p>\n

Open web.json to specify the mysql root password<\/p>\n

{<\/p>\n

“mysql”: {“server_root_password”: “ankush”, “server_debian_password”: “ankush”, “server_repl_password”: “ankush”}<\/em>,<\/span><\/p>\n

“run_list”: [ “recipe[apt]”, “recipe[phpapp]” ]<\/em><\/p>\n

}<\/p>\n

[shell]root@ankush:~\/chef-repo# chef-solo -c solo.rb -j web.json[\/shell]<\/p>\n

Now to install PHP<\/strong><\/p>\n

[shell]root@ankush:~\/chef-repo# cd cookbooks\/<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download php<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf php*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# rm php*.tar.gz[\/shell]<\/p>\n

The php cookbook depends on the xml, yum-epel, windows, and iis cookbooks, so we’ll need those even though we won’t be using all of them. We’ll also have to install sub-dependencies yum (a dependency of yum-epel), chef_handler, and powershell (dependencies of windows).<\/p>\n

[shell]root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download xml<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf xml-*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download yum<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf yum-*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download yum-epel<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf yum-epel-*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download powershell<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf powershell-*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# knife cookbook site download iis<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# tar zxf iis-*.tar.gz<\/p>\n

root@ankush:~\/chef-repo\/cookbooks# rm *.tar.gz[\/shell]<\/p>\n

Let’s use the php cookbook in our cookbook.<\/p>\n

[shell]root@ankush:~\/chef-repo\/cookbooks# cd phpapp[\/shell]<\/p>\n

Open metadata.rb add below line<\/p>\n

depends “php”<\/em><\/p>\n

Open recipes\/default.rb , add below lines<\/p>\n

include_recipe “php”<\/em><\/p>\n

include_recipe “php::module_mysql”<\/em><\/p>\n

include_recipe “apache2::mod_php5”<\/em><\/p>\n

Save the file and we’re good to run chef-solo again to install all of those things<\/p>\n

[shell]root@ankush:~\/chef-repo\/cookbooks\/phpapp# cd ..\/..<\/p>\n

root@ankush:~\/chef-repo# chef-solo -c solo.rb -j web.json[\/shell]<\/p>\n

So that’s PHP installed. Let’s confirm that by creating a test page. Open \/var\/www\/test.php<\/em><\/strong> in your editor.<\/p>\n

<?php phpinfo(); ?><\/em><\/strong><\/p>\n

Now goto http:\/\/yourserver\/test.php , you will see the phpinfo page.<\/p>\n","protected":false},"excerpt":{"rendered":"

Chef as we all know is a Configuration Management Tool. It enables Infrastructure as Code. Recently I had to give a technical presentation on Chef in my current organization which helped me to get some insights into how Chef works & how it eases the deployment process. In this article I would touch upon very […]<\/p>\n","protected":false},"author":91,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":5},"categories":[7],"tags":[2391,2390],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/12590"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/91"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=12590"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/12590\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=12590"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=12590"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=12590"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}