Changes between Initial Version and Version 1 of KentuckyAggregate

09/27/11 12:17:57 (11 years ago)



  • KentuckyAggregate

    v1 v1  
     3== The Kentucky Aggregate ==
     5[[Image(fig2low.jpg, 21%)]]
     6[[Image(fig1low.jpg, 25%)]]
     8An initial version of the Kentucky aggregate is up and running and was
     9demonstrated working with the Utah clearinghouse and the Utah aggregate at the
     10GEC 4 meeting.  The Kentucky aggregate consists of 79 Dell PCs.  Of the 79
     11machines, 47 are Dell Optiplex GX240 available for general use,
     12and 24 are Dell Inspiron 530 machines which are currently
     13reserved for work on the InstrumentationTools Project.
     14An additional 8 Dell Poweredge 1900 machines were recently added to the list of
     15available machines and are being used for student class projects.
     16All machines have 4 experimental network interfaces that can be configured
     17via the Emulab web interface to produce the desired topology, bandwidth,
     18delay, etc.
     20=== Accessing The Kentucky Aggregate ===
     22The Kentucky [wiki:ProtoGENI] aggregate can be accessed by obtaining
     23an account at one of the [wiki:ProtoGENI] aggregates.  The preferred way to
     24gain access to [wiki:ProtoGENI] is to obtain an account on the Utah aggregate at
     25[].  Access to the Utah aggregate will also enable access
     26to the Kentucky aggregate.  However, users who plan to primarily use
     27resources on the Kentucky aggregate may apply for an account at the Kentucky
     28site [] directly.
     30Once this account is created, a user who wishes to access [wiki:ProtoGENI] resources
     31should create a personal key that will be used to authenticate them to
     32[wiki:ProtoGENI].  Key creation is described under "Getting Ready" on the [wiki:ProtoGENI]
     33wiki ([]).  In short, the
     34new user must login to their Emulab account and following the
     35"My Emulab->Profile->Generate SSL Cert" links to create a unique certificate.
     36After giving a secure pass-phrase, your certificates will be generated and
     37saved in $HOME/.ssl/encrypted.pem.  These credentials can be used to access
     38any of the [wiki:ProtoGENI] aggregates (including the Kentucky aggregate).
     40Because [wiki:ProtoGENI] is still in the early development stages, the interface
     41used to obtain resources is rather primitive.  To obtain resources
     42users must write a python script that make calls to the [wiki:ProtoGENI] API.
     43A few test scripts are available as examples.  The [wiki:ProtoGENI] API is
     44described at,
     45and can be used to create slices, slivers, and boot those slivers.
     46Resources are specified via an rspec which is an XML formatted specification
     47of the PCs and links required by the experiment.  More information about
     48Rspecs can be found at []
     50Additional information about using [wiki:ProtoGENI] can be found at