rcbops / chef-cookbooks

RCB OPS - Chef Cookbooks
Other
118 stars 102 forks source link

[cinde] Cinder cookbook should support multiple backends #924

Open breu opened 10 years ago

breu commented 10 years ago

We should be able to set multiple cinder storage backends and name them so we can add them as a filter for volume-types:

cinder type-create SATA
cinder type-key SATA set volume_backend_name=cinder-sata
cinder type-create SSD
cinder type-key SSD set volume_backend_name=cinder-ssd

# create a 1GB SATA volume
cinder create --display-name test-sata --volume-type SATA 1

# create a 1GB SSD volume
cinder create --display-name test-sata --volume-type SSD 1

At a minimum this resolves the problem for cinder and LVM: https://gist.github.com/rackerjoe/9920058. With this gist you can set a default in the node attribute to define the backend name like:

54321-cinder01.domain.com
    "cinder": {
      "storage": {
        "lvm": {
          "volume_backend_name": "cinder-sata"
        }
      }
    }

12345-cinder02.domain.com
   "cinder": {
      "storage": {
        "lvm": {
          "volume_backend_name": "cinder-ssd"
        }
      }
    }

The default attributes for cinder storage needs to really support multiple backends and enable the backends per node. something like:

enabled_backends=backend1,backend2
[backend1]
...some values...

[backend2]
...some values....

[backend3]
...some backend that isn't enabled...

This allows us to mix and match the cinder storage backends on one or more cinder-volume node and doesn't tie us to a single backend per storage node as we do today.

odyssey4me commented 10 years ago

:+1: https://github.com/rcbops/chef-cookbooks/issues/537