In principle, the OMII server will run on any modern Linux version or any modern Apple Macintosh version with any Java JDK.
The client will run on any modern Linux or Windows version, any modern Apple Macintosh version (eg. MAC OSX 10.3 or 10.4) with any Java JRE or JDK.
If installing on an Apple Mac, you need to ensure that all the OMII supporting databases are installed on a separate Linux box - this is because the OMII does not support the use of OMII-installed PostgreSQL on the Apple Mac platform at this time. You can install your own PostgreSQL and instructions can be found here for this.
The OMII has a requirement to test its software release across a range of platforms against a number of metrics – successful deployment, functional operation, performance, etc. The NSF Middleware Initiative (NMI) has a similar remit in that it provides pre-compiled software distributions comprised of multiple, potentially interdependent, possibly conflicting, packages. The correct operation and interoperability of these packages has to be verified through deployment and testing. To support this software deployment activity, the NMI have funded the development of a distributed build and testing framework. This framework has been designed and developed by the Condor group at Madison.
The OMII has been collaborating with the Condor NMI group to verify the deployment of OMII releases across multiple platforms.
OMII server install as non-root user; this includes execution of the post-installation tests.
Install OMII proprietary Stress Test Harness; this exercises the OMII Client installer and its post-installation tests.
Perform one iteration of the Stress Test Harness; this involves the Client opening an account on the OMII server and running a job with the Cauchy Horizons application. This exercises the three Integrated services and the Account Service.
Runs tests on Software Component Services ie. WSRF::Lite, OGSA-DAI, Grimoires, PlotWS, FINS, GridSAM.
The following table shows the test results using the NMI framework deployed at OMII in Southampton and the NMI build pool in Madison, Wisconsin, USA. Not all Java environments are available on all platforms. Therefore no attempt is made to validate the OMII release across all combinations. Successful validation using these combinations gives some confidence that all combinations are possible. However, this is not guaranteed.
|
Platform/JDK |
java-1.4.2_04 |
java-1.4.2_05 |
java-1.5.0_01 |
jre-1.5.0_04 |
jdk1.5.0_06 |
jdk1.5.0_07 |
jdk1.5.0_08 |
jdk1.5.0_09 |
|
x86_rhas_4 (Redhat Enterprise Linux AS 4) |
|
|
|
|
|
|
|
|
|
x86_rhes_3 (Redhat Enterprise Linux ES 3) |
|
|
|
|
|
|
|
|
|
x86_suse_9.0 (SUSE 9) |
|
|
|
|
|
|
|
|
|
x86_deb_3.1 (Debian) |
FAIL |
FAIL |
FAIL |
FAIL |
FAIL |
FAIL |
FAIL |
FAIL |
|
x86_suse_10.0 (OpenSuSE 10.0) |
|
|
|
|
|
|
|
|
WSRF::Lite and FINS fail on Debian 3.1 across all Java versions but all other tests pass on 1.4.2_05.
The OMII software undergoes a more rigorous level of quality assurance on certain platforms. This includes use of the NMI testbed, manual regression testing and bug verification and longer running stress tests.
For the OMII_3.2.0 release, the platform which underwent the most rigorous QA evaluation was Redhat Enterprise Linux 4 (RHEL4) running the ext3 filesystem (RHEL4). For previous releases, the chosen platforms were Redhat Enterprise Linux 3 (RHEL3) and SUSE 9.0 on the server and Windows XP sp 2 on the client. There is a high degree of confidence in the quality of the OMII releases on these platforms.
Please note that the OMII has only performed limited testing on 64-bit Linux and none on Redhat 7.2 or SuSE 8.
