Changes between Version 6 and Version 7 of GiB-to-ProtoGENI

Timestamp:

10/09/12 19:54:49 (12 years ago)

Author:

Vic Thomas

Comment:

--

GiB-to-ProtoGENI

@@ -7 +7 @@
   * Experimenters get root access to their virtual machines.
   * Virtual machines from both aggregates are implemented as OpenVZ containers running Fedora 15.  The Ubuntu flavor of GENI-in-a-Box provides OpenVZ containers running Ubuntu. 
-  * The manifest rspec is available in all the experimenter nodes at {{{/prof/geni-in-a-box.net/exp/<slicename>/tbdata/geni_manifest}}} and the fully qualified name of the node is available in {{{/var/emulab/boot/nickname}}}.  An example of a fully qualified node name is {{{pc101.myslice.geni-in-a-box.net}}} where {{{myslice}}} is the name of the slice.
+  * The manifest rspec is available in all the experimenter nodes at {{{/proj/geni-in-a-box.net/exp/<slicename>/tbdata/geni_manifest}}} and the fully qualified name of the node is available in {{{/var/emulab/boot/nickname}}}.  An example of a fully qualified node name is {{{left.myslice.geni-in-a-box.net}}} where {{{myslice}}} is the name of the slice.
 
 
@@ -29 +29 @@
 </node>  
 }}}
-  * '''Aggregate URN in rspec.'''  As you might expect, the aggregate URN in a GENI-in-a-Box rspec will be different from that in a  ProtoGENI rspec.  However, you can use your ProtoGENI rspec, with the URN for a ProtoGENI aggregate, in your GENI-in-a-Box rspec.  The GENI-in-a-Box aggregate manager does not check the aggregate URN in the rspec.  This is a feature and not a bug.  It is so you can use your ProtoGENI rspec with GENI--in-a-Box with very little or no changes.
+  * '''Aggregate URN in rspec.'''  As you might expect, the aggregate URN in a GENI-in-a-Box rspec will be different from that in a  ProtoGENI rspec.  However, you can use your ProtoGENI rspec, with the URN for a ProtoGENI aggregate, in your GENI-in-a-Box rspec.  The GENI-in-a-Box aggregate manager does not check the aggregate URN in the rspec.  This is a feature and not a bug.  It is so you can use your ProtoGENI rspec with GENI-in-a-Box with very little or no changes.
   * '''Running commands as root in startup scripts'''.  The startup script specified by the experimenter as an {{{<execute>}}} element of the request rspec is executed with root privileges in the GENI-in-a-Box aggregate.  You therefore do not require to sudo to run commands that require root privileges.  In fact, such scripts with sudo in them will fail as the VMs are set up to disallow sudo'ing without a tty.