Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Heat Resource Plugin for third party storage


We come across this:

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