Database Migration Strategy
Change-Id: Ibc2f1691d7002ab5bd6eb20ed51ec63a6f424155
This commit is contained in:
parent
f543c5ef2e
commit
109fb6f4c0
37
doc/source/devref/database_migration.rst
Normal file
37
doc/source/devref/database_migration.rst
Normal file
@ -0,0 +1,37 @@
|
||||
===========================
|
||||
Database Migration Strategy
|
||||
===========================
|
||||
|
||||
*******************************
|
||||
What happens on a model change?
|
||||
*******************************
|
||||
|
||||
If a model is changed and this change is committed to the repo, a Jenkins
|
||||
job will vote against the change until also a migration file for this change is
|
||||
uploaded.
|
||||
|
||||
Similar to Neutron migration strategy a script for auto generation is used:
|
||||
`Neutron Script Auto-generation <http://docs.openstack.org/developer/neutron/devref/alembic_migrations.html#script-auto-generation>`_
|
||||
The big difference is that Proton will have a YAML model. So a new
|
||||
auto generate script is needed.
|
||||
|
||||
*****************
|
||||
Migration Process
|
||||
*****************
|
||||
The migrations in the alembic/versions contain the changes needed to migrate
|
||||
from older Neutron releases to newer versions. A migration occurs by executing
|
||||
a script that details the changes needed to upgrade the database. The
|
||||
migration scripts are ordered so that multiple scripts can run sequentially
|
||||
to update the database.
|
||||
|
||||
The migration process is done in the exact same way as the Neutron
|
||||
database migration.
|
||||
See details in the devref:
|
||||
`Neutron Database Migration <http://docs.openstack.org/developer/neutron/devref/alembic_migrations.html>`_
|
||||
|
||||
*******
|
||||
Testing
|
||||
*******
|
||||
|
||||
Unit test need to be written to verify the changed model. This unit test will be
|
||||
triggered by a Jenkins job and vote on the commit which changes the model.
|
Loading…
Reference in New Issue
Block a user