GIMI Acceptance Test Plan

The GIMI tests will build on the GPO ​ExoGENI test plan.

Process

1. Select aggregate manager
2. Select target resource configuration
3. Select target software configuration
4. Select tools
5. Select extension
6. Run scripts
   1. get resources
   2. load software
   3. configure software
   4. test functions
   5. evaluate performance

Assumptions and Dependencies

The following assumptions are made for all tests described in this plan:

GPO ProtoGENI credentials from ​https://pgeni.gpolab.bbn.com are used for all tests.
GPO ProtoGENI is the Slice Authority for all tests.
All Aggregate Manager requests MUST be made via the Omni command line tool which uses the GENI AM API.
In all scenarios, one experiment is always equal to one slice.

Aggregate Managers

TBD

Experiment control tools

OMNI

Gush

UNIS tools (sendmanifest, getcertificate, etc.)

Portal?

Target resource configurations

[Add diagrams]

1. One aggregate (Utah?)

1. 3 raw PCs (1 MC, 2 MP)

2. 1 raw PC (MC) + 2VMs (MPs)

3. 3 VMs (1 MC, 2MPs)

4. More MPs?

2. Two aggregates (one slice)

1. Common node in one aggregate, 2 MPs in the other (possible?)

2. Common node in one aggregate, 1 MP in each (possible?)

3. 1 Common node and 1-2 MPs in each aggregate

Target software configurations

1. Static install (full images)

• with rspec

2. Dynamic install (packages on top of generic images)

• with Gush
• with rspec?

3. Add experimenter applications

• use OMF EC enable/disable app and I&M services

Extensions

Required services

• OMF Messaging Server
• iRODS Server
• iREEL Web Server

Test Descriptions

XXX Acceptance Tests

GIM-XX-1. Title

Description

Prerequisites:

Procedure: