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