openstack/nova
Code Issues Proposed changes

doc: code review considerations for online data migrations

Browse Source 
Online data migrations that move something from the cell database
to the API database typically create new things in the API DB and
on a query, look in the API DB first and then fallback to the cell
database. We started supporting multiple cells in Pike, so any online
data migrations that move things to the API DB after that will need
to be multi-cell aware for the fallback lookup code.

This just adds a reminder in the code review guide.

Change-Id: If0d7d9b80e336b696aaf87ec13ac18daa1068357
This commit is contained in:
Matt Riedemann
2017-08-08 14:58:14 -04:00
parent 6787d62bf6
commit 8ab41c83a8
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
doc/source/contributor/code-review.rst
View File

@@ -86,6 +86,9 @@ Database Schema
online. Generally, this can and should be hidden within the object
layer so that an object can load from either the old or new
location, and save to the new one.
* Multiple Cells v2 cells are supported started in the Pike release.
As such, any online data migrations that move data from a cell
database to the API database must be multi-cell aware.
REST API
=========