Files

T

Steve Baker 9850832da5 Implement nova client plugin

This moves the client creation code out of Clients._nova() into
its own client plugin.

Raising nova exceptions has been moved to
heat.tests.v1_1.fakes.fake_exception since it is actually impossible
to directly create a nova exception object which works on both
novaclient 2.17 and (yet to be released) 2.18.
nova.exceptions.from_response is stable across novaclient releases
so all test exceptions are now raised using from_response.

Change-Id: Id68ff32c381c9c8c06f3712736d1888d1d0e8110

2014-07-08 09:42:36 +12:00

resources

Implement Flavor Extra-specs Key/Value Pairs

2014-07-02 15:07:12 +08:00

tests

Implement nova client plugin

2014-07-08 09:42:36 +12:00

__init__.py

Add a Nova Flavor resource.

2014-05-02 20:47:35 +02:00

README.md

Implement Flavor Extra-specs Key/Value Pairs

2014-07-02 15:07:12 +08:00

README.md

Nova Flavor plugin for OpenStack Heat

This plugin enables using Nova Flavors as resources in a Heat template.

Note that the current implementation of the Nova Flavor resource does not allow specifying the name and flavorid properties for the resource. This is done to avoid potential naming collision upon flavor creation as all flavor have a global scope.

1. Install the Nova Flavor plugin in Heat

NOTE: Heat scans several directories to find plugins. The list of directories is specified in the configuration file "heat.conf" with the "plugin_dirs" directive.

2. Restart heat

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

Template Format

Here's an example nova flavor resource:

heat_template_version: 2013-05-23
description:  Heat Flavor creation example
resources:
  test_flavor:
    type: OS::Nova::Flavor
    properties:
      ram: 1024
      vcpus: 1
      disk: 20
      swap: 2
      extra_specs: {"quota:disk_read_bytes_sec": "10240000"}

Issues with the Nova Flavor plugin

By default only the admin tenant can manage flavors because of the default policy in Nova: "compute_extension:flavormanage": "rule:admin_api"

To let the possibility to all tenants to create flavors, the rule must be replaced with the following: "compute_extension:flavormanage": ""

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

Currently all nova flavors have a global scope, which leads to several issues:

Per-stack flavor creation will pollute the global flavor list.
If two stacks create a flavor with the same name collision will occur, which will lead to the following error:

ERROR (Conflict): Flavor with name dupflavor already exists.