Red Hat Bugzilla – Bug 1405098
Ocata requires additional cellvs2 setup
Last modified: 2017-05-17 15:51:22 EDT
Nova will require cellsv2 setup before/during the upgrade to ocata. At this time, the following are known, but more steps are likely to materialize before the ocata release: https://github.com/openstack/nova/blob/master/releasenotes/notes/cell-id-db-sync-nova-manage-8504b54dd115a2e9.yaml https://github.com/openstack/nova/blob/master/releasenotes/notes/cells-single-migration-command-0e98d66e31e02a50.yaml https://github.com/openstack/nova/blob/master/releasenotes/notes/ocata-requires-cellv2-96bd243be874d77f.yaml
Scott you didn't ask a question?
To summarize the release notes: For an upgrade to Ocata of a non-cells deployment, the following steps are needed in Newton: 1. Create a new database for cell0 based on the current name of the api database: <API database name>_cell0. If the api database is named nova_api, then the cell0 database should be named nova_api_cell0. 2. Run the simple cell setup command: nova-manage cell_v2 simple_cell_setup --transport-url <transport url for message queue>. An upgrade of an existing cells v1 deployment requires different, more complex steps, so let us know if that info is needed. There's also an enhancement to the simple_cell_setup command in Ocata that can pick up [DEFAULT]/transport_url from the nova.conf (instead of only the command line), so I'm going to try to get that backported to Newton for use. I will update here if that happens.
*** Bug 1418907 has been marked as a duplicate of this bug. ***
Hello, could you please provide more info about this bug. Is it going to be a part of OSP 11 or not? It would help me to decide how I will handle the documentation for this issue. Thanks a lot.
(In reply to Lukas Ruzicka from comment #17) > Hello, could you please provide more info about this bug. Is it going to be > a part of OSP 11 or not? It would help me to decide how I will handle the > documentation for this issue. Thanks a lot. RHOSP 11 will deploy a so called "cell of one", a single cell deployment. This is because this is mandatory for Nova from Ocata and beyond. This is mostly plumbing from a user perspective, but should be reflected in any manual configuration or architecture documentation so that they are able to understand what is being deployed. Deployment and configuration of multi-cell environments is not addressed in this release.
There will be no manual configuration required. OSPD will deploy a single cell setup for a fresh install or upgrade RHOSP 10 to a single cell. Upstream docs describe the architecture quite well IMO: http://docs.openstack.org/developer/nova/cells.html#cells-v2
By manual configuration I was referring to the fact that in addition to the director-based installation documentation the docs folks maintain these guides which will likely need updates: Architecture Guide https://access.redhat.com/documentation/en/red-hat-openstack-platform/10/paged/architecture-guide/ Manual Installation Procedures https://access.redhat.com/documentation/en/red-hat-openstack-platform/10/paged/manual-installation-procedures/chapter-8-install-the-compute-service
Thanks, guys, for your quick reply. I highly appreciate that.
Ah, ok. The manual setup procedures will need to be updated for both cell_v2 setup and the placement api setup.
Can this be moved to POST or MODIFIED?
Greenfield install implemented in numerous upstream patches: https://review.openstack.org/#/q/topic:bug/1649341 10 -> 11 Upgrade implemented in https://review.openstack.org/405241
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1245