Changes between Version 13 and Version 14 of ChefonDETER

Timestamp:

Jul 15, 2014 3:42:19 PM (10 years ago)

Author:

Geoff Lawler

Comment:

--

ChefonDETER

@@ -176 +176 @@
 }}}
 
-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. 
+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. But you can see the recipes run and fail. 
 
 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.)
-
+ * {{{etchosts}}}: extract peer information and create an experiment specific {{{/etc/hosts}}} for the node.
+ * {{{routing}}}: set default routes and route correctly for control net and data net. It grabs all addresses and subnet information, builds a graph and uses Dijkstra's algorithm to find shortest-path routing, then sets the appropriate routes. It currently sets a route for each node in the experiment. This is not good. The recipe will have to be improved to handle subnet routing.  
+ * {{{mounts}}}: look in the appropriate "data bag" for the test bed type the client is running on and mount the file systems found there. 
+ * {{{accounts}}}: extract user account information from the database and make the user accounts. Home directories would be on the mounted directories from the {{{mounts}}} recipe.
+ * {{{ifconfig}}}: extract data network IP address(es) and netmask(s) from the database and set them on the appropriate network interfaces.
+ * {{{binaries}}}: copy (via wget) platform specific binaries and start them running. This recipe currently start {{{ipodd}}} and {{{slothd}}}. This recipe could be expanded to build the binaries, create /etc/init.d/ scripts, then start the daemons. Etc. 
+ 
 === Chef Client(s) Installation/Configuration ===