Michał Dulko fc0034b385 Rolling upgrade procedure documentation

One of the requirements to achieve assert:supports-rolling-upgrade TC
tag is to provide a "plan that allows operators to roll out new code to
subsets of services, eliminating the need to restart all services on new
code simultaneously".

This commit documents such rolling upgrade procedure in the devref,
which is last outstanding requirement for Cinder.

Change-Id: I562deafcd4bb9f5666cc35ae77a6bf20ab889612

2016-12-16 11:03:56 +01:00

2.3 KiB

Raw Blame History

Welcome to Cinder's developer documentation!

Cinder is an OpenStack project to provide "block storage as a service".

Component based architecture: Quickly add new behaviors
Highly available: Scale to very serious workloads
Fault-Tolerant: Isolated processes avoid cascading failures
Recoverable: Failures should be easy to diagnose, debug, and rectify
Open Standards: Be a reference implementation for a community-driven api

This documentation is generated by the Sphinx toolkit and lives in the source tree. Additional draft and project documentation on Cinder and other components of OpenStack can be found on the OpenStack wiki. Cloud administrators, refer to docs.openstack.org.

Developer Docs

devref/index database_architecture scheduler-filters scheduler-weights oslo-middleware upgrade

Drivers

Cinder maintains drivers for volume backends, backup targets, and fibre channel zone manager fabric types. The list of the available drivers can be found here:

drivers

API Extensions

Go to http://api.openstack.org for information about Cinder API extensions.

Sample Configuration File

sample_config

Indices and tables

genindex
modindex
search

2.3 KiB Raw Blame History