OSOL - OpenSolaris Server based on OpenSolaris 2008.05 - Test Plan

Preparation

Host platform

The tests described here for the OSOL appliance are designed to run on an AppLogic grid. All tests are to be run as a regular Applogic user.

3rd-party tools

None.

Tests Summary

• Verify that the appliance can be started/stopped with varying memory and CPU resources
• Verify that the appliance's terminals are operational
• Verify that the appliance provides a full build environment

Running the Tests

Copy and uncompress the test application archive file osol-tst-app.tar.bz2 on the impex volume. Import the test application test-osol.

This is a diagram of the test harness:

Design

Structure

• an OpenSolaris server srv_sol
• an input gateway in used to verify the in terminal
• a net gateway net used to verify the net terminal
• a monitoring appliance mon used to verify the mon terminal and counters
• a web appliance srv used to verify the out terminal

Test Details

Verify that the appliance can be started/stopped with varying memory and CPU resources

1. Configure the test application with usable network settings.
2. Start the test application with default resources and verify that it starts successfully
   • SSH into the server appliance and execute svcs -vx to verify all services running.
3. Stop the application and configure the server appliance to have minimum CPU and memory resources
4. Start the application and verify that it starts successfully
5. Stop the application and configure the server appliance to have CPU and memory resources greater than the default
6. Start the application and verify that it starts successfully

Verify that the appliance's terminals are all operational

1. default interface
   • verify that you can successfully SSH into the appliance from a 3t shell and can execute various commands - ps, ls, etc.
2. in terminal
   • SSH into the running appliance and configure an SSH public key
   • SSH to the appliance through the IN gateway IP and verify that you end up in the SOL10 appliance.
3. net terminal
   • SSH into the running appliance and verify that you can ping the outside world (e.g., www.google.com)
4. out terminal
   • SSH into the running appliance and verify wget http://out returns the page from srv
5. mon terminal
   • Open the MON GUI from the Editor and verify that all counters are available. All counters should function except for the following, which are continuously zero (unavailable on Solaris):
     • CPU Summary: CPU Nice, CPU Irq, CPU Soft Irq
     • Memory: Active, Inactive, Buffers, Cached, Low Total, Low Used, Low Free, High Total, High Used, High Free, Swap Cached
     • Scheduler: Processes blocked, Processes running
     • Filesystem: Free File Handles, Used File Handles, Allocated File Handles
     • Volume: Time Spent in Reads, Time Spent in Writes
   • Create a view containing CPU usage counter
   • From the running appliance, run a loop that takes 100% of the CPU load and verify that the resulting CPU load is reflected within the MON GUI.

Verify the appliance provides a full build environment

1. Use pkgadd to add a package:
   • wget ftp://ftp.sunfreeware.com/pub/freeware/intel/10/bzip2-1.0.4-sol10-x86-local.gz
   • gunzip bzip2-1.0.4-sol10-x86-local.gz
   • pkgadd -d bzip2-1.0.4-sol10-x86-local
2. Build and install a package from source
   • wget http://www.reverse.net/pub/apache/httpd/httpd-2.2.8.tar.gz
   • gtar -zxf httpd-2.2.8.tar.gz
   • cd httpd-2.2.8
   • ./configure  --prefix=/usr/apache2.2.8
   • make
   • make install

-- StephenQ - 20 Mar 2008