15:00:04 <kumarmn> #startmeeting trove
15:00:04 <openstack> Meeting started Wed Oct 25 15:00:04 2017 UTC and is due to finish in 60 minutes.  The chair is kumarmn. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:06 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:08 <openstack> The meeting name has been set to 'trove'
15:00:28 <kumarmn> #topic gate
15:01:25 <kumarmn> smatzek, Thanks for all your work with stabilizing the gate.
15:02:31 <kumarmn> Noticed last night that some jobs are running several hours (5-6).
15:02:41 <smatzek> thanks.  There is still a fair amount of work to go with stable/pike, likely stable/ocata (I haven't looked at that yet), and troveclient.
15:02:58 <smatzek> I noticed that too but have been tied up in non-upstream work since I saw it this morning.
15:03:28 <smatzek> I'm not sure what's up with that since devstack gate should be timing all jobs out around the 3 hour mark, we've hit that timeout with the functionals several times.
15:04:58 <smatzek> my current focus on the gates is this:  1. stable/pike, talk to Matt R about cherry-picking in yet another fix we have in master to up the chance of recheck success.  2. look into the rash of timeouts we've been getting on master.  3. troveclient zuul v3 job addition.
15:06:48 <smatzek> after that I'm thinking of doing something mriedem brought up yesterday as well, moving all non-voting jobs to experimental so they don't run on every patch set. As amrith stated at PTG this is just sweeping any problems under the rug.  So I would consider it a temporary move to have our jobs get voted on faster and relieve some of the stress on the infra systems.
15:07:10 <smatzek> We would then take work items to make those stable and bring them back in as voting gates.
15:07:45 <kumarmn> That sounds good to me.
15:07:56 <smatzek> possibly investigate scoping when they run with the zuul job definitions where you can tell it to only run when certain files/paths are changed.  Consider only running things like 'redis' if redis specific paths are changed, etc.
15:09:14 <kumarmn> Can conditional jobs be voting?
15:09:34 <smatzek> I believe so
15:10:31 <smatzek> I haven't dug into the zuul v3 docs and that level of detail yet as I've been focused on getting them running.  Now with the request to add the missing python-troveclient tempest job to the project vs infra I need to go do all of that learning.
15:10:51 <smatzek> python-troveclient's gate will be broken until we get that done
15:12:58 <smatzek> amrith: are you around?
15:13:51 <kumarmn> I was going to ping amrith as well for the next topic: Retiring trove-integration
15:15:01 <smatzek> How about this topic for now:  Trove core membership in Gerrit groups.
15:15:15 <lukebrowning_> It looks like the trove stable/newton branch disappeared.
15:15:51 <lukebrowning_> It is not on github anymore.  Is that expected?
15:16:07 <smatzek> that lukebrowning_ that may be intentional.  I'm not sure how they do EOL. Newton went EOL so it may only be tag.
15:17:33 <lukebrowning_> Ah, there is a newton-eol tag
15:17:58 <smatzek> on the topic of gerrit groups.  There is trove-ci, which kumarmn, lukebrowning_, and I are not in.  I don't know what its for.
15:18:38 <smatzek> there is trove-milestone, which we are not in. amrith and Nikhil are.
15:19:14 <smatzek> and lastly, trove-stable-maint, which lukebrowning_, kumarmn, and I are not in.  Membership in this group is required to get you +2 authority on stable branches.
15:20:23 <kumarmn> #topic gerrit-groups
15:20:30 <smatzek> I am not sure how much amrith plans to be active in Trove.  When I asked the openstack-stable core group to get membership for kumarmn, lukebrowning_, and myself, they had a few questions, but said we should have 2 cores in it.
15:20:50 <smatzek> so amrith is already there, as are a few others, but we need 2 active cores in there.
15:20:51 <kumarmn> I do not see johnma or nikhil on here either.
15:21:21 <smatzek> johnma and nikhil are trove-stable-maint. https://review.openstack.org/#/admin/groups/543,members
15:22:54 <smatzek> in the openstack-stable channel smcginnis deferred to tonyb to decide about getting us membership.
15:25:27 <smatzek> tonyb: are you around, and do you have any thoughts on adding some or all of the new Trove cores to trove-stable-maint?
15:48:23 <kumarmn> #topic retiring trove-integration
15:56:08 <kumarmn> it sounds like we will have to get with amrith and tonyb separately.
15:58:49 <kumarmn> lukebrowning, emtrevin, vserrao: Any other topics?
16:00:09 <vserrao> Nothing from my side
16:00:23 <emtrevin> none for me atm
16:00:24 <kumarmn> #endmeeting