Thursday, 2019-01-10

*** macza has quit IRC00:01
*** slaweq has quit IRC00:05
*** yamamoto has quit IRC00:05
*** yamamoto has joined #openstack-meeting-300:05
*** moguimar has quit IRC00:12
*** jamesmcarthur has joined #openstack-meeting-300:12
*** jamesmcarthur has quit IRC00:16
*** yamamoto has quit IRC00:16
*** slaweq has joined #openstack-meeting-300:22
*** yamamoto has joined #openstack-meeting-300:23
*** slaweq has quit IRC00:26
*** yamamoto has quit IRC00:45
*** gmann_pto is now known as gmann01:07
*** yamamoto has joined #openstack-meeting-301:19
*** mjturek has quit IRC01:20
*** yamamoto has quit IRC01:24
*** yamamoto has joined #openstack-meeting-301:30
*** yamamoto has quit IRC01:32
*** yamamoto has joined #openstack-meeting-301:35
*** macza has joined #openstack-meeting-301:38
*** yamamoto has quit IRC01:38
*** markvoelker has joined #openstack-meeting-301:40
*** markvoelker has quit IRC01:45
*** macza has quit IRC01:50
*** yamamoto has joined #openstack-meeting-302:01
*** yamamoto has quit IRC02:03
*** macza has joined #openstack-meeting-302:17
*** macza has quit IRC02:22
*** hongbin has joined #openstack-meeting-302:30
*** Haunted330 has joined #openstack-meeting-302:31
*** yamamoto has joined #openstack-meeting-302:34
Haunted330This channel is closed. You will have to leave.02:34
*** bobh has joined #openstack-meeting-302:39
*** yamamoto has quit IRC02:40
*** Haunted330 has quit IRC02:42
*** Haunted330 has joined #openstack-meeting-302:43
*** bobh has quit IRC02:43
*** Haunted330 has quit IRC02:46
*** Haunted330 has joined #openstack-meeting-302:47
*** Haunted330 has quit IRC02:50
*** Haunted330 has joined #openstack-meeting-302:50
*** markvoelker has joined #openstack-meeting-302:51
*** raildo has quit IRC02:51
*** Haunted330 has quit IRC02:53
*** Haunted330 has joined #openstack-meeting-302:54
*** Haunted330 has quit IRC03:08
*** Haunted330 has joined #openstack-meeting-303:09
*** Haunted330 has quit IRC03:11
*** yamahata has joined #openstack-meeting-303:31
*** iyamahat has quit IRC03:35
*** markvoelker has quit IRC03:53
*** jamesmcarthur has joined #openstack-meeting-304:00
*** jamesmcarthur has quit IRC04:05
*** yamamoto has joined #openstack-meeting-304:12
*** yamamoto_ has joined #openstack-meeting-304:45
*** lpetrut has joined #openstack-meeting-304:46
*** yamamoto has quit IRC04:49
*** diablo_rojo has quit IRC04:56
*** hongbin has quit IRC04:56
*** markvoelker has joined #openstack-meeting-304:59
*** lpetrut has quit IRC05:15
*** radeks_ has joined #openstack-meeting-305:42
*** radeks__ has joined #openstack-meeting-305:45
*** radeks_ has quit IRC05:47
*** radeks__ has quit IRC05:55
*** markvoelker has quit IRC06:03
*** markvoelker has joined #openstack-meeting-306:05
*** macza has joined #openstack-meeting-306:10
*** macza has quit IRC06:14
*** radeks__ has joined #openstack-meeting-306:33
*** lpetrut has joined #openstack-meeting-307:04
*** yamamoto_ has quit IRC07:18
*** macza has joined #openstack-meeting-307:27
*** macza has quit IRC07:31
*** Luzi has joined #openstack-meeting-307:35
*** yamahata has quit IRC07:48
*** pcaruana has joined #openstack-meeting-307:51
*** yamamoto has joined #openstack-meeting-308:24
*** yamamoto has quit IRC08:27
*** radeks_ has joined #openstack-meeting-308:27
*** radeks__ has quit IRC08:29
*** ralonsoh has joined #openstack-meeting-308:37
*** markvoelker has quit IRC08:52
*** bobh has joined #openstack-meeting-309:19
*** logan- has quit IRC09:21
*** logan- has joined #openstack-meeting-309:28
*** logan- has quit IRC09:28
*** e0ne has joined #openstack-meeting-309:33
*** yamamoto has joined #openstack-meeting-309:39
*** apetrich has quit IRC09:42
*** apetrich has joined #openstack-meeting-309:43
*** yamamoto has quit IRC09:43
*** markvoelker has joined #openstack-meeting-309:49
*** markvoelker has quit IRC09:51
*** yamamoto has joined #openstack-meeting-310:09
*** bobh has quit IRC10:19
*** e0ne has quit IRC10:47
*** e0ne has joined #openstack-meeting-310:50
*** pbourke has quit IRC11:11
*** pbourke has joined #openstack-meeting-311:13
*** psachin has joined #openstack-meeting-311:35
*** psachin has quit IRC11:44
*** psachin has joined #openstack-meeting-311:48
*** pbourke has left #openstack-meeting-311:51
*** slaweq has joined #openstack-meeting-311:58
*** yamamoto has quit IRC12:09
*** yamamoto has joined #openstack-meeting-312:09
*** raildo has joined #openstack-meeting-312:29
*** slaweq has quit IRC12:38
*** raildo has quit IRC13:13
*** raildo has joined #openstack-meeting-313:24
*** e0ne has quit IRC13:30
*** tosky has joined #openstack-meeting-313:41
*** jamesmcarthur has joined #openstack-meeting-313:45
*** jeremyfreudberg has joined #openstack-meeting-313:59
*** tellesnobrega has joined #openstack-meeting-314:00
tellesnobrega#startmeeting sahara14:00
openstackMeeting started Thu Jan 10 14:00:27 2019 UTC and is due to finish in 60 minutes.  The chair is tellesnobrega. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
jeremyfreudbergo/14:00
tellesnobregathanks jeremyfreudberg for joining at the exact right time, I almost lost track of time14:01
toskyhi14:01
jeremyfreudberghi!14:01
toskyme too, 10 minutes ago I knew about this meeting and I was fixing a commit message and I forgot14:01
tellesnobregahi all14:02
tellesnobrega#topic News/Updates14:02
*** openstack changes topic to "News/Updates (Meeting topic: sahara)"14:02
tellesnobregaI'm really focused on getting the split plugin patch to merge14:03
toskya) helping with the bureacratic part of the plugin splitting (done, we have the new repositories); writing the APIv2 support for both tempest tests (almost done, thanks jeremyfreudberg and tellesnobrega  for the fixes) and scenario tests (basically working, waiting for multihost results)14:03
tellesnobregaalso worked on some enhancements on apiv214:03
jeremyfreudbergi was deep into apiv2 with a patch finally coming out last night; i spent the rest of the time marvelling at tosky's productivity14:04
tellesnobregajeremyfreudberg, he is amazing14:05
toskycome on, I couldn't have done anything without your (both) fixes14:05
*** Luzi has quit IRC14:05
tellesnobregamoving on14:06
tellesnobrega#topic APIv214:06
*** openstack changes topic to "APIv2 (Meeting topic: sahara)"14:06
tellesnobregawe got some really good progress yesterday14:06
tellesnobregawe have some merged patches, some under review14:07
tellesnobregawhat is missing at this point?14:07
toskyJeremy's patch with the fixes, and your patches with OSC support14:07
tellesnobregapolicies inconsistencies, osc, the polish of apiv2 and microversioning14:07
toskyI think I may found another smaller issues14:07
tellesnobregaon osc?14:08
toskywith job binaries (see my last comment)14:08
toskythe same thing that I touched; waiting for the next results from sahara-v2 tempest tests14:08
toskymicroversioning is probably more relevant (pending the answer from the TC)14:08
toskyis the policy fixes something that affects the API, or is it something that we can better recheck next week?14:09
tellesnobregait doesn't affect the API itself14:09
tellesnobregait is just policy checking, I guess we can wait a little more14:10
jeremyfreudbergdoesn't affect the api itself, but it is part of making the api ready and great... since it is server side i would give it more priority than anything client-side, for the purposes of m214:10
*** e0ne has joined #openstack-meeting-314:10
tellesnobregathat makes sense too14:11
toskyclient-side == the OSC patch?14:11
jeremyfreudbergclient side is the OSC patch, plus some currently not-yet-written dashboard patches (I think telles's patch covers everything for osc, but i didn't look)14:12
tellesnobregajeremyfreudberg, I think it covers, but as usual, when you get too close you may not see clearly14:13
tellesnobregaso please take a look whenever you can14:13
jeremyfreudbergso, just to put it clearly, the server side stuff is my new patch, policy things, and microversion / declaration of stable14:14
jeremyfreudbergi didn't quite understand what the concern yesterday with microversion was, can someone sum it up again?14:15
*** mjturek has joined #openstack-meeting-314:16
toskywe have two pending patches, declaration of stable and microversion14:17
toskythe question is: in order to reduce the amount of work, and especially if some final touches are needed for the microversioning patch,14:17
toskyif we land the 'declaration of stable' now before M2, and discuss and merge the microversion patch next week, will this break the API?14:18
toskyor is it allowed?14:18
toskyin any case, if we can merge the microversion support now, so be it14:18
jeremyfreudbergi see, i don't know the official advice (But I know you have gone looking for it), but i wouldn't want to declare stable without the microvresions (i consider it a breaking change to add the microversions later, since some headers will go from failing silently to failing loudly)14:20
tellesnobregajeremyfreudberg, do you think we can make microversion get in today?14:21
jeremyfreudbergi think the microversions patch is mergable toay-- we only didn't merge it in the summer because i wanted more time to fixup apiv2 before naming 2.00-- with last night's patch i guess the fixups are there now14:21
tellesnobregaawesome, if that is the case, all concern is pointless since we can make it all happen today14:22
tellesnobregawhich is the best case scenario14:22
jeremyfreudbergtosky, does it make sense?14:23
jeremyfreudbergthat all being said, it does still require some blind confidence to declare it stable and declare 2.00 -- because then there is no going back14:23
toskyjeremyfreudberg: sure14:24
toskyand that's the reason why I'd like to have the tempest tests working :)14:24
toskyscenario tests seems to be fine, but I'm waiting for the multinode results14:24
toskyeven if we don't merge the sahara-tests patch14:25
jeremyfreudbergright14:25
toskybut at least so far the API itself seems fine (the endpoints and the results, at least)14:25
jeremyfreudbergmy hunch is that we are in good shape, but doubting can be useful at times14:26
jeremyfreudbergfor what it's worth, i have much more confidence in the plugin split than apiv2 being 100.0% perfect (i'd guess 99%)14:26
tellesnobregajeremyfreudberg, I would say that is pretty high, but we are close :)14:27
jeremyfreudbergok, any more admisitrative comments on apiv2? if not, we should take a second to discuss the policy names14:28
*** mjturek has quit IRC14:29
toskyjeremyfreudberg: can you please rebase the "Give the illusion of microversion support" on top of the "Some polish for APIv2" patch, so that I can test both?14:29
jeremyfreudbergyes, i can do that14:29
*** armstrong has joined #openstack-meeting-314:30
*** armstron_ has joined #openstack-meeting-314:30
*** armstro__ has joined #openstack-meeting-314:30
toskythanks, I don't have other questions for now14:30
*** armstrong has quit IRC14:30
*** armstron_ has quit IRC14:30
*** armstro__ has quit IRC14:30
tellesnobregajeremyfreudberg, anything else on apiv2?14:31
jeremyfreudbergtellesnobrega: just the policy names14:31
tellesnobregago ahead14:31
jeremyfreudbergthe idea is that with apiv2 we have made big efforts to entire rename jobs->job_templates and job_executions->jobs, but the policy names are still in the old way: a job-executions policy controls the v2 jobs endpoints14:34
jeremyfreudbergi think we all agree that accurate naming is best14:34
jeremyfreudbergi guess the problem (in my head, anyway) is that we can't create a "jobs" policy for v2 jobs because that policy name is already taken for the v1 thing14:34
tellesnobregayes14:35
tellesnobregaI only see one way out of this, is to create a jobs_v2 policy14:35
tellesnobregaand once we drop v1 we can change that back14:35
toskyare we sure we can change it back?14:36
toskywell, maybe following the deprecation policies14:36
jeremyfreudbergtosky: yea, policies can be deprecated14:37
toskydo policies support aliases?14:37
jeremyfreudbergit looks like not, but i could be wrong14:38
jeremyfreudbergi'm reading the "naming policies" section here, by the way: https://docs.openstack.org/oslo.policy/latest/user/usage.html#naming-policies14:39
jeremyfreudbergand i guess i found the solution14:39
jeremyfreudbergbecause the resource name should be _singular_14:39
jeremyfreudbergas in, not plural14:39
tellesnobregaso job?14:40
*** haleyb has joined #openstack-meeting-314:40
jeremyfreudbergyeah, at the very least apiv2 jobs would be controlled by "job"... for ultimate consistency we could deprecate all the old stuff and use singular nouns for everytinhg14:41
*** haleyb is now known as haleyb|away14:41
tellesnobregasounds good14:41
jeremyfreudbergyeah, as long as we do the deprecation properly i think that that is best14:43
jeremyfreudbergmaybe it should wait till after m2 though14:43
jeremyfreudbergtosky, any thought?14:43
tellesnobregafor deprecating stuff, yes14:43
tellesnobregaI can fix the inconsistencies now by adding the job policy for v214:43
toskyif we can do it without breaking the API, sure14:43
toskytalking about APIv2, did anyone have some time to check that small quirck with /plugins endpoint that I pointed out last time?14:43
toskyor was it just a non-issue?14:44
jeremyfreudbergi don't recall what it was14:44
tellesnobregaand we start deprecating the rest after m2? makes sense?14:44
tellesnobregatosky, I don't recall either, sorry14:44
toskyuh, maybe we discussed it outside the meeting14:46
toskyok, so I guess we need a) deploy with unversioned endpoint b) fix quirks by Jeremy c) microversioning support d) stable14:47
toskyas basic requirements14:47
tellesnobregayes14:48
tellesnobregaand I'm fixing the policy patches as well14:49
jeremyfreudbergtosky, if you end up remembering the /plugins quirk, let us know14:49
toskyscenario tests with APIv2 passed, in the meantime; both single (fake) and simple multinode (spark)14:49
jeremyfreudbergtellesnobrega, i'm in the process of commenting on the policy patch14:50
toskyI'm waiting for a rebase of the microversion patch to test it too14:50
tellesnobregajeremyfreudberg, awesome14:50
jeremyfreudbergtosky: i'm mid-rebase now14:50
toskyshould we merge first the APIv2 patches before the plugin split?14:50
tellesnobregaawesome tosky14:50
tellesnobregayes, I can rebase it after the apiv2 merges14:50
toskyprobably yes, better APIv2, then split (which is "just" one patch right now)14:51
tellesnobregayes14:51
toskythe big work with split will be next week, with the cascade breakages in the deployment systems (puppet, ansible, tripleo) and packaging14:51
tellesnobregatosky, count me in for that14:52
tellesnobreganot sure how much help I will be, but I can try14:52
tellesnobregaplaying with tripleo has been on my list forever14:52
toskylet's discuss it next week :)14:52
tellesnobregayeah14:53
tellesnobrega7 minutes left14:53
tellesnobregasplit-plugins seems pretty straight forward now14:53
tellesnobregaI'm disabling grenade job for it to pass14:54
tellesnobreganot a huge deal, we can fix it later14:54
toskyyes, and better recheck it after APIv2 as just said14:54
tellesnobregaof course14:54
toskyso we know that everything is more or less fine14:54
tellesnobregabtw, split plugins patch passed tempest14:54
toskyyep, noticed14:55
toskywe need to refine the jobs, but *after*14:55
tellesnobregayeah14:56
*** armstrong has joined #openstack-meeting-314:56
*** armstron_ has joined #openstack-meeting-314:56
*** armstro__ has joined #openstack-meeting-314:56
tellesnobregaI guess we have a good definition of what we need to get it done today14:56
*** armstro__ has quit IRC14:56
*** armstrong has quit IRC14:56
*** armstron_ has quit IRC14:56
tellesnobregalets keep the focus and make it happen14:56
tellesnobregathanks jeremyfreudberg and tosky14:57
tellesnobregaI know it has been a crazy cycle, but it most certainly will be a great one for Sahara14:58
toskycrossing fingers14:58
*** armstrong has joined #openstack-meeting-314:58
*** armstron_ has joined #openstack-meeting-314:58
*** armstro__ has joined #openstack-meeting-314:58
tellesnobregathanks again, you both have been great :D14:59
*** armstrong has quit IRC14:59
*** armstro__ has quit IRC14:59
*** armstron_ has quit IRC14:59
tellesnobrega#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:59
toskythanks you all!14:59
openstackMeeting ended Thu Jan 10 14:59:42 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2019/sahara.2019-01-10-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2019/sahara.2019-01-10-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2019/sahara.2019-01-10-14.00.log.html14:59
*** jamesmcarthur has quit IRC14:59
*** jeremyfreudberg has left #openstack-meeting-314:59
*** armstrong has joined #openstack-meeting-314:59
*** tosky has left #openstack-meeting-315:00
*** davidsha has joined #openstack-meeting-315:00
*** moguimar has joined #openstack-meeting-315:03
*** moguimar has quit IRC15:05
*** moguimar has joined #openstack-meeting-315:05
*** igordc has joined #openstack-meeting-315:22
*** armstron_ has joined #openstack-meeting-315:24
*** armstro__ has joined #openstack-meeting-315:24
*** armstr___ has joined #openstack-meeting-315:24
*** armstro__ has quit IRC15:24
*** armstr___ has quit IRC15:26
*** armstron_ has quit IRC15:26
*** armstron_ has joined #openstack-meeting-315:29
*** armstro__ has joined #openstack-meeting-315:29
*** armstr___ has joined #openstack-meeting-315:29
*** armstr___ has quit IRC15:29
*** armstro__ has quit IRC15:29
*** armstron_ has quit IRC15:29
*** armstron_ has joined #openstack-meeting-315:30
*** armstro__ has joined #openstack-meeting-315:30
*** jamesmcarthur has joined #openstack-meeting-315:30
*** armstron_ has quit IRC15:30
*** armstro__ has quit IRC15:30
*** armstron_ has joined #openstack-meeting-315:31
*** armstro__ has joined #openstack-meeting-315:31
*** armstron_ has left #openstack-meeting-315:33
*** armstro__ has quit IRC15:33
*** jamesmcarthur has quit IRC15:37
*** tellesnobrega has left #openstack-meeting-315:46
*** slaweq has joined #openstack-meeting-315:53
*** hongbin has joined #openstack-meeting-315:53
*** diablo_rojo has joined #openstack-meeting-316:02
*** jamesmcarthur has joined #openstack-meeting-316:10
*** jamesmcarthur has quit IRC16:14
*** lpetrut has quit IRC16:17
*** slaweq has quit IRC16:19
*** slaweq has joined #openstack-meeting-316:36
*** macza has joined #openstack-meeting-316:37
*** e0ne has quit IRC16:38
*** macza_ has joined #openstack-meeting-316:40
*** macza has quit IRC16:42
*** slaweq has quit IRC16:48
*** iyamahat has joined #openstack-meeting-316:49
*** igordc has quit IRC17:10
*** jamesmcarthur has joined #openstack-meeting-317:20
*** mjturek has joined #openstack-meeting-317:22
*** mjturek has quit IRC17:26
*** mjturek has joined #openstack-meeting-317:27
*** psachin has quit IRC17:28
*** tbachman has joined #openstack-meeting-317:47
*** davidsha has quit IRC17:50
*** SridarK has joined #openstack-meeting-317:51
*** rkukura has joined #openstack-meeting-317:56
*** jamesmcarthur has quit IRC17:58
rkukuratbachman, SridarK: hi!17:59
tbachmanrkukura: SridarK: hi17:59
*** jamesmcarthur has joined #openstack-meeting-317:59
*** igordc has joined #openstack-meeting-318:00
tbachmannot sure annakk will make it18:00
tbachman#startmeeting networking_policy18:00
openstackMeeting started Thu Jan 10 18:00:17 2019 UTC and is due to finish in 60 minutes.  The chair is tbachman. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: networking_policy)"18:00
openstackThe meeting name has been set to 'networking_policy'18:00
*** SridarK_ has joined #openstack-meeting-318:00
SridarK_Hi All18:00
tbachmanSridarK_: hi!18:00
rkukurahi18:00
tbachmanI’m not sure we have too much to cover today, but figured we’d meet, just in case18:01
tbachmanOne thing we can discuss is the gate resources and branches18:01
tbachmanrkukura: SridarK_: any topics you all want to touch on?18:01
SridarK_tbachman: not much from just coming up to speed18:02
rkukuraI can mention a bit about baked queries, for the record18:02
tbachmansounds good18:02
*** SridarK has quit IRC18:02
tbachmanwant to start off with that?18:02
rkukuraAnd also bring up the question of eliminating unmaintained code from the repo18:03
rkukurasure18:03
tbachman#topic Using baked queries18:03
*** openstack changes topic to "Using baked queries (Meeting topic: networking_policy)"18:03
tbachmanrkukura: you have the floor :)18:03
rkukuraSo we have a patch in review that is specific to the AIM backend18:03
rkukura#link https://review.openstack.org/#/c/623113/18:04
rkukuraThis changes most of the queries in the various AIM drivers and extensions to use sqlalchemy’s baked query feature18:04
rkukurathis reduces the python CPU overhead in neutron-server by caching the generated queries rather than building them up each time they are executed18:05
rkukurait makes the queries a bit more verbose, but I don’t think they are any more difficult to read or write once you are familiar with them18:05
tbachmanrkukura: do you have a sense of improvement this approach has, in terms of execution time?18:06
rkukuraI have covered all the AIM-specific queries in this patch (there are a few that can’t be baked in master, and more in older stable branches), but I have not touched any of the queries in GBP that are not AIM-specific18:06
rkukuraJust want to note that as a followup, the same approach could be applied to the non-AIM queries18:07
tbachmanack18:07
rkukuraI see a noticible, but hard to quantifiy, improvement in the time needed to run the UTs, hopefully reducing timeouts in CI jobs18:07
tbachmannice!18:07
tbachmanI’ll review the patch and backports today18:08
tbachmanI’d started it, but still have a bit to go18:08
rkukuraI also did some profiling of a UT that does some complex queiring, an measured about a 30% reduction in CPU usage for the UT itself.18:08
tbachmanthat’s a good gain!18:08
rkukuraSo that is probably >50% improvement in the query speed, since there is a lot of UT code that was also being profiled18:09
rkukuraIt should be roughly equivalent to making the same exact query using raw SQL.18:09
tbachmanAt some point, it might be interesting to share this kind of thing with the usptream neutron crew18:09
rkukuraright18:09
tbachmanSridarK_: if you get a chance, can you have a look at the patch and comment?18:10
rkukuraUnfortunately, older versions of sqlalchemy are lacking some features for the baked queries, so fewer queries are baked in the backports18:10
tbachmanrkukura: I’ll try to wrap up my review today18:10
SridarK_tbachman: will do - started looking and trying to understand the changes18:10
tbachmanthx!18:10
rkukurathanks SridarK_ and tbachman!18:11
tbachmanrkukura: anything else on that front?18:11
tbachmanIf not, I’ll transition to the upstream gate topic18:11
rkukuraSo I do not intend to followup with baking GPB or upstream neutron queries in the short term, but anyone is welcome to take those on18:11
tbachmanack18:11
rkukurathat is for that18:12
rkukurathat’s it for that18:13
tbachmank18:13
rkukuracan’t type18:13
tbachmanthx rkukura!18:13
tbachman#topic EOL branches and upstream gate jobs18:13
*** openstack changes topic to "EOL branches and upstream gate jobs (Meeting topic: networking_policy)"18:13
tbachmanAlthough I haven’t seen this in the most recent gate jobs, we were seeing a lot of timeouts on the ocata branch18:13
tbachmanspeculation was that zuul was limiting the amount of resources to ocata, as it was becoming EOL18:13
tbachmanWe saw similar problems when the newton branch went EOL18:14
*** jamesmcarthur has quit IRC18:14
tbachmanOur “fix” for newton was to limit the UTs that run in the gate, with the understanding that people posting backports to newton had to run UTs locally without the tests being disabled18:15
rkukuratbachman: do we know if these limits are in overall time, number of CPU cores, or both?18:15
tbachmanrkukura: I don’t, but will check18:15
rkukuratbachman: that reminds me that we should do a local run of the full set of UTs in the stable/newton back-port of the baked_query patch18:15
tbachmank18:15
tbachmanIn any case, the most recent ocata jobs seem to be passing, so we may not have to make this change just yet, but I wanted to give folks a heads-up that we may have to use the same policy for that branch soon18:16
rkukurais ocata a long term support branch for any distros we know of?18:17
tbachmanI think for Canonical it is18:17
*** jamesmcarthur has joined #openstack-meeting-318:17
tbachmanI’ll take the action to find out how these jobs are limited, and if/when ocata will become so-constrained18:18
tbachmanrkukura: SridarK_: any comments?18:18
SridarK_tbachman: sounds good18:18
rkukuratbachman: thanks!18:19
tbachmanrkukura: want to talk about the question of eliminating unmaintained code from the repo18:19
tbachman?18:19
rkukurasure18:19
tbachman#topic Unmaintained code in the GBP repo18:19
*** openstack changes topic to "Unmaintained code in the GBP repo (Meeting topic: networking_policy)"18:19
*** jamesmcarthur has quit IRC18:19
rkukuraI think we merged a patch a while back that turned off UTs for the servicechain feature in order to avoid CI timeouts18:20
rkukuramy understanding is that this code only worked with the old APIC policy driver, which has been eliminated since stable/ocata18:20
tbachmanrkukura: ack18:21
rkukuraso we should probably start some deprecation process to remove the code (functionality and UTs) from the repo if nobody plans to use it18:21
tbachmanrkukura: SridarK_: are you aware of how this is typically done upstream?18:22
*** ralonsoh has quit IRC18:22
SridarK_tbachman: well usually there is a heads up for deprecation and if no one objects in a cycle or 2 we can remove it18:22
tbachmanLike something to the mailing list?18:23
SridarK_tbachman: yes exactly18:23
tbachmank18:23
rkukuraI’ve been giving heads up on this IRC channel for a while, but not sure if that counts ;)18:23
tbachmanheh18:23
tbachmanrkukura: SridarK_: would one of you be up for sending an email to the list?18:24
SridarK_tbachman: surely no issues18:24
tbachmanSridarK_: thanks!18:24
rkukuraMaybe a patch to remove it, linked in the email18:24
tbachmanrkukura: would we need to leave the patch open beyond a release? Is there any issue in doing that?18:25
tbachman(i.e. in order to account for giving at least one release cycle for deprecation)18:25
SridarK_rkukura: i was thinking more of a heads up as the first step18:26
tbachmanI guess having such a patch is helpful b/c it is specific18:26
rkukuralets start with an email18:26
tbachmank18:26
rkukuraideally we’d decorate stuff with deprecation warnings, but I really don’t think that is useful18:26
tbachmanany other comments on this topic?18:26
rkukuranope18:27
SridarK_nothing more from me18:27
tbachman#topic Open Forum18:27
*** openstack changes topic to "Open Forum (Meeting topic: networking_policy)"18:27
tbachmanJust want to welcome SridarK_ to the GBP channel!18:27
SridarK_tbachman: thx :-)18:27
*** yamahata has joined #openstack-meeting-318:28
tbachmanSridarK_ is a new contributor to GBP — welcome SridarK_!18:28
tbachmanIf there aren’t any other open items, I’ll wrap things up18:28
rkukuranothing from me18:28
SridarK_same here18:29
tbachmank18:29
tbachmanThanks all!18:29
tbachman#endmeeting18:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"18:29
openstackMeeting ended Thu Jan 10 18:29:12 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2019/networking_policy.2019-01-10-18.00.html18:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2019/networking_policy.2019-01-10-18.00.txt18:29
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2019/networking_policy.2019-01-10-18.00.log.html18:29
tbachmanrkukura: SridarK_: bye!18:29
rkukurabye18:29
SridarK_bye18:29
*** tbachman has left #openstack-meeting-318:29
*** rkukura has left #openstack-meeting-318:29
*** diablo_rojo has quit IRC18:48
*** jamesmcarthur has joined #openstack-meeting-318:49
*** jamesmcarthur has quit IRC18:54
*** e0ne has joined #openstack-meeting-319:00
*** jamesmcarthur has joined #openstack-meeting-319:01
*** jamesmcarthur has quit IRC19:13
*** jamesmcarthur has joined #openstack-meeting-319:17
*** diablo_rojo has joined #openstack-meeting-319:19
*** moguimar has quit IRC19:26
*** moguimar has joined #openstack-meeting-319:27
*** iyamahat has quit IRC19:31
*** moguimar has quit IRC19:32
*** jamesmcarthur has quit IRC19:33
*** jamesmcarthur has joined #openstack-meeting-319:34
*** moguimar has joined #openstack-meeting-319:36
*** moguimar has quit IRC19:41
*** moguimar has joined #openstack-meeting-319:43
*** moguimar has quit IRC19:48
*** armstrong has quit IRC20:19
*** hongbin has quit IRC20:24
*** jamesmcarthur has quit IRC20:40
*** jamesmcarthur has joined #openstack-meeting-320:41
*** iyamahat has joined #openstack-meeting-320:49
*** hongbin has joined #openstack-meeting-320:56
*** radeks_ has quit IRC21:12
*** e0ne has quit IRC21:13
*** radeks has joined #openstack-meeting-321:15
*** bobh has joined #openstack-meeting-321:25
*** e0ne has joined #openstack-meeting-321:30
*** bobh has quit IRC21:33
*** e0ne has quit IRC21:33
*** radeks has quit IRC21:42
*** pcaruana has quit IRC21:46
*** mjturek has quit IRC21:55
*** bobh has joined #openstack-meeting-322:09
*** bobh has quit IRC22:15
*** hongbin has quit IRC22:36
*** jamesmcarthur has quit IRC22:42
*** jamesmcarthur has joined #openstack-meeting-322:43
*** jamesmcarthur has quit IRC22:47
*** e0ne has joined #openstack-meeting-322:55
*** e0ne has quit IRC22:58
*** edleafe- has joined #openstack-meeting-323:23
*** edleafe has quit IRC23:24
*** edleafe- is now known as edleafe23:24
*** Haunted330 has joined #openstack-meeting-323:28
*** Haunted330 has quit IRC23:47
*** Haunted330 has joined #openstack-meeting-323:47
*** Haunted330 has quit IRC23:48
*** Haunted330 has joined #openstack-meeting-323:49
*** diablo_rojo has quit IRC23:54
*** macza_ has quit IRC23:57
*** diablo_rojo has joined #openstack-meeting-323:58
Haunted330This channel is closed. You are going to have to leave.23:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!