15:00:08 <eglynn> #startmeeting ceilometer
15:00:08 <openstack> Meeting started Thu Jul 24 15:00:08 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:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:12 <openstack> The meeting name has been set to 'ceilometer'
15:00:16 <jd__> o/
15:00:17 <nealph> o/
15:00:20 <ildikov> o/
15:00:21 <idegtiarov> o/
15:00:21 <nsaje> o/
15:00:28 <DinaBelova> o/
15:00:36 <eglynn> hey strangers! :)
15:00:41 <DinaBelova> :)
15:00:41 * eglynn has been a half-time slacker this week
15:00:48 <gordc> o/
15:00:50 <llu-laptop> o/
15:00:56 <prad> o/
15:00:58 <vrovachev> o/
15:01:11 <KurtRao> o/
15:01:23 <eglynn> #topic juno-2 retrospective
15:01:32 <cdent> o/
15:01:32 <eglynn> so juno-2 is tagged and bagged :)
15:01:39 <eglynn> http://tarballs.openstack.org/ceilometer/ceilometer-2014.2.b2.tar.gz
15:01:48 <eglynn> thanks to all!
15:02:03 <eglynn> for the efforts to get stuff over the line
15:02:12 <eglynn> ... also lots of nursemaiding of approved patches through the gate
15:02:48 <eglynn> BTW the gating situation should improve when the 1.3.1 oslo-messaging release is finally cut
15:02:56 <eglynn> https://review.openstack.org/#/c/107915/1/doc/source/index.rst
15:03:17 <eglynn> these are the laggard backports still holding it up ...
15:03:24 <eglynn> https://review.openstack.org/#/q/status:open+project:openstack/oslo.messaging+branch:stable/icehouse,n,z
15:03:39 * gordc crosses fingers
15:03:58 <eglynn> at least nsaje's and sileht's fixes for the fake driver are now safely landed
15:04:34 <eglynn> sileht: BTW should we thinking about jumping straight to the 1.4.0.next release if that appears first?
15:05:27 <eglynn> sileht: ... k, one to think about :)
15:05:42 <eglynn> so in the end, only two j2 BPs needed last minute bumps to juno-3
15:05:54 <eglynn> dedicated-alarm-database was pretty much approved by Monday
15:05:58 <eglynn> ... but the gating Gods chose not to smile upon the many rechecks
15:06:21 <eglynn> grenade-resource-survivability was also code-complete in time by cdent
15:06:42 <tongli> @eglynn, IBM needs a http dispatcher (Gorden wrote the initial one), I made some changes and I hope it can get in
15:06:43 <eglynn> ... but the QA PTL is declining any new javelin features until the core of javelin2 is fixed
15:07:19 <eglynn> tongli: can you propose a BP spec?
15:07:23 <tongli> @eglynn, does every new feature in Juno needs a BP?
15:07:38 <tongli> @eglynn, ok, I will create one. thanks.
15:07:42 <llu-laptop> tongli: yes, i think so
15:07:43 <sileht> eglynn, yep using 1.4.0 permit to land the notification publisher patch, that make ceilometer fastest
15:07:45 <tongli> patch set will be there soon.
15:07:53 <eglynn> tongli: anything chunky at least, beyond an RFE bug
15:08:00 <gordc> tongli: you betch yah... unless you manage to confuse everyone and sneak it in as a bug.
15:08:00 <eglynn> tongli: cool, thank you sir!
15:08:42 <tongli> @gordc, that is the http dispatcher your wrote first, I made some changes, so it is more generic, and I think can be used by anyone.
15:08:44 <gordc> tongli: i can take a look at it. the poc i did was relativelys simple
15:08:54 <gordc> tongli: cool cool
15:09:02 <tongli> thanks folks.
15:09:03 <eglynn> sileht: OK if the successor to 1.4.0.0a3 lands before 1.3.1 does, let's just go striaght onto that
15:09:23 <jd__> gordc: stop disclosing my tactics publicly!
15:09:43 <eglynn> so the discussion of BPs dovetails nicely onto juno-3 planning ...
15:09:50 <eglynn> #topic juno-3 planning
15:10:03 <eglynn> #link https://launchpad.net/ceilometer/+milestone/juno-3
15:10:15 <gordc> jd__: lol we've all caught on to your schemes.
15:10:24 <jd__> :->
15:10:30 <eglynn> so the cupboard is looking a bit bare still for juno-3
15:10:37 <eglynn> mainly bumps from juno-2
15:10:49 <jd__> eglynn: isn't there supposed to be some Gnocchi stuff?
15:11:02 <jd__> like are we sure every bp in ceilometer-specs has a bp on launchpad or what?
15:11:28 <gordc> eglynn: i can probably tackle sql-part2... i might need some vetting by Mike Bayer.
15:11:30 <eglynn> jd__: yeah, do you wanna start filing placeholder BPs in luanchpad to point to the gnocchi specs?
15:11:40 <eglynn> gordc: excellent!
15:11:46 <jd__> bureaucracy, ya never got enough
15:12:02 <eglynn> jd__: the placeholder is really just a holder for the 'Specification URL' link
15:12:06 <eglynn> jd__: :)
15:12:14 <gordc> also, i might have found reason for collector performance issues... i might have broken it... still need to verify but also might need some help from Bayer.
15:12:34 <eglynn> jd__: ... I think ttx has cooked up a script to auto-file the LP BPs when the specs land
15:12:40 <jd__> eglynn: haha the spec for the dispatch references https://blueprints.launchpad.net/ceilometer/+spec/dispatcher-for-gnocchi-integration that does not exist
15:12:42 * jd__ blames ildikov
15:12:58 <DinaBelova> :)
15:12:58 <eglynn> gordc: is that captured in a bug?
15:12:59 <jd__> I can blame ttx otherwise, let me know
15:13:10 <eglynn> yeah blame ttx :)
15:13:13 <DinaBelova> jd__, no blames please :)
15:13:14 <tongli> https://blueprints.launchpad.net/ceilometer/+spec/http-dispatcher
15:13:20 <gordc> eglynn: it's the bug related to telemetry tempest tests failing.
15:13:29 <ildikov> jd__: me? my last info that the PTL registers the BP on launchpad after it was approved, so I blame eglynn :)
15:13:30 <tongli> if anyone can approve it, that will be great.
15:13:36 <jd__> hahahaha
15:13:37 <gordc> tongli: you'll need to write up spec.
15:13:46 <eglynn> so the workflow is supposed to be land spec first then file LP BP, but TBH it's a bit counter-intuitive
15:13:57 <eglynn> gordc: a-ha, got it
15:14:00 <tongli> @gordc, where to write a spec for BP?
15:14:04 <gordc> https://github.com/openstack/ceilometer-specs
15:14:31 <jd__> I'm gonna grab popcorns and rant about how much time we lose on those form things
15:14:36 <eglynn> gordc: so this one https://launchpad.net/bugs/1336755 right?
15:14:40 <uvirtbot> Launchpad bug 1336755 in ceilometer "telemetry_notification_api.py test times out waiting for Nova notification" [Critical,Triaged]
15:14:52 <gordc> tongli: there's a template and a few past examples you can base off of.
15:15:06 <jd__> eglynn: ildikov: so who's gonna create that one so we put it on j3? ildikov do you still plan on working on it?
15:15:15 <gordc> eglynn: yeah... i'm not sure why i didn't just copy/paste link in...i have the window open.lol
15:15:16 <tongli> @gordc, will do that. thanks.
15:15:24 <eglynn> gordc: FYI I've proposed a temporary skip for that in tempest https://review.openstack.org/108011
15:15:40 <ildikov> jd__: yeap, just had some health and internal work interrupt...
15:15:41 <gordc> ok.
15:15:46 <eglynn> gordc: so you may need to un-skip the skip if you need further diagnostics on the failure
15:16:03 <ildikov> jd__: eglynn: I will register that BP on launchpad
15:16:11 <eglynn> ildikov: thanks!
15:16:17 <jd__> ildikov: ok cool! let me know if you need help or someone to blame
15:16:33 <gordc> is ilya around? i was wondering if he could run his fancy performance script again to see if performance issue can be seen?
15:16:37 <ildikov> jd__: thanks :)
15:16:45 <DinaBelova> gordc, Ilya is not, but I am :)
15:16:46 <eglynn> gordc: good idea!
15:16:52 <tongli> hi, how about creating a message listener for keystone messags so that these messages turn to meters, that needs a BP and spec as well?
15:16:59 <DinaBelova> eglynn, gordc, I'll let him know :)
15:17:16 <gordc> DinaBelova: thanks!
15:17:27 <gordc> DinaBelova: this patch might be the reason: https://review.openstack.org/#/c/96200/
15:17:35 <DinaBelova> gordc, ok, got it
15:17:39 <eglynn> gordc: apparently Ilya has made some efforts to make the loadgen script etc. more consumable outside the mirantis lab
15:17:47 <_nadya_> tongli:
15:17:53 <DinaBelova> eglynn, still in progress
15:17:59 <DinaBelova> :)
15:18:00 <eglynn> tongli: the basics of that have already been done by boris-42
15:18:13 <_nadya_> tongli: I've seen the patch about keystone notifications
15:18:17 <tongli> @eglynn, not really, we talked yesterday.
15:18:27 <eglynn> tongli: a-ha, k
15:18:42 <eglynn> tongli: but that *could* be more in the nature of a bug-fix
15:18:52 <tongli> boris patch made ceilometer listens to keystone exchange, but no listener really handles any keystone messages.
15:18:54 <tongli> that is what is missing.
15:19:34 <eglynn> so we've got quite a few still open specs reviews
15:19:40 <tongli> @eglynn, ok, all right then, no BP or spec for that.
15:20:05 <gordc> tongli: step1 of jd__'s bug technique: never ask if a bp is needed.
15:20:07 <eglynn> we've missed the acceptance deadline, but we said we wouln't enforce that structly, given vacation and all
15:20:24 <eglynn> however I think we'll have to draw a line by next week's meeting
15:20:28 <tongli> @gordc, lol.
15:20:31 <fabiog_> eglynn, what about the PaaS notification format, do we have any closure on that, please?
15:20:43 <nsaje> isn't acceptance deadline August 21st, not July 21st?
15:20:46 <llu-laptop> eglynn: agreed
15:20:49 * jd__ stares at gordc and says "learning you are, young padawan"
15:20:57 <gordc> jd__: :)
15:21:02 <eglynn> fabiog_: nealph raised that earlier
15:21:13 <nsaje> https://wiki.openstack.org/wiki/Juno_Release_Schedule
15:21:31 * gordc still never seen movie but i get the reference.
15:21:45 <llu-laptop> nsaje: that's for actual patches, not bp
15:21:53 * jd__ suggests we put more rules so we can have more exceptions to them
15:21:54 <eglynn> nsaje: hmmm, I was going on http://lists.openstack.org/pipermail/openstack-dev/2014-July/039201.html
15:22:26 <eglynn> nsaje: Aug 21st is FeatureProposalFreeze
15:22:54 <eglynn> nsaje: i.e. a deadline for proposal of patches *implementing* the BP
15:23:15 <eglynn> nsaje: whereas SAD was a deadline for the spec being landed in the *-specs repo
15:23:34 <eglynn> ... Kafkaesque, I know
15:23:49 <llu-laptop> looks like neutron have 83 bps approved by its SAD date for juno-3, terrifying
15:24:07 <nsaje> eglynn: ok, I see
15:24:30 <eglynn> fabiog_: are you planning to update https://review.openstack.org/101282 based on the discussions in Paris?
15:25:01 <fabiog_> eglynn: I am working on it
15:25:07 <eglynn> fabiog_: thank you sir!
15:25:17 <DinaBelova> eglynn, fabiog_ and I are planning to have the discussion about it now and early next week
15:25:25 <fabiog_> eglynn: realistically I can have something next week
15:25:30 <DinaBelova> to define what actually we need to do here and how
15:25:36 <eglynn> DinaBelova, fabiog_: cool!
15:25:43 <fabiog_> eglynn: it will probably land code in Kilo-1
15:25:54 <KurtRao> What if the implementing code that has been done but haven't been approved by code review? Is it forbidden to check in such code after Aut 21st?
15:26:27 <idegtiarov> DinaBelova: Hope I could join your discussion!
15:26:32 <DinaBelova> idegtiarov, ;)
15:26:47 <eglynn> fabiog_: ok, let's look at whether we can expedite that and get something in for juno, maybe without all the bells and whistles
15:27:03 <fabiog_> eglynn: I am all for that
15:27:28 <eglynn> fabiog_: (context is that this feature has been on our roadmap since the end of the Havana cycle)
15:27:34 <eglynn> fabiog_: cool :)
15:27:35 <DinaBelova> :D
15:27:45 <DinaBelova> for quite a lo-ong time :)
15:28:18 <eglynn> KurtRao: Aug 21st is just a deadline to get the patches proposed to gerrit, not reviewed or landed
15:28:50 <eglynn> KurtRao: it just recognizes the reality that getting patches thru' the review cycle always takes longer than you'd expect
15:28:55 <KurtRao> eglynn: great!
15:29:42 <eglynn> k, let's shoot for this day next week to have specs for all the realistic juno BP candidates landed
15:29:45 <eglynn> thanks folks!
15:29:51 <eglynn> shall we move on?
15:30:06 <DinaBelova> +1
15:30:10 <idegtiarov> +1
15:30:18 <eglynn> #topic tempest status
15:30:22 <DinaBelova> a-ha :)
15:30:38 <DinaBelova> well, folks I have some not really nice news :(
15:30:42 <vrovachev> oohhh
15:30:45 <DinaBelova> https://review.openstack.org/#/c/71259/ - here is the chain of changes
15:30:48 <idegtiarov> :(
15:30:57 <DinaBelova> and they still are in the review process
15:31:04 <DinaBelova> form February to be clear :D
15:31:29 <DinaBelova> they are really ready to be landed, but they won't land in j2 obviously
15:31:29 <eglynn> DinaBelova, ildikov: so no response on that idea to restart services to temporarily accelerate the polling cycle?
15:31:35 <vrovachev> very slow code review process :(
15:31:46 <eglynn> DinaBelova: yeah the juno-2 ship has sailed :(
15:32:12 <ildikov> eglynn: not yet, but this patch is for notifications as I saw
15:32:15 <DinaBelova> eglynn, as for the restarting - no, no news... this letter was sent, etc
15:32:30 <DinaBelova> ildikov, yeah - there are ready ones
15:32:34 <eglynn> so part of this may be resolved by this notion being pushed by QA currently
15:32:42 <DinaBelova> tempest tests not related to the polling
15:32:53 <DinaBelova> eglynn, they were silent :(
15:32:56 <eglynn> of pushing non-blackbox testing into the functional test suites in the project trees
15:32:58 <DinaBelova> will continue pinging :(
15:33:02 <eglynn> i.e. removing from tempest
15:33:15 <eglynn> DinaBelova: k, I'll also ping if there's no response bu EoW
15:33:19 <mtreinish> DinaBelova: well to be fair that was sent during that midcycle
15:33:30 <ildikov> eglynn: maybe your PTL hat would be useful now to start the discussion about that topic ;)
15:33:30 <DinaBelova> mtreinish, yes, I know that
15:33:38 <DinaBelova> it was sent to start the async discussion
15:33:40 <mtreinish> I had forgotten about it, until I just saw this
15:33:51 <mtreinish> I'll write a reply
15:33:56 <DinaBelova> mtreinish, as sync one was not available
15:34:09 <ildikov> mtreinish: cool, thanks
15:34:11 <eglynn> mtreinish: np, we realized you guys would be in conclave last week
15:34:12 <DinaBelova> mtreinish, I'm really ok to have just irc chat :)
15:34:23 <DinaBelova> mtreinish, or letter responce
15:34:30 <DinaBelova> whatever is comfortable for you
15:34:55 <mtreinish> DinaBelova: either or, I don't want to take up your meeting time though
15:34:56 <DinaBelova> mtreinish, and some reviews for the https://review.openstack.org/#/c/71259/ cain will be also really appreciated
15:35:09 <DinaBelova> mtreinish, ;)
15:35:13 <DinaBelova> thank you sir so much
15:36:13 <DinaBelova> eglynn, so I hope to see the ready tests asap (they are really almost done - and different comments have been fixed)
15:36:30 <mtreinish> DinaBelova: sure, I'll try to take another look at that after I get back fromlunch
15:36:42 <eglynn> FYI mtreinish & I also had a brief discussion yesterday on what's coming up re. pushing out functional testing into the projects http://paste.openstack.org/show/87779
15:36:49 <DinaBelova> as for the polling tests - let's see what we'll have after mtreinish & co will look on them :)
15:36:56 <eglynn> ... will be followed up on the ML and at the PTLs meeting the week after next
15:37:27 <DinaBelova> mtreinish, thank you sir so much! I know that's tough to keep in mind so much things you have folks in the QA sphere here
15:37:59 <eglynn> ok, anything else on Tempest?
15:38:35 <DinaBelova> no, i guess no
15:38:35 <eglynn> moving on ...
15:38:38 <eglynn> #topic TSDaaS/gnocchi status
15:38:56 <eglynn> jd__: the floor is yours sir! :)
15:40:08 <jd__> sure
15:40:20 <jd__> so we got merged the new aggregation code using pandas
15:40:26 <jd__> that now compute things correctly :-D
15:40:39 <eglynn> jd__: \o\ :)
15:40:52 <jd__> we also have the new indexer feature to have details when listing resources
15:41:24 <eglynn> jd__: will we go ahead and land that with the accept-extension idea?
15:41:52 <eglynn> ... *without the accept-extension idea?
15:42:27 <eglynn> jd__: a-ha, you've got it in the latest :)
15:42:29 <eglynn> https://review.openstack.org/#/c/109315/1/gnocchi/rest/__init__.py
15:42:30 <eglynn> cool
15:43:22 <jd__> yes
15:43:30 <jd__> and I'll try to continue otherwise nothing new
15:44:17 <eglynn> jd__: I've given pauldix a few weeks since mid-cycle to work on those influxdb issue we talked about
15:44:34 <eglynn> jd__: ... I'm planning to pick that up again next week with his latest
15:44:51 <jd__> ok
15:45:14 <eglynn> jd__: ... so we may need to touch base on how the "restricted" rention policies might look like in the API
15:45:27 * jd__ nods
15:45:40 <eglynn> ... i.e. in the case where a driver is not capable of giving infinite degrees on freedom on that
15:45:44 <eglynn> cool
15:45:56 <eglynn> DinaBelova: anythng to report on opentsdb?
15:46:08 <DinaBelova> eglynn, /me still debugging
15:46:15 <DinaBelova> hope to end up with it today
15:46:19 <eglynn> DinaBelova: cool enough, thanks!
15:46:26 <DinaBelova> also Julien said really nice idea to me
15:46:41 <eglynn> oh yeah, wanna share?
15:46:45 <DinaBelova> I needed to write my own rest client to opentsdb
15:46:47 <DinaBelova> yeah
15:46:59 <DinaBelova> and I've placed that code in gnocchi code - like utils, etc
15:47:02 <jd__> yeah I don't want to bring an opentsdb client in gnocchi as it should be useful standalone
15:47:11 <DinaBelova> jd__, indeed
15:47:14 <eglynn> yeah I saw that patch being -2'd
15:47:32 <DinaBelova> so I've posted the change to infa config
15:47:41 <DinaBelova> to create new stackforge project
15:47:47 <DinaBelova> not merged yet, but still
15:48:12 <DinaBelova> now I keep code in gnocchi to debug, but I'll move to the standalone client when the repo will be created
15:48:25 <eglynn> DinaBelova: cool, thanks!
15:48:30 <DinaBelova> eglynn, np
15:48:49 <eglynn> anything else related to gnocchi?
15:49:26 <eglynn> #topic open discussion
15:50:01 <eglynn> reminder: proposal deadline for summit talks is next Monday July 28th
15:50:36 <eglynn> so if anyone is chewing on proposing something related to ceilo, best to get your skates on :)
15:50:37 <cdent> just for a quick update, it looks like s.dague is getting pretty closeon the javelin2 stuff
15:50:47 <eglynn> cdent: nice one!
15:51:04 <cdent> I keep an eye on the various reviews, and they are creeping forward
15:51:09 <eglynn> cdent: ... so that would mean the restriction on new features for javelin would be lifted?
15:51:20 <cdent> eventually, but can't guess when
15:51:35 <eglynn> cdent: cool, thanks for the update
15:53:25 <eglynn> ... going, going ...
15:53:41 <eglynn> ... gone! :)
15:54:03 <eglynn> thanks all for the productive meeting, let's call that a wrap!
15:54:08 <eglynn> #endmeeting