Hello, We come across this: http://docs.openstack.org/developer/heat/pluginguide.html Looks like it solves three of the purposes listed below: 1. Define a custom resource type with properties and attributes 2. Register the resource to the Hear orchestrator 3. Write a driver/plugin (most likely the Life Cycle methods) which can create/manage the resources when encounter from the Heat orchestration engine. Am I right? Now the question is: in one place it is mentioned as: " It defines methods corresponding to the life cycle as well as the basic hooks for plug-ins to handle the work of communicating with specific down-stream services " Can this down-stream service be *anything* (say a third-party storage array)? Or it has to be a OpenStack service only? Thanks in advance, Pradip -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141112/ad5a8c31/attachment.html>