History

Steve Baker bb4c915434 Do not specify version for contrib plugins The pbr 0.11.0 release has shown that having multiple trees in a repo each with their on version that is different to the git history is really not going to work. This change means that the version will be derived from git history, which will still be useful for operators managing what version of a plugin they have installed. Running sudo python setup.py install (as documented) is known to work with the latest pbr. Change-Id: I716a5374bb283d11e26459b5866a0437ab6fe0dd Closes-Bug: #1450733		2015-05-04 10:33:23 +12:00
..
cinder_volume_type	Show deprecated warnings when import parser	2015-04-14 17:49:15 +08:00
README.md	Add OS::Cinder::VolumeType resource	2014-12-01 03:49:54 +00:00
setup.cfg	Do not specify version for contrib plugins	2015-05-04 10:33:23 +12:00
setup.py	Add OS::Cinder::VolumeType resource	2014-12-01 03:49:54 +00:00

README.md

Cinder volume_type plugin for OpenStack Heat

This plugin enables using Cinder volume_types as resources in a Heat template.

1. Install the Cinder volume_type plugin in Heat

NOTE: These instructions assume the value of heat.conf plugin_dirs includes the default directory /usr/lib/heat.

To install the plugin, from this directory run: sudo python ./setup.py install

2. Restart heat

Only the process "heat-engine" needs to be restarted to load the new installed plugin.

Template Format

Here's an example cinder volume_type and cinder volume resources:

heat_template_version: 2013-05-23
description:  Heat Cinder creation with volume_type example
resources:
  my_volume_type:
    type: OS::Cinder::VolumeType
    properties:
      name: volumeBackend
      metadata: {volume_backend_name: lvmdriver}
  my_volume:
    type: OS::Cinder::Volume
    properties:
      size: 1
      volume_type: {get_resource: my_volume_type}

Issues with the Cinder volume_type plugin

By default only users who have the admin role can manage volume types because of the default policy in Cinder: "volume_extension:types_manage": "rule:admin_api"

To let the possibility to all users to create volume type, the rule must be replaced with the following: "volume_extension:types_manage": ""

The following error occurs if the policy has not been correctly set: ERROR: Policy doesn't allow volume_extension:types_manage to be performed.