{"id":8323,"date":"2015-04-10T16:00:50","date_gmt":"2015-04-10T07:00:50","guid":{"rendered":"http:\/\/www.creationline.com\/?p=8323"},"modified":"2023-08-29T14:01:29","modified_gmt":"2023-08-29T05:01:29","slug":"english-translation-migrating-from-knife-solo-to-knife-zero-getchef","status":"publish","type":"post","link":"https:\/\/www.creationline.com\/tech-blog\/cloudnative\/chef\/8323","title":{"rendered":"[English Translation] Migrating from Knife-Solo to Knife-Zero #getchef"},"content":{"rendered":"

This is the English translation of Knife-Solo\u304b\u3089Knife-Zero\u3078\u306e\u79fb\u884c<\/a> (2014\/11\/14).<\/p>\n

Introduction<\/h2>\n

Last time, we compared Chef-Solo and Chef-Client Local Mode and converged the localhost. This time, we will compare Knife-Solo<\/a> and Knife-Zero<\/a> that are used for managing a remote host.<\/p>\n

As shown in the illustration below, Knife-Solo transfers policies such as Cookbooks and Attributes that are on the local file system to a remote host using ssh+rsync. Then, it logs into the remote host via ssh, executes \u201cChef-Solo\u201d, refers to the policies and converges.<\/p>\n

\"knife-solo\"<\/a><\/p>\n

On the other hand, Knife-Zero starts up Chef-Zero to refer to policies on the localhost or Node Object. Then, logs into a remote host via ssh while setting up the TCP port forwarding, refers to the policies in Chef-Zero and converges.<\/p>\n

\"knife-zero\"<\/a><\/p>\n

Put very simply, Knife-Zero could act like a client-server as if there is a Chef-Server (even when there isn\u2019t one), and converges a remote host by using Chef-Client Local Mode.
\nNow, let\u2019s look at some examples of Knife-Zero.<\/p>\n

Preparations<\/h2>\n

Prepare two Ubuntu 12.04 LTS: One Ubuntu 12.04 LTS with Chef DK 0.3.2 installed \u2013 this will be used as a workstation (ws.example.jp<\/strong>).
\nThe other Ubuntu 12.04 LTS will be used as a remote host (node.example.jp<\/strong>) for converging.<\/p>\n


\nubuntu@ws:~$ sudo dpkg -i chefdk_0.3.2-1_amd64.deb
\n\u4ee5\u524d\u306b\u672a\u9078\u629e\u306e\u30d1\u30c3\u30b1\u30fc\u30b8 chefdk \u3092\u9078\u629e\u3057\u3066\u3044\u307e\u3059\u3002
\n(\u30c7\u30fc\u30bf\u30d9\u30fc\u30b9\u3092\u8aad\u307f\u8fbc\u3093\u3067\u3044\u307e\u3059 ... \u73fe\u5728 49086 \u500b\u306e\u30d5\u30a1\u30a4\u30eb\u3068\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u304c\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3055\u308c\u3066\u3044\u307e\u3059\u3002)
\n(chefdk_0.3.2-1_amd64.deb \u304b\u3089) chefdk \u3092\u5c55\u958b\u3057\u3066\u3044\u307e\u3059...
\nchefdk (0.3.2-1) \u3092\u8a2d\u5b9a\u3057\u3066\u3044\u307e\u3059 ...
\nThank you for installing Chef Development Kit!
\nubuntu@ws:~$
\n<\/code><\/p>\n

On the workstation, generate an SSH key pair without a passphrase and transfer the public key to the remote host in advance.<\/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:
\n2e:51:77:b0:2e:6b:bd:14:a9:a6:cc:ef:65:27:82:53 ubuntu@ws.example.jp
\nThe key's randomart image is:
\n+--[ RSA 2048]----+
\n| . |
\n| o |
\n| . o . |
\n| . o o |
\n| . E + |
\n| = = . |
\n| + B * . |
\n| o * = + |
\n| +oo . |
\n+-----------------+
\nubuntu@ws:~$
\n<\/code><\/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

The login user \u201cubuntu<\/strong>\u201d of the remote host must be set in such a way that \u201csudo<\/strong>\u201d command can be executed without entering a password.<\/p>\n

On the workstation, create a chef-repo directory using \u201cchef generate repo<\/strong>\u201d command. We will use this working directory from now on.<\/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:
\n:
\n(diff output suppressed by config)
\nubuntu@ws:~$ <\/code><\/p>\n

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

ubuntu@ws:~$ tree -a chef-repo
\nchef-repo
\n\u251c\u2500\u2500 .gitignore
\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


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

6 directories, 11 files
\nubuntu@ws:~$
\n<\/code><\/p>\n

Let\u2019s place the chef-repo under the git management. We will not go into the detailed procedures here. Please refer to our previous post about Chef Starter Kit<\/a> (Japanese article) for more information.<\/p>\n

We will use an ntp Cookbook as an example. The message \u201cWARNING: No knife configuration file found\u201d will appear frequently from now on because \u201c.chef\/knife.rb\u201d does not exist. You can ignore the message for now.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife cookbook site install ntp -o cookbooks
\nWARNING: No knife configuration file found
\nInstalling ntp to \/home\/ubuntu\/chef-repo\/cookbooks
\nChecking out the master branch.
\nCreating pristine copy branch chef-vendor-ntp
\nDownloading ntp from the cookbooks site at version 1.6.5 to \/home\/ubuntu\/chef-repo\/cookbooks\/ntp.tar.gz
\nCookbook saved: \/home\/ubuntu\/chef-repo\/cookbooks\/ntp.tar.gz
\nRemoving pre-existing version.
\nUncompressing ntp version 1.6.5.
\nremoving downloaded tarball
\n1 files updated, committing changes
\nCreating tag cookbook-site-imported-ntp-1.6.5
\nChecking out the master branch.
\nUpdating 4878097..b23a1b8
\nFast-forward
\n:
\n:
\n:
\nCookbook ntp version 1.6.5 successfully installed
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Create a Role to be used for setting.<\/p>\n


\nubuntu@ws:~\/chef-repo$ vi roles\/ntp.json
\n{
\n\"json_class\": \"Chef::Role\",
\n\"name\": \"ntp\",
\n\"description\": \"ntp basic\",
\n\"default_attributes\": {
\n\"ntp\": {
\n\"servers\": [
\n\"0.ubuntu.pool.ntp.org\",
\n\"1.ubuntu.pool.ntp.org\",
\n\"2.ubuntu.pool.ntp.org\",
\n\"3.ubuntu.pool.ntp.org\"
\n]
\n}
\n},
\n\"run_list\": [
\n\"recipe[ntp]\"
\n]
\n}
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Knife-Solo<\/h2>\n

