104c9e6375
Everyone seems to agree that the only sane ordering of these operations is "api first, cell after." However, grenade and our own documentation shows the api database as coming after the main one. I believe this was added to grenade in a sort of append operation, and thus after the main database. This was done back when usage of the API database was still optional (for upgrades) and thus the ordering didn't matter much. Since the process has been correct (api first) in devstack for a long time, and since grenade runs after devstack, we haven't had any issues. A recent change to add something to a core data structure column format highlighted the out-of-order-ness of this. I also believe the docs got the same append behavior when adding the command to the list, and/or it may have been copied from grenade, which is our in-code manifestation of the upgrade steps. Change-Id: I19f263ed314a8b01bbb07337467392cc1c146b66 Related-Bug: #1761775 |
||
|---|---|---|
| .. | ||
| _extra | ||
| _static | ||
| admin | ||
| cli | ||
| configuration | ||
| contributor | ||
| figures | ||
| install | ||
| reference | ||
| user | ||
| conf.py | ||
| index.rst | ||