Changes between Version 6 and Version 7 of ChefonDETER

Timestamp:

Jul 14, 2014 2:43:19 PM (10 years ago)

Author:

Geoff Lawler

Comment:

--

ChefonDETER

@@ -31 +31 @@
 }}}
 
-Configure admin user and set up keys. Note there is a web interface for this. Since it assumes you're running the browser locally though, you need to setup an ssh tunnel and a web proxy like Foxy-Proxy to access it. For this script, we just stick to the command line. For this though, we need to copy private keys. The procedure for using the web API copies public keys from a web page.
-
 Install git and the chef-repo:
 {{{
@@ -40 +38 @@
 > git clone /share/chef/chef-repo
 > cd chef-repo
+}}}
+
+Take a look in {{{/local/chef-repo/cookbooks/deter_node/recipes}}} for the "deter_node" recipes. There is also a simple "deter_node" role in {{{/local/chef-repo/roles/deter_node.rb}}} that has a {{{run_list}}} that tells the node to execute the recipes in the correct order.  
+
+Now configure the workstation user and set up keys. Note that there *is* a web interface for this and that is the standard interface to use for this. Since it assumes you're running the browser locally though, you need to setup an ssh tunnel and a web proxy like Foxy-Proxy to access it. For this script though (and because we prefer it as it's scriptable) we stick to the command line. To do this though, we need to copy private keys. The procedure for using the web API copies public keys from a web page.
+
+{{{
 > mkdir .chef
 > # copy keys!
@@ -70 +75 @@
 >
 }}}
-Take a look in {{{/local/chef-repo/cookbooks/deter_node/recipes}}} for the "deter_node" recipes. There is also a simple "deter_node" role in {{{/local/chef-repo/roles/deter_node.rb}}} that has a {{{run_list}}} that tells the node to execute the recipes in the correct order.  
-
-In order to talk to the chef server with authority, we set up an {{{admin}}} user and distribute/generate keys. 
-{{{