The online data migrations command in the release notes
needs to be corrected.
$ cinder-manage db online-data-migrations
usage: cinder-manage db [-h]
{online_data_migrations,purge,sync,version} ...
cinder-manage db: error: argument action: invalid choice:
'online-data-migrations' (choose from 'online_data_migrations',
'purge', 'sync', 'version')
"cinder-manage db online_data_migrations" is the right command.
Change-Id: I38d36f0721a6d0889639010e91ab041f935d0a00
Release note explaining ``cinder-manage db online-schema-migrations``
was created back in Newton, and was referring to wrong release names.
This commit fixes that by changing "Newton" to "Ocata" and "Ocata" to
"Pike".
Change-Id: Ia52fe964ad37fab0271bda3057cc16fdd4848ae1
To limit downtime during upgrade we've decided to ban data migrations
done in migrations scripts and do them online during the runtime of the
cloud. This commit implements generic infrastructure for that.
This was part of a commit adding a mapping table between volume types
and consistency groups, but I've separated it because it's needed
independently. Also the aforementioned commit will probably be obsolete
when we finish generic volume groups efforts.
UpgradeImpact
Related: blueprint online-schema-upgrades
Change-Id: I655d47c39e44251cbbad6e4b3fbc8e8d73995d30