openstack/cinder
Code Issues Proposed changes

Merge "Fix names in online-data-migrations release note"

Browse Source
This commit is contained in:
Jenkins 2016-11-24 11:19:16 +00:00 committed by Gerrit Code Review
commit 7f1fb7c00b
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
releasenotes/notes/cinder-manage-db-online-schema-migrations-d1c0d40f26d0f033.yaml
View File

@ -2,12 +2,12 @@
upgrade: upgrade:
- To get rid of long running DB data migrations that must be run offline, - To get rid of long running DB data migrations that must be run offline,
Cinder will now be able to execute them online, on a live cloud. Before Cinder will now be able to execute them online, on a live cloud. Before
upgrading from Newton to Ocata operator needs to perform all the Newton upgrading from Ocata to Pike, operator needs to perform all the Newton
data migrations. To achieve that he needs to perform `cinder-manage db data migrations. To achieve that he needs to perform `cinder-manage db
online-data-migrations` until there are no records to be updated. To limit online-data-migrations` until there are no records to be updated. To limit
DB performance impact migrations can be performed in chunks limited by DB performance impact migrations can be performed in chunks limited by
`--max_number` option. If your intent is to upgrade Cinder in a non-live `--max_number` option. If your intent is to upgrade Cinder in a non-live
manner, you can use `--ignore-state` option safely. Please note that manner, you can use `--ignore_state` option safely. Please note that
finishing all the Newton data migrations will be enforced by the first finishing all the Newton data migrations will be enforced by the first
schema migration in Ocata, so you won't be able to upgrade to Ocata without schema migration in Pike, so you won't be able to upgrade to Pike without
that. that.