Changes between Version 12 and Version 13 of ChefNotes

Timestamp:

May 28, 2014 10:35:27 AM (10 years ago)

Author:

Geoff Lawler

Comment:

--

ChefNotes

@@ -227 +227 @@
     * I also need to know this for the simple node_id --> pid/eid SQL. 
     * Found the correct table to extract node_id and interface information from. {{{interfaces}}} and wrote the ifconfig recipe. Seems to work.
+
+
+ifconfig sorted out for simplist case: hostname -->  ipaddress. Used 3rd party host file manager cookbook. To integrate was easy: git clone the cookbook, cp -r it into our chef-repo, add dependency in cookbook/deter_node/metadata.rb. 
+
+Working now on routing. First pass is not straight-forward: tmcd just returns {{{ROUTERTYPE=static}}} for {{{tmcc routing}}}. Looking through the tmcd.c code is no help. I need to find where routes are set. 
+  * found rc.route on testnodes.
+    * rc.route --> getrouterconfig --> libsetup.pm --> seems to assume that it gets something back from {{{tmcd routing}}}
+  * checked on more complicated experiment and {{{tmcc routing}}} still just gives {{{ROUTERTYPE=static}}}.
+  * Need to find this "new" routing technique. Code comment says to return static at vers > 19.
+    * Looks like static --> triggers {{{calcroutes}}} which uses the {{{linkmap}}} file. 
+      * Can we assume it'll be there? If we mount the /proj file it should be... So write our own {{{calcroutes}}} as a (ruby) recipe? Looking into it. 
+    * Looks like rc.routes calls into libsetup to get route info then writes a new rc.routes in /var/emulab/boot that itself sets the routes based on the command line args. What calls this? Who knows. 
+  * So two ways this could go: follow existing arcane routing method or use the "old" routing information that emulab puts in the database somewhere (this would entail finding out where/how the {{{linkmap}}} file is generated. It must come from the database somehow, right?)
+
 ----