18:01:14 <johnma> #startmeeting Trove
18:01:15 <openstack> Meeting started Wed Jun 15 18:01:14 2016 UTC and is due to finish in 60 minutes.  The chair is johnma. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:01:18 <openstack> The meeting name has been set to 'trove'
18:01:27 <peterstac> hi johnma
18:01:36 <pmalik> ?/
18:01:37 <johnma> Hello peterstac :)
18:01:46 <johnma> Hi Petr
18:01:49 <mvandijk_> ./
18:02:02 <johnma> Hi Matt
18:02:12 <vgnbkr> o/
18:02:32 <trevormc> hey everybody :)
18:03:01 <trevormc> I changed my nick recently, I used to be the awful twm2016 name.
18:03:25 <johnma> Hello :)
18:03:39 <dloi> o/
18:04:11 <johnma> Hello Morgan, Duk
18:04:32 <johnma> I guess we can get started, its 4 mins past
18:05:03 <johnma> so I am just filling in for amrith today. Looks like we have a light crowd so this might go fast
18:05:12 <johnma> #topic Action items from last week meeting
18:05:24 <johnma> #info things that we can get into Newton including new features/bug fixes/backlog
18:05:48 <cp16net> hello
18:05:52 <johnma> amrith had this from last week. not sure if everyone got a chance to think about this but we will get to this later
18:06:14 <johnma> first let's look at how we have been doing on reviews
18:06:18 <johnma> #topic Trove pulse update
18:06:36 <johnma> #link https://gist.github.com/amrith/1f8da04643dea7d727597e9c45497d6e
18:06:48 <johnma> #link http://bit.ly/1VQyg00
18:07:30 <trevormc> are there any alternative links?
18:08:01 <trevormc> They don't work for me, it might be a company proxy. I can use stackalytics if were just looking at reviews.
18:08:19 <johnma> looks like good progress to me. I dont take any credit for the good progress but thanks to all of you who has been with reviews
18:08:33 <johnma> #link https://wiki.openstack.org/wiki/Meetings/TroveMeeting
18:08:52 <johnma> trevormc the links are posted in the agenda
18:09:02 <johnma> can you see if you can access it from there
18:09:17 <johnma> anyone have anything to add on this topic?
18:09:33 <trevormc> yeah they are the same links. No I can not. Google docs are blocked because it is a competitor for at&t, so dumb.. hshs
18:09:44 <johnma> :)
18:10:11 <johnma> moving forward
18:10:17 <johnma> #topic Trove Midcycle
18:10:49 <johnma> So the midcycle is going to be a 2 -day event instead of 3-days like it used to be.
18:11:09 <johnma> #info Trove Midcycle (August 25th & 26th)
18:11:43 <johnma> OpenStack East is on the 23rd and 24th. Does anyone know when Trove Day is? 24th?
18:12:21 <amrith> johnma, check openstackeast.com. it is earlier the same week.
18:12:21 <johnma> I have created an etherpad to start collecting ideas for the midcycle
18:12:25 * amrith thanks johnma for running the meeting ... \o  |o   o/ ... sorry, I had a conflict.
18:12:48 <johnma> thanks amrith :)
18:12:53 <johnma> #link https://etherpad.openstack.org/p/newton-trove-midcycle
18:14:16 <johnma> oops, I was just corrected. It needs to be ocata midcyle . my bad. I will correct that, thanks amrith :)
18:14:36 <johnma> moving on to the next topic
18:14:39 <johnma> #topic Announcements
18:15:01 <johnma> #info R-16 (Trove spec proposal deadline)
18:15:52 <johnma> so the trove spec deadline is this week which means if anyone has any specs that needs to be considered for this release this is the last week to put that in
18:16:06 <johnma> #link http://releases.openstack.org/newton/schedule.html
18:16:23 <johnma> that's the newton schedule for reference
18:17:28 <johnma> I have one more to go in on the db2 online backups. Does anyone have any other specs that we should expect
18:18:15 <amrith> johnma, to this end I've also pushed up https://review.openstack.org/#/c/329524/ so anyone with a new spec after this week can push it there.
18:18:54 <johnma> awesome. thanks Amrith. I saw that one
18:19:06 <johnma> #topic Specs that are up for review
18:19:07 * amrith requests others (cp16net, johnma, peterstac) to approve this
18:19:28 <peterstac> amrith, just so you know - once that changeset lands the tests won't run on newton anymore
18:19:58 <amrith> peterstac, good point. please -2 it
18:20:00 <peterstac> it'll automatically switch to the ocata directory
18:20:03 <johnma> so can we try to merge this after this week? Does that make sense
18:20:11 <amrith> till newton spec approved deadline
18:20:19 <johnma> aah ok
18:20:31 <peterstac> right - then move any outstanding specs to the new dir at the same time mayve?
18:20:36 <cp16net> ok i'l look at it amrith
18:20:42 <johnma> which is July11-15
18:20:45 <amrith> thx cp16net
18:22:04 <johnma> so regarding the specs that are up for review
18:22:20 <johnma> #link https://review.openstack.org/#/q/status:open+project:openstack/trove-specs+branch:master
18:22:30 <johnma> that's the list
18:23:16 <johnma> Since we have the trove image building spec already approved, do we really need this one: https://review.openstack.org/#/c/295274/
18:24:05 <amrith> johnma, I'm starting to look at the trove image building more closely. I dont know about the second one you reference. will defer to pete on that.
18:24:15 <johnma> also, I am not sure if vkmc is here but I think we need to see what are the plans for the RPC-API-versioning spec
18:25:13 <johnma> I think that was the first spec that was created for trove-image-building using libguestfs.
18:25:22 <peterstac> johnma, it looks as if the spec you mentioned is an older version of the one that got approved
18:25:32 <johnma> right
18:25:40 <peterstac> I'm guessing that it's obsolete (but I haven't looked at it)
18:25:42 <amrith> peterstac, that was the libguestfs spec
18:25:56 <amrith> pmackinn proposed a new spec for dib
18:26:37 <johnma> yes he did and that for approved.
18:26:47 <peterstac> hmm, well the name of the rst file in both specs is trove-image-builder
18:26:54 <johnma> we could put a note in there
18:27:33 <johnma> well that brings me to our next topic, which was the action item from last week
18:27:37 <peterstac> that's probably why it's in merge conflict now
18:27:44 <peterstac> (same file name)
18:28:02 <johnma> right, could be. I haven't looked at it in detail either
18:28:38 <johnma> #info things that we can get into Newton including new features/bug fixes/backlog
18:29:25 <johnma> as far as the specs go, we have 4 specs that have been approved and  a number of them under review
18:30:42 <johnma> The ones that are approved are: locality support/ trove image building/instance upgrade/couchdb configuration groups
18:31:48 <johnma> I hope I am not missing anything else. Again we need to get some info on the couchdb configuration groups one. vkmc had signed up to complete that one
18:33:31 <johnma> for the other specs under review, are there any concerns?
18:34:09 <peterstac> there's also the 'show fault' spec - https://specs.openstack.org/openstack/trove-specs/specs/newton/persist-error-message.html
18:35:30 <peterstac> the code for that has been complete for a while, and it'd be useful to see those messages in the gate at times :)
18:35:36 <johnma> why isn't that showing up in the specs link I posted earlier
18:36:15 <peterstac> it's been approved already
18:36:46 <johnma> aah ok, makes sense. noted, will look at it. Thanks peterstac
18:37:02 <peterstac> you didn't mention it in your 'specs that have been approved' list :(
18:37:26 <peterstac> ok, thx!
18:37:39 <johnma> for the other patches under review - the main ones I could gather are the ones related to :
18:38:07 <johnma> - integration-tests refactor
18:38:09 <johnma> - porting to python-3
18:39:03 <johnma> pmalik: are all the changesets related to integration-tests refactoring complete
18:39:23 <peterstac> wrt the integration tests refactor - the numbers look like they'd pass in the gate now
18:39:49 <johnma> what numbers peterstac?
18:39:58 <trevormc> are the scenario tests different from the integration tests?
18:40:29 <peterstac> trevormc, they're similar, however designed to run on all datastores - not just mysql
18:40:44 <peterstac> here's the changeset that puts it all together:
18:40:44 <pmalik> johnma I would say they are complete. They can certainly go as non-voting and we can then decide when we want to flip them to voting.
18:40:46 <peterstac> #link https://review.openstack.org/#/c/325676/
18:41:30 <peterstac> they consistently run within the time limit now
18:42:02 <peterstac> (they still take longer than the api functional mysql test, but they test a whole lot more)
18:42:12 <johnma> thanks peterstack & pmalik. There are quite a few changesets related to this and it would be good to get them in sooner than later I believe
18:42:19 <johnma> do you agree?
18:42:25 <peterstac> right
18:42:50 <pmalik> trevormc The old 'integration'/'api' tests work only with MySQL. They have no longer been developed and hence do not cover all new stuff that the scenario tests do.
18:43:04 <peterstac> I pushed up the changesets as I worked on them, but if you think it'd be easier to review it all together, I could crush them into one
18:43:06 <johnma> ok, will look at those. Do we have any other reviews that require priority or any discussion?
18:43:07 <trevormc> thanks for the explanation :)
18:43:22 <pmalik> johnma Yes.
18:43:54 <pmalik> johnma I think the sooner we can get them in the better. We can keep them as non-voting to gather more stats.
18:44:42 <johnma> ok, makes sense.  I would rather keep them as is peterstac. It might be easier to review code this way I think
18:44:50 <peterstac> ok, sounds good
18:45:31 <johnma> great, so I guess we know were to focus our reviews for this week. Thanks peterstac and pmalik
18:45:36 <trevormc> I agree, if you can break up patch sets into logical smaller commits that's better than leaving it all as one.
18:46:06 <johnma> anything else to discuss while we are on this topic?
18:46:30 <johnma> #topic Newton Project Update
18:46:56 <johnma> I don't have any updates apart from the Trove spec proposal deadline we mentioned earlier
18:47:10 <vgnbkr> trevormc, The issue with smaller patch sets is that they languish and cause cascading rebases in dependent patchsets.
18:48:36 <johnma> that's also true vgnbkr.
18:48:45 <trevormc> vgnbkr, true. I don't know what's a bigger pain, reviewing a large patch or dealing with the cascading rebases.
18:50:27 <johnma> how big of a patchset will this become if we put them all together. I haven't looked at it, so trying to gauge
18:52:02 <peterstac> it'll be pretty big ...
18:52:12 <trevormc> No idea, maybe 1500 - 2000 lines right?
18:52:37 <peterstac> probably
18:52:44 <johnma> yeah, that's going to be difficult to review
18:53:16 <johnma> anyways, let's see if there is a less painful way to get these changes in
18:53:23 <peterstac> one of the reasons I did it per 'module' was to verify that the test ran the same before and after
18:53:56 <peterstac> it's harder to see that in the final changeset that stiches it all together, since the tests are interleaved at that point
18:54:17 <pmalik> Since the work has already been done, I'd say let's get them it as they stand now. They should ideally go together or very close to each other anyways.
18:54:35 <johnma> sounds like a plan
18:54:45 <johnma> in the interest of time, let's move on to the next topic
18:54:46 <peterstac> for me, I tend to prefer smaller changes (like the ones Victor is doing for py3)
18:55:05 <johnma> right
18:55:33 <johnma> #topic Open Discussion
18:55:45 <johnma> anyone have anything else to discuss?
18:55:50 <trevormc> The meetings almost over and I have to run, but I wanted to introduce myself. My name is Trevor McCasland, I work for AT&T, and I was just matched with amrith through the Women of Openstack Mentoring program.
18:56:30 <trevormc> I'm currently trying to get the hardware together to run Trove but until then I'll be making smaller contributions where I can.
18:56:33 <johnma> Hi Trevor, thank you for the introduction and welcome to the group
18:56:49 <peterstac> welcome, trevormc!
18:57:03 <amrith> welcome trevormc ... let's chat tomorrow.
18:57:14 <trevormc> Sorry for missing some of the meetings but I've been having conflicts. See you all later :)
18:57:15 <johnma> Please let us know if there is anything we can do to help you.
18:57:35 <johnma> sure, thanks for joining us
18:57:40 <trevormc> johnma: I plan on it haha, thanks for the review btw!
18:57:43 <amrith> trevormc needs a new laptop :_
18:57:49 <johnma> :)
18:57:50 <trevormc> ^ yep
18:57:51 <amrith> johnma can help :)
18:58:09 <trevormc> ok bye seriously this time.
18:59:12 <johnma> I guess that's all I have for today as well. Anyone have anything else to discuss?
18:59:38 <amrith> thanks johnma for running the meeting ... much appreciated.
18:59:50 <cp16net> thx
18:59:56 <johnma> back to #openstack-trove I guess. Thank you all for joining today's meeting. Wish you all a great day ahead.
19:00:24 <johnma> Thanks :)
19:00:32 <johnma> #endmeeting