Difference: DcacheXrootd (21 vs. 22)

Revision 222014-01-14 - FabioMartinelli

Line: 1 to 1
 
META TOPICPARENT name="CmsXrootdArchitecture"
Line: 256 to 256
 

Useful Links.

Changed:
<
<

Xrootd, gPlazma2 and dcache-2.6.16-1

>
>

Xrootd, gPlazma2 and dcache-2.6.19-1

 

Disclaimer

Changed:
<
<
21-11-2013 Fabio Martinelli: This is my personal experience with the triple [ SLAC Xrootd, gPlazma2 and dcache-2.6.16-1 ], it was not tested by other sites, it was not approved by CMS, it simply worked for me and I thought it was worth to report my experiences here ( it took me 1 day of tests ).
>
>
14th Jan 2014 Fabio Martinelli: This is my personal experience with the triple [ SLAC Xrootd, gPlazma2 and dcache-2.6.19-1 ] and it was not approved by CMS, it simply worked for me and I thought it was worth to report my experiences here ( it took me a day of tests ).
 

Intro

Changed:
<
<
The dCache 2.6 Admin can avoid to manage both a gPlazma1 and a gPlazma2 configuration and simply use the gPlazma2 cell also for the dCache Xrootd cell; to achieve that I did the following configurations on my T3; be aware that writes by xrootd are not allowed because of the empty list xrootdAllowedWritePaths=
>
>
The dCache 2.6 Admin can avoid to manage both a gPlazma1 and a gPlazma2 configuration and simply use the gPlazma2 cell also for the dCache Xrootd cell; to achieve that I did the following configurations; be aware that writes by xrootd are not allowed because of the empty list xrootdAllowedWritePaths=
 

Xrootd conf

More... Close
<!--/twistyPlugin twikiMakeVisibleInline-->

 
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