wiki:GIMITestPlan

Version 5 (modified by Jeanne Ohren, 12 years ago) (diff)

--

  1. GIMI Acceptance Test Plan
    1. Process
    2. Assumptions and Dependencies
    3. Aggregate and Service Managers
    4. Experiment control tools
    5. Target resource configurations
      1. 1. One aggregate (RENCI or BBN ExoGENI Rack)
      2. 2. Two aggregates (one slice, both RENCI and BBN ExoGENI Racks)
    6. Target software configurations
      1. 1. Installation
        1. a. Static install (full images)
        2. b. Dynamic install (packages on top of generic images)
      2. 2. Measurement configuration
      3. 3. Add experimenter applications
    7. Extensions
      1. 1. Push measurement data from MC to iRODS server
      2. 2. Pull measurement data from iRODS server to user workspace
      3. 3. Push the analysis data from user workspace to iRODS server
    8. Required services
    9. Test Descriptions
      1. One Aggregate, Common node inside the slice
        1. Static Install
          1. GIM-1A-IS-1. Slice/Sliver Setup
        2. Dynamic Install/Debian
          1. GIM-1A-IS-X. Slice/Sliver Setup
      2. One Aggregate, Common node outside the slice
        1. Static Install
          1. GIM-1A-OS-1. Slice/Sliver Setup
        2. Dynamic Install/Debian
          1. GIM-1A-OS-X. Slice/Sliver Setup

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 Service Manager (SM) requests MUST be made 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.
Compute resources are VMs unless otherwise stated.

Aggregate and Service Managers

ExoSM (Service Manager) BBN ExoGENI Aggregate Manager RENCI ExoGENI Aggregate Manager

Experiment control tools

OMNI

OMF EC

iREEL Portal

iRODS client i-commands

Target resource configurations

1. One aggregate (RENCI or BBN ExoGENI Rack)

  1. Common node in slice, 2 MPs
  1. Common node out of slice, 2 MPs

2. Two aggregates (one slice, both RENCI and BBN ExoGENI Racks)

  1. 1 Common node and 1-2 MPs in each aggregate
  1. Common node outside of slice, 1-2 MPs in each aggregate
  1. Common node in one aggregate, 2 MPs in the other (possible?)
  1. Common node in one aggregate, 1 MP in each (possible?)

Target software configurations

1. Installation

a. Static install (full images)

  • how many different images?
  • with rspec

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

  • which images will be supported?
  • with rspec?

2. Measurement configuration

  • What are the configuration parameters?

3. Add experimenter applications

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

Extensions

1. Push measurement data from MC to iRODS server

2. Pull measurement data from iRODS server to user workspace

  • analyze and visualize the data

3. Push the analysis data from user workspace to iRODS server

Required services

  • OMF Messaging Server
  • iRODS Server
  • iREEL Web Server

Test Descriptions

One Aggregate, Common node inside the slice

Static Install

GIM-1A-IS-1. Slice/Sliver Setup

This test creates a slice on one ExoGENI aggregate with 3 VMs using a static image with GIMI I&M packages installed. One of the VMs will be the common (OML server) node and the other two VMs will be measurement points.

Prerequisites:

  • ExoSM has made available a static image (images?) with GIMI I&M packages installed.
  • The resource allocated for the MC is externally accessible by SSH and HTTP.
  • A messaging (XMPP) server is available and accessible by all nodes in the slice. (Is this required for slice set-up?)

Procedure:

  • Using OMNI, allocate three VMs from the same ExoGENI AM to a slice.
  • Generate and install necessary certificates on the nodes?
  • Enable required services (examples?) on the MC and MP nodes.
  • Verify full connectivity of the slice (ping and ssh)
  • Verify required services have been enabled

Dynamic Install/Debian

GIM-1A-IS-X. Slice/Sliver Setup

This test creates a slice on one ExoGENI aggregate with 3 VMs using a Debian image with GIMI I&M packages installed dynamically. One of the VMs will be the common (OML server) node and the other two VMs will be measurement points.

Prerequisites:

  • ExoSM has made available a Debian image on which to install the GIMI I&M packages.
  • The GIMI I&M packages are available on a public web server?
  • The resource allocated for the MC is externally accessible by SSH and HTTP.
  • A messaging (XMPP) server is available and accessible by all nodes in the slice. (Is this required for slice set-up?)

Procedure:

  • Using OMNI, allocate three VMs from the same ExoGENI AM to a slice.
  • Install the GIMI I&M packages.
  • Generate and install necessary certificates on the nodes?
  • Enable required services (examples?) on the MC and MP nodes.
  • Verify full connectivity of the slice (ping and ssh)
  • Verify required services have been enabled

One Aggregate, Common node outside the slice

Static Install

GIM-1A-OS-1. Slice/Sliver Setup

This test creates a slice on one ExoGENI aggregate with 2 VMs using a static image with GIMI I&M packages installed. Both VMs will be measurement points. The common (OML server) node will be located outside the slice (in the user workspace?).

Prerequisites:

  • ExoSM has made available a static image (images?) with GIMI I&M packages installed.
  • The common node is configured outside the slice and is externally accessible by SSH and HTTP.
  • The common node is accessible by the VMs within the slice (which ports?).
  • A messaging (XMPP) server is available and accessible by all nodes in the slice. (Is this required for slice set-up?)

Procedure:

  • Using OMNI, allocate two VMs from the same ExoGENI AM to a slice.
  • Generate and install necessary certificates on the nodes?
  • Enable required services (examples?) on the MP nodes.
  • Verify full connectivity of the nodes within the slice (ping and ssh) as well as connectivity to the common node outside the slice.
  • Verify required services have been enabled.

Dynamic Install/Debian

GIM-1A-OS-X. Slice/Sliver Setup

This test creates a slice on one ExoGENI aggregate with 2 VMs using a Debian image with GIMI I&M packages installed dynamically. Both VMs will be measurement points. The common (OML server) node will be located outside the slice (in the user workspace?).

Prerequisites:

  • The aggregate/rack has made available a Debian image on which to install the GIMI I&M packages.
  • The GIMI I&M packages are available on a public web server?
  • The common node is configured outside the slice and is externally accessible by SSH and HTTP.
  • The common node is accessible by the VMs within the slice (which ports?).
  • A messaging (XMPP) server is available and accessible by all nodes in the slice. (Is this required for slice set-up?)

Procedure:

  • Using OMNI, allocate two VMs from the same ExoGENI AM to a slice.
  • Install the GIMI I&M packages.
  • Generate and install necessary certificates on the nodes?
  • Enable required services (examples?) on the MC and MP nodes.
  • Verify full connectivity of the nodes within the slice (ping and ssh) as well as connectivity to the common node outside the slice
  • Verify required services have been enabled.