Checked your alarm_url string again, it seems that your heat.conf file
contains this line:

heat_waitcondition_server_url=http://<MY_IP>:8000/waitcondition

You have to change <MY_IP> to the IP of the heat-cfn-api service host.

Regards,
 Qiming

On Tue, Mar 10, 2015 at 10:47:10AM +0000, Srujana C P wrote:
> Hi,
> 
> I would like to explore on auto scaling functionality of heat. So I have 
> started with sample word press template available. It could create a 
> stack(alarms, instance, etc., ). However, alarm is not getting triggered 
> whenever I put stress on it. The alarm_action assigned to the alarm created 
> from the template is
> Alarm_action : 
> http://<MY_IP>:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a7c4be2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f2cf321a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2<http://%3cMY_IP%3e:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a7c4be2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f2cf321a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2>
>  
> 015-03-10T03%3A56%3A36Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=3013823c3d564433b32c81c4bff2c638&SignatureVersion=2&Signature=CWLhRKiwRPOT1P88i0AH8SaeY%2FA4QTQqMtkwY0gkZno%3D
> 
> This alarm_url is not doing required scaling action. So, in order to confirm 
> whether the alarm has been hit, I just modified alarm action with some script 
> url. I could see the script got executed.
> 
> Can someone please help me on below queries
> 
> 1.       How this alarm_url got generated?
> 
> 2.       Why this has AWSAccesskeyId details? To which access key it is 
> referring to?
> 
> 3.       What changes need to be done to execute the above mentioned alarm 
> url?
> 
> 4.       How to configure heat to authenticate with Openstack?
> 
> Any help on this would be very thankful.
> 
> Thanks,
> Srujana
> 
> 
> DISCLAIMER
> ==========
> This e-mail may contain privileged and confidential information which is the 
> property of Persistent Systems Ltd. It is intended only for the use of the 
> individual or entity to which it is addressed. If you are not the intended 
> recipient, you are not authorized to read, retain, copy, print, distribute or 
> use this message. If you have received this communication in error, please 
> notify the sender and delete all copies of this message. Persistent Systems 
> Ltd. does not accept any liability for virus infected mails.
> 



> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to