glance-specs/specs/untargeted/glance/lite-spec-db-sync-check.rst
Brian Rosmaita 092f61e9f4 Move non-prioritized Pike specs to 'untargeted'
Following discussion at the Glance virtual midcycle meeting, specs
that were approved for Pike but whose owners are no longer available
to work on them are to be moved to an 'untargeted' directory.

Change-Id: I6da5d9ec49e60609173456456bb8635ada6dbdd2
2017-05-31 20:50:44 -04:00

1.3 KiB

Lite Spec: Introduce db sync --check feature

problem

It is very hard for automation of deploy and upgrade operations to know if there are db migrations pending. It requires the automation to know what the latest version is, and compare that to the output of a command to check the current version, then interpret the potential difference somehow.

solution

Similar to the linked feature added to Keystone's manage command, Glance should support an operation which enumerates any outstanding db upgrade operations and provide a distinct return code based on that status. Each expand, migrate, and contract operation required to upgrade the db should be listed in the proper order of execution in the response. For consistency with Keystone, this may be implemented by using a --check option. When this option is present no db upgrades would be performed but potential operations would be reported, acting similar to the pattern of a dry-run.

impacts

Introduces new option to the db sync operation in glance-manage.

timeline

Expected to be merged within the Pike time frame.

link

https://bugs.launchpad.net/keystone/+bug/1642212

assignee

Open