Browse Source

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
bhagyashris 1 year ago
parent
commit
f8736b39af

+ 1
- 0
doc/source/_extra/.htaccess View File

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

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

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

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

Loading…
Cancel
Save