Skip Menu | Logged in as guest | Logout
 
Ticket metadata
Id: 2851
Status: resolved
Priority: 4/0
Queue: vdt-internal

Fixed in: (no value)
Fix scheduled: (no value)

Owner: Scot Kronenfeld
Requestors: Alain Roy
Cc:
AdminCc:

New reminder:

Created: Wed Aug 01 10:50:19 2007
Starts: Not set
Started: Not set
Last Contact: Wed Aug 01 11:25:39 2007
Due: Not set
Closed: Mon Aug 20 13:36:37 2007
Updated: Mon Aug 20 13:36:37 2007 by roy



History Brief headersFull headers
Subject: Change vdt-update-certs to backup certificates
Download (untitled) / with headers
text/plain 581b
We should backup the old certificates in vdt-update-certs, so if there
is a total failure, people can recover.

I had some code to do a backup, but it was sucky because it wasn't part
of the filelist and Scot rightfully commented it out.

We should think about the right way to do the backup. A few ideas:
- Should we backup in in the same base directory, so the backup is
easy to find?
If so, we need to adjust the package file list.
- Should we do backups like vdt-untar does them? I'm not sure of the
implications of that.
- We should garbage collect old backups.
Download (untitled) / with headers
text/plain 690b

> I had some code to do a backup, but it was sucky because it wasn't part
> of the filelist and Scot rightfully commented it out.

I commented out backups, but the old certificates don't get deleted. So
if the installation fails, people will still have some (old)
certificates to use. But this might be confusing to have multiple
directories of certificates at the top level.

Changing the filelist is not that hard. What about this:
- Install new certificates, say certificates-XX-X
- Move existing certificates from certificates-YY-Y to
certificates-YY-Y.old, and change the filelist accordingly
- Delete any previous certificates-*.old folders, and update the
filelist accordingly