Bug 989729
Summary: | [Doc] Upgrades from RHOS 3.0 Quantum to RHOS 4.0 Neutron (configuration, database migrations) | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Stephen Gordon <sgordon> |
Component: | doc-Release_Notes | Assignee: | Summer Long <slong> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.0 | CC: | breeler, hateya, slong, yeylon |
Target Milestone: | --- | Keywords: | Documentation |
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-01-06 03:55:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 958568, 1011085 |
Description
Stephen Gordon
2013-07-29 19:32:21 UTC
DO NOT PUT IN FOR BETA RELEASE NOTES, ONLY FOR GA. *** Bug 989732 has been marked as a duplicate of this bug. *** Moving back to RC, per request from Program Mtg. Per Jeff Dexter: Going off release notes from Grizzly 3.0 I was able to use this path stop all services for i in /etc/init.d/quantum-* ; do $i stop ; done for i in /etc/init.d/openstack-* ; do $i stop ; done Add channel for Rhos 4 remove channel for Rhos 3 yum upgrade Sync databases keystone-manage db_sync cinder-manage db sync glance-manage db_sync nova-manage db sync neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugin.ini current neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugin.ini stamp grizzly neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugin.ini upgrade head start services This worked besides for Horizon failing to start which is documented in BZ 1040688 ----- After going through the upgrade process on a non-allinone test system, it took 40 minutes to do the keystone-manage db_sync. Should we note that a customers delete expired tokens before starting the database syncs? Draft finished and in git. Sanity check and need to do bug-list generation before publishing. Deepti has approved sanity check. Waiting for build before moving to QE. |