Context Navigation

DesignSetup

Timestamp:: 05/26/15 11:57:17 (9 years ago)
Author:: rick@mcgeer.com
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

GENIExperimenter/Tutorials/GENI-SAVI/DesignSetup

-                      v5
+                      v6
 }}}
+we have chosen values for all parameters.  The vm-name should be your geni-username
+{{{
+$ ./tutorial.sh createvm savi <tenant_name> toronto ubuntu-14-04-64 small savi_tutorial <geni_username>
+$  ./tutorial.sh createvm savi <tenant_name> victoria ubuntu-14-04-64 small savi_tutorial <geni_username>
+}}}
+We now have VMs at Cornell, Utah, Toronto, and Victoria.
+{{{
+$ ssh -i id_rsa -F ssh-config slice338.pcvm3-1.instageni.metrodatacenter.com
+}}}
+Type '''ifconfig eth0'''.  You should see an eth0 interface with an IP address in the 10.0.0.0/8 range, a ''private'' IP address.
+{{{
+root@slice347:~# ifconfig eth0
+eth0      Link encap:Ethernet  HWaddr a6:24:c1:df:c7:09
+          inet addr:10.20.0.243  Bcast:0.0.0.0  Mask:255.255.0.0
+          inet6 addr: fe80::a424:c1ff:fedf:c709/64 Scope:Link
+          UP BROADCAST RUNNING  MTU:1500  Metric:1
+          RX packets:56555 errors:0 dropped:2 overruns:0 frame:0
+          TX packets:49525 errors:0 dropped:0 overruns:0 carrier:0
+          collisions:0 txqueuelen:1000
+          RX bytes:93890170 (93.8 MB)  TX bytes:8052865 (8.0 MB)
+}}}
+This IP address is behind a NAT and not directly reachable from outside (i.e., from the Internet).  However all nodes in your slicelet can contact each other using the private addresses.
+The nodes in your '''ssh-config''' file are Docker containers running on (virtual) hosts.  These hosts have ''public'' IP addresses that are routable from the Internet, that's why you can login to the Docker containers of your slicelet.  A port on the public IP address (e.g., 49155) is forwarded to the SSH port (22) on the container's private IP address.  The '''ssh-config''' file contains the names of the virtual hosts and the port forwarding information.
+When you run a server on a node in your slicelet, it will listen on the private address, because that is the only one it can see.  By default it will only be visible to other nodes in your slicelet.  Docker provides facilities for exposing ports to the public Internet, but this topic is outside the scope of this tutorial.
+''Note that later on you will need to find both the ''public'' and ''private'' IP addresses for each node in the slicelet.''
+----
+== 3. Configure the Ansible controller for your slicelet ==
+If you already have Ansible installed on your laptop, then you can use it as the controller for this experiment.  Otherwise, you will use one of the nodes in your slicelet as the Ansible controller.  Pick one, log into it, and install ansible using apt-get:
+{{{
+$ apt-get update
+$ apt-get install ansible
+}}}
+Then upload your slicelet helper files to that node.  {{{scp}}} can be used for this; in the directory where you unzipped the files, run a command like the following:
+{{{
+$ scp -F ssh-config * ansible-hosts slice323.pcvm3-1.instageni.metrodatacenter.com:
+}}}
+|| [[Image(wiki:GENIExperimenter/Tutorials/Graphics:tip.png, nolink, 50px, bottom)]] || '''Pro Tip:''' remove your controller node from the '''ansible_hosts''' file after you’ve uploaded. ||
+----
+we have chosen 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
+{{{
+$ ./tutorial.sh createvm savi <tenant_name> toronto ubuntu-14-04-64 small savi_tutorial <geni_username>-toronto
+$  ./tutorial.sh createvm savi <tenant_name> victoria ubuntu-14-04-64 small savi_tutorial <geni-username>-victoria
+}}}
+We now have VMs at Cornell, Utah, Toronto, and Victoria.   Check the status of your resources on both GENI and SAVI
+{{{
+$ ./tutorial.sh listinstance geni
+$ ./tutorial.sh listinstance savi
+}}}
+Notice that access to the SAVI machines are by IP address
 == 4. Learn some basic concepts of Ansible ==
 …
 Ansible (http://docs.ansible.com) is a free, open-source, intuitive IT automation tool that is well-suited to the tasks in this tutorial.  Ansible commands can be run from the command line or put in a YAML file called a ''playbook''.  We will be creating an Ansible playbook to run the parameterized HTTP query described earlier.
 Two basic concepts in Ansible are ''inventories'' and ''modules''.  An inventory is a list of hosts to be managed by Ansible, organized into groups.  When you run Ansible commands, either from the command-line or in a playbook, you specify the host group that the command should operate on.  In this way Ansible commands can operate on many hosts in parallel.  Take a look at the Ansible inventory in your '''ansible-hosts''' file.  This is basically the equivalent of the '''ssh-config''' except its specialized for Ansible.
+Two basic concepts in Ansible are ''inventories'' and ''modules''.  An inventory is a list of hosts to be managed by Ansible, organized into groups.  When you run Ansible commands, either from the command-line or in a playbook, you specify the host group that the command should operate on.  In this way Ansible commands can operate on many hosts in parallel.  Take a look at the Ansible inventory in your '''ansible-hosts''' file.  This is basically the equivalent of the '''ssh-config''' except it's specialized for Ansible.
 A ''task'' in Ansible consists of a module and some arguments for the module.  A module provides a declarative abstraction on top of standard shell commands.  So for example, in the shell on an Ubuntu machine you might install package “foo” like this:
 …
 Here are a few Ansible tasks to run, to get some experience with the command-line interface.
+=== (a) The ping module ===
+=== (a) Create an Ansible Hosts file ===
+An Ansible hosts file is of the form
+{{{
+server1.example.com
+server2.example.com
+}}}
+or
+{{{
+server1.example.com ansible_ssh_host=10.0.0.1
+server2.example.com ansible_ssh_host=10.0.0.2
+}}}
+Create an Ansible Hosts file for your slice.  An example is here:
+=== (b) 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:
 …
 If you don’t see success everywhere then there is something wrong with your setup.  Ask one of the tutorial leaders for help.
 === (b) The shell module ===
+=== (c) 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.  Try it out:
 …
 You can replace ''hostname'' above with any other Linux command.
 === (c) 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 playbooks.  This will be really useful to do the tutorial!   Try it out on a node to see what it collects (replace `<your-slicelet>` with your slicelet’s name):
 {{{
 $ ansible <your-slicelet>.pcvm1-1.instageni.wisc.edu -i ansible-hosts -m setup
 }}}
 === (d) A simple playbook ===
+=== (d) 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 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):
+{{{
+$ ansible <yourvm>.utahddc.geniracks.net -i ansible-hosts -m setup
+}}}
+=== (e) A simple playbook ===
 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: