Re: [openstack-dev] [aodh] Tempest gate not working

Hi, Thanks for this mail, I also noticed that yesterday, and I am trying to fix it by https://review.openstack.org/#/c/320378/ cheers, Liusheng 在 2016/5/24 22:50, Julien Danjou 写道: Hi, So it turns out we tried (especially Ryota) to add Tempest support via https://review.openstack.org

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

Another personal suggestion: maybe we can have a weekly routine mail thread to present the things need to be discussed or need to be notified. The mail will also list the topics posted in meeting agenda and ask to Telemetry folks if a online IRC meeting is necessary, if there are a very few

Re: [openstack-dev] [telemetry] stepping down as PTL

Thanks for your awsome work in last cycle Gordon! I know you have pay a lot of efforts to make telemetry better, and I have learnt much from you. -- Liu sheng 在 2016/3/12 1:33, Emilien Macchi 写道: On Fri, Mar 11, 2016 at 11:32 AM, gordon chung > wrote:

Re: [openstack-dev] [telemetry][aodh] "aodh alarm list" vs "aodh alarm search"

Thanks for this discussion and the agreement, it sounds good, I will upload related changes. -- Liu sheng 在 2016/3/7 23:42, gordon chung 写道: On 07/03/2016 8:05 AM, Julien Danjou wrote: On Mon, Mar 07 2016, gordon chung wrote: shall we drop 'alarm search' nomenclature and use just 'alarm

[openstack-dev] [telemetry][aodh] "aodh alarm list" vs "aodh alarm search"

Hi folks, Currently, we have supported "aodh alarm list" and "aodh alarm search" commands to query alarms. They both need mandatory "--type" parameter, and I want to drop the limitation[1]. if we agree that, the "alarm list" will only used to list all alarms and don't support any query

Re: [openstack-dev] [ceilometer] Unable to get ceilometer events for instances running for demo project

Hi Umar, You can only get the events(or events without project info) belong to admin tenant if you run event-list command with admin project; and you can only get the events belong to demo tenant with event-list running with demo project. -- Liu sheng 在 2016/3/1 14:00, Umar Yousaf 写道: I have

Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating

k the main items are to not flood the message bus with messages that no one is listening to. but if there is a use case for it, i'm happy to see it remain (and improved). you can check the patch that Liusheng referenced, but the basic concept is as mentioned: send message when an alarm state is cha

Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating

PI instead? And what do you mean by "aggregation on events data"? what kind of aggregations can we do? Thanks, Ifat. -Original Message- From: liusheng [mailto:liusheng1...@126.com] Sent: Wednesday, January 06, 2016 10:10 AM Hi Ifat, what way do you want to use the alarm change

[openstack-dev] [telemetry][aodh] The purpose of notification about alarm updating

Hi folks, Currently, a notification message will be emitted when updating an alarm (state transition, attribute updating, creation), this functionality was added by change[1], but the change didn't describe any purpose. So I wonder whether there is any usage of this type of notification, we

Re: [openstack-dev] [Ceilometer] [Bug#1497073]The return sample body of sample-list is different when use -m and not

I don't think we need two APIs to act duplicated functionalities, the "sample-list -m" command actually invoke API "GET /V2/meters/", it is more like a meter related API, not sample. I personally prefer to mark the "sample-list -m" command deprecated and dropped in future cycle. is this

[openstack-dev] [Ceilometer]heavy time cost of event-list

Hi folks, With the master Ceilometer installed, and use mysql backend, the event-list command met a heavy time cost. if we have a bit large number of events stored, it is easy to cause event list API request timeout, the rally people told me that this issue has broken the

Re: [openstack-dev] [Ceilometer][Aodh] event-alarm fire policy

Just a personal thought, can we add an ACK to alarm notifier? when an event-alarm fired, the alarm state transformed to "alarm", if 'alarm_action' has been set, the 'alarm_action' will be triggered and notify. for event-alarm, a timout can be set to wait the ACK from alarm notifier, if the ACK

Re: [openstack-dev] [Ceilometer][AODH] Timeout Event Alarms

events based on events timeout when we need an event-timeout alarm. and also, the access of event pipeline definitions to users is inadvisable. I personally think it'd better to implement the second option and based on Ryota's proposal. Best Regards Liusheng 在 2015/8/5 3:36, gord chung 写道: hi

Re: [openstack-dev] [nova][security] Enable user password complexity verification

Thanks for this topic, also, I think it is similar situation when talking about keystone users, not only the instances's password. 在 2015/6/3 17:48, 郑振宇 写道: Hi All, The current OpenStack does not provide user password complexity verification option. When performing actions such as create

Re: [openstack-dev] [nova][ceilometer] FloatingIp pollster spamming n-api logs (bug 1328694)

Matt, Eoghan, thanks Firstly , sorry for the effection, the direct reason of the bug is an issue in nova-network scenario, it is my mistake when commit patch https://review.openstack.org/#/c/81429/ to fix the bug 1262124. with agreement of Matt's view, to dissipate the load of nova API, so it

Re: [openstack-dev] [ceilometer]support direct alarm_evaluator db access

will greatly improve the performance if you have many alarms. Best regards, Nihongi From: liusheng liusheng1...@126.com To: openstack-dev@lists.openstack.org Date: Tue, 15 Apr 2014 15:26:58 +0800 Subject: [openstack-dev] [ceilometer]support direct alarm_evaluator db access Hi there, Currently

[openstack-dev] [ceilometer]support direct alarm_evaluator db access

Hi there, Currently,alarm_evaluator invoke ceilometerclient to get all assigned alarms. and then, evaluate per alarm by get statistics, which will also call ceilometerclient. this process is: evaluator--ceilometerclient--ceilometer API--db. If we use default option of evaluation_interval (60s),