#486 Document migration steps for dogtag 9 -> dogtag 10 instances
Closed: Fixed None Opened 11 years ago by vakwetu.

It would be nice to have some kind of automated tools to do this - but maybe thats more work than we need to do right now.

We should at least try out and document a migration. I think it will look something like this:

  1. set up a new instance
  2. switch out the security databases and update CS.cfg and maybe serverCertNick.conf
  3. switch out the databases

Of course, the devil is in the details.


Will work on automated tools. This is task 294.

We've gone to deciding to document this. We need this asap as we have put in code to ensure that no updates to f19 occur without a migration.

Metadata Update from @vakwetu:
- Issue assigned to jmagne
- Issue set to the milestone: 10.0.3

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1057

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata