Document migration path from grizzly to havana

Bug #1199773 reported by Lorin Hochstein
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
High
Matt Kassawara

Bug Description

We need to document the process of migrating/upgrading a grizzly deployment to havana.

Setting importance to "High" since this is pretty important for release.

Lorin Hochstein (lorinh)
Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → High
description: updated
Changed in openstack-manuals:
milestone: none → havana
Revision history for this message
Stephen Gordon (sgordon) wrote :

- Quantum -> Neutron?
- Nova API upgrade?

Revision history for this message
Stephen Gordon (sgordon) wrote :

I think in general what we need is a "generic" upgrade process template that we would then bolt release specific steps into. Effectively

- Stop services.
- Upgrade code.
- Upgrade databases.
- Release specific steps?
- Start services.

Here is an example of what I did for Grizzly, but I'm not sure I would consider it exhaustive:

https://access.redhat.com/site/documentation/en-US/Red_Hat_OpenStack/3/html-single/Release_Notes/index.html#chap-OpenStackNotes-Upgrading

This kind of procedure is also only really suited to relatively small deployments. Users are likely interested in how to perform a staggered upgrade of a larger/more realistic deployment.

Revision history for this message
Jon Proulx (jproulx) wrote :

seems to me https://wiki.openstack.org/wiki/ReleaseNotes/Havana#General_Upgrade_Notes is a good place for something like Stephen's "generic upgrade process"

as a cloud admin/operator that's where I'd look and the release/project specific upgrade notes should be in line in the same document.

I think the amount of variation between sites precludes and exhaustive step by step procedural description.

Revision history for this message
Tom Fifield (fifieldt) wrote :

yay for Jon back on docs!

We also have to remember: http://docs.openstack.org/trunk/openstack-ops/content/maintenance.html#upgrades :)

Revision history for this message
Summer Long (slong-g) wrote :

And I have an RH Havana process. Tom, where was the upgrade put in for Grizzly? Only in the Ops Guide? Perhaps in the Install Guide?

Changed in openstack-manuals:
assignee: nobody → Summer Long (slong-g)
Revision history for this message
Anne Gentle (annegentle) wrote :

Only in the Ops Guide. It hasn't ever been in an Install Guide. It has been in the old Compute Admin Manual.

Revision history for this message
Anne Gentle (annegentle) wrote :

Also, upgrade notes are supposed to be put in release notes in the wiki. I can dig up examples if needed.

Revision history for this message
Summer Long (slong-g) wrote :

After talk with Anne, will put in wiki, as well as updating the generic process in Ops guide if need be.

Revision history for this message
Tom Fifield (fifieldt) wrote :

Another tidbit:

Following the migration, we found that nova image-list and glance image-list were showing different results.

The root cause was related to the bug https://bugs.launchpad.net/glance/+bug/1152716. The fix for the problem was to add the policy statement for the parameter context_is_admin which is needed to limit access to private images for projects.

Revision history for this message
Anne Gentle (annegentle) wrote :
Revision history for this message
Matt Kassawara (ionosphere80) wrote :

Can we set this to "in progress" status?

Summer Long (slong-g)
Changed in openstack-manuals:
status: Confirmed → In Progress
Revision history for this message
Summer Long (slong-g) wrote :

Can't figure out a way to assing Matt...https://launchpad.net/~ionosphere80. Have taken myself off at least.

Changed in openstack-manuals:
assignee: Summer Long (slong-g) → nobody
Changed in openstack-manuals:
assignee: nobody → Matt Kassawara (ionosphere80)
Changed in openstack-manuals:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.