Wednesday, 2018-02-14

*** gauravsitlani has joined #openstack-meeting-300:04
*** VW has joined #openstack-meeting-300:13
*** VW has quit IRC00:14
*** VW has joined #openstack-meeting-300:15
*** VW has quit IRC00:20
*** jamesmcarthur has joined #openstack-meeting-300:25
*** jamesmcarthur has quit IRC00:30
*** slaweq has joined #openstack-meeting-300:31
*** slaweq has quit IRC00:36
*** mjturek has quit IRC00:39
*** chyka has quit IRC00:42
*** chyka has joined #openstack-meeting-300:42
*** chyka has quit IRC00:47
*** VW has joined #openstack-meeting-301:22
*** armstrong has quit IRC01:23
*** hongbin has joined #openstack-meeting-301:24
*** jamesmcarthur has joined #openstack-meeting-301:26
*** VW has quit IRC01:43
*** VW has joined #openstack-meeting-301:44
*** gauravsitlani has quit IRC01:44
*** rmcall has joined #openstack-meeting-301:46
*** VW has quit IRC01:49
*** benj_ has quit IRC02:08
*** chyka has joined #openstack-meeting-302:09
*** benj_ has joined #openstack-meeting-302:09
*** chyka has quit IRC02:13
*** jamesmcarthur has quit IRC02:26
*** slaweq has joined #openstack-meeting-302:33
*** slaweq has quit IRC02:37
*** notmyname has quit IRC02:38
*** iyamahat__ has quit IRC02:40
*** notmyname has joined #openstack-meeting-302:41
*** yamahata has quit IRC02:42
*** salv-orl_ has joined #openstack-meeting-302:45
*** salv-orlando has quit IRC02:48
*** d0ugal has quit IRC02:49
*** d0ugal has joined #openstack-meeting-302:59
*** harlowja has quit IRC03:30
*** VW has joined #openstack-meeting-303:32
*** yamamoto has joined #openstack-meeting-303:43
*** d0ugal has quit IRC03:55
*** d0ugal has joined #openstack-meeting-303:59
*** anilvenkata has joined #openstack-meeting-304:00
*** harlowja has joined #openstack-meeting-304:12
*** cshastri has joined #openstack-meeting-304:20
*** jamesmcarthur has joined #openstack-meeting-304:26
*** harlowja has quit IRC04:30
*** jamesmcarthur has quit IRC04:30
*** slaweq has joined #openstack-meeting-304:34
*** lpetrut has joined #openstack-meeting-304:38
*** slaweq has quit IRC04:38
*** hongbin has quit IRC04:55
*** psachin` has joined #openstack-meeting-305:04
*** psachin has joined #openstack-meeting-305:04
*** VW has quit IRC05:06
*** VW has joined #openstack-meeting-305:07
*** lpetrut has quit IRC05:11
*** VW has quit IRC05:11
*** harlowja has joined #openstack-meeting-305:14
*** lpetrut has joined #openstack-meeting-305:19
*** lpetrut has quit IRC05:29
*** diablo_rojo has quit IRC05:34
*** VW has joined #openstack-meeting-305:37
*** iyamahat has joined #openstack-meeting-305:37
*** VW has quit IRC05:42
*** iyamahat has quit IRC05:45
*** psachin has quit IRC05:45
*** psachin` has quit IRC05:45
*** pgadiya has joined #openstack-meeting-305:49
*** VW has joined #openstack-meeting-305:51
*** psachin has joined #openstack-meeting-305:51
*** VW has quit IRC05:56
*** slaweq has joined #openstack-meeting-305:59
*** slaweq has quit IRC06:04
*** coolsvap has joined #openstack-meeting-306:17
*** psachin has quit IRC06:20
*** marios has joined #openstack-meeting-306:21
*** VW has joined #openstack-meeting-306:23
*** harlowja has quit IRC06:24
*** VW has quit IRC06:28
*** psachin has joined #openstack-meeting-306:28
*** VW has joined #openstack-meeting-306:33
*** VW has quit IRC06:37
*** VW has joined #openstack-meeting-306:56
*** stendulker has joined #openstack-meeting-306:59
*** VW has quit IRC07:01
*** belmoreira has joined #openstack-meeting-307:01
*** ianychoi_ is now known as ianychoi07:08
*** alexchadin has joined #openstack-meeting-307:17
*** VW has joined #openstack-meeting-307:27
*** VW has quit IRC07:32
*** lpetrut has joined #openstack-meeting-307:42
*** slaweq has joined #openstack-meeting-307:45
*** slaweq has quit IRC07:53
*** slaweq has joined #openstack-meeting-307:54
*** pcaruana has joined #openstack-meeting-307:56
*** slaweq has quit IRC07:59
*** VW has joined #openstack-meeting-308:05
*** slaweq has joined #openstack-meeting-308:05
*** VW has quit IRC08:10
*** slaweq has quit IRC08:10
*** zhipeng has joined #openstack-meeting-308:14
*** yamamoto has quit IRC08:21
*** yamamoto has joined #openstack-meeting-308:22
*** e0ne has joined #openstack-meeting-308:22
*** VW has joined #openstack-meeting-308:38
*** slaweq has joined #openstack-meeting-308:40
*** VW has quit IRC08:43
*** slaweq has quit IRC08:44
*** ttx has joined #openstack-meeting-308:50
*** iyamahat has joined #openstack-meeting-309:05
*** tssurya has joined #openstack-meeting-309:05
*** yamahata has joined #openstack-meeting-309:07
*** zhipeng has quit IRC09:11
*** VW has joined #openstack-meeting-309:17
*** VW has quit IRC09:22
*** iyamahat has quit IRC09:23
*** slaweq has joined #openstack-meeting-309:24
*** yamahata has quit IRC09:24
*** jamesmcarthur has joined #openstack-meeting-309:25
*** pgadiya has quit IRC09:28
*** slaweq has quit IRC09:28
*** pgadiya has joined #openstack-meeting-309:29
*** jamesmcarthur has quit IRC09:30
*** yamahata has joined #openstack-meeting-309:31
*** pgadiya has quit IRC09:31
*** pgadiya has joined #openstack-meeting-309:33
*** pgadiya has quit IRC09:33
*** pgadiya has joined #openstack-meeting-309:38
*** pgadiya has quit IRC09:38
*** yikun_jiang has quit IRC09:45
*** VW has joined #openstack-meeting-309:47
*** VW has quit IRC09:52
*** stendulker_ has joined #openstack-meeting-309:55
*** alexchadin has quit IRC09:56
*** alexchadin has joined #openstack-meeting-309:57
*** stendulker has quit IRC09:57
*** VW has joined #openstack-meeting-310:02
*** pcaruana has quit IRC10:05
*** VW has quit IRC10:06
*** makowals has joined #openstack-meeting-310:19
*** pcaruana has joined #openstack-meeting-310:20
*** VW has joined #openstack-meeting-310:25
*** VW has quit IRC10:30
*** anilvenkata has quit IRC10:32
*** anilvenkata has joined #openstack-meeting-310:32
*** yamahata has quit IRC10:34
*** sambetts|afk is now known as sambetts10:48
*** slaweq_ has joined #openstack-meeting-310:50
*** slaweq_ has quit IRC10:55
*** ywat has quit IRC11:00
*** VW has joined #openstack-meeting-311:02
*** stendulker has joined #openstack-meeting-311:05
*** VW has quit IRC11:07
*** stendulker_ has quit IRC11:09
*** stendulker has quit IRC11:13
*** jamesmcarthur has joined #openstack-meeting-311:19
*** jamesmcarthur has quit IRC11:23
*** pbourke has quit IRC11:29
*** pcaruana has quit IRC11:30
*** pbourke has joined #openstack-meeting-311:30
*** zhipeng has joined #openstack-meeting-311:31
*** alexchadin has quit IRC11:38
*** VW has joined #openstack-meeting-311:38
*** armstrong has joined #openstack-meeting-311:42
*** pcaruana has joined #openstack-meeting-311:42
*** VW has quit IRC11:44
*** alexchadin has joined #openstack-meeting-311:47
*** raildo has joined #openstack-meeting-311:57
*** cshastri_ has joined #openstack-meeting-312:08
*** zhipeng has quit IRC12:09
*** julim has quit IRC12:11
*** cshastri has quit IRC12:11
*** slaweq_ has joined #openstack-meeting-312:11
*** VW has joined #openstack-meeting-312:12
*** julim has joined #openstack-meeting-312:12
*** slaweq_ has quit IRC12:16
*** VW has quit IRC12:17
*** zhipeng has joined #openstack-meeting-312:18
*** slaweq_ has joined #openstack-meeting-312:19
*** slaweq_ has quit IRC12:23
*** yamamoto has quit IRC12:23
*** yamamoto has joined #openstack-meeting-312:24
*** zhipeng has quit IRC12:35
*** makowals has quit IRC12:43
*** VW has joined #openstack-meeting-312:47
*** VW has quit IRC12:51
*** zhipeng has joined #openstack-meeting-312:55
*** ianychoi has quit IRC13:00
*** ianychoi has joined #openstack-meeting-313:04
*** zhipeng has quit IRC13:04
*** ianychoi has quit IRC13:09
*** VW has joined #openstack-meeting-313:10
*** e0ne has quit IRC13:10
*** e0ne has joined #openstack-meeting-313:13
*** yamamoto has quit IRC13:17
*** yamamoto has joined #openstack-meeting-313:18
*** yamamoto has quit IRC13:22
*** sgrasley1 has quit IRC13:23
*** VW has quit IRC13:25
*** VW has joined #openstack-meeting-313:25
*** VW has quit IRC13:30
*** julim has quit IRC13:35
*** jamesmcarthur has joined #openstack-meeting-313:41
*** rmcall has quit IRC13:43
*** jamesmcarthur has quit IRC13:46
*** yamamoto has joined #openstack-meeting-313:48
*** mjturek has joined #openstack-meeting-313:52
*** cshastri_ has quit IRC13:53
*** jonher- is now known as jonher13:55
*** pilgrimstack has joined #openstack-meeting-314:00
tobberydberg#startmeeting publiccloud-wg14:04
openstackMeeting started Wed Feb 14 14:04:48 2018 UTC and is due to finish in 60 minutes.  The chair is tobberydberg. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:04
*** openstack changes topic to " (Meeting topic: publiccloud-wg)"14:04
openstackThe meeting name has been set to 'publiccloud_wg'14:04
tobberydbergHope you all are well!14:05
tobberydbergNice to see you all here14:05
tobberydbergAgenda at
tobberydbergThink about this weeks agenda as very open, feel free to add things14:06
tobberydbergAnd please add you name there14:06
tobberydbergI assume Howard will join in soon here as well, but lets get started14:07
tobberydberg#topic 1. Planning of PTG agenda14:07
*** openstack changes topic to "1. Planning of PTG agenda (Meeting topic: publiccloud-wg)"14:07
*** jamesmcarthur has joined #openstack-meeting-314:07
*** alexchadin has quit IRC14:08
*** alexchadin has joined #openstack-meeting-314:08
*** alexchadin has quit IRC14:08
tobberydbergWhen it comes to that planning, it looks like we are doing "mornings" only for official schedule ... howard has a lot of conflicting duties during afternoons14:08
*** alexchadin has joined #openstack-meeting-314:09
tobberydbergWe have been waiting to set that as a final for people to signup for interest and check how their schedule looks like14:09
*** alexchadin has quit IRC14:09
*** zhipeng has joined #openstack-meeting-314:09
tobberydbergWhat about you that wont be in Dublin, can you join remotely?14:10
*** alexchadin has joined #openstack-meeting-314:10
*** alexchadin has quit IRC14:10
*** alexchadin has joined #openstack-meeting-314:11
astellwagI'll be able to join remotely14:11
*** alexchadin has quit IRC14:11
*** jamesmca_ has joined #openstack-meeting-314:11
tobberydbergIf so, please put your name there as well, so we can take that into consideration14:11
*** alexchadin has joined #openstack-meeting-314:11
*** alexchadin has quit IRC14:12
tobberydbergYou are welcome and add suggestions of topics as well14:12
*** alexchadin has joined #openstack-meeting-314:12
*** alexchadin has quit IRC14:12
*** zhipeng has quit IRC14:14
*** cshastri has joined #openstack-meeting-314:14
tobberydbergLunch presentation14:15
tobberydbergJust added that to the PTG planning14:15
tobberydbergWe will most probably get the opportunity to say a few words about the group, so feel free to suggest things worth mention14:16
tobberydbergThoughts, suggestions etc??14:16
tobberydbergMoving on slowly here and we can get back to that14:17
tobberydberg#topic 2. Recap feedback sent to foundation14:17
*** openstack changes topic to "2. Recap feedback sent to foundation (Meeting topic: publiccloud-wg)"14:17
mrhillsmanIs this a lightning talk?14:17
tobberydbergThe lunch thing is not really a lightning - but kind of .... just one or two quick slides basically14:18
apriceI would like to put time on the PTG agenda to discuss the feedback sent to the Foundation14:19
apricewe have a few folks attending that would like to join and I think that it would be a good place to go through the list tobberrydberg sent last week14:19
tobberydbergFor sure. Suitable under the Passport topic?14:19
apriceyeah I think that works14:20
apriceI think that there are 5 folks from our side that are interested in attending.14:20
tobberydbergPerfect! Please add the names there, or inform them about that page14:20
apricei can add their names to the etherpad14:20
apricethank you for sending that over!14:21
*** julim has joined #openstack-meeting-314:21
tobberydbergyou are welcome!14:21
*** sgrasley1 has joined #openstack-meeting-314:21
tobberydbergThat was basically what this tpoic was about, checking the status of that feedback14:22
tobberydbergNow we know we will get response at the PTG14:22
*** alexchadin has joined #openstack-meeting-314:22
tobberydberg#topic 3. Other topics14:23
*** openstack changes topic to "3. Other topics (Meeting topic: publiccloud-wg)"14:23
tobberydbergpilgrimstack - your topic:  Changing the time slot for this bi-weekly meeting14:23
*** rmcall has joined #openstack-meeting-314:24
*** amofakhar has joined #openstack-meeting-314:25
*** alexchadin has quit IRC14:26
tobberydbergI know pilgrimstack often has conflicting meeting at this time14:26
pilgrimstackYep that's the case every week in fact14:26
pilgrimstackI'm trying to manage 2 meeting right now14:27
tobberydbergDo you have a suggestion for a time? Or, should we setup a doodle and vote until next meeting?14:27
pilgrimstackit's ok for me 30 min later in fact14:28
pilgrimstackin 2 min14:28
pilgrimstackor later, I'm free the rest of the day14:29
tobberydbergHehe, ok. The general meeting rooms are booked by the hour, so as long as we don't have a meetbot in our channel we will have to find a free slot14:29
apriceI think a doodle would be a good idea so we could see if a time change opens it up for other folks14:30
tobberydbergThat is my commit for meetbot ... haven't been reviewed yet, will ping the soon to see if I'm missing something14:31
*** zhipeng has joined #openstack-meeting-314:31
tobberydbergOk, I agree ... doodle is the best14:31
tobberydbergWhat about weekly meeting instead of bi-weekly?14:32
astellwagthat would open up for a chance to alternate time slots14:32
tobberydbergyes, for sure .... would make it much easier14:33
zhipenghi guys14:34
zhipengsorry for running late14:34
jamesmca_are there is enough content to warrant weekly meetings?14:34
jamesmca_sorry - is there enough content to warrant weekly meetings14:35
pilgrimstacknot sure for a weekly meeting14:35
pilgrimstackbi-weekly on my side seems ok14:35
zhipengi think if we are gonna extend to APAC this year14:36
zhipenga tick-tock weekly meeting is definitely needed14:36
tobberydbergI would like to spend some more time on a more weekly basis with the projects we have ... getting more traction of those, so seeking weekly commitment ?)14:38
*** coolsvap has quit IRC14:39
tobberydbergBut, with better communication in our channel, what might be good enough?14:39
tobberydbergAs you say zhipeng ... to get apac more onboard I believe we need another meeting on even weeks that is better suited for them time wise14:40
zhipengwhich could happen on #openstack-publiccloud14:40
tobberydbergBut, on the other hand...are we enough engaged people to manage that?14:41
tobberydbergfor sure, more like an "inofficial" meeting ?14:41
persiaBased on my estimates of the timezones of the folks that tend to attend this meeting, I suspect it would be possible to sustain something around 9:00 UTC, which is early enough that many APAC people can make it.  Earlier than that might be thin.14:42
tobberydberg#action tobberydberg to setup a doodle for meeting time suggestions14:43
tobberydbergYes persia ... harder for US people14:43
jamesmca_I'm not sure making it an unofficial meeting is going to work for APAC folks. IMO, if you're trying to get them on board, should be an official meeting.14:43
persiatobberydberg: Americas/APAC overlap is about 23:00 UTC, which might be hard for you :)14:43
zhipengtobberydberg I could definitely help with the APAC friendly meetings14:44
tobberydbergThat can be hard for a fresh mind, yes =)14:44
mrhillsman++ jamesmca_ sentiment14:44
tobberydbergI setup a doodle with some suggestions, please add your suggestions to the etherpad!!14:45
tobberydbergagree jamesmca_ ... I also believe an official meeting is for the best14:45
*** sc has joined #openstack-meeting-314:45
tobberydbergI started and added current time slot just for the heck of it14:46
zhipengtobberydberg I'm not sure if you guys have covered these items: (1) we need to send out an official PTG agenda and (2) Thierry's email on post-lunch talk14:47
*** ianychoi has joined #openstack-meeting-314:47
tobberydbergTalked some about it14:48
tobberydbergAdded "Lunch presentation" as the Thierry email topic14:48
tobberydbergAgree, we need to specify times for the different topics. I ealier said that "mornings" will be dedicated PCWG since you are busy afternoons14:49
*** aadams has joined #openstack-meeting-314:50
zhipengPer item (2) I think we could provide 2 slides14:50
zhipengwhat we have covered on Mon (since it will be already lunch)14:51
zhipengand what we will cover on Tuesday14:51
tobberydbergSounds like a plan14:51
tobberydbergWe create that offline? You zhipeng create a start in a google doc and I and everyone that would like to help out join in?14:53
*** yamamoto has quit IRC14:53
*** yamamoto has joined #openstack-meeting-314:54
zhipengtobberydberg no problem14:54
*** yamahata has joined #openstack-meeting-314:54
tobberydbergThanks zhipeng14:54
tobberydberg#action zhipeng created draft of PTG lunch presentation14:54
zhipengbut we need to settle down on the schedule first, then we know what is the outline of the slide :P14:54
tobberydbergchat in publuiccloud at say, 0800 UTC?14:55
tobberydberg5 minutes left .... other topics?14:55
zhipengtobberydberg Chinese new year tmr, so won't be able to make it14:56
zhipengbut maybe later I could do around the same time as today14:56
*** yamamoto has quit IRC14:57
*** yamamoto has joined #openstack-meeting-314:57
tobberydbergok. I have a meeting around that time, but ping me when you are online and we give it a try14:57
tobberydbergAnything else folks?14:57
*** iyamahat has joined #openstack-meeting-314:58
*** kjansson has joined #openstack-meeting-314:58
*** nseyvet_ has joined #openstack-meeting-314:58
pilgrimstackAlison is still here ?14:58
zhipengsure no problem :)14:58
pilgrimstackWe identify some improvment we could do on the web site14:59
pilgrimstackmaybe it's already managed, I don't know as I partially here sorry14:59
tobberydbergRegarding the PP pilgrimstack?14:59
pilgrimstackfor example :15:00
tobberydbergI did include your feedback there as well15:00
pilgrimstack doesn't link back to passport15:00
tobberydbergExactly ++15:00
*** alexchadin has joined #openstack-meeting-315:00
tobberydbergWe are ut of time, but make sure to join that session remotely at the PTG15:00
apriceyep - we are meeting internally this week to review the feedback that tobberydberg sent over and planning to discuss in person at the PTG15:00
tobberydbergThanks for today folks and Happy Valentines Day! ;-)15:00
pilgrimstackgoogle "try openstack" should show the passport program page, what can we do for that ?15:01
pilgrimstackok, it's managed, good ;)15:01
tobberydbergFeel free to contineu the discussoin in #openstacl-publiccloud15:01
*** openstack changes topic to "OpenStack Meetings ||"15:01
jamesmca_pilgrimstack we will work on some SEO strategy around the passport program15:01
openstackMeeting ended Wed Feb 14 15:01:34 2018 UTC.  Information about MeetBot at . (v 0.1.4)15:01
openstackMinutes (text):
*** cbellucci has joined #openstack-meeting-315:02
witek#startmeeting monasca15:02
openstackMeeting started Wed Feb 14 15:02:03 2018 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: monasca)"15:02
openstackThe meeting name has been set to 'monasca'15:02
pilgrimstackok good to know15:02
*** haruki has joined #openstack-meeting-315:02
witekhello everyone15:02
*** pilgrimstack has left #openstack-meeting-315:02
*** coolsvap has joined #openstack-meeting-315:02
witeknice attendance today15:02
witekaadams: can we start with your change?15:03
witek#topic reject old metrics15:03
*** openstack changes topic to "reject old metrics (Meeting topic: monasca)"15:03
*** alexchadin has quit IRC15:03
witekso there was some discussion in review if we should reject at all15:04
aadamsI think we should reject15:04
witekdoes threshold engine has problems with handling measurements out of sync?15:04
aadamsit evaluates alarms based on timestamps15:05
amofakharwhy not rejecting those in threshold engine?15:05
aadamsand if you are receiving metics with wrong timestamps then alarms will be bad too15:05
*** jamesmca_ has quit IRC15:05
*** bobh has joined #openstack-meeting-315:05
aadamsthat is certainly an option, but in the past we have done it in the api15:05
*** jamesmca_ has joined #openstack-meeting-315:06
witekseems indeed like it could be improved in threshold engine15:06
aadamsare there any other questions?15:06
amofakharbecause if it be done in api then we will lose some data which can be useful for other parts15:06
witekbut that is definitely more effort15:06
amofakharand also it makes the api slower15:06
aadamshow does it make the api slower?15:07
nseyvet_How does an old timestamp for a metric generate an alarm?15:07
*** iyamahat has quit IRC15:07
nseyvet_Does not the threshold engine use some time window and rejects events outside of that?15:08
aadamsif a timestamp should be for now but there is an ntp problem, alarms might flip or evaluate wrong15:08
nseyvet_I dont understand15:08
aadamsthe main issue here is timestamps that are wrong15:08
nseyvet_no they are correct15:08
nseyvet_from the agent perspective they are fine15:09
amofakharand in a case if metrics pass the evaluation and come into the queue but threshold is stopped for a reason and it be started again then it will have the same problem as before15:09
nseyvet_there might be network congestion15:09
nseyvet_or those metrics are generated in the future on purpose by a prediction engine for example15:09
nseyvet_so the timestamp is fine15:09
aadamsmy isue is when they are not fine15:09
nseyvet_I dont understand why this timestamp troubles the engine?15:09
aadamsand there is an ntp problem15:09
aadamsbecause alarms are evaluated based on timestamps15:10
nseyvet_but how do u know if it is NTP or network pb?15:10
*** jamesmca_ has quit IRC15:10
aadamsI don't know about your use cases, but furure metrics points to an ntp problem15:10
nseyvet_if alarms are based on timestamps I dont see the pb15:10
nseyvet_I predict 10 min ahead a metric15:11
nseyvet_I push it into Monasca API15:11
nseyvet_perfectly legit use case15:11
aadamswell then, i suppose this patch should not be turned on for you15:11
nseyvet_I still dont understand the pb w timestamps and alarms?15:11
aadamsIn my use case, I do not chage the metric created at timestamp15:11
nseyvet_I dont see much point for this patch at atll IMO15:11
aadamsand do not expect furure timestamps15:11
nseyvet_because of what?15:12
aadamsi do not expect future timestamps because i dont create metrics in the future15:12
aadamsa future timestamp to me is an ntp problem15:12
aadamsthe good news is that if you are expecting furure timestamps, the default behaviour does not change with this patch15:13
aadamsso you will not be effected15:13
nseyvet_There is a large misunderstand here. If the pb is in the threshold engine it should be fixed there.  At this point I dont understand the pb.  And assuming time is off due to NTP is plain wrong15:13
kjanssonwon't this also obfuscate a NTP or similar problems at the agent side? the story says we should make these problems visible and debuggable?15:13
witekI think the key question at the moment is to understand why wrong (out of sync) timestamps are causing problems in threshold15:14
nseyvet_Also, I am wondering when the agent receives a 422, does it re-transmit?15:14
nseyvet_or queue?15:14
aadamswhat would you rather throw?15:15
nseyvet_nothing since it is fine IMO15:15
nseyvet_question 1: what is this solving?15:15
aadamsmetrics with furure timestamps are invalid in my usecase15:15
aadamsi should be able to configure the api to agree with that15:16
*** zhipeng has quit IRC15:16
aadamsi understand, in your use case they are valid, so dont configure it to be on15:16
nseyvet_Should I expand that to assume I may want to reject any metrics that have negative values?15:16
nseyvet_It sounds to me like a filter function15:17
aadamsit is not15:17
aadamsit rejects only invalid metrics as the user defines them15:17
nseyvet_it filter metrics based on timestamp15:17
nseyvet_invalid is in your situation a timestamp in the future or in the past by 2 weeks. yes?15:18
nseyvet_so the pb to solve is how to define "invalid" for a general use case and add it as a general functionality in API IMO15:20
nseyvet_It sounds like a filter15:20
nseyvet_so I may want to filter on negative values for example15:20
nseyvet_or NaN15:20
nseyvet_or etc15:20
nseyvet_or timestamp being old15:20
aadamswhats your point15:20
*** cshastri has quit IRC15:20
nseyvet_I dont think the API is the proper location for that function15:21
aadamsthats valid, i didn't add gereneral filering though\15:21
aadamsI wouldnt put general filtering there either15:21
kjanssonbut specific filtering? and if some other use case requires another specific filter?15:23
*** lpetrut has quit IRC15:23
aadamswell i suppose the conversaition should be what is a filter and what is simple invalid then?15:23
aadamsbecause I am hearing two very different points of view here15:24
witekaadams: what behaviour do you have now with old metrics being sent?15:25
witekin thresh15:25
aadamsold alarms aren't as problematic to me as future alarms, because caching is expected, but a two week old metric that is only 2 weeks old because of an NTP problem is bad for my system15:26
witekand for future measurements?15:27
aadamsagain, alarms won't be evaluated correctly, and the NTP problem is hidden15:27
nseyvet_Let me see if I understand, a timestamp 2 weeks in the past is an NTP problem?15:28
witekbecause thresh evaluates on window (now - 1 min. -> now) ?15:28
aadamsI am not exactly sure on the math the thresh does but yes, i assume so15:29
witekso the alarm state would correspond to the actual alarm state in the past15:29
nseyvet_The only way to detect that there is an NTP pb would be compare the state of a specific agent vs others, calculate a deviation and etc.15:30
*** alexchadin has joined #openstack-meeting-315:30
nseyvet_any network congestion can slow down packets for minutes15:30
*** hongbin has joined #openstack-meeting-315:31
sgrasley1What is the NTP Check used for if it does not tell you about NTP problems?15:32
*** VW has joined #openstack-meeting-315:32
aadamsThat is a good question15:32
*** dklyle has joined #openstack-meeting-315:33
*** tellesnobrega has quit IRC15:33
*** david-lyle has quit IRC15:33
*** slaweq has joined #openstack-meeting-315:34
amofakharyou said having it in thresh is an option, would you please tell us what was the reason and benefits of choosing API for it?15:34
witekyes, if it's all about NTP problems, it could be better approach to monitor the time offset on agent node15:34
aadamsMostly time, and parity to the java implementation15:35
aadamswe already have this implemented with out configurability in the java api15:35
*** julim has quit IRC15:36
witekso, do we get to decisions?15:37
aadamsim not sure, did we decide that this needs to be implemented elsewhere?15:38
*** slaweq has quit IRC15:38
witekno, we could think of having it in thresh, but that's definitely more work15:39
aadamsI have already spent too much time on this bug15:39
witekaadams: is this feature urgent for you?15:40
aadamsIm affraid I wont get permission to do a deeper fix15:40
*** jamesmca_ has joined #openstack-meeting-315:40
aadamsWe can work around, but we have already seen this problem once on a customer environment and are a little affraid of dectecting it in the future15:40
witekI would suggest to discuss it again during the PTG if it can wait until then15:41
witeknseyvet_: ?15:42
aadamsalthough Im affraid I can't do any thresh work, so that fix might be just an open storyboard15:42
*** julim has joined #openstack-meeting-315:42
amofakharYes -> PTG15:43
aadamsOk, thanks everybody!15:43
witekok, let's discuss it again then15:43
witekthanks aadams15:43
nseyvet_What are the documentation describing the threshold engine computations?15:43
amofakharthank you aadams15:43
nseyvet_yes thanks aadams15:43
witeknseyvet_: I think craigbr is the best to ask15:44
witek#topic tempest tests15:44
*** openstack changes topic to "tempest tests (Meeting topic: monasca)"15:44
witekI was going through bugs related to tempest tests15:45
witekwanted to ask about this one:!/story/200130915:45
*** caboucha has joined #openstack-meeting-315:45
witekhaven't seen it for a while now15:46
witekis it fixed?15:46
witekjamesgu: it's yours15:46
jamesguI ma havin gtrouble opening the story board15:47
jamesguah yes... let me close it15:47
witekcool, thanks15:47
witekthanks to craigbr tip we have added some waits in other two test15:48
witekwhich seems to fix occasional failures in CI jobs15:48
witekI'm adding Depends-On tag on changes which fail15:49
witekto see if the fix helps15:49
witek#topic Ceilosca update15:50
*** openstack changes topic to "Ceilosca update (Meeting topic: monasca)"15:50
witekAshwin has provided new path for monasca-ceilometer project15:50
witekcan someone report on the current state of the master branch?15:51
*** haruki has quit IRC15:51
witekjoadavis is not around?15:51
witekpeschk_l has also pushed two small changes for Ceilosca15:52
witekhe works for CloudKitty project15:53
witekhe proposed the presentation about integration with Monasca for the next Summit15:54
*** cbellucci has quit IRC15:54
witekwith cbellucci15:54
*** aagate has joined #openstack-meeting-315:54
witekhi aagate15:54
aagatehi witek15:55
witekI've seen your recent change in monasca-ceilometer15:55
witekcould you give an update about the current state?15:55
witekis it now in sync with current Ceilometer code?15:58
aagateyes sure. We have made changes to monasca-ceilometer master so that it works with latest ceilometer master. Had to remove dependency within monasca-ceilometer on oslo config that was major change.15:58
witekis there still some work remaining?15:58
aagateAlso monasca-ceilometer stable/pike now also works  with ceilometer stable/pike15:59
witekthanks, I have to finish soon15:59
witekone more announcement16:00
aagateThere is still some work to do to make sure devstack plugin in monasca-ceilometer still functions as before. But as far as getting code uptospeed with ceilometer its done16:00
witekMonasca has gained the diverse-affiliation tag16:00
witekthanks everyone for your contribution16:00
witekit's based on review stats16:01
witekthat's alll16:01
witekthank you for today16:01
witekbye bye16:01
*** openstack changes topic to "OpenStack Meetings ||"16:01
openstackMeeting ended Wed Feb 14 16:01:33 2018 UTC.  Information about MeetBot at . (v 0.1.4)16:01
openstackMinutes (text):
*** alexchadin has quit IRC16:02
*** amofakhar has quit IRC16:06
*** aadams has quit IRC16:11
*** pcaruana has quit IRC16:13
*** yamamoto has quit IRC16:13
*** yamamoto has joined #openstack-meeting-316:27
*** belmoreira has quit IRC16:28
*** psachin has quit IRC16:29
*** yamamoto has quit IRC16:31
*** slaweq has joined #openstack-meeting-316:34
*** iyamahat has joined #openstack-meeting-316:35
*** tssurya has quit IRC16:39
*** slaweq has quit IRC16:39
*** alexchadin has joined #openstack-meeting-316:40
*** tssurya has joined #openstack-meeting-316:42
*** krtaylor has joined #openstack-meeting-316:43
*** e0ne has quit IRC16:43
*** alexchadin has quit IRC16:44
*** tellesnobrega has joined #openstack-meeting-316:48
*** tssurya has quit IRC16:51
*** marios has quit IRC16:55
*** rmcall has quit IRC16:58
*** slaweq_ has joined #openstack-meeting-317:00
*** lpetrut has joined #openstack-meeting-317:03
*** rmcall has joined #openstack-meeting-317:03
*** slaweq_ has quit IRC17:05
*** rmcall has quit IRC17:08
*** VW has quit IRC17:09
*** VW has joined #openstack-meeting-317:10
*** chyka has joined #openstack-meeting-317:12
*** yamamoto has joined #openstack-meeting-317:12
*** VW has quit IRC17:15
*** diablo_rojo has joined #openstack-meeting-317:15
*** VW has joined #openstack-meeting-317:16
*** alexchadin has joined #openstack-meeting-317:16
*** pcaruana has joined #openstack-meeting-317:17
*** yamamoto has quit IRC17:17
*** slaweq has joined #openstack-meeting-317:22
*** iyamahat has quit IRC17:23
*** tssurya has joined #openstack-meeting-317:24
*** tssurya has quit IRC17:27
*** yamahata has quit IRC17:31
*** jamesmcarthur has quit IRC17:40
*** MarkBaker has joined #openstack-meeting-317:41
*** armstrong has quit IRC17:42
*** jamesmca_ has quit IRC17:46
*** iyamahat has joined #openstack-meeting-317:46
*** jamesmcarthur has joined #openstack-meeting-317:46
*** jamesmcarthur has joined #openstack-meeting-317:47
*** lpetrut has quit IRC17:48
*** alexchadin has quit IRC17:50
*** rmcall has joined #openstack-meeting-317:56
*** lpetrut has joined #openstack-meeting-317:56
*** sambetts is now known as sambetts|afk17:56
*** jamesmcarthur has quit IRC18:00
*** jamesmcarthur has joined #openstack-meeting-318:00
*** sc has left #openstack-meeting-318:01
*** yamahata has joined #openstack-meeting-318:07
*** aagate has quit IRC18:23
*** sgrasley1 has quit IRC18:24
*** psachin has joined #openstack-meeting-318:26
*** yamamoto has joined #openstack-meeting-318:27
*** alexchadin has joined #openstack-meeting-318:32
*** yamamoto has quit IRC18:32
*** alexchadin has quit IRC18:36
*** VW has quit IRC18:36
*** VW has joined #openstack-meeting-318:37
*** VW has quit IRC18:41
*** VW has joined #openstack-meeting-318:42
*** e0ne has joined #openstack-meeting-318:52
*** yamamoto has joined #openstack-meeting-318:52
*** yamamoto has quit IRC18:52
*** bobh has quit IRC18:58
*** alexchadin has joined #openstack-meeting-319:07
*** lpetrut has quit IRC19:10
*** harlowja has joined #openstack-meeting-319:21
*** aagate has joined #openstack-meeting-319:24
*** MarkBaker has quit IRC19:25
*** aagate has left #openstack-meeting-319:31
*** dklyle has quit IRC19:33
*** bobh has joined #openstack-meeting-319:38
*** alexchadin has quit IRC19:39
*** coolsvap has quit IRC19:41
*** yamamoto has joined #openstack-meeting-319:53
*** rdopiera has joined #openstack-meeting-319:59
ying_zuo#startmeeting horizon20:00
openstackMeeting started Wed Feb 14 20:00:23 2018 UTC and is due to finish in 60 minutes.  The chair is ying_zuo. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
ying_zuoHi everyone o/20:00
ying_zuoHappy Valentine’s Day :)20:01
ying_zuo#topic Queens-RC2 release next week20:02
*** openstack changes topic to "Queens-RC2 release next week (Meeting topic: horizon)"20:02
ying_zuothat will be the final release candidate for Horizon Queens20:02
ying_zuothanks everyone for your contribution during this cycle :)20:02
*** yamamoto has quit IRC20:02
ying_zuo#topic Open Discussion20:03
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:03
e0neany thought about removing nose from horizon?20:05
e0neit's not a big deal for us, but it could affect plugins20:05
ying_zuois it causing any problems?20:06
e0neoriginally, I looked at selenium job20:06
e0nefor now, it passes almost every time but it's totally broken20:07
e0newe don't see any errors because of nose bug #link
e0nethat's why I started nose removal20:07
ying_zuooh, do you know why it's not reporting the errors?20:07
ying_zuoI see20:09
rdopierae0ne: can't plugins install nose when they need it themselves?20:09
e0nerdopiera: I hope they do it20:09
rdopierae0ne: if not, that's a bug20:09
e0neI'll send a mail to openstack-dev, once my patch will be ready20:09
rdopierathat's for Rocky, right?20:10
ying_zuoright now the changes will be in Rocky by default20:10
ying_zuounless we cherry pick them to stable/queens20:11
e0nethere are some issues with our tests and django test runner #link
e0nebut I figuread out why it's happening and fixing it20:11
e0neI didn't submit a blueprint yet20:12
e0newill do it a bit later20:12
*** david-lyle has joined #openstack-meeting-320:12
ying_zuocool. thanks20:12
e0nebtw, here is my test patch for seleium job #link
e0ne#link - WIP. Use default django test runner instead of nose20:14
ying_zuoat least it's showing the tests failed20:18
*** alexchadin has joined #openstack-meeting-320:21
ying_zuointeresting it doesn't show the same errors as in other reviews20:21
e0neyes, we've got some issues with out unit tests20:22
e0nesome time, it's depend on execution order:(20:22
ying_zuoyes, the tests pass on some reviews20:23
ying_zuoI wonder if we need to manually check the test results before merging the code now20:24
ying_zuobut the errors may not be caused by the changes on the reviews20:24
*** alexchadin has quit IRC20:25
ying_zuobut I think we should check the unit test results before merging now20:25
e0neI almost completed patch to fix this issue20:26
e0neit will be ready this week20:26
ying_zuothank you20:26
ying_zuoanything else to discuss?20:27
e0nenothing from me20:27
ying_zuothanks everyone for joining20:29
ying_zuoenjoy the rest of your day20:29
*** openstack changes topic to "OpenStack Meetings ||"20:29
openstackMeeting ended Wed Feb 14 20:29:22 2018 UTC.  Information about MeetBot at . (v 0.1.4)20:29
e0nesee you next week20:29
openstackMinutes (text):
*** jamesmcarthur has quit IRC21:05
*** psachin has quit IRC21:12
*** VW has quit IRC21:16
*** VW has joined #openstack-meeting-321:16
*** julim has quit IRC21:17
*** slaweq has quit IRC21:18
*** pcaruana has quit IRC21:28
*** raildo has quit IRC21:42
*** sgrasley1 has joined #openstack-meeting-321:45
*** MarkBaker has joined #openstack-meeting-321:48
*** caboucha has quit IRC21:59
*** julim has joined #openstack-meeting-322:02
*** slaweq has joined #openstack-meeting-322:04
*** rmcall has quit IRC22:05
*** julim has quit IRC22:05
*** slaweq has quit IRC22:11
*** julim has joined #openstack-meeting-322:13
*** bobh has quit IRC22:17
*** VW_ has joined #openstack-meeting-322:34
*** VW has quit IRC22:38
*** VW_ has quit IRC22:39
*** abalutoiu_ has joined #openstack-meeting-322:49
*** sgrasley1 has quit IRC22:49
*** abalutoiu has quit IRC22:51
*** sgrasley1 has joined #openstack-meeting-322:52
*** hongbin has quit IRC23:06
*** e0ne has quit IRC23:36
*** jamesmcarthur has joined #openstack-meeting-323:48
*** sgrasley1 has quit IRC23:53
*** jamesmcarthur has quit IRC23:53

Generated by 2.15.3 by Marius Gedminas - find it at!