forked from EUDAT-B2SAFE/B2SAFE-core
-
Notifications
You must be signed in to change notification settings - Fork 0
/
changelog.txt
135 lines (115 loc) · 6.58 KB
/
changelog.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
B2SAFE package 4.2.0 [2019/01/07]
- fixed bug related to redundant replica handles (https://github.com/EUDAT-B2SAFE/B2SAFE-core/issues/120)
- updated test rules
- improved wiki docuentation
- added support for oauth2 protocol via PAM module
- added support to HTTP interfaces in the PID parameters
B2SAFE package 4.1.1 [2018/02/22]
- fixed bug related to EUDATTransferUsingFailLog rule (https://github.com/EUDAT-B2SAFE/B2SAFE-core/issues/113)
- updated test rules
B2SAFE package 4.1.0 [2017/12/18]
- tested sucessfully against iRODS v4.2.1. The test against iRODS 4.2.2 failed due to this bug: https://github.com/irods/irods/issues/3722, therefore the v4.2.2 is not supported yet.
- fixed bug related to EUDATReplication rule (https://github.com/EUDAT-B2SAFE/B2SAFE-core/issues/102)
- improved install.txt documentation (https://github.com/EUDAT-B2SAFE/B2SAFE-core/issues/103)
- added EUDATeURLupdateColl(*PID, *newURL) to update the url in multiple PIDS associeted to a whole collection of objects.
- many improvements in the logging
- added the option to specify the destination iRODS resource in many rules, included the EUDATReplication.
B2SAFE package 4.0.1 [2017/07/11]
- added support for iRODS 4.2.1 (https://github.com/EUDAT-B2SAFE/B2SAFE-core/issues/94)
- fixed bug related to package deployment (https://github.com/EUDAT-B2SAFE/B2SAFE-core/issues/85)
- updated test rules (https://github.com/EUDAT-B2SAFE/B2SAFE-core/issues/89)
- implemented bulk actions in epicclient2.py (https://github.com/EUDAT-B2SAFE/B2SAFE-core/issues/91)
B2SAFE package 4.0.0 [2017/04/12]
Tested with iRODS 4.1.x and 4.2.0.
Compatible with EPIC API and HSv8 API.
- added support for iRODS v4.2.0
- added support for the EUDAT PID profile
- changed epic client to support new b2handle library
- python script code cleaning
- initial support of the metadata module (added a couple of rules)
- various bug fixing
- initial support for the ARGO messaging system
B2SAFE package 3.1.3 [2017/01/04]
bug fixing release:
- fixed many epicclents bugs
- fixed authentication script to sync B2SAFE and B2ACCESS
- fixed iCatCache true to have a consistent behaviour in the EUDATCreatePID rule
B2SAFE package 3.1.2 [2016/10/25]
It includes:
- Few new rules implementing minor functions to rerieve PID record key-value
pair and to convert boolean values.
- An experimental new feature, which is a proof of concept, so not ready for
production: the metadata ingestion scripts. It is a set of python script to generate a METS
manifest file for a collection, parse it and populate a neo4j graphDB.
B2SAFE package 3.2-beta [2016/08/24]
It includes two main new features:
1) the monitoring probe for iRODS: a bash script compatible with nagios-like tools to actively monitor the iRODS server
2) the metadata ingestion scripts: a set of python script to generate a METS manifest file for a collection, parse it and populate a neo4j graphDB.
B2SAFE package 3.1.1 [2016/04/22]
- added support for HSv8
- initial implementation of the role based approach for the authorization mechanism
- fixed the memory leak related to the call of external executables
- added the option to switch to a faster configuration for the PID creation
B2SAFE package 3.1.0-beta [2016/02/09]
new version of the authentication scripts
B2SAFE package 3.0.2 [2015/11/27]
improved deployment procedure: now it is possible to build the binary packages as a user different from the iRODS administrator.
B2SAFE package 3.0.1 [2015/10/30]
fixed support for debian package bulding
B2SAFE package 3.0.0 [2015/10/23]
This version is compatible with iRODS v4.x .
It is still backward compatible with iRODS 3.3.1 .
- added more flexibility in data replication: it is now possible to replicate
data and register them asynchronously.
- improved the response messages of the main replication, registration and data
integrity chek rules
- removed the need of a shared collection
- added a couple of features as a preview: asynchronous messaging and system
metadata handling.
- consolidated the deployment procedure.
B2SAFE package 3.0 [2014/12/18]
This is the first version compatible with iRODS v4.0.x .
It is still backward compatible with iRODS 3.3.1 .
- added two further dependencies: defusedxml, lxml .
- improved documentation
- added new rules: EUDATgetLastAVU, EUDATModifyAVU, EUDATcountMetaKeys
EUDATrp_checkMeta, EUDATrp_ingestObject, EUDATrp_transferInitiated, EUDATrp_transferFinished
B2SAFE module 2.3 [2014/10/30]
Unless you need to apply the patches mentioned in the documentation, there
is no need to recompile the module.
- completed the implementation of the integrity check tools
- extended the authentication mechanism to import automatically X.509 certificate DN
- improved the EPIC client, adding more command line options, optimizing the code
and improving security against XML vulnerabilities.
- added new rules: EUDATiCHECKSUMdate, EUDATeURLsearch, EUDATIntegrityCheck, EUDATVerifyCollection
- added a script named quota_stats.py to calculate the storage stats (used space, number of objects)
per collection
- added new document "tutorial" in the docs directory
B2SAFE module 2.2.1 [2014/08/22]
This is mainly a bug fix release with minor updates related to deployment,
test and integrity check scripts.
Unless you need to apply the patches mentioned in the documentation, there
is no need to recompile the module.
- fixed URI retrieval in the epic client function modifyHandle
- fixed the PPID update in function EUDATCreatePID
- updated docs/integrityCheck.pdf and docs/administrator.guide.pdf.
- fixed a function name mismatch related to the rule EUDATUpdateLogging in catchError.re
- added a test module for all scripts in cmd
- update fix regarding to function EUDATeCHECKSUMupdate
- update of the shell based install script
- added script for verification of checksums on TSM
B2SAFE module 2.2 [2014/07/09]
- defined a set of properties to publish the basic local B2SAFE configuration
- on demand checksum generation and verification tools based on replica location paths
- partial implementation of a basic authentication mechanism: sync of remote user accounts with local cache
B2SAFE module 2.1 [2014/06/04]
- refined the integrity check mechanism
- defined a rule for the replication of a collection of objects
- added a script to deploy automatically the module
- bug fixing
B2SAFE module 2.0 [2014/04/13]
- added an integrity check mechanism: see <module_home>/docs/integrityCheck.pdf
- improved the PID interlinking mechanism: see <module_home>/docs/PID_interlinking-1.pdf
- defined a rule for the replication of a single object: see <module_home>/docs/transferSingleFile.jpg
- added a new logging mechanism
- added a new authorization mechanism