Changes between Version 49 and Version 50 of GiB-gettingStarted

Timestamp:

10/16/12 14:13:44 (12 years ago)

Author:

lnevers@bbn.com

Comment:

--

GiB-gettingStarted

@@ -146 +146 @@
 We'll use the rspec file called two-nodes-iperf.rspec.  You can view it [attachment:two-nodes-iperf.rspec here] or inside the VM.  This rspec requests two hosts called {{{left}}} and {{{right}}}.  Host {{{left}}} has one interface called {{{left:if0}}} and host {{{right}}} has one interface called {{{right:if0}}}.  The two interfaces are connected by a link called {{{left-right-lan}}}.  The following figure illustrates the resources requested by this rspec.
 
-[[Image(ResourcesRequested.png, 55%)]]
+[[Image(ResourcesRequested.png, 60%)]]
 
 The {{{<install>}}} element in the rspec asks the GENI-in-a-Box aggregate manager to download a [attachment:iperf-script.sh script] from the specified URL, uncompress and untar it,  and save it in the {{{/local}}} directory.  The {{{<execute>}}} element asks the aggregate to execute the specified script when the hosts come up.  In this case the script to be executed is the one that was installed in {{{/local}}}. 
@@ -237 +237 @@
 Notice the manifest rspec is essentially your request rspec 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 ).  The following figure illustrates the resource allocation made by the GENI-in-a-Box aggregate, as described in the manifest spec.
 
-[[Image(ResourcesAllocated.png, 55%)]]
+[[Image(ResourcesAllocated.png, 60%)]]
 
 === 2.3 Using your Resources ===