
On offline upgrades, due to the rolling upgrade mechanism we need to restart the cinder services twice to complete the upgrade, just like in the rolling upgrade case. The current offline upgrade process is: - Stop cinder services - Upgrade the cinder nodes - Sync your DB - Start the cinder services - Restart all the cinder services This second restart creates a bad user experience and it should not be necessary on an offline upgrade, so this patch adds a new optional parameter -called "--bump-versions"- to the cinder-manage db sync command that allows us to skip the restart of the services. Closes-Bug: #1756321 Change-Id: I1b58c637f6b2187a78c9c00a6c4933335439ad6f
Team and repository tags
CINDER
You have come across a storage service for an open cloud computing service. It has identified itself as Cinder. It was abstracted from the Nova project.
- Wiki: https://wiki.openstack.org/Cinder
- Developer docs: https://docs.openstack.org/cinder/latest/
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
For developer information please see HACKING.rst
You can raise bugs here https://bugs.launchpad.net/cinder
Python client
https://git.openstack.org/cgit/openstack/python-cinderclient
Description
Languages
Python
99.7%
Smarty
0.3%