Difference between revisions of "Fast forward upgrades"
(→Preconditions) |
James Penick (talk | contribs) (→What is a Fast Forward Upgrade?) |
||
| Line 2: | Line 2: | ||
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. | 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. | ||
== What is a Fast Forward Upgrade? == | == 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 == | == Preconditions == | ||
Revision as of 10:00, 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!)
