Changes between Version 17 and Version 18 of ChefNotes

Timestamp:

Feb 17, 2015 10:10:28 AM (10 years ago)

Author:

Geoff Lawler

Comment:

newer(est) plan written down.

ChefNotes

@@ +1 @@
+=== The newer(est) plan: ===
+
+Build a local, experiment-specific database from files generated by the containers system. Use this local database (living on a pnode or experiment wide configuration/Chef) to configure containers (and eventually physical) nodes. 
+
+1. look through and document files generated or existing in the containers system. Working document is here: http://containers.deterlab.net/wiki/ContainerFilesDoc. 
+
+2. determine what information is needed to properly configure the nodes to be good DETERizens. Rough cut is: user accounts (id, name, etc.), mounts (user home dirs, scratch, project dir), network interfaces (addresses, subnets, filters?, etc). For pnodes it'd be nice to have Chef (or whatever) also configure the container networks. (This is not unreasonable as it exists in python in the containers system now, but would require a rewrite in Ruby if we use Chef. If we use Puppet it might be less painful as Puppet speaks python.) 
+
+3. use info from 2 to write a script/module that creates the local database. 
+
+4. rewrite the existing Chef recipes in {{{/share/chef/chef-repo}}} to use the new schemas. They currently use the boss DETER schemas.
+
 === The new(est) plan: ===
 Make recipes that query the tbdb directly. If done right, the nodes configure themselves with information from the database directly. The code for querying the database will live in Chef recipes, pulled onto the nodes, then executed on boot. We'll add a hook in dhcp init, much like emulab does now to insure the control network is up, that executes 'chef-client', which does the magic.