Difference between revisions of "Fast forward upgrades"
James Penick (talk | contribs) (→What is a Fast Forward Upgrade?) |
Rybridges16 (talk | contribs) (→Preconditions) |
||
| Line 8: | Line 8: | ||
* VMs should be accessible by customer | * VMs should be accessible by customer | ||
* Since control plane is down, operator can't do actions on existing instances (duh!) | * Since control plane is down, operator can't do actions on existing instances (duh!) | ||
| + | * Take a full backup of your database before running the migration scripts just in case things get weird | ||
== Upgrade scripts == | == Upgrade scripts == | ||
Revision as of 10:05, 26 February 2018
Fast Forward Upgrade steps This document will serve to record a suggested path (and gotchas) when performing a fast-forward upgrade (ffu), as well as link to relevant projects (triple-o, ansible, etc) documentation for ffu.
Contents
What is a Fast Forward Upgrade?
A fast-forward upgrade is an offline upgrade which effectively runs the upgrade processes for all versions of openstack components from your originating version to your desired final version.
Preconditions
- Control plane will be down for the entire time of upgrade
- VMs should be accessible by customer
- Since control plane is down, operator can't do actions on existing instances (duh!)
- Take a full backup of your database before running the migration scripts just in case things get weird
