wiki:GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-MON-2

Version 9 (modified by lnevers@bbn.com, 6 years ago) (diff)

--

Detailed test plan for IG-MON-2: GENI Software Configuration Inspection Test

This page captures status for the test case IG-MON-2, which verifies the ability to determine software configuration in the InstaGENI racks. For overall status see the InstaGENI Acceptance Test Status page.

Last update: 2013-03-05

Test Status

Step State Tickets Notes
1 Color(green,Pass)?
2 ready to test now that OpenFlow and shared VLANs are available
3 ready to test now that FOAM is available
4 ready to test now that FOAM is available


State Legend Description
Color(green,Pass)? Test completed and met all criteria
Color(#98FB98,Pass: most criteria)? Test completed and met most criteria. Exceptions documented
Color(red,Fail)? Test completed and failed to meet criteria.
Color(yellow,Complete)? Test completed but will require re-execution due to expected changes
Color(orange,Blocked)? Blocked by ticketed issue(s).
Color(#63B8FF,In Progress)? Currently under test.


Test Plan Steps

Step 1: determine experimental node allocations

This step will verify the ability to determine VM in use as well as VMs available as follows:

  • On boss and ops, use available system data sources (process listings, monitoring output, system logs, etc) and/or AM administrative interfaces (Emulab UI, testbed database) to determine the experimental state of each node.
  • For each OpenVZ node found, determine what operating system that node makes available to users.

As a site admin login to https://boss.instageni.gpolab.bbn.com, select "red dot" mode and select pulldown "Experimentation"->"Node Status", which will show this page:

[Image(IG-MON-2-nodes.jpg)]].

On the resulting page select "physical" from the tabular view listing across the top of the panel. This will show all physical systems in the rack, along with the OS running on those nodes.

The above shows:

  • pc3 is in used by an experiment (EID) named "jbstmp"
  • pc4 and pc5 are available
  • pc1 and pc2 are part of the "shared-nodes" experiment used to reserve the PCs that provide VMs.

To determine what VMs are in use, while still in the Experimentation"->"Node Status" page (in red dot mode) select "virtual" from the tabular view across the top of the panel, which will provide a list of VMs in use in the rack:

If further information is needed for any of the VMs on the "virtual" table, simply click on the VM "ID" and all VM information will be shown.

Step 2: determine rack VLAN configuration

Using:

  • On boss and ops, use available data sources to determine how many VLANs on the experimental switch are available for experimenters to use
  • For each available experimental VLAN, determine whether it is available for exclusive OpenFlow control
  • Determine what bound VLANs are available for use

Verify:

  • The site administrator can determine how many unbound VLANs are available for use
  • The site administrator can determine which VLANs InstaGENI is able to configure for OpenFlow use
  • The site administrator can determine what bound VLANs are available for use

Results of testing step 2: 2012-05-28

  • On boss, use the database to find out the set of VLANs which can be used for dedicated experiments:
    boss,[~],12:19(0)$ mysql tbdb
    mysql> select stack_id,min_vlan,max_vlan,leader from switch_stack_types;
    +------------+----------+----------+-----------+
    | stack_id   | min_vlan | max_vlan | leader    |
    +------------+----------+----------+-----------+
    | Control    |      128 |      256 | procurve1 | 
    | Experiment |      257 |      999 | procurve2 | 
    +------------+----------+----------+-----------+
    2 rows in set (0.00 sec)
    
  • I am confused by this, because, looking at procurve1:
    ProCurve Switch 2610-24# show vlans 
    ...
      VLAN ID Name                             | Status     Voice Jumbo
      ------- -------------------------------- + ---------- ----- -----
      1       DEFAULT_VLAN                     | Port-based No    No   
      257     _42                              | Port-based No    No   
      260     _44                              | Port-based No    No   
    
    Why are VLANs in the experimental range on the control switch? Incidentally, the mac-address table doesn't show any VLANs in that range, but i am confused by this.
  • I went ahead and created a sliver containing two virtual nodes and a virtual LAN:
    omni -a http://www.utah.geniracks.net/protogeni/xmlrpc/am createsliver ecgtest2 ~/omni/rspecs/request/rack-testing/acceptance-tests/IG-MON-nodes-C.rspec
    
  • That did not generate any additional VLANs on the control switch. I can't experiment with a physical node because there aren't any free right now.

Anyway, i also can't look into OpenFlow options because that's not implemented yet.

I have an open question on the list about bound VLANs, and i'm blocked on that to look into bound VLANs.

Step 3: determine which GENI SAs are trusted by InstaGENI AM

Using:

  • On boss, use available system data sources and/or AM administrative interfaces to determine which GENI slice authorities the InstaGENI AM trusts.
  • On foam, use available system data sources and/or AM administrative interfaces to determine which GENI slice authorities the FOAM AM trusts.
  • Use the GENI AM API to verify that the BBN and Utah InstaGENI AMs trust the pgeni.gpolab.bbn.com SA.
  • Use the GENI AM API to verify that the BBN and Utah FOAM AMs trusts the pgeni.gpolab.bbn.com SA.

Verify:

  • The site administrator can determine the full set of trusted GENI slice authorities on the local rack.
  • An experimenter can verify that the four AMs to be used in the test trust the pgeni.gpolab.bbn.com SA.

Step 4: determine rack OpenFlow state

Using:

  • From a login to the dataplane switch, view the OpenFlow configuration.
  • On flowvisor, use fvctl to view the set of devices reporting to the FlowVisor
  • Use the GENI AM API to view the set of datapaths advertised by FOAM
  • On boss or ops, use available system or AM tools to determine the configuration which the InstaGENI AM will use to install OpenFlow configuration on the switch and share it with FOAM

Verify:

  • All datapaths on the rack switch report either to FlowVisor or directly to experimental controllers
  • All datapaths on the rack switch which are shared with FlowVisor are advertised by FOAM
  • All datapaths reporting to FlowVisor or to FOAM come from the rack switch
  • A site administrator can look at flowvisor's state using fvctl
  • A site administrator can look at FOAM's state using foamctl
  • A site administrator can look at InstaGENI's OpenFlow configuration

Attachments (3)

Download all attachments as: .zip