ff6b9998bb
We have code going into Ocata that needs to be sure that cell and host mappings are in place. Since this was required homework in Newton, we can land a migration to intentionally fail if this was not completed. This is, however, a little difficult to require because a first-time deployment will be initialized schema-wise with none of these records, which is also sane. So, we look to see if any flavors are defined as a sentinel to indicate that this is an upgrade of an existing deployment instead of a first-time event. Not perfect, but since this is really just a helper for the user, it seems like a reasonable risk. Depends-On: If1af9c478e8ea2420f2523a9bb8b70fafddc86b7 Change-Id: I72fb724dc13e1a5f4e97c58915b538ba761c582d
8 lines
282 B
YAML
8 lines
282 B
YAML
---
|
|
upgrade:
|
|
- Ocata requires that your deployment have created the
|
|
cell and host mappings in Newton. If you have not done
|
|
this, Ocata's `db sync` command will fail. Small deployments
|
|
will want to run `nova-manage db simple_cell_setup`
|
|
on Newton before upgrading.
|