{"id":100,"date":"2015-09-26T21:32:45","date_gmt":"2015-09-26T21:32:45","guid":{"rendered":"http:\/\/cephswift.com\/?page_id=100"},"modified":"2015-09-28T02:00:30","modified_gmt":"2015-09-28T02:00:30","slug":"chef-setup","status":"publish","type":"page","link":"https:\/\/cephswift.com\/index.php\/chef-setup\/","title":{"rendered":"Chef automation setup"},"content":{"rendered":"

Chef server, client, and workstation setup:<\/p>\n

root@chef_server:~# <\/p>\n

# sudo apt-get upgrade # use this command to update software first on ubuntu linux<\/p>\n

Install ruby and verify before Chef Env setup:<\/p>\n

# sudo apt-get install ruby-full
\n# which ruby ## verify if ruby get install
\n# ruby -v
\n# wget https:\/\/opscode-omnibus-packages.s3.amazonaws.com\/ubuntu\/12.04\/x86_64\/chef-server_11.0.8-1.ubuntu.12.04_amd64.deb<\/p>\n

# which ruby
\n \/bin\/ruby<\/p>\n

reset ruby path: ( after the Chef development kit is installed to\/opt\/chefdk\/ on UNIX and Linux systems )<\/p>\n

https:\/\/docs.chef.io\/install_dk.html<\/p>\n

# echo ‘eval “$(chef shell-init bash)”‘ >> ~\/.bash_profile<\/p>\n

# which ruby<\/p>\n

\/opt\/chefdk\/embedded\/bin\/ruby<\/p>\n

Chef server download and install<\/p>\n

# wget https:\/\/opscode-omnibus-packages.s3.amazonaws.com\/ubuntu\/12.04\/x86_64\/chef-server_11.0.8-1.ubuntu.12.04_amd64.deb
\n # sudo dpkg -i chef-server_11.0.8-1.ubuntu.12.04_amd64.deb
\n # sudo chef-server-ctl reconfigure<\/p>\n

# root@chef_server:~# dpkg –list | grep chef ### list chef pkg installed
\n# root@chef_server:~# dpkg -P chef-server chef-zero ### remove chef after install on ubountu linux if you don’t need it any more<\/p>\n

Recipe: chef-server::erchef
\n * service[erchef] action restart
\n – restart service service[erchef]<\/p>\n

Chef Client finished, 270 resources updated
\nchef-server Reconfigured!
\nChef_server running status check:<\/p>\n

# chef-server-ctl status
\nrun: bookshelf: (pid 995) 2262767s; run: log: (pid 993) 2262767s
\nrun: chef-expander: (pid 990) 2262767s; run: log: (pid 989) 2262767s
\nrun: chef-server-webui: (pid 996) 2262767s; run: log: (pid 994) 2262767s
\nrun: chef-solr: (pid 1644) 2262430s; run: log: (pid 987) 2262767s
\nrun: erchef: (pid 998) 2262767s; run: log: (pid 997) 2262767s
\nrun: nginx: (pid 1000) 2262767s; run: log: (pid 999) 2262767s
\nrun: postgresql: (pid 1007) 2262767s; run: log: (pid 1004) 2262767s
\nrun: rabbitmq: (pid 992) 2262767s; run: log: (pid 991) 2262767s<\/p>\n

Chef_Server running Status UI login:<\/p>\n

https:\/\/192.168.1.2\/users\/login ### you may login to web ui, to play with…as you do in command line.<\/p>\n

192.168.1.2 \u2013-> chef_server<\/p>\n

username: admin<\/p>\n

password: p@ssw0rd1 #### change to WHAT YOUR WANT then SAVE to somewhere !!!!!<\/p>\n

Please change the default password immediately after logging in!
\nPublic and Private Key created from chef server admin:
\nClient: chef-validator
\nchef-validator.pub.pem<\/p>\n

—–BEGIN PUBLIC KEY—–
\n—–END PUBLIC KEY—–<\/p>\n

root@chef_server:\/etc\/chef-server# cat chef-validator.pem<\/p>\n

—–BEGIN RSA PRIVATE KEY—–
\n—–END RSA PRIVATE KEY—–<\/p>\n

default admin user and passed:<\/p>\n

login: admin
\npasswd: <\/p>\n

added admin user:
\nlogin:
\npasswd:<\/p>\n

admin key for ADDED USER ### save the key to some where for later use…. <\/p>\n

—–BEGIN PUBLIC KEY—–
\n—–END PUBLIC KEY—–<\/p>\n

—–BEGIN RSA PRIVATE KEY—–
\n—–END RSA PRIVATE KEY—–<\/p>\n

For Chef server:<\/p>\n

admin key:<\/p>\n

—–BEGIN PUBLIC KEY—–
\n—–END PUBLIC KEY\u2014\u2014<\/p>\n

—–BEGIN RSA PRIVATE KEY—–
\n—–END RSA PRIVATE KEY—–<\/p>\n

Remove & uninstall not worked Chef installed:<\/p>\n

[root@chef_server ~]# rpm -qa *chef*
\nchef-server-11.1.5-1.el6.x86_64
\nchef-12.2.0-1.el6.x86_64<\/p>\n

root@chef_server ~]# yum remove *chef* ### this is for Chef clean up on Centos Linux, if chef was instlled with yum….
\n===========================================================================================================================<\/p>\n

root@chef_ws:~# #### you may assign IP as 192.168.1.3 for this host<\/p>\n

Workstation Setup:<\/p>\n

[root@chef_ws]# <\/p>\n

Install ruby as what have been done in chef server, then download and install \u201cchefdk\u201d:<\/p>\n

# sudo dpkg -i chefdk_0.4.0-1_amd64.deb<\/p>\n

root@chef_ws:\/tmp\/chef_pkgs# ls -ltr
\ntotal 328324
\n-rw-r–r– 1 root root 197934506 Apr 23 2013 chef-server_11.0.8-1.ubuntu.12.04_amd64.deb
\n-rw-r—– 1 root root 138265262 Mar 30 17:52 chefdk_0.4.0-1_amd64.deb<\/p>\n

root@chef_ws:\/tmp\/chef_pkgs# sudo dpkg -i chefdk_0.4.0-1_amd64.deb
\nSelecting previously unselected package chefdk.
\n(Reading database … 82743 files and directories currently installed.)
\nPreparing to unpack chefdk_0.4.0-1_amd64.deb …
\nUnpacking chefdk (0.4.0-1) …
\nSetting up chefdk (0.4.0-1) …
\nThank you for installing Chef Development Kit!<\/p>\n

=========================================================================================
\nroot@chef_ws:\/tmp\/chef_pkgs# curl -O -L http:\/\/www.opscode.com\/chef\/install.sh<\/p>\n

root@chef_ws:\/tmp\/chef_pkgs# ls -l
\ntotal 328344
\n-rw-r—– 1 root root 138265262 Mar 30 17:52 chefdk_0.4.0-1_amd64.deb
\n-rw-r–r– 1 root root 197934506 Apr 23 2013 chef-server_11.0.8-1.ubuntu.12.04_amd64.deb
\n-rw-r–r– 1 root root 18373 Mar 31 10:42 install.sh<\/p>\n

root@chef_ws:\/tmp\/chef_pkgs# sudo sh install.sh<\/p>\n

Downloading Chef for ubuntu…
\ndownloading http:\/\/www.opscode.com\/chef\/metadata?v=&prerelease=false&nightlies=false&p=ubuntu&pv=14.04&m=x86_64
\n to file \/tmp\/install.sh.15425\/metadata.txt
\ntrying wget…
\nurl\thttp:\/\/opscode-omnibus-packages.s3.amazonaws.com\/ubuntu\/13.04\/x86_64\/chef_12.2.1-1_amd64.deb
\nmd5\t84119f54115d754373c9891b8759497c
\nsha256\t8e0a8a2477c11615f86ffe686a68fa6636112ba82ebe6bb22daa5dd416f3c13e
\ndownloaded metadata file looks valid…
\ndownloading http:\/\/opscode-omnibus-packages.s3.amazonaws.com\/ubuntu\/13.04\/x86_64\/chef_12.2.1-1_amd64.deb
\n to file \/tmp\/install.sh.15425\/chef_12.2.1-1_amd64.deb
\ntrying wget…
\nComparing checksum with sha256sum…
\nInstalling Chef
\ninstalling with dpkg…
\nSelecting previously unselected package chef.
\n(Reading database … 125291 files and directories currently installed.)
\nPreparing to unpack …\/chef_12.2.1-1_amd64.deb …
\nUnpacking chef (12.2.1-1) …
\nSetting up chef (12.2.1-1) \u2026
\nThank you for installing Chef!<\/p>\n

root@chef_ws:\/tmp\/chef_pkgs# <\/p>\n

==============================================
\nhttp:\/\/thornelabs.net\/2013\/09\/16\/install-the-open-source-chef-server-setup-knife-on-your-workstation-and-bootstrap-your-first-client-server.html<\/p>\n

root@chef_ws:\/tmp\/chef_pkgs# mkdir ~\/Development
\nroot@chef_ws:\/tmp\/chef_pkgs# cd ~\/Development
\nroot@chef_ws:~\/Development# git clone https:\/\/github.com\/opscode\/chef-repo.git
\nCloning into ‘chef-repo’…
\nremote: Counting objects: 250, done.
\nremote: Total 250 (delta 0), reused 0 (delta 0), pack-reused 250
\nReceiving objects: 100% (250\/250), 49.55 KiB | 0 bytes\/s, done.
\nResolving deltas: 100% (70\/70), done.
\nChecking connectivity… done.
\nroot@chef_ws:~\/Development# <\/p>\n

# cd ~\/Development\/chef-repo
\n# mkdir .chef
\n# cd .chef<\/p>\n

root@chef_ws:~\/Development\/chef-repo\/.chef# <\/p>\n

# vi chef-validator.pem
\n# vi chef-client-validator.pub.pem
\n# vi admin.pem
\n# vi admin.pub.pem<\/p>\n

# cd ~\/Development\/chef-repo\/.chef\/<\/p>\n

root@chef_ws:~\/Development\/chef-repo\/.chef\/<\/p>\n

# knife configure<\/p>\n

Overwrite \/root\/Development\/chef-repo\/.chef\/knife.rb? (Y\/N) Y
\nPlease enter the chef server URL: [https:\/\/192.168.1.2:443] https:\/\/192.168.1.2:443
\nPlease enter an existing username or clientname for the API: [root] admin
\nPlease enter the validation clientname: [chef-validator] chef-validator
\nPlease enter the location of the validation key: [\/etc\/chef-server\/chef-validator.pem] ~\/Development\/chef-repo\/.chef\/chef-validator.pem
\nPlease enter the path to a chef repository (or leave blank):
\n*****<\/p>\n

You must place your client key in:
\n \/root\/Development\/chef-repo\/.chef\/admin.pem
\nBefore running commands with Knife!<\/p>\n

*****<\/p>\n

You must place your validation key in:
\n \/root\/Development\/chef-repo\/.chef\/chef-validator.pem
\nBefore generating instance data with Knife!<\/p>\n

*****
\nConfiguration file written to \/root\/Development\/chef-repo\/.chef\/knife.rb<\/p>\n

=========================================================================<\/p>\n

# knife configure
\n# cat chef-validator.pem >> \/root\/Development\/chef-repo\/.chef\/admin.pem
\n# cat \/root\/Development\/chef-repo\/.chef\/chef-validator.pem
\n# cat \/root\/Development\/chef-repo\/.chef\/knife.rb
\n# knife client list
\n# knife ssl check<\/p>\n

# mkdir \/root\/Development\/chef-repo\/.chef\/trusted_certs
\n# cd trusted_certs<\/p>\n

Copy “192.168.1.2.crt\u201d from server to client for SSL communication:<\/p>\n

# scp 192.168.1.2:\/var\/opt\/chef-server\/nginx\/ca\/192.168.1.2.crt \/root\/Development\/chef-repo\/.chef\/trusted_certs\/<\/p>\n

========================================================================<\/p>\n

Test knife from client to server via SSL check:<\/p>\n

root@chef_ws:~\/Development\/chef-repo\/.chef<\/p>\n

# knife ssl check
\nConnecting to host 192.168.1.2:443
\nSuccessfully verified certificates from `192.168.1.2\u2019<\/p>\n

root@chef_ws:~\/Development\/chef-repo\/.chef# <\/p>\n

root@chef_ws:~# cd ~\/Development\/chef-repo\/.chef<\/p>\n

root@chef_ws:~\/Development\/chef-repo\/.chef# ls -l
\ntotal 36
\n-rw-r–r– 1 root root 1675 Mar 31 12:24 admin.pem
\n-rw-r–r– 1 root root 451 Mar 31 12:19 admin.pub.pem
\n-rw-r–r– 1 root root 451 Mar 31 12:35 chef-client-validator.pub.pem
\n-rw-r–r– 1 root root 1675 Mar 31 12:34 chef-validator.pem
\n-rw-r–r– 1 root root 423 Mar 31 15:31 knife.rb
\n-rw-r–r– 1 root root 1675 Mar 31 13:11 root.pem
\ndrwxr-xr-x 2 root root 4096 Mar 31 15:28 trusted_certs
\nroot@chef_ws:~\/Development\/chef-repo\/.chef# <\/p>\n

root@chef_ws:~# chef verify<\/p>\n

Running verification for component ‘berkshelf’<\/p>\n

Running verification for component ‘test-kitchen’<\/p>\n

Running verification for component ‘chef-client’<\/p>\n

Running verification for component ‘chef-dk’<\/p>\n

Running verification for component ‘chefspec’<\/p>\n

Running verification for component ‘rubocop’<\/p>\n

Running verification for component ‘fauxhai’<\/p>\n

Running verification for component ‘knife-spork’<\/p>\n

Running verification for component ‘kitchen-vagrant’<\/p>\n

Running verification for component ‘package installation’<\/p>\n

…..<\/p>\n

———————————————<\/p>\n

Verification of component ‘chef-dk’ succeeded.<\/p>\n

Verification of component ‘rubocop’ succeeded.<\/p>\n

Verification of component ‘knife-spork’ succeeded.<\/p>\n

Verification of component ‘berkshelf’ succeeded.<\/p>\n

Verification of component ‘chef-client’ succeeded.<\/p>\n

Verification of component ‘fauxhai’ succeeded.<\/p>\n

Verification of component ‘test-kitchen’ succeeded.<\/p>\n

Verification of component ‘kitchen-vagrant’ succeeded.<\/p>\n

Verification of component ‘chefspec’ succeeded.<\/p>\n

Verification of component ‘package installation’ succeeded.<\/p>\n

root@chef_ws:~# <\/p>\n

root@chef_ws:~# which ruby
\n\/opt\/chefdk\/embedded\/bin\/ruby
\nRefer online docs:<\/p>\n

http:\/\/thornelabs.net\/2013\/09\/16\/install-the-open-source-chef-server-setup-knife-on-your-workstation-and-bootstrap-your-first-client-server.html<\/p>\n

http:\/\/gettingstartedwithchef.com\/first-steps-with-chef.html<\/p>\n

http:\/\/www.linuxfunda.com\/2014\/02\/04\/how-to-install-and-configure-chef-client\/<\/p>\n

http:\/\/tcotav.github.io\/chefdk_getting_started.html<\/p>\n

http:\/\/docs.chef.io\/client\/install_workstation.html<\/p>\n

Thank you for installing Chef!<\/p>\n

Setup git :<\/p>\n

root@chef_ws:~# which git
\n\/usr\/bin\/git
\nroot@chef_ws:~# git config –global user.name “Benjamin Lu” ###### Please replace my name with yours to create your github account
\nroot@chef_ws:~# git config –global user.email “benlu369@yahoo” ###### Please replace my e-mail with yours to setup your github contact
\nroot@chef_ws:~# <\/p>\n

root@chef_ws:~# which knife
\n\/opt\/chefdk\/bin\/knife<\/p>\n

root@chef_server:~# scp 192.168.1.3:\/root\/Development\/chef-repo\/.chef\/chef-validator.pem \/etc\/chef\/chef-validator<\/p>\n

Install chef_client from chef_work_station on \u201cchef_ws on 192.168.1.3\u201d to chef_server on “192.168.1.2\u201d:<\/p>\n

root@chef_ws:~\/Development\/chef-repo\/.chef#<\/p>\n

# knife bootstrap -u root 192.168.1.4 #### thsi will add your 3rd host as chef_client with IP: 192.168.1.4 to Chef_server on 192.168.1.2 from your chef_ws on 192.168.1.3<\/p>\n

Connecting to 192.168.1.4
\nroot@192.168.1.4’s password:
\n192.168.1.4 Installing Chef Client…
\n…..
\n100%[======================================>] 18,378 –.-K\/s in 0.002s
\n….
\n192.168.1.4o Chef Client finished, 0\/0 resources updated in 1.795916082 seconds<\/p>\n

root@chef_ws:~\/Development\/chef-repo\/.chef<\/p>\n

root@chef_server:\/etc\/chef# chmod 644 client.pem
\nroot@chef_server:\/etc\/chef# ls -ltr
\ntotal 20
\n-rw——- 1 root root 1676 Mar 31 16:03 validation.pem
\ndrwxr-xr-x 2 root root 4096 Mar 31 16:03 trusted_certs
\n-rw-r–r– 1 root root 192 Mar 31 16:03 client.rb
\n-rw-r–r– 1 root root 16 Mar 31 16:03 first-boot.json
\n-rw-r–r– 1 root root 1675 Mar 31 16:03 client.pem<\/p>\n

Test client\/workstation ====> server talk from listing chef_client created on chef_server:<\/p>\n

root@chef_ws:~\/Development\/chef-repo# knife client list
\nchef-validator
\nchef-webui
\n192.168.1.4
\nroot@chef_ws:~\/Development\/chef-repo# <\/p>\n

example of add \u201cclient\u201d as “chef_client_01.XYZ.com\u201d from workstation chef_ws to CHEF server remotely:<\/p>\n

root@chef_ws:~\/Development\/chef-repo# knife bootstrap -u root chef_client_01.XYZ.com<\/p>\n

example of create\/detete \u201cenvironment\u201d from workstation chef_ws on CHEF server remotely:<\/p>\n

# knife environment create development -d “The development environment\u201d
\n# knife environment delete development -d “The development environment\u201d
\n# knife environment list # this is to list \u201cenvironment\u201d created on server side, the same view can be see from web ui at: https:\/\/192.168.1.2\/environments<\/p>\n

troubleshooting:<\/p>\n

root@chef_ws:~\/Development\/chef-repo# knife cookbook create my_test_cookbook<\/p>\n

# cd \/var\/chef\/cookbooks\/my_test_cookbook<\/p>\n

root@chef_ws:# ls
\nattributes CHANGELOG.md definitions files libraries metadata.rb providers README.md recipes resources templates<\/p>\n

root@chef_ws:\/var\/chef\/cookbooks\/my_test_cookbook# cd recipes<\/p>\n

root@chef_ws:\/var\/chef\/cookbooks\/my_test_cookbook\/recipes# ls<\/p>\n

default.rb
\n===================================================================<\/p>\n

#### start chef_client to deploy cookbook on host:<\/p>\n

root@192.168.1.4:~\/Development\/chef-repo# sudo chef-client
\nStarting Chef Client, version 12.2.1
\nresolving cookbooks for run list: []
\nSynchronizing Cookbooks:
\nCompiling Cookbooks…
\n[2015-04-14T14:23:17+00:00] WARN: Node 192.168.1.4 has an empty run list.
\nConverging 0 resources
\nRunning handlers:
\nRunning handlers complete
\nChef Client finished, 0\/0 resources updated in 1.132211206 seconds
\nroot@chef_ws:~\/Development\/chef-repo# <\/p>\n

====================================<\/p>\n

### add “run list\u201d to “192.168.1.4\u201d for “recipe[motd]\u201d :<\/p>\n

root@chef_ws:~\/Development\/chef-repo# knife node run_list add 192.168.1.4 recipe[motd]<\/p>\n

192.168.1.4:<\/p>\n

run_list: recipe[motd]<\/p>\n

Removed \u201crun list\u201d added:<\/p>\n

root@chef_ws:~\/Development\/chef-repo# knife node run_list remove 192.168.1.4 recipe[motd]<\/p>\n

https:\/\/docs.chef.io\/knife_cookbook.html<\/p>\n

root@chef_ws:~\/Development\/chef-repo\/roles# knife cookbook bulk delete motd<\/p>\n

All versions of the following cookbooks will be deleted:
\nmotd
\nDo you really want to delete these cookbooks? (Y\/N) Y
\nDeleted cookbook motd [0.1.0]<\/p>\n

root@chef_ws:~\/Development\/chef-repo# knife cookbook create motd<\/p>\n

** Creating cookbook motd in \/var\/chef\/cookbooks<\/p>\n

** Creating README for cookbook: motd<\/p>\n

** Creating CHANGELOG for cookbook: motd<\/p>\n

** Creating metadata for cookbook: motd<\/p>\n

root@chef_ws:~\/Development\/chef-repo# knife cookbook upload -a \/var\/chef\/cookbooks\/motd -E production<\/p>\n

Uploading motd [0.1.0]<\/p>\n

Uploaded all cookbooks.<\/p>\n

***************************************************************************************************<\/p>\n

Examples:<\/p>\n

Chef: step_to_deply_new_host_and_Remove_user_from_data_bag<\/p>\n

root@ws:~\/Development\/chef-repo# cat step_2_deply_new_host_for_chef<\/p>\n

## go to chef workstation, do following:<\/p>\n

cd ~\/Development\/chef-repo\/<\/p>\n

# knife bootstrap -u root ### add host to chef node and client<\/p>\n

# knife node list | grep ### verify node list on chef server to see if this host get added<\/p>\n

# knife client list | grep ### verify client list on chef server to see if this host get added<\/p>\n

## transfer the new added host to production ENV:<\/p>\n

# knife exec -E ‘nodes.transform(“chef_environment:_default”) { |n| n.chef_environment(“production”) }’<\/p>\n

# add host to run list:<\/p>\n

# for most host not as DNS and NTP server, they only need apply the role below:<\/p>\n

# knife node run_list set HOST_NAME ‘role[dns_ntp_client_role]’<\/p>\n

# example: knife node run_list set ‘role[dns_ntp_client_role]’<\/p>\n

# verify runlist to see if the host has been added:<\/p>\n

# knife search node ‘run_list:recipe\\[roles\\]’<\/p>\n

# example: knife search node ‘run_list:role\\[dns_ntp_client_role\\]’<\/p>\n

# example: knife search node <\/p>\n

# if all above are running successfilly, go to the client host to run “sudo chef-client” or run from anyware from cli.<\/p>\n

===================================================================================================================<\/p>\n

# on some CentOS 7 linux, add node and client from WS does not work with error about NTP, need to go to that box to intall NTP then restart services:<\/p>\n

$ sudo yum install ntp ntpdate ntp-doc;<\/p>\n

$ sudo chkconfig ntpd on;<\/p>\n

$ sudo ntpdate pool.ntp.org;<\/p>\n

$ sudo \/etc\/init.d\/ntpd start;<\/p>\n

$ sudo yum install bind-utils ##### install nslookup from this command, optional<\/p>\n

$ sudo yum install ruby; ruby –version; #### install ruby as chef needed<\/p>\n

or<\/p>\n

$ sudo yum install ntp ntpdate ntp-doc; sudo chkconfig ntpd on; sudo ntpdate pool.ntp.org; sudo \/etc\/init.d\/ntpd start; sudo yum install bind-utils; sudo yum install ruby; ruby –version;<\/p>\n

============================================================================<\/p>\n

# upload cookbook to production:<\/p>\n

$ sudo knife cookbook upload -E production -o cookbooks -a<\/p>\n

$ chef-client -v<\/p>\n

# upgrade chef-client on node<\/p>\n

$ curl -L https:\/\/www.opscode.com\/chef\/install.sh | sudo bash<\/p>\n

================================================================================================================
\nExample to remove user from data bag steps:<\/p>\n

step 1: <\/p>\n

Edit the user json file to set action to remove:<\/p>\n

root@ws:~\/Development\/chef-repo\/data_bags\/# cat blu.json
\n{
\n “id”: “blu”, #### the USER_ID could be as example
\n “comment”: “Benjamin Lu”, #### the comment for could be
\n “groups”: [ “sysadmin”],
\n “shell”: “\/bin\/bash”,
\n “uid”: 3000, #### this example is a fake, 3000 should the the real “uid” for
\n “action”: \u201cremove” #### this line of “remove” should be added here for remove !<\/p>\n

}<\/p>\n

Step 2:<\/p>\n

Update data bag in chef server from command :<\/p>\n

“knife data bag from file YOUR_sysadmin_group \/blu.json”<\/p>\n

root@ws:~\/Development\/chef-repo\/data_bags# ls -ltr
\ntotal 8
\n-rw-r–r– 1 root root 1876 Mar 31 10:48 README.md
\ndrwxr-xr-x 2 root root 4096 Jun 26 19:16 YOUR_sysadmin_group
\nroot@ws:~\/Development\/chef-repo\/data_bags# knife data bag from file YOUR_sysadmin_group YOUR_sysadmin_group\/blu.json
\nUpdated data_bag_item[YOUR_sysadmin_group::blu]<\/p>\n

Step 3:<\/p>\n

Go to any host has the user installed from chef, rerun \u201csudo chef-client\u201d to remove the user.<\/p>\n

step 4:<\/p>\n

Repeat step 3 on all host has the user installed.<\/p>\n

step 5:<\/p>\n

Delete this user as \u201cblu\u201d from data bag in chef server from command as below:<\/p>\n

# knife data bag delete YOUR_sysadmin_group blu<\/p>\n

root@ws:~\/Development\/chef-repo\/data_bags\/YOUR_sysadmin_group# <\/p>\n

# knife data bag delete YOUR_sysadmin_group blu
\nDo you really want to delete blu? (Y\/N) Y
\nDeleted data_bag_item[blu]<\/p>\n

Done !
\n==============================================================================================
\nTroubleshooting :<\/p>\n

Some host has no FQDN in \/etc\/hosts, cause chef deploy NOT work, need fix as below:<\/p>\n

Step 1: remove “\/etc\/chef\/client.pem\u201d, then edit “\/etc\/hosts \u201c to have FQDN, them remove “\/etc\/chef”<\/p>\n

[root@ ~]# <\/p>\n

$ rm \/etc\/chef\/client.pem
\n $ hostname
\n $ vi \/etc\/hosts ( the host name has to be FQDN )
\n $ rm -rf \/etc\/chef<\/p>\n

Step 2: go to chef working station to add it again: at <\/p>\n

root@ws:~\/Development\/chef-repo# <\/p>\n

example:<\/p>\n

$ knife bootstrap -u root ;<\/p>\n

Step 3, Apply role again:<\/p>\n

$ knife node run_list set ‘role[dns_server_role]\u2019<\/p>\n

Step 4, deploy chef again on the client host:<\/p>\n

[root@ ~]# chef-client;<\/p>\n

Done;<\/p>\n","protected":false},"excerpt":{"rendered":"

Chef server, client, and workstation setup: root@chef_server:~# # sudo apt-get upgrade # use this command to update software first on ubuntu linux Install ruby and verify before Chef Env setup: # sudo apt-get install ruby-full # which ruby ## verify if ruby get install # ruby -v # wget https:\/\/opscode-omnibus-packages.s3.amazonaws.com\/ubuntu\/12.04\/x86_64\/chef-server_11.0.8-1.ubuntu.12.04_amd64.deb # which ruby \/bin\/ruby reset […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/cephswift.com\/index.php\/wp-json\/wp\/v2\/pages\/100"}],"collection":[{"href":"https:\/\/cephswift.com\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/cephswift.com\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/cephswift.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cephswift.com\/index.php\/wp-json\/wp\/v2\/comments?post=100"}],"version-history":[{"count":4,"href":"https:\/\/cephswift.com\/index.php\/wp-json\/wp\/v2\/pages\/100\/revisions"}],"predecessor-version":[{"id":113,"href":"https:\/\/cephswift.com\/index.php\/wp-json\/wp\/v2\/pages\/100\/revisions\/113"}],"wp:attachment":[{"href":"https:\/\/cephswift.com\/index.php\/wp-json\/wp\/v2\/media?parent=100"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}