1
Nova Flavor plugin for OpenStack Heat
2
=====================================
4
This plugin enables using Nova Flavors as resources in a Heat template.
6
Note that the current implementation of the Nova Flavor resource does not
7
allow specifying the name and flavorid properties for the resource.
8
This is done to avoid potential naming collision upon flavor creation as
9
all flavor have a global scope.
11
### 1. Install the Nova Flavor plugin in Heat
13
NOTE: Heat scans several directories to find plugins. The list of directories
14
is specified in the configuration file "heat.conf" with the "plugin_dirs"
19
Only the process "heat-engine" needs to be restarted to load the new installed
24
Here's an example nova flavor resource:
26
heat_template_version: 2013-05-23
27
description: Heat Flavor creation example
30
type: OS::Nova::Flavor
36
extra_specs: {"quota:disk_read_bytes_sec": "10240000"}
39
### Issues with the Nova Flavor plugin
41
By default only the admin tenant can manage flavors because of the default
42
policy in Nova: ```"compute_extension:flavormanage": "rule:admin_api"```
44
To let the possibility to all tenants to create flavors, the rule must be
45
replaced with the following: ```"compute_extension:flavormanage": ""```
47
The following error occurs if the policy has not been correctly set:
48
ERROR: Policy doesn't allow compute_extension:flavormanage to be performed.
50
Currently all nova flavors have a global scope, which leads to several issues:
51
1. Per-stack flavor creation will pollute the global flavor list.
52
2. If two stacks create a flavor with the same name collision will occur,
53
which will lead to the following error:
55
ERROR (Conflict): Flavor with name dupflavor already exists.