17:01:45 <mmedvede> #startmeeting third-party
17:01:46 <openstack> Meeting started Tue Aug  9 17:01:45 2016 UTC and is due to finish in 60 minutes.  The chair is mmedvede. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:47 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:49 <openstack> The meeting name has been set to 'third_party'
17:02:22 <mmedvede> anyone is around for third-party CI meeting?
17:05:24 <asselin> hi, i'm here
17:05:35 <mmedvede> hey asselin
17:05:49 <mmedvede> not too big of a crowd lately
17:06:28 <asselin> no, but a few updates going on in puppet-openstackci
17:07:07 <asselin> there was an incompatibility between zuul and nodepool dependencies reported yesterday and fixed in https://review.openstack.org/#/c/352560/
17:07:08 <mmedvede> are you talking about pins?
17:07:16 <asselin> yes
17:08:19 <asselin> when installed on the same system. We don't have tests for this...but this would be caught only at the functional level which we don't really have right now.
17:09:29 <mmedvede> asselin: this is python package dependency problem, correct?
17:10:08 <asselin> mmedvede, yes, for apscheduler>=3.0
17:10:23 <mmedvede> ok, so installing in venv should take care of that too
17:10:41 <mmedvede> it is not like zuul depends on nodepool and vice versa
17:10:44 <asselin> zuul required < 3.0. so jeblair created a new zuul tag 2.5 yesterday that depends on >=3.0
17:11:10 <asselin> mmedvede, yes that's another solution and a good idea actually
17:12:03 <asselin> having each service run in it's own venv, not sure if -infra folks would object to that
17:12:15 <mmedvede> creating venv is not that much overhead
17:12:48 <jeblair> we won't run them in venv on infra production servers
17:14:04 <mmedvede> jeblair: is it because it adds complexity in debugging?
17:14:46 <mmedvede> asselin: maybe can be optional just for all-in-one example somehow
17:14:50 <jeblair> mmedvede: it's also inconvenient for sysadmins
17:15:17 <jeblair> at any rate, the components should have compatible requirements, so i think we did the right fix this time
17:15:53 <asselin> mmedvede, either way it would require updating the individual puppet-<service> modules to optionally running in a venv.
17:16:29 <mmedvede> right, might not be worth it
17:17:06 <asselin> ok, so as long as there are compatible tags of the tools working together in a single node, I'm fine with the current approach
17:17:27 <jeblair> the 2.5.0 tag for zuul also includes *a lot* of bugfixes, btw
17:17:28 <mmedvede> asselin: do you have an idea how many third-party CIs run all-in-one, as opposed to similar to infra team's architecture?
17:17:57 <asselin> mmedvede, my guess is the majority of them...at least for cinder folks
17:18:44 <asselin> jeblair, thanks again for creating the zuul tag.
17:19:02 <mmedvede> jeblair: +1, I upgraded to 2.5.0 recently, and it runs better so far. I have noticed memory footprint looks better.
17:19:32 <asselin> I personally prefer keeping tags for all 3rd party ci folks. They have enough stability/maintenance problems as is.
17:19:46 <jeblair> yeah, we were holding off on tagging that until the known memory leak cleared up, which it seems to have done
17:21:40 <mmedvede> thank you for that
17:21:56 <jeblair> np :)
17:22:14 <mmedvede> worth it, would upgrade again :)
17:23:45 <mmedvede> should probably set the topic, as there are no set items on agenda
17:23:50 <mmedvede> #topic Open Discussion
17:25:04 <mmedvede> asselin: it seems there are either less problems in CIs, or people do not know about the meetings :)
17:25:16 <mmedvede> I hope it is the former
17:25:46 <asselin> I think there are less problems :)
17:26:10 <mmedvede> common CI definitely helps with that
17:26:23 <mmedvede> thanks for watching that area
17:26:28 <asselin> \0/ glad to hear it :)
17:28:08 <mmedvede> if there is nothing else to discuss, one fyi for today:
17:28:08 <mmedvede> devstack has been switched to use neutron by default
17:28:42 <mmedvede> #link https://review.openstack.org/#/c/350750/
17:29:22 <mmedvede> I did not notice any side effects in our nova CI, but have seen problems in ironic third-party CIs, that might have been related
17:30:13 <mmedvede> any objections to closing the meeting?
17:30:22 <asselin> none from me
17:32:30 <mmedvede> thanks for attending
17:32:30 <mmedvede> #endmeeting