Introduce db sync --check feature
Lite-spec for a dry-run option for db upgrades in glance-manage. Change-Id: Ie1e2fec2361765ddf23da897abcf0e12e682612e
This commit is contained in:
parent
0522238825
commit
9dcdb915c0
@ -103,5 +103,35 @@ Remove Glare code from the Glance repository
|
||||
End of `Remove Glare code from the Glance repository`
|
||||
+++++++++++++++++++++++++++++++++++++++++++++++++++++
|
||||
|
||||
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: Alexander Bashmakov
|
||||
|
||||
End of `Introduce db sync --check feature`
|
||||
++++++++++++++++++++++++++++++++++++++++++
|
||||
|
||||
Add your Spec Lite before this line
|
||||
===================================
|
||||
|
Loading…
x
Reference in New Issue
Block a user