gLite Integration Steps

How to join IGALC as a Resource Center using the gLite middleware
IGALC operates on resources located in Latin America and The Caribbean region. Below is the procedure to join as a Resource Center. Doubts and inquiries may be sent to roc AT igalc.org.
This document is based on the integration procedures of the German/Swiss and Central European ROCs, which can be found, respectively, here and here.

Basic Requirements

Willingness to set-up the Resource Center.
Primary Site Manager - the person entitled to represent the Resource Center in IGALC - must own a valid personal certificate.
Authority to sign a Service Level Description.

Step 1 - Registration

Formal commitments and support tools enrollment.

1.1. Primary Site Manager actions

Send a digitally signed email to roc AT igalc.org including the following data:

Primary Site Manager

  • Name
  • Email
  • Telephone
  • Working hours
  • Certificate Distinguished Name (DN)

Resource Center

  • System Name (eg. UFRJ-IF…)
  • Name of hosting institution
  • Country
  • Web Domain
  • Telephone
  • Email

Resources

  • If providing a Computing Element: amount of CPU cores
  • If providing a Storage Element: amount of TB of storage

1.2. IGALC actions

  • Send the OLA to the Resource Center.
  • Register the site at GOCDB as candidate site.

1.3. Primary Site Manager actions (continued)

1.4. IGALC actions (continued)

  • Confirm and approve the Primary Site Manager role at GOCDB.

Step 2 - Preparation

Mailing lists creation, support tools data insertion, VO enrollment.

2.1. Primary Site Manager actions

  • Fill in the missing information about the site and its nodes in GOCDB. Absolutely critical are the “GIIS URL” field and the “Nodes” section.
  • Register other personnel (Secondary Site Administrators and/or Security Officers) in GOCDB, assigning them the proper roles. It is mandatory to have at least one Security Officer.
  • Create a Site Administrator contact list and a Security Incident Response (CSIRT) list, adding them to the Site GOCDB entry. Each list should reach at least two people, who should be willing to quickly react to requests, specially security incidents.

2.2. All Site administrators actions

2.3. IGALC actions

  • Test the mailing lists.
  • Test the Site responsiveness in GGUS by opening an integration ticket.
  • Move site from 'Candidate' to 'Uncertified' status.
  • Enable monitoring of the Site.
  • Some hours after the completion of this step, the Resource Center should be visible at GSTAT.

Step 3 - Installation

Middleware deployment.

Primary Site Manager actions

  • Check the obligatory middleware versions for production Resource Centers.
  • Install the grid middleware according to the documentation on the release pages and the OLA.
  • The top-level BDII to be used during the certification process is cert-is.igalc.org.

Important Notes

  • Aside from any user VO that the site may accept, it must accept the DTEAM and OPS VOs.
  • Consult the GIIS Monitor to check the status of your Site.
  • Admins registered in GOCDB may submit Nagios tests to their sites from here.
  • IGALC is ready to help administrators on any issue concerning the setup, installation or deployment of the Site. Feel free to email anytime.

Step 4 - Certification

Site testing and problem solving.

4.1. Primary Site Manager actions

  • Inform IGALC that site is fully installed and configured properly.
  • Fix any issues raised by IGALC staff.

4.2. IGALC actions

  • Check if the site is fully functional and inform detected issues to the Site administrators.
  • When the Site passes all monitoring tests for one week, switch it to “Certified” status and schedule “Initial maintenance” for two working days. The downtime is necessary to check if the site is working properly in production environment, as some features can be verified only in production mode.
  • After the initial scheduled downtime is over, the Site will be available on the production Information System (BDII).

Final Remarks

  • If your site fails monitoring tests you may receive a ticket. Please be pro-active - monitor your site and fix problems before tickets are raised.
  • If you have problems with solving a ticket/problem or you don't know how to handle it you may ask for support by sending an e-mail support AT igalc.org.
  • Middleware is subject of obligatory upgrades, you will be informed about new releases and deadline for upgrades by IGALC.