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 --install-purelib=/usr/lib/heat works well for source-installed heat. Hope that helps, Cheers, Tim [1] https://github.com/gridcentric/cobalt-heat On Mon, Oct 14, 2013 at 5:18 PM, Sam Alba <sam.a...@gmail.com> 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... > > Right now, I am linking my module.py file in /usr/lib/heat to get it > loaded when heat-engine starts. But according to the doc, I am > supposed to be able to make the plugin discoverable by heat-engine if > the module appears in the package "heat.engine.plugins"[1] > > I looked into the plugin_loader module in the Heat source code and it > looks like it should work. However I was unable to get a proper Python > package. > > Has anyone been able to make this packaging right for an external Heat > plugin? > > Thanks in advance, > > > [1] > https://wiki.openstack.org/wiki/Heat/Plugins#Installation_and_Configuration > > -- > @sam_alba > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
