Friday, 2018-10-26

*** darvon has joined #openstack-meeting00:21
*** erlon has joined #openstack-meeting00:24
*** Liang__ has joined #openstack-meeting00:32
*** Liang__ is now known as LiangFang00:32
*** tetsuro has joined #openstack-meeting00:40
*** longkb has joined #openstack-meeting00:40
*** diablo_rojo has quit IRC00:55
*** jamesmcarthur has joined #openstack-meeting01:03
*** jamesmcarthur has quit IRC01:05
*** jamesmcarthur has joined #openstack-meeting01:05
*** fanzhang has joined #openstack-meeting01:07
*** jamesmcarthur has quit IRC01:35
*** mhen has quit IRC01:40
*** mhen has joined #openstack-meeting01:42
*** lbragstad has quit IRC01:49
*** lbragstad has joined #openstack-meeting01:49
*** ykatabam has joined #openstack-meeting01:54
*** rcernin has joined #openstack-meeting01:55
*** yamahata has quit IRC01:55
*** iyamahat_ has quit IRC01:56
*** cloudrancher has quit IRC02:03
*** cloudrancher has joined #openstack-meeting02:04
*** jamesmcarthur has joined #openstack-meeting02:05
*** jamesmcarthur has quit IRC02:09
*** bobh has joined #openstack-meeting02:14
*** bobh has quit IRC03:10
*** lpetrut has joined #openstack-meeting03:58
*** tetsuro has quit IRC04:04
*** hle2 has joined #openstack-meeting04:20
*** janki has joined #openstack-meeting04:22
*** lpetrut has quit IRC04:34
*** yamahata has joined #openstack-meeting05:02
*** iyamahat has joined #openstack-meeting05:02
*** yamamoto has quit IRC05:26
*** yamamoto has joined #openstack-meeting05:26
*** hle2 has quit IRC05:44
*** Luzi has joined #openstack-meeting05:45
*** kopecmartin has joined #openstack-meeting05:50
*** Liang__ has joined #openstack-meeting05:50
*** jgriffit1 has joined #openstack-meeting05:51
*** evrardjp_ has joined #openstack-meeting05:51
*** hemna_ has joined #openstack-meeting05:54
*** ianw_ has joined #openstack-meeting05:54
*** dims_ has joined #openstack-meeting05:54
*** LiangFang has quit IRC05:55
*** erlon has quit IRC05:55
*** apetrich has quit IRC05:55
*** liuyulong|away has quit IRC05:55
*** SotK has quit IRC05:55
*** jgriffith has quit IRC05:55
*** kopecmartin|off has quit IRC05:55
*** dims has quit IRC05:55
*** strigazi has quit IRC05:55
*** hemna has quit IRC05:55
*** evrardjp has quit IRC05:55
*** mattoliverau has quit IRC05:55
*** chkumar|off has quit IRC05:55
*** ianw has quit IRC05:55
*** Qiming has quit IRC05:55
*** jlvillal has quit IRC05:55
*** ianw_ is now known as ianw05:55
*** irclogbot_1 has quit IRC05:58
*** mhen has quit IRC05:59
*** tetsuro has joined #openstack-meeting06:01
*** apetrich has joined #openstack-meeting06:02
*** erlon has joined #openstack-meeting06:03
*** mhen has joined #openstack-meeting06:07
*** hle2 has joined #openstack-meeting06:10
*** hle2 has left #openstack-meeting06:13
*** aojeagarcia has joined #openstack-meeting06:29
*** aojea has quit IRC06:33
*** hle2 has joined #openstack-meeting06:35
*** hle2 has left #openstack-meeting06:43
*** hle2 has joined #openstack-meeting06:43
*** yamamoto has quit IRC06:53
*** yamamoto has joined #openstack-meeting06:53
*** yamamoto has quit IRC06:53
*** yamamoto has joined #openstack-meeting06:54
*** njohnston has quit IRC07:06
*** ykatabam has quit IRC07:09
*** njohnston has joined #openstack-meeting07:11
*** erlon has quit IRC07:12
*** rcernin has quit IRC07:22
*** strigazi has joined #openstack-meeting07:26
*** bauzas is now known as bauwser07:35
*** evrardjp_ is now known as evrardjp07:37
*** rossella_s has joined #openstack-meeting08:00
*** SotK has joined #openstack-meeting08:06
*** ttsiouts has joined #openstack-meeting08:33
*** rfolco|rover has quit IRC08:35
*** ttsiouts has quit IRC08:38
*** tetsuro has quit IRC08:38
*** ttsiouts has joined #openstack-meeting08:53
*** ttsiouts has quit IRC09:14
*** ttsiouts has joined #openstack-meeting09:15
*** e0ne has joined #openstack-meeting09:16
*** Qiming has joined #openstack-meeting09:35
*** yamamoto has quit IRC09:36
*** electrofelix has joined #openstack-meeting09:58
*** erlon has joined #openstack-meeting10:07
*** lpetrut has joined #openstack-meeting10:11
*** ssbarnea has joined #openstack-meeting10:11
*** jamesmcarthur has joined #openstack-meeting10:12
*** ttsiouts has quit IRC10:15
*** jamesmcarthur has quit IRC10:16
*** Liang__ has quit IRC10:31
*** ssbarnea has quit IRC10:49
*** e0ne has quit IRC10:51
*** e0ne_ has joined #openstack-meeting10:52
*** a-pugachev has joined #openstack-meeting10:54
*** tridde is now known as trident11:17
*** EmilienM is now known as EvilienM11:24
*** janki has quit IRC11:36
*** ttsiouts has joined #openstack-meeting11:48
*** longkb has quit IRC11:49
*** yamamoto has joined #openstack-meeting12:02
*** liuyulong has joined #openstack-meeting12:09
*** raildo has joined #openstack-meeting12:13
*** eharney has joined #openstack-meeting12:25
*** bobh has joined #openstack-meeting12:26
*** e0ne_ has quit IRC12:26
*** yamamoto has quit IRC12:32
*** rfolco|rover has joined #openstack-meeting12:33
*** njohnston has quit IRC12:39
*** jamesmcarthur has joined #openstack-meeting12:47
*** ttsiouts has quit IRC12:51
*** yamamoto has joined #openstack-meeting12:55
*** dustins has joined #openstack-meeting13:07
*** tpsilva has joined #openstack-meeting13:09
*** Liang__ has joined #openstack-meeting13:12
*** mriedem has joined #openstack-meeting13:19
*** efried is now known as fried_rice13:23
*** e0ne has joined #openstack-meeting13:25
*** cloudrancher has quit IRC13:31
*** cloudrancher has joined #openstack-meeting13:32
*** jamesmcarthur has quit IRC13:46
*** awaugama has joined #openstack-meeting13:53
*** bnemec has joined #openstack-meeting13:54
*** munimeha1 has joined #openstack-meeting13:57
*** mlavalle has joined #openstack-meeting14:00
mlavalle#startmeeting neutron_drivers14:00
openstackMeeting started Fri Oct 26 14:00:51 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. 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: neutron_drivers)"14:00
openstackThe meeting name has been set to 'neutron_drivers'14:00
yamamotohi14:01
mlavallehi14:01
amotokihi14:02
hle2hi14:02
kailunhi14:02
*** Chenjie has joined #openstack-meeting14:02
bcafarelsorry I kept a few drivers busy, they should get in soon14:02
mlavallebcafarel: LOL14:02
slaweqhi14:02
haleybhi14:03
mlavalleok, we have quorum now14:03
*** Luzi has quit IRC14:03
mlavallehle2, kailun: are you here to discuss something with the team?14:04
*** njohnston has joined #openstack-meeting14:04
njohnstono/14:05
kailunmlavalle: yes, I have one RFE to discuss14:05
mlavallekailun: do you have the pointer?14:05
kailunhttps://bugs.launchpad.net/neutron/+bug/179521214:05
openstackLaunchpad bug 1795212 in neutron "[RFE] Prevent DHCP agent from processing stale RPC messages when restarting up" [Wishlist,In progress] - Assigned to Kailun Qin (kailun.qin)14:05
kailunAnd the patch is available @ https://review.openstack.org/#/c/609463/14:06
kailunI'd like to have the idea triaged and move forward :)14:06
*** longkb has joined #openstack-meeting14:08
ChenjieHello everyone, I have an RFE that I want to discuss.14:10
slaweqkailun: I think I don't understand bug You described there14:10
Chenjiehttps://bugs.launchpad.net/neutron/+bug/179365314:10
openstackLaunchpad bug 1793653 in neutron "[RFE] Enable other subprojects to extend l2pop fdb information" [Wishlist,In progress] - Assigned to ChenjieXu (midone)14:10
*** jaypipes is now known as leakypipes14:10
*** artom is now known as temka14:10
ChenjieThe patch is available https://review.openstack.org/#/c/599319/14:11
slaweqhost with agent goes down and is rebooted, neutron-server rechedule networks from this dhcp agent to another ones, then host is booted again - what rpc messages it will have then?14:11
*** hongbin has joined #openstack-meeting14:12
mlavalleI see haleyb is co-author of the patch14:14
kailunslaweq: the rpc sent to the agent before the agent is down14:15
haleybwell, i helped update it but it wasn't my original idea14:15
slaweqand how that short (I guess) delay can help to solve this problem?14:15
kailunslawek: a schedule rpc  for instance14:15
slaweqshouldn't it be solved e.g. by smaller ttl time for messages in rabbitmq?14:16
*** onovy has quit IRC14:16
kailunslaweq: the agent will block the rpc messages during the init delay and have an active sync state to get the  up-to-date info from the sever after that delay14:18
haleybi was also wondering about doing it without a config option somehow, since if it's a bug the default should be to enable the 'wait'14:18
amotokiIIRC, when dhcp-agent is restarted, full sync will be done, right?14:18
amotokiIf so, when RPC msgs older than full sync arrives, we can drop them. perhaps this is what the timestamp based solution tries to do.14:18
kailunslaweq: ttl is another way IMO14:18
mlavalleamotoki: yes14:18
amotokiI think the complicated case is where delayed msgs arrive after full sync, but I am not sure this happens.14:19
*** ttsiouts has joined #openstack-meeting14:20
slaweqamotoki: ok, I understand now "timestamp" solution14:20
amotokikailun: is my understanding correct?14:20
slaweqbut proposed patch was doing this second approach (delay): https://review.openstack.org/#/c/609463/14:20
slaweqand in fact how You want to be sure then that agent waited enough time and will not consume some stale message anyway?14:21
*** jamesmcarthur has joined #openstack-meeting14:21
*** stephenfin is now known as finucannot14:22
haleybwould the other alternative be to use the Resource queue like the l3-agent?14:22
amotokiyeah, I see it too.14:22
kailunamotoki: yes14:23
amotokiwhat I am not sure so far is what kind of corner cases and negative behaviors could happen (even with full sync)14:23
kailunsorry guys my connection is unstable :)14:23
amotokikailun: you can follow up the discussion at http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-10-26-14.00.log.txt (with little delay)14:24
slaweqhaleyb: yes, Resource queue with ExclusiveResourceProcessor should maybe be better idea IMO14:26
kailunamotoki: dhcp does not have a timestamp support right now, correct?14:26
haleybslaweq: that was one reason i moved it from under l314:26
kailunamotoki: while l3 agent has one I guess14:26
amotokikailun: i cannot answer it immediately. does anyone know it?14:27
slaweqalso, one more question14:27
slaweqI don't remember exactly but in some (very) old releases rpc queues which agent's registered had some random id14:28
kailunslaweq: I also tried to evaluate timestamp and the delay I proposed, I did not see a obvious drawback14:28
slaweqso when agent was e.g. restarted it created new queue and would not consume messages from this old one14:28
slaweqisn't it like that anymore?14:28
kailunslaweq: I don't have an answer to this one,  I can double check14:29
slaweqkailun: would be good IMO to check that14:30
amotokiit seems we need to clarify failure modes in question, i.e., what actually happens before discussing a solution.14:30
kailunslaweq: sure I'll do that14:30
slaweqamotoki++14:30
kailunamotoki: agree, let me follow up with this one14:32
mlavallekailun: based on this discussion, let's continue the conversation in the RFE14:32
amotokislaweq and I raises several questions. let's follow them up on the bug14:32
slaweqamotoki: mlavalle: I agree, let's follow up on RFE14:33
kailunmlavalle: slaweq: amotoki: haleyb: let's follow them up on the bug14:33
mlavallekailun: thanks14:33
amotokikailun: thanks for raising this14:34
mlavallekailun: and thanks for your patches. I think we merged one yesterday, didn't we?14:34
mlavallealso DHCP14:34
kailunyes  thank you all for the review and discussion14:35
mlavalleI liked the way you used the Event object ;-)14:35
mlavalleand the throttling, which was a concern when we approved that RFE14:36
kailun:) every concern has a solution14:37
mlavalleok, now let's move on to https://bugs.launchpad.net/neutron/+bug/179365314:38
openstackLaunchpad bug 1793653 in neutron "[RFE] Enable other subprojects to extend l2pop fdb information" [Wishlist,In progress] - Assigned to ChenjieXu (midone)14:38
Chenjiemlavalle: thanks!14:38
mlavalleChenjie: I saw this one a little more than a week ago and asked in the bug to keep the status as New, so it doesn't slipped thorugh our screen14:39
mlavallebut apparently you pushed a patch and the status was changed14:40
mlavallethat's ok14:40
mlavalleThe leasson for us is we need to update that screening criteria14:40
Chenjiemlavalle: sorry for that!14:40
mlavalleChenjie: no worries. it's really a lesson for me that I need to improve that screening criteria14:41
amotokiregarding the status, we now use tags to track RFE states (rfe, rfe-confirmed, rfe-triaged), so i think LP bug status does not matter us.14:42
mlavalleamotoki: yeah, but this one slipped through the cracks somehow14:42
mlavalleIt didn't show up yesterday when I was preparing for the meeting14:42
mlavalleChenjie: anyways, the upshot is that we may finish reviewing your rfe today and we would continue the discussion in the RFE clarifying14:44
Chenjiemlavalle: thank you very much!14:45
Chenjiethank you all!14:45
mlavalleChenjie: thanks for your submission, first of all14:46
mlavalleChenjie: question: is this being proposed in the context of bgpvpn-networking? or it is just an example?14:46
amotokiwe can first discuss the problem statement and what is needed (before going into the detail of the solution) in the RFE. The detail can be discussed in the spec.14:47
Chenjiemlavalle: Yes, it is. But this can be used by other subprojects.14:48
*** Liang__ is now known as LiangFang14:49
amotokiChenjie: are there any usecases in other subprojects in your mind?14:49
munimeha1hi14:49
amotokiI understand it can potentially be used by other projects of course14:49
mlavalleamotoki, haleyb, slaweq, yamamoto: here's the figure mentioned in the rfe: https://launchpadlibrarian.net/389540006/rfe_EXTEND_L2POP_FDB_INFORMATION.PNG14:50
Chenjieamotoki: For now another RFE has been drafted to add l2pop support for floating ip resources. This can be used in here.14:50
*** armstrong has joined #openstack-meeting14:51
*** ssbarnea|bkp2 has quit IRC14:51
Chenjieamotoki: yes, other projects can use this.14:51
amotokiChenjie: thanks, I see.14:52
Chenjieamotoki: the name should be changed to "Enable other projects to extend l2pop fdb information"?14:52
*** rossella_s has quit IRC14:53
amotokiChenjie: I am not sure now. If another RFE requests more and it affects the design/direction of this RFE, it is better to be considered.14:53
amotokiotherwise, the current title sounds good14:54
mlavalleyeah, the title looks good to me. don't worry about it14:54
amotokiChenjie: let's understand and discuss the current usecase first.14:54
Chenjiethanks!14:55
liuyulongslaweq, https://bugs.launchpad.net/neutron/+bug/1796824, I'd like to raise this to the meeting, since the patch is almost done here: https://review.openstack.org/#/c/608909/14:55
openstackLaunchpad bug 1796824 in neutron "Port in some type of device_owner should not allow update IP address" [Medium,In progress] - Assigned to LIU Yulong (dragon889)14:55
liuyulongAnd here: https://review.openstack.org/#/c/612969/14:56
yamamotodoes bgpvpn assume l2-agent based networks?14:56
slaweqliuyulong: lets follows mlavalle's order in the meeting - he is chair here :)14:57
mlavalleChenjie: I went over the your proposal and in principle it makes sense to me. I would like to go over it again14:59
Chenjieyamamoto: Do you mean networking-bgpvpn uses l2-agent(ovs and linuxbridge agent)?14:59
Chenjiemlavalle: Thank you very much!14:59
mlavalleand we can retake it next week14:59
*** ssbarnea has joined #openstack-meeting15:00
*** diablo_rojo has joined #openstack-meeting15:00
mlavallewe ran out of time today15:00
yamamotoi meant if it didn't work for other l2 impl like odl15:00
slaweqthx, and have a great weekend guys :)15:00
slaweqo/15:00
yamamotoi'll ask on rfe15:00
*** dansmith is now known as SteelyDan15:01
mlavallealso if you have time, please look at https://review.openstack.org/#/c/57447715:01
Chenjiemlavalle: thank you very much!15:01
mlavallespec is ready for next rund of review15:01
mlavalle#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:01
openstackMeeting ended Fri Oct 26 15:01:23 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-10-26-14.00.html15:01
yamamotogood night15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-10-26-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-10-26-14.00.log.html15:01
amotokithanks15:01
Chenjieyamamoto: Ok, thank you for your reviewing!15:01
smcginnis#startmeeting releaseteam15:01
openstackMeeting started Fri Oct 26 15:01:43 2018 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: releaseteam)"15:01
openstackThe meeting name has been set to 'releaseteam'15:01
fungihowdy!15:01
smcginnisMorning fungi15:01
diablo_rojoHello :)15:02
smcginnis#link https://etherpad.openstack.org/p/stein-relmgt-tracking Agenda - R-24, ~line 11315:02
smcginnisHey diablo_rojo, long time no see.15:02
ttxo/15:02
armstrongHello15:03
smcginnisOK, that's probably everyone for today.15:03
smcginnis#topic15:03
*** openstack changes topic to " (Meeting topic: releaseteam)"15:03
smcginnisMark Ocata as extended maintenance15:03
smcginnisGrr15:03
smcginnis#topic Mark Ocata as extended maintenance15:03
*** openstack changes topic to "Mark Ocata as extended maintenance (Meeting topic: releaseteam)"15:03
smcginnis#link https://review.openstack.org/#/c/598164/15:03
smcginnisttx: I think you added this?15:03
ttxyes for some reason that one does not appear on the dashboard so we did not approve it15:04
ttxany reason we should not approve it?15:04
smcginnisI don't think so. THere was some question of teams making that extended-maintenance decision,15:04
smcginnisBut as far as the official release page, I think it should reflect that that release is now in e-m mode.15:04
ttxok approving now15:05
smcginnisYay, one more out my queue.15:05
fungispeaking of em, there's an interesting thread going on the debian-devel ml at the moment about user confusion over their choice to call "lts" what we decided against referring to as "lts" (for the very same reasons)15:05
smcginnisAnything more we need to do as the release team for that? Or leave it to tonyb for any follow up.15:05
ttxnothing15:06
smcginnisfungi: Oh, interesting. They're coming to the same conclusions on wording?15:06
fungiyeah, specifically that "lts" in the linux kernel and ubuntu communities means specific releases that get longer official maintenance15:06
*** mlavalle has left #openstack-meeting15:06
fungiwhereas debian lts is that after a release reaches what would be eol a separate team takes over care and feeding of it for as long as they can muster the resources to do so15:07
smcginnisI wasn't initially a fan of the em phrasing, but I've grown to like it now and think it better descibes what to expect from the community.15:07
fungiso users are installing debian "lts" releases thinking that means longer support, when it actually means they're just installing outdated versions15:07
smcginnisMakes sense.15:08
smcginnisAnyway...15:08
smcginnis#topic stein-1 requests15:08
*** openstack changes topic to "stein-1 requests (Meeting topic: releaseteam)"15:08
smcginnisttx: Yours again...15:08
fungiso if we'd started calling ocata "lts" now, users might be incentivised to choose ocata over, say, rocky15:08
smcginnisLet's hope not.15:08
*** kailun has quit IRC15:08
ttxyes, wanted to discuss how to handle stein-1 requests... there are basically two types15:08
ttxones we triggered (the library refreshes posted by Sean)15:09
ttxones that were proposed (milestone releases)15:09
ttxFor the former we said we'd finally approve them on the 1st15:09
ttxFor the latter, there are cases where people submit them because they assume they have to15:10
smcginnisFor the ones I've seen where folks have requested b1 releases, I've just asked on the review if they actually need that and make sure they've seen the ML thread.15:10
ttxright15:10
smcginnisNot too surprisingly, a lot have not.15:10
smcginnise0ne had a good reason with horizon, and there's probably others that may still want to do a milestone release.15:10
smcginnisBut I just want to make sure they are doing it on purpose and not because they think they have to.15:11
ttxok, so the process for those is to ask for confirmation, and if confirmed just approve them without waiting for Nov 115:11
* e0ne is reading meeting log...15:11
smcginnise0ne: Sorry, not important.15:11
smcginnisJust saying how awesome you are. :)15:11
smcginnisttx: Yeah, I think that makes sense.15:11
e0nesmcginnis: :)15:12
ttxok, are you going to do that for the recently-posted ones ?15:12
smcginnisDid I miss some new one?15:12
smcginnis*ones15:12
ttxhttps://review.openstack.org/#/c/613444/15:12
ttxoh that's the only one missing15:13
ttxi can copypaste your blurb15:13
e0nesmcginnis, ttx: I had to cut stein-1 mostly because we haven't something like horizon-lib and other projects (plugins) use horizon as a library15:13
smcginnisHmm, they are cycle-with-rc, but he is proposing a full version number.15:13
diablo_rojoto clairfy for my new to releases brain- by confirmation you mean +1ed by a release liaison or PTL? Or that they intended to do a release for some reason despite not having to?15:13
*** zaitcev has quit IRC15:13
smcginnise0ne: Yeah, that made sense. We might have some similar cases with neutron I think.15:13
ttxsmcginnis: uh yes15:14
e0neAFAIR, we've got neutron-lib15:14
smcginnisdiablo_rojo: Yeah, for the ones where they are proposing a x.x.x.0b1, we just want to check with them that they are creating a milestone "beta" release on purpose.15:14
ttxsmcginnis: weird that it passes tests (final without rc)15:14
smcginnisThat there's actually a need for some downstream consumer or something for doing it.15:14
smcginnisOtherwise there's not really a need.15:14
* ttx digs deeper15:15
diablo_rojosmcginnis, got it15:15
smcginnisttx: I'm guessing we're missing some previous validation logic for -rc that we did for -milestones.15:15
smcginnisOr maybe we just never did and it was up to reviews to catch that.15:15
smcginnisamotoki: Did you need milestone-1 deliverables for all of those? And if so, did you mean to have b1 release versioning?15:16
smcginnis#link http://lists.openstack.org/pipermail/openstack-dev/2018-September/135088.html15:17
smcginnisSo we have another breadcrumb somewhere to increase odds more folks have seen that. ^15:17
smcginnisAnyway, we can follow up later.15:18
ttxok15:18
smcginnisttx: Anything more on stein-1 we should discuss?15:18
ttxno15:18
smcginnis#topic cycle-with-intermediary changes15:18
*** openstack changes topic to "cycle-with-intermediary changes (Meeting topic: releaseteam)"15:19
smcginnisSo we kind of just discussed this (ttx's first type) but wanted to still point out there are patches out there.15:19
smcginnisI skipped libs that only had <5 commits or only had zuul related commits.15:19
smcginnisI need to cleanup/rewrite my script for doing that and push that up for future use.15:20
smcginnisBut it's way too hacky in its current state.15:20
smcginnisSo far, most feedback has been positive and I got a lot of PTL/liaison +1s.15:21
ttx(no-rc is actually considered a valid case)15:21
smcginnisttx: Odd15:21
smcginnisI suppose we didn't want to paint ourselves into a corner for some odd case.15:21
ttx(only tested as part of the pre-release progression checks)15:22
smcginnisIn the commit messages for the lib releases I said we would approve them by next Thursday unless we hear yay or nay otherwise.15:22
ttx++15:22
smcginnisA few commit hash updates, but so far it's been smoother than I had expected.15:22
*** gyee has joined #openstack-meeting15:23
smcginnis#topic sem-ver patches15:23
*** openstack changes topic to "sem-ver patches (Meeting topic: releaseteam)"15:23
smcginnis#link https://review.openstack.org/#/q/topic:sem-ver15:23
smcginnisBackground on this for those that hadn't seen -15:23
*** zaitcev has joined #openstack-meeting15:23
smcginnisWith not requiring milestone releases, downstream distro packaging that works on upgrades had an issue.15:23
smcginnisPreviously they could wait until milestone 1, but with getting rid of that, waiting until RC was too long.15:24
smcginnisThe issue being the package versions need to be incremented.15:24
smcginnisWhich does happen with a beta 1 release/15:25
smcginnisSo to get the version incremented without doing a release, we can use a PBR feature where it will see the tag in the commit and calculate a higher version.15:25
smcginnisThat will now be automated for cycle-with-rc deliverables when stable branches are created.15:25
smcginnisWe normally would generate patches to update the release notes, .gitreview, etc. This will be included now.15:26
diablo_rojoHandy15:26
smcginnisSo this one time for stein, since we didn't have that automated when the stable branch for rocky was created, we needed to manually propose these patches to get them bumped.15:27
fungii'm still mildly concerned people will see those in the commit history and think it's a safe feature to rely on more generally without realizing the down-sides15:27
smcginnisDefinitely a concern.15:27
smcginnisI added a little note in the commit messages to hopefully help prevent that.15:27
fungialso very easy for those to slip through review in projects when people aren't paying super close attention to commit message footers15:27
fungiit's happened before anyway (though at least you can still push a conflicting tag and i _think_ pbr does the right thing afterward?)15:28
smcginnisI wonder if we can have some kind of automated check across all python projects to flag those or something.15:28
smcginnisMaybe we need to add a sem-unver to pbr. :)15:28
fungiyeah, it's mostly that you end up with a non-increasing version break to fix it via tags15:29
fungiwhich could get confusing, especially in continuous deployment scenarios15:29
fungiwhere your deployment automation breaks because the version number is jumping backwards15:30
smcginnisHopefully this will never happen. The sem-ver approach was the least impacting option we came up with for handling this for distros.15:30
*** onovy has joined #openstack-meeting15:31
fungiin the past we deemed it not a huge risk to just ignore the low version number problem after release because master branches generally accrue commits faster than stable branches and so will outpace them quickly enough that when someone switches from stable to master the "dev" version number increment is higher anyway15:31
*** longkb has quit IRC15:32
fungioh, right, this is because we broke that assumption by no longer merging release tags back into master15:33
fungito work around shortcomings in reno's matching logic15:33
smcginnisRed Hat at least seemed to need this to happen for their work.15:34
fungiso, yeah, i guess that's inevitable that we need to work around it somehow unless reno can be fixed to not get confused when we merge release tags into the master branch15:34
smcginnisWe can discuss more next week when Doug is back.15:34
smcginnisSince he has insight both on reno and on Red Hat's needs.15:34
smcginnis#topic Governance / Releases mismatches review15:35
*** openstack changes topic to "Governance / Releases mismatches review (Meeting topic: releaseteam)"15:35
smcginnis#link https://etherpad.openstack.org/p/UChiqxElUV15:35
smcginnis#link https://review.openstack.org/#/c/613268/15:35
smcginnisttx: Want to take this?15:35
ttxyes15:36
ttxSo... officially we are doing release management for everything official15:37
ttxBut we haven't really been checking that we actually did that15:37
ttxThere are exceptions, and it's been traditionally difficult for us to know which repos are exceptions15:38
ttxI've been introducing a change to governance to track which repos are exceptions15:38
ttx#link https://review.openstack.org/#/c/613268/15:38
ttxBUT there is a gap15:38
ttxthings that are under governance but are not really standing exceptions15:38
ttxand that we do not handle release for15:38
ttxThat is what is listed on https://etherpad.openstack.org/p/UChiqxElUV15:39
*** hle2 has quit IRC15:39
ttxIn a lot of cases it's just recent repos, for which we should probably have a skeleton deliverable file in openstack/releases15:39
ttxIn some other cases it's an abandoned repo, for which we might want to add another keyword ("abandoned"15:40
ttxin order to track them as well15:40
ttxIn yet other cases it's just things that are cycle-independent and released EXTREMELY rarely15:40
ttxas in were never released since we created the openstack/releases repo15:41
ttxThat still leaves corner cases, for which I could use help investigating15:41
ttxLike openstackclient, sounds like something we should release, but we do not, and I'm sure there is a good explanation for it15:41
smcginnisFor the abandoned ones, it might make sense to just get those repos removed as "official". They can always be added back later if the team picks them up again.15:41
ttxI bet we'll uncover dead things that need to be removed.15:42
smcginnisNot sure, but I think there was a plan to migrate python-openstackclient to openstackclient?15:42
ttxLike some of those xstatic repos were never tagged15:42
smcginnisMaybe another "abandoned" case?15:42
ttxI have a script to generate that list, it has exceptions (like all of Infra repos), but would like to get most of the list categorized otherwise15:43
*** ttsiouts has quit IRC15:43
ttxI bet a lot of them are just release-management:none cases but that would be good to document them once and for all15:44
smcginnisAgree completely.15:44
*** apetrich has quit IRC15:44
smcginnisAnd having it in an easily consumable place like this makes a lot of sense to me. We can build scripting around it and validation checks.15:44
ttxbecause I'm pretty sure I asked about heat-cfnclient before and got an answer and just forgot about it15:44
fungithe infra repo exceptions at least should be able to go away once we separate those repos out with namespace reorg or whatever15:45
fungi(as part of opendev migration)15:45
ttxAlso we might uncover real offenders (things that are official and yet not under openstack/releases) which we should definitely fix, if only so that those appear on releases.o.o15:45
ttxfungi: yes that's why I wildcarded them out15:45
smcginnisTangential, but what ever happened to the namespace flattening talk? Are we just going to recategorize things more appropriately now?15:46
fungismcginnis: the spec is still out there, but we may want to reintroduce namespacing to separate repos for different communities under opendev now15:46
ttxgood question, it's been put in hold pattern while we do opendev15:47
fungiunfortunately it would be yet another major project renaming for unofficial projects15:47
smcginnisYeah, I think things have evolved somewhat.15:47
fungibut might actually eventually become that being in the "openstack" namespace really means what people thought it meant15:47
ttxback on topic, I'd welcome help on that categorization etherpad, so if you end up talking to one of those PTLs, be sure to ask them about their repos if listed15:48
smcginnisWith random libs being pushed on the oslo team, it might make sense to have a neutral zone territory for some common libs and unofficial things.15:48
smcginnisttx: Sorry15:48
fungibecause to do things like handing over management of github org/replication and white-labeling services like the git server farm means our viable options are either run separate gerrits and find a way to move projects between them (really messy) or just make renames less painful15:49
smcginnisttx: Should we send that to the ML to try to get more input?15:49
ttxsmcginnis: it's tricky because those are all corner cases. I'd rather engage individually. It's not really that urgent15:49
smcginnisTrue, good point.15:49
ttxAlso it's all exceptions to a TC rule (which is that the RelMgt team handles releases of official things), so it's good to document that on a file that is approved by TC members15:51
smcginnisVery good point. And I think if any new exceptions are added, then it is appropriate for that to have to go through a TC vote to happen.15:51
smcginnisWe also need to clean up more project ACLs, but that will be a side effect output from this.15:52
ttxyes, knowing where we are alloed to step in and where we should just let go will be very useful15:52
smcginnisAnd cause less friction.15:52
smcginnisHopefully.15:52
ttxI did add the etherpad review to next week's tasks15:53
smcginnisOK, great.15:54
smcginnisAnything else to discuss today?15:54
ttxI'll cover the bulk of it, but if you talk to PTLs, just ask them about their repos in that file15:54
ttxnothing else15:55
smcginnisSounds like a good plan to me.15:55
smcginnisOK, most of the hour used. Let's wrap it up.15:55
smcginnisThanks everyone.15:55
diablo_rojoThanks smcginnis :)15:55
smcginnis#endmeeting15:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:55
openstackMeeting ended Fri Oct 26 15:55:51 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2018/releaseteam.2018-10-26-15.01.html15:55
ttx++15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2018/releaseteam.2018-10-26-15.01.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2018/releaseteam.2018-10-26-15.01.log.html15:55
fungithanks smcginnis15:56
*** a-pugachev_ has joined #openstack-meeting15:57
smcginnisThanks everyone for attending.15:57
*** apetrich has joined #openstack-meeting15:58
*** Chenjie has quit IRC15:59
*** a-pugachev has quit IRC15:59
*** a-pugachev_ is now known as a-pugachev15:59
*** lpetrut has quit IRC16:00
*** e0ne has quit IRC16:10
*** kopecmartin is now known as kopecmartin|off16:13
*** bnemec is now known as beekneemech16:13
*** fried_rice is now known as fried_rolls16:20
*** mjturek has joined #openstack-meeting16:29
*** aojeagarcia has quit IRC16:30
*** iyamahat has quit IRC16:31
*** mriedem is now known as mriedem_away16:34
*** a-pugachev has quit IRC16:38
*** yamahata has quit IRC16:39
*** iyamahat has joined #openstack-meeting16:55
*** iyamahat_ has joined #openstack-meeting16:58
*** yamahata has joined #openstack-meeting16:58
*** bauwser is now known as bauzas17:01
*** iyamahat has quit IRC17:01
*** njohnston has quit IRC17:01
*** lpetrut has joined #openstack-meeting17:08
*** cloudrancher has quit IRC17:14
*** cloudrancher has joined #openstack-meeting17:15
*** jamesmcarthur has quit IRC17:16
*** ralonsoh has quit IRC17:23
*** electrofelix has quit IRC17:32
*** bobh has quit IRC17:36
*** lbragstad is now known as elbragstad17:37
*** Swami has joined #openstack-meeting17:38
*** njohnston has joined #openstack-meeting17:46
*** jamesmcarthur has joined #openstack-meeting18:01
*** armstrong has quit IRC18:10
*** munimeha1 has quit IRC18:11
*** mriedem_away is now known as mriedem18:28
*** munimeha1 has joined #openstack-meeting18:33
*** apetrich has quit IRC18:34
*** apetrich has joined #openstack-meeting18:35
*** e0ne has joined #openstack-meeting18:35
*** jamesmcarthur has quit IRC18:48
*** armax has quit IRC19:05
*** fried_rolls is now known as efried19:07
*** erlon has quit IRC19:09
*** efried is now known as fried_rice19:11
*** e0ne has quit IRC19:14
*** toabctl has quit IRC19:19
*** e0ne has joined #openstack-meeting19:19
*** toabctl has joined #openstack-meeting19:21
*** e0ne has quit IRC19:23
*** lpetrut has quit IRC19:37
*** jamesmcarthur has joined #openstack-meeting19:46
*** cloudrancher has quit IRC19:55
*** cloudrancher has joined #openstack-meeting19:55
*** mjturek has quit IRC20:26
*** armax has joined #openstack-meeting20:28
*** jamesmcarthur has quit IRC20:29
*** imacdonn has quit IRC20:32
*** imacdonn has joined #openstack-meeting20:32
*** mjturek has joined #openstack-meeting20:35
*** openstack has joined #openstack-meeting20:43
*** ChanServ sets mode: +o openstack20:43
*** ttsiouts has joined #openstack-meeting20:46
*** awaugama has quit IRC20:47
*** munimeha1 has quit IRC20:53
*** ttsiouts has quit IRC20:58
*** raildo has quit IRC21:08
*** dustins has quit IRC21:11
*** eharney has quit IRC21:12
*** jamesmcarthur has joined #openstack-meeting21:13
*** jamesmcarthur has quit IRC21:24
*** jbadiapa has quit IRC21:34
*** mjturek has quit IRC21:50
*** mriedem has quit IRC21:52
*** armax has quit IRC21:53
*** tpsilva has quit IRC22:27
*** bobh has joined #openstack-meeting22:28
*** armax has joined #openstack-meeting22:59
*** hongbin has quit IRC23:01
*** pcaruana has quit IRC23:10
*** diablo_rojo has quit IRC23:40
*** Swami has quit IRC23:43
*** rcernin has joined #openstack-meeting23:44
*** jesusaur has quit IRC23:45
*** rcernin has quit IRC23:51
*** gyee has quit IRC23:55

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