TommyLike e1ec4b4c2e Support filter backend based on operation type
During Rocky PTG, we discussed the concept of
'sold out'. In order to fully utilize
current codes, we decided to achieve this via
scheduler filters, cloud vendors can write their own
scheduler filter plugin to disable new resource
creation actions on sold out pools. Therefore, the
only change on cinder framework side is to delivery
'operation' when asking scheduler to filter hosts.

For this first stage, the initial operations are:
1. create_group
2. manage_existing
3. extend_volume
4. create_volume
5. create_snapshot
6. migrate_volume
7. retype_volume
8. manage_existing_snapshot

Partial-Implements: bp support-mark-pool-sold-out
Change-Id: I4f0a14444675ebd0fe6397a5ff2ef9dca62b4453
2018-05-07 17:58:36 +08: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
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 908 MiB
Languages
Python 99.7%
Smarty 0.3%