Changes between Version 18 and Version 19 of InstrumentationTools

10/23/09 17:58:42 (13 years ago)



  • InstrumentationTools

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