#710 Database upgrade framework
Closed: migrated 3 years ago by dmoluguw. Opened 10 years ago by edewata.

Similar to the system and server configuration upgrade framework, a database upgrade framework is needed to automatically update an existing database to work with the new code. It should maintain an upgrade tracker in the database itself. The database upgrade may need to be run separately from RPM upgrade since the database may be shared with multiple servers.


For upgrading a standalone server or a master server the procedure will be like this:

$ yum upgrade dogtag-pki
$ pki-database-upgrade -h <localhost> -D "cn=Directory Manager" -w <password>\
    -s <subsystem> -b <base DN>
$ serverctl restart pki-tomcatd@pki-tomcat.service

For replica installation which is using an older master:

$ yum install dogtag-pki
$ pki-database-upgrade -h <master> -D "cn=Directory Manager" -w <password>\
    -s <subsystem> -b <base DN>
$ pkispawn

This will require:

  • adding an LDAP attribute to store the database version
  • writing upgrade framework classes
  • writing a CLI to execute the upgrade
  • writing a man page

Moved to 10.3.1 per discussion with alee and nkinder.

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: 10.4

7 years ago

Per CS/DS meeting of 04/24/2017: 10.5

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue set to the milestone: 10.5 (was: 10.4)

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

6 years ago

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

6 years ago

Metadata Update from @edewata:
- Issue set to the milestone: FUTURE (was: 10.6)

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: FUTURE)

5 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/1279

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.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata