openstack
/
glance-specs
Code Issues Proposed changes

Introduce db sync check feature 

Lite-spec for a dry-run option for db upgrades in glance-manage.

This spec is moved from /specs/untargeted/glance/lite-spec-db-sync-check.rst
to /specs/queens/implemented/glance/lite-spec-db-sync-check.rst because it was
implemented by change I1e0b02d615690f65a17b4ccfe4e4a72cc9e15ada

Change-Id: Ice1ab9657e236d969df50016a3b47a893e6aff0c
This commit is contained in:
bhagyashris 2018-03-06 13:03:02 +05:30
parent 449947b209
commit f8736b39af
3 changed files with 32 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/source/_extra/.htaccess
View File

@ -9,3 +9,4 @@ Redirect 301 /specs/queens/approved/glance/remove-registry-v1.html /specs/rocky/
Redirect 301 /specs/queens/approved/glance/remove-v1.html /specs/rocky/approved/glance/remove-v1.html Redirect 301 /specs/queens/approved/glance/remove-v1.html /specs/rocky/approved/glance/remove-v1.html
Redirect 301 /specs/mitaka/approved/image-import/image-import-refactor.html /specs/rocky/approved/glance/image-import/image-import-refactor.html Redirect 301 /specs/mitaka/approved/image-import/image-import-refactor.html /specs/rocky/approved/glance/image-import/image-import-refactor.html
Redirect 301 /specs/queens/approved/python-glanceclient/no-schema-validation.html /specs/untargeted/python-glanceclient/no-schema-validation.html Redirect 301 /specs/queens/approved/python-glanceclient/no-schema-validation.html /specs/untargeted/python-glanceclient/no-schema-validation.html
Redirect 301 /specs/untargeted/glance/lite-spec-db-sync-check.html /specs/queens/implemented/glance/lite-spec-db-sync-check.html

1
doc/test/redirect-tests.txt
View File

@ -10,3 +10,4 @@
/specs/queens/approved/glance/remove-v1.html 301 /specs/rocky/approved/glance/remove-v1.html /specs/queens/approved/glance/remove-v1.html 301 /specs/rocky/approved/glance/remove-v1.html
/specs/mitaka/approved/image-import/image-import-refactor.html 301 /specs/rocky/approved/glance/image-import/image-import-refactor.html /specs/mitaka/approved/image-import/image-import-refactor.html 301 /specs/rocky/approved/glance/image-import/image-import-refactor.html
/specs/queens/approved/python-glanceclient/no-schema-validation.html 301 /specs/untargeted/python-glanceclient/no-schema-validation.html /specs/queens/approved/python-glanceclient/no-schema-validation.html 301 /specs/untargeted/python-glanceclient/no-schema-validation.html
/specs/untargeted/glance/lite-spec-db-sync-check.html 301 /specs/queens/implemented/glance/lite-spec-db-sync-check.html

56
specs/untargeted/glance/lite-spec-db-sync-check.rst → specs/queens/implemented/glance/lite-spec-db-sync-check.rst
View File

@ -1,26 +1,30 @@
Lite Spec: Introduce db sync --check feature ==========================================
-------------------------------------------- Spec Lite: 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 :problem: It is very hard for automation of deploy and upgrade operations to
to know what the latest version is, and compare that to the output know if there are db migrations pending. It requires the automation
of a command to check the current version, then interpret the to know what the latest version is, and compare that to the output
potential difference somehow. 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 :solution: Similar to the linked feature added to Keystone's manage command,
db upgrade operations and provide a distinct return code based on Glance should support an operation which enumerates any outstanding
that status. Each expand, migrate, and contract operation required db upgrade operations and provide user friendly message based on
to upgrade the db should be listed in the proper order of execution that status. Each expand, migrate, and contract operation required
in the response. For consistency with Keystone, this may be to upgrade the db should be listed in the proper order of execution
implemented by using a ``--check`` option. When this option is in the response.
present no db upgrades would be performed but potential operations This may be implemented by using a ``glance-manage db check`` option.
would be reported, acting similar to the pattern of a dry-run. When this option is present no db upgrades would be performed
but potential operations would be reported, acting similar to the
:impacts: Introduces new option to the db sync operation in glance-manage. pattern of a dry-run.
:timeline: Expected to be merged within the Pike time frame. :impacts: Introduces new option to the db sync operation in glance-manage.
:link: https://bugs.launchpad.net/keystone/+bug/1642212 :timeline: Queens RC-1
:assignee: Open :link: https://bugs.launchpad.net/keystone/+bug/1642212
:reviewers: rosmaita, abhishekk, jokke
:assignee: bhagyashris