diff options
| author | Grzegorz Grasza <grzegorz.grasza@intel.com> | 2016-12-08 11:34:27 +0100 |
|---|---|---|
| committer | Ruby Loo <ruby.loo@intel.com> | 2017-08-02 13:33:37 -0400 |
| commit | 54efd312395a56cbeee5c556df34afd8153c8076 (patch) | |
| tree | 2ebd89bb197e3448ea8a1c4ddfb8ce8bb0c191f8 /babel.cfg | |
| parent | f15934eb8d12391807809d198997102108074eb2 (diff) | |
| download | ironic-54efd312395a56cbeee5c556df34afd8153c8076.tar.gz | |
Add new dbsync command with first online data migration
This adds the new command 'ironic-dbsync online_data_migrations'.
To limit downtime during upgrades, data migrations will be done online
with migration scripts that could be run during normal operation of an
ironic cluster, after the upgrade but before the next one.
Each migration script should ensure that all related DB records are
migrated to the new format. Scripts can detect the format based on
the object version which is stored in the version column.
The online data migration has one script; a function that backfills
the new version column, using versions of objects from the release
prior to this.
This includes code to check the object versions for compatibility with
an ironic release. However, the check is turned off (and will be turned on
in Queens), since we need to boot-strap the new version column before
we can turn the check on. To do this check, we need to keep a list of all
supported versions for every object; release_mapping.RELEASE_MAPPING was
modified so that the object versions is now a list instead of one value.
Change-Id: I1a9fa829951ecf98cae6896d82ba20cf89062394
Closes-Bug: #1585141
Partial-bug: #1526283
Co-Authored-By: Ruby Loo <ruby.loo@intel.com>
Diffstat (limited to 'babel.cfg')
0 files changed, 0 insertions, 0 deletions