Inca test review

From TeraGrid Wiki

Jump to: navigation, search

Contents

[edit]

Remote Login

Rick Mohr

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
ctss-login-registration-4.0.2
ctss-login-4.0.2-registration Y Y N
gsi-openssh-4.0.2
version: >= 3.9 Y Y N
gsissh-unit-rl-4.0.2 Y Y N This checks a user's ability to gsissh into a resource using a certificate.
NEED: Multi-hop gsissh Kit contains use case where user logs into resource, and then logs into another resource without authenticating again. [Recommended test: Use gsissh-unit-rl test as a basis for multi-hop test. After first successful login, gsissh to second host. It might be best if the second host was the same as the first so that other external factors (like network failures, outage at second site, etc.) do not come into play. Perhaps this test and the gsissh-unit-rl test can be combined into a single test that checks both cases.]
NEED: gsi-scp test Kit mentions that scp should be available to users. Test should check that scp works using GSI authentication. [Recommended test: Copy small file to site and verify that it transfered correctly. gsissh-unit-rl test uses gsissh to authenticate and then execute a command. Perhaps this test could be modified to copy a file instead of executing a command.]
gx-map-4.0.2
version: 0.5.3.3|0.5.3.2p1 Y Y N Checks that gx-map has been updated (earlier versions had security issue).
myproxy-4.0.2
version: >= 3.4 Y Y N
NEED: myproxy client commands Need a test to verify that basic myproxy commands work as intended. [Recommended test: Testing myproxy-logon is probably the most important one, but maybe testing myproxy-info would be worthwhile too.] (Kate added test 12/3/09)
softenv-4.0.2
version: >= 1.6.2 N N It is my understanding that modules will become the standard package for environment mangament, so softenv will eventually be unnecessary. Of course, that means equivalent tests for modules need to be deployed.
softenv-unit-rl-4.0.2 N N Will need to be replaced by equivalent test for modules. Kit implementation states that "teragrid-basic" macro should be defined, but this test looks for "teragrid" macro. In any case, we need to decide whether we want to only test for macro, or for the individual components included by macro. [Recommended test: The equivalent modules test would probably be something like "module load teragrid-basic" (assuming that there is a module by that name installed at the site).]
tgusage-4.0.2
version: >= 2.9 Y Y Kate updated version in kit implementation page
tgusage-unit-rl-4.0.2 Y Y N
uberftp-4.0.2
version: >= 1.18 Y Y N
NEED: Functionality test There needs to be a test which can check the basic functionality of the uberftp command. However, this could be tricky. Testing it would require accessing a GridFTP server, and if the test failed, there would have to be a way to distinguish failures of uberftp from failures of the remote GridFTP server, network failures, etc.
tgproxy-4.0.2
COMMENT Even though this component is listed as a required part of the kit, it assumes that the set-user-proxy script will be invoked via softenv. Not all RPs have softenv installed, and even if it is installed, tgproxy is not part of the default softenv environment. It also looks as though softenv will be replaced by modules.
tgproxy-unit-rl-4.0.2 Y N Y This test checks that X509_USER_PROXY environment variable does not start with "/tmp". However, it implicitly assumes that set-user-proxy command has been run, which may not be true. Also, the purpose of the script is to relocate the proxy to $HOME/.globus/userproxy.pem. Simply checking that the proxy doesn't reside in /tmp does not verify that the script worked as it should. [Recommended test: Test that set-user-proxy will actually move a proxy cert to new location. One possible way might be to: 1) Create file with fake proxy and set env variable X509_USER_PROXY to this file path, 2) set env variable HOME to some temp path for testing, 3) run set-user-proxy script, 4) verify that $HOME/.globus directory gets created, 5) verify that fake proxy gets moved to $HOME/.globus/userproxy.pem, 6) verify that script prints $HOME/.globus/userproxy.pem to stdout.] -- Rick: Kate revised the test 12/2/09
NEED: version >= 0.9.1 If we are going to test tgproxy, we probably want to enforce minimum version number like other components. [Recommended test: I don't know how to test for the version. The set-user-proxy script doesn't seem to have a --version option. Maybe ask JP how to do this.]
NEED: tgpolicy
COMMENT No tests exist for tg-policy package although it is listed as a required component of kit.
NEED: version >= 0.2 Enforce minimum version number like other components. [Recommended test: Run "tg-policy -v" and parse out version number.] (Kate added test 12/3/09)
NEED: Policy existence Test that all three policies (data, sched, fs) are defined. [Recommended test: Run "tg-policy -data", "tg-policy -sched", and "tg-policy -fs" and look for non-empty output.] (Kate added test 12/3/09)
[edit]

