Skip to content

Configuration management with chef #586

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
katmutua wants to merge 7 commits into from
Closed

Configuration management with chef #586

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
8583bf5
Add practical reference for ansible
katmutua Oct 6, 2015
f870869
Include preliminery content on chef
katmutua Oct 6, 2015
c39415e
Make grammar changes to last commit
katmutua Oct 6, 2015
823b390
More notes on chef for configuration management
katmutua Oct 6, 2015
14e4864
More notes on chef for configuration management
katmutua Oct 6, 2015
5ad8a9a
More notes on chef for configuration management
katmutua Oct 6, 2015
139c48f
More notes on chef for configuration management
katmutua Oct 6, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 26 additions & 3 deletions docs/scenarios/admin.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -232,14 +232,37 @@ The Ansible playbook will ping all of the servers in the :file:`hosts.yml` file.
You can also select groups of servers using Ansible. For more information
about Ansible, read the `Ansible Docs <http://docs.ansible.com/>`_.

`An Ansible tutorial <https://serversforhackers.com/an-ansible-tutorial/>`_ is also a
great and detailed introduction to getting started with Ansible.


Chef
----
`Chef <https://www.chef.io/chef/>`_ is a systems and cloud infrastructure automation
framework that makes it easy to deploy servers and applications to any physical,
virtual, or cloud location. In case this is your choice for configuration management,
you will primarily use Ruby to write your infrastructure code.

Chef clients run on every server that is part of your infrastructure and these regularly
check with your Chef server to ensure your system is always aligned and represents the
desired state. Since each individual server has its own distinct Chef client, each server
configures itself and this distributed approach makes Chef a scalable automation platform.

Chef works by using custom recipes (configuration elements), implemented in cookbooks. Cookbooks, which are basically
packages for infrastructure choices, are usually stored in your Chef server.
Read the `Digital Ocean tutorial series <https://www.digitalocean.com/community/tutorials/how-to-install-a-chef-server-workstation-and-client-on-ubuntu-vps-instances>`_ on chef to learn how to create a simple Chef Server.

To create a simple cookbook the `knife <https://docs.chef.io/knife.html>`_ command is used:

.. code-block:: console

knife cookbook create cookbook_name

.. todo:: Write about Chef
`Getting started with Chef <http://gettingstartedwithchef.com/first-steps-with-chef.html>`_
is a good starting point for Chef Beginners and many community maintained cookbooks that can
serve as a good reference or tweaked to serve your infrustructure configuration needs can be
found on the `Chef Supermarket <https://supermarket.chef.io/cookbooks>`_.

`Chef Documentation
<http://wiki.opscode.com/display/chef/Documentation>`_

Puppet
------
Expand Down