Changes between Initial Version and Version 1 of tier-one-meeting-20170110


Ignore:
Timestamp:
01/10/17 16:00:46 (2 years ago)
Author:
paul
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • tier-one-meeting-20170110

    v1 v1  
     1[[TOC(depth=0)]] 
     2= dCache Tier I meeting January 10, 2017 = 
     3[part of a [wiki:developers-meetings series of meetings]] 
     4 
     5== Present == 
     6 
     7dCache.org(Paul, Tigran), PIC(Marc), KIT(Xavier) 
     8 
     9= Agenda = 
     10 
     11(see box on the other side) 
     12 
     13= Site reports = 
     14 
     15== PIC == 
     16 
     17Everything was OK over Christmas, so no incidences to report. 
     18 
     19=== Problem with enstore === 
     20 
     21Migration to 2.16 issue with enstore -- email to Dmitry -- cc Sasha --  
     22 
     23Function in Chimera called enstoreLevel2Info.  Upload new files to dCache -- t_locationinfo  fields have a different order. 
     24 
     25The error looks like: 
     26 
     27    [chimera@127.0.0.1(50682):chimera] 2017-01-02 13:33:58 GMT: QUERY: INSERT INTO t_locationinfo VALUES (NEW.inumber,0,'enstore:',10,NOW(),NOW(),1) 
     28 
     29Marc to open a ticket. 
     30 
     31=== UPgrade delayed === 
     32 
     33Plan to update 17th of January, but 
     34 
     35Scheduled update to v6 of enstore.   
     36 
     37Plan upgrade to v3 this year. 
     38 
     39=== New instance === 
     40 
     41PIC supports the VO CIEMAT.  Plan to create a federated storage using dCache, similar to NDGF. 
     42 
     43== KIT == 
     44 
     45Things are running well -- no problems within dCache over last 3 weeks. 
     46 
     47=== SQL function === 
     48 
     49Tigran to work on this 
     50 
     51=== Migration of tape to HPSS === 
     52 
     53Internally uses MD5 checksums. 
     54 
     55Can dCache support MD5 checksums? 
     56 
     57Sort of -- with the limitations that a pool uses a single checksum algorithm and WLCG still uses ADLER32.  dCache can store multiple checksums, but there's currently no mechanism to generate multiple checksums. 
     58 
     59= Support tickets for discussion = 
     60 
     61[Items are added here automagically] 
     62 
     63= DTNM = 
     64 
     65Proposed: same time, next week.