Gratia Interfaces - APEL/WLCG - Notes

Description

The purpose of this little project is to tighten up the procedures for reporting CMS/ATLAS Tier 1/2 reporting to WLCG. The TOC sections address these areas.

Although, this topic mainly references Tier 2 sites, it is intended to cover Tier 1, as well.

There is a little logic (fuzzy in nature) to the font colors used:

• normal - is kind of a general statement of what exists today (sortof)
• green - items that are already in place in some manner
• blue - to-do type items
• red- areas in which I have no clue about what I am saying (although that could overlap with any other area).

Description of change process

The recommended route is an email to lcg.office@cern.ch with a
meaningful title e.g. Change to the USA Purdue CMS T2 Federation.

This will then trigger the change to be made and the relevant services
(APEL, GRIDVIEW) to be alerted. There is no ticketing system for this as
although changes do and will continue to occur, there are not enough to
warrant one.

The monthly accounting and availability reports which are sent from
lcg.office give people the chance to cross-check and signal any
anomalies which can either be in the data which is corrected at the
source, or the Federation/site mapping or pledge information which we
correct before the reports are published. The earlier reply from
Cristina hopefully confirms that work is on-going to correct the Purdue
sites in the portal. 

The other groups/people involved in this at this time are:

• egee-admin (egee-admin@cesga.es)
• sergio diaz (sdiaz@cesga.es)
• APEL-SUPPORT@JISCMAIL.AC.UK
• Sue.Foffano@cern.ch

Determining when WLCG data is "frozen"

It appears that there is a cutoff or freeze date based on the Accounting report that follows.

Tier 2 Accounting report
There is a draft report that is issued via email (???? days before the final). This was from Ruth on 4/16. It looks like this is sent 3 days prior to the cutoff .

Subject:  	March 2008 - Tier2 Accounting Report
Date: 	Fri, 11 Apr 2008 16:20:08 +0200
From: 	Lcg Office (Lcg.Office@cern.ch)
To: 	project-wlcg-tier2 (project-wlcg-tier2@cern.ch)
CC: 	worldwide-lcg-management-board (LCG Management Board)

Dear WLCG Collaboration Board Member and associated collaborators,
Attached is the draft Tier2 Accounting report for March 2008, which will be published 
on the LCG Planning Page at the end of this week. 
Please therefore signal any anomalies that you find to LCG office (lcg.office@cern.ch), 
before Friday 14 April 2008 pm

Regards,
Fabienne Baud-Lavigne
**********************
Fabienne Baud-Lavigne
LHC Computing Grid Project
Assistant to Les Robertson
IT Department
CERN
European Organization for Nuclear Research

To do:
Based on this, it appears that an afternoon execution of the interface cron script (lcg.sh) might be necessary.

• we are currently running at 01:00 daily
• need to account for time differential between here and Cern when the email stated 4/14 pm. So it may be a mid-afternoon run.
• this appears to be the date those numbers are frozen. We should NOT update prior months anymore.

Providing visibility to Gratia-APEL interface data

• EGEE Portal OSG view: http://www3.egee.cesga.es/gridsite/accounting/CESGA/osg_view.html
• EGEE Portal Tier 1 view: http://www3.egee.cesga.es/gridsite/accounting/CESGA/tier1_view.html
• EGEE Portal Tier 2 view: http://www3.egee.cesga.es/gridsite/accounting/CESGA/tier2_view.html

• The Monthly Accounting Report mentioned previously.

On April 15th, changes were made to the Gratia-APEL interface (LCG.py) to generate 2 files (xml and html formats) containing the APEL database's Gratia data. The data is extracted immediately after the daily updates are made. This data is currently (and temporarily) viewable here on Brian Bockleman's Nebraska web site:

• http://t2.unl.edu/gratia/wlcg_reporting

To do:
The following items need to be addressed to incorporate them in Gratia or a module of Gratia:

1. The xml file used by Brian's site is temporarily being made available on http://home.fnal.gov/~weigand/apel-wlcg/ . This was done to expedite and test the viability of the process.
   This could be made available on the Gratia tomcat server in a directory similar to where the static (pdf) reports are: http://gratia.opensciencegrid.org:8880/gratia-reports/apel-wlcg
   This may require the cron process for the interface be moved to the gratia09 host thus requiring a change to the authorized user in the APEL database which is currently only the gratia06 host. A very nice feature of Brian's web site is that it accesses the xml file directly at the source. No data transfer is required. So this web could be on another machine so long as the data is available external to the host it is on.
2. Brian's code needs to be moved to the fnal cvs repository as its own module or a module of Gratia.

Visibility / Maintenance of Normalization factors

Note: This will not address the value/validity of using SI2K? or any other SpecINT type number used in determining the Normalization Factor. That is entirely outside the scope of this interface.

Since the normalization factor is a part of the Gratia-APEL interface data, it is now (as of 4/15) visible at the Nebraska site with the other metrics:

• http://t2.unl.edu/gratia/wlcg_reporting

The Site Normalization Calculation Comparison table is temporary in nature to show the differences between the manually maintained factor and the GIP calculated one. If agreement can be obtain from all sites to use the GIP generated value, then the need for this table should go away.

To do:

