Changes between Version 34 and Version 35 of GENIExperimenter/Tutorials/GENI-SAVI/DesignSetup
- Timestamp:
- 06/15/15 15:42:14 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/GENI-SAVI/DesignSetup
v34 v35 170 170 Where geni_resource_name and savi_resource_ip are what you found from the listinstance commands from step 3. 171 171 172 === (b) The ping module === 172 === (b) Add private key to SSH agent === 173 174 In the next step, Ansible will try to do a SSH login to multiple nodes. To save time entering the passphrase for your private key multiple times, add your private key to your ssh agent as folllows. 175 176 {{{ 177 $ ssh-agent bash 178 $ ssh-add ~/.ssh/geni_portal_key 179 }}} 180 181 === (c) The ping module === 173 182 174 183 The '''ping''' module simply tries to do a SSH login to a node and reports success or failure. Run the following command on your controller: … … 180 189 If you don’t see success everywhere then there is something wrong with your setup. Ask one of the tutorial leaders for help. 181 190 182 === ( c) The shell module ===191 === (d) The shell module === 183 192 184 193 The '''shell''' module lets you run arbitrary SSH commands in parallel across a set of hosts. It’s useful for poking around, or if there is no Ansible module with the functionality you need. Try it out: … … 190 199 You can replace ''hostname'' above with any other Linux command. 191 200 192 === ( d) The setup module ===201 === (e) The setup module === 193 202 194 203 The '''setup''' module gathers a bunch of information about each node and saves it in variables that you can reference in your Ansible playbooks. This will be really useful to do the tutorial! Try it out on a node to see what it collects (replace `<your-vm>` with your hostname): … … 198 207 }}} 199 208 200 === ( e) A simple playbook ===209 === (f) A simple playbook === 201 210 202 211 Next, we will look at a simple Ansible playbook. An Ansible playbook is a YAML file containing a list of Ansible tasks. Copy the playbook below into a file called test.yaml: