Configuring chef Part-2

Lets recap what all we have done in the last blog :

1.) Setup workstation and chef-repo.
2.) Registered on chef to use hosted chef as the chef-server.
3.) Bootstrapped a node to be managed by the chef-server.
4.) Downloaded the “apache” cookbook in our chef-repo.
5.) Uploaded the “apache” cookbook to the chef-server.
6.) Added the recipe[apache] in the run-list of the node.
7.) Ran the chef-client on the client to apply the cookbook.

Now lets continue, and try to understand some more concepts around chef and see them in action.
Read More »

Configuring Chef part 1

Below are the first steps in getting started with using chef.
The three main components of chef are :
1.) Work station
This is the developer’s machine will be used to author cookbooks and recipes and upload them to the chef-server using the command line utility called knife.
2.) Chef-Server
This is the main server on which all the cookbooks, roles, policies are uploaded.
3.) Node
This is the instance which would be provisioned by applying the cookbooks uploaded on the chef-server.

So, lets get started:
Read More »

chef-solo with vagrant

To learn the concepts of chef, we can start by using chef-solo with Vagrant.
See my previous post on Vagrant to install vagrant and know more about it.

Next, lets install chef-solo on our machine.
We will install chef-solo using ruby gem,(for both Linux and Mac) make sure you have ruby installed.

root@intro:~# cd ~
root@intro:~# sudo gem install chef
Thank you for installing Chef!

So, now we have installed chef-solo and vagrant on our machine.
In this exercise, we will try and install apache2 on an ubuntu virtual machine (virtual box)
using chef-solo and vagrant.
To begin we would first need to understand few concepts; which would be required to run chef-solo in Vagrant.
Read More »