IFDH v2_x Marc Mengel FIFE Meeting 2016-08-24
Why v2_0? ifdh is expecting many changes in the next few years: ● Google cloud storage ● DUNE locations at BNL, Cern, etc. ● Changes curently require a recompile/relink ● Difficult to get users to upgrade – Some NOvA keepup still running v1_7_x – Tied into strict Art-suite versioning 2 4/10/17 Presenter | Presentation Title or Meeting Title
What did we do? This is a major rewrite of the file I/O portions of ifdh. ● ifdh cp, ifdh ls, etc. are all table driven ● Source code is about 2/3's its previous size ● Adding new protocols, etc. now is a config file change ● Many updates will now be a change to the “ifdh_config” package containing the config file and not require new binary code. 3 4/10/17 Presenter | Presentation Title or Meeting Title
Confjg file Format ● In .ini file format ● Several stanzas – [global] sets overal lists of protocols, prefixes, etc. – [prefix xxx] for each prefix maps to location – [location xxx] sets ● protocols location supports ● prefixes for each protocol – [protocol yyy] sets ● commands for ls, cp, etc ● regular expressions to parse ls output – [conditional ccc] has ● test rule for condition ● config file stanza rename
Actual Confjg ifdh.cfg
Why should I care? ● Once you upgrade to ifdhc v2_x – You need far less often to upgrade binary ifhdc package versions – We can configure special cases for file delivery, etc on the fly – As we try things like Google cloud storage, this can be config-file only update
Recommend
More recommend