Chapter 3. Upgrading
3.1. Upgrade Overview
Warning
Red Hat does not support:
Upgrading any Beta release of Red Hat Enterprise Linux OpenStack Platform to any
supported release (for example, 3 or 4).
Upgrading Compute Networking (nova-networking) to OpenStack Networking (neutron) in
Red Hat Enterprise Linux OpenStack Platform 4. The only supported networking upgrade is
between versions of OpenStack Networking (neutron) from Red Hat Enterprise Linux
OpenStack Platform version 3 to version 4 .
Users who installed Red Hat Enterprise Linux OpenStack Platform 3 (Grizzly) can use these
procedures to upgrade their systems to Red Hat Enterprise Linux OpenStack Platform 4 (Havana).
There are four methods to upgrade Red Hat Enterprise Linux OpenStack Platform. The following table
provides a brief description of each.
T ab le 3.1. Upg rad e Met h o ds
Met h o d Descrip t io n
Using a parallel
cloud
The easiest way to do an upgrade is to deploy a completely separate Red Hat
Enterprise Linux OpenStack Platform 4 (Havana) environment, and slowly
migrate resources over from the old Grizzly environment to the new one. This
might be excessive for a lot of users, but it is something that may be
considered as the least-intrusive alternative to the other options.
Because this method is based on a new installation, no upgrade instructions
are included. For installation procedures, refer to either the Installation and
Configuration Guide (foreman or manual procedures for larger environments) or
the Getting Started Guide (packstack procedures for an all-in-one installation).
All at Once In this method, you take down all of the OpenStack services at the same time,
do the upgrade, then bring all services back up after the upgrade process is
complete.
Pro s: This upgrade process is simple. Because everything is down, no
orchestration is required. Although services will be down, VM workloads
can be kept running if there are no requirements to move from one version
of Red Hat Enterprise Linux to another.
Co n s: All of your services will be unavailable at the same time. In a large
environment, the upgrade can result in a potentially extensive downtime
while you wait for database-schema upgrades to complete. Downtime can
be mitigated by proper dry-runs of your upgrade procedure on a test
environment as well as scheduling a specific downtime window for the
upgrade.
Section 3.2, “ Method - Upgrade All at Once”
(124 strony)
(90 strony)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji