MAN01 How to publish Site Information

From EGIWiki
Revision as of 18:30, 2 February 2011 by Psolagna (talk | contribs) (Created page with '= How to Publish My Site Information = TableOfContents == Checking Your Own GlueSite Object == $ ldapsearch -x -H ldap://YourSiteBdii.example.org:2170 \ -b 'Mds-V…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

How to Publish My Site Information

TableOfContents

Checking Your Own GlueSite Object

    $ ldapsearch -x -H ldap://YourSiteBdii.example.org:2170 \
    -b 'Mds-Vo-Name=<SiteName>,o=Grid'  '(ObjectClass=GlueSite)'

Results

Some results from an EGI view of the world. http://cern.ch/steve.traylen/GlueSite/PlotEgeeProdGlueSites.html

GStat2 http://gstat-prod.cern.ch/gstat/summary

Current Situation of GlueSite Object

These are the existing well established attributes in the !GlueSite object.

!GlueSiteName RAL-LCG2 Free Text, No White Space Same as GOCDB name if in GOCDB, your choice. GlueSiteUniqueID RAL-LCG2 Identical to your !GlueSiteName Same as !GlueSiteName !GlueSiteWeb `http://cern.ch/it` Free Text Valid URL about the site. !GlueSiteLatitude 52.42 NN.NN Site Latitute. !GlueSiteLongnitude 16.91 NN.NN Longnitude of Site. !GlueSiteDescription Rutherford Lab Free Text A long name for the site. !GlueSiteLocation Dublin, Ireland Town, City, Country An decreasing resolution ending with Country, agree a country name with in a country. i.e UK != United Kingdom. Scotland and the Balkans should write a dynamic provider. !GlueSiteUserSupportContact `mailto:helpdesk@example.org` Valid URL URL for getting support. A ticket system if available. !GlueSiteSysAdminContact `xmpp://admins@jabber.org` Valid URL How to contact the admins. !GlueSiteSecurityContact `mailto:security@example.org` Valid URL How to contact for security related matters.


and all of these should remain.


The !GlueSite object in the 1.3 Glue Schema contains an attribute !GlueSiteOtherInfo. To quote.

{{{ The attribute is to be used to publish data that does not fit any other attribute of the site entity. A name=value pair or an XML structure are example[s] of usage. }}}


Guidelines for GlueSite Object

A format for publishing useful information about sites within the !GlueSiteOtherInfo is needed. || Key || Example || Type || Notes || || GRID || EGEE || [#validgrid List of valid grid names] || Multiple ones can be defined. || || WLCG_TIER || 1 || Tier level of site in WLCG context. || Either 0, 1 , 2 , 3 , 4 || || WLCG_PARENT || UK-T1-RAL || Name of the higher (administrative) tier site in WLCG || The WLCG_NAME of the site at a higher tier with WLCG || || WLCG_NAME || IT-ATLAS-federation || [#lcgnames Valid WLCG Names] || An official WLCG name. || || WLCG_NAMEICON || `http://example.org/tier2.png` || Valid URL || URL to WLCGNAME icon, ideally 80x80 pixels. || || EGEE_ROC || SWE || text || Agree within your ROC what the field should be. || ||EGI_NGI||NGI_CZ||Valid NGI||Must agree with the GOC DB|| || EGEE_SERVICE || prod || prod, pps or cert || Which EGEE grid your site is part of, multiple attributes is okay. || || OLDNAME || Bristol || text || If your !GlueSiteName changes at some point please record your old name here. || || ICON || `http://example.org/icon.png` || Valid URL || Icon Image for your site, ideally 80x80 pixels || || BLOG || `http://scotgrid.blogspot.com/feeds/posts/default` || Valid RSS or Atom Feed || Your site blog if you have one ||


Keywords starting with one of the grid names are to some extent reserved for that grid.

Example

{{{ GlueSiteUniqueId: RAL-LCG2 GlueSiteName: RAL-LCG2 GlueSiteOtherInfo: GRID=EGEE GlueSiteOtherInfo: GRID=WLCG GlueSiteOtherInfo: WLCG_TIER=2 GlueSiteOtherInfo: WLCG_PARENT=CH-CERN GlueSiteOtherInfo: WLCG_NAME=UK-T1-RAL GlueSiteOtherInfo: EGEE_ROC=UK/I GlueSiteOtherInfo: EGEE_SERVICE=prod GlueSiteOtherInfo: OLDNAME=RAL-LCG1 GlueSiteOtherInfo: OLDNAME=RAL-LCG GlueSiteOtherInfo: ICON=logo_b_bground.jpg GlueSiteOtherInfo: BLOG=http://scotgrid.blogspot.com/feeds/posts/default }}}

Distributed Tier1s and Tier2s

Within an WLCG context for instance there are instances of distributed Tier2s and Tier1s. If separate component sites want to exist as a single WLCG tier then they might contain common values for their WLCGNAME.

{{{ GlueSiteUniqueId: UKI-NORTHGRID-LANCS-HEP GlueSiteName: UKI-NORTHGRID-LANCS-HEP GlueSiteOtherInfo: GRID=WLCG GlueSiteOtherInfo: GRID=EGEE GlueSiteOtherInfo: GRID=NORTHGRID GlueSiteOtherInfo: EGEE_SERVICE=prod GlueSiteOtherInfo: EGEE_ROC=UK/I GlueSiteOtherInfo: WLCG_TIER=2 GlueSiteOtherInfo: WLCG_NAME=UK-NorthGrid GlueSiteOtherInfo: WLCG_NAMEICON=sgbanner.png GlueSiteOtherInfo: WLCG_PARENT=UK-T1-RAL }}} {{{ GlueSiteUniqueId: UKI-NORTHGRID-LIV-HEP GlueSiteName: UKI-NORTHGRID-LIV-HEP GlueSiteOtherInfo: GRID=WLCG GlueSiteOtherInfo: GRID=EGEE GlueSiteOtherInfo: GRID=NORTHGRID GlueSiteOtherInfo: EGEE_SERVICE=prod GlueSiteOtherInfo: EGEE_ROC=UK/I GlueSiteOtherInfo: WLCG_TIER=2 GlueSiteOtherInfo: WLCG_NAME=UK-NorthGrid GlueSiteOtherInfo: WLCG_NAMEICON=sgbanner.png GlueSiteOtherInfo: WLCG_PARENT=UK-T1-RAL }}} Note that when a WLCGPARENT is a accounting unit from the MOU document http://gridops.cern.ch/mou/

Anchor(validgrid)

Established Grid Name

|| Short Name || Long Name || URL || || EGEE || Enabling Grids for E-sciencE Service || http://cern.ch/egee || || EELA || Europe and Latin America || http://www.eu-eela.eu/ || || WLCG || World LHC Computing Grid || http://cern.ch/lcg || || UKNGS || National UK Grid Service || http://www.ngs.ac.uk || || OSG || Open Science Grid || http://www.opensciencegrid.org/ || || NDGF || Nordic !DataGrid Facility || http://www.ndgf.org/ || || SCOTGRID || Scot Grid || http://www.scotgrid.ac.uk/ || Being part of a grid is just a reference that your site is in some way associated with a particular grid either technically or as part of a collaboration.

If your grid is not present then please add it here.

Anchor(lcgnames)

Valid WLCG Names

The WLCG names are the site names that appear within the LCG MOU concerning commitments to LHC computing. || WLCG Name || Current !GlueSiteName || || CA-TRIUMF || TRIUMF-LCG2 || || CERN || CERN-PROD || || DE-KIT || FZK-LCG2 || || ES-PIC || pic || || FR-CCIN2P3 || IN2P3-CC || || IT-INFN-CNAF || INFN-T1 || || NDGF || NGDF-T1 || || NL-T1 || SARA-MATRIX || || TW-ASGC || Taiwan-LCG2 || || UK-T1-RAL || RAL-LCG2 || || US-FNAL-CMS || USCMS-FNAL-W1 || || US-T1-BNL || BNL-LCG2 ||


For the tier two names please consult http://gridops.cern.ch/mou/ The column marked Accounting Name are the WLCG Names which in the case of Tier2s are the federation names. Use your federation name as your WLCG_NAME.

Also some tier2s live under more than 1 tier1 perhaps for different for different VOs. If your tier2 has more that one WLCG_PARENT then just add two distinct records to show this. Also some tier2s do not have a WLCGNAME at all.

{{{ GlueSiteUniqueId: EENet GlueSiteName: EENet GlueSiteOtherInfo: GRID=WLCG GlueSiteOtherInfo: GRID=EGEE GlueSiteOtherInfo: EGEE_SERVICE=prod GlueSiteOtherInfo: EGEE_ROC=Northern GlueSiteOtherInfo: WLCG_TIER=2 GlueSiteOtherInfo: WLCG_PARENT=UK-T1-RAL GlueSiteOtherInfo: WLCG_PARENT=NL-T1 }}}

Valid EGEE ROC Names

|| Region || Value || ||AsiaPacific ||AP || ||France ||FR || ||CERN || CERN || ||SouthWest Europe || SWE ||

Implementing This

All this extra configuration will be with in the static information for the glue site within the GIP system.

Manual Instructions

T.B.D.

YAIM Instructions

YAIM will have to be updated for those sites using yaim. This will be done and submitted to sites in the normal way. Please follow bug 34708 for progress. There is now a gLite patch, once released patch 1786. This has now been released as part of the EGEE release. 3.1.0 Update 27. || YAIM Variable and Value || Resulting Glue Attribute and Value || || SITE_NAME=RAL_LCG2 || !GlueSiteName: RAL-LCG2 || || SITE_DESC="Rutherford Lab" || !GlueSiteDescription: Rutherford Lab || || SITE_EMAIL= steve@example.org || !GlueSiteSysAdminContact: mailto:steve@example.org || || SITE_SUPPORT_EMAIL= steve@example.org || !GlueSiteUserSupportContact: mailto:steve@example.org || || SITE_SECURITY_EMAIL= steve@example.org || !GlueSiteSecurityContact: mailto:steve@example.org || || SITE_LOC="Soho, London, United Kingdom" || !GlueSiteLocation: Soho, London, United Kingdom || || SITE_LONG=52.45 || !GlueSiteLongitude: 52.45 || || SITE_LAT=-12.34 || !GlueSiteLatitude: -12.34 || || SITE_WEB="http://example.org/" || !GlueSiteWeb: http://example.org/ || || SITE_OTHER_GRID="EGEE|WLCG" || !GlueSiteOtherInfo: GRID=EGEEBR!GlueSiteOtherInfo: GRID=WLCG || || SITE_OTHER_EGEE_ROC="UK/I" || !GlueSiteOtherInfo: EGEE_ROC=UK/I || ||SITE_OTHER_EGI_NGI="NGI_CZ"||!GlueSiteOtherInfo: EGI_NGI=NGI_CZ|| || SITE_OTHER_EGEE_SERVICE="prod" || !GlueSiteOtherInfo: EGEE_SERVICE=prod || || SITE_OTHER_EGEE_SERVICE="pps" || !GlueSiteOtherInfo: EGEE_SERVICE=pps || || SITE_OTHER_WLCG_TIER=2 || !GlueSiteOtherInfo: WLCG_TIER=2 || || SITE_OTHER_<KEY>="<VALUE1>|<VALUE2>|<VALUE3>" || !GlueSiteOtherInfo: <KEY>=<VALUE1>BR!GlueSiteOtherInfo: <KEY>=<VALUE2>BR!GlueSiteOtherInfo <KEY>=<VALUE3> ||


As can be seen you want multiple values for !GlueSiteOtherInfo key to be set then just delimit your values with a |. If you want want of your values to contain a | then good luck to you.