Changes between Version 19 and Version 20 of GEC21Agenda/ScalingUp/Procedure/Appendix

Timestamp:

05/27/15 22:11:48 (9 years ago)

Author:

sedwards@bbn.com

Comment:

--

GEC21Agenda/ScalingUp/Procedure/Appendix

@@ -158 +158 @@
 </table>
 }}}
-The Playbook to configure the `server` node is in `server.yml`.  It links to other files.  For example, the code to tell the `server` node to run the `nmap` scan and post the results is in `roles/nmap/tasks/map.yml` and looks as follows:
+The Playbook to configure the `server` node is in `server.yml`.  It links to other files.  For example, the code to tell the `server` node to run an `nmap` scan and post the results is in `roles/nmap/tasks/map.yml` and looks as follows:
 
    {{{
@@ -176 +176 @@
     }}}
 
-''Do these commands look like the Ad Hoc commands from the previous step?''
+''Do these commands look like the Ad Hoc ping command from the previous step?''
 
-Run the playbook with the following command on the local machine:
+Run the playbook to configure the `server` with the following command on the local machine:
 
    {{{
@@ -185 +185 @@
    }}}
 }}}
- a. Browse to the server node.  Click on the `nmap` link.
+ a. Browse to hostname of the server node in your browser.  Click on the `nmap` link.
 
 === 4. Update a portion of the configuration ===
- a. After some of your neighbors have brought up their nodes, run the following command to only do a portion of the `server` configuration:
+ a. After some of your neighbors have brought up their nodes, run the following command to only do the nmap portion of the `server` configuration:
    {{{
 #!python
 ansible-playbook update-map.yml -i inventory
    }}}
- a. You should see more nodes found by the nmap scan.  
+ a. Over time you should see more nodes found by the nmap scan.  
  a. Change the value of `address_range` in `groups_vars/all.yml` and rerun `update-map.yml` to search for more nodes.