1. Get agreement to use the GIP generated number from all sites/VOs
2. Define the process/procedure for determining the SI2K? number when new processors come online.
3. Develop the process to mechanically use the GIP generated number in the interface
4. Develop (in-progress already by Brian) the capability to display the details of the subcluster calculations.
5. Determine what data needs to be maintained in the Gratia database or if a separate database is required.
6. Determine if the gratia probes need to be enhanced to capture better data for recording HostDescription which is intended to contain information on the processor used when a job was run. This data field is very incomplete in the production gratia database.

Insuring all Tier 1/2 Sites are included in the interface.

1. For CMS sites,
   • UFlorida-HPC and UFlorida-IHEPA were not being reported by the interface.
   • HEPGRID_UERJ and SPRACE are being reported, but do not appear in the Tier2 drill down and, hence, should not be reported.
2. For ATLAS sites,
   • UC_Teraport and OU_OSCER_ATLAS are being reported, but do not appear in the Tier2 drill down and, hence, should not be reported.

The 2 Florida sites have been added to the interface (4/15).

The 4 sites that we are reporting, but do not show in the EGEE view, are still in the interface. I left them in the event my manual evaluation was in error.

• The problem with leaving them is that the view of the interface data shown at http://t2.unl.edu/gratia/wlcg_reporting will be misleading.
• Additionally, if we provide the capability of tracking actual vs pledged data (next section), it will likely be even more misleading unless we take this into account.

There are 2 mapping tables in the APEL accounting database ( goc-accounting.grid-support.ac.uk ) that identify the Tier 1 and Tier 2 groups/sites:

• org_Tier1
• org_Tier2

+-------------------+--------+-------+-------+
| Name              | Path   | RefID | MapID |
+-------------------+--------+-------+-------+
| US-FNAL-CMS       | 1.10   |     0 |     0 | 
| USCMS-FNAL-WC1-CE | 1.10.1 |    16 |     0 | 
| US-T1-BNL         | 1.4    |     0 |     0 | 
| BNL               | 1.4.1  |     9 |     0 | 
| BNL_ATLAS_1       | 1.4.2  |  9998 |     0 | 
+-------------------+--------+-------+-------+

+-----------------+-----------+-------+-------+
| Name            | Path      | RefID | MapID |
+-----------------+-----------+-------+-------+
| USA             | 1.31      |     0 |     0 | 
| US-AGLT2        | 1.31.1    |     0 |     0 | 
| AGLT2           | 1.31.1.1  |     1 |     0 | 
| T2_US_Purdue    | 1.31.10   |     0 |     0 | 
| Purdue-Lear     | 1.31.10.1 |     1 |     0 | 
| Purdue-RCAC     | 1.31.10.2 |     1 |     0 | 
| T2_US_UCSD      | 1.31.11   |     0 |     0 | 
| UCSDT2          | 1.31.11.1 |     1 |     0 | 
| T2_US_Wisconsin | 1.31.12   |     0 |     0 | 
| GLOW            | 1.31.12.1 |     1 |     0 | 
| US-NET2         | 1.31.2    |     0 |     0 | 
| BU_ATLAS_Tier2  | 1.31.2.1  |     1 |     0 | 
| US-MWT2         | 1.31.3    |     0 |     0 | 
| MWT2_UC         | 1.31.3.1  |     1 |     0 | 
| MWT2_IU         | 1.31.3.2  |     1 |     0 | 
| UC_ATLAS_MWT2   | 1.31.3.3  |     1 |     0 | 
| IU_OSG          | 1.31.3.4  |     1 |     0 | 
| US-SWT2         | 1.31.4    |     0 |     0 | 
| OU_OCHEP_SWT2   | 1.31.4.1  |     1 |     0 | 
| UTA_SWT2        | 1.31.4.2  |     1 |     0 | 
| SWT2_CPB        | 1.31.4.3  |     1 |     0 | 
| US-WT2          | 1.31.5    |     0 |     0 | 
| PROD_SLAC       | 1.31.5.1  |     1 |     0 | 
| T2_US_Caltech   | 1.31.6    |     0 |     0 | 
| CIT_CMS_T2      | 1.31.6.1  |     1 |     0 | 
| T2_US_Florida   | 1.31.7    |     0 |     0 | 
| Uflorida-PG     | 1.31.7.1  |     1 |     0 | 
| Uflorida-IHEPA  | 1.31.7.2  |     1 |     0 | 
| UFlorida-HPC    | 1.31.7.3  |     1 |     0 | 
| T2_US_MIT       | 1.31.8    |     0 |     0 | 
| MIT_CMS         | 1.31.8.1  |     1 |     0 | 
| T2_US_Nebraska  | 1.31.9    |     0 |     0 | 
| Nebraska        | 1.31.9.1  |     1 |     0 | 
+-----------------+-----------+-------+-------+

Tracking actual vs pledged usage

Pledge information (From Ruth (4/16):
The location of the Tier-2 pledge information we should use is:

• http://lcg.web.cern.ch/LCG/MB/accounting/Tier-2/T2%20Federation%20and%20site%20names.xls
• http://lcg.web.cern.ch/LCG/MB/accounting/ gives some documentation but no contact information.

To Do:
Brian is currently working on providing this capability for his web site.

Brian, can you give me some details here.

Contact information on Tier1/2 Site administrators

Usage of non-LCG VOs at Tier 1/2 sites

Include Tier 3 sites

Other Issues

Major updates

• Tier-2_Accounting_Report_March2008.pdf: Tier 2 Accounting Report - March 2008