Difference: AddCmsSite (1 vs. 66)

Revision 662019-09-17 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 9 to 9
 
https://twiki.cern.ch/twiki/bin/view/CMSPublic/PhedexAdminDocsNewSite#Tier2
-->
Added:
>
>
The instructions below are for the Site Support team to setup a new site. For site executive/admins there is a different twiki with more reference, explanation, etc. here.
 

Requirements

What will you need to be a good site

Revision 652019-09-12 - DaniloPiparo

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Revision 642019-09-06 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 29 to 29
 

Fully Operational Sites

T1s & T2s

Changed:
<
<
  1. CMS secretariat & CMS VO: Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
>
>
  1. CMS secretariat & CMS VO: Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS and needs to be a member of the CERN cms-zh e-group.
 
Changed:
<
<
    • Once you will be a CMS member, you will also need to :
  1. CMS Name: Define a CMS name for site
>
>
  1. CMS Name: Propose a CMS name for the site
 
    • Name should follow the convention: Tier#(T#)_Country(2 letters)_Site(Short). For example: T2_US_FNAL
Changed:
<
<
  1. SiteDB:
>
>
  1. CRIC (old SiteDB setup):
 
    • Send an email to cms-comp-ops-coordinators@cern.ch informing about new site and also ask for last confirmation.
    • Create a ggus ticket (be sure that you are able to create ggus ticket. If you are not, please visit the registration page of the ggus)
      • Type of issue: CMS_Register New CMS Site, CMS Support Unit: CMS SiteDB, subject: Tier-{1, 2, 3} Registration
Changed:
<
<
      • Include the following info:
        Title: Tier: CMS Name: LCG Name: Site Executive: Location: Usage (LCG,OSG,ARC,other): URL: Logo (url): 
           Example   Close   
        <!--/twistyPlugin twikiMakeVisibleInline-->
        Title: MIT Tier: Tier 2 CMS Name: T2_US_MIT LCG Name: MIT_CMS Site Executive: Maxim Goncharov, Wei Li Location: Boston, MA, USA Usage: OSG URL: None Logo: None
        <!--/twistyPlugin-->
      • Please note that you can also provide the following fields (or site executive can fill these fields later on):
        Data Manager: name, e-mail, phone, certificate DN CMS.PhEDEx Contact: name, e-mail, phone, certificate DN Site Admin: name, e-mail, phone, certificate DN 
    • Site Executive should update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
      • Russian Tier-1 might be a good candidate for serving as parent site for Eastern European sites.
    • Instructions for adding your DN to SiteDB and to verify your certificate:
    • If Site Admin has 2 certificates: The Site Admin needs to decide which certificate he/she wants to use and map it in ca.cern.ch.
    • Site Support should make an entry in the Data tab for the site equal to the sitename (required for CRAB-3).
>
>
      • Include the following info:
        Title: Tier: CMS Name: Site Executive: Location:
           Example   Close   
        <!--/twistyPlugin twikiMakeVisibleInline-->
        Title: MIT Tier: Tier 2 CMS Name: T2_US_MIT LCG Name: MIT_CMS Site Executive: Maxim Goncharov, Wei Li Location: Boston, MA, USA Usage: OSG
        <!--/twistyPlugin-->
      • Please note that you can also provide the following fields (or site executive can fill these fields later on):
        Data Manager: name, e-mail; PhEDEx Contact: name, e-mail; Site Admin: name, e-mail
      • Site support team will setup site and facility in CRIC. THere is no need currently for site executives or admins to interact with CRIC if "Data Manager" and "PhEDEx Contact" information is provided in the ticket (or in case the site will not have a PhEDEx endpoint). The "Site Executive" and "Site Admin" lists are CERN e-groups and can be changed here. Put "cms-" into the search field, leave the search set to "begins with", check the "Only groups I own or manage" box and click "Search" to find the admin/exec group of your facility.
 
  1. GIT: Setup GIT and commit files to SITECONF
    • First you need to get the site registered in SiteDB, and then you need to be registered as "Site Admin" of that site.
    • Create a ggus ticket for CMS Site Suport Team with request to create project for your site in SITECONF group.
Line: 87 to 77
 
    • when ready in the production factories, please set the "Processing" field in SiteDB; this will enable your site in CRAB so HammerCloud jobs can run
    • CE has to be whitelisted in the job dashboard. Inform Edward Karavakis or CERN MONIT team.
  1. SAM tests:
Changed:
<
<
If the previous steps were successfully completed, the CMS SAM CE tests should start working.
    • SAM tests are driven by CE and SE information in the VO-feed. (GOCDB and OIM entries are not used.) In case queue information is not explicitly specified in the glide-in WMS entry for the CE (and then the VO-feed will not include queue information for the CE either), SAM ETF takes the queue information from BDII.
>
>
If the previous steps were successfully completed, CMS SAM CE tests should start to appear.
    • SAM tests are driven by CE and SE information in the VO-feed. (GOCDB and MyOSG entries are not used.) In case queue information is not explicitly specified in the glide-in WMS entry for the CE (and then the VO-feed will not include queue information for the CE either), SAM ETF takes the queue information from BDII if available.
 
    • Start debugging the following tests results (not all of the SAM tests):
      1. org.sam.CREAMCE-JobSubmit
      2. org.cms.WN-env
Line: 164 to 154
 
    • HammerCloud test
      • To start test contact Andrea Sciaba to add the site to the appropriate test templates.
  1. Xrootd Architecture - Link
Added:
>
>
    • Please inform the CMS Site Support team, cms-comp-ops-site-support-team@cernNOSPAMPLEASE.ch, about the URI of the xrootd endpoints of your site. This should be the site endpoint(s) (or redirector) that is subscribed to the federation and serves the namespace of the PhEDEx node name (and does not re-direct to other site(s)).
 
  1. CMS VO Feed - Link
Changed:
<
<
    • If the site and its services are correctly registered in the CMS SiteDB, the glide-in WMS factories, and PhEDEx the site will appear in CMS VO feed.
    • The CMS VO feed uses the following information sources:
      • for SEs: PhEDEx
      • for CEs: glide-in WMS factories
>
>
    • If the site is properly registered, i.e. configured in CRIC, glide-in WMS factory entries are defined, PhEDEx configured and agents running, and xrootd endpoints announced, then the site with all it's services will appear in the VO-feed.
    • The CMS VO-feed uses information from:
      • PhEDEx for SEs
      • glide-in WMS factories for CEs
      • from a JSON for xrootd
 
  1. Monitoring:
    • Is the site automatically appearing in Site Status Board?
      • CMS VO Feed is the source for the TopologyMaintenances metric in SSB, it means that if the site is in the CMS VO Feed it will appear in SSB as well.

Revision 632019-02-19 - XiaoweiJiang

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 76 to 76
 
    • If CVMFS is working properly, site could also pass the SAM Frontier test in next steps.
  1. glide-in WMS Subscription
    • CMS uses glide-in WMS to utilize Grid resources. Tier-1 and 2 sites thus need to allow pilot jobs of the glide-in WMS factory to execute on their compute elements.