Installing Knife-Solo<\/h3>\n

Install Knife-Solo using \u201cchef gem install<\/strong>\u201d command.<\/p>\n


\nubuntu@ws:~\/chef-repo$ chef gem install knife-solo
\nFetching: knife-solo-0.4.2.gem (100%)
\nWARNING: You don't have \/home\/ubuntu\/.chefdk\/gem\/ruby\/2.1.0\/bin in your PATH,
\ngem executables will not run.
\nThanks for installing knife-solo!<\/code><\/p>\n

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

If you run into any issues please let us know at:
\nhttps:\/\/github.com\/matschaffer\/knife-solo\/issues<\/p>\n

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

If you are upgrading knife-solo please uninstall any old versions by
\nrunning `gem clean knife-solo` to avoid any errors.<\/p>\n


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

See http:\/\/bit.ly\/CHEF-3255 for more information on the knife bug
\nthat causes this.
\nSuccessfully installed knife-solo-0.4.2
\nParsing documentation for knife-solo-0.4.2
\nInstalling ri documentation for knife-solo-0.4.2
\nDone installing documentation for knife-solo after 1 seconds
\n1 gem installed
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Installing Chef-Solo to the remote host<\/h3>\n

Use \u201cknife solo prepare<\/strong>\u201d command to install a Chef-Client Omnibus package on the specified host.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife solo prepare node.example.jp
\nWARNING: No knife configuration file found
\nBootstrapping Chef...
\n% Total % Received % Xferd Average Speed Time Time Time Current
\nDload Upload Total Spent Left Speed
\n100 16472 100 16472 0 0 14504 0 0:00:01 0:00:01 --:--:-- 18570
\nDownloading Chef 11.16.0 for ubuntu...
\n:
\n:
\n:
\nchef (11.16.0-1) \u3092\u8a2d\u5b9a\u3057\u3066\u3044\u307e\u3059 ...
\nThank you for installing Chef!
\nGenerating node config '.\/nodes\/node.example.jp.json'...
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

The Chef-Client Omnibus package is installed on the remote host now. At the same time, a JSON file for node setting is generated in the workstation\u2019s nodes\/<\/strong> directory.<\/p>\n


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


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

],
\n\"automatic\": {
\n\"ipaddress\": \"node.example.jp\"
\n}
\n}
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Executing Chef-Solo on the remote host to converge<\/h3>\n

Edit the JSON file for node setting, and add the previously created Role to the run_list.<\/p>\n


\nubuntu@ws:~\/chef-repo$ vi nodes\/node.example.jp.json
\nubuntu@ws:~\/chef-repo$ git diff
\ndiff --git a\/nodes\/node.example.jp.json b\/nodes\/node.example.jp.json
\nindex cf38459..575ca94 100644
\n--- a\/nodes\/node.example.jp.json
\n+++ b\/nodes\/node.example.jp.json
\n@@ -1,6 +1,6 @@
\n{
\n\"run_list\": [
\n-
\n+ \"role[ntp]\"
\n],
\n\"automatic\": {
\n\"ipaddress\": \"node.example.jp\"
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Use \u201cknife solo cook<\/strong>\u201c command to transfer the chef-repo to the specified host, and then execute chef-solo on the specified host.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife solo cook node.example.jp
\nWARNING: No knife configuration file found
\nRunning Chef on node.example.jp...
\nChecking Chef version...
\nUploading the kitchen...
\nGenerating solo config...
\nRunning Chef...
\n:
\n:
\n:
\nStarting Chef Client, version 11.16.0
\nCompiling Cookbooks...
\nConverging 9 resources
\nRecipe: ntp::default
\n* package[ntp] action install
\n- install version 1:4.2.6.p3+dfsg-1ubuntu3.1 of package ntp
\n* package[ntpdate] action install (up to date)
\n* directory[\/var\/lib\/ntp] action create (up to date)
\n* directory[\/var\/log\/ntpstats\/] action create (up to date)
\n* cookbook_file[\/etc\/ntp.leapseconds] action create
\n- create new file \/etc\/ntp.leapseconds
\n- update content in file \/etc\/ntp.leapseconds from none to 274665
\n:
\n:
\n:
\n- change mode from '' to '0644'
\n- change owner from '' to 'root'
\n- change group from '' to 'root'
\nRecipe: ntp::apparmor
\n* service[apparmor] action nothing (skipped due to action :nothing)
\n* cookbook_file[\/etc\/apparmor.d\/usr.sbin.ntpd] action create
\n- update content in file \/etc\/apparmor.d\/usr.sbin.ntpd from a88a6b to fdf13c
\n:
\n:
\n:
\nRecipe: ntp::default
\n* template[\/etc\/ntp.conf] action create
\n- update content in file \/etc\/ntp.conf from 4eb9a0 to 64d24c
\n:
\n:
\n:
\n* service[ntp] action enable (up to date)
\n* service[ntp] action start (up to date)
\nRecipe: ntp::apparmor
\n* service[apparmor] action restart
\n- restart service service[apparmor]
\nRecipe: ntp::default
\n* service[ntp] action restart
\n- restart service service[ntp]<\/code><\/p>\n


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

Running handlers:
\nRunning handlers complete
\nChef Client finished, 6\/11 resources updated in 14.870581634 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Make sure that the specified policy has been applied.<\/p>\n


\nubuntu@ws:~\/chef-repo$ ssh node.example.jp ps auxwwwf | grep '[ n]tp'
\nntp 9914 0.0 0.0 37780 2192 ? Ss 16:52 0:00 \/usr\/sbin\/ntpd -p \/var\/run\/ntpd.pid -g -u 106:113
\nubuntu@ws:~\/chef-repo$ <\/code><\/p>\n


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

