Thanks, Zane for pointing out the right mailing list.
--pradip On Wed, Nov 12, 2014 at 6:35 PM, Zane Bitter <zbit...@redhat.com> wrote: > The developer mailing list is not for usage questions. Please ask this on > ask.openstack.org - I'm sure a lot of people will be interested in the > answer and we want it searchable for them in future. Feel free to ping me > with a link when you've posted it. > > cheers, > Zane. > > On 12/11/14 06:00, Pradip Mukhopadhyay wrote: > >> 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 >> >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStackemail@example.com >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStackfirstname.lastname@example.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev