Difference: RemoveCmsSite (1 vs. 29)

Revision 292019-08-08 - AkankshaAhuja1

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 49 to 49
 
Changed:
<
<
      • Pledges (Site Support Team)
>
>
      • Pledges, Production Cores and Real Cores (Ignore at the moment)
 
    • Delete dashboard data of the site for the last two months (if site was in drain that long) or wait for site to flush out
      • to delete data, right-click on cell in site readiness and select "Remove Cell from Database"
      • site should disappear from Site-Readiness after about two month (script will remove site after all feeding metrics provides no data for about a month)

Revision 282019-04-26 - XiaoweiJiang

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
  2. Compute Elements of Site: Decommission the dedicated CMS CEs
Changed:
<
<
>
>
 
  1. Storage Elements of site Contact transfer team to relocate data and disable transfers to the site, i.e.:
    • SE Data: Ensure that all data on your SE is safely replicated to a custodial location
    • VO CMS: Remove support for the VO CMS from SEs
Line: 42 to 42
 
  1. Dashboard & SSB: contact Dashboard team to remove site and to identify metrics that still feed info into SSB for the site
    • Ask the metric responsible to stop providing data for the site
Changed:
<
<
>
>
 
      • HammerCloud (Andrea Sciaba)
      • #good links in the site readiness view (Andrea Sciaba)
Changed:
<
<
>
>
 
      • Pledges (Site Support Team)
    • Delete dashboard data of the site for the last two months (if site was in drain that long) or wait for site to flush out
      • to delete data, right-click on cell in site readiness and select "Remove Cell from Database"

Revision 272019-04-26 - XiaoweiJiang

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 42 to 42
 
  1. Dashboard & SSB: contact Dashboard team to remove site and to identify metrics that still feed info into SSB for the site
    • Ask the metric responsible to stop providing data for the site
Changed:
<
<
      • Phedex
>
>
 
      • HammerCloud (Andrea Sciaba)
      • #good links in the site readiness view (Andrea Sciaba)
      • Production (Workflow team)
      • Site readiness (Site Support Team)
      • Claimed/Unclaimed Pilots (lolass@cernNOSPAMPLEASE.ch)
Changed:
<
<
>
>
 
      • Pledges (Site Support Team)
    • Delete dashboard data of the site for the last two months (if site was in drain that long) or wait for site to flush out
      • to delete data, right-click on cell in site readiness and select "Remove Cell from Database"

Revision 262018-07-09 - StephanLammel

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 62 to 62
  and finally
cat datatoDelete.txt | xargs -n 1 curl -k -H "Accept : application/json" -X GET --cert ~/.globus/usercert.pem --key ~/.globus/unencr_key.pem
That last step actually deletes the data, using the unencrypted cert for authentication with the dashboard web service.
Changed:
<
<
  1. Tickets: Close all tickets for the site.
>
>
  1. GGUS: close out tickets and prevent new tickets
    • Close out all tickets for the site.
    • If appropriate, remove the site from the CMS Site selector and grid site selectors by making a ticket and asking the GGUS team to delete the entry from the internal database
  * Based on past experience: it took about 3 weeks to completely remove T2 Lisbon site (early 2013).

Revision 252018-07-03 - StephanLammel

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 36 to 36
 
  1. SiteDB: Remove from SiteDB
Deleted:
<
<
    • If the site does not apper here anymore, that means that v2 of SiteDB is already aware that the site does not exist.
 
Line: 51 to 50
 
Deleted:
<
<
    • Can run into problems because SSB uses old v1 SiteDB api (as of early 2013).
      • The problem is that some of the SiteDB queries still return info of deleted sites, and some will not.
      • Contact SiteDB responsible (Diego da Silva).
 
    • Delete dashboard data of the site for the last two months (if site was in drain that long) or wait for site to flush out
      • to delete data, right-click on cell in site readiness and select "Remove Cell from Database"
      • site should disappear from Site-Readiness after about two month (script will remove site after all feeding metrics provides no data for about a month)

Revision 242017-04-25 - StephanLammel

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 27 to 27
  If yes, then
    • lookup email address of site admin in SiteDB
    • send email to site admin asking her/him to remove support for VO CMS from site level BDII (advise that site executive should remove site completely from BDII if CMS was last/only VO supported)
Changed:
<
<
    • follow up with GGUS ticket for site or ROC
>
>
    • CMS does no longer use BDII, so this is for consistency only
 
  1. Squids: Stop monitoring squids

Revision 232017-01-17 - RokasMaciulaitis

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 32 to 32
 
  1. SITECONF: Remove the Site from SITECONF in GIT
Changed:
<
<
>
>
 
  1. SiteDB: Remove from SiteDB
Line: 41 to 40
 
Changed:
<
<
      • SiteDB responsible (Diego da Silva) has to manually remove the site.
>
>
 
  1. Dashboard & SSB: contact Dashboard team to remove site and to identify metrics that still feed info into SSB for the site
    • Ask the metric responsible to stop providing data for the site
      • Phedex

Revision 222017-01-16 - StephanLammel

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 35 to 35
 
  1. SiteDB: Remove from SiteDB
Changed:
<
<
    • email person with permissions to remove sites from SiteDB
>
>
    • ask Stephan or email other person with permissions to remove sites from SiteDB
 
    • https://cmsweb.cern.ch/sitedb/prod/sites
    • If the site does not apper here anymore, that means that v2 of SiteDB is already aware that the site does not exist.
    • If the site still appears in the "List of CMS site names and the SAM/BDII name used by WLCG" it is because the site is still in SiteDB

Revision 212017-01-10 - NataliaRatnikova

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 18 to 18
 
    • Phedex endpoints:
      • Remove Phedex endpoints and revoke PhEDEx DB roles (GGUS ticket to Transfer team)
      • Remove all links to/from the site in Prod/Debug/Dev (can be done by the transfer team)
Changed:
<
<
      • Rename site to XT2_PL_Cracow (should be done by Tony Wildish)
      • Remove the DB roles for T2PLCRACOW (should be done by Tony Wildish)
      • If an SE is renamed or changed: Site has to change that information in SiteDB, BDII and their storage.xml and site-local-config.xml. After that send an email to the factories and also to Tony Wildish to update the TMDB manually with the new SE name.
>
>
      • Rename site to XT2_PL_Cracow (should be done by Natalia )
      • Remove the DB roles for T2PLCRACOW (should be done by Natalia )
      • If an SE is renamed or changed: Site has to change that information in SiteDB, BDII and their storage.xml and site-local-config.xml. After that send an email to the factories and also to Natalia to update the TMDB manually with the new SE name.
 
  1. Check/Update BDII Information
    • check if site still advertises CMS support,
      ldapsearch -x -h lcg-bdii.cern.ch -p 2170 -b mds-vo-name=local,o=grid -LLL '(|(GlueSAAccessControlBaseRule=cms)(GlueSAAccessControlBaseRule=VO:cms)(GlueSAAccessControlBaseRule=VOMS:/cms/*)(GlueCEAccessControlBaseRule=VO:cms)(GlueCEAccessControlBaseRule=VOMS:/cms/*))' | grep Glue | grep UniqueID
      
      

Revision 202016-03-16 - RokasMaciulaitis

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 59 to 59
 
      • to delete data, right-click on cell in site readiness and select "Remove Cell from Database"
      • site should disappear from Site-Readiness after about two month (script will remove site after all feeding metrics provides no data for about a month)
      • site should disappear from Site-Readiness View depending on the Tier it belongs to. Tier 2 takes longest, three months.
Added:
>
>
      • another way to delete dashboard data is to run script:
         python deleteSiteInfo.py -c 154 -s T2_RU_RRC_KI -f "2015-01-01" -t "2015-02-02" 
        where -c is the column from which you wish to delete data -s is the site and -f and -t are from and to dates in which to delete the data. follow the steps and it'll create a file named dataToDelete.txt. Then create an unencrypted copy of your key at .globus with
        openssl rsa -in  ~/.globus/userkey.pem -out  ~/.globus/unencr_key.pem
        and finally
        cat datatoDelete.txt | xargs -n 1 curl -k -H "Accept : application/json" -X GET --cert ~/.globus/usercert.pem --key ~/.globus/unencr_key.pem
        That last step actually deletes the data, using the unencrypted cert for authentication with the dashboard web service.
 
  1. Tickets: Close all tickets for the site.

* Based on past experience: it took about 3 weeks to completely remove T2 Lisbon site (early 2013). \ No newline at end of file

Revision 192015-12-10 - DanielAbercrombie

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 29 to 29
 
    • send email to site admin asking her/him to remove support for VO CMS from site level BDII (advise that site executive should remove site completely from BDII if CMS was last/only VO supported)
    • follow up with GGUS ticket for site or ROC
  1. Squids: Stop monitoring squids
Changed:
<
<
>
>
 
  1. SITECONF: Remove the Site from SITECONF in GIT

Revision 182015-12-09 - StephanLammel

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 23 to 23
 
      • If an SE is renamed or changed: Site has to change that information in SiteDB, BDII and their storage.xml and site-local-config.xml. After that send an email to the factories and also to Tony Wildish to update the TMDB manually with the new SE name.
  1. Check/Update BDII Information
    • check if site still advertises CMS support,
      
      
Changed:
<
<
ldapsearch -x -h lcg-bdii.cern.ch -p 2170 -b mds-vo-name=local,o=grid -LLL '(|(GlueSAAccessControlBaseRule=cms)(GlueSAAccessControlBaseRule=VO:cms)(GlueSAAccessControlBaseRule=VOMS:/cms/*))' | grep GlueSEUniqueID
>
>
ldapsearch -x -h lcg-bdii.cern.ch -p 2170 -b mds-vo-name=local,o=grid -LLL '(|(GlueSAAccessControlBaseRule=cms)(GlueSAAccessControlBaseRule=VO:cms)(GlueSAAccessControlBaseRule=VOMS:/cms/*)(GlueCEAccessControlBaseRule=VO:cms)(GlueCEAccessControlBaseRule=VOMS:/cms/*))' | grep Glue | grep UniqueID
  If yes, then
    • lookup email address of site admin in SiteDB
    • send email to site admin asking her/him to remove support for VO CMS from site level BDII (advise that site executive should remove site completely from BDII if CMS was last/only VO supported)

Revision 172015-12-09 - StephanLammel

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 21 to 21
 
      • Rename site to XT2_PL_Cracow (should be done by Tony Wildish)
      • Remove the DB roles for T2PLCRACOW (should be done by Tony Wildish)
      • If an SE is renamed or changed: Site has to change that information in SiteDB, BDII and their storage.xml and site-local-config.xml. After that send an email to the factories and also to Tony Wildish to update the TMDB manually with the new SE name.
Changed:
<
<
  1. Update BDII Information
>
>
  1. Check/Update BDII Information
    • check if site still advertises CMS support,
      ldapsearch -x -h lcg-bdii.cern.ch -p 2170 -b mds-vo-name=local,o=grid -LLL '(|(GlueSAAccessControlBaseRule=cms)(GlueSAAccessControlBaseRule=VO:cms)(GlueSAAccessControlBaseRule=VOMS:/cms/*))' | grep GlueSEUniqueID
      
      If yes, then
 
    • lookup email address of site admin in SiteDB
    • send email to site admin asking her/him to remove support for VO CMS from site level BDII (advise that site executive should remove site completely from BDII if CMS was last/only VO supported)
    • follow up with GGUS ticket for site or ROC

Revision 162015-11-19 - StephanLammel

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Changed:
<
<
  1. Comute Elements of Site: Decommission the dedicated CMS CEs
>
>
  1. Compute Elements of Site: Decommission the dedicated CMS CEs
 
  1. Storage Elements of site Contact transfer team to relocate data and disable transfers to the site, i.e.:
    • SE Data: Ensure that all data on your SE is safely replicated to a custodial location
Line: 16 to 16
 
        • Transfer Team has to do a local invalidation of all datasets on the site (or global if it was the last copy) before proceeding with the removal in the usual way.
    • Phedex agents: Stop Phedex agents (Site Admin)
    • Phedex endpoints:
Changed:
<
<
      • Remove Phedex endpoints and revoke PhEDEx DB roles (Savannah ticket to Transfer team)
>
>
      • Remove Phedex endpoints and revoke PhEDEx DB roles (GGUS ticket to Transfer team)
 
      • Remove all links to/from the site in Prod/Debug/Dev (can be done by the transfer team)
      • Rename site to XT2_PL_Cracow (should be done by Tony Wildish)
      • Remove the DB roles for T2PLCRACOW (should be done by Tony Wildish)

Revision 152015-02-18 - StephanLammel

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 51 to 51
 
    • Can run into problems because SSB uses old v1 SiteDB api (as of early 2013).
      • The problem is that some of the SiteDB queries still return info of deleted sites, and some will not.
      • Contact SiteDB responsible (Diego da Silva).
Added:
>
>
    • Delete dashboard data of the site for the last two months (if site was in drain that long) or wait for site to flush out
      • to delete data, right-click on cell in site readiness and select "Remove Cell from Database"
      • site should disappear from Site-Readiness after about two month (script will remove site after all feeding metrics provides no data for about a month)
      • site should disappear from Site-Readiness View depending on the Tier it belongs to. Tier 2 takes longest, three months.
 
  1. Tickets: Close all tickets for the site.

* Based on past experience: it took about 3 weeks to completely remove T2 Lisbon site (early 2013). \ No newline at end of file

Revision 142015-02-06 - StephanLammel

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Line: 45 to 45
 
      • #good links in the site readiness view (Andrea Sciaba)
      • Production (Workflow team)
      • Site readiness (Site Support Team)
Added:
>
>
 
    • Can run into problems because SSB uses old v1 SiteDB api (as of early 2013).
      • The problem is that some of the SiteDB queries still return info of deleted sites, and some will not.
      • Contact SiteDB responsible (Diego da Silva).

Revision 132015-01-28 - StephanLammel

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
Changed:
<
<
  1. CEs: Decommission the dedicated CMS CEs
>
>
  1. Comute Elements of Site: Decommission the dedicated CMS CEs
 
Changed:
<
<
    • Remove from site level BDII that the CE supports CMS (email Site Admin (lookup in SiteDB) and GGUS ticket).
  1. Contact transfer team to relocate data and disable transfers to the site, i.e.:
>
>
  1. Storage Elements of site Contact transfer team to relocate data and disable transfers to the site, i.e.:
 
    • SE Data: Ensure that all data on your SE is safely replicated to a custodial location
    • VO CMS: Remove support for the VO CMS from SEs
      • Done in BDII (Site Admin)
Line: 22 to 21
 
      • Rename site to XT2_PL_Cracow (should be done by Tony Wildish)
      • Remove the DB roles for T2PLCRACOW (should be done by Tony Wildish)
      • If an SE is renamed or changed: Site has to change that information in SiteDB, BDII and their storage.xml and site-local-config.xml. After that send an email to the factories and also to Tony Wildish to update the TMDB manually with the new SE name.
Added:
>
>
  1. Update BDII Information
    • lookup email address of site admin in SiteDB
    • send email to site admin asking her/him to remove support for VO CMS from site level BDII (advise that site executive should remove site completely from BDII if CMS was last/only VO supported)
    • follow up with GGUS ticket for site or ROC
 
  1. Squids: Stop monitoring squids
Changed:
<
<
  1. GIT: Remove the Site from GIT (SITECONF)
>
>
  1. SITECONF: Remove the Site from SITECONF in GIT
 
  1. SiteDB: Remove from SiteDB
Line: 35 to 38
 
Deleted:
<
<
  1. BDII: Remove completely from BDII (Site Executive)
    • example check: ldapsearch -h lcg-bdii.cern.ch:2170 -x -b'GlueServiceUniqueID=ce02-cms.lip.pt_org.glite.ce.CREAM_686107625,Mds-Vo-name=LIP-Lisbon,Mds-Vo-name=local,o=grid'
 
  1. Dashboard & SSB: contact Dashboard team to remove site and to identify metrics that still feed info into SSB for the site
    • Ask the metric responsible to stop providing data for the site
      • Phedex

Revision 122015-01-22 - StephanLammel

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

Site Support Team - Documentation
Removing a CMS Site

  1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
  2. CEs: Decommission the dedicated CMS CEs
Changed:
<
<
 
    • Remove from site level BDII that the CE supports CMS (Site Admin).
  1. SE Data: Ensure that all data on your SE is safely replicated to a custodial location -->