ubuntu@ws:~\/chef-repo$ ssh node.example.jp grep pool.ntp.org \/etc\/ntp.conf
\nserver 0.ubuntu.pool.ntp.org iburst
\nrestrict 0.ubuntu.pool.ntp.org nomodify notrap noquery
\nserver 1.ubuntu.pool.ntp.org iburst
\nrestrict 1.ubuntu.pool.ntp.org nomodify notrap noquery
\nserver 2.ubuntu.pool.ntp.org iburst
\nrestrict 2.ubuntu.pool.ntp.org nomodify notrap noquery
\nserver 3.ubuntu.pool.ntp.org iburst
\nrestrict 3.ubuntu.pool.ntp.org nomodify notrap noquery
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Converging is completed successfully.<\/p>\n

Now, let\u2019s look at the files transferred to the remote host.<\/p>\n


\nubuntu@ws:~\/chef-repo$ ssh node.example.jp tree -aF -L 2 chef-solo
\nchef-solo
\n\u251c\u2500\u2500 cookbooks-1\/
\n\u2502 \u2514\u2500\u2500 chef-solo-search\/
\n\u251c\u2500\u2500 cookbooks-2\/
\n\u2502 \u251c\u2500\u2500 README.md
\n\u2502 \u2514\u2500\u2500 ntp\/
\n\u251c\u2500\u2500 data_bags\/
\n\u2502 \u2514\u2500\u2500 README.md
\n\u251c\u2500\u2500 dna.json
\n\u251c\u2500\u2500 environments\/
\n\u2502 \u2514\u2500\u2500 README.md
\n\u251c\u2500\u2500 nodes\/
\n\u2502 \u2514\u2500\u2500 node.example.jp.json
\n\u251c\u2500\u2500 roles\/
\n\u2502 \u251c\u2500\u2500 README.md
\n\u2502 \u2514\u2500\u2500 ntp.json
\n\u2514\u2500\u2500 solo.rb<\/code><\/p>\n


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

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

