Changes between Version 25 and Version 26 of GiB-gettingStarted

Timestamp:

10/02/12 15:48:31 (12 years ago)

Author:

Vic Thomas

Comment:

--

GiB-gettingStarted

@@ -127 +127 @@
 The output of the command is the ''advertisement rspec'' from the GENI-in-a-Box aggregate.  You'll see the aggregate advertises six compute resources.   Only two are shown here for readability reasons but you will find the complete advertisement rspec [attachment:gib-advert.rspec here].  Look at the description of the first resource in the rspec.   This compute resources is an openVZ container running Fedora 15 image (or an Ubuntu 10 image if you are using the Ubuntu flavor of GENI-in-a-Box).  The  resource has four network interfaces: {{{eth0}}} through {{{eth3}}}.  {{{eth0}}} is a control interface and is not available to the experimenter.  All six compute resources advertised by this aggregate are identical.  You can therefore use this aggregate to create experiment topologies with up to six nodes and up to three links per node. 
 
-=== 2.2 Acquire and configure resources ===
+=== 2.2 Acquire and Configure Resources ===
 Before we run an experiment we need to acquire the resources needed the experiment.   Our introductory experiment will consist of two hosts connected to one another by a single link.   When the hosts come up they execute a script provided by us that:
     * Downloads and installs iperf on each host.
@@ -223 +223 @@
 Notice the manifest rspec is essentially your request respec annotated with information about the resources that got allocated to you.  For example, the {{{<node>}}} element of the manifest includes the MAC and IP addresses assigned to each network interface on the node (host) and information you will need to ssh into the nodes (e.g. the fully qualified domain name of the host ).
 
+=== 2.3 Using your Resources ===
+You can now ssh into the hosts allocated to you and do what you need to do to get your experiment working.  For example, you can install and run software.  If needed, you can use the {{sudo}} command to do things that require root privileges.  
+
+In the case of our experiment, the software needed (iperf) was installed by our startup script.  Our startup script put the output of iperf in a file accessible from a web browser.   Since our iperf client ran on node {{{pc102}}} (the node labeled 'right' in the request spec), we can use a browser to view the output of this client.  Start up Firefox in a terminal on the GENI-in-a-Box virtual machine and enter the url {{{http://pc102.geni-in-a-box.net/iperf-client.log}}}.  The iperf client output should appear in your browser window.
+
+You can also ssh into the node pc102 to view this file.  GENI-in-a-Box comes with a user account 'alice' with private and public keys for alice installed in it.  When experimenter nodes are created an account is created for alice on these nodes and alice's public key installed in the .ssh directory inside alice's home directory.  You can create your own user accounts; see here for instructions.
+
+You can ssh into node {{{pc102}} as alice type {{{ssh -lalice pc102.geni-in-a-box.net}}} or just {{{ssh -lalice pc102}}}.  The terminal session below shows the ssh'ing into {{{pc102}}}, going to the directory with the iperf log file, and viewing that file.
+
 
 [[BR]]