OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|4 months ago|
|deploy||2 years ago|
|deployment/puppet/octane_tasks||2 years ago|
|docs/records||2 years ago|
|misc||4 years ago|
|octane||2 years ago|
|specs||2 years ago|
|.coveragerc||3 years ago|
|.gitignore||2 years ago|
|.gitreview||4 months ago|
|.mailmap||4 years ago|
|Gemfile||3 years ago|
|Gemfile.lock||3 years ago|
|HACKING.rst||4 years ago|
|LICENSE||4 years ago|
|MAINTAINERS||2 years ago|
|MANIFEST.in||3 years ago|
|README.rst||2 years ago|
|Rakefile||3 years ago|
|bindep.txt||3 years ago|
|requirements.txt||3 years ago|
|setup.cfg||2 years ago|
|setup.py||3 years ago|
|test-requirements.txt||3 years ago|
|tox.ini||2 years ago|
Octane - upgrade your Fuel.
Tool set to backup, restore and upgrade Fuel installer and OpenStack environments that it manages. This version of the toolset supports upgrade from versions 7.0 and 8.0 to version 9.1.
Fuel Octane is installed on the Fuel Master node. Version of
fuel-octane package must match the version of Fuel.
To download the latest version of
fuel-octane package on the Fuel Master node, use the following command:
yum instal fuel-octane
Use this command to backup configuration of the Fuel Master node, environments and target nodes:
octane fuel-backup --to=/path/to/backup.file.tar.gz
Use this command to backup packages and images for all supported OpenStack release bundles from the Fuel Master node:
octane fuel-repo-backup --full --to=/path/to/repo-backup.file.tar.gz
Use this command to restore configuration of the Fuel Master node, environments and target nodes:
octane fuel-restore --from=/path/to/backup.file.tar.gz --admin-password=<passwod>
<password> with appropriate password for user
admin in your installation of Fuel.
Use this command to restore package repositories and images for OpenStack release bundbles from backup file:
octane fuel-repo-restore --from=/path/to/repo-backup.file.tar.gz
Upgrade of Fuel Master node requires making both backups of configuration and repos and images from older Fuel, as described above. Copy those files to a secure location. After you create two backup files, install a new (9.1) version of Fuel on the same physical node or on a new one.
Please, note that you must specify the same IP address for the new installation of the Fuel Master node as for the old one. Otherwise, target nodes won't be able to communicate with the new Fuel Master node.
Copy backup files to a new node from the secure location. Use
octane to restore Fuel configuration and packages from backup files. Database schema will be upgraded according to migration scripts. See detailed commands above.
The Fuel Master node of new version must now have all configuration data from an old version of the Fuel Master node.
Pick environment of version <9.0 that you want to upgrade. Run tha following command and remember an ID of the environment you picked:
Run command to create Upgrade Seed environment:
octane upgrade-env $SEED_ID
Remember ID of environment that will be shown:
Pick controller with minimal ID:
Run the following command to upgrade it:
octane upgrade-node --isolated $SEED_ID $NODE_ID
Run the following command to upgrade state database of OpenStack environment to be upgraded:
octane upgrade-db $ORID_ID $SEED_ID
Run the command to upgrade Ceph cluster:
octane upgrade-ceph $ORIG_ID $SEED_ID
The following command redirects all nodes in OpenStack cluster to talk to the new OpenStack Controller with upgraded version:
octane upgrade-control $ORIG_ID $SEED_ID
Run the following command to upgrade remaining controllers to version 9.1:
octane upgrade-node $SEED_ID $NODE_ID_2 $NODE_ID_3
Pick a compute node(s) to upgrade and remember their IDs.
export NODE_ID_1=<ID1> ...
Run the command to upgrade the compute node(s) without evacuating virtual machines:
octane upgrade-node --no-live-migration $SEED_ID $NODE_ID_1 ...
Run the command to upgrade the compute node(s) with evacuating virtual machines to other compute nodes in the environment via live migration:
octane upgrade-node $SEED_ID $NODE_ID_1 ...