Add a post migration step to support rolling upgrades
In order to support rolling upgrades (i.e. upgrading a multi-node keystone one node at a time while still running the service), some migration scripts cannot leave the database in the state they would ideally like. By adding a keystone-manage "migration complete" command, we allow this to be resolved once all nodes have been migrated. This is in line with the general approach for rolling upgrades being supported cross project.
Blueprint information
- Status:
- Complete
- Approver:
- Steve Martinelli
- Priority:
- High
- Drafter:
- Henry Nash
- Direction:
- Approved
- Assignee:
- Henry Nash
- Definition:
- New
- Series goal:
- Accepted for newton
- Implementation:
-
Implemented
- Milestone target:
-
newton-3
- Started by
- Steve Martinelli
- Completed by
- Steve Martinelli
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add migration-complete step to keystone-manage
Addressed by: https:/
Add the migration phase status table
Addressed by: https:/
WIP Add support for rolling upgrades to keystone-manage
Addressed by: https:/
WIP - Add contract migrations to keystone-manage
Addressed by: https:/
Add basic upgrade documentation
Addressed by: https:/
Add rolling upgrade documentation
Gerrit topic: https:/
Addressed by: https:/
Introduce read-only mode for the database
Addressed by: https:/
Add migration helper logic for rolling upgrades
Gerrit topic: https:/
Addressed by: https:/
Make KeyRepository shareable
Addressed by: https:/
Add conf to support credential encryption
Addressed by: https:/
Add key_hash and encrypted_blob to credential table
Addressed by: https:/
Add create and update methods to credential Manager
Addressed by: https:/
Create a fernet credential provider
Addressed by: https:/
Document the fernet credential provider
Addressed by: https:/
Add key repository uniqueness check to doctor
