Skip to end of metadata
Go to start of metadata

Contacts

The Inca deployment for XSEDE is currently being managed by SDSC. Please email inca@sdsc.edu for any questions or comments. This email alias maps to the following staff members: 

Main contact: Shava Smallen (ssmallen@sdsc.edu)

Backup contacts: Paul Hoover (phoover@sdsc.edu)

Status Pages

Current Inca status pages are linked from http://inca.xsede.org

Adding Inca To A New Resource

For each resource Inca will be monitoring, the following is required: 

  • Software Requirements 
    • Perl 5.8.6 or greater 
    • OpenSSL-0.9.6[[jkl]] or OpenSSL-0.9.7b or greater 
    • GNU tar (i.e., no limit on filename length) 
    • sshd service is running on the resource 
    • MyProxy 
  • Inca Account Requirements 
    • a generic "inca" user account 
    • add inca admin keys from https://software.xsede.org/inca/authorized_keys to authorized_keys (same as key in next section below)
    • ability to edit inca user cron 
    • 1GB home directory space 
    • include inca DN in gridmap file: "/C=US/O=National Center for Supercomputing Applications/CN=Inca Inca" 

Inca Public SSH key 

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAwmFER2xi9wqBylDGbwBdRmDmoq1a/tz1TjDa63jq47RL+PIS5dEysoveVi4OaXMosCIAH0cXwplWNgikiZMdCi7r2WVsR+ymu/J2KDEjU6g/VmKQ339xDlsMQFGwN4oVhSabz8urVRl4ztDKZAkd4CFdFXtpyz5jyBtWw7OQIoUf/Q5iICEOK0xN1tZ2Ii0pW4wLCiHFRs3K0Lj0NOhWFYAJfDclKGCycrQyq8SZm7uc29wfBOUHgCMPrSnv0ggUI4QSBNCANuIOQaSmhikzl3JcSNgBsqrmRcw1PGq+X5IKavYYucEclkhlHyYcAXJbuW5AoF68IHm25X/GWylSUw== inca@sapa

Please email inca@sdsc.edu when these requirements are ready and an Inca developer will install the software. Test will be configured based on capability kit registrations into the Information Services (please see "Reporter Configuration" section below) 

Deleting Inca From A Resource

Testing will be stopped for a resource when the Production end date registered in RDR is passed.  

Test Configuration

Inca tests are configured based on the user documentation and the following pages: 

The registrations are pulled every hour and if a change is detected, the Inca administrator is notified by email and manually propagates the changes to the Inca configuration file. We are currently working on automating this process so that the changes get automatically configured and the Inca administrator simply reviews them to make sure they look ok and then commits them to the Inca deployment. More information about this will be coming late this year or early next year. 

Note, that Inca maintains some configuration information for resources outside of the kit registrations. If you notice that the test configuration (input parameters, etc) is incorrect or a test itself needs improvement, please email inca@sdsc.edu

Testing During A Resource Outage

Inca will continue to test on a resource if able to during a scheduled or unscheduled outage but will mark any errors that are detected as special downtimes errors. These errors are treated as "neutral" meaning that no email notifications will be sent, the status of a service will have a gray "down err" in the status box, and when the history of a test is displayed, the error will show up as 0 indicating its neutral status (1 means test success and -1 means test failure). 

Inca currently pulls outage information every 5 minutes from the Information Services at the below url (except in JSON): 

https://info.xsede.org/wh1/outages/v1/outages/?format=html

This information comes from outages published into News. When publishing your outage, please be sure to fill out the "Inca Testing Info" section, indicate the outage type as "Show all affected systems as unavailable", and select the appropriate resource checkboxes. 

Updating or Adding New Inca Tests

Fair Use of the Inca Account and Pre-approval Process

The Inca account on XSEDE may only be used to execute tests that have been approved. To request approval for new tests or changes to tests: 

  1. email inca@sdsc.edu with details about changes or proposed tests (input parameters, dependencies, execution frequencies) 
  2. attend a group telecon or work with Inca team to contact a working group with your request. All tests and their execution frequencies must be approved by one of the following groups: Operations or RACD. Those groups may also approve their own tests and changes. 
  3. possibly also attend a XSEDE telecon or email the XSEDE list to receive that approval if the working group in step #2 deems your request to be performance impacting or resource consuming. 

Changing Tests or Adding New Tests

Any changes to the Inca deployment will need to be approved by the appropriate XSEDE group(s) before deployment (see section above). Please email inca@sdsc.edu with proposed changes to test configuration (e.g. input parameters, frequency of execution, etc.) or with code and commands to be executed by new tests before beginning work. 

The Inca team will deploy approved changes to tests and approved new tests. Once a new test is approved, follow the Inca user guide's instructions for writing reporters to create a reporter for the test. On most XSEDE machines the $INCA_DIST/Inca-Reporter-* directory mentioned in the guide can be replaced with ~inca/inca2install/var/reporter-packages. Set your $PERL5LIB environment variable as it is set on the Inca status pages in the reporter details execution command. Once a new reporter is written, contact inca@sdsc.edu to test first on a few XSEDE machines and then to deploy to all relevant resources. Include the names of machines the reporter will run on, the input parameters for each XSEDE machine, and the frequency of reporter execution for the new reporter. 

Test Examples

Drilling down to test details pages from any of the current status pages will lead to clickable test names to view test source code and help information. 

The following is an example of a simple version reporter using the Inca::Reporter::Version Perl API (determines Globus version): 

 #!/usr/bin/env perl
 use Inca::Reporter::Version;
 use strict;
 my $reporter = new Inca::Reporter::Version(
  name => 'grid.middleware.globus4.version',
  version => 2,
  url => 'http://www.globus.org',
  description => 'Reports the version of gt4',
 );
 $reporter->processArgv( @ARGV );
 $reporter->setPackageName('globus4');
 $reporter->setVersionByExecutable("$ENV{'GLOBUS_LOCATION'}/bin/globus-version","([[^\s\n]]+)");
 $reporter->print();

The following is an example of a simple unit reporter using the Inca::Reporter::SimpleUnit Perl API (Globus gatekeeper ping): 

#!/usr/bin/env perl
 use strict;
 use warnings;
 use Inca::Reporter::SimpleUnit;
 my $reporter = new Inca::Reporter::SimpleUnit(
  name => 'grid.middleware.globus.unit.gatekeeper',
  version => 2,
  description =>
    'Checks that the gatekeeper at a host is accessible from the local machine',
  url => 'http://www.ncsa.uiuc.edu/People/jbasney/teragrid-setup-test.html',
  unit_name => 'remoteLogin'
 );
 $reporter->addArg('host', 'gatekeeper host');
 $reporter->processArgv(@ARGV);
 my $host = $reporter->argValue('host');
 my $output = $reporter->loggedCommand("globusrun -a -r $host");
 if(!$output) {
  $reporter->unitFailure("globusrun failed: $!");
 } elsif($output !~ /GRAM Authentication test successful/) {
  $reporter->unitFailure("globusrun failed: $output");
 } else {
  $reporter->unitSuccess();
 }
 $reporter->print();

Updating Inca Test Result Manually

If you would like to invoke a test to run sooner than its regularly scheduled time (e.g., after some system modification), you can use the "Run Now" button on the test details page highlighted in red below: 

 

When you press the button, you will be prompted for a username and password. Please use your XSEDE username/password and email inca@sdsc.edu if you have trouble authenticating. Once authenticated, you will see the following confirmation screen: 

  • No labels