Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Prochaine révision
Révision précédente
access_to_cms_data_at_cc-in2p3 [2016/12/05 14:43]
127.0.0.1 modification externe
access_to_cms_data_at_cc-in2p3 [2016/12/16 10:15] (Version actuelle)
Ligne 7: Ligne 7:
 \\ \\
  
-====== Chapitre 1 :  http:%%//%%www.dcache.org/​manuals/​Book/​cookbook/​cb-net-firewall.shtml ======+====== Chapitre 1 :  http://​www.dcache.org/​manuals/​Book/​cookbook/​cb-net-firewall.shtml ======
  
  
Ligne 60: Ligne 60:
 If the //<​dCapDoorPort>//​ is not specified, 22125 is used to establish a TCP connection to //<​dCapDoorHostFQN>//​ (see next paragraph). In this case no NFS mount is needed anymore. However, the access is unauthenticated and therefore access is only granted if the “  other  ” part of the UNIX rights are set accordingly. In other words: The user is mapped to nobody for unauthenticated dCap access. If the //<​dCapDoorPort>//​ is not specified, 22125 is used to establish a TCP connection to //<​dCapDoorHostFQN>//​ (see next paragraph). In this case no NFS mount is needed anymore. However, the access is unauthenticated and therefore access is only granted if the “  other  ” part of the UNIX rights are set accordingly. In other words: The user is mapped to nobody for unauthenticated dCap access.
  
-In both cases (  pnfs  mount and URL access) the dCap client (dCap library or  **dccp** ​ command) will connect to the dCap door (doorDomain) on the admin node with TCP port 22125 (can be changed in **config/​dCacheSetup** with dCapPort). After the pool manager selected a pool to be used for the transfer ( [[http://​cctools.in2p3.fr/​baseConnaissance/​php/​config/​cf-pm-psu.shtml|the section called “The Pool Selection Mechanism”]] describes how to configure that selection mechanism.) this pool will establish the data connection to the client on a TCP port which has been selected by the client. The port range to use may be specified on the client side (e.g. by the -p option of the  **dccp** ​ command.)+In both cases (  pnfs  mount and URL access) the dCap client (dCap library or  **dccp** ​ command) will connect to the dCap door (doorDomain) on the admin node with TCP port 22125 (can be changed in **config/​dCacheSetup** with dCapPort). After the pool manager selected a pool to be used for the transfer ( [[#cf-pm-psu.shtml|the section called “The Pool Selection Mechanism”]] describes how to configure that selection mechanism.) this pool will establish the data connection to the client on a TCP port which has been selected by the client. The port range to use may be specified on the client side (e.g. by the -p option of the  **dccp** ​ command.)
  
 This protocol should be used for local, trusted access only, because it is not authenticated?​ This protocol should be used for local, trusted access only, because it is not authenticated?​
Ligne 85: Ligne 85:
 A GridFTP client connects to one of the GridFTP doors on TCP port 2811. The data connections are established independent of the direction of the data transfer. In “  active ​ ” FTP mode the server connects to the client while in “  passive ​ ” FTP mode the client connects to the server. A GridFTP client connects to one of the GridFTP doors on TCP port 2811. The data connections are established independent of the direction of the data transfer. In “  active ​ ” FTP mode the server connects to the client while in “  passive ​ ” FTP mode the client connects to the server.
  
-In “  active ​ ” FTP mode the pool selected by the pool manager (see [[http://​cctools.in2p3.fr/​baseConnaissance/​php/​config/​cf-pm-psu.shtml|the section called “The Pool Selection Mechanism”]] ) will open one or more data connections to the client on a TCP port in the range between 20000 and 25000. In “  passive ​ ” FTP mode, the client will establish the data connections to the GridFTP door in the same port range. The pool will connect to the door and the door will route the data traffic. It is not possible to establish a direct connection between pool and client in “  passive ​ ” mode, because the FTP protocol redirection mechanism has to be triggered before the client sends the name of the requested file.+In “  active ​ ” FTP mode the pool selected by the pool manager (see [[#cf-pm-psu.shtml|the section called “The Pool Selection Mechanism”]] ) will open one or more data connections to the client on a TCP port in the range between 20000 and 25000. In “  passive ​ ” FTP mode, the client will establish the data connections to the GridFTP door in the same port range. The pool will connect to the door and the door will route the data traffic. It is not possible to establish a direct connection between pool and client in “  passive ​ ” mode, because the FTP protocol redirection mechanism has to be triggered before the client sends the name of the requested file.
  
  
Ligne 155: Ligne 155:
  
  
-===== 1. Which MC-samples have been requested? =====+=====  Which MC-samples have been requested? =====
  
 https://​cmsweb.cern.ch/​prodrequest/​ProdRequest/​getHome https://​cmsweb.cern.ch/​prodrequest/​ProdRequest/​getHome
Ligne 162: Ligne 162:
  
  
-===== 2. What is the number of events already publicly available? =====+=====  What is the number of events already publicly available? =====
  
 http://​cmsdbs.cern.ch/​DBS2_discovery/​ http://​cmsdbs.cern.ch/​DBS2_discovery/​
  
  
-===== 3. What is the status of the production? =====+=====  What is the status of the production? =====
  
 https://​cmsweb.cern.ch/​prod-mon/​ https://​cmsweb.cern.ch/​prod-mon/​
Ligne 230: Ligne 230:
  
  
-==== 0.1.  lcg-cp ====+====   lcg-cp ====
  
 <​code>​ <​code>​
Ligne 262: Ligne 262:
 </​code>​ </​code>​
  
-===== 1.  Access From the VOBOX  =====+=====   Access From the VOBOX  =====
  
 <​code>​ <​code>​
  • access_to_cms_data_at_cc-in2p3.txt
  • Dernière modification: 2016/12/16 10:15
  • (modification externe)