wiki:GEMINIAcceptanceTests/GEMINITest8.22.2012

Version 4 (modified by Jeanne Ohren, 7 years ago) (diff)

--

GEMINI Testing executed on 8/22/2012


Status of All Tests


Color(green, Pass)? Color(yellow, Provisionally Pass)?

Step Status Open Tickets
1. Establish test/experiment environment
2. Obtain slice of GENI resources, install and configure GEMINI I&M tools
3. Run and orchestrate GEMINI I&M tools and reference/actual experiment
4. Observe I&M measurement results on GEMINI presentation service
5. Push I&M measurement and analysis results to iRODS archive service
6. Release resources, and cleanup

1. Establish test/experiment environment

Color(pink,Insert image here)?

User Workspace

  • Using the GEC14 Tutorial VM
  • Inputs:
    • GENI certificate
      • Two formats: PEM and PKC12
      • installed in $HOME/.ssl
      • location of PEM file configured in omni_config
      • stripped the passphrase for automation
      • created the password file to be used by instrumentize.py
    • SSH key pair
      • installed in $HOME/.ssh
      • location configured in omni_config
      • key added to ssh-agent
    • iRODS account
      • username configured in $HOME/.irods/.irodsEnv
      • password stored using iinit
  • All credentials configured using credconfig.sh script
  • GENI pkc12 certificate installed in the Firefox browser
  • Outputs:
    • omni.py ready to use
    • i-commands ready to use
    • ready to log into nodes in the slice

iRODS server

  • irodswes.netlab.uky.edu

UNIS server

LAMP CA

2. Obtain slice of GENI resources, install and configure GEMINI I&M tools

  • Used omni to create the slice and the sliver on UKY Protogeni aggregate
    • Rspec includes an execute service for each node that downloads phoebus_install.sh from a web server and runs it to install the phoebus software for the reference experiment
    • Made sure I could ssh in to all of the nodes without a password
  • Run instrumentize.py to install and configure GEMINI tools on the nodes in the slice
  • Inputs:
  • Output:
    • slice manifest
    • slice login information
    • portal username and password
    • all nodes are ready to run the experiment
      • phoebus installed
      • GEMINI tools installed
      • able to log into the GEMINI portal

Color(pink,Insert picture of portal)?

3. Run and orchestrate GEMINI I&M tools and reference/actual experiment

Configure active measurements

The tutorial directs me to configure one-way (OWAMP) and round-trip (Ping) latency regular tests according to the following diagram.

  • Accessed psConfig UI

Image

  • Enabled services on pca, pcb, and pcc and pushed configuration to UNIS

Image

  • Configured regular active measurements according to diagram (above) and pushed configuration to UNIS

Image

  • Applied configuration to the nodes

Image

Execute the reference experiment

  • Started the iperf server on PCC
    [johren@PCC ~]$ iperf -s
    ------------------------------------------------------------
    Server listening on TCP port 5001
    TCP window size: 85.3 KByte (default)
    ------------------------------------------------------------
    
  • Started the iperf client on PCA
    [johren@PCA ~]$ iperf -c pcc -t 120 -i 12
    
  • Started the Phoebus gateway on PCB
    [johren@PCB ~]$ sudo /etc/init.d/phoebus start
    [johren@PCB ~]$ tail -f /var/log/phoebus.log
    
  • Introduced network impairments
    • For this step I had to create an SSH key pair for user johren and install them in ~/.ssh/authorized_keys on PCA and PCB
    • I also had to set the SSH config in ~/.ssh/config to use the new private key when contacting these hosts:
      Host PCA
         IdentityFile ~/.ssh/phoebus
      Host PCB
         IdentityFile ~/.ssh/phoebus
      
    • I then ran the "user" version of the setup_netem script
      [johren@PCA ~]$ sh /tmp/setup_netem_user.sh
      Setting PCA->PCB link to 5ms latency and .01% loss
      Setting PCB->PCC link to 50ms latency and no loss
      done
      
  • Again, ran the iperf client on PCA
  • Enabled phoebus gateway on PCB
    [johren@PCA ~]$ setenv LD_PRELOAD /usr/lib64/libxsp_phoebuswrapper.so
    [johren@PCA ~]$ setenv XSP_PATH pcb/5006
    

Color(pink, Insert picture of log here)?

  • Again, ran the iperf client on PCA
  • Stopped phoebus service on PCB and iperf server on PCC
    [johren@PCB ~]$ sudo /etc/init.d/phoebus stop
    

4. Observe I&M measurement results on GEMINI presentation service

Observe passive measurements

Observe sidebar graphs for each node

  • For each node (PCA, PCB, PCC)...
    • click on node in Map view

Color(pink,Insert image here)?

  • select graphs individually and make graphs show up on the left

Color(pink,Insert image here)?

  • select All Graphs and make sure all graphs show up in separate tab

Color(pink,Insert image here)?

  • Select VNC and make sure I can log in to the node

Color(pink,Insert image here)?

  • Access the Passive UI on MC node
  • For each node (PCA, PCB, PCC)...
    • View all graphs
    • View all tables (compare to command line results; ifconfig, arp, lsmod, etc.)

Color(pink,Insert image here)?

Observe active measurements

  • Inputs:
    • None
  • Outputs:
    • Graphs and tables viewable in the GEMINI portal

5. Push I&M measurement and analysis results to iRODS archive service

  • Go to archive section of GEMINI portal
    • NOTE: It requires me to log in again when I click on the Archive button

Color(pink,Insert image here)?

  • Enter iRODS login information and select "Archive to iRODS"

Color(pink,Insert image here)?

  • Click on "View IRODS Archive" and log into iRODS UI

Color(pink,Insert image here)?

  • Find the set of data that was just pushed and view some of the graphs and table

Color(pink,Insert image here)?

  • Inputs:
    • graphs, tables, databases, manifest from experiment
  • Outputs:
    • images and data viewable in iRODS

6. Release resources, and cleanup

  • Used omni to delete the sliver
    geniuser@UserWorkspace:~/Tutorials/GEMINI/common$ omni.py -a pg-ky deletesliver johGEM1208221147
    INFO:omni:Loading config file /home/geniuser/.gcf/omni_config
    INFO:omni:Using control framework pg
    INFO:omni:Substituting AM nickname pg-ky with URL https://www.uky.emulab.net/protogeni/xmlrpc/am, URN unspecified_AM_URN
    INFO:omni:Deleted sliver urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+johGEM1208221147 on unspecified_AM_URN at https://www.uky.emulab.net/protogeni/xmlrpc/am
    INFO:omni: ------------------------------------------------------------
    INFO:omni: Completed deletesliver:
    
      Options as run:
            aggregate: pg-ky
            framework: pg
            native: True
    
      Args: deletesliver johGEM1208221147
    
      Result Summary: Deleted sliver urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+johGEM1208221147 on unspecified_AM_URN at https://www.uky.emulab.net/protogeni/xmlrpc/am
    INFO:omni: ============================================================
    
  • Inputs:
    • slice name
  • Outputs:
    • sliver has been deleted

Attachments (18)