TWiki>
LCG Web>WLCGConfigurationEvaluation>DiscussionsOnCMSSpecificCRIC>Archive (2018-02-05, PanosPaparrigopoulos)
EditAttachPDF
LCG Web>WLCGConfigurationEvaluation>DiscussionsOnCMSSpecificCRIC>Archive (2018-02-05, PanosPaparrigopoulos) EditAttachPDFTABLE OF CONTENTS
Bootstrap CMS info into CRIC prototype
CMS Site
CMS Site vs GocDB /OIM site investigation
Sites in sitedb (under lcg tag) but not on OIM/GocDB:| LCG Site Name | CMS Site name | In VOFeed? | Proposed action | Required action from CMS |
|---|---|---|---|---|
| Argonne | T3_US_ANL | NO | Add the site to CORE | - |
| INFN-IT_OPPORTUNISTIC | T3_IT_Opportunistic | No | Add the site to CORE | - |
| JINR-T1-DISK | no cms site is defined | NO | Whether sites with '-DISK' extension are needed, to confirm with CMS | Please, confirm what to do with '-DISK' sites |
| NU Tier3 under lcg tag is mapped to Northwestern | T3_US_NU | NO | to be added to CORE, the name to be confirmed | - |
| None under lcg tag is mapped to MEPhI | T3_RU_MEPhI | No | The site exists in GocDB and CORE with name ru-Moscow-MEPHI-LCG2 and proper mapping to the CMS site | Might need a fix in SiteDB , instead of None under LCG tag should have ru-Moscow-MEPHI-LCG2, the fix in Glidein XML is required as well |
| Northeastern | T3_US_NEU | NO | Add the site to CORE | - |
| RAL-LCG2-DISK is mapped under lcg tag to RALDISK | T1_UK_RAL_Disk | NO | Whether sites with '-DISK' extension are needed, to confirm with CMS | Please, confirm waht to do with '-DISK' sites |
| T2-MY-UMSIFIR under lcg tag is mapped to University of Malaya | T2_MY_SIFIR | NO | to be added to CORE, the name to be confirmed | - |
| T3USHEPCLOUD | T3_US_HEPCloud | YES | Add the site to CORE | - |
| JHU | T3_US_JHU | NO | Add the site to CORE | - |
| Kansas | T3_US_Kansas | NO | Add the site to CORE | - |
| T3_US_Princeton_ICSE | T3_US_Princeton_ICSE | YES | For some reason the name of the site in CORE is now Princeton_ICSE_T3_CMS should be T3_US_Princeton_ICSE instead | - |
| T3_US_UTENN | T3_US_UTENN | NO | Add the site to CORE | - |
| UKI-GridPP-Cloud under lcg tag is mapped to GridPP Cloud | T3_UK_GridPP_Cloud | NO | The site is registred in GocDB , but with the name is UKI-GridPP-Cloud-IC Add the site to CORE, but the name in SiteDB might need to be corrected | Make the name in SiteDB consistent with the name registered in GocDB |
| USCMS-FNAL-LPC | T3_US_FNALLPC | YES | Add the site to CORE | - |
| USCMS-FNAL-WC1-DISK is mapped under wlcg tag to FNALDISK | T1_US_FNAL_Disk | NO | Whether sites with '-DISK' extension are needed, to confirm with CMS | Please, confirm what to do with '-DISK' sites |
| UVA-HEP under lcg tag is mapped to UVA | T3_US_UVA | YES | Add the site to CORE, the name to be confirmed | - |
| VBU_CMSunder lcg taf is mapped to T3_IN_VBU | T3_IN_VBU | YES | Add the site to CORE, the name to be confirmed | - |
| Volunteer_CMS | T3_CH_Volunteer | YES | Add the site to CORE | - |
| grid.puhep.res.in under lcg tag is mapped to PUHEP | T3_IN_PUHEP | NO | to be added to CORE, the name to be confirmed | - |
| ru-Moscow-SINP-LCG2 under LCG tag is mapped to SINP | T2_RU_SINP | YES | Strange that SINP T3 site is registered in GocDB, while T2 one is not, need confirmation from CMS what to do with this site | Probably T2 site has to be registered in GocDB |
| ru-Moscow-SINP-LCG2-t3 under lcg tag is mapped to Skobeltsyn Institute of Nuclear Physics | T3_RU_SINP | NO | THe site name registered in GocDB is ru-Moscow-SINP-T3 which is inconsistent with the name in SiteDB. Looks to be a mistake. Should add to CORE, but need to understand with which name, the change in SiteDB is desired | Make the name in SiteDB consistent with the one the site is registered in GocDB |
| t3ustacc under lcg tag is mapped to T3_US_TACC | T3_US_TACC | NO | Add the site to CORE, the name to be confirmed | - |
| t3uswisconsin under lcg tag is mapped to T3 US Wisconsin | T3_US_Wisconsin | NO | Add the site to CORE, the name to be confirmed | - |
| Site Name | CMS site name | Whether returned by SiteDB site-names API | Proposed action | Required action from CMS |
|---|---|---|---|---|
| Comet | T3_US_SDSC | NO | Add the site to CORE | - |
| None | T3_RU_MEPhI | YES | The site ru-Moscow-MEPHI-LCG2 is registered in GocDB and is in CORE with this name | Might need a fix in SiteDB , insted of None under LCG tag should have ru-Moscow-MEPHI-LCG2, the fix in Glidein XML is required as well |
| SU-OG-CE | T3_US_OSG | NO | This is wrong. We skip importing it and we instead hardcode the data needed to generate the vofeed. | - |
| SU-OG-CE1 | T3_US_OSG | NO | This is wrong. We skip importing it and we instead hardcode the data needed to generate the vofeed. | - |
| Stampede | T3_US_TACC | NO | There is no site Stampede in SiteDB, there is t3ustacc instead, so in core we should add the site with the name | Glidein entry shuld be fixed in order to have to t3ustacc instead of Stampede |
| T3USHEPCLOUD | T3_US_HEPCloud | YES | Add the site to CORE | - |
| T3_CH_CERN_HelixNebula | T3_CH_CERN_HelixNebula | YES but is mapped under lcg tag to HelixNebula | Add the site to CORE, name to be confirmed | - |
| T3_US_Princeton_ICSE | T3_US_Princeton_ICSE | YES but is mapped under lcg tag to Princeton ICSE | Add the site to CORE, name to be confirmed | - |
| TAMU_BRAZOS_CE | T3_US_TAMU | NO | Add the site to CORE | - |
| UCSDT2Sleep | Is not any more in VOfeed | |||
| USCMS-FNAL-LPC | T3_US_FNALLPC | YES | Add the site to CORE | - |
| UVA-HEP | T3_US_UVA | YES but mapped under lcg tag to UVA | Add the site to CORE, name to be confirmed | - |
| VBU_CMS | T3_IN_VBU YES but mapped under lcg tag to T3_IN_VBU | Add the site to CORE, name to be confirmed | - | |
| Volunteer_CMS | T3_CH_Volunteer | YES | Add the site to CORE, name to be confirmed | - |
| umd-ce | T3_US_UMD | YES it exists but with the name umd-cms under lcg tag which is mapped to UMD | umd-cms site does exist in OIM and Core and is corrcetly mapped to T3_US_UMD | The problem looks to come from Glidein entry , where we have umd-ce instead of umd-cms. If the problem is fixed there, it is also fixed in VOfeed , and everything is consistent |
| CMS Name | Core Name | Core site appearance | Mapping source | CMS name appearances count | Core Name appearances count | SiteDB Title | SiteDB Usage | Issue | Clarification |
|---|---|---|---|---|---|---|---|---|---|
| T0_CH_CERN | CERN-PROD | gocdb | both | 1 | 3 | CERN Tier-0 | None | see below | - |
| T2_CH_CERN | CERN-PROD | gocdb | both | 1 | 3 | CERN Tier-2 | None | see below | - |
| T3_CH_CERN_CAF | CERN-PROD | gocdb | both | 1 | 3 | T3_CH_CERN_CAF | LCG | CMS sites associated to CERN-PROD have both “other” and “None” usage. In this context: - “None” should mean “dedicated resource" (with even WMAgent instance for T0) for reconstruction (T0) or alignment and calibration (T2)? - “other” for T3 means accessible via CRAB for analysis or commissioning only to a restricted set of people (see the SITECONF entry  )? |
- |
| T2_CH_CERN_AI | CERN-PROD-AI | none | siteDB | 1 | 1 | CERN Tier-2 AI | LCG | CERN-PROD-AI core site was created in CRIC. What does "LCG" usage mean in this context? | Will be removed from siteDB, for the time being let's create a peer as it is in core. |
| T2_CH_CERN_HLT | CERN-PROD-HLT | none | siteDB | 1 | 1 | CERN Tier-2 HLT | LCG | CERN-PROD-HLT core site was created in CRIC. Does “LCG” usage mean: resources here can be accessed via the “HLT cloud interface”? | for the time being let's create a peer as it is in core. |
| T2_CH_CERN_Wigner | CERN-PROD-WIGNER | none | siteDB | 1 | 1 | CERN Tier-2 Wigner | LCG | CERN-PROD-WIGNER core site was created in CRIC. What does "LCG" usage mean in this context? | Will be removed from siteDB, for the time being let's create a peer as it is in core. |
| T3_CH_CERN_HelixNebula | CERN_HelixNebula_CMS | none | siteDB | 1 | 1 | HelixNebula | LCG | CERN_HelixNebula_CMS core site was created in CRIC. What does "LCG" usage mean in this context? | for the time being let's create a peer as it is in core. |
| T3_CH_CERN_OpenData | Public_CERN_CMS | none | both | 1 | 1 | CERN Open Data | other | CERN Open Data core site was created in CRIC. In this context, does “other” mean: not used for WLCG jobs? | for the time being let's create a peer as it is in core. |
| T1_RU_JINR | JINR-T1 | gocdb | both | 1 | 1 | JINR-T1 | LCG | - | - |
| T1_RU_JINR_Disk | JINR-T1-DISK | none | siteDB | 1 | 1 | JINR-T1DISK | LCG | We should understand what is the use of the '_Disk' suffix. | let's skip all _Disk sites for the time being |
| T1_DE_KIT | FZK-LCG2 | gocdb | both | 1 | 1 | KIT | LCG | - | - |
| T1_ES_PIC | pic | gocdb | both | 1 | 1 | PIC | LCG | - | - |
| T1_FR_CCIN2P3 | IN2P3 -CC | gocdb | both | 1 | 1 | CC-IN2P3 | LCG | - | - |
| T1_IT_CNAF | INFN-T1 | gocdb | both | 1 | 1 | CNAF | LCG | - | - |
| T1_UK_RAL | RAL-LCG2 | gocdb | both | 1 | 1 | RAL | LCG | - | - |
| T1_UK_RAL_Disk | RAL-LCG2-DISK | none | siteDB | 1 | 1 | RALDISK | None | We should understand what is the use of the '_Disk' suffix. | skip this site |
| T1_US_FNAL | USCMS-FNAL-WC1 | both | both | 1 | 1 | FNAL | OSG | - | - |
| T1_US_FNAL_Disk | USCMS-FNAL-WC1-DISK | none | siteDB | 1 | 1 | FNALDISK | None | We should understand what is the use of the '_Disk' suffix. | skip this site |
| T2_AT_Vienna | Hephy-Vienna | gocdb | both | 1 | 1 | Hephy-Vienna | LCG | - | - |
| T2_BE_IIHE | BEgrid-ULB-VUB | gocdb | both | 1 | 1 | IIHE | LCG | - | - |
| T2_BE_UCL | BelGrid -UCL | gocdb | both | 1 | 1 | Louvain | LCG | - | - |
| T2_BR_SPRACE | SPRACE | oim | both | 1 | 1 | SPRACE | OSG | - | - |
| T2_BR_UERJ | UERJ | oim | both | 2 | 1 | HEPGRID_UERJ | OSG | - | This is the currently used mapping since we are not yet using VOFeed to populate the db. |
| T2_BR_UERJ | UERJ_CE_2 | none | VOFeed | 2 | 1 | - | - | - | Will be fixed |
| T2_CH_CSCS | CSCS-LCG2 | gocdb | both | 1 | 2 | CSCS | LCG | - | - |
| T2_CH_CSCS_HPC | CSCS-LCG2 | gocdb | both | 1 | 2 | Swiss National Supercomputing Centre | LCG | - | - |
| T2_CN_Beijing | BEIJING-LCG2 | gocdb | both | 1 | 1 | Beijing | LCG | - | - |
| T2_DE_DESY | DESY-HH | gocdb | both | 1 | 1 | DESY | LCG | - | - |
| T2_DE_RWTH | RWTH-Aachen | gocdb | both | 1 | 1 | RWTH | LCG | - | - |
| T2_EE_Estonia | T2_Estonia | gocdb | both | 1 | 1 | Estonia | LCG | - | - |
| T2_ES_CIEMAT | CIEMAT-LCG2 | gocdb | both | 1 | 1 | CIEMAT | LCG | - | - |
| T2_ES_IFCA | IFCA-LCG2 | gocdb | both | 1 | 1 | IFCA | LCG | - | - |
| T2_FI_HIP | FI_HIP_T2 | gocdb | both | 1 | 1 | Helsinki Institute of Physics | ARC | The ARC usage (I assume for NordUGrid) is set only for "Helsinki Institute of Physics" title: the corresponding physical site FI_HIP_T2 is registered in GocDB. Can this value be changed into LCG, or should we keep it for some NordUGrid specific features? | - |
| T2_FR_CCIN2P3 | IN2P3 -CC-T2 | gocdb | both | 1 | 1 | CC-IN2P3 AF | LCG | - | - |
| T2_FR_GRIF_IRFU | GRIF | gocdb | both | 1 | 2 | GRIF_IRFU | LCG | - | - |
| T2_FR_GRIF_LLR | GRIF | gocdb | both | 1 | 2 | GRIF_LLR | LCG | - | - |
| T2_FR_IPHC | IN2P3 -IRES | gocdb | both | 1 | 1 | IPHC | LCG | - | - |
| T2_GR_Ioannina | GR-07-UOI-HEPLAB | gocdb | both | 1 | 1 | Ioannina | LCG | - | - |
| T2_HU_Budapest | BUDAPEST | gocdb | both | 1 | 1 | Hungary | LCG | - | - |
| T2_IN_TIFR | INDIACMS-TIFR | gocdb | both | 1 | 1 | - | - | ||
| T2_IT_Bari | INFN-BARI | gocdb | both | 1 | 1 | Bari | LCG | - | - |
| T2_IT_Legnaro | INFN-LNL-2 | gocdb | both | 1 | 1 | Legnaro | LCG | - | - |
| T2_IT_Pisa | INFN-PISA | gocdb | both | 1 | 1 | Pisa | LCG | - | - |
| T2_IT_Rome | INFN-ROMA1-CMS | gocdb | both | 1 | 1 | Rome | LCG - | - | |
| T2_KR_KISTI | KR-KISTI-GSDC-02 | gocdb | both | 1 | 1 | KISTI-GSDC | LCG | - | - |
| T2_KR_KNU | LCG_KNU | gocdb | both | 1 | 1 | KNU | LCG | - | - |
| T2_MY_SIFIR | T2-MY-UMSIFIR | none | siteDB | 1 | 1 | University of Malaya | LCG | - | - |
| T2_MY_UPM_BIRUNI | MY-UPM-BIRUNI-01 | gocdb | siteDB | 1 | 1 | UPM Biruni | LCG | - | - |
| T2_PK_NCP | NCP-LCG2 | gocdb | both | 1 | 1 | NCP-LCG2 | LCG | - | - |
| T2_PL_Swierk | NCBJ-CIS | gocdb | both | 1 | 1 | T2_PL_Swierk | LCG | - | - |
| T2_PL_Warsaw | ICM | gocdb | both | 1 | 1 | Warsaw | LCG | - | - |
| T2_PT_NCG_Lisbon | NCG-INGRID-PT | gocdb | both | 1 | 1 | NCG-INGRID-PT | None | Should usage be LCG? | - |
| T2_RU_IHEP | RU-Protvino-IHEP | gocdb | both | 1 | 1 | IHEP | None | Should usage be LCG? | - |
| T2_RU_INR | Ru-Troitsk-INR-LCG2 | gocdb | both | 1 | 1 | INR | None | Should usage be LCG? | - |
| T2_RU_ITEP | ITEP | gocdb | both | 1 | 1 | ITEP | None | Should usage be LCG? | - |
| T2_RU_PNPI | ru-PNPI | gocdb | both | 1 | 1 | PNPI | None | Should usage be LCG? | - |
| T2_RU_JINR | JINR-LCG2 | gocdb | both | 3 | 1 | JINR | None | We should understand why T2_RU_JINR seems to be associated with 3 sites ( note that only one of those 3 can be found in our databases) | This is the correct mapping (JINR_NOVA_CE1 and JINR_NOVA_CE2 are wrong entries). Why usage is None? Should be LCG? |
| T2_RU_JINR | JINR_NOVA_CE1 | none | VOFeed | 3 | 1 | - | Invalid mapping, will be fixed in the source | ||
| T2_RU_JINR | JINR_NOVA_CE2 | none | VOFeed | 3 | 1 | - | Invalid mapping, will be fixed in the source | ||
| T2_RU_SINP | ru-Moscow-SINP-LCG2 | none | both | 1 | 1 | SINP | None | ru-Moscow-SINP-LCG2 does not exist in GocDB. TBC | - |
| T2_TH_CUNSTDA | T2-TH-CUNSTDA | gocdb | both | 1 | 1 | CUNSTDA | LCG | - | - |
| T2_TR_METU | TR-03-METU | gocdb | both | 1 | 1 | METU | None | Should usage be LCG? | - |
| T2_TW_NCHC | TW-NCHC | gocdb | both | 1 | 1 | Nat Center High Perf Comp NCHC | LCG | - | - |
| T2_UA_KIPT | Kharkov-KIPT-LCG2 | gocdb | both | 1 | 1 | KIPT | None | Should usage be LCG? | - |
| T2_UK_London_Brunel | UKI-LT2-Brunel | gocdb | both | 1 | 1 | Brunel | LCG | - | - |
| T2_UK_London_IC | UKI-LT2-IC-HEP | gocdb | both | 1 | 1 | IC | LCG | - | - |
| T2_UK_SGrid_Bristol | UKI-SOUTHGRID-BRIS-HEP | gocdb | both | 1 | 1 | Bristol | LCG | - | - |
| T2_UK_SGrid_RALPP | UKI-SOUTHGRID-RALPP | gocdb | both | 1 | 1 | Rutherford PPD | LCG | - | - |
| T2_US_Caltech | CIT_CMS_T2 | oim | both | 1 | 1 | Caltech | Unknown | Should usage be changed to OSG? | - |
| T2_US_Florida | UFlorida-HPC | oim | both | 1 | 1 | Florida | OSG | - | - |
| T2_US_MIT | MIT_CMS | oim | both | 1 | 1 | MIT | OSG | - | - |
| T2_US_Nebraska | Nebraska | oim | both | 4 | 1 | Nebraska | OSG | We should understand why T2_US_Nebraska seems to be associated with 4 different CORE sites. | This is the currently used mapping since we are not yet using VOFeed to populate the db. Map T2_US_Nebraska to Nebraska |
| T2_US_Nebraska | Sandhills | oim | VOFeed | 4 | 1 | - | - | We should understand why T2_US_Nebraska seems to be associated with 4 different CORE sites. | map to Nebraska |
| T2_US_Nebraska | Crane | oim | VOFeed | 4 | 1 | - | - | We should understand why T2_US_Nebraska seems to be associated with 4 different CORE sites. | map to Nebraska |
| T2_US_Nebraska | Tusker | oim | VOFeed | 4 | 1 | - | - | We should understand why T2_US_Nebraska seems to be associated with 4 different CORE sites. | map to Nebraska |
| T2_US_Purdue | Purdue-Conte | oim | both | 6 | 1 | We should understand why T2_US_Purdue CMS site seems to be associated with multiple core sites. | Let's map all CMS purdue sites to a single Purdue site Purdue-Hammer, handle it as an exceptional case in the code | ||
| T2_US_Purdue | Purdue-Hammer | oim | both | 6 | 1 | Purdue | OSG | We should understand why T2_US_Purdue CMS site seems to be associated with multiple core sites. | - |
| T2_US_Purdue | Purdue-Carter | oim | siteDB | 6 | 1 | Purdue | OSG | We should understand why T2_US_Purdue CMS site seems to be associated with multiple core sites. | - |
| T2_US_Purdue | Purdue-Hadoop | oim | both | 6 | 1 | Purdue | OSG | We should understand why T2_US_Purdue CMS site seems to be associated with multiple core sites. | - |
| T2_US_Purdue | Purdue-Rice | oim | both | 6 | 1 | Purdue | OSG | We should understand why T2_US_Purdue CMS site seems to be associated with multiple core sites. | - |
| T2_US_Purdue | Purdue-Halstead | oim | both | 6 | 1 | Purdue | OSG | We should understand why T2_US_Purdue CMS site seems to be associated with multiple core sites. | - |
| T2_US_UCSD | UCSDT2 | oim | both | 2 | 1 | UCSD | OSG | - | - |
| T2_US_UCSD | UCSDT2-B | none | siteDB | 2 | 1 | - | - | UCSDT2 exists in OIM but not UCSDT2-B | This entry is invalid and it has been removed from SiteDB |
| T2_US_Vanderbilt | Vanderbilt | oim | both | 1 | 1 | Vanderbilt | OSG | - | - |
| T2_US_Wisconsin | GLOW | oim | both | 1 | 1 | Wisconsin | OSG | - | - |
| T3_BG_UNI_SOFIA | BG05-SUGrid | gocdb | both | 1 | 1 | Uni Sofia | LCG | - | - |
| T3_BY_NCPHEP | BY-NCPHEP | gocdb | both | 1 | 1 | BY-NCPHEP | None | Should usage be LCG? | - |
| T3_CH_PSI | T3_CH_PSI | gocdb | both | 1 | 1 | PSI | None | Should usage be LCG? | - |
| T3_CH_Volunteer | Volunteer_CMS | none | both | 1 | 1 | Volunteer | LCG | Volunteer_CMS is not in GocDB, what does LCG usage mean here? | - |
| T3_CN_PKU | CN-BEIJING-PKU | gocdb | both | 1 | 1 | CN_PKU | LCG | - | - |
| T3_CO_Uniandes | UNIANDES | gocdb | both | 1 | 1 | UNIANDES | LCG | - | - |
| T3_ES_Oviedo | UOGRID | gocdb | siteDB | 1 | 1 | Oviedo | Unknown | Should usage be LCG? | - |
| T3_FR_IPNL | IN2P3 -IPNL | gocdb | both | 1 | 1 | IN2P3 -IPNL | LCG | - | - |
| T3_GR_Demokritos | GR-05-DEMOKRITOS | gocdb | siteDB | 1 | 1 | Demokritos | LCG | - | - |
| T3_GR_IASA | GR-06-IASA | gocdb | siteDB | 2 | 1 | IASA | LCG | - | - |
| T3_GR_IASA | HG-02-IASA | gocdb | both | 2 | 1 | IASA | LCG | - | map to GR-06-IASA |
| T3_HR_IRB | egee.irb.hr | gocdb | both | 1 | 1 | IRB | LCG | - | - |
| T3_HU_Debrecen | T3_HU_Debrecen | gocdb | both | 1 | 1 | T3_HU_Debrecen | LCG | - | - |
| T3_IN_PUHEP | grid.puhep.res.in | none | siteDB | 1 | 1 | PUHEP | LCG | grid.puhep.res.in site is not in GocDB. What does LCG usage mean here? | - |
| T3_IN_TIFRCloud | T3_IN_TIFRCloud | gocdb | both | 1 | 1 | TIFR Opportunistic | LCG | - | - |
| T3_IN_VBU | VBU_CMS | none | both | 1 | 1 | T3_IN_VBU | LCG | VBU_CMS site is not in GocDB. What does LCG usage mean here? | - |
| T3_IR_IPM | IR-IPM-HEP | gocdb | both | 1 | 1 | IPM | None | Should usage be LCG? | - |
| T3_IT_Bologna | INFN-BOLOGNA-T3 | gocdb | both | 1 | 1 | Bologna-T3 | None | Should usage be LCG? | - |
| T3_IT_Firenze | INFN-FIRENZE | gocdb | siteDB | 1 | 1 | Firenze | None | Should usage be LCG? | - |
| T3_IT_MIB | INFN-MIB | gocdb | both | 1 | 1 | INFN-MIB | LCG | - | - |
| T3_IT_Opportunistic | INFN-IT_OPPORTUNISTIC | none | siteDB | 1 | 1 | T3_IT_Opportunistic | other | - | - |
| T3_IT_Perugia | INFN-PERUGIA | gocdb | both | 1 | 1 | Perugia | LCG | - | - |
| T3_IT_Trieste | INFN-TRIESTE | gocdb | both | 1 | 1 | Trieste | LCG | - | - |
| T3_KR_KISTI | T3_KR_KISTI | oim | both | 1 | 1 | KISTI T3 | OSG | - | - |
| T3_KR_KNU | KR-KNU-T3 | gocdb | both | 1 | 1 | KR_KNU | LCG | - | - |
| T3_KR_UOS | KR-UOS-SSCC | gocdb | both | 1 | 1 | UOS | LCG | - | - |
| T3_MX_Cinvestav | cinvestav | oim | both | 1 | 1 | cinvestav | OSG | - | - |
| T3_RU_FIAN | ru-Moscow-FIAN-LCG2 | gocdb | both | 1 | 1 | FIAN | LCG | - | - |
| T3_RU_MEPhI | None | none | both | 1 | 1 | MEPhI | LCG | This site relates to a site called 'None' both on SiteDB and VOFeed. We should check if this is a mistake or something else. | associate to GocDB site ru-Moscow-MEPHI-LCG2 |
| T3_RU_SINP | ru-Moscow-SINP-LCG2-t3 | none | siteDB | 1 | 1 | Skobeltsyn Institute of Nuclear Physics | LCG | ru-Moscow-SINP-LCG2-t3 does not exist in GocDB | Map to GocDB site ru-Moscow-SINP-T3. This is consistent with LCG usage. |
| T3_TH_CHULA | T3-TH-CHULA | gocdb | both | 1 | 1 | T3_TH_CHULA | LCG | - | - |
| T3_TW_NCU | TW-NCUHEP | gocdb | both | 1 | 1 | NCU | LCG | - | - |
| T3_TW_NTU_HEP | TW-NTU-HEP | gocdb | both | 1 | 1 | NTU_HEP | LCG | - | - |
| T3_UK_GridPP_Cloud | UKI-GridPP-Cloud | none | siteDB | 1 | 1 | GridPP Cloud | LCG | - | - |
| T3_UK_London_QMUL | UKI-LT2-QMUL | gocdb | both | 1 | 1 | QMUL | None | Should usage be LCG? | - |
| T3_UK_London_RHUL | UKI-LT2-RHUL | gocdb | both | 1 | 1 | RHUL | None | Should usage be LCG? | - |
| T3_UK_SGrid_Oxford | UKI-SOUTHGRID-OX-HEP | gocdb | both | 1 | 1 | Oxford | LCG | - | - |
| T3_UK_ScotGrid_ECDF | UKI-SCOTGRID-ECDF | gocdb | both | 1 | 1 | ECDF | None | Should usage be LCG? | - |
| T3_UK_ScotGrid_GLA | UKI-SCOTGRID-GLASGOW | gocdb | both | 1 | 1 | UKI-SCOTGRID-GLASGOW | None | Should usage be LCG? | - |
| T3_US_ANL | Argonne | none | siteDB | 1 | 1 | Argonne | OSG | This might be ANLASC on OIM. If so, OSG usage is consistent. | - |
| T3_US_BU | T3_US_BU | none | siteDB | T3_US_BU | OSG | 1 | 1 | This might be BU_ATLAS_Tier2 (Atlas site on Boston University). Given that we have created a physical site T3_US_BU in core, the OSG usage is not consistent, as the site is not in OIM. |
create a peer in core |
| T3_US_Baylor | Baylor-Kodiak | oim | both | 1 | 1 | Baylor University Tier3 | None | Should usage be OSG? | - |
| T3_US_Brown | brown-cms-new | oim | both | 1 | 1 | Brown-CMS | OSG | - | - |
| T3_US_Colorado | UColorado_HEP | oim | both | 1 | 1 | Colorado | OSG | - | - |
| T3_US_Cornell | NYSGRID_CORNELL_NYS1 | oim | both | 1 | 1 | Cornell | OSG | - | - |
| T3_US_FIT | FLTECH | oim | both | 1 | 1 | FLTECH | OSG | - | - |
| T3_US_FIU | FIUPG | oim | both | 1 | 1 | T3_US_FIU | OSG | - | - |
| T3_US_FNALLPC | USCMS-FNAL-LPC | none | both | FNALLPC | OSG | 1 | 1 | USCMS-FNAL-LPC site is not in OIM. What does OSG usage mean here? | - |
| T3_US_FSU | FSU-HEP | oim | both | 1 | 1 | T3_US_FSU | OSG | - | - |
| T3_US_HEPCloud | T3USHEPCLOUD | none | both | 1 | 1 | T3_US_HEPCloud | other | T3USHEPCLOUD site is not in OIM. The “other” usage could be therefore consistent, provided that we decide what it means. | - |
| T3_US_JHU | T3_US_JHU | none | siteDB | 1 | 1 | JHU | OSG | T3_US_JHU site is not in OIM. What does OSG usage mean here? | - |
| T3_US_Kansas | T3_US_Kansas | none | siteDB | 1 | 1 | Kansas | None | - | - |
| T3_US_MIT | MIT_CMS_T3 | oim | both | 1 | 1 | T3 US MIT | OSG | - | - |
| T3_US_Minnesota | UMN-CMS | oim | both | 1 | 1 | Minnesota | Unknown | Should usage be OSG? | - |
| T3_US_NERSC | t3usnersc | none | siteDB | 1 | 1 | T3 US NERSC | OSG | There are 8 sites in OIM resembling to this one ( e.g. NERSC-ITB, NERSC-Carver, NERSC-Franklin etc). If the CMS site is linked to any of them, the OSG usage is consistent. | - |
| T3_US_NEU | Northeastern | none | siteDB | 1 | 1 | Northeastern | OSG | This is mapped to T3_US_NEU on OIM in CRIC. With this, the OSG usage is consistent. | I believe this has to be corrected on the source and mapped to T3_US_NEU in core |
| T3_US_NU | NU Tier3 | none | both | 1 | 1 | Northwestern | OSG | This should be mapped to NU_CMS_TIER3_CE on OIM in CRIC. With this, the OSG usage is consistent. | - |
| T3_US_NotreDame | NWICG_NDCMS | oim | both | 1 | 1 | NWICG_NDCMS | OSG | - | - |
| T3_US_OSG | T3USOSG | none | siteDB | 7 | 1 | T3_US_OSG | OSG | T3USOSG site is not in OIM. We created it in core CRIC, so the OSG usage is not consistent. | - |
| T3_US_OSG | Clemson-Palmetto | oim | VOFeed | 7 | 1 | - | - | - | map to T3USOSG (to be created in core) as all other entries for this site |
| T3_US_OSG | SU-OG-CE1 | none | VOFeed | 7 | 1 | - | - | - | - |
| T3_US_OSG | MWT2 | oim | VOFeed | 7 | 1 | - | - | - | - |
| T3_US_OSG | BNL-ATLAS | both | VOFeed | 7 | 1 | - | - | - | - |
| T3_US_OSG | AGLT2 | oim | VOFeed | 7 | 1 | - | - | - | - |
| T3_US_OSG | SU-OG-CE | none | VOFeed | 7 | 1 | - | - | - | - |
| T3_US_OSU | osu-cms | oim | both | 1 | 1 | OSU | None | Should usage be OSG? | - |
| T3_US_Omaha | Firefly | oim | both | 1 | 1 | Firefly | OSG | - | This entry will soon disappear. |
| T3_US_Princeton_ARM | T3_US_Princeton_ARM | none | both | 1 | 1 | Princeton ARM | OSG | T3_US_Princeton_ARM site is not in OIM. What does OSG usage mean here? | - |
| T3_US_Princeton_ICSE | T3_US_Princeton_ICSE | none | both | 1 | 1 | Princeton ARM | None | This is mapped to Princeton_ICSE_T3_CMS on OIM in CRIC. Should usage be now OSG? | map to Princeton_ICSE_T3_CMS , might be an error |
| T3_US_PuertoRico | uprm-cms | oim | both | 1 | 1 | UPRM | OSG | - | - |
| T3_US_Rice | Rice | oim | both | 1 | 1 | Rice | OSG | - | - |
| T3_US_Rutgers | rutgers-cms | oim | both | 1 | 1 | Rutgers | OSG | - | - |
| T3_US_SDSC | t3ussdsc | none | siteDB | 2 | 1 | T3 US SDSC | OSG | t3ussdsc site is not in OIM. We created it in core CRIC, so the OSG usage is not consistent. | - |
| T3_US_SDSC | Comet | none | VOFeed | 2 | 1 | - | - | - | map to t3ussdsc |
| T3_US_TACC | t3ustacc | none | siteDB | 2 | 1 | T3_US_TACC | other | We mapped it to the CRIC created t3ussdsc, so now we have both OSG and other as usage for it. Is this expected? Or should we create t3ustacc entry? | map to t3ussdsc |
| T3_US_TACC | Stampede | none | VOFeed | 2 | 1 | - | - | - | - |
| T3_US_TAMU | TAMU_BRAZOS | oim | both | 2 | 1 | - | TAMU | OSG | This is the currently used mapping since we are not yet using VOFeed to populate the db. |
| T3_US_TAMU | TAMU_BRAZOS_CE | none | VOFeed | 2 | 1 | - | - | TAMU_BRAZOS exists in OIM but not TAMU_BRAZOS_CE | map to TAMU_BRAZOS |
| T3_US_TTU | TTU-ANTAEUS | oim | both | 1 | 1 | TTU | OSG | - | - |
| T3_US_UB | NYSGRID-CCR-U2 | oim | siteDB | 1 | 1 | SUNY_BUFFALO | OSG | - | - |
| T3_US_UCD | UCD | oim | both | 1 | 1 | UCD | OSG | - | - |
| T3_US_UCR | UCR-HEP | oim | both | 1 | 1 | UC Riverside | OSG | - | - |
| T3_US_UCSB | ucsb-cms | oim | both | 1 | 1 | UCSB | OSG | - | - |
| T3_US_UIowa | GROW-PROD | oim | siteDB | 1 | 1 | UIowa | OSG | - | - |
| T3_US_UMD | umd-cms | oim | both | 2 | 1 | UMD | OSG | - | This is the currently used mapping since we are not yet using VOFeed to populate the db. |
| T3_US_UMD | umd-ce | none | VOFeed | 2 | 1 | - | - | UMD-IGS-CE appears as a resource of UMD-IGS but also umd-ce appears as a resource of umd-cms (on OIM). | map to umd-cms |
| T3_US_UMiss | UMissHEP | oim | both | 1 | 1 | UMissHEP | OSG | - | - |
| T3_US_UTENN | T3_US_UTENN | none | siteDB | 1 | 1 | UTenn | None | - | - |
| T3_US_UVA | UVA-HEP | none | both | 1 | 1 | UVA | None | Appears as a SRMv2 SE resource on the physical site uva-cms-se in OIM. | - |
| T3_US_Vanderbilt_EC2 | Vanderbilt_EC2 | oim | both | 1 | 1 | Vanderbilt_EC2 | OSG | - | - |
| T3_US_Wisconsin | t3uswisconsin | none | siteDB | 1 | 1 | T3 US Wisconsin | OSG | t3uswisconsin is not in OIM. What does OSG usage mean here? | - |
Edit | Attach | Topic revision: r1 - 2018-02-05 - PanosPaparrigopoulos
LCG Wikis
- ABATBEA
- ACPP
- ADCgroup
- AEGIS
- AfricaMap
- AgileInfrastructure
- ALICE
- AliceEbyE
- AliceSPD
- AliceSSD
- AliceTOF
- AliFemto
- ALPHA
- Altair
- ArdaGrid
- ASACUSA
- AthenaFCalTBAna
- Atlas
- AtlasLBNL
- AXIALPET
- CAE
- CALICE
- CDS
- CENF
- CERNSearch
- CLIC
- Cloud
- CloudServices
- CMS
- Controls
- CTA
- CvmFS
- DB
- DefaultWeb
- DESgroup
- DPHEP
- DM-LHC
- DSSGroup
- EGEE
- EgeePtf
- ELFms
- EMI
- ETICS
- FIOgroup
- FlukaTeam
- Frontier
- Gaudi
- GeneratorServices
- GuidesInfo
- HardwareLabs
- HCC
- HEPIX
- ILCBDSColl
- ILCTPC
- IMWG
- Inspire
- IPv6
- IT
- ItCommTeam
- ITCoord
- ITdeptTechForum
- ITDRP
- ITGT
- ITSDC
- LAr
- LCG
- LCGAAWorkbook
- Leade
- LHCAccess
- LHCAtHome
- LHCb
- LHCgas
- LHCONE
- LHCOPN
- LinuxSupport
- Main
- Medipix
- Messaging
- MPGD
- NA49
- NA61
- NA62
- NTOF
- Openlab
- PDBService
- Persistency
- PESgroup
- Plugins
- PSAccess
- PSBUpgrade
- R2Eproject
- RCTF
- RD42
- RFCond12
- RFLowLevel
- ROXIE
- Sandbox
- SocialActivities
- SPI
- SRMDev
- SSM
- Student
- SuperComputing
- Support
- SwfCatalogue
- TMVA
- TOTEM
- TWiki
- UNOSAT
- Virtualization
- VOBox
- WITCH
- XTCA
 |
|
Copyright &© 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback