Difference: RedirectorsSubscription (18 vs. 19)

Revision 192015-08-24 - MarianZvada

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

Redirectors subscription overview

AAA - Make accessible Any data from the existing distributed CMS data cache to scientists Anywhere, Anytime. The resulting system - hierarchy of redirectors - improves the scientific productivity of CMS physicists reach the data, as well as effectivness of the storage infrastructures deployed among the CMS Tier-1/2/3 worldwide. Access is based on XRoodtD protocol.
>
>

Redirectors (site managers) subscription overview

AAA - Make accessible Any data from the existing distributed CMS data cache to scientists Anywhere, Anytime. The resulting system - hierarchy of redirectors - improves the scientific productivity of CMS physicists reach the data, as well as effectiveness of the storage infrastructures deployed among the CMS Tier-1/2/3 worldwide. Access is based on XRoodtD protocol.
 
Changed:
<
<
The hierarchical subscription of XRootD managers provides resiliency in data access towards clients. Effectivelly this means if accessed data are not available at given site where job lands client will be resilently redirected to the closest data available within the hierarchy of redirectors to the storage server where the data exist.
>
>
prod-transit-diagram.png

The hierarchical subscription of XRootD managers (cmsd process) provides resiliency in data access towards clients. Effectively this means if accessed data are not available at given site where job lands client will be resiliently redirected to the closest data available within the hierarchy of redirectors to the storage server where the data exist.

 
Line: 14 to 16
  Please note the '+' in the xrootd-clustered.cfg file, it means the IP is known to be multiply resolved, and hence a multiple connection to the redirector will take place. A restart of all the daemons is needed, refer to this section below when your configuration is ready.
Changed:
<
<

US sites

Being part of CMS AAA in the US region, we do require your site to be whitelisted, otherwise redirections will fail with autherntication troubles. If you experience that or you are completely new site, contact us to specify your domain to be added in allow list in the US regional redirector. Contact you can find below the following steps that are pre-requisite as postinstall of your xrootd redirector/servers configuration.

Editing xrootd config - T1/T2 sites

>
>

Site allow list

Being part of CMS AAA production federation, we do require your site to be whitelisted, otherwise site manager (cmsd process) won't authenticate in the hierarchy of redirectors. If you experience that or you are completely new site, contact us to specify your domain to be added in allow list in the US regional redirector.

US sites subscription

Editing xrootd config

 Locate configuration file xrootd-clustered.cfg on your site redirector or server and point it to cmsxrootd.fnal.gov:1213. This requires following change, if you are already subscribed to xrootd.unl.edu replace the line:
   all.manager meta xrootd.unl.edu:1213 
Line: 28 to 32
  all.manager meta all cmsxrootd.fnal.gov+ 1213
Changed:
<
<
When ready, continue with TFC (fallback) configuration. Also, if you're T3 site without local redirecgtor, please refer to the next chapter.

Note: this configuration assumes site runs local redirector in front of the site's xrootd servers. Local redirector subscription to regional redirector is recommended hierarchical setup of redirectors, where site's xrootd servers should subscribe to local redirector. Here example:

>
>

Using site local redirector

This configuration assumes site runs local redirector in front of the site's xrootd servers. Local redirector subscription to regional redirector is recommended hierarchical setup of redirectors, where site's xrootd servers should subscribe to local redirector first. Here example:
 
   # this is part of xrootd-clustered.cfg file of local redirector (site manager).
   all.role manager 
Line: 44 to 47
  all.manager :1213 # this subscribes server to your local redirector
Changed:
<
<

Editing xrootd config - T3 sites

This configuration assumes T3 not running local redirector thus expects direct subscription to the regional redirector. Site admin needs to do slightly different subscription method in the xrootd server configuration file:
>
>
Does your configuration supports TFC (fallback)?

NOT using local redirector

This configuration assumes site not running local redirector thus expects direct subscription of xrootd servers to the regional redirector. Site admin needs to do slightly different subscription method in the xrootd server configuration file:
 
   # this is part of xrootd-clustered.cfg file of xrootd server
Line: 53 to 58
  all.manager cmsxrootd.fnal.gov+ 1213
Added:
>
>
When ready, continue with TFC (fallback) configuration.
 If you think your site needs different subscription method, please, consult settings at hn-cms-wanaccess@cernNOSPAMPLEASE.ch.
Changed:
<
<

EU sites

>
>

EU/Asia sites subscription

 

Editing xrootd config

You simply need to point your site redirector or servers (depending whether you have a site redirector) to xrootd-cms.infn.it:1213.
Line: 67 to 74
 with