As you can see, Knife-Solo transfers chef-repo to the remote host with rsync, and executes Chef-Solo on the remote host.
\nIf rsync is not installed on the remote host, transferring of the chef-repo fails.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife solo cook node.example.jp
\nWARNING: No knife configuration file found
\nRunning Chef on node.example.jp...
\nChecking Chef version...
\nUploading the kitchen...
\nbash: rsync: command not found
\nrsync: connection unexpectedly closed (0 bytes received so far) [sender]
\nrsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
\nERROR: RuntimeError: Failed to launch command [\"rsync\", (snip)
\n<\/code><\/p>\n

Knife-Zero<\/h2>\n

Preparations<\/h3>\n

Before applying policy with Knife-Zero, uninstall the ntp package and chef package that have been installed on the remote host. Even if they are remained on the host, they do not have any impact on the operations. However, it is better to uninstall them in advance to check the operations of Knife-Zero clearly.<\/p>\n


\nubuntu@ws:~\/chef-repo$ ssh node.example.jp sudo apt-get purge ntp chef -y
\n\u30d1\u30c3\u30b1\u30fc\u30b8\u30ea\u30b9\u30c8\u3092\u8aad\u307f\u8fbc\u3093\u3067\u3044\u307e\u3059...
\n\u4f9d\u5b58\u95a2\u4fc2\u30c4\u30ea\u30fc\u3092\u4f5c\u6210\u3057\u3066\u3044\u307e\u3059...
\n\u72b6\u614b\u60c5\u5831\u3092\u8aad\u307f\u53d6\u3063\u3066\u3044\u307e\u3059...
\n\u4ee5\u4e0b\u306e\u30d1\u30c3\u30b1\u30fc\u30b8\u304c\u81ea\u52d5\u3067\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3055\u308c\u307e\u3057\u305f\u304c\u3001\u3082\u3046\u5fc5\u8981\u3068\u3055\u308c\u3066\u3044\u307e\u305b\u3093:
\nlibopts25 libcap2
\n\u3053\u308c\u3089\u3092\u524a\u9664\u3059\u308b\u306b\u306f 'apt-get autoremove' \u3092\u5229\u7528\u3057\u3066\u304f\u3060\u3055\u3044\u3002
\n\u4ee5\u4e0b\u306e\u30d1\u30c3\u30b1\u30fc\u30b8\u306f\u300c\u524a\u9664\u300d\u3055\u308c\u307e\u3059:
\nchef* ntp*
\n\u30a2\u30c3\u30d7\u30b0\u30ec\u30fc\u30c9: 0 \u500b\u3001\u65b0\u898f\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb: 0 \u500b\u3001\u524a\u9664: 2 \u500b\u3001\u4fdd\u7559: 6 \u500b\u3002
\n\u3053\u306e\u64cd\u4f5c\u5f8c\u306b 111MB \u306e\u30c7\u30a3\u30b9\u30af\u5bb9\u91cf\u304c\u89e3\u653e\u3055\u308c\u307e\u3059\u3002
\n(\u30c7\u30fc\u30bf\u30d9\u30fc\u30b9\u3092\u8aad\u307f\u8fbc\u3093\u3067\u3044\u307e\u3059 ... \u73fe\u5728 61148 \u500b\u306e\u30d5\u30a1\u30a4\u30eb\u3068\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u304c\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3055\u308c\u3066\u3044\u307e\u3059\u3002)
\nchef \u3092\u524a\u9664\u3057\u3066\u3044\u307e\u3059 ...
\nchef \u306e\u8a2d\u5b9a\u30d5\u30a1\u30a4\u30eb\u3092\u524a\u9664\u3057\u3066\u3044\u307e\u3059 ...
\nntp \u3092\u524a\u9664\u3057\u3066\u3044\u307e\u3059 ...
\n* Stopping NTP server ntpd
\n...done.
\nntp \u306e\u8a2d\u5b9a\u30d5\u30a1\u30a4\u30eb\u3092\u524a\u9664\u3057\u3066\u3044\u307e\u3059 ...
\nman-db \u306e\u30c8\u30ea\u30ac\u3092\u51e6\u7406\u3057\u3066\u3044\u307e\u3059 ...
\nureadahead \u306e\u30c8\u30ea\u30ac\u3092\u51e6\u7406\u3057\u3066\u3044\u307e\u3059 ...
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Delete the JSON file for node setting, which was generated after executing Knife-Solo.<\/p>\n


\nubuntu@ws:~\/chef-repo$ rm nodes\/node.example.jp.json
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Installing Knife-Zero<\/h3>\n

Install Knife-Zero using \u201cchef gem install<\/strong>\u201d command.<\/p>\n


\nubuntu@ws:~\/chef-repo$ chef gem install knife-zero
\nFetching: knife-zero-1.0.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.0.0
\nParsing documentation for knife-zero-1.0.0
\nInstalling ri documentation for knife-zero-1.0.0
\nDone installing documentation for knife-zero after 0 seconds
\n1 gem installed
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Installing Chef-Client to the remote host<\/h3>\n

Use \u201cknife zero bootstrap<\/strong>\u201d command to install a Chef-Client Omnibus package to the specified host. Use \u201c-x<\/strong>\u201c option to specify a login user, and \u201c--sudo<\/strong>\u201d option enables to get a root privilege.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero bootstrap node.example.jp -x ubuntu --sudo
\nWARNING: No knife configuration file found
\nConnecting to node.example.jp
\nnode.example.jp Installing Chef Client...
\n:
\n:
\n:
\nnode.example.jp chef (11.16.4-1) \u3092\u8a2d\u5b9a\u3057\u3066\u3044\u307e\u3059 ...
\nnode.example.jp Thank you for installing Chef!
\nnode.example.jp Starting first Chef Client run...
\n:
\n:
\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-11-11T17:43:21+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.116895026 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

The Chef-Client Omnibus package is now installed to the remote host. At the same time, \u201cNode Object\u201d is generated in the workstation nodes\/<\/strong> directory.<\/p>\n


\nubuntu@ws:~\/chef-repo$ ls -lF nodes\/
\n\u5408\u8a08 32
\n-rw-rw-r-- 1 ubuntu ubuntu 31250 11\u6708 11 17:43 node.example.jp.json
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ view 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:
\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

These objects were generated by the Chef-Zero server, which had been executed on the localhost. Knife-Zero achieves this functionality by linking between the Chef-Zero server executed on the localhost and the Chef-Client executed on the remote host with SSH port forwarding. Unlike Knife-Solo, rsync is not necessary.<\/p>\n

As described in the previous post \u201cMigrating from Chef-Solo to Chef Client Local Mode<\/a>\u201d (Japanese article), these objects can be viewed and operated by executing a knife subcommand with \u201c-z<\/strong> (--local-mode<\/strong>)\u201d option.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife client list -z
\nWARNING: No knife configuration file found
\nnode.example.jp
\nubuntu@ws:~\/chef-repo$ <\/code><\/p>\n


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

ubuntu@ws:~\/chef-repo$ knife node list -z
\nWARNING: No knife configuration file found
\nnode.example.jp
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Executing Chef-Client on the remote host to converge<\/h3>\n

Edit a Role in advance to see the changes in the file set by Knife-Solo.<\/p>\n


\nubuntu@ws:~\/chef-repo$ vi roles\/ntp.json
\nubuntu@ws:~\/chef-repo$ git diff
\ndiff --git a\/roles\/ntp.json b\/roles\/ntp.json
\nindex 045d224..adbc3bc 100644
\n--- a\/roles\/ntp.json
\n+++ b\/roles\/ntp.json
\n@@ -5,10 +5,10 @@
\n\"default_attributes\": {
\n\"ntp\": {
\n\"servers\": [
\n- \"0.ubuntu.pool.ntp.org\",
\n- \"1.ubuntu.pool.ntp.org\",
\n- \"2.ubuntu.pool.ntp.org\",
\n- \"3.ubuntu.pool.ntp.org\"
\n+ \"0.asia.pool.ntp.org\",
\n+ \"1.asia.pool.ntp.org\",
\n+ \"2.asia.pool.ntp.org\",
\n+ \"3.asia.pool.ntp.org\"
\n]
\n}
\n},
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Add a Role to run_list using a knife command (local mode).<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife node run_list add node.example.jp 'role[ntp]' -z
\nWARNING: No knife configuration file found
\nnode.example.jp:
\nrun_list: role[ntp]
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ git diff nodes\/node.exmple.jp.json
\ndiff --git a\/nodes\/node.example.jp.json b\/nodes\/node.example.jp.json
\nindex eb7f9b5..c3f0e8a 100644
\n--- a\/nodes\/node.example.jp.json
\n+++ b\/nodes\/node.example.jp.json
\n@@ -1321,5 +1321,8 @@
\n\"roles\": [<\/code><\/p>\n


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

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

