From 7cbde1d724be9c748b87cf5175e6e4be7829d909 Mon Sep 17 00:00:00 2001 From: 75072107 <44470386+75072107@users.noreply.github.com> Date: Sun, 31 Mar 2019 10:58:29 -0700 Subject: [PATCH] added a ' quick search ' method. (#28660) --- guide/english/chef/index.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/guide/english/chef/index.md b/guide/english/chef/index.md index fdb63a1496..1f12729162 100644 --- a/guide/english/chef/index.md +++ b/guide/english/chef/index.md @@ -8,11 +8,13 @@ title: Chef Chef enables programmers and system administrators to work together. Instead of developers writing applications and then waiting on Ops staff to figure out how to deploy the software, Chef serves both communities. Chef moves the process from a herky-jerky release cycle to a continuous delivery model by enabling an effective and automated workflow—a central goal of the DevOps movement. #### How Chef Works -

Chef stores collections of recipes in a cookbook. One cookbook should relate to a single task, but can have a number of different server configurations involved (for example a web application with a database will have two recipes, one for each part, stored together in a cookbook).

+Chef stores collections of recipes in a cookbook. One cookbook should relate to a single task, but can have a number of different server configurations involved (for example a web application with a database will have two recipes, one for each part, stored together in a cookbook). -

There is a Chef server which stores each of these cookbooks and as a new chef client node checks in with the server, recipes are sent to tell the node how to configure itself.

+There is a Chef server which stores each of these cookbooks and as a new chef client node checks in with the server, recipes are sent to tell the node how to configure itself. -

The client will then check in every now and again to make sure that no changes have occurred, and nothing needs to change. If it does, then the client deals with it. Patches and updates can be rolled out over your entire infrastructure by changing the recipe. There is no need to interact with each machine individually.

+The client will then check in every now and again to make sure that no changes have occurred, and nothing needs to change. If it does, then the client deals with it. Patches and updates can be rolled out over your entire infrastructure by changing the recipe. There is no need to interact with each machine individually. + +Clients should be able to quickly find recipes they desire by using Tags. For example, a Beef Wellington may have tags such as 'beef', 'puff pastry', and 'steak'. This may help the client find not only the recipe he wants but other similar recipes that might pique his interest or suit his cooking style. #### Chef Configuration ![Image Title](https://regmedia.co.uk/2015/10/07/chef_configuration_management.jpg "Chef Configuration process chart")