contact transfer team
  • VO CMS: Remove support for the VO CMS from SEs
  • >
    >
      • Remove from site level BDII that the CE supports CMS (email Site Admin (lookup in SiteDB) and GGUS ticket).
    1. Contact transfer team to relocate data and disable transfers to the site, i.e.:
      • SE Data: Ensure that all data on your SE is safely replicated to a custodial location
      • VO CMS: Remove support for the VO CMS from SEs
     
      • Done in BDII (Site Admin)
    Changed:
    <
    <
    1. CMS Data: Delete all CMS data from site.
    >
    >
      • CMS Data: Delete all CMS data from site.
     
      • Through Phedex (Data Manager of the Site)
      • Deletion request of all replicas/subscriptions at the site.
      • Contact Users & Groups that have files on Site (/store/user & /store/group) (Data Manager of the Site or Site Admin)
      • If the deletion is stuck because the site is not running agents anymore:
        • Transfer Team has to do a local invalidation of all datasets on the site (or global if it was the last copy) before proceeding with the removal in the usual way.
    Changed:
    <
    <
    1. Phedex agents: Stop Phedex agents (Site Admin)
    2. Phedex endpoints:
    >
    >
      • Phedex agents: Stop Phedex agents (Site Admin)
      • Phedex endpoints:
     
      • Remove Phedex endpoints and revoke PhEDEx DB roles (Savannah ticket to Transfer team)
      • Remove all links to/from the site in Prod/Debug/Dev (can be done by the transfer team)
      • Rename site to XT2_PL_Cracow (should be done by Tony Wildish)

    Revision 112015-01-22 - StephanLammel

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

    Site Support Team - Documentation
    Removing a CMS Site

    1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
    2. CEs: Decommission the dedicated CMS CEs
    Changed:
    <
    <
      • Remove from BDII that the CE supports CMS (Site Admin).
    >
    >
      • Remove from site level BDII that the CE supports CMS (Site Admin).
     
     
    1. SE Data: Ensure that all data on your SE is safely replicated to a custodial location -->
    contact transfer team
  • VO CMS: Remove support for the VO CMS from SEs
    • Done in BDII (Site Admin)
  • Line: 25 to 25
     
    1. GIT: Remove the Site from GIT (SITECONF)
    Added:
    >
    >
     
    1. SiteDB: Remove from SiteDB
    Deleted:
    <
    <
      • to make sure that v1 of SiteDB is also aware of the removal - Contact Diego da Silva
     

    Revision 102014-11-17 - JohnArtieda

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

    Site Support Team - Documentation
    Removing a CMS Site

    Added:
    >
    >
    1. Morgue: Make sure the site is IN the morgue (down for production) and no jobs or data is being sent to it anymore.
     
    1. CEs: Decommission the dedicated CMS CEs
    Changed:
    <
    <
    >
    >
     
     
      • Remove from BDII that the CE supports CMS (Site Admin).
    1. SE Data: Ensure that all data on your SE is safely replicated to a custodial location -->
    contact transfer team
  • VO CMS: Remove support for the VO CMS from SEs
  • Line: 25 to 26
     
    1. GIT: Remove the Site from GIT (SITECONF)
    2. SiteDB: Remove from SiteDB
    Changed:
    <
    <
      • email to Oliver Gutsche
    >
    >
      • email person with permissions to remove sites from SiteDB
     
    Line: 40 to 41
     
        • Phedex
        • HammerCloud (Andrea Sciaba)
        • #good links in the site readiness view (Andrea Sciaba)
    Changed:
    <
    <
        • Production (Sten)
        • Site readiness (Duncan Ralph)
    >
    >
        • Production (Workflow team)
        • Site readiness (Site Support Team)
     
      • Can run into problems because SSB uses old v1 SiteDB api (as of early 2013).
        • The problem is that some of the SiteDB queries still return info of deleted sites, and some will not.
        • Contact SiteDB responsible (Diego da Silva).

    Revision 92013-11-22 - JohnArtieda

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

    Site Support Team - Documentation
    Removing a CMS Site

    1. CEs: Decommission the dedicated CMS CEs
    Line: 14 to 14
     
      • If the deletion is stuck because the site is not running agents anymore:
        • Transfer Team has to do a local invalidation of all datasets on the site (or global if it was the last copy) before proceeding with the removal in the usual way.
    1. Phedex agents: Stop Phedex agents (Site Admin)
    Changed:
    <
    <
    1. Phedex endpoints: Remove Phedex endpoints and revoke PhEDEx DB roles (Savannah ticket to Transfer team)
    >
    >
    1. Phedex endpoints:
      • Remove Phedex endpoints and revoke PhEDEx DB roles (Savannah ticket to Transfer team)
     
      • Remove all links to/from the site in Prod/Debug/Dev (can be done by the transfer team)
      • Rename site to XT2_PL_Cracow (should be done by Tony Wildish)
      • Remove the DB roles for T2PLCRACOW (should be done by Tony Wildish)
    Added:
    >
    >
      • If an SE is renamed or changed: Site has to change that information in SiteDB, BDII and their storage.xml and site-local-config.xml. After that send an email to the factories and also to Tony Wildish to update the TMDB manually with the new SE name.
     
    1. Squids: Stop monitoring squids
    2. GIT: Remove the Site from GIT (SITECONF)

    Revision 82013-07-19 - JohnArtieda

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

    Site Support Team - Documentation
    Removing a CMS Site

    Changed:
    <
    <
    1. Decommission the dedicated CMS CEs
    >
    >
    1. CEs: Decommission the dedicated CMS CEs
     
    Changed:
    <
    <
     
    1. Ensure that all data on your SE is safely replicated to a custodial location -->
    contact transfer team
  • Remove support for the VO CMS from SEs
  • >
    >
     
    1. SE Data: Ensure that all data on your SE is safely replicated to a custodial location -->
    contact transfer team
  • VO CMS: Remove support for the VO CMS from SEs
  •  
      • Done in BDII (Site Admin)
    Changed:
    <
    <
    1. Delete all CMS data from site.
    >
    >
    1. CMS Data: Delete all CMS data from site.
     
      • Through Phedex (Data Manager of the Site)
      • Deletion request of all replicas/subscriptions at the site.
      • Contact Users & Groups that have files on Site (/store/user & /store/group) (Data Manager of the Site or Site Admin)
      • If the deletion is stuck because the site is not running agents anymore:
        • Transfer Team has to do a local invalidation of all datasets on the site (or global if it was the last copy) before proceeding with the removal in the usual way.
    Changed:
    <
    <
    1. Stop Phedex agents (Site Admin)
    2. Remove Phedex endpoints and revoke PhEDEx DB roles (Savannah ticket to Transfer team)
    >
    >
    1. Phedex agents: Stop Phedex agents (Site Admin)
    2. Phedex endpoints: Remove Phedex endpoints and revoke PhEDEx DB roles (Savannah ticket to Transfer team)
     
      • Remove all links to/from the site in Prod/Debug/Dev (can be done by the transfer team)
      • Rename site to XT2_PL_Cracow (should be done by Tony Wildish)
      • Remove the DB roles for T2PLCRACOW (should be done by Tony Wildish)
    Changed:
    <
    <
    1. Stop monitoring squids
    >
    >
    1. Squids: Stop monitoring squids
     
    Changed:
    <
    <
    1. Remove the Site from GIT (SITECONF)
    >
    >
    1. GIT: Remove the Site from GIT (SITECONF)
     
    Changed:
    <
    <
    1. Remove from SiteDB
    >
    >
    1. SiteDB: Remove from SiteDB
     
    Changed:
    <
    <
    1. Remove completely from BDII (Site Executive)
      • to check: wget https://cmsweb.cern.ch/sitedb/reports/showXMLReport?reportid=cms_to_sam.ini -q -O - |grep -C 1 -i LIP
      • example check: ldapsearch -h lcg-bdii.cern.ch:2170 -x -b'GlueServiceUniqueID=ce02-cms.lip.pt_org.glite.ce.CREAM_686107625,Mds-Vo-name=LIP-Lisbon,Mds-Vo-name=local,o=grid'
      • can run into problems because SSB uses old v1 SiteDB api (as of early 2013).
        • The problem is that some of the SiteDB queries return the sites that are going to be deleted, and some will not.
        • BDII, SAM, Topology. These ones appear because the site is still in SiteDB
    >
    >
      • If the site does not apper here anymore, that means that v2 of SiteDB is already aware that the site does not exist.
      • to make sure that v1 of SiteDB is also aware of the removal - Contact Diego da Silva
      • If the site still appears in the "List of CMS site names and the SAM/BDII name used by WLCG" it is because the site is still in SiteDB
     
    Changed:
    <
    <
          • SiteDB responsible has to manually remove the site.
    1. contact Dashboard team to identify metrics that still feed info into SSB for the site, ask the metric responsible to stop providing data for this site
    >
    >
        • SiteDB responsible (Diego da Silva) has to manually remove the site.
    1. BDII: Remove completely from BDII (Site Executive)
      • example check: ldapsearch -h lcg-bdii.cern.ch:2170 -x -b'GlueServiceUniqueID=ce02-cms.lip.pt_org.glite.ce.CREAM_686107625,Mds-Vo-name=LIP-Lisbon,Mds-Vo-name=local,o=grid'
    2. Dashboard & SSB: contact Dashboard team to remove site and to identify metrics that still feed info into SSB for the site
      • Ask the metric responsible to stop providing data for the site
     
      • Phedex
      • HammerCloud (Andrea Sciaba)
      • #good links in the site readiness view (Andrea Sciaba)
      • Production (Sten)
      • Site readiness (Duncan Ralph)
    Changed:
    <
    <
    1. Close all tickets for the site.
    >
    >
      • Can run into problems because SSB uses old v1 SiteDB api (as of early 2013).
        • The problem is that some of the SiteDB queries still return info of deleted sites, and some will not.
        • Contact SiteDB responsible (Diego da Silva).
    1. Tickets: Close all tickets for the site.
     
    Deleted:
    <
    <
    References (based on past experience: it took about 3 weeks to completely remove T2 Lisbon site).
     \ No newline at end of file
    Added:
    >
    >
    * Based on past experience: it took about 3 weeks to completely remove T2 Lisbon site (early 2013).

    Revision 72013-07-11 - JohnArtieda

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

    Site Support - Documentation
    Removing a CMS Site

    >
    >

    Site Support Team - Documentation
    Removing a CMS Site

     
    1. Decommission the dedicated CMS CEs

    Revision 62013-07-11 - JohnArtieda

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

    Site Support - Documentation
    Removing a CMS Site

    1. Decommission the dedicated CMS CEs
    Line: 9 to 9
     
      • Done in BDII (Site Admin)
    1. Delete all CMS data from site.
      • Through Phedex (Data Manager of the Site)
    Added:
    >
    >
      • Deletion request of all replicas/subscriptions at the site.
     
      • Contact Users & Groups that have files on Site (/store/user & /store/group) (Data Manager of the Site or Site Admin)
    Added:
    >
    >
      • If the deletion is stuck because the site is not running agents anymore:
        • Transfer Team has to do a local invalidation of all datasets on the site (or global if it was the last copy) before proceeding with the removal in the usual way.
     
    1. Stop Phedex agents (Site Admin)
    Changed:
    <
    <
    1. Remove Phedex endpoints and revoke PhEDEx DB roles
      • Savannah ticket to Transfer team.
    >
    >
    1. Remove Phedex endpoints and revoke PhEDEx DB roles (Savannah ticket to Transfer team)
      • Remove all links to/from the site in Prod/Debug/Dev (can be done by the transfer team)
      • Rename site to XT2_PL_Cracow (should be done by Tony Wildish)
      • Remove the DB roles for T2PLCRACOW (should be done by Tony Wildish)
     
    1. Stop monitoring squids
    2. Remove the Site from GIT (SITECONF)
    3. Remove from SiteDB
      • email to Oliver Gutsche
    Added:
    >
    >
     
    1. Remove completely from BDII (Site Executive)
    Deleted:
    <
    <
     
      • example check: ldapsearch -h lcg-bdii.cern.ch:2170 -x -b'GlueServiceUniqueID=ce02-cms.lip.pt_org.glite.ce.CREAM_686107625,Mds-Vo-name=LIP-Lisbon,Mds-Vo-name=local,o=grid'
    Changed:
    <
    <
    1. contact Dashboard team to identify metrics that still feed info into SSB for the site, ask the metric responsible to stop providing data for this site
    >
    >
      • can run into problems because SSB uses old v1 SiteDB api (as of early 2013).
        • The problem is that some of the SiteDB queries return the sites that are going to be deleted, and some will not.
     
    Changed:
    <
    <
      • Phedex (Nicolo), HammerCloud (Andrea Sciaba), Production (Sten), Site readiness (Duncan Ralph)
    >
    >
          • v1 of SiteDB still thinks that the site is there
          • SiteDB responsible has to manually remove the site.
    1. contact Dashboard team to identify metrics that still feed info into SSB for the site, ask the metric responsible to stop providing data for this site
      • Phedex
      • HammerCloud (Andrea Sciaba)
      • #good links in the site readiness view (Andrea Sciaba)
      • Production (Sten)
      • Site readiness (Duncan Ralph)
     
    1. Close all tickets for the site.

    References (based on past experience: it took about 3 weeks to completely remove T2 Lisbon site).

    Revision 52013-07-10 - JohnArtieda

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

    Site Support - Documentation
    Removing a CMS Site

    1. Decommission the dedicated CMS CEs
    Line: 25 to 25
     
      • can run into problems because SSB uses old v1 SiteDB api (as of early 2013)
      • example check: ldapsearch -h lcg-bdii.cern.ch:2170 -x -b'GlueServiceUniqueID=ce02-cms.lip.pt_org.glite.ce.CREAM_686107625,Mds-Vo-name=LIP-Lisbon,Mds-Vo-name=local,o=grid'
    1. contact Dashboard team to identify metrics that still feed info into SSB for the site, ask the metric responsible to stop providing data for this site
    Added:
    >
    >
    1. Close all tickets for the site.
     References (based on past experience: it took about 3 weeks to completely remove T2 Lisbon site).

    Revision 42013-06-28 - JohnArtieda

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

    Site Support - Documentation
    Removing a CMS Site

    1. Decommission the dedicated CMS CEs
    Line: 15 to 15
     
      • Savannah ticket to Transfer team.
    1. Stop monitoring squids
    Changed:
    <
    <
    1. Remove the Site from SITECONF.
    >
    >
    1. Remove the Site from GIT (SITECONF)
     
    1. Remove from SiteDB
    Changed:
    <
    <
    1. Remove completely from BDII
    >
    >
      • email to Oliver Gutsche
    1. Remove completely from BDII (Site Executive)
     

    Revision 32013-06-24 - JohnArtieda

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

    Site Support - Documentation
    Removing a CMS Site

    1. Decommission the dedicated CMS CEs
    Line: 13 to 13
     
    1. Stop Phedex agents (Site Admin)
    2. Remove Phedex endpoints and revoke PhEDEx DB roles
      • Savannah ticket to Transfer team.
    Changed:
    <
    <
    1. Email cms-frontier-support@cernNOSPAMPLEASE.ch to stop monitoring squids
    >
    >
    1. Stop monitoring squids
     
    1. Remove the Site from SITECONF.
    2. Remove from SiteDB
    3. Remove completely from BDII

    Revision 22013-06-12 - JohnArtieda

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

    Site Support - Documentation
    Removing a CMS Site

    1. Decommission the dedicated CMS CEs
    Added:
    >
    >
     
    1. Ensure that all data on your SE is safely replicated to a custodial location -->
    contact transfer team
     
    1. Remove support for the VO CMS from SEs
      • Done in BDII (Site Admin)
    2. Delete all CMS data from site.
      • Through Phedex (Data Manager of the Site)
      • Contact Users & Groups that have files on Site (/store/user & /store/group) (Data Manager of the Site or Site Admin)
    3. Stop Phedex agents (Site Admin)
    Changed:
    <
    <
    1. Remove Phedex endpoints
    >
    >
    1. Remove Phedex endpoints and revoke PhEDEx DB roles
     
      • Savannah ticket to Transfer team.
    1. Email cms-frontier-support@cernNOSPAMPLEASE.ch to stop monitoring squids
    Added:
    >
    >
    1. Remove the Site from SITECONF.
     
    1. Remove from SiteDB
    2. Remove completely from BDII

    Revision 12013-06-11 - JohnArtieda

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

    Site Support - Documentation
    Removing a CMS Site

    1. Decommission the dedicated CMS CEs
    2. Remove support for the VO CMS from SEs
      • Done in BDII (Site Admin)
    3. Delete all CMS data from site.
      • Through Phedex (Data Manager of the Site)
      • Contact Users & Groups that have files on Site (/store/user & /store/group) (Data Manager of the Site or Site Admin)
    4. Stop Phedex agents (Site Admin)
    5. Remove Phedex endpoints
      • Savannah ticket to Transfer team.
    6. Email cms-frontier-support@cernNOSPAMPLEASE.ch to stop monitoring squids
    7. Remove from SiteDB
    8. Remove completely from BDII
    9. contact Dashboard team to identify metrics that still feed info into SSB for the site, ask the metric responsible to stop providing data for this site
    References (based on past experience: it took about 3 weeks to completely remove T2 Lisbon site).
     
    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