openstack/glance-specs
Code Issues Proposed changes

Update spec template for db migrations

Browse Source 
Modify the "Data model impact" section of the spec template to
so that the impact of a change on zero-downtime database migrations
will be addressed.

Change-Id: I1ad5ad4ff333aef66ce80b442d8290982160c1c8
Depends-On: Ic8b21d2cc1e42f3e1478973df0f80792e5098f90
Partially-Implements: blueprint rolling-upgrades
This commit is contained in:
Brian Rosmaita 2017-03-21 09:48:12 -04:00
parent 3c6f8c5ddb
commit 49843c995d
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
specs/template.rst
View File

@ -91,7 +91,18 @@ Questions which need to be addressed by this section include:
* What new data objects and/or database schema changes is this going to * What new data objects and/or database schema changes is this going to
require? require?
* What database migrations will accompany this change? * Glance is committed to zero-downtime database migrations and has adopted an
`E-M-C migration strategy <https://docs.openstack.org/developer/glance/database_migrations.html>`_
to achieve this. Address the following in sufficient detail to make it clear
that the intended database change will be achieved.
- Will this change require database triggers? If yes, describe them.
- Explain what your expand migrations will look like.
- Explain what your data migrations will look like.
- Explain what your contract migrations will look like.
- Finally, do these changes have the potential to interfere with the
database migrations for other specs that have been approved for this
cycle?
* How will the initial set of new data objects be generated? For example if you * How will the initial set of new data objects be generated? For example if you
need to take into account existing images, or modify other existing data, need to take into account existing images, or modify other existing data,