Gorka Eguileor 3cd2ebd375 Avoid second restart on offline upgrades
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
2018-04-02 15:13:06 +02:00
2017-10-13 08:37:57 +00:00
2012-05-03 10:48:26 -07:00
2017-10-10 00:46:42 +00:00
2018-03-09 11:15:51 -05:00
2012-05-03 10:48:26 -07:00
2017-04-08 15:03:44 +08:00
2017-09-07 11:55:44 +08:00
2012-05-03 10:48:26 -07:00
2015-06-11 17:19:19 +02:00
2018-03-11 00:09:35 +08:00
2018-02-05 13:04:04 -06:00
2017-03-02 23:53:29 +00:00

Team and repository tags

image

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.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://git.openstack.org/openstack/cinder.git

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
OpenStack Block Storage (Cinder)
Readme 913 MiB
Languages
Python 99.7%
Smarty 0.3%