Context Navigation

DesignSetup

Timestamp:: 06/23/15 10:41:05 (9 years ago)
Author:: sedwards@bbn.com
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

GENIExperimenter/Tutorials/GENI-SAVI/DesignSetup

-                      v64
+                      v65
 $ ./tutorial.sh createvm savi <tenant_name> <location> <os_image_name> <vm-size> <ssh_key> <vm-name>
 }}}
+ * Each group will be given a specific site and values for all parameters.
+   * The `vm-name` should be your GENI username, followed by the `sitename`.  e.g., for `rickmcg`, the name at Toronto will be `rickmcg-toronto`
+   * Use the following command to reserve your SAVI node:
+ * Each group will be given a specific site and values for all parameters.  The `vm-name` should be your GENI username, followed by the `sitename`.  e.g., for `rickmcg`, the name at Toronto will be `rickmcg-toronto`
+{{{
+#!div style="background: #ffd; border: 3px ridge; width: 800px;"
+Use the following command to reserve your SAVI node:
 {{{
 $ ./tutorial.sh createvm savi geniUsers <savi site> Ubuntu-14-04-64 small geni_key_portal <geni_username>-<savi sitename>
 }}}
+ * You should now have one VM on a GENI rack and one VM at a SAVI site.   Check the status of your resources on both GENI and SAVI:
+}}}
+ * You should now have one VM on a GENI rack and one VM at a SAVI site.
+{{{
+#!div style="background: #ffd; border: 3px ridge; width: 800px;"
+Check the status of your resources on both GENI and SAVI:
 {{{
 $ ./tutorial.sh listinstance geni <slice-name>
 $ ./tutorial.sh listinstance savi <site-name>
 }}}
+ * Take note of the hostname for your GENI VM and the public IP address listed for your SAVI VM as these will be used in the next step.  ''Notice that access to the SAVI machines are by IP address.''
+}}}
+ * Make note of the hostname for your GENI VM and the public IP address listed for your SAVI VM as these will be used in the next step.  ''Notice that access to the SAVI machines are by IP address.''
 == 4. Set up Ansible for your experiment ==
 …
 }}}
+{{{
+#!div style="background: #ffd; border: 3px ridge; width: 800px;"
 Create an Ansible inventory file named `ansible-hosts` for your slice.
 …
 Where `geni_resource_name` and `savi_resource_ip` are what you found from the `listinstance` commands from step 3.
+}}}
 === (b) Add private key to SSH agent ===
 In the next step, Ansible will try to SSH into multiple nodes.
+ * To save time entering the passphrase for your private key multiple times, add your private key to your ssh agent as follows:
+{{{
+#!div style="background: #ffd; border: 3px ridge; width: 800px;"
+To save time entering the passphrase for your private key multiple times, add your private key to your ssh agent as follows:
 {{{
 $ ssh-agent bash
 $ ssh-add ~/.ssh/geni_key_portal
 }}}
+}}}
 === (c) The ping module ===
+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:
+The '''ping''' module simply tries to do a SSH login to a node and reports success or failure.
+{{{
+#!div style="background: #ffd; border: 3px ridge; width: 800px;"
+Run the following command on your controller:
 {{{
 $ ansible nodes -i ansible-hosts -m ping
 …
 If you don’t see success everywhere then there is something wrong with your setup.  Ask one of the tutorial leaders for help.
+}}}
 === (d) The shell module ===
 …
 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.
+{{{
+#!div style="background: #ffd; border: 3px ridge; width: 800px;"
 Try it out:
 …
 You can replace ''hostname'' above with any other Linux command.
+}}}
 === (e) The setup module ===
 The '''setup''' module gathers a bunch of information about each node and saves it in variables that you can reference in your Ansible playbook.  This will be really useful to do the tutorial!
+{{{
+#!div style="background: #ffd; border: 3px ridge; width: 800px;"
 Try it out on a node to see what it collects (replace `<your-vm>` with your hostname):
 …
 }}}
+}}}
 {{{
 #!comment
 …
 == 5. Create and run an Ansible playbook to install the software you will need ==
 Now you will use a playbook to install the software you will need on all the nodes.  Below is the ansible playbook you will need.
  * To download this playbook to your client machine, type:
 {{{
+ wget http://groups.geni.net/geni/raw-attachment/wiki/GENIExperimenter/Tutorials/GENI-SAVI/DesignSetup/software-install-solution.yaml
+}}}
  * The ansible playbook:
+Now you will use a playbook to install the software you will need on all the nodes.
+{{{
+#!div style="background: #ffd; border: 3px ridge; width: 800px;"
+The ansible playbook you will need:
 {{{
 ---
 …
 }}}
+ * To download this playbook to your client machine, type:
+{{{
+ wget http://groups.geni.net/geni/raw-attachment/wiki/GENIExperimenter/Tutorials/GENI-SAVI/DesignSetup/software-install-solution.yaml
+}}}
  * Run this playbook on your Ansible control machine against all the nodes in your slice.
 {{{
 …
 || [[Image(wiki:GENIExperimenter/Tutorials/Graphics:tip.png, nolink, 50px, bottom)]] || '''Pro Tip:''' use the `-f` argument to `ansible-playbook` to speed things up -- it lets you control the number of nodes to operate on in parallel, and the default is 5.  Specifying `-f 20` will run the playbook's tasks against all your nodes in parallel.   ||
+}}}
 ----