Changes between Version 52 and Version 53 of ReleaseNotes/SCDB
- Timestamp:
- Dec 23, 2010, 3:27:05 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReleaseNotes/SCDB
v52 v53 25 25 || 15/01/10 || [milestone:SCDB-2.3.3 2.3.3] || (really!) fixed `update.vo.config` (bugs in VO group processing) || 26 26 || 22/01/10 || [milestone:SCDB-3.0.0 3.0.0] || SCDB [milestone:SCDB-2.3.3 2.3.3] + SVN 1.5/16 support (SVN 1.4 no longer supported) || 27 || 23/12/10 || [milestone:SCDB-3.1.O 3.1.0] || New VOConfigTask (full rewrite, same features) || 27 28 28 29 == Known Problems == 29 30 31 === 3.1.0: new VOConfigTask backward compatibility === #KB310VOConfigTask 32 33 As described in [#310VOConfigTask new features], SCDB [milestone:SCDB-3.1.O 3.1.0] provides a new version of `VOConfigTask` that implements a new algorithm for account name generation. This new algorithm is better at producing unique account names and is used by default. In an existing configuration, it is important to disable this new algorithm and to use the legacy one as changing account names requires a lot of planning and '''should not be attempted on the fly'''. 34 35 To use the legacy algorithm, it is necessary to add in `quattor.build.properties` (located in the same directory as `quattor.build.xml`) the following line: 36 {{{ 37 legacySuffixAlgorithm=false 38 }}} 39 30 40 === 3.0.0 requires svnkit >= 1.2 === 31 41 … … 41 51 42 52 == New and Changed Features == 53 54 === 3.1.0: full rewrite of VOConfigTask === #310VOConfigTask 55 56 VOConfigTask has been rewritten from scratch to solve maintainability issues and to provide support for more VO parameters from the VO ID cards. This also provides improved consistency checks of the parameters in the VO ID card. The main visible changes are: 57 58 * A VOMS server certificate is not added to the configuration if it is not valid or expired. As a result, a lot of previously declared `oldcert` are now removed. 59 * `oldcert` is not added to the VO configuration if there is not an existing certificate valid and different from the one in the VO card. 60 * A new algorithm has been implemented to produce unique account names for each different FQAN. A flaw in the previous algorithm tended to generate the same account name for several FQANs (it was based on FQAN length) and had to retry several times before finding a unique one, making the generated account name dependent on FQAN order. The new algorithm is used by default: to produce backward compatible templates, see [#KB310VOConfigTask known problems] above. 61 43 62 44 63 === 3.0.0: update_yum_repos script added ===