Version 3 (modified by, 9 years ago) (diff)


GEMINI v1.1 Definition

Based on GEMINI design reviews on 9/28 and 10/5, the GEMINI release v1.1 to be released at GEC15 is defined to include:

a) Continue to support GEMINI tools in v1.0 that are based on LAMP and INSTOOLS modules, to provide (respectively) active network and passive host measurements.

b) Introduce the new GEMINI architecture with the BLiPP Measurement Point and the Measurement Store (MS) modules, to provide an alternate way to gather passive host measurements.

c) Use the current rspec extension approach to load and enable tools on nodes: active network measurements (Lamp modules), Type-1 passive host measurements (INSTOOLS modules) and Type-2 passive host measurements (BLiPP and MS modules).

d) Use Periscope installed on GN to observe Type-2 passive host measurements.

e) Include NewUNIS operational service (IU) for use with BLiPP and MS modules; retain OldUNIS operational service (IU) to support legacy modules; modify instrumentation script to push configuration data to both OldUNIS and NewUNIS.

f) Introduce flexible Authentication and Authorization (AA) modules between new modules (BLiPP and MS) and NewUNIS.

g) Modify GEMINI Portal to display data from all modules, and to utilize NewUNIS for storing configuration data.

h) Support these operational services: NewUNIS (IU); OldUNIS (IU); ProxyCertGenerator (IU); LAMP CA (IU); GEMINI Portal (UK); iRODS (UK)

c) Focus on target aggregates including protoGENI sites (e.g., Utah) and InstaGENI racks.

d) Use the GENI AM API and ssh as the principal interfaces to the aggregates

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”.

f) g) Integrate tools so that user can ask for active network and/or passive host measurements, in a unified manner.

h) Aim for “providing usable tools” to users, to be presented in a tutorial at GEC14. (content of tutorial TBD)