1 | Based on GEMINI design review on 5/7 and 5/8, the GEMINI plan to produce v1.0 between now and GEC14 is this:
|
---|
2 |
|
---|
3 | a) Focus on GEMINI tools that include primarily existing LAMP and INSTOOLS modules, to provide (respectively) active network and passive host measurements.
|
---|
4 |
|
---|
5 | b) Postpone the testing and integration of the new GEMINI architecture until after GEC14 (since there is no chance that it could be useful by GEC14); complete and integrate it later, at a time TBD.
|
---|
6 |
|
---|
7 | c) Focus on target aggregates including protoGENI sites (e.g., Utah) and InstaGENI racks.
|
---|
8 |
|
---|
9 | d) Use the GENI AM API and ssh as the principal interfaces to the aggregates
|
---|
10 |
|
---|
11 | e) Use OMNI to drive the GENI AM API, and write scripts to install software packages and configure the tools, where the scripts will run in the defined user workspace.
|
---|
12 |
|
---|
13 | f) Include these operational services: Old UNIS (Delaware to IU); LAMP CA (Delaware to IU); Portal (UK); iRODS (UK)
|
---|
14 |
|
---|
15 | g) Integrate tools so that user can ask for active network and/or passive host measurements, in a unified manner.
|
---|
16 |
|
---|
17 | h) Aim for providing usable tools to users, to be presented in a tutorial at GEC14. (content of tutorial TBD)
|
---|