{"id":8962,"date":"2015-04-17T14:00:07","date_gmt":"2015-04-17T05:00:07","guid":{"rendered":"http:\/\/www.creationline.com\/?p=8962"},"modified":"2023-08-29T14:02:09","modified_gmt":"2023-08-29T05:02:09","slug":"english-translation-lets-begin-infrastructure-as-code-with-knife-zero-getchef","status":"publish","type":"post","link":"https:\/\/www.creationline.com\/tech-blog\/cloudnative\/chef\/8962","title":{"rendered":"[English Translation] Let’s begin Infrastructure as Code with Knife-Zero #getchef"},"content":{"rendered":"

This is the English translation of Knife-Zero\u3067Infrastructure as Code\u3092\u59cb\u3081\u3088\u3046<\/a> (2014\/12\/24).<\/p>\n

\u25a0What is Chef?<\/a><\/h2>\n

Chef<\/a> is a tool for centralized management of IT infrastructure information. Chef is described as follows in \"An Overview of Chef<\/a>\":<\/p>\n

Chef is a powerful automation platform that transforms complex infrastructure into code, bringing your servers and services to life. (snip)<\/p>\n

Chef is built around simple concepts: achieving desired state, centralized modeling of IT infrastructure, and resource primitives that serve as building blocks. (snip)<\/p><\/blockquote>\n

The real value of Chef is: enables centralized management of IT infrastructure information, separates each component of the infrastructure into more detailed part so that they can be reused, and then converges those components to desired state.<\/p>\n

One of the great features of Chef, which is enabling centralized management of IT infrastructure information, tends to be overlooked in many cases. Chef can be used simply as an automated setup tool, too. However, it would be a waste not to utilize this great feature.<\/p>\n

\u25a0Installing Chef<\/a><\/h2>\n

Now, let's try to install Chef. You don't need Chef Server this time. We will use Ubuntu 12.04 LTS as a workstation and install only the client package.
\nWe will also use Ubuntu 12.04 LTS as a remote node to be managed.<\/p>\n

\u25cfInstalling Chef Development Kit<\/a><\/h3>\n

The client package for workstation is Chef Development Kit<\/a>, commonly called \"Chef DK<\/strong>\". It contains not only the Chef client program, but also tools necessary to do development works with Chef, and Ruby that is required to operate Chef. This means you do not need to either install Ruby separately, or use RubyGems to install Chef<\/strong>.<\/p>\n

Chef DK is available for download from Chef Development Kit | Chef Downloads | Chef<\/a>. Select OS, Chef DK version and OS version that suit your environment. This time, we have downloaded chefdk_0.3.5-1_amd64.deb<\/strong>. Let's install it now.<\/p>\n


\nubuntu@ws:~$ sudo dpkg -i chefdk_0.3.5-1_amd64.deb
\nSelecting previously unselected package chefdk.
\n(Reading database ... 49102 files and directories currently installed.)
\nPreparing to unpack chefdk_0.3.5-1_amd64.deb ...
\nUnpacking chefdk (0.3.5-1) ...
\nSetting up chefdk (0.3.5-1) ...
\nThank you for installing Chef Development Kit!
\nubuntu@ws:~$
\n<\/code><\/p>\n

\u25cfInstalling Knife-Zero<\/a><\/h3>\n

Use Knife-Zero<\/a>, we will not use the Chef Client program that comes with Chef DK here.<\/p>\n


\nubuntu@ws:~$ chef gem install knife-zero --no-document
\nFetching: knife-zero-1.1.0.gem (100%)
\nWARNING: You don't have \/home\/ubuntu\/.chefdk\/gem\/ruby\/2.1.0\/bin in your PATH,
\ngem executables will not run.
\nSuccessfully installed knife-zero-1.1.0
\n1 gem installed
\nubuntu@ws:~$
\n<\/code><\/p>\n

Warning here is not related to Knife-Zero, so you can ignore it.<\/p>\n

\u25cfPreparations: Creating SSH key pair<\/a><\/h3>\n

Since Knife-Zero uses SSH to operate the remote node, create an SSH private\/public key pair in advance. Here, we generate a key pair without a passphrase.<\/p>\n


\nubuntu@ws:~$ ssh-keygen -N ''
\nGenerating public\/private rsa key pair.
\nEnter file in which to save the key (\/home\/ubuntu\/.ssh\/id_rsa):
\nCreated directory '\/home\/ubuntu\/.ssh'.
\nYour identification has been saved in \/home\/ubuntu\/.ssh\/id_rsa.
\nYour public key has been saved in \/home\/ubuntu\/.ssh\/id_rsa.pub.
\nThe key fingerprint is:
\n9a:72:67:23:3a:5c:2e:e9:74:03:44:0f:5e:87:0e:67 ubuntu@ws.example.jp
\nThe key's randomart image is:
\n+--[ RSA 2048]----+
\n| o ... |
\n| o.+E. |
\n| o=. |
\n| . . |
\n| . S |
\n| ..o |
\n| .o+B + |
\n| .==.= . |
\n| .oo |
\n+-----------------+
\nubuntu@ws:~$
\n<\/code><\/p>\n

As you may know, the SSH daemon must run on the target remote node, so start the node beforehand. Also, place the public key created in the previous step on the remote node.<\/p>\n


\nubuntu@node:~$ mkdir .ssh
\nubuntu@node:~$ cat > .ssh\/authorized_keys
\nssh-rsa (snip) ubuntu@ws.example.jp
\nubuntu@node:~$
\n<\/code><\/p>\n

For convenience, set the login account in such a way that enables to execute sudo without password to acquire a root privilege.<\/p>\n

\u25a0Creating a working environment<\/a><\/h2>\n

Create a directory tree to be used as an environment to execute Knife-Zero, and then place it under the management of git. This directory tree is called chef-repo<\/a> and this is where the infrastructure information is transformed into code (Infrastructure as Code).<\/p>\n


\nubuntu@ws:~$ chef generate repo chef-repo
\nCompiling Cookbooks...
\nRecipe: code_generator::repo
\n* directory[\/home\/ubuntu\/chef-repo] action create
\n- create new directory \/home\/ubuntu\/chef-repo
\n:
\n(diff output suppressed by config)
\nubuntu@ws:~$<\/code><\/p>\n

<\/code><\/code><\/p>\n

ubuntu@ws:~$ cd chef-repo
\nubuntu@ws:~\/chef-repo$ tree
\n.
\n\u251c\u2500\u2500 LICENSE
\n\u251c\u2500\u2500 README.md
\n\u251c\u2500\u2500 Rakefile
\n\u251c\u2500\u2500 certificates
\n\u2502 \u2514\u2500\u2500 README.md
\n\u251c\u2500\u2500 chefignore
\n\u251c\u2500\u2500 config
\n\u2502 \u2514\u2500\u2500 rake.rb
\n\u251c\u2500\u2500 cookbooks
\n\u2502 \u2514\u2500\u2500 README.md
\n\u251c\u2500\u2500 data_bags
\n\u2502 \u2514\u2500\u2500 README.md
\n\u251c\u2500\u2500 environments
\n\u2502 \u2514\u2500\u2500 README.md
\n\u2514\u2500\u2500 roles
\n\u2514\u2500\u2500 README.md<\/p>\n

<\/code><\/code><\/p>\n

6 directories, 10 files
\nubuntu@ws:~\/chef-repo$<\/p>\n


\n<\/code><\/p>\n

ubuntu@ws:~\/chef-repo$ git init
\nInitialized empty Git repository in \/home\/ubuntu\/chef-repo\/.git\/
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Prepare the config file, which will be managed by Knife-Zero from now on.<\/p>\n


\nubuntu@ws:~\/chef-repo$ mkdir .chef
\nubuntu@ws:~\/chef-repo$ echo 'local_mode true' > .chef\/knife.rb
\nubuntu@ws:~\/chef-repo$ cat .chef\/knife.rb
\nlocal_mode true
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

\u25a0Installing Chef-Client to Node<\/a><\/h2>\n

Install Chef-Client on the remote node to be managed by Chef.
\nUse \"knife zero bootstrap<\/strong>\" command for installation. \"node.example.jp<\/strong>\" specifies a node's host name, \"-x ubuntu<\/strong>\" specifies a login user name, and \"--sudo<\/strong>\" enables to execute sudo command for getting a root privilege.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero bootstrap node.example.jp -x ubuntu --sudo
\nConnecting to node.example.jp
\nnode.example.jp Installing Chef Client...
\nnode.example.jp --2014-12-19 12:06:20-- https:\/\/www.opscode.com\/chef\/install.sh
\nnode.example.jp Resolving www.opscode.com (www.opscode.com)... 184.106.28.90
\nnode.example.jp Connecting to www.opscode.com (www.opscode.com)|184.106.28.90|:443... connected.
\nnode.example.jp HTTP request sent, awaiting response... 200 OK
\nnode.example.jp Length: 18285 (18K) [application\/x-sh]
\nnode.example.jp Saving to: `STDOUT'
\nnode.example.jp
\n100%[======================================>] 18,285 --.-K\/s in 0.002s
\nnode.example.jp
\nnode.example.jp 2014-12-19 12:06:21 (7.52 MB\/s) - stdout saved [18285\/18285]
\nnode.example.jp
\nnode.example.jp Downloading Chef 11 for ubuntu...
\nnode.example.jp downloading https:\/\/www.opscode.com\/chef\/metadata?v=11&prerelease=false&nightlies=false&p=ubuntu&pv=12.04&m=x86_64
\nnode.example.jp to file \/tmp\/install.sh.1100\/metadata.txt
\nnode.example.jp trying wget...
\nnode.example.jp url https:\/\/opscode-omnibus-packages.s3.amazonaws.com\/ubuntu\/12.04\/x86_64\/chef_11.16.4-1_amd64.deb
\nnode.example.jp md5 2ffff5b4d80e4dcffc917f8eb2003a31
\nnode.example.jp sha256 28b08975e7e33ac46c888616ec7fa232a0c624aeeda81e58a6047d2c6b62edfb
\nnode.example.jp downloaded metadata file looks valid...
\nnode.example.jp downloading https:\/\/opscode-omnibus-packages.s3.amazonaws.com\/ubuntu\/12.04\/x86_64\/chef_11.16.4-1_amd64.deb
\nnode.example.jp to file \/tmp\/install.sh.1100\/chef_11.16.4-1_amd64.deb
\nnode.example.jp trying wget...
\nnode.example.jp Comparing checksum with sha256sum...
\nnode.example.jp Installing Chef 11
\nnode.example.jp installing with dpkg...
\nnode.example.jp Selecting previously unselected package chef.
\n(Reading database ... 49102 files and directories currently installed.)
\nnode.example.jp Preparing to unpack ...\/chef_11.16.4-1_amd64.deb ...
\nnode.example.jp Setting up chef (11.16.4-1) ...
\nnode.example.jp Thank you for installing Chef!
\nnode.example.jp Starting first Chef Client run...
\n:
\nnode.example.jp Starting Chef Client, version 11.16.4
\nnode.example.jp Creating a new client identity for node.example.jp using the validator key.
\nnode.example.jp resolving cookbooks for run list: []
\nnode.example.jp Synchronizing Cookbooks:
\nnode.example.jp Compiling Cookbooks...
\nnode.example.jp [2014-12-19T12:06:48+09:00] WARN: Node node.example.jp has an empty run list.
\nnode.example.jp Converging 0 resources
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 0\/0 resources updated in 1.443860973 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Chef-Client is automatically downloaded and installed on the node.
\nThe node is now under the management of Chef. The data to be managed is stored in the Chef-Repo directory of the workstation, not in Chef Server.<\/p>\n


\nubuntu@ws:~\/chef-repo$ cat clients\/node.example.jp.json | cat
\n{
\n\"name\": \"node.example.jp\",
\n\"public_key\": \"-----BEGIN PUBLIC KEY-----\\n(snip)\\n-----END PUBLIC KEY-----\\n\"
\n}
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ cat nodes\/node.example.jp.json
\n{
\n\"name\": \"node.example.jp\",
\n\"normal\": {
\n\"tags\": [<\/code><\/p>\n

<\/code><\/code><\/p>\n

]
\n},
\n\"automatic\": {
\n\"network\": {
\n\"interfaces\": {
\n\"lo\": {
\n\"mtu\": \"16436\",
\n\"flags\": [
\n\"LOOPBACK\",
\n\"UP\",
\n\"LOWER_UP\"
\n],
\n\"encapsulation\": \"Loopback\",
\n\"addresses\": {
\n\"127.0.0.1\": {
\n\"family\": \"inet\",
\n\"prefixlen\": \"8\",
\n\"netmask\": \"255.0.0.0\",
\n\"scope\": \"Node\"
\n},
\n\"::1\": {
\n\"family\": \"inet6\",
\n\"prefixlen\": \"128\",
\n\"scope\": \"Node\"
\n}
\n},
\n\"state\": \"unknown\"
\n},
\n\"eth0\": {
\n\"type\": \"eth\",
\n\"number\": \"0\",
\n\"mtu\": \"1500\",
\n\"flags\": [
\n\"BROADCAST\",
\n\"MULTICAST\",
\n\"UP\",
\n\"LOWER_UP\"
\n],
\n\"encapsulation\": \"Ethernet\",
\n\"addresses\": {
\n\"52:54:00:8E:F7:2A\": {
\n\"family\": \"lladdr\"
\n},
\n\"192.168.122.67\": {
\n\"family\": \"inet\",
\n\"prefixlen\": \"24\",
\n\"netmask\": \"255.255.255.0\",
\n\"broadcast\": \"192.168.122.255\",
\n\"scope\": \"Global\"
\n},
\n\"fe80::5054:ff:fe8e:f72a\": {
\n\"family\": \"inet6\",
\n\"prefixlen\": \"64\",
\n\"scope\": \"Link\"
\n}
\n},
\n\"state\": \"up\",
\n\"arp\": {
\n\"192.168.122.209\": \"52:54:00:62:c3:07\"
\n},
\n:
\n\"recipes\": [<\/p>\n

<\/code><\/code><\/p>\n

],
\n\"roles\": [<\/p>\n


\n<\/code><\/p>\n

]
\n}
\n}
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Let's use this opportunity to register the workstation itself.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero bootstrap ws.example.jp -x ubuntu --sudo
\nConnecting to ws.example.jp
\nws.example.jp Starting first Chef Client run...
\n:
\nws.example.jp Starting Chef Client, version 11.18.0.rc.1
\nws.example.jp Creating a new client identity for ws.example.jp using the validator key.
\nws.example.jp resolving cookbooks for run list: []
\nws.example.jp Synchronizing Cookbooks:
\nws.example.jp Compiling Cookbooks...
\nws.example.jp [2014-12-19T12:33:12+09:00] WARN: Node ws.example.jp has an empty run list.
\nws.example.jp Converging 0 resources
\nws.example.jp
\nws.example.jp Running handlers:
\nws.example.jp Running handlers complete
\nws.example.jp Chef Client finished, 0\/0 resources updated in 1.627046827 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ ls -l clients
\ntotal 8
\n-rw-rw-r-- 1 ubuntu ubuntu 511 12\u6708 19 12:06 node.example.jp.json
\n-rw-rw-r-- 1 ubuntu ubuntu 509 12\u6708 19 12:33 ws.example.jp.json
\nubuntu@ws:~\/chef-repo$ ls -l nodes
\ntotal 64
\n-rw-rw-r-- 1 ubuntu ubuntu 31169 12\u6708 19 12:23 node.example.jp.json
\n-rw-rw-r-- 1 ubuntu ubuntu 31157 12\u6708 19 12:33 ws.example.jp.json
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Manage nodes using Knife-Zero from now on.<\/p>\n

\u25a0Managing nodes with knife command<\/a><\/h2>\n

We will now try to get the information registered by using knife command. We use knife search<\/a> here. The example below shows acquiring an IP address of a node.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife search 'name:*' --attribute ipaddress
\n2 items found<\/code><\/p>\n

<\/code><\/code><\/p>\n

node.example.jp:
\nipaddress: 192.168.122.67<\/p>\n

<\/code><\/code><\/p>\n

ws.example.jp:
\nipaddress: 192.168.122.209<\/p>\n


\n<\/code><\/p>\n

ubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

These are coming from the data stored in Chef-Repo.
\nInformation about each node can be displayed by using argument.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife search 'name:node*' --attribute fqdn
\n1 items found<\/code><\/p>\n

<\/code><\/code><\/p>\n

node.example.jp:
\nfqdn: node.example.jp<\/p>\n

<\/code><\/code><\/p>\n

ubuntu@ws:~\/chef-repo$ knife search 'name:ws*' --attribute fqdn
\n1 items found<\/p>\n

<\/code><\/code><\/p>\n

ws.example.jp:
\nfqdn: ws.example.jp<\/p>\n


\n<\/code><\/p>\n

ubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

knife ssh<\/a> allows you to execute commands remotely on each node.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife ssh 'name:*' 'uname -a'
\nnode.example.jp Linux node.example.jp 3.2.0-74-generic #109-Ubuntu SMP Tue Dec 9 16:45:49 UTC 2014 x86_64 x86_64 x86_64 GNU\/Linux
\nws.example.jp Linux ws.example.jp 3.2.0-74-generic #109-Ubuntu SMP Tue Dec 9 16:45:49 UTC 2014 x86_64 x86_64 x86_64 GNU\/Linux
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

\u25a0Creating cookbooks<\/a><\/h2>\n

Chef files that enable infrastructure as code and describe the desired state are called Cookbook<\/a>. You can write a cookbook without knowing Ruby<\/strong>. Let's forget for a moment that cookbooks are internal DSL in Ruby. All we need to know is how to write a cookbook.<\/p>\n

\u25cfInstalling one package<\/a><\/h3>\n

Let's create a cookbook to install an ntp<\/strong> package.
\nUse \"chef generate cookbook<\/strong>\" command to prepare a cookbook base structure. Name this cookbook as \"ntp<\/strong>\".<\/p>\n


\nubuntu@ws:~\/chef-repo$ chef generate cookbook cookbooks\/ntp
\nCompiling Cookbooks...
\nRecipe: code_generator::cookbook
\n* directory[\/home\/ubuntu\/chef-repo\/cookbooks\/ntp] action create
\n- create new directory \/home\/ubuntu\/chef-repo\/cookbooks\/ntp
\n:
\n(diff output suppressed by config)
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ tree cookbooks\/ntp
\ncookbooks\/ntp
\n\u251c\u2500\u2500 Berksfile
\n\u251c\u2500\u2500 README.md
\n\u251c\u2500\u2500 chefignore
\n\u251c\u2500\u2500 metadata.rb
\n\u2514\u2500\u2500 recipes
\n\u2514\u2500\u2500 default.rb<\/code><\/p>\n


\n<\/code><\/p>\n

1 directory, 5 files
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

cookbooks\/ntp\/recipes\/default.rb<\/strong> is called \"default Recipe<\/a>\" of \"ntp cookbook\". Usually, cookbook is a collection of various types of data except for recipes. However, you could consider cookbooks and recipes roughly the same thing.
\nNow, let's edit the recipe and install the ntp<\/strong> package.<\/p>\n


\n#
\n# Cookbook Name:: ntp
\n# Recipe:: default
\n#
\n# Copyright (c) 2014 The Authors, All Rights Reserved.<\/code><\/p>\n


\n<\/code><\/p>\n

package 'ntp'
\n<\/code><\/p>\n

It's as simple as this. Only one line has been added except the original comments. You can't find any Ruby element.
\nApply this recipe to the target node.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife node run_list add node.example.jp 'recipe[ntp]'
\nnode.example.jp:
\nrun_list: recipe[ntp]
\nubuntu@ws:~\/chef-repo$ knife node run_list add ws.example.jp 'recipe[ntp]'
\nws.example.jp:
\nrun_list: recipe[ntp]
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Before executing chef-client on the node and actually applying it, try why-run (similar to dry-run) with -W<\/strong> option.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero chef_client 'name:*' -x ubuntu --sudo -W
\nnode.example.jp [2014-12-22T13:09:25+09:00] WARN:
\n:
\nnode.example.jp Starting Chef Client, version 11.16.4
\nnode.example.jp resolving cookbooks for run list: [\"ntp\"]
\nnode.example.jp Synchronizing Cookbooks:
\nnode.example.jp - ntp
\nnode.example.jp Compiling Cookbooks...
\nnode.example.jp Converging 1 resources
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * package[ntp] action install
\nnode.example.jp - Would install version 1:4.2.6.p3+dfsg-1ubuntu3.1 of package ntp
\nnode.example.jp [2014-12-22T13:09:26+09:00] WARN: In whyrun mode, so NOT performing node save.
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 1\/1 resources would have been updated
\nws.example.jp [2014-12-22T13:09:27+09:00] WARN:
\n:
\nws.example.jp Starting Chef Client, version 11.18.0.rc.1
\nws.example.jp resolving cookbooks for run list: [\"ntp\"]
\nws.example.jp Synchronizing Cookbooks:
\nws.example.jp - ntp
\nws.example.jp Compiling Cookbooks...
\nws.example.jp Converging 1 resources
\nws.example.jp Recipe: ntp::default
\nws.example.jp * package[ntp] action install
\nws.example.jp - Would install version 1:4.2.6.p3+dfsg-1ubuntu3.1 of package ntp
\nws.example.jp [2014-12-22T13:09:28+09:00] WARN: In whyrun mode, so NOT performing node save.
\nws.example.jp
\nws.example.jp Running handlers:
\nws.example.jp Running handlers complete
\nws.example.jp Chef Client finished, 1\/1 resources would have been updated
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

You can see that the ntp<\/strong> package is being installed. Now, remove the -W option and apply recipe to converge the node to the desired state.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero chef_client 'name:*' -x ubuntu --sudo
\nnode.example.jp [2014-12-22T13:14:00+09:00] WARN:
\n:
\nnode.example.jp Starting Chef Client, version 11.16.4
\nnode.example.jp resolving cookbooks for run list: [\"ntp\"]
\nnode.example.jp Synchronizing Cookbooks:
\nnode.example.jp - ntp
\nnode.example.jp Compiling Cookbooks...
\nnode.example.jp Converging 1 resources
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * package[ntp] action install
\nnode.example.jp - install version 1:4.2.6.p3+dfsg-1ubuntu3.1 of package ntp
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 1\/1 resources updated in 9.409252235 seconds
\nws.example.jp [2014-12-22T13:14:11+09:00] WARN:
\n:
\nws.example.jp Starting Chef Client, version 11.18.0.rc.1
\nws.example.jp resolving cookbooks for run list: [\"ntp\"]
\nws.example.jp Synchronizing Cookbooks:
\nws.example.jp - ntp
\nws.example.jp Compiling Cookbooks...
\nws.example.jp Converging 1 resources
\nws.example.jp Recipe: ntp::default
\nws.example.jp * package[ntp] action install
\nws.example.jp - install version 1:4.2.6.p3+dfsg-1ubuntu3.1 of package ntp
\nws.example.jp
\nws.example.jp Running handlers:
\nws.example.jp Running handlers complete
\nws.example.jp Chef Client finished, 1\/1 resources updated in 10.834032539 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

The recipe has been applied successfully. \"1\/1 resources updated<\/strong>\" indicates that there has been a change in one out of one resource of the node. Apply the recipe once again in order to check idempotency.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero chef_client 'name:*' -x ubuntu --sudo
\nnode.example.jp [2014-12-22T13:18:52+09:00] WARN:
\n:
\nnode.example.jp Starting Chef Client, version 11.16.4
\nnode.example.jp resolving cookbooks for run list: [\"ntp\"]
\nnode.example.jp Synchronizing Cookbooks:
\nnode.example.jp - ntp
\nnode.example.jp Compiling Cookbooks...
\nnode.example.jp Converging 1 resources
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * package[ntp] action install (up to date)
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 0\/1 resources updated in 0.991954497 seconds
\nws.example.jp [2014-12-22T13:18:55+09:00] WARN:
\n:
\nws.example.jp Starting Chef Client, version 11.18.0.rc.1
\nws.example.jp resolving cookbooks for run list: [\"ntp\"]
\nws.example.jp Synchronizing Cookbooks:
\nws.example.jp - ntp
\nws.example.jp Compiling Cookbooks...
\nws.example.jp Converging 1 resources
\nws.example.jp Recipe: ntp::default
\nws.example.jp * package[ntp] action install (up to date)
\nws.example.jp
\nws.example.jp Running handlers:
\nws.example.jp Running handlers complete
\nws.example.jp Chef Client finished, 0\/1 resources updated in 1.050684551 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

\"0\/1 resources updated<\/strong>\" indicates that there has been no change in any resources of the node.
\nIn order to check idempotency, uninstall the package and run the recipe once again.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife ssh 'name:*' 'sudo apt-get purge -y ntp' -x ubuntu
\nReading package lists... Done
\nBuilding dependency tree
\nReading state information... Done
\nws.example.jp The following packages were automatically installed and are no longer required:
\nws.example.jp libopts25 libcap2
\nws.example.jp Use 'apt-get autoremove' to remove them.
\nws.example.jp The following packages will be REMOVED:
\nws.example.jp ntp*
\nws.example.jp 0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
\nws.example.jp After this operation, 1,511 kB disk space will be freed.
\n(Reading database ... 100642 files and directories currently installed.)
\nws.example.jp Removing ntp ...
\nws.example.jp * Stopping NTP server ntpd [ OK ]
\nws.example.jp Purging configuration files for ntp ...
\nws.example.jp Processing triggers for man-db ...
\nws.example.jp Processing triggers for ureadahead ...
\nReading package lists... Done
\nBuilding dependency tree
\nReading state information... Done
\nnode.example.jp The following packages were automatically installed and are no longer required:
\nnode.example.jp libopts25 libcap2
\nnode.example.jp Use 'apt-get autoremove' to remove them.
\nnode.example.jp The following packages will be REMOVED:
\nnode.example.jp ntp*
\nnode.example.jp 0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
\nnode.example.jp After this operation, 1,511 kB disk space will be freed.
\n(Reading database ... 61224 files and directories currently installed.)
\nnode.example.jp Removing ntp ...
\nnode.example.jp * Stopping NTP server ntpd [ OK ]
\nnode.example.jp Purging configuration files for ntp ...
\nnode.example.jp Processing triggers for man-db ...
\nnode.example.jp Processing triggers for ureadahead ...
\nubuntu@ws:~\/chef-repo$<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero chef_client 'name:*' -x ubuntu --sudo
\nnode.example.jp [2014-12-22T13:25:47+09:00] WARN:
\n:
\nnode.example.jp Starting Chef Client, version 11.16.4
\nnode.example.jp resolving cookbooks for run list: [\"ntp\"]
\nnode.example.jp Synchronizing Cookbooks:
\nnode.example.jp - ntp
\nnode.example.jp Compiling Cookbooks...
\nnode.example.jp Converging 1 resources
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * package[ntp] action install
\nnode.example.jp - install version 1:4.2.6.p3+dfsg-1ubuntu3.1 of package ntp
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 1\/1 resources updated in 5.015853954 seconds
\nws.example.jp [2014-12-22T13:25:54+09:00] WARN:
\n:
\nws.example.jp Starting Chef Client, version 11.18.0.rc.1
\nws.example.jp resolving cookbooks for run list: [\"ntp\"]
\nws.example.jp Synchronizing Cookbooks:
\nws.example.jp - ntp
\nws.example.jp Compiling Cookbooks...
\nws.example.jp Converging 1 resources
\nws.example.jp Recipe: ntp::default
\nws.example.jp * package[ntp] action install
\nws.example.jp - install version 1:4.2.6.p3+dfsg-1ubuntu3.1 of package ntp
\nws.example.jp
\nws.example.jp Running handlers:
\nws.example.jp Running handlers complete
\nws.example.jp Chef Client finished, 1\/1 resources updated in 5.624764122 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

\"1\/1 resources updated<\/strong>\" indicates that the recipe has been applied successfully again and the resource has been updated.
\nIn addition, information stored in nodes\/<\/strong> directory of Chef-Repo directory gets updated when something like Chef-Client is executed.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ git diff
\ndiff --git a\/nodes\/node.example.jp.json b\/nodes\/node.example.jp.json
\nindex d90e315..03bea39 100644
\n--- a\/nodes\/node.example.jp.json
\n+++ b\/nodes\/node.example.jp.json
\n:
\n@@ -1207,11 +1208,11 @@
\n},
\n\"current_user\": \"ubuntu\",
\n\"root_group\": \"root\",
\n- \"ohai_time\": 1418959381.048563,
\n- \"uptime_seconds\": 2566,
\n- \"uptime\": \"42 minutes 46 seconds\",
\n- \"idletime_seconds\": 2528,
\n- \"idletime\": \"42 minutes 08 seconds\",
\n+ \"ohai_time\": 1419222348.6213446,
\n+ \"uptime_seconds\": 5229,
\n+ \"uptime\": \"1 hours 27 minutes 09 seconds\",
\n+ \"idletime_seconds\": 5154,
\n+ \"idletime\": \"1 hours 25 minutes 54 seconds\",
\n\"block_device\": {
\n\"ram0\": {
\n\"size\": \"131072\",
\n@@ -1316,10 +1317,14 @@
\n}
\n},
\n\"recipes\": [
\n-
\n+ \"ntp\",
\n+ \"ntp::default\"
\n],
\n\"roles\": [<\/code><\/p>\n

<\/code><\/code><\/code><\/p>\n

]
\n- }
\n+ },
\n+ \"run_list\": [
\n+ \"recipe[ntp]\"
\n+ ]
\n}
\ndiff --git a\/nodes\/ws.example.jp.json b\/nodes\/ws.example.jp.json
\nindex 09b10d6..099b1af 100644
\n--- a\/nodes\/ws.example.jp.json
\n+++ b\/nodes\/ws.example.jp.json
\n:
\n@@ -1207,11 +1208,11 @@
\n},
\n\"current_user\": \"ubuntu\",
\n\"root_group\": \"root\",
\n- \"ohai_time\": 1418959992.8692613,
\n- \"uptime_seconds\": 3175,
\n- \"uptime\": \"52 minutes 55 seconds\",
\n- \"idletime_seconds\": 3127,
\n- \"idletime\": \"52 minutes 07 seconds\",
\n+ \"ohai_time\": 1419222354.9337227,
\n+ \"uptime_seconds\": 5235,
\n+ \"uptime\": \"1 hours 27 minutes 15 seconds\",
\n+ \"idletime_seconds\": 5117,
\n+ \"idletime\": \"1 hours 25 minutes 17 seconds\",
\n\"block_device\": {
\n\"ram0\": {
\n\"size\": \"131072\",
\n@@ -1316,10 +1317,14 @@
\n}
\n},
\n\"recipes\": [
\n-
\n+ \"ntp\",
\n+ \"ntp::default\"
\n],
\n\"roles\": [<\/p>\n


\n<\/code><\/code><\/code><\/p>\n

]
\n- }
\n+ },
\n+ \"run_list\": [
\n+ \"recipe[ntp]\"
\n+ ]
\n}
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

\u25cfInstalling multiple packages<\/a><\/h3>\n

<\/code><\/code><\/p>\n

Let's create a cookbook that installs the nginx<\/strong> and redis-server<\/strong> packages.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ chef generate cookbook cookbooks\/multi_pkgs
\nCompiling Cookbooks...
\nRecipe: code_generator::cookbook
\n* directory[\/home\/ubuntu\/chef-repo\/cookbooks\/multi_pkgs] action create
\n- create new directory \/home\/ubuntu\/chef-repo\/cookbooks\/multi_pkgs
\n:
\n(diff output suppressed by config)
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ vi cookbooks\/multi_pkgs\/recipes\/default.rb
\n#
\n# Cookbook Name:: multi_pkgs
\n# Recipe:: default
\n#
\n# Copyright (c) 2014 The Authors, All Rights Reserved.<\/code><\/p>\n


\n<\/code><\/code><\/code><\/p>\n

package 'nginx'
\npackage 'redis-server'
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife node run_list add node.example.jp 'recipe[multi_pkgs]'
\nnode.example.jp:
\nrun_list:
\nrecipe[ntp]
\nrecipe[multi_pkgs]
\nubuntu@ws:~\/chef-repo$ knife node run_list add ws.example.jp 'recipe[multi_pkgs]'
\nws.example.jp:
\nrun_list:
\nrecipe[ntp]
\nrecipe[multi_pkgs]
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero chef_client 'name:*' -x ubuntu --sudo
\nnode.example.jp [2014-12-22T16:23:51+09:00] WARN:
\n:
\nnode.example.jp Starting Chef Client, version 11.16.4
\nnode.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\"]
\nnode.example.jp Synchronizing Cookbooks:
\nnode.example.jp - ntp
\nnode.example.jp - multi_pkgs
\nnode.example.jp Compiling Cookbooks...
\nnode.example.jp Converging 3 resources
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * package[ntp] action install (up to date)
\nnode.example.jp Recipe: multi_pkgs::default
\nnode.example.jp * package[nginx] action install
\nnode.example.jp - install version 1.1.19-1ubuntu0.6 of package nginx
\nnode.example.jp * package[redis-server] action install
\nnode.example.jp - install version 2:2.2.12-1build1 of package redis-server
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 2\/3 resources updated in 14.823459658 seconds
\nws.example.jp [2014-12-22T16:24:07+09:00] WARN:
\n:
\nws.example.jp Starting Chef Client, version 11.18.0.rc.1
\nws.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\"]
\nws.example.jp Synchronizing Cookbooks:
\nws.example.jp - ntp
\nws.example.jp - multi_pkgs
\nws.example.jp Compiling Cookbooks...
\nws.example.jp Converging 3 resources
\nws.example.jp Recipe: ntp::default
\nws.example.jp * package[ntp] action install (up to date)
\nws.example.jp Recipe: multi_pkgs::default
\nws.example.jp * package[nginx] action install
\nws.example.jp - install version 1.1.19-1ubuntu0.6 of package nginx
\nws.example.jp * package[redis-server] action install
\nws.example.jp - install version 2:2.2.12-1build1 of package redis-server
\nws.example.jp
\nws.example.jp Running handlers:
\nws.example.jp Running handlers complete
\nws.example.jp Chef Client finished, 2\/3 resources updated in 15.721211671 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Installation has been completed. Uninstall the packages for now.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife ssh 'name:*' 'sudo apt-get purge -y nginx redis-server' -x ubuntu
\nReading package lists... Done
\nBuilding dependency tree
\nReading state information... Done
\nws.example.jp The following packages were automatically installed and are no longer required:
\nws.example.jp libjpeg-turbo8 libjpeg8 libxslt1.1 nginx-full nginx-common libgd2-noxpm
\nws.example.jp Use 'apt-get autoremove' to remove them.
\nws.example.jp The following packages will be REMOVED:
\nws.example.jp nginx* redis-server*
\nws.example.jp 0 upgraded, 0 newly installed, 2 to remove and 1 not upgraded.
\nws.example.jp After this operation, 610 kB disk space will be freed.
\n(Reading database ... 100734 files and directories currently installed.)
\nws.example.jp Removing nginx ...
\nws.example.jp Removing redis-server ...
\nws.example.jp Stopping redis-server: redis-server.
\nws.example.jp Purging configuration files for redis-server ...
\nws.example.jp dpkg: warning: while removing redis-server, directory '\/var\/log\/redis' not empty so not removed.
\nws.example.jp Processing triggers for man-db ...
\nws.example.jp Processing triggers for ureadahead ...
\nReading package lists... Done
\nBuilding dependency tree
\nReading state information... Done
\nnode.example.jp The following packages were automatically installed and are no longer required:
\nnode.example.jp libjpeg-turbo8 libjpeg8 libxslt1.1 nginx-full nginx-common libgd2-noxpm
\nnode.example.jp Use 'apt-get autoremove' to remove them.
\nnode.example.jp The following packages will be REMOVED:
\nnode.example.jp nginx* redis-server*
\nnode.example.jp 0 upgraded, 0 newly installed, 2 to remove and 1 not upgraded.
\nnode.example.jp After this operation, 610 kB disk space will be freed.
\n(Reading database ... 61316 files and directories currently installed.)
\nnode.example.jp Removing nginx ...
\nnode.example.jp Removing redis-server ...
\nnode.example.jp Stopping redis-server: redis-server.
\nnode.example.jp Purging configuration files for redis-server ...
\nnode.example.jp dpkg: warning: while removing redis-server, directory '\/var\/log\/redis' not empty so not removed.
\nnode.example.jp Processing triggers for man-db ...
\nnode.example.jp Processing triggers for ureadahead ...
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Rewrite the recipe by using loop.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ vi cookbooks\/multi_pkgs\/recipes\/default.rb
\n#
\n# Cookbook Name:: multi_pkgs
\n# Recipe:: default
\n#
\n# Copyright (c) 2014 The Authors, All Rights Reserved.<\/code><\/p>\n


\n<\/code><\/code><\/code><\/p>\n

%w{ nginx redis-server }.each do |pkg|
\npackage pkg
\nend
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero chef_client 'name:*' -x ubuntu --sudo
\nnode.example.jp [2014-12-22T16:28:00+09:00] WARN:
\n:
\nnode.example.jp Starting Chef Client, version 11.16.4
\nnode.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\"]
\nnode.example.jp Synchronizing Cookbooks:
\nnode.example.jp - ntp
\nnode.example.jp - multi_pkgs
\nnode.example.jp Compiling Cookbooks...
\nnode.example.jp Converging 3 resources
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * package[ntp] action install (up to date)
\nnode.example.jp Recipe: multi_pkgs::default
\nnode.example.jp * package[nginx] action install
\nnode.example.jp - install version 1.1.19-1ubuntu0.6 of package nginx
\nnode.example.jp * package[redis-server] action install
\nnode.example.jp - install version 2:2.2.12-1build1 of package redis-server
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 2\/3 resources updated in 6.903009063 seconds
\nws.example.jp [2014-12-22T16:28:08+09:00] WARN:
\n:
\nws.example.jp Starting Chef Client, version 11.18.0.rc.1
\nws.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\"]
\nws.example.jp Synchronizing Cookbooks:
\nws.example.jp - ntp
\nws.example.jp - multi_pkgs
\nws.example.jp Compiling Cookbooks...
\nws.example.jp Converging 3 resources
\nws.example.jp Recipe: ntp::default
\nws.example.jp * package[ntp] action install (up to date)
\nws.example.jp Recipe: multi_pkgs::default
\nws.example.jp * package[nginx] action install
\nws.example.jp - install version 1.1.19-1ubuntu0.6 of package nginx
\nws.example.jp * package[redis-server] action install
\nws.example.jp - install version 2:2.2.12-1build1 of package redis-server
\nws.example.jp
\nws.example.jp Running handlers:
\nws.example.jp Running handlers complete
\nws.example.jp Chef Client finished, 2\/3 resources updated in 7.603140636 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Installation has been completed in the same way as multiple package<\/strong>s are used. Note that the number of resources<\/strong> has not been changed. This means that there are various ways to write a recipe to get the same result.<\/p>\n

<\/code><\/code><\/p>\n

\u25cfUsing a template<\/a><\/h3>\n

<\/code><\/code><\/p>\n

With Chef, it is possible to use a Template<\/a> that uses ERB<\/a> for the engine.
\nCreate a cookbook that embeds the values acquired from variables (Hello, World!<\/strong>) into a template (tmpl.hello.erb<\/strong>), and outputs as a file (\/tmp\/hello.txt<\/strong>).
\nStart with a cookbook, which is a collection of data. Name the cookbook as \"tmpl<\/strong>\" cookbook.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ chef generate cookbook cookbooks\/tmpl
\nCompiling Cookbooks...
\nRecipe: code_generator::cookbook
\n* directory[\/home\/ubuntu\/chef-repo\/cookbooks\/tmpl] action create
\n- create new directory \/home\/ubuntu\/chef-repo\/cookbooks\/tmpl
\n:
\n(diff output suppressed by config)
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

This is an Attribute<\/a> file that describes a variable. Name this file as default<\/strong> attribute since it will contain the default value.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ chef generate attribute cookbooks\/tmpl default
\nCompiling Cookbooks...
\nRecipe: code_generator::attribute
\n* directory[cookbooks\/tmpl\/attributes] action create
\n- create new directory cookbooks\/tmpl\/attributes
\n* template[cookbooks\/tmpl\/attributes\/default.rb] action create
\n- create new file cookbooks\/tmpl\/attributes\/default.rb
\n- update content in file cookbooks\/tmpl\/attributes\/default.rb from none to e3b0c4
\n(diff output suppressed by config)
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

This is the template file. As mentioned in the previous step, the file name is \"tmpl.hello.erb<\/strong>\".<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ chef generate template cookbooks\/tmpl tmpl.hello.erb
\nCompiling Cookbooks...
\nRecipe: code_generator::template
\n* directory[cookbooks\/tmpl\/templates\/default] action create
\n- create new directory cookbooks\/tmpl\/templates\/default
\n* template[cookbooks\/tmpl\/templates\/default\/tmpl.hello.erb] action create
\n- create new file cookbooks\/tmpl\/templates\/default\/tmpl.hello.erb
\n- update content in file cookbooks\/tmpl\/templates\/default\/tmpl.hello.erb from none to e3b0c4
\n(diff output suppressed by config)
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

A base structure of the tmpl cookbook has been prepared now.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ tree cookbooks\/tmpl\/
\ncookbooks\/tmpl\/
\n\u251c\u2500\u2500 Berksfile
\n\u251c\u2500\u2500 README.md
\n\u251c\u2500\u2500 attributes
\n\u2502 \u2514\u2500\u2500 default.rb
\n\u251c\u2500\u2500 chefignore
\n\u251c\u2500\u2500 metadata.rb
\n\u251c\u2500\u2500 recipes
\n\u2502 \u2514\u2500\u2500 default.rb
\n\u2514\u2500\u2500 templates
\n\u2514\u2500\u2500 default
\n\u2514\u2500\u2500 tmpl.hello.erb<\/code><\/p>\n


\n<\/code><\/code><\/code><\/p>\n

4 directories, 7 files
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Let's create a cookbook using structure as a base.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ vi cookbooks\/tmpl\/attributes\/default.rb
\ndefault['tmpl']['message'] = 'Hello, World!'
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ vi cookbooks\/tmpl\/templates\/default\/tmpl.hello.erb
\n\"<%= node['tmpl']['message'] %>\"
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ vi cookbooks\/tmpl\/recipes\/default.rb
\n#
\n# Cookbook Name:: tmpl
\n# Recipe:: default
\n#
\n# Copyright (c) 2014 The Authors, All Rights Reserved.<\/code><\/p>\n


\n<\/code><\/code><\/code><\/p>\n

template '\/tmp\/hello.txt' do
\nsource 'tmpl.hello.erb'
\nend
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Apply the template parameter to the node.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife node run_list add node.example.jp 'recipe[tmpl]'
\nnode.example.jp:
\nrun_list:
\nrecipe[ntp]
\nrecipe[multi_pkgs]
\nrecipe[tmpl]
\nubuntu@ws:~\/chef-repo$ knife node run_list add ws.example.jp 'recipe[tmpl]'
\nws.example.jp:
\nrun_list:
\nrecipe[ntp]
\nrecipe[multi_pkgs]
\nrecipe[tmpl]
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero chef_client 'name:*' -x ubuntu --sudo
\nnode.example.jp [2014-12-22T17:25:29+09:00] WARN:
\n:
\nnode.example.jp Starting Chef Client, version 11.16.4
\nnode.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\", \"tmpl\"]
\nnode.example.jp Synchronizing Cookbooks:
\nnode.example.jp - multi_pkgs
\nnode.example.jp - ntp
\nnode.example.jp - tmpl
\nnode.example.jp Compiling Cookbooks...
\nnode.example.jp Converging 4 resources
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * package[ntp] action install (up to date)
\nnode.example.jp Recipe: multi_pkgs::default
\nnode.example.jp * package[nginx] action install (up to date)
\nnode.example.jp * package[redis-server] action install (up to date)
\nnode.example.jp Recipe: tmpl::default
\nnode.example.jp * template[\/tmp\/hello.txt] action create
\nnode.example.jp - create new file \/tmp\/hello.txt
\nnode.example.jp - update content in file \/tmp\/hello.txt from none to 3d06fb
\nnode.example.jp --- \/tmp\/hello.txt 2014-12-22 17:25:30.600670333 +0900
\nnode.example.jp +++ \/tmp\/chef-rendered-template20141222-9137-1tt4lvn 2014-12-22 17:25:30.600670333 +0900
\nnode.example.jp @@ -1 +1,2 @@
\nnode.example.jp +\"Hello, World!\"
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 1\/4 resources updated in 1.531860219 seconds
\nws.example.jp [2014-12-22T17:25:31+09:00] WARN:
\n:
\nws.example.jp Starting Chef Client, version 11.18.0.rc.1
\nws.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\", \"tmpl\"]
\nws.example.jp Synchronizing Cookbooks:
\nws.example.jp - ntp
\nws.example.jp - multi_pkgs
\nws.example.jp - tmpl
\nws.example.jp Compiling Cookbooks...
\nws.example.jp Converging 4 resources
\nws.example.jp Recipe: ntp::default
\nws.example.jp * package[ntp] action install (up to date)
\nws.example.jp Recipe: multi_pkgs::default
\nws.example.jp * package[nginx] action install (up to date)
\nws.example.jp * package[redis-server] action install (up to date)
\nws.example.jp Recipe: tmpl::default
\nws.example.jp * template[\/tmp\/hello.txt] action create
\nws.example.jp - create new file \/tmp\/hello.txt
\nws.example.jp - update content in file \/tmp\/hello.txt from none to 3d06fb
\nws.example.jp --- \/tmp\/hello.txt 2014-12-22 17:25:33.028000026 +0900
\nws.example.jp +++ \/tmp\/chef-rendered-template20141222-9405-1e5lqms 2014-12-22 17:25:33.028000026 +0900
\nws.example.jp @@ -1 +1,2 @@
\nws.example.jp +\"Hello, World!\"
\nws.example.jp
\nws.example.jp Running handlers:
\nws.example.jp Running handlers complete
\nws.example.jp Chef Client finished, 1\/4 resources updated in 1.301652536 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Make sure that the file has been created.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife ssh 'name:*' 'cat \/tmp\/hello.txt' -x ubuntu
\nws.example.jp \"Hello, World!\"
\nnode.example.jp \"Hello, World!\"
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

You can also embed the value collected with Ohai<\/a>. Embed fqdn<\/strong> here.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ git diff cookbooks
\ndiff --git a\/cookbooks\/tmpl\/templates\/default\/tmpl.hello.erb b\/cookbooks\/tmpl\/templates\/default\/tmpl.hello.erb
\nindex 1c1ac75..b8087c4 100644
\n--- a\/cookbooks\/tmpl\/templates\/default\/tmpl.hello.erb
\n+++ b\/cookbooks\/tmpl\/templates\/default\/tmpl.hello.erb
\n@@ -1 +1 @@
\n-\"<%= node['tmpl']['message'] %>\"
\n+<%= node['fqdn'] %> says \"<%= node['tmpl']['message'] %>\"
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Apply the fqdn parameter to the node.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero chef_client 'name:*' -x ubuntu --sudo
\nnode.example.jp [2014-12-22T17:29:34+09:00] WARN:
\n:
\nnode.example.jp Starting Chef Client, version 11.16.4
\nnode.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\", \"tmpl\"]
\nnode.example.jp Synchronizing Cookbooks:
\nnode.example.jp - multi_pkgs
\nnode.example.jp - tmpl
\nnode.example.jp - ntp
\nnode.example.jp Compiling Cookbooks...
\nnode.example.jp Converging 4 resources
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * package[ntp] action install (up to date)
\nnode.example.jp Recipe: multi_pkgs::default
\nnode.example.jp * package[nginx] action install (up to date)
\nnode.example.jp * package[redis-server] action install (up to date)
\nnode.example.jp Recipe: tmpl::default
\nnode.example.jp * template[\/tmp\/hello.txt] action create
\nnode.example.jp - update content in file \/tmp\/hello.txt from 3d06fb to f3a09e
\nnode.example.jp --- \/tmp\/hello.txt 2014-12-22 17:25:30.600670333 +0900
\nnode.example.jp +++ \/tmp\/chef-rendered-template20141222-9637-g2wd8o 2014-12-22 17:29:35.516354291 +0900
\nnode.example.jp @@ -1,2 +1,2 @@
\nnode.example.jp -\"Hello, World!\"
\nnode.example.jp +node.example.jp says \"Hello, World!\"
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 1\/4 resources updated in 1.291272443 seconds
\nws.example.jp [2014-12-22T17:29:36+09:00] WARN:
\n:
\nws.example.jp Starting Chef Client, version 11.18.0.rc.1
\nws.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\", \"tmpl\"]
\nws.example.jp Synchronizing Cookbooks:
\nws.example.jp - ntp
\nws.example.jp - multi_pkgs
\nws.example.jp - tmpl
\nws.example.jp Compiling Cookbooks...
\nws.example.jp Converging 4 resources
\nws.example.jp Recipe: ntp::default
\nws.example.jp * package[ntp] action install (up to date)
\nws.example.jp Recipe: multi_pkgs::default
\nws.example.jp * package[nginx] action install (up to date)
\nws.example.jp * package[redis-server] action install (up to date)
\nws.example.jp Recipe: tmpl::default
\nws.example.jp * template[\/tmp\/hello.txt] action create
\nws.example.jp - update content in file \/tmp\/hello.txt from 3d06fb to 053da1
\nws.example.jp --- \/tmp\/hello.txt 2014-12-22 17:25:33.028000026 +0900
\nws.example.jp +++ \/tmp\/chef-rendered-template20141222-10088-1kk0bd5 2014-12-22 17:29:37.982553342 +0900
\nws.example.jp @@ -1,2 +1,2 @@
\nws.example.jp -\"Hello, World!\"
\nws.example.jp +ws.example.jp says \"Hello, World!\"
\nws.example.jp
\nws.example.jp Running handlers:
\nws.example.jp Running handlers complete
\nws.example.jp Chef Client finished, 1\/4 resources updated in 1.348914275 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Make sure that the file has been changed.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife ssh 'name:*' 'cat \/tmp\/hello.txt' -x ubuntu
\nws.example.jp ws.example.jp says \"Hello, World!\"
\nnode.example.jp node.example.jp says \"Hello, World!\"
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

\u25cfCommunication between resources<\/a><\/h3>\n

<\/code><\/code><\/p>\n

By using notifies or subscribes<\/a>, service can be restarted as soon as the config file is changed.
\nCreate a cookbook, which installs an nginx<\/strong> package, and places the config file (\/etc\/nginx\/sites-available\/default<\/strong>) that can only change the listen port number (listen_port<\/strong>).
\nFirstly, create a base structure of nginx<\/strong> cookbook.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ chef generate cookbook cookbooks\/nginx
\nCompiling Cookbooks...
\nRecipe: code_generator::cookbook
\n* directory[\/home\/ubuntu\/chef-repo\/cookbooks\/nginx] action create
\n- create new directory \/home\/ubuntu\/chef-repo\/cookbooks\/nginx
\n:
\nubuntu@ws:~\/chef-repo$ chef generate attribute cookbooks\/nginx default
\nCompiling Cookbooks...
\nRecipe: code_generator::attribute
\n* directory[cookbooks\/nginx\/attributes] action create
\n- create new directory cookbooks\/nginx\/attributes
\n* template[cookbooks\/nginx\/attributes\/default.rb] action create
\n- create new file cookbooks\/nginx\/attributes\/default.rb
\n- update content in file cookbooks\/nginx\/attributes\/default.rb from none to e3b0c4
\n(diff output suppressed by config)
\nubuntu@ws:~\/chef-repo$ chef generate template cookbooks\/nginx nginx.default.erb
\nCompiling Cookbooks...
\nRecipe: code_generator::template
\n* directory[cookbooks\/nginx\/templates\/default] action create
\n- create new directory cookbooks\/nginx\/templates\/default
\n* template[cookbooks\/nginx\/templates\/default\/nginx.default.erb] action create
\n- create new file cookbooks\/nginx\/templates\/default\/nginx.default.erb
\n- update content in file cookbooks\/nginx\/templates\/default\/nginx.default.erb from none to e3b0c4
\n(diff output suppressed by config)
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Let's create a cookbook now. We use notifies<\/strong> here. The same thing can be achieved by using subscribes<\/strong>, but we will neither go on to details nor explain the code examples now. Please check them on your own later.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ vi cookbooks\/nginx\/attributes\/default.rb
\ndefault['nginx']['listen_port'] = 80
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ vi cookbooks\/nginx\/templates\/default\/nginx.default.erb
\n#
\n# Generated by Chef for <%= node['fqdn'] %>
\n#<\/code><\/p>\n

<\/code><\/code><\/code><\/p>\n

server {
\nlisten <%= node['nginx']['listen_port'] %> default_server;
\nlisten [::]:<%= node['nginx']['listen_port'] %> default_server ipv6only=on;<\/p>\n

<\/code><\/code><\/code><\/p>\n

root \/usr\/share\/nginx\/html;
\nindex index.html index.htm;<\/p>\n

<\/code><\/code><\/code><\/p>\n

server_name localhost;<\/p>\n


\n<\/code><\/code><\/code><\/p>\n

location \/ {
\ntry_files $uri $uri\/ =404;
\n}
\n}
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ vi cookbooks\/nginx\/recipes\/default.rb
\n#
\n# Cookbook Name:: nginx
\n# Recipe:: default
\n#
\n# Copyright (c) 2014 The Authors, All Rights Reserved.<\/code><\/p>\n

<\/code><\/code><\/code><\/p>\n

package 'nginx'<\/p>\n

<\/code><\/code><\/code><\/p>\n

template '\/etc\/nginx\/sites-available\/default' do
\nsource 'nginx.default.erb'
\nnotifies :restart, 'service[nginx]'
\nend<\/p>\n


\n<\/code><\/code><\/code><\/p>\n

service 'nginx' do
\nsupports :restart => true
\naction :enable
\nend
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Apply the nginx parameter to the node.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife node run_list add node.example.jp 'recipe[nginx]'
\nnode.example.jp:
\nrun_list:
\nrecipe[ntp]
\nrecipe[multi_pkgs]
\nrecipe[tmpl]
\nrecipe[nginx]
\nubuntu@ws:~\/chef-repo$ knife node run_list add ws.example.jp 'recipe[nginx]'
\nws.example.jp:
\nrun_list:
\nrecipe[ntp]
\nrecipe[multi_pkgs]
\nrecipe[tmpl]
\nrecipe[nginx]
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero chef_client 'name:*' -x ubuntu --sudo
\nnode.example.jp [2014-12-22T18:17:40+09:00] WARN:
\n:
\nnode.example.jp Starting Chef Client, version 11.16.4
\nnode.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\", \"tmpl\", \"nginx\"]
\nnode.example.jp Synchronizing Cookbooks:
\nnode.example.jp - tmpl
\nnode.example.jp - ntp
\nnode.example.jp - multi_pkgs
\nnode.example.jp - nginx
\nnode.example.jp Compiling Cookbooks...
\nnode.example.jp [2014-12-22T18:17:41+09:00] WARN: Cloning resource attributes for package[nginx] from prior resource (CHEF-3694)
\nnode.example.jp [2014-12-22T18:17:41+09:00] WARN: Previous package[nginx]: \/var\/chef\/cache\/cookbooks\/multi_pkgs\/recipes\/default.rb:8:in `block in from_file'
\nnode.example.jp [2014-12-22T18:17:41+09:00] WARN: Current package[nginx]: \/var\/chef\/cache\/cookbooks\/nginx\/recipes\/default.rb:7:in `from_file'
\nnode.example.jp Converging 7 resources
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * package[ntp] action install (up to date)
\nnode.example.jp Recipe: multi_pkgs::default
\nnode.example.jp * package[nginx] action install (up to date)
\nnode.example.jp * package[redis-server] action install (up to date)
\nnode.example.jp Recipe: tmpl::default
\nnode.example.jp * template[\/tmp\/hello.txt] action create (up to date)
\nnode.example.jp Recipe: nginx::default
\nnode.example.jp * package[nginx] action install (up to date)
\nnode.example.jp * template[\/etc\/nginx\/sites-available\/default] action create
\nnode.example.jp - update content in file \/etc\/nginx\/sites-available\/default from 7fe53b to 97aa27
\nnode.example.jp --- \/etc\/nginx\/sites-available\/default 2012-03-29 11:50:24.000000000 +0900
\nnode.example.jp +++ \/tmp\/chef-rendered-template20141222-10157-1n5zvby 2014-12-22 18:17:42.116304044 +0900
\nnode.example.jp @@ -1,121 +1,18 @@
\n:
\nnode.example.jp * service[nginx] action enable (up to date)
\nnode.example.jp * service[nginx] action restart
\nnode.example.jp - restart service service[nginx]
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 2\/8 resources updated in 2.850105057 seconds
\nws.example.jp [2014-12-22T18:17:44+09:00] WARN:
\n:
\nws.example.jp Starting Chef Client, version 11.18.0.rc.1
\nws.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\", \"tmpl\", \"nginx\"]
\nws.example.jp Synchronizing Cookbooks:
\nws.example.jp - ntp
\nws.example.jp - tmpl
\nws.example.jp - multi_pkgs
\nws.example.jp - nginx
\nws.example.jp Compiling Cookbooks...
\nws.example.jp [2014-12-22T18:17:45+09:00] WARN: Cloning resource attributes for package[nginx] from prior resource (CHEF-3694)
\nws.example.jp [2014-12-22T18:17:45+09:00] WARN: Previous package[nginx]: \/var\/chef\/cache\/cookbooks\/multi_pkgs\/recipes\/default.rb:8:in `block in from_file'
\nws.example.jp [2014-12-22T18:17:45+09:00] WARN: Current package[nginx]: \/var\/chef\/cache\/cookbooks\/nginx\/recipes\/default.rb:7:in `from_file'
\nws.example.jp Converging 7 resources
\nws.example.jp Recipe: ntp::default
\nws.example.jp * package[ntp] action install (up to date)
\nws.example.jp Recipe: multi_pkgs::default
\nws.example.jp * package[nginx] action install (up to date)
\nws.example.jp * package[redis-server] action install (up to date)
\nws.example.jp Recipe: tmpl::default
\nws.example.jp * template[\/tmp\/hello.txt] action create (up to date)
\nws.example.jp Recipe: nginx::default
\nws.example.jp * package[nginx] action install (up to date)
\nws.example.jp * template[\/etc\/nginx\/sites-available\/default] action create
\nws.example.jp - update content in file \/etc\/nginx\/sites-available\/default from 7fe53b to 223390
\nws.example.jp --- \/etc\/nginx\/sites-available\/default 2012-03-29 11:50:24.000000000 +0900
\nws.example.jp +++ \/tmp\/chef-rendered-template20141222-10819-d944p2 2014-12-22 18:17:45.884371929 +0900
\nws.example.jp @@ -1,121 +1,18 @@
\n:
\nws.example.jp * service[nginx] action enable (up to date)
\nws.example.jp * service[nginx] action restart
\nws.example.jp - restart service service[nginx]
\nws.example.jp
\nws.example.jp Running handlers:
\nws.example.jp Running handlers complete
\nws.example.jp Chef Client finished, 2\/8 resources updated in 2.687193341 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Make sure that you can access to port 80 as specified.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ curl http:\/\/node.example.jp<\/p>\n

<\/code><\/p>\n

<\/code><\/code><\/p>\n

<\/p>\n

<\/code><\/code><\/p>\n

404 Not Found<\/h1>\n

<\/code><\/code><\/p>\n

<\/center><\/code><\/code><\/p>\n

<\/code><\/code><\/code><\/p>\n

\n

<\/code><\/code><\/code><\/p>\n

nginx\/1.1.19<\/center><\/p>\n

ubuntu@ws:~\/chef-repo$
\n<\/code><\/code><\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ curl http:\/\/ws.example.jp<\/p>\n

<\/code><\/p>\n

<\/code><\/code><\/p>\n

<\/p>\n

<\/code><\/code><\/p>\n

404 Not Found<\/h1>\n

<\/code><\/code><\/p>\n

<\/center><\/code><\/code><\/p>\n

<\/code><\/code><\/code><\/p>\n

\n

<\/code><\/code><\/code><\/p>\n

nginx\/1.1.19<\/center><\/p>\n

ubuntu@ws:~\/chef-repo$
\n<\/code><\/code><\/code><\/p>\n

<\/code><\/code><\/p>\n

Change the port number to 8080<\/strong>. You can change the attribute of the cookbook instead, but we will edit the node information stored in Chef-Repo here.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife node edit node.example.jp
\n{
\n\"name\": \"node.example.jp\",
\n\"chef_environment\": \"_default\",
\n\"normal\": {
\n\"nginx\": {
\n\"listen_port\": 8080
\n},
\n\"tags\": [<\/code><\/p>\n

<\/code><\/code><\/code><\/p>\n

]
\n},
\n\"run_list\": [
\n\"recipe[ntp]\",
\n\"recipe[multi_pkgs]\",
\n\"recipe[tmpl]\",
\n\"recipe[nginx]\"
\n]<\/p>\n


\n<\/code><\/code><\/code><\/p>\n

}
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife node edit ws.example.jp
\n{
\n\"name\": \"ws.example.jp\",
\n\"chef_environment\": \"_default\",
\n\"normal\": {
\n\"nginx\": {
\n\"listen_port\": 8080
\n},
\n\"tags\": [<\/code><\/p>\n

<\/code><\/code><\/code><\/p>\n

]
\n},
\n\"run_list\": [
\n\"recipe[ntp]\",
\n\"recipe[multi_pkgs]\",
\n\"recipe[tmpl]\",
\n\"recipe[nginx]\"
\n]<\/p>\n


\n<\/code><\/code><\/code><\/p>\n

}
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ git diff
\ndiff --git a\/nodes\/node.example.jp.json b\/nodes\/node.example.jp.json
\nindex c4c6fb5..09e752e 100644
\n--- a\/nodes\/node.example.jp.json
\n+++ b\/nodes\/node.example.jp.json
\n@@ -1,6 +1,9 @@
\n{
\n\"name\": \"node.example.jp\",
\n\"normal\": {
\n+ \"nginx\": {
\n+ \"listen_port\": 8080
\n+ },
\n\"tags\": [<\/code><\/p>\n

<\/code><\/code><\/code><\/p>\n

]
\ndiff --git a\/nodes\/ws.example.jp.json b\/nodes\/ws.example.jp.json
\nindex 9043d68..76bf9b4 100644
\n--- a\/nodes\/ws.example.jp.json
\n+++ b\/nodes\/ws.example.jp.json
\n@@ -1,6 +1,9 @@
\n{
\n\"name\": \"ws.example.jp\",
\n\"normal\": {
\n+ \"nginx\": {
\n+ \"listen_port\": 8080
\n+ },
\n\"tags\": [<\/p>\n


\n<\/code><\/code><\/code><\/p>\n

]
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Apply the changed node information to the node.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero chef_client 'name:*' -x ubuntu --sudo -C 1
\nnode.example.jp [2014-12-22T18:26:40+09:00] WARN:
\n:
\nnode.example.jp Starting Chef Client, version 11.16.4
\nnode.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\", \"tmpl\", \"nginx\"]
\nnode.example.jp Synchronizing Cookbooks:
\nnode.example.jp - multi_pkgs
\nnode.example.jp - tmpl
\nnode.example.jp - ntp
\nnode.example.jp - nginx
\nnode.example.jp Compiling Cookbooks...
\nnode.example.jp [2014-12-22T18:26:41+09:00] WARN: Cloning resource attributes for package[nginx] from prior resource (CHEF-3694)
\nnode.example.jp [2014-12-22T18:26:41+09:00] WARN: Previous package[nginx]: \/var\/chef\/cache\/cookbooks\/multi_pkgs\/recipes\/default.rb:8:in `block in from_file'
\nnode.example.jp [2014-12-22T18:26:41+09:00] WARN: Current package[nginx]: \/var\/chef\/cache\/cookbooks\/nginx\/recipes\/default.rb:7:in `from_file'
\nnode.example.jp Converging 7 resources
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * package[ntp] action install (up to date)
\nnode.example.jp Recipe: multi_pkgs::default
\nnode.example.jp * package[nginx] action install (up to date)
\nnode.example.jp * package[redis-server] action install (up to date)
\nnode.example.jp Recipe: tmpl::default
\nnode.example.jp * template[\/tmp\/hello.txt] action create (up to date)
\nnode.example.jp Recipe: nginx::default
\nnode.example.jp * package[nginx] action install (up to date)
\nnode.example.jp * template[\/etc\/nginx\/sites-available\/default] action create
\nnode.example.jp - update content in file \/etc\/nginx\/sites-available\/default from 97aa27 to 3960f9
\nnode.example.jp --- \/etc\/nginx\/sites-available\/default 2014-12-22 18:17:42.116304044 +0900
\nnode.example.jp +++ \/tmp\/chef-rendered-template20141222-10563-2yu0aq 2014-12-22 18:26:41.266762936 +0900
\nnode.example.jp @@ -3,8 +3,8 @@
\nnode.example.jp #
\nnode.example.jp
\nnode.example.jp server {
\nnode.example.jp - listen 80 default_server;
\nnode.example.jp - listen [::]:80 default_server ipv6only=on;
\nnode.example.jp + listen 8080 default_server;
\nnode.example.jp + listen [::]:8080 default_server ipv6only=on;
\nnode.example.jp
\nnode.example.jp root \/usr\/share\/nginx\/html;
\nnode.example.jp index index.html index.htm;
\nnode.example.jp * service[nginx] action enable (up to date)
\nnode.example.jp * service[nginx] action restart
\nnode.example.jp - restart service service[nginx]
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 2\/8 resources updated in 2.28401369 seconds
\nws.example.jp [2014-12-22T18:26:43+09:00] WARN:
\n:
\nws.example.jp Starting Chef Client, version 11.18.0.rc.1
\nws.example.jp resolving cookbooks for run list: [\"ntp\", \"multi_pkgs\", \"tmpl\", \"nginx\"]
\nws.example.jp Synchronizing Cookbooks:
\nws.example.jp - ntp
\nws.example.jp - nginx
\nws.example.jp - multi_pkgs
\nws.example.jp - tmpl
\nws.example.jp Compiling Cookbooks...
\nws.example.jp [2014-12-22T18:26:44+09:00] WARN: Cloning resource attributes for package[nginx] from prior resource (CHEF-3694)
\nws.example.jp [2014-12-22T18:26:44+09:00] WARN: Previous package[nginx]: \/var\/chef\/cache\/cookbooks\/multi_pkgs\/recipes\/default.rb:8:in `block in from_file'
\nws.example.jp [2014-12-22T18:26:44+09:00] WARN: Current package[nginx]: \/var\/chef\/cache\/cookbooks\/nginx\/recipes\/default.rb:7:in `from_file'
\nws.example.jp Converging 7 resources
\nws.example.jp Recipe: ntp::default
\nws.example.jp * package[ntp] action install (up to date)
\nws.example.jp Recipe: multi_pkgs::default
\nws.example.jp * package[nginx] action install (up to date)
\nws.example.jp * package[redis-server] action install (up to date)
\nws.example.jp Recipe: tmpl::default
\nws.example.jp * template[\/tmp\/hello.txt] action create (up to date)
\nws.example.jp Recipe: nginx::default
\nws.example.jp * package[nginx] action install (up to date)
\nws.example.jp * template[\/etc\/nginx\/sites-available\/default] action create
\nws.example.jp - update content in file \/etc\/nginx\/sites-available\/default from 223390 to f0e3c4
\nws.example.jp --- \/etc\/nginx\/sites-available\/default 2014-12-22 18:17:45.884371929 +0900
\nws.example.jp +++ \/tmp\/chef-rendered-template20141222-11323-n203be 2014-12-22 18:26:44.702071618 +0900
\nws.example.jp @@ -3,8 +3,8 @@
\nws.example.jp #
\nws.example.jp
\nws.example.jp server {
\nws.example.jp - listen 80 default_server;
\nws.example.jp - listen [::]:80 default_server ipv6only=on;
\nws.example.jp + listen 8080 default_server;
\nws.example.jp + listen [::]:8080 default_server ipv6only=on;
\nws.example.jp
\nws.example.jp root \/usr\/share\/nginx\/html;
\nws.example.jp index index.html index.htm;
\nws.example.jp * service[nginx] action enable (up to date)
\nws.example.jp * service[nginx] action restart
\nws.example.jp - restart service service[nginx]
\nws.example.jp
\nws.example.jp Running handlers:
\nws.example.jp Running handlers complete
\nws.example.jp Chef Client finished, 2\/8 resources updated in 2.440957849 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

<\/code><\/code><\/p>\n

Now that the config file has been changed and nginx has been restarted. Make sure that you can access to port 8080 as specified.<\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ curl http:\/\/node.example.jp
\ncurl: (7) couldn't connect to host
\nubuntu@ws:~\/chef-repo$ curl http:\/\/node.example.jp:8080<\/p>\n

<\/code><\/p>\n

<\/code><\/code><\/p>\n

<\/p>\n

<\/code><\/code><\/p>\n

404 Not Found<\/h1>\n

<\/code><\/code><\/p>\n

<\/center><\/code><\/code><\/p>\n

<\/code><\/code><\/code><\/p>\n

\n

<\/code><\/code><\/code><\/p>\n

nginx\/1.1.19<\/center><\/p>\n

ubuntu@ws:~\/chef-repo$
\n<\/code><\/code><\/code><\/p>\n

<\/code><\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ curl http:\/\/ws.example.jp
\ncurl: (7) couldn't connect to host
\nubuntu@ws:~\/chef-repo$ curl http:\/\/ws.example.jp:8080<\/p>\n

<\/code><\/p>\n

<\/code><\/code><\/p>\n

<\/p>\n

<\/code><\/code><\/p>\n

404 Not Found<\/h1>\n

<\/code><\/code><\/p>\n

<\/center><\/code><\/code><\/p>\n

<\/code><\/code><\/code><\/p>\n

\n

<\/code><\/code><\/code><\/p>\n

nginx\/1.1.19<\/center><\/p>\n

ubuntu@ws:~\/chef-repo$
\n<\/code><\/code><\/code><\/p>\n

<\/code><\/code><\/p>\n

\u25a0Summary<\/a><\/h2>\n

<\/code><\/code><\/p>\n

Knife-Zero is a very helpful tool that easily enables practicing Infrastructure as Code through the use of Chef without using Chef Server. One of the advantages of using Knife-Zero is that migration to Chef Server is easy when the number of nodes scales out while retaining the usability that is equivalent to Chef Server.
\nFor those who want to try practicing Infrastructure as Code, but think that Chef Server is too much to handle, we recommend using Knife-Zero first. We tried to describe this document as easily as possible for a better understanding of Knife-Zero. We hope you will experience the convenience of Knife-Zero.<\/p>\n

<\/code><\/code><\/p>\n

\n

<\/code><\/code><\/p>\n