15:00:41 <eglynn> #startmeeting ceilometer
15:00:41 <openstack> Meeting started Thu Sep  4 15:00:41 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:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:46 <openstack> The meeting name has been set to 'ceilometer'
15:00:46 <nsaje> o/
15:00:51 <DinaBelova> o/
15:00:51 <dhellmann> o/
15:00:54 <fabiog_> o/
15:00:54 <llu-laptop> o/
15:01:08 <eglynn> hey folks!
15:01:12 <eglynn> #topic Juno-3 status and FFEs
15:01:23 <eglynn> #link https://launchpad.net/ceilometer/+milestone/juno-3
15:01:37 <eglynn> so kudos to everyone who got their patches landed
15:01:55 <eglynn> the gate rush was pretty extreme this time round
15:02:06 <nealph_> o/
15:02:19 <_nadya_> o/
15:02:19 <DinaBelova> eglynn, as usual..
15:02:26 <DinaBelova> _nadya_, good evening :)
15:02:31 <eglynn> that effectively pushing the de facto milestone deadline a day or two earlier
15:02:37 <cdent> o/
15:02:42 <ddieterly> o/
15:03:11 <eglynn> so I discussed FFEs with our release manager earlier
15:03:24 <eglynn> here's the gist of what we agreed ...
15:03:51 <eglynn> nealph_: paas-event-format-for-ceilometer gets a pass by default as it documentation only
15:04:30 <eglynn> nealph_: do you feel this can be closed out and landed by next week?
15:04:47 <nealph_> eglynn: new patches up this morning (US)
15:04:53 <nealph_> so, yes.
15:05:10 <nealph_> Barring any resistence from the PaaS service folks.
15:05:21 <eglynn> nealph_: cool, let's try to get that landed by early/mid- next week so
15:05:56 <nealph_> eglynn: will do!
15:06:01 <eglynn> nealph_: thanks!
15:06:19 <gordc> o/
15:06:31 <eglynn> moving onto the next FFE
15:06:40 <eglynn> gordc's bigger-data-sql has been granted one week of grace-time to reconcile the different performance test results seen on different mysql versions etc
15:06:56 <eglynn> ... and to combine patches to minimize migrations etc.
15:07:04 <eglynn> gordc: does that sounds sufficient?
15:07:17 <gordc> eglynn: cool. i'll keep an eye on it.
15:07:25 <gordc> eglynn: just hoping gate holds up
15:07:42 <eglynn> gordc: (context is there was resistence to granting a longer extension given the possiblity for introducing regressions)
15:08:13 <eglynn> gordc: yeah I hope that the gate latency will go down a lot, now that we're over the juno-3 hump
15:08:52 <eglynn> gordc: presumably we're including in the sql-a ORM->core switch as well as the schema changes in that BP?
15:09:21 <gordc> eglynn: i think it might help given ilya's results...
15:09:52 <eglynn> yeah, the test results reported by DinaBelova and Ilya do sound promising
15:09:52 <gordc> eglynn: we can re-evaluate if necessary... ie. worse case is a 10% performance bump
15:10:03 <DinaBelova> gordc, eglynn - yeah - Ilya had to go afk right now
15:10:09 <DinaBelova> but he started mysql upgrade
15:10:12 <eglynn> cool
15:10:16 <DinaBelova> on the nodes of the lab
15:10:41 <DinaBelova> so he'll continue the tests
15:10:50 <eglynn> so this one is extra important because it's on the TC radar
15:10:57 <eglynn> (via the gapa analysis)
15:11:12 <DinaBelova> eglynn, yes, we keeep track on this for sure
15:11:20 <eglynn> so bigger-data-sql is definitely the highest priority RC1 task for the team
15:11:23 <eglynn> cool, thanks!
15:11:57 <eglynn> k, moving on to the last FFE
15:12:34 <eglynn> dunno if Edwin is around, but his impi-support BP will also get a week or so in grace-time
15:12:49 <llu-laptop> Edwin is not here, but I can pass the info to him tomorrow
15:13:09 <eglynn> so we can sort out the issues around aggregation of sensor-specific and system-wide aggregated data
15:13:13 <llu-laptop> I saw he just posted all the patches https://review.openstack.org/#/q/project:openstack/ceilometer+topic:bp/ipmi-support,n,z
15:13:51 <eglynn> and also get clarity on the behavior on non-Intel/nodemanager hosts
15:13:56 <eglynn> llu-laptop: cool, thanks!
15:14:33 <eglynn> llu-laptop: BTW do you know Edwin's IRC nick? ... I don't think I've seen him on the channel
15:15:05 <llu-laptop> sorry, don't know either :)
15:15:11 <eglynn> k
15:15:14 <llu-laptop> i'll ask him tomorrow
15:15:19 <eglynn> cool, thanks!
15:15:36 <gordc> eglynn: i've just been emailing.. been pretty responsive (aside from time zone diff)
15:15:57 <eglynn> gordc: yeah +1, I've done the same
15:16:04 <eglynn> other than that, we still have a lot of bugs on the RC1 slate
15:16:10 <eglynn> #link https://launchpad.net/ceilometer/+milestone/juno-rc1
15:16:52 <eglynn> so I'll need to cull that bug list early next week to remove anything that isn't getting review traction
15:17:26 <eglynn> anything else on juno-3?
15:17:31 <DinaBelova> eglynn, about "Central agent pollsters not using discovery mechanism" bug
15:17:42 <DinaBelova> I took a look on the final version this morning
15:17:51 <llu-laptop> #link https://bugs.launchpad.net/bugs/1364352
15:17:52 <uvirtbot> Launchpad bug 1364352 in ceilometer "Central agent pollsters not using discovery mechanism" [High,In progress]
15:18:03 <DinaBelova> ir seems to work okay with multinode devstack, multiple central agents, etc
15:18:26 <DinaBelova> so /me hopes to see it soon in the repo :
15:18:27 <DinaBelova> :)
15:18:41 <eglynn> DinaBelova: cool, good to have that confirmation
15:19:04 <eglynn> it's missed juno-3 at this stage obviously, but definitely need to land it for RC1
15:19:17 <DinaBelova> yeah, for sure
15:19:24 <gordc> testing it now myself
15:19:24 <DinaBelova> hehe, i see -1  by fabiog_ :)
15:20:17 <DinaBelova> well, anyway, this change is quite important :)
15:20:27 <eglynn> absolutely, agreed
15:20:58 <eglynn> but we've a bit of time before RC1 for objections such as fabiog_'s to be aired and addressed
15:21:34 <eglynn> shall we move on?
15:21:38 <gordc> i'm digging into a ceilometerclient bug as well... see any tempest ceilometer-alarm-evaluator log
15:21:46 <gordc> http://logs.openstack.org/53/96653/9/check/check-tempest-dsvm-full/d8edccb/logs/screen-ceilometer-alarm-evaluator.txt.gz?level=TRACE
15:21:59 <gordc> if someone knows ceilometerclient really well, feel free to take this over from me.
15:22:05 <eglynn> gordc: yeah, I saw that mentioned on IRC last night, didn't get a chance to look
15:22:32 <eglynn> gordc: do you have a sense of where the problem lies?
15:22:33 <gordc> eglynn: yeah. i can't see it locally so i'm sort of blindly patching right now
15:22:40 <DinaBelova> gordc, frankly speaking this does not look like ceilo client error for me >_<
15:23:29 <gordc> eglynn: i think it's how we're using keystone discovery... i noticed there's a fallback action the other clients use so i just ported taht over
15:23:37 <gordc> i'm not exactly sure if it fixes this case specifically tough
15:23:39 <gordc> though*
15:24:00 <gordc> i'll keep digging for now
15:24:10 <eglynn> hmmm, that log signature rings a bell, I think ildikov saw a similar issue
15:24:59 <eglynn> gordc: IIRC she solved it simply by switching the port numbers
15:25:01 <cdent> gordc: if you don't make any headway on that today and want to punt it to me I can pick it up tomorrow and after.
15:25:19 <eglynn> i.e. s/35357/5000/
15:25:34 <cdent> eglynn: I recall that but wasn't there some debate about the correctness of doing so?
15:25:54 <gordc> eglynn: yeah... could be a devstack patch as well... just wanted to bring up it's broken. :)
15:26:01 <eglynn> cdent: yeah, I don't recall all the details TBH, discussed about a month ago on IRC
15:26:09 <gordc> visibly broken
15:26:21 <gordc> https://bugs.launchpad.net/python-ceilometerclient/+bug/1351841
15:26:22 <uvirtbot> Launchpad bug 1351841 in python-ceilometerclient "python-ceilometerclient does not works without v3 keystone endpoint" [High,Triaged]
15:26:39 <gordc> eglynn: that's probably the bug ildiko was looking at.
15:27:08 <eglynn> gordc: k, that's definitely high priority so we'll need to line up a python-ceilometerclient release with the final juno tag
15:27:50 <eglynn> ... I'll follow up with ildikov when she gets back from her work trip
15:28:41 <eglynn> k, moving on ...
15:28:44 <eglynn> #topic Proposed design summit changes
15:29:06 <eglynn> just a heads up on a few summit changes that being discussed currently
15:29:35 <eglynn> first, a move towards more open/collaborative scheduling of the design session tracks
15:30:25 <eglynn> avoiding using the webapp for proposals, instead just using etherpads etc. to agree the content of the tracks
15:30:47 <eglynn> doesn't sound a million miles from the way we did this for the Juno track
15:31:09 <eglynn> except with s/etherpad/googledoc/ in that case
15:31:32 <eglynn> any opinions on how folks would like to approach that?
15:32:06 <fabiog_> eglynn: would you create a kilo or summit folder in ceilometer specs too?
15:32:20 <eglynn> fabiog_: yep, good point
15:32:24 <fabiog_> so people can start populate with potential ideas
15:32:52 <DinaBelova> fabiog_, good point, yeah
15:32:53 <eglynn> fabiog_: I'll create a kilo directory and any outstanding BP proposals can be rebased onto that
15:33:09 <fabiog_> eglynn: thanks that helps a lot
15:33:37 <fabiog_> are we still have the group table with whiteboard?
15:33:54 <DinaBelova> fabiog_, do you mean project pods?
15:33:55 <eglynn> just one thing to note though about ceilo-specs, some of the other projects are -2'ing all kilo BP proposal to avoid distracting reviewers from juno-3 and RC1
15:34:11 <fabiog_> DinaBelova: yes, I didn't remember the name
15:34:12 <eglynn> personally I think that's a bit OTT
15:34:32 <eglynn> fabiog_: did you see that design summit reloaded thread on the ML?
15:34:52 <eglynn> #link http://lists.openstack.org/pipermail/openstack-dev/2014-August/044169.html
15:34:58 <DinaBelova> eglynn, ++ - that's weird a while - especially keeping in mind the fact we ahave not so mane specs
15:35:08 <fabiog_> eglynn: I will give it a look and shut up ;-)
15:35:24 <eglynn> fabiog_: that was the other summit change I wanted to discuss ...
15:35:57 <eglynn> TL;DR: keep Friday for contributor meetups in a format similar to the project pods in ATL
15:36:57 <eglynn> fabiog_: TBH I'm not sure why we don't just do the project pods in the same way again as ATL, as it would avoid losing 33% of the design session slots
15:37:23 <fabiog_> eglynn: I guess there is not enough space like in Atlanta
15:37:44 <fabiog_> I guess price per sqft in Paris is higher than in Atlanta ;-)
15:37:51 <eglynn> fabiog_: yeah that could be it ... in any case, I raised that idea here: http://lists.openstack.org/pipermail/openstack-dev/2014-September/044914.html
15:38:38 <fabiog_> eglynn: do you think we can ask Hyatt to set-up pods for the different projects?
15:39:00 <fabiog_> eglynn: being one of the conference hotels, they may agree on that, just a thought
15:39:38 <eglynn> a-ha, k, yeah ... though it would obviously add to the cost
15:39:59 <eglynn> ... I'll ask though to get some clarity, as I think the pod was really useful last time round
15:40:11 <fabiog_> eglynn: maybe not, we are closing the hotel anyway for Openstack ;-)
15:41:34 * gordc thought pod was useful as well.
15:42:45 <eglynn> cool, moving on ...
15:42:53 <eglynn> #topic Tempest
15:43:17 <eglynn> DinaBelova: I saw your patch to unskip that nova notification test
15:43:18 <DinaBelova> eglynn, as for the Tempest - here it is tests unskip https://review.openstack.org/#/c/115212/
15:43:22 <DinaBelova> yeah :D
15:43:37 <DinaBelova> and Matthew said he'll add his +2 after gate will feel better
15:43:47 <DinaBelova> so I just need finally to find Sean
15:43:58 <DinaBelova> he's kind of ghost :)
15:44:17 <gordc> DinaBelova: we can probably leave it for now and bring it up when gate calms.
15:44:29 <DinaBelova> gordc, yeah, for sure
15:44:37 <eglynn> DinaBelova: cool, sounds reasonable
15:44:43 <eglynn> cdent has a special kind of skill in shaking +2s out of Sean ;)
15:44:46 <DinaBelova> so after it'll be merged, it'll be possible to remove -2s from other tetss
15:44:52 <DinaBelova> eglynn :D
15:44:57 <cdent> It's bizarre but useful.
15:45:08 <DinaBelova> cdent, quite agree here :)
15:45:08 <gordc> cdent: lol
15:45:25 <DinaBelova> cdent, do you have talent to remove -2's from Sean?
15:45:27 <eglynn> DinaBelova: "remove -2s from other tests" ... that's the other stalled notification tests?
15:45:35 <DinaBelova> eglynn. yeah
15:45:41 <DinaBelova> not for nova, but for other services
15:45:43 <cdent> I haven't yet had the opportunity
15:45:50 <DinaBelova> cdent, you'll have one ;)
15:45:53 <eglynn> DinaBelova: ... that would be great!
15:45:54 <DinaBelova> I promise
15:46:05 <cdent> I'm guess the skill comes from the fact that I have more commits on devstack, grenade and tempest than I do on ceilo
15:46:08 <DinaBelova> eglynn, yeah, I really hope to remove these -2s....
15:46:21 <DinaBelova> cdent, yeah, I guess so
15:46:41 * eglynn thinking again about the TC gap analysis, it would be good to able to declare victory on the tempest task as it's very nearly over the line
15:47:15 <DinaBelova> eglynn - indeed, especially keeping in mind the fact, that now all the jobs are feeling ok for notification tests
15:47:33 <DinaBelova> on any backend we have job now
15:47:40 <DinaBelova> both on Mongo and MySQL
15:48:16 <DinaBelova> so my mongo experimental jobs are just ok for the notifications, although MySQL feels okay as well now
15:48:30 <DinaBelova> gordc and I decided it was kind of temporary issue
15:48:30 <eglynn> DinaBelova: cool ... BTW I've curated the gap analysis wiki a bit but feel free to fix anything I've mispresented
15:48:34 <DinaBelova> with the gate itself
15:48:36 <eglynn> #link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Ceilometer_Gap_Coverage
15:48:47 <DinaBelova> eglynn, ok, I'll take a look, thanks
15:49:09 <eglynn> anything else relevant to Tempest?
15:49:18 <DinaBelova> eglynn, I guess no
15:49:30 <eglynn> cool
15:49:43 <eglynn> BTW TSDaaS/gnocchi status punted to the next meeting as jd__ is on vacation
15:50:01 <eglynn> #topic open discussion
15:50:34 <llu-laptop> eglynn: when do you estimate the "juno3 busy" gate queue be ready for accepting patches for RC1? I saw ceilometer rc3 tarball is already cut?
15:52:02 <eglynn> llu-laptop: yep, juno-3 is tagged and bagged :)
15:52:08 <eglynn> llu-laptop: but I think we can start accepting RC1-oriented patches onto master right away
15:52:32 <eglynn> llu-laptop: IIUC then these must be backported to milestone-proposed in order to get into RC1
15:53:05 <eglynn> llu-laptop: ... so it's the backport, not the landing on master, that represents the acceptance into the RC
15:53:16 <eglynn> ... at least that was the way we did for past releases
15:54:06 <llu-laptop> eglynn: got that
15:54:35 <eglynn> cool
15:56:03 <eglynn> llu-laptop: actually I tell a lie ... the branch has changed a little for juno
15:56:07 <eglynn> IIRC, it'll be the "proposed/juno" branch you backport to
15:56:16 <eglynn> not "milestone-proposed"
15:57:06 <eglynn> the old "milestone-proposed" branch naming has been dropped because we've stopped backporting in the pre-milestone 1-2 day period, as we did before Juno
15:57:50 <eglynn> k, we're up against the shot-clock as per usual ...
15:58:00 <eglynn> thanks all for a productive meeting!
15:58:08 <nsaje> \o
15:58:16 <DinaBelova> bye!
15:58:26 <fabiog_> bye
15:58:26 <eglynn> #endmeeting ceilometer