Changes between Version 27 and Version 28 of GiB-gettingStarted

Timestamp:

10/02/12 15:50:17 (12 years ago)

Author:

Vic Thomas

Comment:

--

GiB-gettingStarted

@@ -165 +165 @@
 }}}
 
-2. We now send our [attachment:two-nodes-iperf.rspec request rspec] to the GENI-in-a-Box aggregate manager using the command {{{omni.py -a http://geni-in-a-box.net:8001 createsliver myslice two-nodes-iperf.rspec}}}.  ''This command will take many minutes to complete because it configures and boots up the requested virtual machines, does some additional configuration, and download, installs, and runs iperf.''  If our request is successful, the aggregate manager will allocate the requested resources to our slice.  In GENI parlance the resources allocated to our slice are called slivers.  The {{{createsliver}}} request returns a manifest spec that provides details of the resources allocated to us.  The following is a snippet of the manifest your will get back from {{{createsliver}}}:
+2. We now send our [attachment:two-nodes-iperf.rspec request rspec] to the GENI-in-a-Box aggregate manager using the command {{{omni.py -a http://geni-in-a-box.net:8001 createsliver myslice two-nodes-iperf.rspec}}}.  ''This command will take many minutes to complete because it configures and boots up the requested virtual machines; does some additional configuration; and download, installs, and runs iperf.''  If our request is successful, the aggregate manager will allocate the requested resources to our slice.  In GENI parlance the resources allocated to our slice are called slivers.  The {{{createsliver}}} request returns a manifest spec that provides details of the resources allocated to us.  The following is a snippet of the manifest your will get back from {{{createsliver}}}:
 {{{
 $ omni.py --api-version 2 -a http://geni-in-a-box.net:8001 createsliver myslice two-nodes-iperf.rspec