Open Stack

Abhishek,

for communication with Nova Heat is using Nova's REST API via
python-novaclient exclusively. So if any Nova functionality is exposed via
novaclient's Python API - Heat can in principle do it.

Another question is what are those "check" and "change" you are willing to
do? This should be in line with Heat resource life cycle model. If it is
some general thing applicable/useful to any OpenStack deployment you can
propose a patch (or a spec first) and we can consider including it in
upstream. If it is more specific to your deployment - you can make yourself
a specialized resource as Heat resource plugin and override/extend any
methods of OS::Nova::Server resource and use this plugin instead of
OS::Nova::Server in your cloud (for an example see Rackspace Cloud Server
resource in heat/contrib).

Best regards,

Pavlo Shchelokovskyy
Software Engineer
Mirantis Inc
www.mirantis.com

On Fri, Apr 3, 2015 at 10:12 AM, Abhishek Talwar/HYD/TCS <
abhishek.talwar at tcs.com> wrote:

> Hi Folks,
>
> I am trying if we can have an api call from heat to nova and hit one of
> the nova clients method. I want to have a check in heat and if that happens
> it should request nova for a change in the instance through one of nova's
> command.
>
> Any information regarding this.
>
>
>  Thanks and Regards
>
> Abhishek Talwar
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150403/5858577d/attachment.html>