15:00:19 #startmeeting ceilometer 15:00:19 Meeting started Thu Jul 10 15:00:19 2014 UTC and is due to finish in 60 minutes. The chair is eglynn. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:24 The meeting name has been set to 'ceilometer' 15:00:27 o/ 15:00:31 o/ 15:00:46 o/ 15:00:48 o/ 15:00:58 o/ 15:01:13 hey guys o/ 15:01:21 hola 15:01:31 o/ 15:01:48 hey y'all! 15:01:53 #topic Juno-2 status 15:02:04 #link https://launchpad.net/ceilometer/+milestone/juno-2 15:02:16 my dispatcher BP for Gnocchi is under approval 15:02:30 ildikov: internal appro? 15:02:35 o/ 15:02:38 unfortunately it is the holiday season of the Swedish guys 15:02:46 eglynn: yes, of course... 15:03:03 LOL ... it's always holiday seaon in Sweden ;) 15:03:12 internal appro? that sounds weird :) 15:03:15 so some delay is possible, but I'm really trying to push this through, only the last step is missing 15:03:28 * eglynn should up sticks and move to Sweden for all the holidays ... 15:03:43 eglynn: yes it is but, now really noone is available there... 15:04:06 eglynn: if you like that ugly weather, then totally worth to move ;) 15:04:22 jd__: thanks for sharing my pain ;) 15:04:24 dear core-team, that's j2 and it needs review :) https://blueprints.launchpad.net/ceilometer/+spec/mongodb-events-feature 15:04:31 I reckon progress on "consume notifications from ironic" has gone from slow to maybe "good" 15:04:43 jd__: yeah it does to such finely-tuned opensource ears as our own ;) 15:04:48 DinaBelova: sure, on my endless list, no worries 15:04:49 cdent: cool 15:04:55 * jd__ nods 15:04:56 ildikov, :D 15:05:05 needs docs and validation of some of the names used 15:05:31 cdent: I've just updated 15:05:46 ✓ 15:05:59 eglynn: BTW the docco status is not that good, I guess I will not sleep much until the j2 deadline... 15:06:09 OK so at this point it would be great to have a heads-up if anyone's worried about slippage 15:06:13 just a reminder, if core reviewers can review my pending spec , I can try getting them partially in for juno-2 15:06:20 specs* 15:06:37 ildikov: can we divide and conquer on some of the docs work? 15:06:48 prad: yep, apols for being remiss on that 15:07:14 maybe if there is anyone who's willing to write some admin guide sections 15:07:17 np, just wanted those in asap so i can implement those soon 15:07:42 llu-laptop: do you think that any of the SNMP stuff is targetable to juno-2? 15:08:04 eglynn, may we set the https://bugs.launchpad.net/ceilometer/+bug/1330989 to some importance? 15:08:05 Launchpad bug 1330989 in ceilometer "[Hbase] Source filter doesn't work with _get_columns" [Undecided,In progress] 15:08:05 I'll try my best, but it's risky 15:08:21 eglynn, it's still undecided :( 15:08:25 eglynn: I'm not 100% sure how much it would be consistent, I mean the terms we use, how to describe things, etc, so I mean the best is to have the whole text from one author 15:08:36 llu-laptop: great, we can always bump it off to juno-3 if it doesn't make it 15:08:52 eglynn: anyway, I will scream, if I've reached that point 15:09:01 DinaBelova: what importance do you suggest? 15:09:14 eglynn, medium I guess 15:09:17 ildikov: what format is the docco in, docbook? 15:09:32 * eglynn makes it so ... 15:09:37 eglynn: yeah. i've started though I'm not sure if lsomla is satisfied with the spec or not 15:09:52 eglynn: I guess, XML-based 15:10:04 llu-laptop: lsmola is out on vacation for this week and next 15:10:10 eglynn, thank you sir :) 15:10:16 eglynn: we can discuss the status mid-next-week 15:10:21 llu-laptop: ... then he's off at EuroPython for another week 15:10:46 llu-laptop: ... so I think you should prolly just go ahead without his explicit appro 15:10:55 eglynn, ok i'll start first, assuming he won't come back with big suprise for me. :) 15:10:57 ildikov: cool 15:11:02 eglynn: and then decide if I need more hands or not 15:11:10 llu-laptop: thank you sir! 15:11:32 ildikov: cool, if needs be I can try helping get that over the line 15:11:32 ildikov, btw, let's do some polling-tempest fight tomorrow :) 15:11:44 ildikov, how do you look on that? 15:11:46 DinaBelova: ok, tomorrow is fine 15:11:50 ildikov: I'd be intrested in helping some on the docs side of things if that's an option. 15:11:52 ildikov, cool, +1 15:12:02 cdent: cool, thank you sir! 15:12:10 * jd__ smiled 'cause he reads 'pillow-tempest fight' 15:12:14 DinaBelova: at what time is Sean available? 15:12:38 ildikov, about 6-7PM Moscow time he begins being here 15:12:52 ildikov, so smth like this :) 15:13:12 cdent: cool, thanks, I will see, how it could work, if I cannot make any good progress with it in the next very few days 15:13:16 ildikov, that's about 3-4UTC 15:13:27 DinaBelova: ok, cool, it's not that late :) 15:13:35 ildikov, indeed :) 15:13:49 sorry for the offtopic, please continue, folks :) 15:13:53 DinaBelova: ping e tomorrow if you think it's time to fight ;) 15:14:00 ildikov, np 15:14:03 so if anyone else has a juno BP that they're sitting on, please try to get the specs proposed by tmrw if at all possible 15:14:17 ... even just a rough placeholder 15:14:49 anything else WRT juno-2? 15:15:17 just confirmation that the javelin stuff has seen no recent progress, will poke at people early next week 15:15:28 cdent: thanks 15:15:42 ok, moving on I guess ... 15:15:49 #topic TSDaaS/gnocchi status 15:15:56 jd__: anything to report? 15:16:16 jd__: I owe you a unit test I believe 15:16:19 I've been implementing the aggregation stuff discussed last week during the sprint 15:16:34 eglynn: yeah that would be really helpful, and thanks for testing btw 15:16:51 I've been working today on some new shiny features in the indexer 15:17:00 so things are progressing :) 15:17:05 BTW, I couldn't figure out why MySQL is not working on the gate 15:17:15 and I'm waiting for ildikov and her internal team :D wrt ceilometer integration 15:17:28 ildikov: I missed that I guess? 15:17:31 jd__: ... up to now I've just been using a little shell script to hit the API, need to translate that to an in-tree test 15:17:33 * DinaBelova working on the opentsdb driver for gnocchi. I believe it'll help to find what shall we do with the api and common classes to be abstract and good enough for three different backends :) 15:17:44 cool DinaBelova 15:17:50 jd__: you can tell it my managers too, if you wish ;) 15:18:00 ildikov, lol :D 15:18:13 DinaBelova: what do the data retention semantics look like for opentsdb? 15:18:31 eglynn, /me still in progress here 15:18:39 jd__: with the socket included in the URL it cannot connect, otherwise it has authentication problems and locally I have a third issue with the tests with MySQL 15:18:40 DinaBelova: ... i.e. the equivalent of the stuff we were talking to pauldix about last week for influx 15:18:46 DinaBelova: ... a-ha, cool 15:18:53 eglynn, yes, I keep that in mind 15:19:06 jd__: more details: https://review.openstack.org/#/c/104966/ 15:19:11 ildikov: I though the gate was passing? I'll take a look 15:19:44 jd__: it passed, because all the tests were skipped, because there wasn't any working MySQL connection 15:20:02 jd__: just for simplicity, would it be easy to have the tests run in-tree against sqlite for the indexer driver? 15:20:19 jd__: anyway, I just wanted to have more eyes on it, as I got distracted much this week, so I didn't have enough time to deal with it 15:20:28 eglynn: sqlite does not support foreignkey so it's not working with Gnocchi as we need that 15:20:42 jd__: a-ha k, scratch that so 15:20:44 so I just dropped the support for it since it's not really worth it 15:21:11 ildikov: I just saw that, my bad I sucked missing that 15:21:13 jd__: with MySQL I got AttributeError for with_for_update... 15:21:22 sqlite3.something has foreign keys... 15:21:24 ildikov: ok I'll fix that 15:21:30 cdent: so I heard 15:21:45 cdent: but still not really convinced my effort is going onto that direction anytime soon :D 15:21:45 jd__: np, if you have time, please check, I will be too busy to fix it this week for sure 15:21:53 jd__: cool, thanks 15:22:52 anything else on gnocchi? 15:23:09 eglynn, I guess that's it :) 15:23:18 #topic Mid-cycle wrap-up 15:23:43 it was fun and productive I think :) 15:23:52 jd__: thanks for the hospitality! 15:24:02 eglynn, and that amazing french bakery... mmmm 15:24:02 you're welcome, it was fun having you guys! 15:24:11 eglynn: +1 15:24:21 I want more mid-cycles ;) 15:24:32 ildikov, hehe :D 15:24:32 mid-mid-cycle 15:24:42 1/6th-cycle every month 15:24:58 yeah, do folks feel it's something we should aim to do again for Kilo/Kyoto? 15:24:58 jd__: thanks much, everything was really good! 15:24:58 all logs are at https://etherpad.openstack.org/p/paris-July2014-ceilometer-sprint? 15:25:07 eglynn: likely 15:25:16 llu-laptop: yeah, they're a little rough TBH 15:25:19 llu-laptop, and in the links published there 15:25:46 llu-laptop: ... may not be very coherent, need to be read *cough* forensically 15:27:02 k, Paris was fun, but back to reality ... :) 15:27:08 #topic "The continuing saga of branchless Tempest" 15:27:36 ohhh 15:27:49 eglynn: I've just read your yesterday's discussion with Joe about the notifications 15:27:51 so this discussion started up with vrovachev's featureful backport of the cinder snapshot notification support 15:28:18 I then raised it at the PTLs meeting which led to a long inconclusive discussion 15:28:25 ... which we then punted to the ML 15:28:28 http://lists.openstack.org/pipermail/openstack-dev/2014-July/039733.html 15:28:48 and as ildikov says, continued on IRC with jogo last night 15:29:13 so there are several interleaved threads of thought and lines of reasoning 15:29:19 this mailing thread is growing with each minute :( 15:29:35 eglynn: is there any chance to have a freeze and then very slowly move to one direction with notifications? 15:29:51 eglynn: just like what we were talking about on the mid-cycle 15:29:59 but in the short term ... seems that Matt is accepting of a test-skipping decorator based on static (i.e. non-discoverable) tempest config 15:30:13 ildikov: a freeze? 15:30:35 I want to eliminate -1 in Jenkins using api ceilometer(capabilities:storage:production_ready) 15:31:15 vrovachev: "eliminate -1 in Jenkins" ==> is that causing CI failures? 15:31:34 eglynn: yes 15:31:48 eglynn, in grenade job afair 15:31:57 eglynn: I just meant that somehow we need to deal with the changing style of notifications and I guess there was a point in your discussion to have a state and versioning, etc 15:32:00 DinaBelova: yes :) 15:32:23 vrovachev: can you explain the background? ... what changes do we need to avoid that failure? 15:33:52 ildikov: yep, if the other projects step up to actually versioning notifications, then that change would impact on consumers such as ourselves and StackTach 15:33:57 grenade job runned tempest in master branch for stable icehouse devstack. I can to add skip test, if get API request to apabilities:storage:production_ready is False 15:34:05 ildikov: ... but it would be to our benefit, right? 15:34:44 vrovachev: a-ha, so the same skipping logic as you already put into the main devstack job? 15:34:51 eglynn: yeap, smth like that 15:35:04 eglynn: yes 15:35:19 ildikov: k, I just didn't get the freeze reference ... i.e. what was being frozen 15:35:22 eglynn, yes, smth like that - that was fixed by the branches in devstack, but here it's an other situation 15:35:34 a little bit 15:35:41 vrovachev, DinaBelova: ok 15:35:43 eglynn: I still think that it would be much easier to have a some kind of stardized format in the *long-term* future, but still, we have to start at somewhere to even deal with this issue 15:35:57 although, it might be fixed with the API specs endpoint I've done for the ceilo that time 15:36:02 vrovachev: ... so on the cinder tests 15:36:05 ildikov: that's basically the same as what I just posted to the thread 15:36:26 eglynn: yes, on snapshot notification 15:36:30 vrovachev: ... does it Matt's proposed "@test.consumed_notifications('volumes', 'snapshot.exists', 'snapshot.create.*', ...)" style of decorator make sense to you? 15:36:44 on volume notification all ok :) 15:36:58 cdent: I'm trying to give this hint to people around for a few months now..., unfortunately it's not that easy as it sounds... :( 15:37:00 vrovachev: ... i.e. as described in http://lists.openstack.org/pipermail/openstack-dev/2014-July/039819.html 15:37:06 eglynn, I guess it'll look nice - esp. if QA is ok with it 15:37:19 DinaBelova: +1 15:37:35 DinaBelova: it sounds like they are, as Matt has given his blessings 15:37:43 eglynn, yes, indeed 15:38:02 vrovachev: so is that something you could implement so as to avoid the need for the cinder snapshot backport 15:38:04 ? 15:38:29 I think that'll work ok, although I'm still interested how to implement that in tempest, as I'm not the specialist. vrovachev - will it be ok for you? 15:39:35 eglynn: I will discuss code style (implemented decorator or skip in test) with Sean and Matthew. Yes, this can avoid the need for the cinder snapshot backport 15:39:49 vrovachev: excellent! 15:40:01 yay :) 15:40:13 :) 15:40:38 vrovachev: ... so with that skipping approach agreed, is it realistic do you think to get the stalled tempest tests landed for juno-2? 15:41:04 for cinder and swift - juno 2 15:41:10 for glance - juno 1 15:41:37 vrovachev: juno 1 ... do you mean, already landed? 15:41:53 eglynn, also scenario tests (events, alarms) are in progress for j2 15:42:05 oh, no, for nova - juno 1 :) 15:42:21 eglynn, for nova they're landed 15:43:01 for glance juni 2 also 15:43:10 juno_ 15:43:33 DinaBelova, vrovachev: excellent, so it would really geat to be able to declare victory on the TC gap for tempest in juno-2 :) 15:43:46 eglynn, /we are in progress :D 15:43:51 the other thing WRT testing is ... 15:44:00 did folks read Sean's magnum opus on that thread? ... http://lists.openstack.org/pipermail/openstack-dev/2014-July/039733.html 15:44:33 eglynn, indeed :D 15:44:55 it is a nice story :) 15:45:07 particularly the "New Thinking about our validation layers" section 15:45:24 oh, yes... 15:45:39 ... so it seems the wind is blowing somewhat towards in-tree functional tests outside of tempest 15:45:46 thank god for that 15:45:52 ... just wondered what folks thought of that idea? 15:46:34 cdent approves? 15:46:50 eglynn, I just wonder how difficult it'll be to be done 15:47:22 as tempest is now big, but more or less known thing - I wonder how this might look like outside the tempest 15:47:23 In general I prefer maximizing tests in-tree 15:47:37 'in-tree functional tests outside of tempest' this Sean's idea , I'm not thinking, good or bad this 15:47:55 cdent: in ceilo's case, would it end up being effectively a mini-Tempest? 15:48:27 cdent: ... i.e. can we really system-test ceilo in isolation in a meaningful way? 15:48:37 certainly some of it 15:48:38 I think, functional and integrative test outside the tempest it's bad idea 15:48:58 we already require a light mongo for some tests, yes? 15:48:58 _integrated tests 15:49:11 and things like wsgi-intercept can be used for more end2end api tests 15:50:00 so I'm a bit nervous that we'd end up with a bunch of fragmented, diverging, duplicated efforts to build mini-Tempests for each project 15:50:12 ... to do stuff that maxi-Tempest could do prior to the advent of branchless 15:50:29 eglynn, +1 15:50:38 well presumably maxi-tempest is inter-project and ceilo's mini-tempest is intra-project? 15:50:47 check the notifications in tempest very well, because we always know not lost any connection with any project. 15:51:00 for pollsters also 15:51:11 vrovachev, pollsters is other story :D 15:51:20 oh... 15:51:21 cdent: yep, and mini-tempest is whitebox, versus maxi-tempest "kinda" blackbox 15:51:23 we need to persuade that it's needed :D 15:52:54 ok, so I'd encourage folks with strong opinions either one way or the other to chime in on that thread 15:53:33 eglynn: of course 15:53:49 ... I suspect we'll end up with much discussion about this in-tree functional testing idea next time we're in Paris 15:54:05 (if it doesn't come to the fore even earlier than that) 15:54:17 ok, let's move on ... 15:54:25 I'm not undertanding why it is a bad thing on any dimension? Can someone explain that to me out of band? 15:54:33 #topic Eventlet to asynchio switch-over 15:55:21 just a heads up something that markmc, victor stinner & flaper87 discussed at length at the mid-cycle last week 15:55:27 http://lists.openstack.org/pipermail/openstack-dev/2014-July/039291.html 15:55:40 when is the switch-over required to complete? juno? 15:56:11 tl;dr: deprecate eventlet in baby steps, replace piecewise with backport of py3 asyncio (trollius), use ceilo as the guinea pig 15:56:35 llu-laptop: ... well I was thinking it would have to be a multi-cycle effort 15:56:45 llu-laptop: ... maybe the first steps by end of juno 15:57:10 eglynn: relieved to hear this. 15:57:31 ... but there's a few potential pifalls raised on that thread, sql-a coexistence with asyncio for example 15:57:56 ... so still a topic of live discussion, worth keeping at eye on 15:58:11 there's another related thread on the sql-a 15:58:36 * eglynn doesn't pretend to understand all the subtleties being raised on the ML, but good have it aired in any case and addressed by the domain experts 15:58:47 k, running out of time here 15:58:52 cdent: what's he link to the sql-a thread? 15:58:58 one sec 15:59:30 #topic open discussion 15:59:46 ... while cdent is digging for that link 16:00:03 http://lists.openstack.org/pipermail/openstack-dev/2014-July/039716.html 16:00:09 cdent: thx 16:00:29 it's only part of the puzzle, but some people are like "zomg, nightmare" and others are "NBD" 16:01:15 NBD == no big deal? 16:01:43 presumably so 16:01:56 if anyone's interested, /me was telling lies about Juno again 16:02:01 ... https://plus.google.com/events/c6e8vjjn8klrf78ruhkr95j4tas 16:02:14 any got anything else? 16:02:22 ... we're at minus 2 mins ;) 16:02:31 k, let's call it a wrap 16:02:38 thanks folks! 16:02:42 #endmeeting