Changed:
<
<
    • Please open a [[https://ggus.eu/?mode=ticket_cms]CMS GGUS ticket]] for Support Unit "Glidein Factory" and ask the >=48 hour queues of your CEs to be added.
    • Factory operations will likely add them to the integration setup and test that things work first. Don't miss getting them added to the production factories at CERN, Fermilab, GOC, and SDSC.
>
>
    • Please open a [[https://ggus.eu/?mode=ticket_cms]CMS GGUS ticket]] for Support Unit "Glidein Factory", provide the details about your CEs as below and ask the queues of your CEs to be added:
      1. Name of CE
      2. Type of CE
      3. Multi-core or single-core
      4. Wall-time limit
      5. Memory per core
      6. Other special parameters you expected
    • Factory operations will likely add them to the integration setup and test that things work first. Don't miss getting them added to the production factories at CERN, Fermilab, and SDSC.
 
    • when ready in the production factories, please set the "Processing" field in SiteDB; this will enable your site in CRAB so HammerCloud jobs can run
    • CE has to be whitelisted in the job dashboard. Inform Edward Karavakis or CERN MONIT team.
  1. SAM tests:

Revision 622018-07-16 - XiaoweiJiang

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 190 to 190
 
  • 6. Frontier/Squid
    • If more than a few CMSSW jobs will run at the site, a local Squid should be commissioned and registered centrally for monitoring.
    • At the very least, the site must point in it's site-local-config.xml to the CERN Opportunistic Squids cmsopsquid[1,2].cern.ch
Changed:
<
<
  • 7. SAM tests - There won't be any CE related ones if the site only provides SE.
>
>
  • 8. SAM tests - There won't be any CE related ones if the site only provides SE.
 
    • [The SRM test should be addressed though]
  • 12. A Tier-3 has no requirements concerning commissioned links. Note however that data are only transferred on commissioned links. The site has make their plans from where they intend to download and need to commission those links.
  • 15. Since there is no CE there won't be any HC running

Revision 612017-11-13 - RokasMaciulaitis

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 60 to 60
 
Added:
>
>
 
  1. CMSSW/CVMFS:
    • CMS software can be installed locally but this is no longer required. Instead we suggest sites to use the CERN Virtual Machine FileSystem, CVMFS.
Line: 78 to 79
 
    • Please open a [[https://ggus.eu/?mode=ticket_cms]CMS GGUS ticket]] for Support Unit "Glidein Factory" and ask the >=48 hour queues of your CEs to be added.
    • Factory operations will likely add them to the integration setup and test that things work first. Don't miss getting them added to the production factories at CERN, Fermilab, GOC, and SDSC.
    • when ready in the production factories, please set the "Processing" field in SiteDB; this will enable your site in CRAB so HammerCloud jobs can run
Added:
>
>
    • CE has to be whitelisted in the job dashboard. Inform Edward Karavakis or CERN MONIT team.
 
  1. SAM tests: If the previous steps were successfully completed, the CMS SAM CE tests should start working.
    • SAM tests are driven by CE and SE information in the VO-feed. (GOCDB and OIM entries are not used.) In case queue information is not explicitly specified in the glide-in WMS entry for the CE (and then the VO-feed will not include queue information for the CE either), SAM ETF takes the queue information from BDII.
Line: 133 to 135
 
        • The link activation is automatic. Sometimes, however, the link doesn't exist at all - in this case, you will need to contact the transfer team with a ticket before the commissioning asking them to create the link in Prod/Debug/Dev. You can check if the link exists in the PhEDEx Components::Links page.
          • GGUS ticket to Transfer team --> "please commission Links for Site"
          • Specify the links and priority of the commissioning of these links.
Added:
>
>
  1. DDM quota
  2. /store/unmerged/ cleaning
    • Take a look at CMS namespace policy and set up cleaning for /store/unmerged/. With the exception of files belonging to ongoing workflows files older than 2 weeks can be deleted automatically. Still active datasets are published here. Sites are encouraged to take a look at customizable reference implementation
 
  1. HC & SAM tests:
    • Transfer HC & SAM tests samples to site. The datasets are:
      • old SAM dataset: /GenericTTbar/SAM-CMSSW_5_3_1_START53_V5-v1/GEN-SIM-RECO (4 files, 3.4 GB)

Revision 602017-11-10 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 73 to 73
 
Added:
>
>
  1. glide-in WMS Subscription
    • CMS uses glide-in WMS to utilize Grid resources. Tier-1 and 2 sites thus need to allow pilot jobs of the glide-in WMS factory to execute on their compute elements.
    • Please open a [[https://ggus.eu/?mode=ticket_cms]CMS GGUS ticket]] for Support Unit "Glidein Factory" and ask the >=48 hour queues of your CEs to be added.
    • Factory operations will likely add them to the integration setup and test that things work first. Don't miss getting them added to the production factories at CERN, Fermilab, GOC, and SDSC.
    • when ready in the production factories, please set the "Processing" field in SiteDB; this will enable your site in CRAB so HammerCloud jobs can run
 
  1. SAM tests:
Changed:
<
<
If the previous steps were successfully completed, some of the CMS SAM tests should start working.
    • SAM tests are automatically started if the BDII information is correct and the site exists in GOCDB or OIM. In the case of OSG, the CE needs to have a sam_uri entry with the queue information, i.e. something like htcondor://$HOSTNAME:$PORT/$SCHEDDNAME?option1=val1&option2=val2 and the SE needs to have uri_override set in case of non-standard ports (CE: 2119, SRM: 8443, GridFTP: 2811)
>
>
If the previous steps were successfully completed, the CMS SAM CE tests should start working.
    • SAM tests are driven by CE and SE information in the VO-feed. (GOCDB and OIM entries are not used.) In case queue information is not explicitly specified in the glide-in WMS entry for the CE (and then the VO-feed will not include queue information for the CE either), SAM ETF takes the queue information from BDII.
 
    • Start debugging the following tests results (not all of the SAM tests):
      1. org.sam.CREAMCE-JobSubmit
      2. org.cms.WN-env
Line: 83 to 88
 
      1. org.cms.WN-swinst (CVMFS)
      2. org.cms.WN-frontier
      3. org.cms.WN-squid
Deleted:
<
<
  1. glide-in WMS Subscription
    • CMS uses glide-in WMS to utilize Grid resources. Tier-1 and 2 sites thus need to allow pilot jobs of the glide-in WMS factory to execute on their compute elements.
    • Please open a [[https://ggus.eu/?mode=ticket_cms]CMS GGUS ticket]] for Support Unit "Glidein Factory" and ask the >=48 hour queues of your CEs to be added.
    • Factory operations will likely add them to the integration setup and test that things work first. Don't miss getting them added to the production factories at CERN, Fermilab, GOC, and SDSC.
    • when ready in the production factories, please set the "Processing" field in SiteDB; this will enable your site in CRAB so HammerCloud jobs can run
 
  1. PhEDEx Setup
    1. Configure a host to run PhEDEx

Revision 592017-09-05 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 139 to 139
 
      • old HC dataset: /GenericTTbar/HC-CMSSW_7_0_4_START70_V7-v1/GEN-SIM-RECO (185 files, 603.0 GB)
      • new SAM dataset: /GenericTTbar/SAM-CMSSW_9_0_0_90X_mcRun1_realistic_v4-v1/AODSIM (2 files, 2.3 GB)
      • new HC dataset: /GenericTTbar/HC-CMSSW_9_0_0_90X_mcRun1_realistic_v4-v1/AODSIM (47 files, 114.9 GB)
Added:
>
>
      • newest SAM dataset: /GenericTTbar/SAM-CMSSW_9_2_6_91X_mcRun1_realistic_v2-v1/AODSIM (3 files, 2.3 GB)
 
      • newest HC dataset: /GenericTTbar/HC-CMSSW_9_2_6_91X_mcRun1_realistic_v2-v2/AODSIM (46 files, 113.5 GB)
    • The datasets need to be subscribed to the FacOps group (if not, they will be deleted by DDM once the storage of the site gets loaded)!
    • Debug tests results:

Revision 582017-08-02 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 139 to 139
 
      • old HC dataset: /GenericTTbar/HC-CMSSW_7_0_4_START70_V7-v1/GEN-SIM-RECO (185 files, 603.0 GB)
      • new SAM dataset: /GenericTTbar/SAM-CMSSW_9_0_0_90X_mcRun1_realistic_v4-v1/AODSIM (2 files, 2.3 GB)
      • new HC dataset: /GenericTTbar/HC-CMSSW_9_0_0_90X_mcRun1_realistic_v4-v1/AODSIM (47 files, 114.9 GB)
Added:
>
>
      • newest HC dataset: /GenericTTbar/HC-CMSSW_9_2_6_91X_mcRun1_realistic_v2-v2/AODSIM (46 files, 113.5 GB)
 
    • The datasets need to be subscribed to the FacOps group (if not, they will be deleted by DDM once the storage of the site gets loaded)!
    • Debug tests results:
      • Remaining SAM tests:

Revision 572017-07-24 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 91 to 91
 
  1. PhEDEx Setup
    1. Configure a host to run PhEDEx
Added:
>
>
      • ask the CERN DB team/Kate to whitelist the host/punch hole into firewall so host can reach DB machine at CERN
 

Revision 562017-06-16 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 158 to 158
 
    • Is the site automatically appearing in Site Status Board?
      • CMS VO Feed is the source for the TopologyMaintenances metric in SSB, it means that if the site is in the CMS VO Feed it will appear in SSB as well.
      • Having the site in the CMS VO feed doesn't mean that this site will be monitored for every metric in SSB, sometimes the responsible for the metric has to add the site to the test template - for example: HammerCloud test (Andrea Sciaba).
Added:
>
>
      • Set values for the cpubound (160) and iobound (161) metricses. cpubound should be the number of cores of the site and iobound the number of cores that the site can sustain running I/O intensive applications (default 10% of cpubound).
 
    • Is the site automatically appearing in Dashboard?
      • No, Dashboard ops (e.g. Julia) may need to explicitely refresh the import of site names from SiteDB.
    • Is the site automatically appearing in the Site Readiness plots?

Revision 552017-06-07 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 134 to 134
 
          • Specify the links and priority of the commissioning of these links.
  1. HC & SAM tests:
    • Transfer HC & SAM tests samples to site. The datasets are:
Changed:
<
<
      • /GenericTTbar/SAM-CMSSW_9_0_0_90X_mcRun1_realistic_v4-v1/AODSIM (2 files, 2.3 GB)
      • /GenericTTbar/HC-CMSSW_9_0_0_90X_mcRun1_realistic_v4-v1/AODSIM (47 files, 114.9 GB)
>
>
      • old SAM dataset: /GenericTTbar/SAM-CMSSW_5_3_1_START53_V5-v1/GEN-SIM-RECO (4 files, 3.4 GB)
      • old HC dataset: /GenericTTbar/HC-CMSSW_7_0_4_START70_V7-v1/GEN-SIM-RECO (185 files, 603.0 GB)
      • new SAM dataset: /GenericTTbar/SAM-CMSSW_9_0_0_90X_mcRun1_realistic_v4-v1/AODSIM (2 files, 2.3 GB)
      • new HC dataset: /GenericTTbar/HC-CMSSW_9_0_0_90X_mcRun1_realistic_v4-v1/AODSIM (47 files, 114.9 GB)
 
    • The datasets need to be subscribed to the FacOps group (if not, they will be deleted by DDM once the storage of the site gets loaded)!
    • Debug tests results:
      • Remaining SAM tests:

Revision 542017-05-18 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 133 to 133
 
          • GGUS ticket to Transfer team --> "please commission Links for Site"
          • Specify the links and priority of the commissioning of these links.
  1. HC & SAM tests:
Changed:
<
<
    • Transfer HC & SAM tests samples to site. The datasets need to be subscribed to the FacOps group (if not, they will be deleted by DDM once the storage of the site gets loaded)!
>
>
    • Transfer HC & SAM tests samples to site. The datasets are:
      • /GenericTTbar/SAM-CMSSW_9_0_0_90X_mcRun1_realistic_v4-v1/AODSIM (2 files, 2.3 GB)
      • /GenericTTbar/HC-CMSSW_9_0_0_90X_mcRun1_realistic_v4-v1/AODSIM (47 files, 114.9 GB)
    • The datasets need to be subscribed to the FacOps group (if not, they will be deleted by DDM once the storage of the site gets loaded)!
 
    • Debug tests results:
      • Remaining SAM tests:
      1. org.cms.glexec.WN-gLExec

Revision 532017-04-19 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 145 to 145
 
      • To start test contact Andrea Sciaba to add the site to the appropriate test templates.
  1. Xrootd Architecture - Link
  2. CMS VO Feed - Link
Changed:
<
<
    • If the site and its services are correctly registered in CMS SiteDB and BDII the site will appear in CMS VO Feed.
    • The CMS VO Feed uses the following information sources:
      • for SEs: SiteDBv2
      • for CEs: all CEs published in BDII associated or as "close" to the SE
>
>
    • If the site and its services are correctly registered in the CMS SiteDB, the glide-in WMS factories, and PhEDEx the site will appear in CMS VO feed.
    • The CMS VO feed uses the following information sources:
      • for SEs: PhEDEx
      • for CEs: glide-in WMS factories
 
  1. Monitoring:
    • Is the site automatically appearing in Site Status Board?
      • CMS VO Feed is the source for the TopologyMaintenances metric in SSB, it means that if the site is in the CMS VO Feed it will appear in SSB as well.

Revision 522016-12-27 - NataliaRatnikova

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 109 to 109
 
    • Send your grid user public key (usercert.pem) to cms-phedex-admins[AT]cern.ch. You will receive 3 encrypted e-mails containing PhEDEX roles and passwords for Prod, Debug and Dev. You should decode the 3 e-mails using the same certificate you sent and put the 3 outputs in one file to use to connect to PhEDEx TMDB.
    • Access to the PhEDEx database from outside CERN is firewalled, and your hosts will need to be granted access. Please send a mail to Physics-Database.Support AT cern.ch and cms-phedex-admins AT cern.ch asking for your host(s) to be allowed to connect. You should give the name of the domain or subnet that needs access. Ideally this domain/subnet should not contain too many machines, but it should be open enough that you can change hosts without having to repeatedly ask for new holes in the firewall.
    • If a site upgrades to SL6 how to update Phedex?
Changed:
<
<
      • PhEDEx is not distributed through CVMFS, you need to install and configure the PhEDEx agents manually.
>
>
      • Starting from version 4.2.0 PhEDEx is now distributed through CVMFS, but you can still choose to install and configure the PhEDEx agents manually.
 
      • You can find the instructions for SLC6 here: LINK
    • Phedex needs the trivial file catalogue (TFC) of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
  1. SRM test: Debug SRM SAM tests results - org.cms.SRM

Revision 512016-11-08 - RokasMaciulaitis

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 13 to 13
  What will you need to be a good site

Tier2

Changed:
<
<
  • be a good grid site in EGEE or OSG
>
>
  • be a good grid site in EGI or OSG
 
  • a farm with at least one CE (better 2 or more)
  • an SRM (please avoid multiple SE's as much as possible)
  • one machine to run a Squid server (two for a large site with e.g. more then 500 execution slots)

Revision 502016-11-02 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 133 to 133
 
          • GGUS ticket to Transfer team --> "please commission Links for Site"
          • Specify the links and priority of the commissioning of these links.
  1. HC & SAM tests:
Changed:
<
<
    • Transfer HC & SAM tests samples to site.
>
>
    • Transfer HC & SAM tests samples to site. The datasets need to be subscribed to the FacOps group (if not, they will be deleted by DDM once the storage of the site gets loaded)!
 
    • Debug tests results:
      • Remaining SAM tests:
      1. org.cms.glexec.WN-gLExec

Revision 492016-06-03 - RokasMaciulaitis

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 13 to 14
 What will you need to be a good site

Tier2

  • be a good grid site in EGEE or OSG
Changed:
<
<
  • a farm with at least one CE (better 2 or more)
>
>
  • a farm with at least one CE (better 2 or more)
 
  • an SRM (please avoid multiple SE's as much as possible)
  • one machine to run a Squid server (two for a large site with e.g. more then 500 execution slots)
  • a Vobox to run PhEDEx agents
Line: 31 to 32
 
  1. CMS secretariat & CMS VO: Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
Changed:
<
<
      • Get a HyperNews account ((needs a registered CMS member at the site)
>
>
      • Get a HyperNews account ((needs a registered CMS member at the site)
 
  1. CMS Name: Define a CMS name for site
    • Name should follow the convention: Tier#(T#)_Country(2 letters)_Site(Short). For example: T2_US_FNAL
Line: 40 to 41
 
    • Send an email to cms-comp-ops-coordinators@cern.ch informing about new site and also ask for last confirmation.
    • Create a ggus ticket (be sure that you are able to create ggus ticket. If you are not, please visit the registration page of the ggus)
      • Type of issue: CMS_Register New CMS Site, CMS Support Unit: CMS SiteDB, subject: Tier-{1, 2, 3} Registration
Changed:
<
<
      • Include the following info:
        Title:
        Tier:
        CMS Name:
        LCG Name:
        Site Executive:
        Location:
        Usage (LCG,OSG,ARC,other):
        URL:
        Logo (url):
        
           Example   Close   
        <!--/twistyPlugin twikiMakeVisibleInline-->
        Title: MIT Tier: Tier 2 CMS Name: T2_US_MIT LCG Name: MIT_CMS Site Executive: Maxim Goncharov, Wei Li Location: Boston, MA, USA Usage: OSG URL: None Logo: None
        <!--/twistyPlugin-->
      • Please note that you can also provide the following fields (or site executive can fill these fields later on):
        Data Manager: name, e-mail, phone, certificate DN
        CMS.PhEDEx Contact: name, e-mail, phone, certificate DN
        Site Admin: name, e-mail, phone, certificate DN 
>
>
      • Include the following info:
        Title: Tier: CMS Name: LCG Name: Site Executive: Location: Usage (LCG,OSG,ARC,other): URL: Logo (url): 
           Example   Close   
        <!--/twistyPlugin twikiMakeVisibleInline-->
        Title: MIT Tier: Tier 2 CMS Name: T2_US_MIT LCG Name: MIT_CMS Site Executive: Maxim Goncharov, Wei Li Location: Boston, MA, USA Usage: OSG URL: None Logo: None
        <!--/twistyPlugin-->
      • Please note that you can also provide the following fields (or site executive can fill these fields later on):
        Data Manager: name, e-mail, phone, certificate DN CMS.PhEDEx Contact: name, e-mail, phone, certificate DN Site Admin: name, e-mail, phone, certificate DN 
 
    • Site Executive should update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
      • Russian Tier-1 might be a good candidate for serving as parent site for Eastern European sites.
    • Instructions for adding your DN to SiteDB and to verify your certificate:
Line: 74 to 51
 
Changed:
<
<
  1. GIT: Setup GIT and commit files to SITECONF
>
>
  1. GIT: Setup GIT and commit files to SITECONF
 
    • First you need to get the site registered in SiteDB, and then you need to be registered as "Site Admin" of that site.
Changed:
<
<
>
>
 
      • Paths: YOUR_SITE_NAME/JobConfig/site-local-config.xml, YOUR_SITE_NAME/PhEDEx/storage.xml
Changed:
<
<
>
>
 
  1. CMSSW/CVMFS:
    • CMS software can be installed locally but this is no longer required. Instead we suggest sites to use the CERN Virtual Machine FileSystem, CVMFS.
Changed:
<
<
    • CVMFS is a network readonly filesystem, more information, including installation and configuration details, can be found on its twiki page.
>
>
    • CVMFS is a network readonly filesystem, more information, including installation and configuration details, can be found on its twiki page.
 
    • CMS software installations on CVMFS are maintained/managed at CERN.
      • If you add storage.xml and site-local-config.xml files to the siteconf GIT repository they will appear automatically on CVMFS. There is a crontab/script that synchronizes CVMFS every few hours. (If you don't use CVMFS, you need to keep the copies of those files in your local installation in sync with the GIT repository.)
      • The script looks for two files with the names, storage* and site-local-config*.
Line: 107 to 85
 
      1. org.cms.WN-squid
  1. glide-in WMS Subscription
    • CMS uses glide-in WMS to utilize Grid resources. Tier-1 and 2 sites thus need to allow pilot jobs of the glide-in WMS factory to execute on their compute elements.
Changed:
<
<
    • Please open a [[https://ggus.eu/?mode=ticket_cms]CMS GGUS ticket]] for Support Unit "Glidein Factory" and ask the >=48 hour queues of your CEs to be added.
>
>
    • Please open a [[https://ggus.eu/?mode=ticket_cms]CMS GGUS ticket]] for Support Unit "Glidein Factory" and ask the >=48 hour queues of your CEs to be added.
 
    • Factory operations will likely add them to the integration setup and test that things work first. Don't miss getting them added to the production factories at CERN, Fermilab, GOC, and SDSC.
    • when ready in the production factories, please set the "Processing" field in SiteDB; this will enable your site in CRAB so HammerCloud jobs can run
  1. PhEDEx Setup
    1. Configure a host to run PhEDEx
Changed:
<
<
>
>
 
    1. Edit your storage.xml file (needs a registered CMS member at the site)
Line: 132 to 110
 
    • Access to the PhEDEx database from outside CERN is firewalled, and your hosts will need to be granted access. Please send a mail to Physics-Database.Support AT cern.ch and cms-phedex-admins AT cern.ch asking for your host(s) to be allowed to connect. You should give the name of the domain or subnet that needs access. Ideally this domain/subnet should not contain too many machines, but it should be open enough that you can change hosts without having to repeatedly ask for new holes in the firewall.
    • If a site upgrades to SL6 how to update Phedex?
      • PhEDEx is not distributed through CVMFS, you need to install and configure the PhEDEx agents manually.
Changed:
<
<
      • You can find the instructions for SLC6 here: LINK
>
>
      • You can find the instructions for SLC6 here: LINK
 
    • Phedex needs the trivial file catalogue (TFC) of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
  1. SRM test: Debug SRM SAM tests results - org.cms.SRM
    • The site needs working PhEDEx agents to pass these tests.
Line: 165 to 143
 
      1. org.cms.WN-xrootd-fallback
    • HammerCloud test
      • To start test contact Andrea Sciaba to add the site to the appropriate test templates.
Changed:
<
<
  1. Xrootd Architecture - Link
>
>
  1. Xrootd Architecture - Link
 
  1. CMS VO Feed - Link
    • If the site and its services are correctly registered in CMS SiteDB and BDII the site will appear in CMS VO Feed.
    • The CMS VO Feed uses the following information sources:
Line: 184 to 162
 
Changed:
<
<
  1. Waiting Room: Move site out of the SSB Waiting Room
>
>
  1. Waiting Room: Move site out of the SSB Waiting Room
 
  1. Site is ready to work!

T3s

Revision 482016-03-04 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 97 to 97
 
    • If CVMFS is working properly, site could also pass the SAM Frontier test in next steps.
  1. SAM tests: If the previous steps were successfully completed, some of the CMS SAM tests should start working.
Changed:
<
<
    • SAM tests are automatically started if the BDII information is correct and the site exists in GOCDB or OIM. In the case of OSG, the CE needs to have a sam_uri entry with the queue information, i.e. something like htcondor://$HOSTNAME:$PORT/$SCHEDDNAME?option1=val1&option2=val2
>
>
    • SAM tests are automatically started if the BDII information is correct and the site exists in GOCDB or OIM. In the case of OSG, the CE needs to have a sam_uri entry with the queue information, i.e. something like htcondor://$HOSTNAME:$PORT/$SCHEDDNAME?option1=val1&option2=val2 and the SE needs to have uri_override set in case of non-standard ports (CE: 2119, SRM: 8443, GridFTP: 2811)
 
    • Start debugging the following tests results (not all of the SAM tests):
      1. org.sam.CREAMCE-JobSubmit
      2. org.cms.WN-env

Revision 472016-03-04 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 95 to 95
 
Changed:
<
<
  1. SAM tests: If the previous steps were successfully completed, some of the CMS SAM tests should start working.
    • SAM tests are automatically started if the BDII information is correct and the site exists in GOCDB or OIM.
>
>
  1. SAM tests: If the previous steps were successfully completed, some of the CMS SAM tests should start working.
    • SAM tests are automatically started if the BDII information is correct and the site exists in GOCDB or OIM. In the case of OSG, the CE needs to have a sam_uri entry with the queue information, i.e. something like htcondor://$HOSTNAME:$PORT/$SCHEDDNAME?option1=val1&option2=val2
 
    • Start debugging the following tests results (not all of the SAM tests):
      1. org.sam.CREAMCE-JobSubmit
      2. org.cms.WN-env

Revision 462016-03-01 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 73 to 73
 
Added:
>
>
    • Site Support should make an entry in the Data tab for the site equal to the sitename (required for CRAB-3).
 
  1. GIT: Setup GIT and commit files to SITECONF
    • First you need to get the site registered in SiteDB, and then you need to be registered as "Site Admin" of that site.
    • Then you will automatically get permission to push to git

Revision 452016-02-24 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 82 to 82
 
  1. CMSSW/CVMFS:
Changed:
<
<
    • Please note that you don't need to install CMSSW anymore.
    • You should now configure CVMFS and get software releases automatically this way.
      • If you add storage.xml and site-local-config.xml to GIT they should be copied by a script into cvmfs and appear on the client side.
>
>
    • CMS software can be installed locally but this is no longer required. Instead we suggest sites to use the CERN Virtual Machine FileSystem, CVMFS.
    • CVMFS is a network readonly filesystem, more information, including installation and configuration details, can be found on its twiki page.
    • CMS software installations on CVMFS are maintained/managed at CERN.
      • If you add storage.xml and site-local-config.xml files to the siteconf GIT repository they will appear automatically on CVMFS. There is a crontab/script that synchronizes CVMFS every few hours. (If you don't use CVMFS, you need to keep the copies of those files in your local installation in sync with the GIT repository.)
 
      • The script looks for two files with the names, storage* and site-local-config*.
Changed:
<
<
      • Note: this means if you try to test with files named otherwise you will not see them appear in cvmfs!
>
>
      • Note: this means if you name files differently, they will likely not appear automatically on CVMFS!
 
  1. Frontier/Squid: Install and configure Squid for CMS Frontier

Revision 442015-12-16 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 21 to 21
 
    • detailed below

Tier3

Changed:
<
<
  • everything as a T2, but usually at smaller scale and no need to be up 24x7
>
>
  • similar to a T2 but usually at smaller scale
  • no requirement to run CMS Grid jobs; The local batch system does not need to be Grid enabled and can be limited to local users.
  • no need to be up 24x7
 

Fully Operational Sites

T1s & T2s

Line: 101 to 104
 
    • CMS uses glide-in WMS to utilize Grid resources. Tier-1 and 2 sites thus need to allow pilot jobs of the glide-in WMS factory to execute on their compute elements.
    • Please open a [[https://ggus.eu/?mode=ticket_cms]CMS GGUS ticket]] for Support Unit "Glidein Factory" and ask the >=48 hour queues of your CEs to be added.
    • Factory operations will likely add them to the integration setup and test that things work first. Don't miss getting them added to the production factories at CERN, Fermilab, GOC, and SDSC.
Added:
>
>
    • when ready in the production factories, please set the "Processing" field in SiteDB; this will enable your site in CRAB so HammerCloud jobs can run
 
  1. PhEDEx Setup
    1. Configure a host to run PhEDEx
Line: 177 to 181
 
      • New T2 sites will appear in the Waiting Room automatically, explicit action (file editing) is required by Comp Ops to promote them to Production.
  1. Waiting Room: Move site out of the SSB Waiting Room
  2. Site is ready to work!
Added:
>
>
 

T3s

  • Follow the same steps as for T2s except for the following ones which have different instructions depending on the T3:
Changed:
<
<
>
>
  • 3. SiteDB:
    • If you are not Grid-enabling your batch system and accept pilot job from the glide-in WMS factories, then please leave the "Processing" entry in SiteDB blank.
 
  • 5. CMSSW/CVMFS
    • T3s can "skip" this step.
    • However, if the site wants to use the data they host on the Tier3, we should recommend that they install CVMFS on their local machines to get CMSSW.
Line: 187 to 192
 
  • 6. Frontier/Squid
    • If more than a few CMSSW jobs will run at the site, a local Squid should be commissioned and registered centrally for monitoring.
    • At the very least, the site must point in it's site-local-config.xml to the CERN Opportunistic Squids cmsopsquid[1,2].cern.ch
Deleted:
<
<
 
  • 7. SAM tests - There won't be any CE related ones if the site only provides SE.
    • [The SRM test should be addressed though]
Changed:
<
<
  • 13. A Tier-3 has no requirements concerning commissioned links. Note however that data are only transferred on commissioned links. The site has make their plans from where they intend to download and need to commission those links.

  • 14. Since there is no CE there won't be any HC running
  • 16. The VO Feed will miss a CE, which is fine for a SE Tier-3 only.
  • 17. Monitoring for the SE would help the site, but we do not require it.
>
>
  • 12. A Tier-3 has no requirements concerning commissioned links. Note however that data are only transferred on commissioned links. The site has make their plans from where they intend to download and need to commission those links.
  • 15. Since there is no CE there won't be any HC running
  • 17. The VO Feed will miss a CE, which is fine for a SE Tier-3 only.
  • 18. Monitoring for the SE would help the site, but we do not require it.
 

Opportunistic Sites

  • "Opportunistic" means that a site will provide resources without a pledge, which usually means there are no guarantees about availability or it can also mean there is no local CMS support or it can mean the resources are only available for a short time.

Revision 432015-12-15 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 97 to 97
 
      1. org.cms.WN-swinst (CVMFS)
      2. org.cms.WN-frontier
      3. org.cms.WN-squid
Added:
>
>
  1. glide-in WMS Subscription
    • CMS uses glide-in WMS to utilize Grid resources. Tier-1 and 2 sites thus need to allow pilot jobs of the glide-in WMS factory to execute on their compute elements.
    • Please open a [[https://ggus.eu/?mode=ticket_cms]CMS GGUS ticket]] for Support Unit "Glidein Factory" and ask the >=48 hour queues of your CEs to be added.
    • Factory operations will likely add them to the integration setup and test that things work first. Don't miss getting them added to the production factories at CERN, Fermilab, GOC, and SDSC.
 
  1. PhEDEx Setup
    1. Configure a host to run PhEDEx

Revision 422015-07-29 - AliMehmetAltundag

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 187 to 187
 
  • 7. SAM tests - There won't be any CE related ones if the site only provides SE.
    • [The SRM test should be addressed though]
Changed:
<
<
  • 12. A Tier-3 has no requirements concerning commissioned links. Note however that data are only transferred on commissioned links. The site has make their plans from where they intend to download and need to commission those links.
>
>
  • 13. A Tier-3 has no requirements concerning commissioned links. Note however that data are only transferred on commissioned links. The site has make their plans from where they intend to download and need to commission those links.
 
Changed:
<
<
  • 13. Since there is no CE there won't be any HC running
  • 14. The VO Feed will miss a CE, which is fine for a SE Tier-3 only.
  • 15. Monitoring for the SE would help the site, but we do not require it.
>
>
  • 14. Since there is no CE there won't be any HC running
  • 16. The VO Feed will miss a CE, which is fine for a SE Tier-3 only.
  • 17. Monitoring for the SE would help the site, but we do not require it.
 

Opportunistic Sites

  • "Opportunistic" means that a site will provide resources without a pledge, which usually means there are no guarantees about availability or it can also mean there is no local CMS support or it can mean the resources are only available for a short time.

Revision 412015-05-13 - AliMehmetAltundag

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation / Adding a New CMS Site

Line: 73 to 73
 
  1. GIT: Setup GIT and commit files to SITECONF
    • First you need to get the site registered in SiteDB, and then you need to be registered as "Site Admin" of that site.
    • Then you will automatically get permission to push to git
Added:
>
>
 
      • Create site-local-config.xml (TFC) & storage.xml under a subdirectory of the site
Added:
>
>
      • Paths: YOUR_SITE_NAME/JobConfig/site-local-config.xml, YOUR_SITE_NAME/PhEDEx/storage.xml
 
      • Site has to commit the config files to SITECONF.
Deleted:
<
<
 
  1. CMSSW/CVMFS:
    • Please note that you don't need to install CMSSW anymore.

Revision 402015-05-13 - AliMehmetAltundag

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"
Changed:
<
<
    • ---+ Site Support Team - Documentation
      Adding a New CMS Site
>
>

Site Support Team - Documentation / Adding a New CMS Site

 

Revision 392015-05-07 - MericTaze

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"
    • ---+ Site Support Team - Documentation
      Adding a New CMS Site
Line: 116 to 116
 
  1. PhEDEx agents: Configure PhEDEx agents
Added:
>
>
    • Access to the PhEDEx database from outside CERN is firewalled, and your hosts will need to be granted access. Please send a mail to Physics-Database.Support AT cern.ch and cms-phedex-admins AT cern.ch asking for your host(s) to be allowed to connect. You should give the name of the domain or subnet that needs access. Ideally this domain/subnet should not contain too many machines, but it should be open enough that you can change hosts without having to repeatedly ask for new holes in the firewall.
 
    • If a site upgrades to SL6 how to update Phedex?
      • PhEDEx is not distributed through CVMFS, you need to install and configure the PhEDEx agents manually.
      • You can find the instructions for SLC6 here: LINK

Revision 382015-05-06 - AliMehmetAltundag

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"
Changed:
<
<

Site Support Team - Documentation
Adding a New CMS Site

>
>
    • ---+ Site Support Team - Documentation
      Adding a New CMS Site
 
Line: 9 to 9
 
https://twiki.cern.ch/twiki/bin/view/CMSPublic/PhedexAdminDocsNewSite#Tier2
-->
Added:
>
>

Requirements

What will you need to be a good site

Tier2

  • be a good grid site in EGEE or OSG
  • a farm with at least one CE (better 2 or more)
  • an SRM (please avoid multiple SE's as much as possible)
  • one machine to run a Squid server (two for a large site with e.g. more then 500 execution slots)
  • a Vobox to run PhEDEx agents
  • firewall permission for Squid and job monitoring
    • detailed below

Tier3

  • everything as a T2, but usually at smaller scale and no need to be up 24x7
 

Fully Operational Sites

Added:
>
>
 

T1s & T2s

  1. CMS secretariat & CMS VO: Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
Line: 13 to 27
 

T1s & T2s

  1. CMS secretariat & CMS VO: Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
Added:
>
>
    • Once you will be a CMS member, you will also need to :
 
  1. CMS Name: Define a CMS name for site
  2. SiteDB:
Changed:
<
<
    • Send an email to cms-comp-ops-coordinators@cern.ch informing about new site.
>
>
    • Send an email to cms-comp-ops-coordinators@cern.ch informing about new site and also ask for last confirmation.
 
    • Create a ggus ticket (be sure that you are able to create ggus ticket. If you are not, please visit the registration page of the ggus)
      • Type of issue: CMS_Register New CMS Site, CMS Support Unit: CMS SiteDB, subject: Tier-{1, 2, 3} Registration
      • Include the following info:
        
        
Line: 42 to 59
 Logo: None </>
<!--/twistyPlugin-->
Added:
>
>
      • Please note that you can also provide the following fields (or site executive can fill these fields later on):
        Data Manager: name, e-mail, phone, certificate DN
        CMS.PhEDEx Contact: name, e-mail, phone, certificate DN
        Site Admin: name, e-mail, phone, certificate DN 
 
    • Site Executive should update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
      • Russian Tier-1 might be a good candidate for serving as parent site for Eastern European sites.
    • Instructions for adding your DN to SiteDB and to verify your certificate:
Line: 49 to 70
 
Changed:
<
<
  1. GIT: Setup GIT and commit files to SITECONF
>
>
  1. GIT: Setup GIT and commit files to SITECONF
 
    • First you need to get the site registered in SiteDB, and then you need to be registered as "Site Admin" of that site.
    • Then you will automatically get permission to push to git
      • Create site-local-config.xml (TFC) & storage.xml under a subdirectory of the site
Changed:
<
<
      • Site has to commit the config files to SITECONF.
>
>
      • Site has to commit the config files to SITECONF.
 
      • Site admins/executives get access to siteconf automatically and can go ahead and create the directory for their site.
Changed:
<
<
>
>
 
  1. CMSSW/CVMFS:
    • Please note that you don't need to install CMSSW anymore.
    • You should now configure CVMFS and get software releases automatically this way.
Line: 75 to 97
 
      1. org.cms.WN-swinst (CVMFS)
      2. org.cms.WN-frontier
      3. org.cms.WN-squid
Changed:
<
<
  1. Phedex entry (node) & links: (This is done manually)
    • Send a new GGUS ticket to Transfer team (cmscompinfrasup-datatransfer squad) --> "please create Site node & links in Phedex".
>
>
  1. PhEDEx Setup
    1. Configure a host to run PhEDEx
    2. Edit your storage.xml file (needs a registered CMS member at the site)
  2. PhEDEx entry (node) & links: (This is done manually)
    • Open a new GGUS ticket to Transfer team (cmscompinfrasup-datatransfer squad) --> "please create Site node & links in Phedex" with the following information:
      • Storage Element host (e.g. cmsdcache.pi.infn.it)
      • Storage Element kind (e.g. Buffer, MSS, Disk)
      • Storage Element technology (e.g. dCache, Castor, DPM, Disk, Other)
 
    • In this step we can request to create Links as well (not link commissioning)
      • For T3s we don't create all links but only specific requested links - ask which ones.
    • Please add the phedex-node name in the local-stage-out section of the site-local-config.xml file.
  1. PhEDEx agents: Configure PhEDEx agents
Changed:
<
<
    • Contact Tony Wildish for the DBParam role creation. He is the PhEDEx database Admin who can generate the DBParam files for the site.
>
>
    • Send your grid user public key (usercert.pem) to cms-phedex-admins[AT]cern.ch. You will receive 3 encrypted e-mails containing PhEDEX roles and passwords for Prod, Debug and Dev. You should decode the 3 e-mails using the same certificate you sent and put the 3 outputs in one file to use to connect to PhEDEx TMDB.
 
    • If a site upgrades to SL6 how to update Phedex?
      • PhEDEx is not distributed through CVMFS, you need to install and configure the PhEDEx agents manually.
      • You can find the instructions for SLC6 here: LINK
Line: 93 to 126
 
    • Either create one from scratch or copy an existing one from another site, as detailed in the "Downloading_a_LoadTest07_sample" section of this twiki:
    • If the site is a T3, will it be used for MonteCarlo production? If not, it doesn't need the source loadtest dataset to be created and injected, only export links need the source loadtest datasets. T3s usually have import links only.
Changed:
<
<
  1. Link commissioning:
>
>
  1. PhEDEx Link commissioning:
    • Please be sure that your PhEDEx Debug agents are running before starting link commissioning procedure
 

Revision 372015-04-30 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 17 to 17
 
  1. SiteDB:
Changed:
<
<
    • Send an email to cms-comp-ops-site-support-team@cern.ch CC cms-comp-ops-coordinators@cern.ch informing about new site.
    • When you get the confirmation, create a ggus ticket (be sure that you are able to create ggus ticket. If you are not, please visit the registration page of the ggus)
>
>
    • Send an email to cms-comp-ops-coordinators@cern.ch informing about new site.
    • Create a ggus ticket (be sure that you are able to create ggus ticket. If you are not, please visit the registration page of the ggus)
 
      • Type of issue: CMS_Register New CMS Site, CMS Support Unit: CMS SiteDB, subject: Tier-{1, 2, 3} Registration
      • Include the following info:
        Title:
        
        
Line: 80 to 79
 
    • Send a new GGUS ticket to Transfer team (cmscompinfrasup-datatransfer squad) --> "please create Site node & links in Phedex".
    • In this step we can request to create Links as well (not link commissioning)
      • For T3s we don't create all links but only specific requested links - ask which ones.
Changed:
<
<
    • Please add the phesdex-node name in the local-stage-out section of the site-local-config.xml file.
>
>
    • Please add the phedex-node name in the local-stage-out section of the site-local-config.xml file.
 
  1. PhEDEx agents: Configure PhEDEx agents

Revision 362015-04-30 - StephanLammel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 53 to 53
 
  1. GIT: Setup GIT and commit files to SITECONF
    • First you need to get the site registered in SiteDB, and then you need to be registered as "Site Admin" of that site.
    • Then you will automatically get permission to push to git
Changed:
<
<
      • Create site-local-config.xml (TFC) & storage.xml
>
>
      • Create site-local-config.xml (TFC) & storage.xml under a subdirectory of the site
 
  1. CMSSW/CVMFS:
    • Please note that you don't need to install CMSSW anymore.
Changed:
<
<
    • You should now configure CVMFS to get software releases automatically instead.
      • If you add storage.xml and site-local-config.xml to GIT they should appear on the cvmfs client side.
>
>
    • You should now configure CVMFS and get software releases automatically this way.
      • If you add storage.xml and site-local-config.xml to GIT they should be copied by a script into cvmfs and appear on the client side.
 
      • The script looks for two files with the names, storage* and site-local-config*.
      • Note: this means if you try to test with files named otherwise you will not see them appear in cvmfs!
  1. Frontier/Squid: Install and configure Squid for CMS Frontier
Line: 80 to 80
 
    • Send a new GGUS ticket to Transfer team (cmscompinfrasup-datatransfer squad) --> "please create Site node & links in Phedex".
    • In this step we can request to create Links as well (not link commissioning)
      • For T3s we don't create all links but only specific requested links - ask which ones.
Added:
>
>
    • Please add the phesdex-node name in the local-stage-out section of the site-local-config.xml file.
 
  1. PhEDEx agents: Configure PhEDEx agents
Changed:
<
<
    • Phedex needs the TFC of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
>
>
    • Phedex needs the trivial file catalogue (TFC) of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
 
  1. SRM test: Debug SRM SAM tests results - org.cms.SRM
    • The site needs working PhEDEx agents to pass these tests.
  2. LoadTest07 samples: Create and Inject LoadTest07 samples

Revision 352015-04-23 - AliMehmetAltundag

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 19 to 19
 
  1. SiteDB:
    • Send an email to cms-comp-ops-site-support-team@cern.ch CC cms-comp-ops-coordinators@cern.ch informing about new site.
    • When you get the confirmation, create a ggus ticket (be sure that you are able to create ggus ticket. If you are not, please visit the registration page of the ggus)
Changed:
<
<
      • Type of issue: CMS_Register New CMS Site, CMS Support Unit: CMS SiteDB, subject: Tier-X{1, 2, 3} Registration
>
>
      • Type of issue: CMS_Register New CMS Site, CMS Support Unit: CMS SiteDB, subject: Tier-{1, 2, 3} Registration
 
      • Include the following info:
        Title:
        Tier:
        
        

Revision 342015-03-04 - AliMehmetAltundag

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 15 to 15
 
  1. CMS Name: Define a CMS name for site
    • Name should follow the convention: Tier#(T#)_Country(2 letters)_Site(Short). For example: T2_US_FNAL
Changed:
<
<
>
>
 
  1. SiteDB:
Changed:
<
<
    • Send an email to cms-comp-ops-site-support-team@cern.ch CC: cms-comp-ops-coordinators@cern.ch informing about new site.
>
>
    • Send an email to cms-comp-ops-site-support-team@cern.ch CC cms-comp-ops-coordinators@cern.ch informing about new site.
 
    • When you get the confirmation, create a ggus ticket (be sure that you are able to create ggus ticket. If you are not, please visit the registration page of the ggus)
Changed:
<
<
      • Type of issue: CMS_Register New CMS Site, CMS Support Unit: CMS SiteDB, subject: Tier-X Registration
>
>
      • Type of issue: CMS_Register New CMS Site, CMS Support Unit: CMS SiteDB, subject: Tier-X{1, 2, 3} Registration
 
      • Include the following info:
        Title:
        Tier:
        
        

Revision 332015-03-04 - AliMehmetAltundag

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 14 to 14
 
  1. CMS secretariat & CMS VO: Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
  2. CMS Name: Define a CMS name for site
Changed:
<
<
    • Name should follow the convention: Tier#(T#)_Country(2 letters)_Site(Short). For example: T2_US_FNAL (Contact Site Support Team to confirm name)
    • Contact Ken Bloom to confirm the new name is correct and does not present any problems.
>
>
 
  1. SiteDB:
Changed:
<
<
    • Add new site to SiteDB: contact Site Support to create Site (open GGUS ticket)
    • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinators informing about new site.
    • Once the site has been created please reassign the same GGUS ticket to SiteDB to inform about the creation of the site.
      • Include the following info
        Tier
        Title
        CMS Name
        LCG Name
        Site Executive
        Location
        Usage (LCG,OSG,ARC,other)
        URL
        Logo (url) 
    • Contact SiteExecutive so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
>
>
    • Send an email to cms-comp-ops-site-support-team@cern.ch CC: cms-comp-ops-coordinators@cern.ch informing about new site.
    • When you get the confirmation, create a ggus ticket (be sure that you are able to create ggus ticket. If you are not, please visit the registration page of the ggus)
      • Type of issue: CMS_Register New CMS Site, CMS Support Unit: CMS SiteDB, subject: Tier-X Registration
      • Include the following info:
        Title:
        Tier:
        CMS Name:
        LCG Name:
        Site Executive:
        Location:
        Usage (LCG,OSG,ARC,other):
        URL:
        Logo (url):
        
           Example   Close   
        <!--/twistyPlugin twikiMakeVisibleInline-->
        Title: MIT Tier: Tier 2 CMS Name: T2_US_MIT LCG Name: MIT_CMS Site Executive: Maxim Goncharov, Wei Li Location: Boston, MA, USA Usage: OSG URL: None Logo: None
        <!--/twistyPlugin-->

    • Site Executive should update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
 

Revision 322015-01-14 - AliMehmetAltundag

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Changed:
<
<

Pre-requisites

>
>
<!-- ---++ Pre-requisites
  https://twiki.cern.ch/twiki/bin/view/CMSPublic/PhedexAdminDocsNewSite#Tier2
Added:
>
>
-->
 

Fully Operational Sites

T1s & T2s

Revision 312014-11-25 - LuisLinares

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 131 to 131
 
    • However, if the site wants to use the data they host on the Tier3, we should recommend that they install CVMFS on their local machines to get CMSSW.

  • 6. Frontier/Squid
Changed:
<
<
    • If more than a few dozens of nodes will run at the site, a local Squid should be commissioned and registered centrally for monitoring.
>
>
    • If more than a few CMSSW jobs will run at the site, a local Squid should be commissioned and registered centrally for monitoring.
 
    • At the very least, the site must point in it's site-local-config.xml to the CERN Opportunistic Squids cmsopsquid[1,2].cern.ch

  • 7. SAM tests - There won't be any CE related ones if the site only provides SE.

Revision 302014-11-25 - LuisLinares

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 131 to 131
 
    • However, if the site wants to use the data they host on the Tier3, we should recommend that they install CVMFS on their local machines to get CMSSW.

  • 6. Frontier/Squid
Changed:
<
<
    • T3s can "skip" this step.
    • However, if the site wants to use the data they host on the Tier3, we should recommend that they install a Squid, but registering it centrally is optional.
>
>
    • If more than a few dozens of nodes will run at the site, a local Squid should be commissioned and registered centrally for monitoring.
    • At the very least, the site must point in it's site-local-config.xml to the CERN Opportunistic Squids cmsopsquid[1,2].cern.ch
 
  • 7. SAM tests - There won't be any CE related ones if the site only provides SE.
    • [The SRM test should be addressed though]
Line: 170 to 170
 
    • If the site will provide a big amount of resources or will provide them for quite long time it is probably better to add them as a new CMS Site.
  1. Make sure that the site provides a way to access the resources via glideInWMS (which should exist if it's a grid site)
  2. No SITECONF changes needed
Changed:
<
<
  1. Contact Alison McCrea <alison.jean.mc.crea@cern.ch>
    • to configure the existing glideInWMS factory entry to access the # of slots that the site will provide.
    • to take that factory entry and add it to the T3_US_Parrot or T3_EU_Parrot group
>
>
  1. Contact the CMS GlideinWMS Parrot support list
    • To configure the existing glideInWMS factory entry to access the number of slots that the site will provide.
    • To take that factory entry and add it to the T3_US_Parrot or T3_EU_Parrot group
 
  1. Jobs will be submitted to these resources.
  • The modifications are only in the glideInWMS system and they are completely hidden within the glideInWMS system
    • This is a problem for monitoring: all of our system would not know about what's inside T3_US_Parrot, that you added or removed some resources. They just see a collection of resources called T3_US_Parrot which could be anything and anywhere.

Revision 292014-11-05 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 45 to 45
 
  1. CMSSW/CVMFS:
    • Please note that you don't need to install CMSSW anymore.
    • You should now configure CVMFS to get software releases automatically instead.
Added:
>
>
      • If you add storage.xml and site-local-config.xml to GIT they should appear on the cvmfs client side.
      • The script looks for two files with the names, storage* and site-local-config*.
      • Note: this means if you try to test with files named otherwise you will not see them appear in cvmfs!
 
  1. Frontier/Squid: Install and configure Squid for CMS Frontier

Revision 282014-10-29 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 16 to 16
 
    • Name should follow the convention: Tier#(T#)_Country(2 letters)_Site(Short). For example: T2_US_FNAL (Contact Site Support Team to confirm name)
    • Contact Ken Bloom to confirm the new name is correct and does not present any problems.
  1. SiteDB:
Changed:
<
<
    • Add new site to SiteDB: contact Site Support to create Site
>
>
    • Add new site to SiteDB: contact Site Support to create Site (open GGUS ticket)
 
    • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinators informing about new site.
Added:
>
>
    • Once the site has been created please reassign the same GGUS ticket to SiteDB to inform about the creation of the site.
 
      • Include the following info
        Tier
        Title
        CMS Name
        
        

Revision 272014-09-22 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 98 to 98
 
      1. org.cms.WN-xrootd-fallback
    • HammerCloud test
      • To start test contact Andrea Sciaba to add the site to the appropriate test templates.
Added:
>
>
  1. Xrootd Architecture - Link
 
  1. CMS VO Feed - Link
    • If the site and its services are correctly registered in CMS SiteDB and BDII the site will appear in CMS VO Feed.
    • The CMS VO Feed uses the following information sources:

Revision 262014-08-04 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 18 to 18
 
  1. SiteDB:
    • Add new site to SiteDB: contact Site Support to create Site
    • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinators informing about new site.
Changed:
<
<
      • Include the following info
        Tier Title CMS Name LCG Name Site Executive Location Usage (LCG,OSG,ARC,other) URL Logo (url) 
>
>
      • Include the following info
        Tier
        Title
        CMS Name
        LCG Name
        Site Executive
        Location
        Usage (LCG,OSG,ARC,other)
        URL
        Logo (url) 
 
    • Contact SiteExecutive so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
      • Russian Tier-1 might be a good candidate for serving as parent site for Eastern European sites.
    • Instructions for adding your DN to SiteDB and to verify your certificate:
Line: 28 to 36
 
      • Make sure is the only certificate registered here, because some of our systems wouldn't work otherwise.
  1. GIT: Setup GIT and commit files to SITECONF
    • First you need to get the site registered in SiteDB, and then you need to be registered as "Site Admin" of that site.
Changed:
<
<
    • Then you will automatically get permission to push the siteconf for T3_TH_CHULA to git
>
>
    • Then you will automatically get permission to push to git
 
      • Create site-local-config.xml (TFC) & storage.xml
      • Site has to commit the config files to SITECONF.
      • Site admins/executives get access to siteconf automatically and can go ahead and create the directory for their site.

Revision 252014-08-04 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 27 to 27
 
  1. GIT: Setup GIT and commit files to SITECONF
Added:
>
>
    • First you need to get the site registered in SiteDB, and then you need to be registered as "Site Admin" of that site.
    • Then you will automatically get permission to push the siteconf for T3_TH_CHULA to git
 
    • Create site-local-config.xml (TFC) & storage.xml
    • Site has to commit the config files to SITECONF.
      • Site admins/executives get access to siteconf automatically and can go ahead and create the directory for their site.

Revision 242014-07-31 - AlisonMcCrea

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 9 to 10
 

Fully Operational Sites

T1s & T2s

Changed:
<
<
  1. CMS secretariat & CMS VO: Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
>
>
  1. CMS secretariat & CMS VO: Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
 
Changed:
<
<
  1. CMS Name: Define a CMS name for site
>
>
  1. CMS Name: Define a CMS name for site
 
    • Name should follow the convention: Tier#(T#)_Country(2 letters)_Site(Short). For example: T2_US_FNAL (Contact Site Support Team to confirm name)
Changed:
<
<
    • Contact Ken Bloom <kenbloom@unl.edu> to confirm the new name is correct and does not present any problems.
  1. SiteDB:
>
>
    • Contact Ken Bloom to confirm the new name is correct and does not present any problems.
  1. SiteDB:
 
    • Add new site to SiteDB: contact Site Support to create Site
    • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinators informing about new site.
Changed:
<
<
      • Include the following info
        Tier	
        Title	
        CMS Name	
        LCG Name	
        Site Executive	
        Location	
        Usage  (LCG,OSG,ARC,other)
        URL	
        Logo (url)
        
>
>
      • Include the following info
        Tier Title CMS Name LCG Name Site Executive Location Usage (LCG,OSG,ARC,other) URL Logo (url) 
 
    • Contact SiteExecutive so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
      • Russian Tier-1 might be a good candidate for serving as parent site for Eastern European sites.
    • Instructions for adding your DN to SiteDB and to verify your certificate:
Line: 35 to 26
 
Changed:
<
<
  1. GIT: Setup GIT and commit files to SITECONF
>
>
  1. GIT: Setup GIT and commit files to SITECONF
 
Changed:
<
<
  1. CMSSW/CVMFS:
>
>
  1. CMSSW/CVMFS:
 
    • Please note that you don't need to install CMSSW anymore.
    • You should now configure CVMFS to get software releases automatically instead.
Changed:
<
<
  1. Frontier/Squid: Install and configure Squid for CMS Frontier
>
>
  1. Frontier/Squid: Install and configure Squid for CMS Frontier
 
Changed:
<
<
  1. SAM tests: If the previous steps were successfully completed, some of the CMS SAM tests should start working.
>
>
  1. SAM tests: If the previous steps were successfully completed, some of the CMS SAM tests should start working.
 
    • SAM tests are automatically started if the BDII information is correct and the site exists in GOCDB or OIM.
    • Start debugging the following tests results (not all of the SAM tests):
      1. org.sam.CREAMCE-JobSubmit
Line: 56 to 47
 
      1. org.cms.WN-swinst (CVMFS)
      2. org.cms.WN-frontier
      3. org.cms.WN-squid
Changed:
<
<
  1. Phedex entry (node) & links: (This is done manually)
>
>
  1. Phedex entry (node) & links: (This is done manually)
 
    • Send a new GGUS ticket to Transfer team (cmscompinfrasup-datatransfer squad) --> "please create Site node & links in Phedex".
    • In this step we can request to create Links as well (not link commissioning)
      • For T3s we don't create all links but only specific requested links - ask which ones.
Changed:
<
<
  1. PhEDEx agents: Configure PhEDEx agents
>
>
  1. PhEDEx agents: Configure PhEDEx agents
 
Changed:
<
<
    • Contact Tony Wildish <Tony.Wildish@cern.ch> for the DBParam role creation. He is the PhEDEx database Admin who can generate the DBParam files for the site.
>
>
    • Contact Tony Wildish for the DBParam role creation. He is the PhEDEx database Admin who can generate the DBParam files for the site.
 
    • If a site upgrades to SL6 how to update Phedex?
      • PhEDEx is not distributed through CVMFS, you need to install and configure the PhEDEx agents manually.
      • You can find the instructions for SLC6 here: LINK
    • Phedex needs the TFC of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
Changed:
<
<
  1. SRM test: Debug SRM SAM tests results - org.cms.SRM
>
>
  1. SRM test: Debug SRM SAM tests results - org.cms.SRM
 
    • The site needs working PhEDEx agents to pass these tests.
Changed:
<
<
  1. LoadTest07 samples: Create and Inject LoadTest07 samples
>
>
  1. LoadTest07 samples: Create and Inject LoadTest07 samples
 
    • Either create one from scratch or copy an existing one from another site, as detailed in the "Downloading_a_LoadTest07_sample" section of this twiki:
    • If the site is a T3, will it be used for MonteCarlo production? If not, it doesn't need the source loadtest dataset to be created and injected, only export links need the source loadtest datasets. T3s usually have import links only.
Changed:
<
<
  1. Link commissioning:
>
>
  1. Link commissioning:
 
Line: 86 to 77
 
        • The link activation is automatic. Sometimes, however, the link doesn't exist at all - in this case, you will need to contact the transfer team with a ticket before the commissioning asking them to create the link in Prod/Debug/Dev. You can check if the link exists in the PhEDEx Components::Links page.
          • GGUS ticket to Transfer team --> "please commission Links for Site"
          • Specify the links and priority of the commissioning of these links.
Changed:
<
<
  1. HC & SAM tests:
>
>
  1. HC & SAM tests:
 
    • Transfer HC & SAM tests samples to site.
    • Debug tests results:
      • Remaining SAM tests:
Line: 97 to 88
 
      1. org.cms.WN-xrootd-fallback
    • HammerCloud test
      • To start test contact Andrea Sciaba to add the site to the appropriate test templates.
Changed:
<
<
  1. CMS VO Feed - Link
>
>
  1. CMS VO Feed - Link
 
    • If the site and its services are correctly registered in CMS SiteDB and BDII the site will appear in CMS VO Feed.
    • The CMS VO Feed uses the following information sources:
      • for SEs: SiteDBv2
      • for CEs: all CEs published in BDII associated or as "close" to the SE
Changed:
<
<
  1. Monitoring:
>
>
  1. Monitoring:
 
    • Is the site automatically appearing in Site Status Board?
      • CMS VO Feed is the source for the TopologyMaintenances metric in SSB, it means that if the site is in the CMS VO Feed it will appear in SSB as well.
      • Having the site in the CMS VO feed doesn't mean that this site will be monitored for every metric in SSB, sometimes the responsible for the metric has to add the site to the test template - for example: HammerCloud test (Andrea Sciaba).
Line: 115 to 106
 
Changed:
<
<
  1. Waiting Room: Move site out of the SSB Waiting Room
  2. Site is ready to work!
>
>
  1. Waiting Room: Move site out of the SSB Waiting Room
  2. Site is ready to work!
 

T3s

  • Follow the same steps as for T2s except for the following ones which have different instructions depending on the T3:
Line: 142 to 133
 
  • For sites with a small amount of resources, we don't want to create a new CMS site, because there are administrative and operational overheads attached to having a larger number of CMS sites.
  • For sites with larger amount of resources, often the the time period we get them is too short to go through the whole process of adding a new CMS site (could take up to 2 weeks or more).
  • Only for opportunistic sites that provide a large amount of resources for an extended period of time it is worthwhile to go through the whole process of adding a new CMS site.
Deleted:
<
<
 Under opportunistic we define two types of sites:
Changed:
<
<
  1. Fully opportunistic:
>
>
  1. Fully opportunistic:
 
    • A site that is not part of CMS and that has no local CMS support.
    • We can add resources dynamically to an existing meta-site:
      • T3_US_Parrot
Line: 155 to 145
 
    • The dynamic model is useful for adding/removing little amount of resources frequently, just reconfiguring the frontend/factory.
    • Beyond a certain amount of resources it introduces inflexibility in how we can assign work to these resources.
    • A meta-site with much more than 10,000 slots is a bit unwieldy (if we ever get there we can split this up further into more meta-sites).
Changed:
<
<
  1. Semi-opportunistic
>
>
  1. Semi-opportunistic
 
    • An already existing CMS site that wants to provide extra resources for a short period of time.
    • Contact the production/analysis teams to assign more work to this site.

Fully Opportunistic

Changed:
<
<
  1. Confirm that the site has authorization and that has contacted the corresponding people (ask Oliver Gutsche).
  2. Confirm the amount of resources that the site will provide and for how long.
>
>
  1. Confirm that the site has authorization and that has contacted the corresponding people (ask Oliver Gutsche).
  2. Confirm the amount of resources that the site will provide and for how long.
 
    • If the site will provide a big amount of resources or will provide them for quite long time it is probably better to add them as a new CMS Site.
Changed:
<
<
  1. Make sure that the site provides a way to access the resources via glideInWMS (which should exist if it's a grid site)
  2. No SITECONF changes needed
  3. Contact Alison McCrea <alisonjm@gmail.com>
>
>
  1. Make sure that the site provides a way to access the resources via glideInWMS (which should exist if it's a grid site)
  2. No SITECONF changes needed
  3. Contact Alison McCrea <alison.jean.mc.crea@cern.ch>
 
    • to configure the existing glideInWMS factory entry to access the # of slots that the site will provide.
    • to take that factory entry and add it to the T3_US_Parrot or T3_EU_Parrot group
Changed:
<
<
  1. Jobs will be submitted to these resources.
>
>
  1. Jobs will be submitted to these resources.
 
  • The modifications are only in the glideInWMS system and they are completely hidden within the glideInWMS system
    • This is a problem for monitoring: all of our system would not know about what's inside T3_US_Parrot, that you added or removed some resources. They just see a collection of resources called T3_US_Parrot which could be anything and anywhere.
  • SAM and HC tests. We don't need to run those tests at T3_US_Parrot.

Revision 232014-06-30 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 36 to 36
 
  1. GIT: Setup GIT and commit files to SITECONF
Changed:
<
<
    • Create site-local-config.xml & storage.xml
>
>
    • Create site-local-config.xml (TFC) & storage.xml
 
Line: 47 to 47
 
Deleted:
<
<
    • Part of installing Frontier involves creating site-local-config.xml which is certainly necessary for other things.
 
  1. SAM tests: If the previous steps were successfully completed, some of the CMS SAM tests should start working.
    • SAM tests are automatically started if the BDII information is correct and the site exists in GOCDB or OIM.
    • Start debugging the following tests results (not all of the SAM tests):
Line: 58 to 57
 
      1. org.cms.WN-frontier
      2. org.cms.WN-squid
  1. Phedex entry (node) & links: (This is done manually)
Changed:
<
<
    • Send a new Savannah ticket to Transfer team (cmscompinfrasup-datatransfer squad) --> "please create Site node & links in Phedex".
>
>
    • Send a new GGUS ticket to Transfer team (cmscompinfrasup-datatransfer squad) --> "please create Site node & links in Phedex".
 
    • In this step we can request to create Links as well (not link commissioning)
      • For T3s we don't create all links but only specific requested links - ask which ones.
  1. PhEDEx agents: Configure PhEDEx agents
Line: 85 to 84
 
Changed:
<
<
          • Savannah ticket to Transfer team --> "please commission Links for Site"
>
>
          • GGUS ticket to Transfer team --> "please commission Links for Site"
 
          • Specify the links and priority of the commissioning of these links.
Deleted:
<
<
 
  1. HC & SAM tests:
    • Transfer HC & SAM tests samples to site.
    • Debug tests results:

Revision 222014-05-15 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 17 to 17
 
  1. SiteDB:
    • Add new site to SiteDB: contact Site Support to create Site
    • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinators informing about new site.
Added:
>
>
      • Include the following info
        Tier	
        Title	
        CMS Name	
        LCG Name	
        Site Executive	
        Location	
        Usage  (LCG,OSG,ARC,other)
        URL	
        Logo (url)
        
 
    • Contact SiteExecutive so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
      • Russian Tier-1 might be a good candidate for serving as parent site for Eastern European sites.
    • Instructions for adding your DN to SiteDB and to verify your certificate:

Revision 212014-01-14 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 109 to 109
 
  1. Waiting Room: Move site out of the SSB Waiting Room
  2. Site is ready to work!

T3s

Added:
>
>
  • Follow the same steps as for T2s except for the following ones which have different instructions depending on the T3:
 
  • 5. CMSSW/CVMFS
Added:
>
>
    • T3s can "skip" this step.
    • However, if the site wants to use the data they host on the Tier3, we should recommend that they install CVMFS on their local machines to get CMSSW.
 
  • 6. Frontier/Squid
Changed:
<
<
    • T3s can "skip" both.
    • However, if the site wants to use the data they host on the Tier3, we should recommend that they install CVMFS on their local machines to get CMSSW and also a Squid, where registering it centrally is optional.
>
>
    • T3s can "skip" this step.
    • However, if the site wants to use the data they host on the Tier3, we should recommend that they install a Squid, but registering it centrally is optional.
 
  • 7. SAM tests - There won't be any CE related ones if the site only provides SE.
    • [The SRM test should be addressed though]

Revision 202013-12-16 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 13 to 13
 
  1. CMS Name: Define a CMS name for site
    • Name should follow the convention: Tier#(T#)_Country(2 letters)_Site(Short). For example: T2_US_FNAL (Contact Site Support Team to confirm name)
Added:
>
>
    • Contact Ken Bloom <kenbloom@unl.edu> to confirm the new name is correct and does not present any problems.
 
  1. SiteDB:
    • Add new site to SiteDB: contact Site Support to create Site
    • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinators informing about new site.

Revision 192013-12-12 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 61 to 61
 
  1. LoadTest07 samples: Create and Inject LoadTest07 samples
Added:
>
>
    • If the site is a T3, will it be used for MonteCarlo production? If not, it doesn't need the source loadtest dataset to be created and injected, only export links need the source loadtest datasets. T3s usually have import links only.
 
  1. Link commissioning:

Revision 182013-12-11 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 45 to 45
 
      1. org.cms.WN-swinst (CVMFS)
      2. org.cms.WN-frontier
      3. org.cms.WN-squid
Added:
>
>
  1. Phedex entry (node) & links: (This is done manually)
    • Send a new Savannah ticket to Transfer team (cmscompinfrasup-datatransfer squad) --> "please create Site node & links in Phedex".
    • In this step we can request to create Links as well (not link commissioning)
      • For T3s we don't create all links but only specific requested links - ask which ones.
 
  1. PhEDEx agents: Configure PhEDEx agents
Deleted:
<
<
  1. Phedex entry: (This is done manually)
    • Send Savannah ticket to Transfer team --> "please create Site in Phedex".
 
      • Phedex needs the TFC of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
  1. SRM test: Debug SRM SAM tests results - org.cms.SRM
    • The site needs working PhEDEx agents to pass these tests.
Line: 62 to 64
 
  1. Link commissioning:
Added:
>
>
 
      • Links are created in all three instances of PhEDEx (Prod, Debug and Dev).
        • The Prod links are disabled until the Debug links demonstrate sufficient speed.
        • First, several Debug transfers will be injected to and from the new site and they will be monitored if they start and run OK.

Revision 172013-12-09 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 47 to 47
 
      1. org.cms.WN-squid
  1. PhEDEx agents: Configure PhEDEx agents
Added:
>
>
    • Contact Tony Wildish <Tony.Wildish@cern.ch> for the DBParam role creation. He is the PhEDEx database Admin who can generate the DBParam files for the site.
 
    • If a site upgrades to SL6 how to update Phedex?
      • PhEDEx is not distributed through CVMFS, you need to install and configure the PhEDEx agents manually.
      • You can find the instructions for SLC6 here: LINK

Revision 162013-12-03 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 45 to 45
 
      1. org.cms.WN-swinst (CVMFS)
      2. org.cms.WN-frontier
      3. org.cms.WN-squid
Deleted:
<
<
  1. Phedex entry: (This is done manually)
    • Send Savannah ticket to Transfer team --> "please create Site in Phedex".
      • Phedex needs the TFC of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
 
  1. PhEDEx agents: Configure PhEDEx agents
Added:
>
>
  1. Phedex entry: (This is done manually)
    • Send Savannah ticket to Transfer team --> "please create Site in Phedex".
      • Phedex needs the TFC of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
 
  1. SRM test: Debug SRM SAM tests results - org.cms.SRM
    • The site needs working PhEDEx agents to pass these tests.
  2. LoadTest07 samples: Create and Inject LoadTest07 samples

Revision 152013-11-21 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 8 to 8
 https://twiki.cern.ch/twiki/bin/view/CMSPublic/PhedexAdminDocsNewSite#Tier2

Fully Operational Sites

Added:
>
>

T1s & T2s

 
  1. CMS secretariat & CMS VO: Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
  2. CMS Name: Define a CMS name for site
    • Name should follow the convention: Tier#(T#)_Country(2 letters)_Site(Short). For example: T2_US_FNAL (Contact Site Support Team to confirm name)
  3. SiteDB:
Changed:
<
<
    • Add new site to SiteDB: contact Site Support to create Site, Diego da Silva (mapping and SiteDB) or Oliver Gutsche
    • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinator informing about new site.
>
>
    • Add new site to SiteDB: contact Site Support to create Site
    • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinators informing about new site.
 
    • Contact SiteExecutive so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
Added:
>
>
      • Russian Tier-1 might be a good candidate for serving as parent site for Eastern European sites.
 
Line: 27 to 29
 
  1. CMSSW/CVMFS:
Changed:
<
<
    • Please note that you don't need to install it anymore.
>
>
    • Please note that you don't need to install CMSSW anymore.
 
    • You should now configure CVMFS to get software releases automatically instead.
  1. Frontier/Squid: Install and configure Squid for CMS Frontier
Line: 100 to 102
 
      • New T2 sites will appear in the Waiting Room automatically, explicit action (file editing) is required by Comp Ops to promote them to Production.
  1. Waiting Room: Move site out of the SSB Waiting Room
  2. Site is ready to work!
Added:
>
>

T3s

  • 5. CMSSW/CVMFS
  • 6. Frontier/Squid
    • T3s can "skip" both.
    • However, if the site wants to use the data they host on the Tier3, we should recommend that they install CVMFS on their local machines to get CMSSW and also a Squid, where registering it centrally is optional.

  • 7. SAM tests - There won't be any CE related ones if the site only provides SE.
    • [The SRM test should be addressed though]

  • 12. A Tier-3 has no requirements concerning commissioned links. Note however that data are only transferred on commissioned links. The site has make their plans from where they intend to download and need to commission those links.

  • 13. Since there is no CE there won't be any HC running
  • 14. The VO Feed will miss a CE, which is fine for a SE Tier-3 only.
  • 15. Monitoring for the SE would help the site, but we do not require it.
 

Opportunistic Sites

  • "Opportunistic" means that a site will provide resources without a pledge, which usually means there are no guarantees about availability or it can also mean there is no local CMS support or it can mean the resources are only available for a short time.

Revision 142013-10-22 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 48 to 48
 
      • Phedex needs the TFC of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
  1. PhEDEx agents: Configure PhEDEx agents
Added:
>
>
    • If a site upgrades to SL6 how to update Phedex?
      • PhEDEx is not distributed through CVMFS, you need to install and configure the PhEDEx agents manually.
      • You can find the instructions for SLC6 here: LINK
 
  1. SRM test: Debug SRM SAM tests results - org.cms.SRM
    • The site needs working PhEDEx agents to pass these tests.
  2. LoadTest07 samples: Create and Inject LoadTest07 samples

Revision 132013-09-20 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 26 to 26
 
Added:
>
>
  1. CMSSW/CVMFS:
    • Please note that you don't need to install it anymore.
    • You should now configure CVMFS to get software releases automatically instead.
 
  1. Frontier/Squid: Install and configure Squid for CMS Frontier

Revision 122013-09-13 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 78 to 78
 
    • If the site and its services are correctly registered in CMS SiteDB and BDII the site will appear in CMS VO Feed.
    • The CMS VO Feed uses the following information sources:
Changed:
<
<
      • for CEs: all CEs published in BDII as "close" to the SE
>
>
      • for CEs: all CEs published in BDII associated or as "close" to the SE
 
  1. Monitoring:
    • Is the site automatically appearing in Site Status Board?
      • CMS VO Feed is the source for the TopologyMaintenances metric in SSB, it means that if the site is in the CMS VO Feed it will appear in SSB as well.

Revision 112013-09-12 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 74 to 74
 
      1. org.cms.WN-xrootd-fallback
    • HammerCloud test
      • To start test contact Andrea Sciaba to add the site to the appropriate test templates.
Added:
>
>
  1. CMS VO Feed - Link
    • If the site and its services are correctly registered in CMS SiteDB and BDII the site will appear in CMS VO Feed.
    • The CMS VO Feed uses the following information sources:
      • for SEs: SiteDBv2
      • for CEs: all CEs published in BDII as "close" to the SE
 
  1. Monitoring:
    • Is the site automatically appearing in Site Status Board?
Changed:
<
<
      • If the site and its services are correctly registered in CMS SiteDB and BDII the site will appear in CMS VO feed (http://dashb-cms-vo-feed.cern.ch/dashboard/request.py/cmssitemapbdii) and as this is the source for the TopologyMaintenances metric in SSB, it means that it will appear in SSB as well.
      • Having the site in the VO feed doesn't mean that this site will be monitored for every metric in SSB, sometimes the responsible for the metric has to add the site to the test template - for example: HammerCloud test (Andrea Sciaba).
>
>
      • CMS VO Feed is the source for the TopologyMaintenances metric in SSB, it means that if the site is in the CMS VO Feed it will appear in SSB as well.
      • Having the site in the CMS VO feed doesn't mean that this site will be monitored for every metric in SSB, sometimes the responsible for the metric has to add the site to the test template - for example: HammerCloud test (Andrea Sciaba).
 
    • Is the site automatically appearing in Dashboard?
      • No, Dashboard ops (e.g. Julia) may need to explicitely refresh the import of site names from SiteDB.
    • Is the site automatically appearing in the Site Readiness plots?

Revision 102013-08-29 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 124 to 124
 
  1. Jobs will be submitted to these resources.
  • The modifications are only in the glideInWMS system and they are completely hidden within the glideInWMS system
    • This is a problem for monitoring: all of our system would not know about what's inside T3_US_Parrot, that you added or removed some resources. They just see a collection of resources called T3_US_Parrot which could be anything and anywhere.
Added:
>
>
  • SAM and HC tests. We don't need to run those tests at T3_US_Parrot.
  • If we want to evaluate some specific resources what we could do is ask the glidein Factory to turn off (momentarily) the other sites/CEs associated with T3_US_Parrot and leave on only the one we are interested in and start sending jobs. All checks will be limited to the glide in level, we won't have monitoring from any other regular systems.
 

For Production

  • Fully opportunistic - parrot - not ready for that in the glidein level

Revision 92013-08-23 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 92 to 92
 

Opportunistic Sites

  • "Opportunistic" means that a site will provide resources without a pledge, which usually means there are no guarantees about availability or it can also mean there is no local CMS support or it can mean the resources are only available for a short time.
Changed:
<
<
  • For sites with a small amount of resources, we don't want to create a new CMS site, because there are administrative and operational overheads attached to having a larger number of CMS sites
>
>
  • For sites with a small amount of resources, we don't want to create a new CMS site, because there are administrative and operational overheads attached to having a larger number of CMS sites.
 
  • For sites with larger amount of resources, often the the time period we get them is too short to go through the whole process of adding a new CMS site (could take up to 2 weeks or more).
Changed:
<
<
  • Only for opportunistic sites that provide a large amount of resources for an extended period of time is it worthwhile to go through the whole process of adding a new CMS site.
>
>
  • Only for opportunistic sites that provide a large amount of resources for an extended period of time it is worthwhile to go through the whole process of adding a new CMS site.
  Under opportunistic we define two types of sites:
  1. Fully opportunistic:
    • A site that is not part of CMS and that has no local CMS support.
Changed:
<
<
    • We can add resources dynamically to added to an existing meta-site:
>
>
    • We can add resources dynamically to an existing meta-site:
 
      • T3_US_Parrot
      • T3_EU_Parrot
      • T3_US_ParrotTest (only for tests)

Revision 82013-08-23 - DirkHufnagel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 91 to 91
 
  1. Site is ready to work!

Opportunistic Sites

Changed:
<
<
  • "Opportunistic" means that a site will provide resources without a pledge, which means there are no guarantees about availability attached.
  • Usually the amount of resources and/or the time period we get them is too small to go through the whole process for fully operational sites which could take up to 2 weeks or more.
>
>
  • "Opportunistic" means that a site will provide resources without a pledge, which usually means there are no guarantees about availability or it can also mean there is no local CMS support or it can mean the resources are only available for a short time.
  • For sites with a small amount of resources, we don't want to create a new CMS site, because there are administrative and operational overheads attached to having a larger number of CMS sites
  • For sites with larger amount of resources, often the the time period we get them is too short to go through the whole process of adding a new CMS site (could take up to 2 weeks or more).
  • Only for opportunistic sites that provide a large amount of resources for an extended period of time is it worthwhile to go through the whole process of adding a new CMS site.
  Under opportunistic we define two types of sites:
  1. Fully opportunistic:
    • A site that is not part of CMS and that has no local CMS support.
Changed:
<
<
    • The resources will be dynamically added to an existing meta-site:
>
>
    • We can add resources dynamically to added to an existing meta-site:
 
      • T3_US_Parrot
      • T3_EU_Parrot
      • T3_US_ParrotTest (only for tests)
Added:
>
>
      • more meta-sites can be created for different regions as needed (Asia for instance)
    • OR create a new CMS site if the amount of resources and the time we have them warrants it
 
    • The dynamic model is useful for adding/removing little amount of resources frequently, just reconfiguring the frontend/factory.
    • Beyond a certain amount of resources it introduces inflexibility in how we can assign work to these resources.
Changed:
<
<
    • A meta-site with much more than 10,000 slots is a bit unwieldy.
>
>
    • A meta-site with much more than 10,000 slots is a bit unwieldy (if we ever get there we can split this up further into more meta-sites).
 
  1. Semi-opportunistic
    • An already existing CMS site that wants to provide extra resources for a short period of time.
    • Contact the production/analysis teams to assign more work to this site.
Line: 115 to 119
 
  1. Make sure that the site provides a way to access the resources via glideInWMS (which should exist if it's a grid site)
  2. No SITECONF changes needed
  3. Contact Alison McCrea <alisonjm@gmail.com>
Changed:
<
<
    • to configure the exisiting glideInWMS factory entry to access the # of slots that the site will provide.
    • to take that factory entry and add it to the T3_US_Parrot group
>
>
    • to configure the existing glideInWMS factory entry to access the # of slots that the site will provide.
    • to take that factory entry and add it to the T3_US_Parrot or T3_EU_Parrot group
 
  1. Jobs will be submitted to these resources.
  • The modifications are only in the glideInWMS system and they are completely hidden within the glideInWMS system
    • This is a problem for monitoring: all of our system would not know about what's inside T3_US_Parrot, that you added or removed some resources. They just see a collection of resources called T3_US_Parrot which could be anything and anywhere.

Revision 72013-08-23 - DirkHufnagel

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 91 to 91
 
  1. Site is ready to work!

Opportunistic Sites

Changed:
<
<
  • "Opportunistic" means that a site will provide resources for a limited period of time.
  • Usually the time period is too short to go through the whole process for fully operational sites which could take up to 2 weeks or more.
>
>
  • "Opportunistic" means that a site will provide resources without a pledge, which means there are no guarantees about availability attached.
  • Usually the amount of resources and/or the time period we get them is too small to go through the whole process for fully operational sites which could take up to 2 weeks or more.
  Under opportunistic we define two types of sites:
  1. Fully opportunistic:

Revision 62013-08-21 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Changed:
<
<
Pre-requisites:
>
>

Pre-requisites

 https://twiki.cern.ch/twiki/bin/view/CMSPublic/PhedexAdminDocsNewSite#Tier2
Added:
>
>

Fully Operational Sites

 
  1. CMS secretariat & CMS VO: Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
  2. CMS Name: Define a CMS name for site
Line: 22 to 23
 
      • Make sure is the only certificate registered here, because some of our systems wouldn't work otherwise.
  1. GIT: Setup GIT and commit files to SITECONF
    • Create site-local-config.xml & storage.xml
Changed:
<
<
    • Site has to commit the config files to SITECONF (site admin needs permissions to access - Contact Site Support Team).
>
>
    • Site has to commit the config files to SITECONF.
      • Site admins/executives get access to siteconf automatically and can go ahead and create the directory for their site.
 
  1. Frontier/Squid: Install and configure Squid for CMS Frontier
Line: 89 to 91
 
  1. Site is ready to work!

Opportunistic Sites

Changed:
<
<
  • For Production
    • fully opportunistic - parrot - not ready for that in the glidein level
    • semi-opportunistic - could be set up in an easy way - creating a CMS site - we need to commission time=depends (1week-2weeks)
>
>
  • "Opportunistic" means that a site will provide resources for a limited period of time.
  • Usually the time period is too short to go through the whole process for fully operational sites which could take up to 2 weeks or more.

Under opportunistic we define two types of sites:

  1. Fully opportunistic:
    • A site that is not part of CMS and that has no local CMS support.
    • The resources will be dynamically added to an existing meta-site:
      • T3_US_Parrot
      • T3_EU_Parrot
      • T3_US_ParrotTest (only for tests)
    • The dynamic model is useful for adding/removing little amount of resources frequently, just reconfiguring the frontend/factory.
    • Beyond a certain amount of resources it introduces inflexibility in how we can assign work to these resources.
    • A meta-site with much more than 10,000 slots is a bit unwieldy.
  2. Semi-opportunistic
    • An already existing CMS site that wants to provide extra resources for a short period of time.
    • Contact the production/analysis teams to assign more work to this site.

Fully Opportunistic

  1. Confirm that the site has authorization and that has contacted the corresponding people (ask Oliver Gutsche).
  2. Confirm the amount of resources that the site will provide and for how long.
    • If the site will provide a big amount of resources or will provide them for quite long time it is probably better to add them as a new CMS Site.
  3. Make sure that the site provides a way to access the resources via glideInWMS (which should exist if it's a grid site)
  4. No SITECONF changes needed
  5. Contact Alison McCrea <alisonjm@gmail.com>
    • to configure the exisiting glideInWMS factory entry to access the # of slots that the site will provide.
    • to take that factory entry and add it to the T3_US_Parrot group
  6. Jobs will be submitted to these resources.
  • The modifications are only in the glideInWMS system and they are completely hidden within the glideInWMS system
    • This is a problem for monitoring: all of our system would not know about what's inside T3_US_Parrot, that you added or removed some resources. They just see a collection of resources called T3_US_Parrot which could be anything and anywhere.

For Production

  • Fully opportunistic - parrot - not ready for that in the glidein level
  • Semi-opportunistic - could be set up in an easy way
    • if it is an already existing CMS site and it is already in the production list it is a matter of increasing the threshold in the WMAgent to send more jobs to the site.
    • If it is a new CMS site - we need to commission the site (1-2weeks)
 
      • it should be easier to commission an already existing CMS T3

Revision 52013-07-19 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Changed:
<
<
Pre-requisites: https://twiki.cern.ch/twiki/bin/view/CMSPublic/PhedexAdminDocsNewSite#Tier2
>
>
 
Changed:
<
<
  1. Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
>
>
Pre-requisites: https://twiki.cern.ch/twiki/bin/view/CMSPublic/PhedexAdminDocsNewSite#Tier2

  1. CMS secretariat & CMS VO: Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
 
Changed:
<
<
  1. Define a CMS name for site
>
>
  1. CMS Name: Define a CMS name for site
 
    • Name should follow the convention: Tier#(T#)_Country(2 letters)_Site(Short). For example: T2_US_FNAL (Contact Site Support Team to confirm name)
Changed:
<
<
    • Add it to SiteDB: contact Site Support to create Site, Diego da Silva (mapping and SiteDB) or Oliver Gutsche
>
>
  1. SiteDB:
    • Add new site to SiteDB: contact Site Support to create Site, Diego da Silva (mapping and SiteDB) or Oliver Gutsche
 
    • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinator informing about new site.
Changed:
<
<
  1. Contact SiteExecutive so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
>
>
    • Contact SiteExecutive so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
 
Changed:
<
<
  1. GIT setup and commit files to SITECONF
>
>
  1. GIT: Setup GIT and commit files to SITECONF
 
Changed:
<
<
  1. Install and configure Squid for CMS Frontier
>
>
  1. Frontier/Squid: Install and configure Squid for CMS Frontier
 
    • https://twiki.cern.ch/twiki/bin/view/CMS/SquidForCMS
    • If correctly installed: SAM Squid test could be successful in next steps.
    • If CVMFS is working properly, site could also pass the SAM Frontier test in next steps.
    • Part of installing Frontier involves creating site-local-config.xml which is certainly necessary for other things.
Changed:
<
<
  1. If the previous steps were successfully completed, some of the CMS SAM tests should start working.
>
>
  1. SAM tests: If the previous steps were successfully completed, some of the CMS SAM tests should start working.
 
    • SAM tests are automatically started if the BDII information is correct and the site exists in GOCDB or OIM.
    • Start debugging the following tests results (not all of the SAM tests):
      1. org.sam.CREAMCE-JobSubmit
Line: 34 to 38
 
      1. org.cms.WN-swinst (CVMFS)
      2. org.cms.WN-frontier
      3. org.cms.WN-squid
Changed:
<
<
  1. Phedex entry (This is done manually)
>
>
  1. Phedex entry: (This is done manually)
 
    • Send Savannah ticket to Transfer team --> "please create Site in Phedex".
      • Phedex needs the TFC of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
Changed:
<
<
  1. Configure PhEDEx agents
>
>
  1. PhEDEx agents: Configure PhEDEx agents
 
Changed:
<
<
  1. Debug SRM SAM tests results - org.cms.SRM
>
>
  1. SRM test: Debug SRM SAM tests results - org.cms.SRM
 
    • The site needs working PhEDEx agents to pass these tests.
Changed:
<
<
  1. Create and Inject LoadTest07 samples
>
>
  1. LoadTest07 samples: Create and Inject LoadTest07 samples
 
Changed:
<
<
  1. Link commissioning.
>
>
  1. Link commissioning:
 
Line: 57 to 61
 
Changed:
<
<
  1. Transfer HC & SAM tests samples to site.
  2. Debug tests results:
    • Remaining SAM tests
>
>
  1. HC & SAM tests:
    • Transfer HC & SAM tests samples to site.
    • Debug tests results:
      • Remaining SAM tests:
 
      1. org.cms.glexec.WN-gLExec
      2. org.cms.WN-analysis
      3. org.cms.WN-mc
Line: 67 to 72
 
      1. org.cms.WN-xrootd-fallback
    • HammerCloud test
      • To start test contact Andrea Sciaba to add the site to the appropriate test templates.
Changed:
<
<
  1. Monitoring:
    • Is the site automatically appearing in Site Status Board?
>
>
  1. Monitoring:
    • Is the site automatically appearing in Site Status Board?
 
      • If the site and its services are correctly registered in CMS SiteDB and BDII the site will appear in CMS VO feed (http://dashb-cms-vo-feed.cern.ch/dashboard/request.py/cmssitemapbdii) and as this is the source for the TopologyMaintenances metric in SSB, it means that it will appear in SSB as well.
      • Having the site in the VO feed doesn't mean that this site will be monitored for every metric in SSB, sometimes the responsible for the metric has to add the site to the test template - for example: HammerCloud test (Andrea Sciaba).
Changed:
<
<
    • Is the site automatically appearing in Dashboard?
>
>
    • Is the site automatically appearing in Dashboard?
 
      • No, Dashboard ops (e.g. Julia) may need to explicitely refresh the import of site names from SiteDB.
Changed:
<
<
    • Is the site automatically appearing in the Site Readiness plots?
>
>
    • Is the site automatically appearing in the Site Readiness plots?
 
      • The site will appear in Site Readiness plots once it appears in SiteReadiness Status metric in SSB (Site has to be added to the test template).
      • Duncan and/or Pepe Flix can give more details about the site readiness machinary.
Changed:
<
<
    • Once in SSB, is the site placed in the Waiting room or in Production?
>
>
    • Once in SSB, is the site placed in the Waiting room or in Production?
 
Changed:
<
<
  1. Move site out of the SSB Waiting Room
>
>
  1. Waiting Room: Move site out of the SSB Waiting Room
 
  1. Site is ready to work!
Added:
>
>

Opportunistic Sites

  • For Production
    • fully opportunistic - parrot - not ready for that in the glidein level
    • semi-opportunistic - could be set up in an easy way - creating a CMS site - we need to commission time=depends (1week-2weeks)
      • it should be easier to commission an already existing CMS T3

Revision 42013-07-09 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 6 to 6
  1. Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.
Changed:
<
<
2. Define a CMS name for site
>
>
  1. Define a CMS name for site
 
  • Name should follow the convention: Tier#(T#)_Country(2 letters)_Site(Short). For example: T2_US_FNAL (Contact Site Support Team to confirm name)
  • Add it to SiteDB: contact Site Support to create Site, Diego da Silva (mapping and SiteDB) or Oliver Gutsche
  • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinator informing about new site.
Changed:
<
<
3. Contact SiteExecutive so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
>
>
  1. Contact SiteExecutive so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
 
Changed:
<
<
4. Install and configure Squid for CMS Frontier
>
>
  1. GIT setup and commit files to SITECONF
  2. Install and configure Squid for CMS Frontier
 
  • https://twiki.cern.ch/twiki/bin/view/CMS/SquidForCMS
  • If correctly installed: SAM Squid test could be successful in next steps.
  • If CVMFS is working properly, site could also pass the SAM Frontier test in next steps.
  • Part of installing Frontier involves creating site-local-config.xml which is certainly necessary for other things.
Changed:
<
<
  • Site has to commit the config file to SITECONF (site admin needs permissions to access - Contact Site Support Team).
5. If the previous steps were successfully completed, some of the CMS SAM tests should start working.
>
>
  1. If the previous steps were successfully completed, some of the CMS SAM tests should start working.
 
  • SAM tests are automatically started if the BDII information is correct and the site exists in GOCDB or OIM.
  • Start debugging the following tests results (not all of the SAM tests):
    1. org.sam.CREAMCE-JobSubmit
Line: 31 to 34
 
    1. org.cms.WN-swinst (CVMFS)
    2. org.cms.WN-frontier
    3. org.cms.WN-squid
Changed:
<
<
6. Phedex entry (This is done manually)
>
>
  1. Phedex entry (This is done manually)
 
  • Send Savannah ticket to Transfer team --> "please create Site in Phedex".
    • Phedex needs the TFC of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
Changed:
<
<
7. Configure PhEDEx agents
>
>
  1. Configure PhEDEx agents
 
Changed:
<
<
8. Debug SRM SAM tests results - org.cms.SRM
>
>
  1. Debug SRM SAM tests results - org.cms.SRM
 
  • The site needs working PhEDEx agents to pass these tests.
Changed:
<
<
9. Create and Inject LoadTest07 samples
>
>
  1. Create and Inject LoadTest07 samples
 
Changed:
<
<
10. Link commissioning.
>
>
  1. Link commissioning.
 
Line: 54 to 57
 
Changed:
<
<
11. Transfer HC & SAM tests samples to site.

12. Debug tests results:

>
>
  1. Transfer HC & SAM tests samples to site.
  2. Debug tests results:
 
  • Remaining SAM tests
    1. org.cms.glexec.WN-gLExec
    2. org.cms.WN-analysis
Line: 65 to 67
 
    1. org.cms.WN-xrootd-fallback
  • HammerCloud test
    • To start test contact Andrea Sciaba to add the site to the appropriate test templates.
Changed:
<
<
13. Monitoring:
>
>
  1. Monitoring:
 
  • Is the site automatically appearing in Site Status Board?
    • If the site and its services are correctly registered in CMS SiteDB and BDII the site will appear in CMS VO feed (http://dashb-cms-vo-feed.cern.ch/dashboard/request.py/cmssitemapbdii) and as this is the source for the TopologyMaintenances metric in SSB, it means that it will appear in SSB as well.
    • Having the site in the VO feed doesn't mean that this site will be monitored for every metric in SSB, sometimes the responsible for the metric has to add the site to the test template - for example: HammerCloud test (Andrea Sciaba).
Line: 80 to 80
 
Changed:
<
<
14. Move site out of the SSB Waiting Room

15. Site is ready to work!

>
>
  1. Move site out of the SSB Waiting Room
  2. Site is ready to work!

Revision 32013-06-13 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 49 to 49
 
      • First, several Debug transfers will be injected to and from the new site and they will be monitored if they start and run OK.
      • If the Debug Transfers work, then the rest of the transfers can be injected to have full matrix with all T1s, and then, when those succeed, the Prod links will be enabled automatically by overnight cronjobs.
Added:
>
>
 

Revision 22013-06-12 - JohnArtieda

Line: 1 to 1
 
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Line: 7 to 7
 1. Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS. 2. Define a CMS name for site
Changed:
<
<
  • Add it to SiteDB: contact Diego da Silva (mapping and SiteDB) or Oliver Gutsche
>
>
  • Name should follow the convention: Tier#(T#)_Country(2 letters)_Site(Short). For example: T2_US_FNAL (Contact Site Support Team to confirm name)
  • Add it to SiteDB: contact Site Support to create Site, Diego da Silva (mapping and SiteDB) or Oliver Gutsche
 
  • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinator informing about new site.
Changed:
<
<
3. Contact SiteAdmin so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
>
>
3. Contact SiteExecutive so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM.
 
Line: 17 to 18
 
    • Make sure is the only certificate registered here, because some of our systems wouldn't work otherwise.
4. Install and configure Squid for CMS Frontier
Changed:
<
<
  • If correctly installed: SAM Squid test could be successful in step 5.
  • If CVMFS is working properly, site could also pass the SAM Frontier test in step 5.
>
>
  • If correctly installed: SAM Squid test could be successful in next steps.
  • If CVMFS is working properly, site could also pass the SAM Frontier test in next steps.
 
  • Part of installing Frontier involves creating site-local-config.xml which is certainly necessary for other things.
Changed:
<
<
  • Site has to commit the config file to CVS (site admin needs CVS access).
>
>
  • Site has to commit the config file to SITECONF (site admin needs permissions to access - Contact Site Support Team).
 5. If the previous steps were successfully completed, some of the CMS SAM tests should start working.
  • SAM tests are automatically started if the BDII information is correct and the site exists in GOCDB or OIM.
  • Start debugging the following tests results (not all of the SAM tests):
Line: 32 to 33
 
    1. org.cms.WN-squid
6. Phedex entry (This is done manually)
  • Send Savannah ticket to Transfer team --> "please create Site in Phedex".
Changed:
<
<
    • Phedex needs the TFC of the site (storage.xml & site_local_config.xml in CVS).
7. Create and Inject LoadTest07 samples
>
>
    • Phedex needs the TFC of the site. It gets it directly from the agents configured at that site. Specifically, there is an agent whose sole job is to make sure that the TFC is regularly uploaded to the PhEDEx database. PhEDEx does not take the TFC, or anything, from SITECONF.
7. Configure PhEDEx agents 8. Debug SRM SAM tests results - org.cms.SRM
  • The site needs working PhEDEx agents to pass these tests.
9. Create and Inject LoadTest07 samples
 
Changed:
<
<
8. Link commissioning.
>
>
10. Link commissioning.
 
Line: 47 to 52
 
Changed:
<
<
9. Transfer HC & SAM tests samples to site.
>
>
11. Transfer HC & SAM tests samples to site.
 
Changed:
<
<
10. Debug tests results:
>
>
12. Debug tests results:
 
  • Remaining SAM tests
    1. org.cms.glexec.WN-gLExec
    2. org.cms.WN-analysis
Line: 58 to 63
 
    1. org.cms.WN-xrootd-fallback
  • HammerCloud test
    • To start test contact Andrea Sciaba to add the site to the appropriate test templates.
Changed:
<
<
11. Monitoring:
>
>
13. Monitoring:
 
  • Is the site automatically appearing in Site Status Board?
    • If the site and its services are correctly registered in CMS SiteDB and BDII the site will appear in CMS VO feed (http://dashb-cms-vo-feed.cern.ch/dashboard/request.py/cmssitemapbdii) and as this is the source for the TopologyMaintenances metric in SSB, it means that it will appear in SSB as well.
    • Having the site in the VO feed doesn't mean that this site will be monitored for every metric in SSB, sometimes the responsible for the metric has to add the site to the test template - for example: HammerCloud test (Andrea Sciaba).
Line: 74 to 78
 
Changed:
<
<
12. Move site out of the SSB Waiting Room
>
>
14. Move site out of the SSB Waiting Room
 
Deleted:
<
<
13. Site is ready to work!
 \ No newline at end of file
Added:
>
>
15. Site is ready to work!

Revision 12013-06-11 - JohnArtieda

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="SiteSupportDocumentation"

Site Support Team - Documentation
Adding a New CMS Site

Pre-requisites: https://twiki.cern.ch/twiki/bin/view/CMSPublic/PhedexAdminDocsNewSite#Tier2

1. Site executive needs to be properly registered in the CMS secretariat and be included in the CMS VO in VOMS.

2. Define a CMS name for site
  • Add it to SiteDB: contact Diego da Silva (mapping and SiteDB) or Oliver Gutsche
  • Send email to cms-comp-ops-site-support-team CC: cms-comp-ops-coordinator informing about new site.
3. Contact SiteAdmin so he can update all the fields for the new Site in SiteDB: WLCG name, CE(s), SE. This will allow the site to appear in SAM. 4. Install and configure Squid for CMS Frontier
  • https://twiki.cern.ch/twiki/bin/view/CMS/SquidForCMS
  • If correctly installed: SAM Squid test could be successful in step 5.
  • If CVMFS is working properly, site could also pass the SAM Frontier test in step 5.
  • Part of installing Frontier involves creating site-local-config.xml which is certainly necessary for other things.
  • Site has to commit the config file to CVS (site admin needs CVS access).
5. If the previous steps were successfully completed, some of the CMS SAM tests should start working.
  • SAM tests are automatically started if the BDII information is correct and the site exists in GOCDB or OIM.
  • Start debugging the following tests results (not all of the SAM tests):
    1. org.sam.CREAMCE-JobSubmit
    2. org.cms.WN-env
    3. WN-basic
    4. org.cms.WN-swinst (CVMFS)
    5. org.cms.WN-frontier
    6. org.cms.WN-squid
6. Phedex entry (This is done manually)
  • Send Savannah ticket to Transfer team --> "please create Site in Phedex".
    • Phedex needs the TFC of the site (storage.xml & site_local_config.xml in CVS).
7. Create and Inject LoadTest07 samples 8. Link commissioning.
  • REQUIREMENTS AND PROCEDURE:
    • https://twiki.cern.ch/twiki/bin/view/CMSPublic/LinkCommissioning
    • Links are created in all three instances of PhEDEx (Prod, Debug and Dev).
      • The Prod links are disabled until the Debug links demonstrate sufficient speed.
      • First, several Debug transfers will be injected to and from the new site and they will be monitored if they start and run OK.
      • If the Debug Transfers work, then the rest of the transfers can be injected to have full matrix with all T1s, and then, when those succeed, the Prod links will be enabled automatically by overnight cronjobs.
  • Savannah ticket to Transfer team --> "please commission Links for Site"
9. Transfer HC & SAM tests samples to site.

10. Debug tests results:

  • Remaining SAM tests
    1. org.cms.glexec.WN-gLExec
    2. org.cms.WN-analysis
    3. org.cms.WN-mc
    4. org.cms.WN-xrootd-access
    5. org.cms.WN-xrootd-fallback
  • HammerCloud test
    • To start test contact Andrea Sciaba to add the site to the appropriate test templates.
11. Monitoring:

  • Is the site automatically appearing in Site Status Board?
    • If the site and its services are correctly registered in CMS SiteDB and BDII the site will appear in CMS VO feed (http://dashb-cms-vo-feed.cern.ch/dashboard/request.py/cmssitemapbdii) and as this is the source for the TopologyMaintenances metric in SSB, it means that it will appear in SSB as well.
    • Having the site in the VO feed doesn't mean that this site will be monitored for every metric in SSB, sometimes the responsible for the metric has to add the site to the test template - for example: HammerCloud test (Andrea Sciaba).

  • Is the site automatically appearing in Dashboard?
    • No, Dashboard ops (e.g. Julia) may need to explicitely refresh the import of site names from SiteDB.

  • Is the site automatically appearing in the Site Readiness plots?
    • The site will appear in Site Readiness plots once it appears in SiteReadiness Status metric in SSB (Site has to be added to the test template).
    • Duncan and/or Pepe Flix can give more details about the site readiness machinary.
  • Once in SSB, is the site placed in the Waiting room or in Production?
12. Move site out of the SSB Waiting Room

13. Site is ready to work!

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback