Changes between Version 7 and Version 8 of ChefonDETER

Timestamp:

Jul 14, 2014 4:10:03 PM (10 years ago)

Author:

Geoff Lawler

Comment:

--

ChefonDETER

@@ -76 +76 @@
 }}}
 
+Note that the {{{knife}}} command looks in ~/.chef and $(cwd)./chef for configuration files, so execute all {{{knife}}} commands from the {{{/local/chef-repo}}} directory or {{{knife}}} will be dull and not-happy. 
+
+Push the local roles and recipes to the chef server.
+{{{
+> cd /local/chef-repo
+> knife cookbook upload hostsfile deter_node 
+Uploading hostsfile    [2.4.4]                                                               
+Uploading deter_node   [0.1.1]                                                               
+Uploaded 2 cookbooks.                                                                        
+> knife role from file roles/deter_node.rb
+Updated Role deter_node!
+> # Confirm things are OK.
+> knife cookbook list
+deter_node   0.1.1
+hostsfile    2.4.4
+> knife role list
+deter_node
+>
+}}}
+
+We are now going to use {{{knife}}} to bootstrap Chef unto a client machine. The usual Chef assumes internet connectivity and asks you to download a script and pipe it to {{{sudo}}} on the client. We will not be doing that. 
+
+{{{
+> cd /local/chef-repo
+> mkdir .chef/bootstrap
+> cp /share/chef/ubuntu12.04-deb.erb .chef/bootstrap
+}}}
+
+The bootstrap usually grabs the package file from the internet. We give {{{chef}}} a custom bootstrap script that looks for it at {{{users:8523}}}. This means something on {{{users}}} must be listening on port 8523 and understand how to serve files via HTTPS. We use python for this. On {{{users}}}, cd to /share/chef and run {{{python -m SimpleHTTPServer 8523}}}. This starts a simple HTTP server on port 8523. If you want to run on your local server instead edit the file {{{/local/chef-repo/.chef/bootstrap/ubuntu12.04-deb.erb}}}, set the {{{SERVER}}} variable to the control net FQDN/ip address of your server and run the python simple server there. 
+
+Now run the bootstrap command to install and configure chef on the client. {{{$NODE}}} is the control net name of the client node, like {{{pc33.isi.deterlab.net}}} and {{{$USER}}} if your sudo-able user name, like {{{glawler}}} or {{{faber}}}. 
+
+{{{
+> knife bootstrap $NODE -x $USER --sudo --distro ubuntu12.04-deb
+}}}
+
+Now kill the python SimpleHTTPServer process on users. 
+
+Confirm the node has chef installed and configured by running this {{{knife}}} command on your workstation machine. It should show the client node.
+
+{{{
+> cd /local/chef-repo
+> knife client list
+chef-validator
+chef-webui
+pc33.isi.deterlab.net
+> # show the node information:
+> knife node show pc33.isi.deterlab.net
+Node Name:   pc33.isi.deterlab.net 
+Environment: _default              
+FQDN:        pc33.isi.deterlab.net 
+IP:          192.168.1.33          
+Run List:                          
+Roles:                             
+Recipes:                           
+Platform:    ubuntu 12.04          
+Tags:                              
+}}}
+
+Now we assign recipes or a role to the client node and tell it to configure itself. (Note this could've been done during the bootstrap via the {{{-r}}} argument.
+
+{{{
+workstation$ knife node run_list add pc33.isi.deterlab.net 'role[deter_node]' 
+pc33.isi.deterlab.net:      
+  run_list: role[deter_node]
+}}}
 
 === Chef Client(s) ===
@@ -82 +148 @@
 
 {{{
-> # already installed via knife bootstrap.
+> # already installed via knife bootstrap!
 }}}