Open Stack

Hi,

I mean the statistic property of the Alarm resource [1], together with
period and evaluation_periods.

[1]
http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Ceilometer::Alarm

Best regards,

Pavlo Shchelokovskyy
Software Engineer
Mirantis Inc
www.mirantis.com

On Fri, Mar 13, 2015 at 3:19 PM, Chinasubbareddy M <
chinasubbareddy_m at persistent.com> wrote:

>  Hi,
>
>
>
> Thank you for your reply , part from your reply  didn’t have any clue for
> me  , here is that
>
>
>
> but by fiddling with aggregate functions you can surely set it up to alarm
> on some stack-average metrics.
>
>
>
> Could you please give me one example of such so that may help me out to go
> further ?
>
>
>
> *From:* Pavlo Shchelokovskyy [mailto:pshchelokovskyy at mirantis.com]
> *Sent:* Friday, March 13, 2015 5:34 PM
> *To:* openstack at lists.openstack.org
> *Subject:* [Openstack] Fwd: [Heat][Ceilometer][Autoscaling]
>
>
>
> Hi,
>
>
>
> when setting up the ceilometer alarm, you provide it with metadata to
> query samples for (contains stack id in some form), and how to aggregate
> them. That's how ceilometer knows when to fire the alarm. AFAIR those
> examples in heat-templates create alarms that go off when any of the
> samples is above threshold, but by fiddling with aggregate functions you
> can surely set it up to alarm on some stack-average metrics.
>
>
>
> You can check the ceilometer resource metadata by launching an ASG stack
> and showing the ceilometer resource with id as id of one of nova servers.
>
>
>
> ceilometer resource-show -r {id-of-nova-server}
>
>
>
> Examining the user_metadata field, there will be something stack-id
> related. Use that user_metadata.<field> name to setup the ceilometer alarm.
>
>
>
> Best regards,
>
>
>   Pavlo Shchelokovskyy
>
> Software Engineer
>
> Mirantis Inc
>
> www.mirantis.com
>
>
>
> On Fri, Mar 13, 2015 at 1:23 PM, Chinasubbareddy M <
> chinasubbareddy_m at persistent.com> wrote:
>
> Hello Qiming,
>
> When I put stress on the server, it is adding one more node to the auto
> scaling group. So I would like to know for the next scaling action to
> perform, is ceilometer alarm is raised based on the load on all existing
> machines in the auto scaling group or individual servers in the group.
>
> As Ceilometer is not considering stack as its resource, How it would
> calculate the statistics for the entire stack?
>
> Regards,
> Subbareddy,
> Persistent systems ltd.
>
> -----Original Message-----
> From: Chinasubbareddy M
> Sent: Wednesday, March 11, 2015 6:55 PM
> To: 'Qiming Teng'; openstack at lists.openstack.org
> Cc: David Peraza
> Subject: RE: [Openstack] [Heat][Ceilometer][Autoscaling]
>
> Hi,
>
> Thank you Qiming  , finally it worked and problem was with auth uri  in
> ec2token section , it has " /ec2token"  ,  after removing it  auto scaling
> started working .
>
> This is the final working  parameter:
>
> [ec2authtoken]
> auth_uri=http://1.2.3.4:5000/v2.0
>
> -----Original Message-----
> From: Qiming Teng [mailto:tengqim at linux.vnet.ibm.com]
> Sent: Wednesday, March 11, 2015 2:52 PM
> To: Chinasubbareddy M; openstack at lists.openstack.org
> Subject: Re: [Openstack] [Heat][Ceilometer][Autoscaling]
>
>
> > > http://<MY_IP>:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a
> <http://%3cMY_IP%3e:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a>
> > > 7c
> > > 4be2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f
> > > 2c
> > > f321a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2<http
> > > :/
> > > /%3cMY_IP%3e:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a7c
> > > 4b
> > > e2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f2c
> > > f3 21a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2>
> > > 015-03-10T03%3A56%3A36Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=30
> > > 13
> > > 823c3d564433b32c81c4bff2c638&SignatureVersion=2&Signature=CWLhRKiwRP
> > > OT 1P88i0AH8SaeY%2FA4QTQqMtkwY0gkZno%3D
>
>
> The alarm_url above shows that the <MY_IP> part is hardcoded in your
> heat.conf file.
>
> Seems that your authentication to Keystone using ec2token has failed?
> You may check if you have the following settings in your heat.conf file:
>
> [ec2authtoken]
> auth_uri=http://1.2.3.4:5000/v2.0
>
> That is one reason that could lead to the problem you have met. Another
> thing to check is whether you have ec2 service configured in Keystone:
>
> $ keystone service-list | grep ec2
>
> It was for compatibility's reason that Heat uses EC2 token authentication
> for the alarm url, as I have mentioned in previous replies.
>
> Regards,
>   Qiming
>
> On Tue, Mar 10, 2015 at 01:44:17PM +0000, Chinasubbareddy M wrote:
> > Hi,
> >
> > We used to have Ip address only , while troubleshooting we made that to
> localhost.
> > If you see the url , there is AWS access key and if we execute the url
> manually , its getting failed to contact keystone and get token.
> >
> > If we get the token manually and request it again ,it's getting failed
> with unknown heat resource.
> >
> > It would be easy if you can share any working template which is
> generating proper webhook.
> >
> >
> > Regards,
> > Subbareddy,
> > Persistent systems.
> >
> >
> >
> > -----Original Message-----
> > From: Qiming Teng [mailto:tengqim at linux.vnet.ibm.com]
> > Sent: Wednesday, March 11, 2015 3:00 AM
> > To: openstack at lists.openstack.org
> > Subject: Re: [Openstack] [Heat][Ceilometer][Autoscaling]
> >
> > 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%3Aec3e93810a
> <http://%3cMY_IP%3e:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a>
> > > 7c
> > > 4be2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f
> > > 2c
> > > f321a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2<http
> > > :/
> > > /%3cMY_IP%3e:8000/v1/signal/arn%3Aopenstack%3Aheat%3A%3Aec3e93810a7c
> > > 4b
> > > e2881bd7ede428526a%3Astacks%2Fsrujana1%2Fc0b5862f-f3e6-4fa8-a6ef-f2c
> > > f3 21a70bb%2Fresources%2Fweb_server_scaledown_policy?Timestamp=2>
> > > 015-03-10T03%3A56%3A36Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=30
> > > 13
> > > 823c3d564433b32c81c4bff2c638&SignatureVersion=2&Signature=CWLhRKiwRP
> > > OT 1P88i0AH8SaeY%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 at 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 at lists.openstack.org
> > Unsubscribe :
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> >
> > 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.
> >
>
>
> 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 at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
>
>
> 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20150313/bb87bf3c/attachment.html>