---
upgrade:
  - 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
    upgrading from Newton to Ocata operator needs to perform all the Newton
    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
    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
    manner, you can use `--ignore-state` option safely. Please note that
    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
    that.

---
upgrade:
  - 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
    upgrading from Ocata to Pike, operator needs to perform all the Newton
    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
    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
    manner, you can use `--ignore_state` option safely. Please note that
    finishing all the Newton data migrations will be enforced by the first
    schema migration in Pike, so you won't be able to upgrade to Pike without
    that.

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

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
