18:00:07 <amrith> #startmeeting openstack-trove
18:00:08 <openstack> Meeting started Wed Dec 28 18:00:07 2016 UTC and is due to finish in 60 minutes.  The chair is amrith. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:11 <openstack> The meeting name has been set to 'openstack_trove'
18:00:34 <amrith> for anyone who's around today ...
18:00:54 <amrith> ping for peterstac johnma slicknik dougshelley66 pmalik vgnbkr mvandijk trevormc aliadil spilla songjian trevormc apsarshaik
18:01:14 <amrith> if I recall correctly, both johnma and slicknik are traveling for the holidays
18:01:17 <amrith> and won't be around
18:01:39 <vgnbkr> o/
18:01:50 <amrith> howdy morgan!
18:02:00 <amrith> how much snow have y'all had so far
18:02:14 <peterstac> o/
18:02:17 <morgan> not a ton :P
18:02:22 <vgnbkr> Hi.  Not much snow here, though there is a bit.  It basically rained for the last two days.
18:02:30 <morgan> also... on vacation ;)
18:02:50 <morgan> also I think you want a different 'morgan' ;)
18:03:18 <amrith> nor morgan I want morgan, aka vgnbkr
18:03:23 <peterstac> yep, morgan -> vgnbkr
18:03:29 <amrith> you are morgan aka morgan
18:03:44 <amrith> unless you are a vegan baker
18:03:52 <amrith> in which case, stick around
18:03:54 <vgnbkr> biker, not baker
18:04:00 <amrith> we discuss interesting recipes
18:04:21 <amrith> how to bake brownies with ingredients that are legal in 26 states
18:04:34 <amrith> ok, let's get started
18:04:37 <amrith> #agenda https://wiki.openstack.org/wiki/Meetings/TroveMeeting
18:04:44 <amrith> I didn't have a lot to chat about
18:04:50 <vgnbkr> OK, first take 2 cups flour...
18:05:03 <amrith> there you go
18:05:16 <amrith> the only thing I had to talk about was Reviews for abandonment
18:05:18 <amrith> #topic Reviews for abandonment
18:05:32 <amrith> #link https://etherpad.openstack.org/p/okipourVgv
18:05:39 <amrith> I blew off a bunch of reviews last night
18:05:58 <amrith> things that had been sitting around for a while
18:06:07 <amrith> and not really making any forward progress
18:06:19 <amrith> had some minor mis-steps along the way (too many brownies)
18:06:37 <peterstac> There are probably a couple that should go in, but we can resurrect those if needed
18:07:00 <amrith> yes, I realize that my filter was broad and the hammer was swung rather clumsily
18:07:09 <peterstac> (especially since they've all stalled in one form or another)
18:07:14 <amrith> so the chance that there were some collateral damage is high
18:08:02 <amrith> from the release perspective, the only update I have is https://review.openstack.org/#/c/414764/
18:08:09 <amrith> I put in for some extra-atc passes
18:08:29 <amrith> if anyone has others who they'd like nominated for extra-atc recognition, please let me know.
18:08:50 <vgnbkr> Have the passes gone out already?
18:09:02 <amrith> no vgnbkr the deadline for extra-atc's is next week
18:09:07 <amrith> so regular passes have NOT gone out
18:09:09 <amrith> I've also been trying to do some spring cleaning of old bugs, and reviews
18:09:18 <amrith> so expect some more collateral damage
18:09:26 <amrith> I would like to get the specs for ocata merged
18:09:38 <amrith> #link https://review.openstack.org/#/q/project:openstack/trove-specs+status:open
18:09:58 <amrith> especially https://review.openstack.org/#/c/391637/ and https://review.openstack.org/391871
18:10:16 <amrith> I'm not optimistic about the future of the other two.
18:10:33 <amrith> There's code to go with the two specs I mention as well
18:10:51 <amrith> #link https://review.openstack.org/409197 (which vgnbkr has reviewed once)
18:11:07 <amrith> and with that
18:11:13 <amrith> I've run out of things I had for the meeting
18:12:01 <amrith> so without further ado
18:12:05 <amrith> #topic open discussion
18:12:20 <peterstac> I have one item
18:12:52 <amrith> you have the floor
18:12:53 <peterstac> oops, I guess I should have done this - o/
18:13:02 <peterstac> ok, thx ;)
18:13:18 <peterstac> The Redis cluster tests have been failing regularly in the gate
18:13:29 <amrith> i see you added a new bug
18:13:34 <peterstac> They always pass for me locally so it's been hard to debug
18:13:58 <peterstac> but I had an idea that the controller machine is now too fast and is trying to pump in data before the cluster is ready
18:14:28 <peterstac> amrith, yes, I put in a new bug since the old one is marked resolved and I couldn't see how to reopen it :(
18:14:56 <peterstac> anyways, I'm cautiously optimistic that this might fix the issue
18:15:06 <peterstac> #link https://review.openstack.org/#/c/415516/
18:15:19 <amrith> so, if the test controller is pushing data before the cluster is ready (hypothesis) it means that (a) we're reporting the cluster ready too soon, or (b) the tests aren't waiting for the cluster to be ready.
18:15:23 <amrith> which do you think it is?
18:15:30 <amrith> oh, you have a fix, let me look
18:15:56 <peterstac> It could be that we're reporting the cluster ready too soon
18:16:21 <peterstac> I just put a loop around all the *data* methods (moved the verify one to all of them)
18:17:01 <amrith> so you are bandaging the tests for something which is really an issue in the system under test? is that a fair assessment?
18:17:11 <peterstac> I'm doing some reading about how to check that the cluster is *actually* ready, but haven't found anything yet
18:17:29 <peterstac> Kind of - the commands are coming back ok, but maybe we need to poll for something else
18:18:06 <amrith> only think I can think of then is that procedurally mark your review as partial-bug rather than closes-bug.
18:18:19 <peterstac> Sure, makes sense
18:18:24 <amrith> if it improves things, that's fine; a real fix is to figure out when the cluster is 'really' ACTIVE
18:18:31 <peterstac> I'll tack some more info onto the bug as well
18:18:36 <peterstac> right
18:18:39 <amrith> sounds good, let's see what the gate does
18:18:47 <amrith> we can give it the usual 5 rechecks
18:18:52 <amrith> and see how well it does
18:18:59 <peterstac> yep, that's my plan :)
18:19:06 <amrith> good plan
18:19:21 <vgnbkr> I'd start with option (b) - it's hard to imagine what "not ready" would mean to Redis.
18:19:32 <amrith> would you (and vgnbkr) take a look at the secure.rpc thing again please
18:19:37 <peterstac> ok
18:19:40 <amrith> I'd like to move that along to merge for ocata
18:20:03 <amrith> a blog post hangs in the balance ;)
18:20:10 <amrith> also a tweet or two
18:20:13 <peterstac> vgnbkr, that's kind of what my fix does, it keeps trying to add data until it passes (or times out)
18:20:23 <amrith> and it'll save me needless jaw flapping at the next summit/ptg
18:21:10 <vgnbkr> peterstac, my point was just that I would guess that for Redis up = ready.
18:21:35 <peterstac> well, when you try to add data, it comes back with 'The cluster is down'
18:22:03 <peterstac> so it looks like maybe a command completes but some work is still being done in the background
18:22:12 <vgnbkr> Right, so I'm saying it was that it was not up yet, not that it was up but not ready.
18:22:38 <vgnbkr> Subtle difference, though :-)
18:24:49 <amrith> maybe the two of you can pick this up on #openstack-trove, or better still f2f :)
18:25:08 <peterstac> sure
18:25:18 <amrith> sorry, I have an agenda in saying that
18:25:24 <amrith> (a) I've got to have lunch
18:25:29 <amrith> (b) it is past lunchtime
18:25:45 <amrith> anything else for the meeting today?
18:25:54 <peterstac> ok, well the Redis cluster test just failed, so that's not the answer :(
18:26:24 <peterstac> That's all I had
18:27:52 <amrith> ok, so going once ... motion to adjourn :)
18:28:53 <amrith> going twice
18:29:13 <amrith> thanks folks
18:29:14 <amrith> #endmeeting