Puppet/bp-cinder-volume-multi-backend
< Puppet
Contents
Overview
We should be able to support Cinder-multi-backend
This moving this way would allow us to support multiple concurent backends.
user story
Use a single cinder-volume backend
class { 'cinder::volume': } class { 'cinder::volume::iscsi': iscsi_ip_address => '10.0.0.2', }
Use two or more cinder-volume backends and assign them to different types
...
Use three or more cinder-volume backends and assign them two to one type and the other to another
...
Requirements
- must configure as many supported backends as possible
- must be comptible with only defining one single backend
- must configure cinder type example
- if types are default, must allow for a default type (so scheduler can consider multiple seperate providers equally)