You can also directly edit the JSON file, which is equivalent to Node Object.<\/p>\n

Use \u201cknife zero converge<\/strong>\u201d command to execute Chef-Client on the specified host and converge.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife zero converge 'name:node.example.jp' -x ubuntu --sudo
\nWARNING: No knife configuration file found
\nnode.example.jp [2014-11-11T18:23:06+09:00] WARN:
\n:
\n:
\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 9 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 * package[ntpdate] action install (up to date)
\nnode.example.jp * directory[\/var\/lib\/ntp] action create (up to date)
\nnode.example.jp * directory[\/var\/log\/ntpstats\/] action create (up to date)
\nnode.example.jp * cookbook_file[\/etc\/ntp.leapseconds] action create (up to date)
\nnode.example.jp Recipe: ntp::apparmor
\nnode.example.jp * service[apparmor] action nothing (skipped due to action :nothing)
\nnode.example.jp * cookbook_file[\/etc\/apparmor.d\/usr.sbin.ntpd] action create
\nnode.example.jp - update content in file \/etc\/apparmor.d\/usr.sbin.ntpd from a88a6b to fdf13c
\n:
\n:
\n:
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * template[\/etc\/ntp.conf] action create
\nnode.example.jp - update content in file \/etc\/ntp.conf from 4eb9a0 to 565516
\n:
\n:
\n:
\nnode.example.jp * service[ntp] action enable (up to date)
\nnode.example.jp * service[ntp] action start (up to date)
\nnode.example.jp Recipe: ntp::apparmor
\nnode.example.jp * service[apparmor] action restart
\nnode.example.jp - restart service service[apparmor]
\nnode.example.jp Recipe: ntp::default
\nnode.example.jp * service[ntp] action restart
\nnode.example.jp - restart service service[ntp]
\nnode.example.jp
\nnode.example.jp Running handlers:
\nnode.example.jp Running handlers complete
\nnode.example.jp Chef Client finished, 5\/11 resources updated in 10.573336982 seconds
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Make sure that the specified policy has been applied.<\/p>\n


