Comment 2 for bug 1199773

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.