Version 2 (modified by, 5 years ago) (diff)


OG-MON-2: GENI Software Configuration Inspection Test

This page captures status for the test case OG-MON-2. For additional information see the Acceptance Test Status - April 2014 page overall status, or the OpenGENI Acceptance Test Plan for details about the planned evaluation.

Step State Notes Tickets
Step 1 Pass
Step 2 Pass

State Legend Description
Pass Test completed and met all criteria
Pass: most criteria Test completed and met most criteria. Exceptions documented
Fail Test completed and failed to meet criteria.
Complete Test completed but will require re-execution due to expected changes
Blocked Blocked by ticketed issue(s).
In Progress Currently under test.

Test Plan Steps

Step 1. Review resource allocation

A site administrator uses available system data sources (process listings, monitoring output, system logs, etc) and/or AM administrative interfaces to determine the configuration of GRAM resources:

  • How many experimental nodes are available for bare metal use, how many are configured as OpenStack containers, and how many are configured as PlanetLab containers
  • What operating system each OpenStack container makes available for experimental VMs.
  • How many unbound VLANs are in the rack's available pool.

A list of experiments and experimenters can be obtained on the control node. Detailed information about the slivers is available in the snapshot files found in /etc/gram/snapshots/gram for current or past experiments.

Also possible to get a list of slivers and how they map to OpenStack Containers. In this example there is only one slice running named "stitchOF":

gram@clemson-clemson-control-1:~$ source /etc/novarc
gram@clemson-clemson-control-1:~$ nova list --all-tenants
| ID                                   | Name    | Status | Networks                                       |
| e4b5ce2c-ea78-4e39-acbe-1157af2e458d | gr-clem | ACTIVE | linkOF=; GRAM-mgmt-net= |
gram@clemson-clemson-control-1:~$ keystone tenant-list
|                id                |                name                | enabled |
| 89a03e397f8b4743be8d6c0c470e9ede |               admin                |   True  |
| 65c073cb3f83446eb400d76013f71bc0 | |   True  |
| 32b79311d95b4483a6d40a6db316fa3f |              service               |   True  |

There are 2 available operating systems that are advertised via the AM API listresources, also the Advertisement passes rspeclint:

        <disk_image description="standard" name="fedora-19" os="Linux" version="19.0"/>      
        <disk_image description="standard" name="ubuntu-12.04" os="Linux" version="12.0"/>      

Step 2. Review OpenFlow resource configuration

A site administrator uses available system data sources to determine the configuration of OpenFlow resources according to VMOC and GRAM.

The VMOC controller service starts the following processes which shows which ports and modules are in use.

gram@clemson-clemson-control-1:~$  ps -eaf|grep pox
gram     11073     1  0 14:15 ?        00:00:05 python2.7 -u -O /opt/pox/ log.level --DEBUG openflow.of_01 --port=9000 vmoc.l2_simple_learning
gram     25680 25972  0 15:34 pts/3    00:00:00 grep --color=auto pox
gram     29867     1  0 14:44 ?        00:00:08 python2.7 -u -O /opt/pox/ log.level --DEBUG vmoc.VMOC --management_port=7001 --default_controller_url=https://localhost:9000

Available VLANs are captured in test case OG-ADM-2 Step 2.