You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/scenarios/admin.rst
+15-5Lines changed: 15 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -231,6 +231,7 @@ To run the playbook:
231
231
The Ansible playbook will ping all of the servers in the :file:`hosts.yml` file.
232
232
You can also select groups of servers using Ansible. For more information
233
233
about Ansible, read the `Ansible Docs <http://docs.ansible.com/>`_.
234
+
234
235
`An Ansible tutorial <https://serversforhackers.com/an-ansible-tutorial/>`_ is also a
235
236
great and detailed introduction to getting started with Ansible.
236
237
@@ -239,19 +240,28 @@ Chef
239
240
----
240
241
`Chef <https://www.chef.io/chef/>`_ is a systems and cloud infrastructure automation
241
242
framework that makes it easy to deploy servers and applications to any physical,
242
-
virtual, or cloud location. Chef works by using custom recipes which can simply be defined
243
-
as configuration elements which implement your polices.
244
-
These custom recipes are usually stored in your Chef server.
243
+
virtual, or cloud location. In case this is your choice for configuration management,
244
+
you will primarily use Ruby to write your infrastructure code.
245
245
246
246
Chef clients run on every server that is part of your infrastructure and these regularly
247
247
check with your Chef server to ensure your system is always aligned and represents the
248
248
desired state. Since each individual server has its own distinct Chef client, each server
249
249
configures itself and this distributed approach makes Chef a scalable automation platform.
250
250
251
+
Chef works by using custom recipes (configuration elements), implemented in cookbooks. Cookbooks, which are basically
252
+
packages for infrastructure choices, are usually stored in your Chef server.
253
+
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.
254
+
255
+
To create a simple cookbook the `knife <https://docs.chef.io/knife.html>`_ command is used:
256
+
257
+
.. code-block:: console
258
+
259
+
knife cookbook create cookbook_name
260
+
251
261
`Getting started with Chef <http://gettingstartedwithchef.com/first-steps-with-chef.html>`_
252
262
is a good starting point for Chef Beginners and many community maintained cookbooks that can
253
-
serve as a good reference or tweaked to server your infrustructure connfiguration needs can be
254
-
found at the `Chef Supermarket <https://supermarket.chef.io/cookbooks>`_.
263
+
serve as a good reference or tweaked to serve your infrustructure configuration needs can be
264
+
found on the `Chef Supermarket <https://supermarket.chef.io/cookbooks>`_.
0 commit comments