Changes between Version 8 and Version 9 of ChefonDETER

Timestamp:

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

Author:

Geoff Lawler

Comment:

--

ChefonDETER

@@ -96 +96 @@
 }}}
 
+Push testbed specific information to the chef server. The {{{deter_user}}} recipes look for this information to get testbed-specific instantiation information, like the name of the boss machine or which file systems to mount. Chef calls these collections of data, "data bags". We first create a named data bag, "testbed-defs" then populate it with the testbed-specific information.
+
+{{{
+workstation$ cd /local/chef-repo
+workstation$ knife data bag create testbed-defs
+workstation$ # We only have an emulab-in-emulab data bag defined right now.
+workstation$ knife data bag from file testbed-defs data_bags/testbed-defs/eine.json
+workstation$ knife data bag show testbed-defs eine
+binary_store_path: binaries                                    
+bossnode:          myboss.eine.deter.isi.deterlab.net          
+db_conf:                                                       
+  host: myboss.eine.deter.isi.deterlab.net                     
+  name: tbdb                                                   
+  user: mysql                                                  
+fsnode:            myops.eine.deter.isi.deterlab.net           
+fsprojdir:         /q/proj                                     
+fsuserdir:         /q/users                                    
+id:                eine                                        
+node_mounts:                                                   
+  device:      myops.eine.deter.isi.deterlab.net:/share        
+  fstype:      nfs                                             
+  mount_point: /share                                          
+  options:     ro                                              
+projdir:           /proj                                       
+scratch:           myboss.eine.deter.isi.deterlab.net:8000     
+testbed_netmask:   255.255.0.0                                 
+testbed_network:   192.168.0.0                                 
+userdir:           /users                                      
+usernode:          myops.eine.deter.isi.deterlab.net           
+workstation$
+}}}
+
 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. 
 
@@ -143 +175 @@
 }}}
 
+Now we force  {{{chef-client}}} to run on the client by sshing to it and running {{{chef-client}}} by hand. The recipes assigned to the node will fail however as we've not installed the mysql2 libraries the recipes need to communicate with the DETER database. If they were installed though, it still would not work as the DETER database is not accessible remotely. 
+
+Thus ends the tutorial. 
+
+If you wanted to take it further, you can run an emulab-in-emulab experiment, install the mysql2 libraries on the client, and re-run {{{chef-client}}} on the client. If run you would see these recipes run in order.
+ * {{{routing}}}: set default routes and route correctly for control net and data net. 
+ * {{{mounts}}}: look in the appropriate "data bag" for the test bed type the client is running on and mount the file systems found there. See {{{/local/chef-repo/data_bags/testbed-defs/eine.json}}} for a sample emulab-in-emulab testbed-specific configuration. (These testbed specific data bags take the place of the compile time *.DEF files in the testbed source tree.)
+
 === Chef Client(s) ===