On 09/02/14 03:09, Robert Collins wrote:
In principle yes.
You need:
- to write a module to orchestrate the nova flavor API.
https://wiki.openstack.org/wiki/Heat/Plugins
- to configure your policy rules in the cloud in question to let the
heat engine user create flavors
Not quite.
In principle yes.
You need:
- to write a module to orchestrate the nova flavor API.
- to configure your policy rules in the cloud in question to let the
heat engine user create flavors
-Rob
On 9 February 2014 20:49, ELISHA, Moshe (Moshe)
moshe.eli...@alcatel-lucent.com wrote:
Hello,
I am
Heat template orchestrates user actions, while management of flavors is
typically admin's job (due to their tight link to the physical hardware
configuration, unknown to a regular user).
Regards,
Alex
From: ELISHA, Moshe (Moshe) moshe.eli...@alcatel-lucent.com
To:
Hello,
I am wondering if instead of being obligated to use an existing flavor, I could
declare a flavor (with its properties) inside Heat template and let Heat create
the flavor automatically?
Similar to the ability to create networks as part of the template.
Thanks.