Application Development & Runtime Support

Lukasz Lacinski

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
ctss-app-support-registration-4.2.0
ctss-app-support-registration-4.2.0 Y Y N
Ant (optional) Optional but also a pre-requisite of required Globus Clients and Libraries.
version: 1.6.5 Y Y N
ant-unit-as-4.2.0 Y Y N
BLAS (optional) RPs usually register several implementations of BLAS routines (atlas, mkl). Lukasz: shouldn't Inca test all of them to say that a particular RP provides registered BLAS routines properly?
blas-level1-as-4.2.0 Y Y
blas-level2-as-4.2.0 Y Y
blas-level3-as-4.2.0 Y Y
C, C++, Fortran Compilers Currently there are tests for gnu, ibm and intel. Do we need to test other compilers like compaq, pgi, hp, sun, upc which may be registered by RPs? Only pgi is installed/registered on Ranger and Queen Bee.
version: any Y Y N
compiler-gnu-c-as-4.2.0 Y Y N
compiler-gnu-c++-as-4.2.0 Y Y N
compiler-gnu-fortran-as-4.2.0 Y Y N
compiler-ibm-c-as-4.2.0 Y Y N
compiler-ibm-c++-as-4.2.0 Y Y N
compiler-ibm-fortran-as-4.2.0 Y Y N
compiler-intel-c-as-4.2.0 Y Y N
compiler-intel-c++-as-4.2.0 Y Y N
compiler-intel-fortran-as-4.2.0 Y Y N
PGI Compiler
version: any There is no Inca test for PGI. [Recommended test: execute "pgc -version" and parse the stdout.]
compiler-pgi-c-as-4.2.0 The same test as for gnu, ibm, intel should work for pgi. PGI C Compiler is "pgcc".
compiler-pgi-c++-as-4.2.0 As above. PGI C++ Compiler is "pgCC".
compiler-pgi-fortran-as-4.2.0 As above. PGI Fortran Compiler is "pgf77".
Globus Clients and Libraries MyProxy and GSI OpenSSH clients are tested in the Remote Login Kit. There is no sense to test libraries because the TG Globus Clients and Libraries package is incomplete from the developer point of view.
grid-proxy-init-patched-as-4.2.0 Y Y N
GNU Make (optional)
NO TEST There is no Inca gnu-make test. Has to be written. [Recommended version test: execute "make -version" and parse the stdout to look for "GNU Make .*"]
GUR (optional)
gur-unit-4.2.0 Y Y N
HDF4 (optional)
version: any Y Y N It executes the hdp to check version only.
HDF5 (optional)
version: any Y Y N It executes the h5dump to check version only.
Java (optional) Optional but also a pre-requisite of required Globus Clients and Libraries.
version: >= 1.4.2_11 Y Y N
java-unit-as-4.2.0 Y Y N
MCP (optional)
mcp-unit-4.2.0 Y Y N
Modules (optional)
NO TEST There is no Inca Modules test. Has to be written. [Recommended test: execute "module help" and parse the stderr. It doesn't work on Ranger. Ranger uses a softenv wrapper which is incompatible and implements only limited functionality of the original Modules. For Ranger an Inca test could execute "modules" and parse stdout.]
Python (optional)
version: >= 2.2 Y Y N The minimum required version could be increased to 2.5.x. The SAGA package requiring at least Python 2.5.x is coming.
python-unit-as- 4.2.0 Y Y RPs' installations (excluding Python coming with OS) are sometimes incomplete. At least shared libraries should be checked also.
Softenv
version: >= 1.6.2 Y Y N
softenv-unit-as-4.2.0 Y Y N
SRB Client (optional)
version: >= 3.4.1 Y Y N
sput-sget-as-4.2.0 Y Y N
sls-as-4.2.0 N sput-sget-as-4.2.0 already does the same things and additionally several others.
Tcl (optional)
version: 8.* Y Y N
tcl-unit-as-4.2.0 Y Y N
TGCP (optional)
version: 1.0.0 Y Y N
NO TEST There is no Inca test checking real functionality of the TGCP. TGCP is a script tool using globus-url-copy and rtf which are tested in other kits. TGCP configuration should be adjusted after every update of TG Globus Clients and Libraries package. It seems that RPs don't do it. So an additional Inca test is needed.
tginfo
NO TEST Inca test is definitely required. [Recommended version test: execute "tginfo" and parse the stdout - first line: "TeraGrid Information Services Discovery Client (Version 1.0.2, Release r2)". ** Note: Kate added test from JP 12/13/09]
[edit]

Parallel Application Support

Lukasz Lacinski and Mike Lowe

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
ctss-parallel-app-registration-4.0.1
ctss-parallel-app-registration-4.0.1 Y Y N
The following MPI implementations are mentioned in Parallel Application Support Implementation and installed (registaered) on several TG machines. NO TESTS JML: suggested tests 'for every key registered, clear environment, check output of which mpicc and which mpirun, success on output' 'for each key compile very small mpi hello world and run'
bglmpi Frost
champion-pro
hpmpi
mpich2
mpich-mx BigRed
mpich-gm
mpich-p4 NSTG
mvapich QueenBee, Lonestar
mvapich2 QueenBee, Ranger
ppe-poe
sgimpt
sunmpi
xt-mp BigBen
[edit]

Science Gateway

Rick Mohr

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
ctss-science-gateway-4.2.0-registration
ctss-science-gateway-4.2.0-registration Y Y N
globus-wsrf-sg-4.2.0 The science gateway kit adds functionality to the remote compute kit. (roughly speaking, science gateway kit = remote compute kit + gridshib + commsh). Components like wsrf, ws-gram, prews-gram, ogsa-dai, and tg-audit-config are listed in both kits. These components can still be monitored under the category of science gateway, but the Inca tests should be the same ones that are used to monitor the remote compute kit. This will ensure that tests for the two kits do not diverge. Therefore, the Inca tests for the science gateway kit should focus only on the extra functionality provided by the kit. Tests which overlap with the remote compute kit will be refered to that kit.

[Update: It seems that ogsa-dai and tg-audit-config have been removed from the remote compute kit and now reside only in the science gateway kit. --Rick]

wsrf-query-mds-sg-4.2.0 See Remote Compute Kit (wsrf-query-mds-rc-4.2.0)
wsrf-query-mds-auth-JobsRP-sg-4.2.0 See Remote Compute Kit (wsrf-query-mds-auth-JobsRP-rc-4.2.0)
wsrf-query-mds-auth-JobsRP-cache-sg-4.2.0 See Remote Compute Kit (wsrf-query-mds-auth-JobsRP-rc-4.2.0)
wsrf-query-mds-auth-LoadRP-sg-4.2.0 See Remote Compute Kit (wsrf-query-mds-auth-LoadRP-rc-4.2.0)
wsrf-query-mds-auth-LoadRP-cache-sg-4.2.0 See Remote Compute Kit (wsrf-query-mds-auth-LoadRP-cache-rc-4.2.0)
COMMENT Any wsrf tests from the remote compute kit which are not included above should be considered for addition.
gridshib-gt-sg-4.2.0
gridshib-unit-4.2.0 Y Y N Checks the gateway entityId <=> x509 DN mapping
COMMENT The kit definition contains use cases for blocking gateway access based on client IP or user attributes. I am not sure if/how this could be tested in Inca.
ogsa-dai-sg-4.0.2 Note: OGSA-DAI has been removed from the remote compute kit.
ogsadai-account-sg-4.2.0 Y Y N This is one of the tests recommended in the OGSA-DAI configuration README.
ogsadai-audit-sg-4.2.0 Y Y N This is one of the tests recommended in the OGSA-DAI configuration README.
prews-gram-sg-4.2.0 See comment for globus-wsrf-sg.
prews-gram-fork-sg-4.2.0 See Remote Compute Kit (prews-gram-fork-rc-4.2.0)
prews-gram-batch-sg-4.2.0 See Remote Compute Kit (prews-gram-batch-rc-4.2.0)
COMMENT Any prews-gram tests from the remote compute kit which are not included above should be considered for addition.
wsgram-sg-4.2.0 See comment for globus-wsrf-sg.
wsgram-fork-sg-4.2.0 See Remote Compute Kit (wsgram-fork-rc-4.2.0)
wsgram-batch-sg-4.2.0 See Remote Compute Kit (wsgram-batch-rc-4.2.0)
COMMENT Any wsgram tests from the remote compute kit which are not included above should be considered for addition.
NEED(?): commsh commsh is used to restrict which commands can be invoked by a community account. Since this is an optional component, I am not sure if it should be included in the standard set of tests or not. (Is there any policy in place on how Inca handles testing of optional software?)
NEED: version >= 0.1.4 The kit implementation does not list a specific version number for commsh, but the last version I saw mentioned on the software-wg mailing list was 0.1.4 [12/8/09 Kate wrote reporter to run "commsh --version" and parse out version number.]
COMMENT It would be nice to test "commsh --check-user" since this is the command used by the globus-job-manager script. Unfortunately, commsh does not provide an option for specifying an alternate configuration file. Without that, I cannot think of a way to test commsh's ability to restrict commands. (Note: no RPs have this package registered yet. --Kate)
NEED: tg-audit-config Science gateway kit relies on GRAM auditing for accounting purposes just like the remote compute kit.

12/7/09 from Eric Blau: I don't believe that OGSA-DAI is running on tg-grid.uc.teragrid.org any longer (if such a machine still even exists). However, if you have an ogsa-dai configuration as shown at

http://software.teragrid.org/pacman/ctss4/globus-wsrf/wsrf-ogsadai-config/wsrf-ogsadai-config-1.1.0-r3/README.install.html

the configuration is very similar to that from the wiki page you referenced, and some example tests are given in the install/configuration instructions. This ogsa-dai configuration was part of the Remote Compute 4.0.2 kit, but was moved out of the remote compute kit before 4.2.0, and into the Science Gateways kit.

I do not know offhand of a good existing test that tests the TG GRAM Audit capability directly, instead of testing it through ogsa-dai.

[Update: It doesn't look like tg-audit-config can be tested directly, so we will have to rely on the ogsa-dai tests. --Rick]

[edit]

Science Workflow Support

Rick Mohr

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
ctss-workflow-registration
ctss-workflow-4.2.0-registration Y Y N
condor Two components of condor are used for science workflow: Condor-G and DAGMan.
version >= 6.7.18 Y Y Y Kit implementation lists version >= 7.0.1
NEED: DAGMan functionality Should check that DAGMan is supported. We don't want to actually run condor jobs, but we can at least run "condor_submit_dag -version". Maybe it would be possible to run "condor_submit_dag -no_submit <DAG_file>" and check that a condor submit description gets generated?
condor-g There is not really a distinction between condor and condor-g, so these tests should be moved to the condor section.
version >= 6.7.18 N N The condor version is already tested.
condorg-condorq-sws-4.2.0 Y Y Y Checks that condor_q command runs without errors. The condor README.install also mentions running condor_status and making sure it returns without error. This could be added as a separate test, but maybe it would just be easier to add it in with the condor_q command. [Move to condor section.]
MyCluster/GridShell I don't see an easy way to test MyCluster without trying to create a virtual cluster, and I don't think this is something we want to do in an Inca test. The only thing to test is if the tool is installed, and this is accomplished by the version test below.
version >= 0.9.9-4 Y Y N
[edit]

Data Movement

Derek Simmel

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
CLIENTS
registration ctss-data-movement-clients-4.2.0-registration yes yes  ? need all sites participating
uberftp uberftp-4.2.0 yes yes yes no test transfer, reports only version
globus-url-copy globus-url-copy-4.2.0  ?  ?  ? covered by speedpage
gsiscp gsi-scp-hpn-client-4.2.0  ?  ?  ? test needed - speedpage?
gsisftp not implemented  ?  ?  ? test needed - speedpage?
tgcp deprecated? no?  ?  ? dropped
rft not implemented  ?  ?  ? see server rft-unit-dms-4.2.0 - Globus 5?
hpn-scp gsi-scp-hpn-client-4.2.0 as opposed to gsiscp?  ?  ? include in gsiscp test
SERVERS
registration ctss-data-movement-servers-4.2.0-registration yes yes  ? need all sites participating
gridftp gridftp-external-ping-dms-4.2.0  ?  ? no value uncertain
gridftp version (striped): matches registered and >= 4.0.8  ?  ? no update for Globus 5
gridftp gridftp-striped-external-telnet-dms-4.2.0  ?  ? no value uncertain
gridftp gridftp-striped-auth-dms-4.2.0  ?  ?  ? value uncertain
gridftp gridftp-striped-transfer-dms-4.2.0  ?  ? yes transfer size? speedpage?
gridftp version (nonstriped): matches registered and >= 4.0.8  ?  ? no update for Globus 5
gridftp gridftp-nonstriped-external-telnet-dms-4.2.0  ?  ? no value uncertain
gridftp gridftp-nonstriped-auth-dms-4.2.0  ?  ?  ? value uncertain
gridftp gridftp-nonstriped-transfer-dms-4.2.0  ?  ? yes transfer size? speedpage?
gsiscp gsi-scp-hpn-server-dms-4.2.0  ?  ? yes no transfer tested
rft rft-unit-dms-4.2.0  ?  ? no update for Globus 5?
rft rft-version-dms-4.2.0  ?  ? no no version requirement specified
[edit]

Data Management

Rich Raymond

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
SRB Client
version >= 3.4.1Y YN
sput-as-4.2.0Y YN
sget-as-4.2.9Y YN
sls-as-4.2.0N YN sput-sget already does the same things
[edit]

WAN GPFS

Mike Lowe

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
ctss-wan-gpfs-4.0.0-registration ctss-wan-gpfs-4.0.0-registration Y Y N
mount-wg-4.0.0 Y Y Kate added test from Mike to execute "mount -l" and grep for the registered endpoint
[edit]

WAN Lustre

Mike Lowe

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
ctss-wan-lustre-4.0.0-registrationctss-wan-lustre-4.0.0-registration Y Y N
mount-wl-4.0.0 Y Y Kate added test from Mike to execute "mount -l" and grep for the registered endpoint
[edit]

Co-Scheduling

Kenneth Yoshimoto

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
ctss-coscheduling-1.0.0-registration
ctss-coscheduling-registration-1.0.0 Y Y N This just says whether the site supports co-scheduling. The actual client software is registered from the App Dev and Runtime Kit. Maybe need a test specific to GUR registration?
[edit]

Metascheduling

Kenneth Yoshimoto

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
ctss-metascheduling-4.2.0-registration
ctss-metascheduling-4.2.0-registration Y Y N This just says whether the site supports metascheduling. The actual client software is registered from the App Dev and Runtime Kit. Maybe need a test specific to MCP registration?
glue2-4.2.0
glue2-4.2.0 Y Y N
[edit]

Remote Compute

Kenneth Yoshimoto

General comment: the tests look for any text in stderr. Maybe they should each parse for some known-good text in the stdout?

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
ctss-remote-compute-registration-4.2.0
ctss-remote-compute-4.2.0-registration Y Y N specific test: parse output for "<Description>TeraGrid Core Integration Kit</Description>"
globus-wsrf-4.2.0
wsrf-query-mds-rc-4.2.0 Y Y N specific test: parse output for "<ns0:IndexRP"
wsrf-query-mds-auth-JobsRP-rc-4.2.0 Y Y N Only works for authorized users. Kenneth thinks it's technically possible, but it would require policy acceptance by all the RPs to expose the queue information.
wsrf-query-mds-auth-JobsRP-cache-rc-4.2.0 Y Y N Only works for authorized users. Kenneth thinks it's technically possible, but it would require policy acceptance by all the RPs to expose the queue information.
wsrf-query-mds-auth-LoadRP-rc-4.2.0 Y Y N only gets load for 2006/09. Maybe should try to compare with actual load? This would vary by local scheduler, so each cluster would need some kind of custom adapter script to extract load info. Specific test: parse for "<Value>"\d+"</Value>"
wsrf-query-mds-auth-LoadRP-cache-rc-4.2.0 Y Y N Specific test: parse for "<Value>"\d+"</Value>"
prews-gram-4.2.0
prews-gram-external-telnet-rc-4.2.0 N Not needed by requested during LEAD work for quick notification (this just sees if there's a listener at that port)
prews-gram-netstat-rc-4.2.0 N Not needed by requested during LEAD work for quick notification (this just sees if there's a listener at that port)
prews-gram-gatekeeper-ping-rc-4.2.0 Y Y N Specific test: parse for "GRAM Authentication test successful"
prews-gram-fork-rc-4.2.0 Y Y N Maybe change sampleGridJob to output know text, like "GridJob Ran"
prews-gram-batch-rc-4.2.0 Y Y N Maybe change sampleGridJob to output know text, like "GridJob Ran"
wsgram-4.2.0
wsgram-external-telnet-rc-4.2.0 N Not needed by requested during LEAD work for quick notification (this just sees if there's a listener at that port)
wsgram-netstat-rc-4.2.0 N Not needed by requested during LEAD work for quick notification (this just sees if there's a listener at that port)
wsgram-wsrf-get-property-rc-4.2.0 Y Y N Specific test: parse output for "<ns1:ServiceMetaDataInfo"
wsgram-fork-rc-4.2.0 Y Y N Specific test: parse output for "Current job state: Active"
wsgram-batch-submit-rc-4.2.0 Y Y N Specific test: parse output for "Termination time:"
wsgram-batch-rc-4.2.0 Y Y N Specific test: parse output for "Termination time:"
gram
gram-external-ping-rc-4.2.0 N Not needed by requested during LEAD work for quick notification (this just sees if there's a listener at that port)
[edit]

Core

David Carver

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
ctss-core-registration-4.2.1
ctss-core-registration-4.2.1
globus-mds-info-4.2.1
globus-mds-info-4.2.1 Y Y
pacman-4.2.1
version: >= 3.14.1 Y Y N
pacman-unit-4.2.1 Y Y N
tg-ca-config-4.2.1
NEED: Version test Y
NEED: Functionality test Y While tg-ca-config is as a required package, not sure which parts of it (if any) are actually required to be deployed. (JP suggested moving the security tests under this component. --Kate)
tgresid-4.2.1
version: >= 2.0.0 Y Y N
tgresid-unit-4.2.1 Y YN
NEED: CTSSV3 Securty test
COMMENT NEED CTSSV3 Security test from http://sapa.sdsc.edu:8080/inca/jsp/status.jsp?xsl=default.xsl&resourceIds=teragrid&suiteNames=security. Many of the problems with the CTSS software can be traced to expired or invalid certifcates. The following two security test were in CTSSV3 and should be brought forward into CTSSV4. (Moved under tg-ca-config per JP. --Kate)
hostcert Y Y N
security.ca.unit Y Y N
NEED: Apache-ant test
COMMENT NEED apache-ant test. This package is required to install many of the CTSS software packages and should be removed from the Application Development & Runtime Support kit. (We are not testing kit pre-requisites, only the components themselves. --Kate)
version: >= 1.6.5 Y Y N
NEED: Java 1.4.2 test
COMMENT NEED Java 1.4.2 test. Many of the CTSS software components require/depend on Java 1.4.2 and should be removed from the Application Development & Runtime Support kit. (We are not testing kit pre-requisites, only the components themselves. --Kate)
version: >= 1.4.2-11 Y Y N Security issues with java version < 1.4.2-11
[edit]

Vizualization Support

David Carver

Cability Kit/Service INCA Test Name Still Needed Still Valid Needs Improvement Recommendation/Comment
vtss-visualization-3.0.0-registration Reviewed by TACC's Visualization team on 11/30.

This is the current software and versions on spur.tacc.teragrid.org and longhorn.tacc.utexas.edu.

Looks okay to me, David.

Paul

Looks good to me too.

Thanks, Greg

vtss-visualization-3.0.0-registration
chromium
version >= 1.9 Y Y N
cmake
version >= 2.6 Y Y N
imagemagick
version >= 6.4.3 Y Y N
mesa
version >= 6.4.2 Y Y N
netpbm
version >= 10.26.56 Y Y N
paraview
version >= 3.4.0 Y Y N
qt
version >= 4.3.5 Y Y N
visit
version >= 1.10.0 Y Y N
vtk
version >= 5.4.2 Y Y N


Back to deliverables.

Retrieved from "http://www.teragridforum.org/mediawiki/index.php?title=Inca_test_review"
Personal tools