Difference: ProductionOperationsWLCGJan10Reports (3 vs. 4)

Revision 42010-06-11 - PeterJones

Line: 1 to 1
 

January 2010 Reports

To the main

29th January 2010 (Friday)

Line: 262 to 262
  Problem at the sites
  • T0 sites issues:
Changed:
<
<
    • LFC Read-Only problem pointed to be due to the CORAL interface used by some user's application.
      • Possible solution: LFC interface of CORAL to be uptodated plus increasing the h/w and threads behind lfc-lhcb-ro instance at CERN. DIRAC will start also to use all T1's instances so far unused. The reason of this last sentence is that we did not feel confident so far in using our mirrors because of the incoherent status of the replication often caught. 3D people vouching for the integrity of the mirrors is a reason more to start using
>
>
    • LFC Read-Only problem pointed to be due to the Persistency interface used by some user's application.
      • Possible solution: LFC interface of Persistency to be uptodated plus increasing the h/w and threads behind lfc-lhcb-ro instance at CERN. DIRAC will start also to use all T1's instances so far unused. The reason of this last sentence is that we did not feel confident so far in using our mirrors because of the incoherent status of the replication often caught. 3D people vouching for the integrity of the mirrors is a reason more to start using
 
      • Before Xmas we left with the idea to intervene on our CASTOR stager to implement the ACLs successfully tested in November. Is there any scheduled intervention in the pipeline whose slot can be used to also bring this new permission schema into production?
  • T1 sites issues
 
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