\nubuntu@ws:~\/chef-repo$ knife ssh 'name:node.example.jp' -z ps auxwwwf | grep '[ n]tp'
\nWARNING: No knife configuration file found
\nnode.example.jp ntp 24654 0.0 0.0 37780 2180 ? Ss 18:23 0:00 \/usr\/sbin\/ntpd -p \/var\/run\/ntpd.pid -g -u 106:113
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n


\nubuntu@ws:~\/chef-repo$ knife ssh 'name:node.example.jp' -z grep pool.ntp.org \/etc\/ntp.conf
\nWARNING: No knife configuration file found
\nnode.example.jp server 0.asia.pool.ntp.org iburst
\nnode.example.jp restrict 0.asia.pool.ntp.org nomodify notrap noquery
\nnode.example.jp server 1.asia.pool.ntp.org iburst
\nnode.example.jp restrict 1.asia.pool.ntp.org nomodify notrap noquery
\nnode.example.jp server 2.asia.pool.ntp.org iburst
\nnode.example.jp restrict 2.asia.pool.ntp.org nomodify notrap noquery
\nnode.example.jp server 3.asia.pool.ntp.org iburst
\nnode.example.jp restrict 3.asia.pool.ntp.org nomodify notrap noquery
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Converging is completed successfully.<\/p>\n

Node Object in chef-repo is also updated.<\/p>\n


\nubuntu@ws:~\/chef-repo$ git diff
\ndiff --git a\/nodes\/node.example.jp.json b\/nodes\/node.example.jp.json
\nindex eb7f9b5..2cdb327 100644
\n--- a\/nodes\/node.example.jp.json
\n+++ b\/nodes\/node.example.jp.json
\n@@ -5,6 +5,42 @@<\/code><\/p>\n


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

]
\n},
\n+ \"default\": {
\n+ \"ntp\": {
\n+ \"servers\": [
\n+ \"0.asia.pool.ntp.org\",
\n+ \"1.asia.pool.ntp.org\",
\n+ \"2.asia.pool.ntp.org\",
\n+ \"3.asia.pool.ntp.org\"
\n+ ],
\n:
\n:
\n:
\n@@ -1316,10 +1365,15 @@
\n}
\n},
\n\"recipes\": [
\n-
\n+ \"ntp\",
\n+ \"ntp::default\",
\n+ \"ntp::apparmor\"
\n],
\n\"roles\": [
\n-
\n+ \"ntp\"
\n]
\n- }
\n+ },
\n+ \"run_list\": [
\n+ \"role[ntp]\"
\n+ ]
\n}
\nubuntu@ws:~\/chef-repo$
\n<\/code><\/p>\n

Summary<\/h2>\n

We have briefly introduced the difference between Knife-Solo and Knife-Zero, and how to migrate and use them. Knife-Zero allows us to use Chef ecosystem without Chef-Server, but through the use of the client-server model recommended by Chef. The migration work to Chef-Server is relatively easy. One of the scenarios you can consider is to start small with Knife-Zero or Hosted Enterprise Chef, and then migrating to Hosted\/On-premises Enterprise Chef as the business grows. We hope that this information would help you utilize Knife-Zero.<\/p>\n

\n

Converging has been completed now on the remote host as if Chef-Server exists. knife zero converge uses Search<\/a> functionality, and it is possible to converge either in serial or parallel for multiple hosts.<\/p>\n