On 15/10/13 02:18, Sam Alba wrote:
Hello,
I am working on a Heat plugin that makes a new resource available in a
template. It's working great and I will opensource it this week if I
can get the packaging right...
Awesome! :)
Right now, I am linking my module.py file in /usr/lib/heat to get
On Tue, Oct 15, 2013 at 2:31 AM, Zane Bitter zbit...@redhat.com wrote:
On 15/10/13 02:18, Sam Alba wrote:
Hello,
I am working on a Heat plugin that makes a new resource available in a
template. It's working great and I will opensource it this week if I
can get the packaging right...
Hi Sam,
We wrote a Heat resource plugin as well [1]
The trick to getting heat to auto-discover a module is to install it to the
/usr/lib/heat (or possibly, but unlikely, /usr/lib64/heat) directory.
I have found that the setuptools incantation:
sudo python setup.py install
On 15/10/13 16:05 -0700, Tim Smith wrote:
Hi Sam,
We wrote a Heat resource plugin as well [1]
The trick to getting heat to auto-discover a module is to install it to the
/usr/lib/heat (or possibly, but unlikely, /usr/lib64/heat) directory.
I have found that the setuptools incantation:
sudo
Hello,
I am working on a Heat plugin that makes a new resource available in a
template. It's working great and I will opensource it this week if I
can get the packaging right...
Right now, I am linking my module.py file in /usr/lib/heat to get it
loaded when heat-engine starts. But according to