Changed:
<
<
all.manager any xrootd-cms.infn.it+ 1213 # if configuring a server
>
>
all.manager xrootd-cms.infn.it+ 1213 # if configuring a server
 

OR

Line: 79 to 86
 with
Changed:
<
<
all.manager meta any xrootd-cms.infn.it+ 1213 # if configuring a local
>
>
all.manager meta all xrootd-cms.infn.it+ 1213 # if configuring a local
 
Deleted:
<
<
 PLEASE NOTE: now we have introduced italian and french redirectors, in order to partition the traffic in a better way. Italian sites should substitute the 1213 with 1313, french sites with 1413. You may want to contact Andrea Sartirana (FR) or Tommaso Boccali (IT).
Line: 90 to 95
 In any case, the basic action is substituting xrootd.ba.infn.it with xrootd-cms.infn.it. The latter is a RR-DNS entry, which points also to the old server, so the action should not be disruptive. When ready, continue with TFC (fallback) configuration.
Added:
>
>

Transitional Federation

Transitional Federation isolates all sites not passing production federation criteria plus integrates T3 sites in the separate federation. Such sites are blocked in the production federation. If your site is not (or blocked) in the allowed list of production federation you can still benefit from the data access within transitional federation if you subscribe into it. Primarily, transitional federation serves data among T3 sites and also provides fallback (one-way) access for those in production who request data present only in the transitional federation. Joining transitional federation is easy to do:

Using local redirector

This configuration assumes site runs local redirector in front of the site's xrootd servers. Local redirector subscription to the redirector in higher level of hierarchy of redirectors is recommended. In this sense, site's xrootd servers should subscribe to local redirector first. Here example:
   # this is part of xrootd-clustered.cfg file of local redirector (site manager).
   all.role manager 
   all.manager <host_name_of_local_redirector>:1213 
   all.manager meta all cms-xrd-transit.cern.ch+ 1213    # this subscribes your local redirector to transitional redirector
And all xrootd servers at a site should subscribe to your local redirector as follows:
   # this is part of xrootd-clustered.cfg file of xrootd server
   all.role server
   all.manager <host_name_of_local_redirector>:1213  # this subscribes server to your local redirector
When ready, continue with TFC (fallback) configuration.

NOT using local redirector

This configuration assumes site not running local redirector thus expects direct subscription of xrootd servers to the transitional top level redirector. Each xrootd server should then use following lines in the xrootd configuration file:

   # this is part of xrootd-clustered.cfg file of xrootd server     # this subscribes your xrootd server directly to transitional redirector
   all.role server
   all.manager cms-xrd-transit.cern.ch+ 1213
When ready, continue with TFC (fallback) configuration.
 

Fallback: editing site TFC

This section assumes your site has implemented TFC trick - if you are completely new to TFC changes, you should skip it and follow this document.
Line: 143 to 176
 ...
Changed:
<
<
NOTE: REDIRECTOR is the full redirector hostname you should have subscribed to (either US or EU one). SITE_NAME is your particular site according to the CMS site naming convention (e.g. T2_US_Nebraska if you are testing subscription of Nebraska). Success in the process of subscription is defined by 'Location IP' result which will be your site server hosting the SAM test file. If not (e.g. seeing as result No matching files were found ) there is something wrong and you should contact for further assistance: hn-cms-wanaccess@cernNOSPAMPLEASE.ch.
>
>
NOTE: REDIRECTOR is the full redirector hostname you should have subscribed into (either US, EU or transitional redirector). SITE_NAME is your particular site according to the CMS site naming convention (e.g. T2_US_Nebraska if you are testing subscription of Nebraska). Success in the process of subscription is defined by 'Location IP' result which will be your site server hosting the SAM test file. If not (e.g. seeing as result No matching files were found ) there is something wrong and you should contact for further assistance: hn-cms-wanaccess@cernNOSPAMPLEASE.ch.
  Also, it may take a while things get propagated through the whole system and thus No matching files were found could be expected if you do xrd REDIRECTOR locateall ... right after the change. Reasonable time to wait would be ~30mins. If inpatient, you can still try xrdcp test:
Line: 154 to 187
 In case of troubles, contact us at: \ No newline at end of file
Added:
>
>
  • Production and Transitional federation schematic overview:

META FILEATTACHMENT attachment="prod-transit-diagram.png" attr="h" comment="Production and Transitional federation schematic overview" date="1440445526" name="prod-transit-diagram.png" path="prod-transit-diagram.png" size="122587" user="zvada" version="1"
 
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