Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "NGI DE:Join as resource centre"

From EGIWiki
Jump to navigation Jump to search
Line 23: Line 23:


     Personal Data of Primary Site Manager:
     Personal Data of Primary Site Manager:
     Name:
     Name:
   
   

Revision as of 10:36, 29 October 2010

Ngi-de-logo-trans.gif


NGI-DE wiki


Join as Resource Centre


NGI-DE Site Registration and Certification Procedure

In German National GRID Initiative (NGI-DE) there are three types of middleware resources. They are gLite, UNICORE and Globus. To be a NGI-DE site, at least one of the three middlewares has to be supported and the site has to register in GOCDB. To be an UNICORE site, UNICOREX and unicore-gateway of UNICORE6 must be supported. To be the Globus site, globus-GRIDFTP and GRAM5 of Globus version 5 must be supported. The gLite site should have the site-BDII, the Storage Element (SE) or/and Computing Element (CE) with at least eight Worker Node cores.

Below you can find a procedure on how to contribute resources to German National GRID Initiative NGI-DE. In case of doubts, please contact us by e-mail: ngi-de-admin@lists.kit.edu


STEP 1 - Registration

Requirements:

  • willingness to set-up the site
  • primary Site Manager - the person entitled to represent the Resource Centre in NGI-DE that owns a personal certificate

Actions by Primary Resource Managers:

  • send a digitally signed e-mail to ngi-de-admin@lists.kit.edu that include the following data and statements:
   Personal Data of Primary Site Manager:
   Name:

   Email:

   Telephone:

   Hours:

   Certificate DN:

   I'm the Primary Site Manager of the site described below.

   Site (GIIS) Name:

   Official Name of Hosting Institution:

   Domain: 
   Site Email Address:

   Site Telephone Number:

   Site Emergency Number:

   Country:

   All administrators and other necessary personnel at the site will be informed of and agree to abide by all Grid operating policies described at:

   the Grid Site Operations Security Policy

   The Site Security Contact and the team members will be informed of and agree to

    the Security Incident Response Policy 

ROC Staff Actions:

  • open a ggus ticket to follow up
  • register the site to GOC DB as a candidate site;
  • confirm registration to Primary Site Manager.


STEP 2: Preparation

Actions by Primary Site Manager:

  • register as a user in the GOCDB: https://goc.gridops.org/help/user/#add
  • apply for the 'Site Manager' role of your newly created site: https://goc.gridops.org/help/user/#role
  • after approval of your role by a regional manager:
  • fill all missing information in GOC DB about the site including names of machines. The most critical are: GIISURL and section "Nodes".
  • add other site administrators and security officers to GOCDB and assign the appropriate roles to them. There should be a least one 'Security Officer'.
  • create a site admin contact list and a security incident response (CSIRT) list and add to your GOCDB entry. The mailing lists should reach at least two people. They should be willing to react quickly to requests, in particular to security incidences.

Actions by All Admins:

ROC staff Actions:

  • test site and especially security contacts
  • switch site to non-certified status
  • enable monitoring of the site

Note: After several hours the site should be visible on the SAM portal: https://lcg-sam.cern.ch:8443/sam-uncert/sam.py or https://lcg-sam.cern.ch:8443/sam-pps-uncert/sam.py (for PPS sites)

STEP 3: Installation

Site Admins Actions:

  • check which version of middleware is obligatory for production installations: http://glite.web.cern.ch/glite/packages/latestRelease.asp
  • install the grid middleware according to the documentation on the release pages.
  • a minimum set of services is one computing element (CE), one storage element (SE), eight worker nodes (WNs), as well as a SiteBDII and a monitoring box (MON)
  • use this topBDII during the certification process: BDII_HOST=bdii-fzk.gridka.de

Important notes:

(or https://lcg-sam.cern.ch:8443/sam-pps-uncert/sam.py for PPS sites)

STEP 4: Certification

Actions by Site Admins:

  • inform the ROC that site is fully installed and configured properly;
  • fix issues raised by ROC staff.
  • register in the ROC DECH support portal as support staff (for your site) under https://dech-support.fzk.de/pages/support.php
  • (subscribe all admins to DECH ROC site admins mailing list. There you can ask questions, share your expertise and get known about recent EGEE news relevant for DECH region. The list's address is XXX-to-be-announced-XXX)

ROC staff actions:

  • check if the site is fully functional and inform the site managers about detected issues;
  • if everything is OK, switch site to certified status and schedule "Initial maintenance" for five working days due to necessity to check if the site is working properly in production environment (some features can be verified only in production mode);
  • if everything is OK and initial scheduled downtime is over, the site is fully certified!

FINAL REMARKS

Some important information for certified sites concerning operation in DECH ROC below:

  1. If your site fails SAM tests you may receive a ticket. Note that COD's send-tickets-priority is based on number of CPUs at a site, so you might not get this immediately after the failure. Please be pro-active - monitor your site and fix problems before tickets are raised.
  2. If you have problems with solving a ticket/problem or you don't know how to handle it you shall send an e-mail asking for support at grid-support-dech at iwr.fzk.de
  3. Don't forget to submit your weekly reports: https://cic.in2p3.fr/index.php?id=rc&subid=rc_report&js_status=2
  4. Middleware is a subject of obligatory upgrades, you will be informed about new releases and deadline for upgrades by EGEE Broadcast and/or DECH ROC.