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