[Opendnssec-develop] 1.4.0a xml migration
sion at nominet.org.uk
Wed Mar 14 12:50:27 UTC 2012
On 14/03/12 12:10, Matthijs Mekking wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 03/14/2012 12:50 PM, Siôn Lloyd wrote:
>> On 14/03/12 11:44, Rickard Bellgrim wrote:
>>>> It occurred to me that we need to write a script to migrate a users xml
>>>> files to be compatible with the new rng files. (I think that this
>>>> just means
>>>> dropping, or commenting out, all auditor tags... Is there anything
> The following changes are made:
> - -ZoneFetchFile
> - -ToolsDirectory
> - -Auditor
> +Listener (optional)
> - -Audit
> - -Audit
> and zonefetch is replaced with adddns.
>>>> Do we need this for the alpha release? Or do we trust folk who use an
>>>> release to be able to comment these lines out themselves, and just
>>>> it in the notes?
>>> We currently install sample files of the configuration. I think you
>>> usually never touch the users configuration. Isn't mostly up to them
>>> to correct any changes in the configuration?
> So there is no clean upgrade from 1.3 to 1.4? (because the components
> will complain about the audit tag).
The enforcer will not run against the old xml as if the rng check fails
it stops... So it is worse than just complaining.
>> So we just need some documentation to say which tags need to go? That
>> works too; I had just thought of this as a migration like any other.
> Is there a migration script for the kasp database (required) ?
Yes, because new columns are added for the adapters.
I think that documentation is okay for an alpha release; but when we
actually go to 1.4.0 we should provide a migration script.
More information about the Opendnssec-develop