373b524041
Cinder Backup has always been run as a single process, and this works fine if the number of backups is small, but there are deployments where a big number of backups are run simultaneously, and in such cases we will find a bottleneck on CPU intensive operations, like compression and SHA calculations, since we are using a single process and therefore a single CPU core. This patch adds support to define the number of processes we want to run on the backup service using a new "backup_processes" configuration option. When running multiple processes they will all be running as children of a parent process, but when running a single process it will run on its own. To preven race conditions and avoid the backup service from becoming available before it should only the first process will do the initial cleanup and all the others will wait on a lock until it is released by this first process. Change-Id: Ib43095024754a6219eb51cc0663913fac10bb642
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