*** darvon has joined #openstack-meeting | 00:21 | |
*** erlon has joined #openstack-meeting | 00:24 | |
*** Liang__ has joined #openstack-meeting | 00:32 | |
*** Liang__ is now known as LiangFang | 00:32 | |
*** tetsuro has joined #openstack-meeting | 00:40 | |
*** longkb has joined #openstack-meeting | 00:40 | |
*** diablo_rojo has quit IRC | 00:55 | |
*** jamesmcarthur has joined #openstack-meeting | 01:03 | |
*** jamesmcarthur has quit IRC | 01:05 | |
*** jamesmcarthur has joined #openstack-meeting | 01:05 | |
*** fanzhang has joined #openstack-meeting | 01:07 | |
*** jamesmcarthur has quit IRC | 01:35 | |
*** mhen has quit IRC | 01:40 | |
*** mhen has joined #openstack-meeting | 01:42 | |
*** lbragstad has quit IRC | 01:49 | |
*** lbragstad has joined #openstack-meeting | 01:49 | |
*** ykatabam has joined #openstack-meeting | 01:54 | |
*** rcernin has joined #openstack-meeting | 01:55 | |
*** yamahata has quit IRC | 01:55 | |
*** iyamahat_ has quit IRC | 01:56 | |
*** cloudrancher has quit IRC | 02:03 | |
*** cloudrancher has joined #openstack-meeting | 02:04 | |
*** jamesmcarthur has joined #openstack-meeting | 02:05 | |
*** jamesmcarthur has quit IRC | 02:09 | |
*** bobh has joined #openstack-meeting | 02:14 | |
*** bobh has quit IRC | 03:10 | |
*** lpetrut has joined #openstack-meeting | 03:58 | |
*** tetsuro has quit IRC | 04:04 | |
*** hle2 has joined #openstack-meeting | 04:20 | |
*** janki has joined #openstack-meeting | 04:22 | |
*** lpetrut has quit IRC | 04:34 | |
*** yamahata has joined #openstack-meeting | 05:02 | |
*** iyamahat has joined #openstack-meeting | 05:02 | |
*** yamamoto has quit IRC | 05:26 | |
*** yamamoto has joined #openstack-meeting | 05:26 | |
*** hle2 has quit IRC | 05:44 | |
*** Luzi has joined #openstack-meeting | 05:45 | |
*** kopecmartin has joined #openstack-meeting | 05:50 | |
*** Liang__ has joined #openstack-meeting | 05:50 | |
*** jgriffit1 has joined #openstack-meeting | 05:51 | |
*** evrardjp_ has joined #openstack-meeting | 05:51 | |
*** hemna_ has joined #openstack-meeting | 05:54 | |
*** ianw_ has joined #openstack-meeting | 05:54 | |
*** dims_ has joined #openstack-meeting | 05:54 | |
*** LiangFang has quit IRC | 05:55 | |
*** erlon has quit IRC | 05:55 | |
*** apetrich has quit IRC | 05:55 | |
*** liuyulong|away has quit IRC | 05:55 | |
*** SotK has quit IRC | 05:55 | |
*** jgriffith has quit IRC | 05:55 | |
*** kopecmartin|off has quit IRC | 05:55 | |
*** dims has quit IRC | 05:55 | |
*** strigazi has quit IRC | 05:55 | |
*** hemna has quit IRC | 05:55 | |
*** evrardjp has quit IRC | 05:55 | |
*** mattoliverau has quit IRC | 05:55 | |
*** chkumar|off has quit IRC | 05:55 | |
*** ianw has quit IRC | 05:55 | |
*** Qiming has quit IRC | 05:55 | |
*** jlvillal has quit IRC | 05:55 | |
*** ianw_ is now known as ianw | 05:55 | |
*** irclogbot_1 has quit IRC | 05:58 | |
*** mhen has quit IRC | 05:59 | |
*** tetsuro has joined #openstack-meeting | 06:01 | |
*** apetrich has joined #openstack-meeting | 06:02 | |
*** erlon has joined #openstack-meeting | 06:03 | |
*** mhen has joined #openstack-meeting | 06:07 | |
*** hle2 has joined #openstack-meeting | 06:10 | |
*** hle2 has left #openstack-meeting | 06:13 | |
*** aojeagarcia has joined #openstack-meeting | 06:29 | |
*** aojea has quit IRC | 06:33 | |
*** hle2 has joined #openstack-meeting | 06:35 | |
*** hle2 has left #openstack-meeting | 06:43 | |
*** hle2 has joined #openstack-meeting | 06:43 | |
*** yamamoto has quit IRC | 06:53 | |
*** yamamoto has joined #openstack-meeting | 06:53 | |
*** yamamoto has quit IRC | 06:53 | |
*** yamamoto has joined #openstack-meeting | 06:54 | |
*** njohnston has quit IRC | 07:06 | |
*** ykatabam has quit IRC | 07:09 | |
*** njohnston has joined #openstack-meeting | 07:11 | |
*** erlon has quit IRC | 07:12 | |
*** rcernin has quit IRC | 07:22 | |
*** strigazi has joined #openstack-meeting | 07:26 | |
*** bauzas is now known as bauwser | 07:35 | |
*** evrardjp_ is now known as evrardjp | 07:37 | |
*** rossella_s has joined #openstack-meeting | 08:00 | |
*** SotK has joined #openstack-meeting | 08:06 | |
*** ttsiouts has joined #openstack-meeting | 08:33 | |
*** rfolco|rover has quit IRC | 08:35 | |
*** ttsiouts has quit IRC | 08:38 | |
*** tetsuro has quit IRC | 08:38 | |
*** ttsiouts has joined #openstack-meeting | 08:53 | |
*** ttsiouts has quit IRC | 09:14 | |
*** ttsiouts has joined #openstack-meeting | 09:15 | |
*** e0ne has joined #openstack-meeting | 09:16 | |
*** Qiming has joined #openstack-meeting | 09:35 | |
*** yamamoto has quit IRC | 09:36 | |
*** electrofelix has joined #openstack-meeting | 09:58 | |
*** erlon has joined #openstack-meeting | 10:07 | |
*** lpetrut has joined #openstack-meeting | 10:11 | |
*** ssbarnea has joined #openstack-meeting | 10:11 | |
*** jamesmcarthur has joined #openstack-meeting | 10:12 | |
*** ttsiouts has quit IRC | 10:15 | |
*** jamesmcarthur has quit IRC | 10:16 | |
*** Liang__ has quit IRC | 10:31 | |
*** ssbarnea has quit IRC | 10:49 | |
*** e0ne has quit IRC | 10:51 | |
*** e0ne_ has joined #openstack-meeting | 10:52 | |
*** a-pugachev has joined #openstack-meeting | 10:54 | |
*** tridde is now known as trident | 11:17 | |
*** EmilienM is now known as EvilienM | 11:24 | |
*** janki has quit IRC | 11:36 | |
*** ttsiouts has joined #openstack-meeting | 11:48 | |
*** longkb has quit IRC | 11:49 | |
*** yamamoto has joined #openstack-meeting | 12:02 | |
*** liuyulong has joined #openstack-meeting | 12:09 | |
*** raildo has joined #openstack-meeting | 12:13 | |
*** eharney has joined #openstack-meeting | 12:25 | |
*** bobh has joined #openstack-meeting | 12:26 | |
*** e0ne_ has quit IRC | 12:26 | |
*** yamamoto has quit IRC | 12:32 | |
*** rfolco|rover has joined #openstack-meeting | 12:33 | |
*** njohnston has quit IRC | 12:39 | |
*** jamesmcarthur has joined #openstack-meeting | 12:47 | |
*** ttsiouts has quit IRC | 12:51 | |
*** yamamoto has joined #openstack-meeting | 12:55 | |
*** dustins has joined #openstack-meeting | 13:07 | |
*** tpsilva has joined #openstack-meeting | 13:09 | |
*** Liang__ has joined #openstack-meeting | 13:12 | |
*** mriedem has joined #openstack-meeting | 13:19 | |
*** efried is now known as fried_rice | 13:23 | |
*** e0ne has joined #openstack-meeting | 13:25 | |
*** cloudrancher has quit IRC | 13:31 | |
*** cloudrancher has joined #openstack-meeting | 13:32 | |
*** jamesmcarthur has quit IRC | 13:46 | |
*** awaugama has joined #openstack-meeting | 13:53 | |
*** bnemec has joined #openstack-meeting | 13:54 | |
*** munimeha1 has joined #openstack-meeting | 13:57 | |
*** mlavalle has joined #openstack-meeting | 14:00 | |
mlavalle | #startmeeting neutron_drivers | 14:00 |
---|---|---|
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
*** openstack changes topic to " (Meeting topic: neutron_drivers)" | 14:00 | |
openstack | The meeting name has been set to 'neutron_drivers' | 14:00 |
yamamoto | hi | 14:01 |
mlavalle | hi | 14:01 |
amotoki | hi | 14:02 |
hle2 | hi | 14:02 |
kailun | hi | 14:02 |
*** Chenjie has joined #openstack-meeting | 14:02 | |
bcafarel | sorry I kept a few drivers busy, they should get in soon | 14:02 |
mlavalle | bcafarel: LOL | 14:02 |
slaweq | hi | 14:02 |
haleyb | hi | 14:03 |
mlavalle | ok, we have quorum now | 14:03 |
*** Luzi has quit IRC | 14:03 | |
mlavalle | hle2, kailun: are you here to discuss something with the team? | 14:04 |
*** njohnston has joined #openstack-meeting | 14:04 | |
njohnston | o/ | 14:05 |
kailun | mlavalle: yes, I have one RFE to discuss | 14:05 |
mlavalle | kailun: do you have the pointer? | 14:05 |
kailun | https://bugs.launchpad.net/neutron/+bug/1795212 | 14:05 |
openstack | Launchpad 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 |
kailun | And the patch is available @ https://review.openstack.org/#/c/609463/ | 14:06 |
kailun | I'd like to have the idea triaged and move forward :) | 14:06 |
*** longkb has joined #openstack-meeting | 14:08 | |
Chenjie | Hello everyone, I have an RFE that I want to discuss. | 14:10 |
slaweq | kailun: I think I don't understand bug You described there | 14:10 |
Chenjie | https://bugs.launchpad.net/neutron/+bug/1793653 | 14:10 |
openstack | Launchpad 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 leakypipes | 14:10 | |
*** artom is now known as temka | 14:10 | |
Chenjie | The patch is available https://review.openstack.org/#/c/599319/ | 14:11 |
slaweq | host 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-meeting | 14:12 | |
mlavalle | I see haleyb is co-author of the patch | 14:14 |
kailun | slaweq: the rpc sent to the agent before the agent is down | 14:15 |
haleyb | well, i helped update it but it wasn't my original idea | 14:15 |
slaweq | and how that short (I guess) delay can help to solve this problem? | 14:15 |
kailun | slawek: a schedule rpc for instance | 14:15 |
slaweq | shouldn't it be solved e.g. by smaller ttl time for messages in rabbitmq? | 14:16 |
*** onovy has quit IRC | 14:16 | |
kailun | slaweq: 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 delay | 14:18 |
haleyb | i 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 |
amotoki | IIRC, when dhcp-agent is restarted, full sync will be done, right? | 14:18 |
amotoki | If 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 |
kailun | slaweq: ttl is another way IMO | 14:18 |
mlavalle | amotoki: yes | 14:18 |
amotoki | I 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-meeting | 14:20 | |
slaweq | amotoki: ok, I understand now "timestamp" solution | 14:20 |
amotoki | kailun: is my understanding correct? | 14:20 |
slaweq | but proposed patch was doing this second approach (delay): https://review.openstack.org/#/c/609463/ | 14:20 |
slaweq | and 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-meeting | 14:21 | |
*** stephenfin is now known as finucannot | 14:22 | |
haleyb | would the other alternative be to use the Resource queue like the l3-agent? | 14:22 |
amotoki | yeah, I see it too. | 14:22 |
kailun | amotoki: yes | 14:23 |
amotoki | what I am not sure so far is what kind of corner cases and negative behaviors could happen (even with full sync) | 14:23 |
kailun | sorry guys my connection is unstable :) | 14:23 |
amotoki | kailun: 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 |
slaweq | haleyb: yes, Resource queue with ExclusiveResourceProcessor should maybe be better idea IMO | 14:26 |
kailun | amotoki: dhcp does not have a timestamp support right now, correct? | 14:26 |
haleyb | slaweq: that was one reason i moved it from under l3 | 14:26 |
kailun | amotoki: while l3 agent has one I guess | 14:26 |
amotoki | kailun: i cannot answer it immediately. does anyone know it? | 14:27 |
slaweq | also, one more question | 14:27 |
slaweq | I don't remember exactly but in some (very) old releases rpc queues which agent's registered had some random id | 14:28 |
kailun | slaweq: I also tried to evaluate timestamp and the delay I proposed, I did not see a obvious drawback | 14:28 |
slaweq | so when agent was e.g. restarted it created new queue and would not consume messages from this old one | 14:28 |
slaweq | isn't it like that anymore? | 14:28 |
kailun | slaweq: I don't have an answer to this one, I can double check | 14:29 |
slaweq | kailun: would be good IMO to check that | 14:30 |
amotoki | it seems we need to clarify failure modes in question, i.e., what actually happens before discussing a solution. | 14:30 |
kailun | slaweq: sure I'll do that | 14:30 |
slaweq | amotoki++ | 14:30 |
kailun | amotoki: agree, let me follow up with this one | 14:32 |
mlavalle | kailun: based on this discussion, let's continue the conversation in the RFE | 14:32 |
amotoki | slaweq and I raises several questions. let's follow them up on the bug | 14:32 |
slaweq | amotoki: mlavalle: I agree, let's follow up on RFE | 14:33 |
kailun | mlavalle: slaweq: amotoki: haleyb: let's follow them up on the bug | 14:33 |
mlavalle | kailun: thanks | 14:33 |
amotoki | kailun: thanks for raising this | 14:34 |
mlavalle | kailun: and thanks for your patches. I think we merged one yesterday, didn't we? | 14:34 |
mlavalle | also DHCP | 14:34 |
kailun | yes thank you all for the review and discussion | 14:35 |
mlavalle | I liked the way you used the Event object ;-) | 14:35 |
mlavalle | and the throttling, which was a concern when we approved that RFE | 14:36 |
kailun | :) every concern has a solution | 14:37 |
mlavalle | ok, now let's move on to https://bugs.launchpad.net/neutron/+bug/1793653 | 14:38 |
openstack | Launchpad bug 1793653 in neutron "[RFE] Enable other subprojects to extend l2pop fdb information" [Wishlist,In progress] - Assigned to ChenjieXu (midone) | 14:38 |
Chenjie | mlavalle: thanks! | 14:38 |
mlavalle | Chenjie: 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 screen | 14:39 |
mlavalle | but apparently you pushed a patch and the status was changed | 14:40 |
mlavalle | that's ok | 14:40 |
mlavalle | The leasson for us is we need to update that screening criteria | 14:40 |
Chenjie | mlavalle: sorry for that! | 14:40 |
mlavalle | Chenjie: no worries. it's really a lesson for me that I need to improve that screening criteria | 14:41 |
amotoki | regarding 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 |
mlavalle | amotoki: yeah, but this one slipped through the cracks somehow | 14:42 |
mlavalle | It didn't show up yesterday when I was preparing for the meeting | 14:42 |
mlavalle | Chenjie: anyways, the upshot is that we may finish reviewing your rfe today and we would continue the discussion in the RFE clarifying | 14:44 |
Chenjie | mlavalle: thank you very much! | 14:45 |
Chenjie | thank you all! | 14:45 |
mlavalle | Chenjie: thanks for your submission, first of all | 14:46 |
mlavalle | Chenjie: question: is this being proposed in the context of bgpvpn-networking? or it is just an example? | 14:46 |
amotoki | we 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 |
Chenjie | mlavalle: Yes, it is. But this can be used by other subprojects. | 14:48 |
*** Liang__ is now known as LiangFang | 14:49 | |
amotoki | Chenjie: are there any usecases in other subprojects in your mind? | 14:49 |
munimeha1 | hi | 14:49 |
amotoki | I understand it can potentially be used by other projects of course | 14:49 |
mlavalle | amotoki, haleyb, slaweq, yamamoto: here's the figure mentioned in the rfe: https://launchpadlibrarian.net/389540006/rfe_EXTEND_L2POP_FDB_INFORMATION.PNG | 14:50 |
Chenjie | amotoki: 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-meeting | 14:51 | |
*** ssbarnea|bkp2 has quit IRC | 14:51 | |
Chenjie | amotoki: yes, other projects can use this. | 14:51 |
amotoki | Chenjie: thanks, I see. | 14:52 |
Chenjie | amotoki: the name should be changed to "Enable other projects to extend l2pop fdb information"? | 14:52 |
*** rossella_s has quit IRC | 14:53 | |
amotoki | Chenjie: 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 |
amotoki | otherwise, the current title sounds good | 14:54 |
mlavalle | yeah, the title looks good to me. don't worry about it | 14:54 |
amotoki | Chenjie: let's understand and discuss the current usecase first. | 14:54 |
Chenjie | thanks! | 14:55 |
liuyulong | slaweq, 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 |
openstack | Launchpad 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 |
liuyulong | And here: https://review.openstack.org/#/c/612969/ | 14:56 |
yamamoto | does bgpvpn assume l2-agent based networks? | 14:56 |
slaweq | liuyulong: lets follows mlavalle's order in the meeting - he is chair here :) | 14:57 |
mlavalle | Chenjie: I went over the your proposal and in principle it makes sense to me. I would like to go over it again | 14:59 |
Chenjie | yamamoto: Do you mean networking-bgpvpn uses l2-agent(ovs and linuxbridge agent)? | 14:59 |
Chenjie | mlavalle: Thank you very much! | 14:59 |
mlavalle | and we can retake it next week | 14:59 |
*** ssbarnea has joined #openstack-meeting | 15:00 | |
*** diablo_rojo has joined #openstack-meeting | 15:00 | |
mlavalle | we ran out of time today | 15:00 |
yamamoto | i meant if it didn't work for other l2 impl like odl | 15:00 |
slaweq | thx, and have a great weekend guys :) | 15:00 |
slaweq | o/ | 15:00 |
yamamoto | i'll ask on rfe | 15:00 |
*** dansmith is now known as SteelyDan | 15:01 | |
mlavalle | also if you have time, please look at https://review.openstack.org/#/c/574477 | 15:01 |
Chenjie | mlavalle: thank you very much! | 15:01 |
mlavalle | spec is ready for next rund of review | 15:01 |
mlavalle | #endmeeting | 15:01 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:01 | |
openstack | Meeting ended Fri Oct 26 15:01:23 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:01 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-10-26-14.00.html | 15:01 |
yamamoto | good night | 15:01 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-10-26-14.00.txt | 15:01 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-10-26-14.00.log.html | 15:01 |
amotoki | thanks | 15:01 |
Chenjie | yamamoto: Ok, thank you for your reviewing! | 15:01 |
smcginnis | #startmeeting releaseteam | 15:01 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
*** openstack changes topic to " (Meeting topic: releaseteam)" | 15:01 | |
openstack | The meeting name has been set to 'releaseteam' | 15:01 |
fungi | howdy! | 15:01 |
smcginnis | Morning fungi | 15:01 |
diablo_rojo | Hello :) | 15:02 |
smcginnis | #link https://etherpad.openstack.org/p/stein-relmgt-tracking Agenda - R-24, ~line 113 | 15:02 |
smcginnis | Hey diablo_rojo, long time no see. | 15:02 |
ttx | o/ | 15:02 |
armstrong | Hello | 15:03 |
smcginnis | OK, that's probably everyone for today. | 15:03 |
smcginnis | #topic | 15:03 |
*** openstack changes topic to " (Meeting topic: releaseteam)" | 15:03 | |
smcginnis | Mark Ocata as extended maintenance | 15:03 |
smcginnis | Grr | 15:03 |
smcginnis | #topic Mark Ocata as extended maintenance | 15: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 |
smcginnis | ttx: I think you added this? | 15:03 |
ttx | yes for some reason that one does not appear on the dashboard so we did not approve it | 15:04 |
ttx | any reason we should not approve it? | 15:04 |
smcginnis | I don't think so. THere was some question of teams making that extended-maintenance decision, | 15:04 |
smcginnis | But as far as the official release page, I think it should reflect that that release is now in e-m mode. | 15:04 |
ttx | ok approving now | 15:05 |
smcginnis | Yay, one more out my queue. | 15:05 |
fungi | speaking 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 |
smcginnis | Anything more we need to do as the release team for that? Or leave it to tonyb for any follow up. | 15:05 |
ttx | nothing | 15:06 |
smcginnis | fungi: Oh, interesting. They're coming to the same conclusions on wording? | 15:06 |
fungi | yeah, specifically that "lts" in the linux kernel and ubuntu communities means specific releases that get longer official maintenance | 15:06 |
*** mlavalle has left #openstack-meeting | 15:06 | |
fungi | whereas 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 so | 15:07 |
smcginnis | I 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 |
fungi | so users are installing debian "lts" releases thinking that means longer support, when it actually means they're just installing outdated versions | 15:07 |
smcginnis | Makes sense. | 15:08 |
smcginnis | Anyway... | 15:08 |
smcginnis | #topic stein-1 requests | 15:08 |
*** openstack changes topic to "stein-1 requests (Meeting topic: releaseteam)" | 15:08 | |
smcginnis | ttx: Yours again... | 15:08 |
fungi | so if we'd started calling ocata "lts" now, users might be incentivised to choose ocata over, say, rocky | 15:08 |
smcginnis | Let's hope not. | 15:08 |
*** kailun has quit IRC | 15:08 | |
ttx | yes, wanted to discuss how to handle stein-1 requests... there are basically two types | 15:08 |
ttx | ones we triggered (the library refreshes posted by Sean) | 15:09 |
ttx | ones that were proposed (milestone releases) | 15:09 |
ttx | For the former we said we'd finally approve them on the 1st | 15:09 |
ttx | For the latter, there are cases where people submit them because they assume they have to | 15:10 |
smcginnis | For 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 |
ttx | right | 15:10 |
smcginnis | Not too surprisingly, a lot have not. | 15:10 |
smcginnis | e0ne had a good reason with horizon, and there's probably others that may still want to do a milestone release. | 15:10 |
smcginnis | But I just want to make sure they are doing it on purpose and not because they think they have to. | 15:11 |
ttx | ok, so the process for those is to ask for confirmation, and if confirmed just approve them without waiting for Nov 1 | 15:11 |
* e0ne is reading meeting log... | 15:11 | |
smcginnis | e0ne: Sorry, not important. | 15:11 |
smcginnis | Just saying how awesome you are. :) | 15:11 |
smcginnis | ttx: Yeah, I think that makes sense. | 15:11 |
e0ne | smcginnis: :) | 15:12 |
ttx | ok, are you going to do that for the recently-posted ones ? | 15:12 |
smcginnis | Did I miss some new one? | 15:12 |
smcginnis | *ones | 15:12 |
ttx | https://review.openstack.org/#/c/613444/ | 15:12 |
ttx | oh that's the only one missing | 15:13 |
ttx | i can copypaste your blurb | 15:13 |
e0ne | smcginnis, ttx: I had to cut stein-1 mostly because we haven't something like horizon-lib and other projects (plugins) use horizon as a library | 15:13 |
smcginnis | Hmm, they are cycle-with-rc, but he is proposing a full version number. | 15:13 |
diablo_rojo | to 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 IRC | 15:13 | |
smcginnis | e0ne: Yeah, that made sense. We might have some similar cases with neutron I think. | 15:13 |
ttx | smcginnis: uh yes | 15:14 |
e0ne | AFAIR, we've got neutron-lib | 15:14 |
smcginnis | diablo_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 |
ttx | smcginnis: weird that it passes tests (final without rc) | 15:14 |
smcginnis | That there's actually a need for some downstream consumer or something for doing it. | 15:14 |
smcginnis | Otherwise there's not really a need. | 15:14 |
* ttx digs deeper | 15:15 | |
diablo_rojo | smcginnis, got it | 15:15 |
smcginnis | ttx: I'm guessing we're missing some previous validation logic for -rc that we did for -milestones. | 15:15 |
smcginnis | Or maybe we just never did and it was up to reviews to catch that. | 15:15 |
smcginnis | amotoki: 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.html | 15:17 |
smcginnis | So we have another breadcrumb somewhere to increase odds more folks have seen that. ^ | 15:17 |
smcginnis | Anyway, we can follow up later. | 15:18 |
ttx | ok | 15:18 |
smcginnis | ttx: Anything more on stein-1 we should discuss? | 15:18 |
ttx | no | 15:18 |
smcginnis | #topic cycle-with-intermediary changes | 15:18 |
*** openstack changes topic to "cycle-with-intermediary changes (Meeting topic: releaseteam)" | 15:19 | |
smcginnis | So we kind of just discussed this (ttx's first type) but wanted to still point out there are patches out there. | 15:19 |
smcginnis | I skipped libs that only had <5 commits or only had zuul related commits. | 15:19 |
smcginnis | I need to cleanup/rewrite my script for doing that and push that up for future use. | 15:20 |
smcginnis | But it's way too hacky in its current state. | 15:20 |
smcginnis | So 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 |
smcginnis | ttx: Odd | 15:21 |
smcginnis | I 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 |
smcginnis | In 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 |
smcginnis | A few commit hash updates, but so far it's been smoother than I had expected. | 15:22 |
*** gyee has joined #openstack-meeting | 15:23 | |
smcginnis | #topic sem-ver patches | 15:23 |
*** openstack changes topic to "sem-ver patches (Meeting topic: releaseteam)" | 15:23 | |
smcginnis | #link https://review.openstack.org/#/q/topic:sem-ver | 15:23 |
smcginnis | Background on this for those that hadn't seen - | 15:23 |
*** zaitcev has joined #openstack-meeting | 15:23 | |
smcginnis | With not requiring milestone releases, downstream distro packaging that works on upgrades had an issue. | 15:23 |
smcginnis | Previously they could wait until milestone 1, but with getting rid of that, waiting until RC was too long. | 15:24 |
smcginnis | The issue being the package versions need to be incremented. | 15:24 |
smcginnis | Which does happen with a beta 1 release/ | 15:25 |
smcginnis | So 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 |
smcginnis | That will now be automated for cycle-with-rc deliverables when stable branches are created. | 15:25 |
smcginnis | We normally would generate patches to update the release notes, .gitreview, etc. This will be included now. | 15:26 |
diablo_rojo | Handy | 15:26 |
smcginnis | So 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 |
fungi | i'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-sides | 15:27 |
smcginnis | Definitely a concern. | 15:27 |
smcginnis | I added a little note in the commit messages to hopefully help prevent that. | 15:27 |
fungi | also very easy for those to slip through review in projects when people aren't paying super close attention to commit message footers | 15:27 |
fungi | it'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 |
smcginnis | I wonder if we can have some kind of automated check across all python projects to flag those or something. | 15:28 |
smcginnis | Maybe we need to add a sem-unver to pbr. :) | 15:28 |
fungi | yeah, it's mostly that you end up with a non-increasing version break to fix it via tags | 15:29 |
fungi | which could get confusing, especially in continuous deployment scenarios | 15:29 |
fungi | where your deployment automation breaks because the version number is jumping backwards | 15:30 |
smcginnis | Hopefully 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-meeting | 15:31 | |
fungi | in 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 anyway | 15:31 |
*** longkb has quit IRC | 15:32 | |
fungi | oh, right, this is because we broke that assumption by no longer merging release tags back into master | 15:33 |
fungi | to work around shortcomings in reno's matching logic | 15:33 |
smcginnis | Red Hat at least seemed to need this to happen for their work. | 15:34 |
fungi | so, 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 branch | 15:34 |
smcginnis | We can discuss more next week when Doug is back. | 15:34 |
smcginnis | Since he has insight both on reno and on Red Hat's needs. | 15:34 |
smcginnis | #topic Governance / Releases mismatches review | 15:35 |
*** openstack changes topic to "Governance / Releases mismatches review (Meeting topic: releaseteam)" | 15:35 | |
smcginnis | #link https://etherpad.openstack.org/p/UChiqxElUV | 15:35 |
smcginnis | #link https://review.openstack.org/#/c/613268/ | 15:35 |
smcginnis | ttx: Want to take this? | 15:35 |
ttx | yes | 15:36 |
ttx | So... officially we are doing release management for everything official | 15:37 |
ttx | But we haven't really been checking that we actually did that | 15:37 |
ttx | There are exceptions, and it's been traditionally difficult for us to know which repos are exceptions | 15:38 |
ttx | I've been introducing a change to governance to track which repos are exceptions | 15:38 |
ttx | #link https://review.openstack.org/#/c/613268/ | 15:38 |
ttx | BUT there is a gap | 15:38 |
ttx | things that are under governance but are not really standing exceptions | 15:38 |
ttx | and that we do not handle release for | 15:38 |
ttx | That is what is listed on https://etherpad.openstack.org/p/UChiqxElUV | 15:39 |
*** hle2 has quit IRC | 15:39 | |
ttx | In a lot of cases it's just recent repos, for which we should probably have a skeleton deliverable file in openstack/releases | 15:39 |
ttx | In some other cases it's an abandoned repo, for which we might want to add another keyword ("abandoned" | 15:40 |
ttx | in order to track them as well | 15:40 |
ttx | In yet other cases it's just things that are cycle-independent and released EXTREMELY rarely | 15:40 |
ttx | as in were never released since we created the openstack/releases repo | 15:41 |
ttx | That still leaves corner cases, for which I could use help investigating | 15:41 |
ttx | Like openstackclient, sounds like something we should release, but we do not, and I'm sure there is a good explanation for it | 15:41 |
smcginnis | For 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 |
ttx | I bet we'll uncover dead things that need to be removed. | 15:42 |
smcginnis | Not sure, but I think there was a plan to migrate python-openstackclient to openstackclient? | 15:42 |
ttx | Like some of those xstatic repos were never tagged | 15:42 |
smcginnis | Maybe another "abandoned" case? | 15:42 |
ttx | I 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 otherwise | 15:43 |
*** ttsiouts has quit IRC | 15:43 | |
ttx | I bet a lot of them are just release-management:none cases but that would be good to document them once and for all | 15:44 |
smcginnis | Agree completely. | 15:44 |
*** apetrich has quit IRC | 15:44 | |
smcginnis | And 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 |
ttx | because I'm pretty sure I asked about heat-cfnclient before and got an answer and just forgot about it | 15:44 |
fungi | the infra repo exceptions at least should be able to go away once we separate those repos out with namespace reorg or whatever | 15:45 |
fungi | (as part of opendev migration) | 15:45 |
ttx | Also 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.o | 15:45 |
ttx | fungi: yes that's why I wildcarded them out | 15:45 |
smcginnis | Tangential, but what ever happened to the namespace flattening talk? Are we just going to recategorize things more appropriately now? | 15:46 |
fungi | smcginnis: the spec is still out there, but we may want to reintroduce namespacing to separate repos for different communities under opendev now | 15:46 |
ttx | good question, it's been put in hold pattern while we do opendev | 15:47 |
fungi | unfortunately it would be yet another major project renaming for unofficial projects | 15:47 |
smcginnis | Yeah, I think things have evolved somewhat. | 15:47 |
fungi | but might actually eventually become that being in the "openstack" namespace really means what people thought it meant | 15:47 |
ttx | back 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 listed | 15:48 |
smcginnis | With 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 |
smcginnis | ttx: Sorry | 15:48 |
fungi | because 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 painful | 15:49 |
smcginnis | ttx: Should we send that to the ML to try to get more input? | 15:49 |
ttx | smcginnis: it's tricky because those are all corner cases. I'd rather engage individually. It's not really that urgent | 15:49 |
smcginnis | True, good point. | 15:49 |
ttx | Also 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 members | 15:51 |
smcginnis | Very 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 |
smcginnis | We also need to clean up more project ACLs, but that will be a side effect output from this. | 15:52 |
ttx | yes, knowing where we are alloed to step in and where we should just let go will be very useful | 15:52 |
smcginnis | And cause less friction. | 15:52 |
smcginnis | Hopefully. | 15:52 |
ttx | I did add the etherpad review to next week's tasks | 15:53 |
smcginnis | OK, great. | 15:54 |
smcginnis | Anything else to discuss today? | 15:54 |
ttx | I'll cover the bulk of it, but if you talk to PTLs, just ask them about their repos in that file | 15:54 |
ttx | nothing else | 15:55 |
smcginnis | Sounds like a good plan to me. | 15:55 |
smcginnis | OK, most of the hour used. Let's wrap it up. | 15:55 |
smcginnis | Thanks everyone. | 15:55 |
diablo_rojo | Thanks smcginnis :) | 15:55 |
smcginnis | #endmeeting | 15:55 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:55 | |
openstack | Meeting ended Fri Oct 26 15:55:51 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:55 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/releaseteam/2018/releaseteam.2018-10-26-15.01.html | 15:55 |
ttx | ++ | 15:55 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2018/releaseteam.2018-10-26-15.01.txt | 15:55 |
openstack | Log: http://eavesdrop.openstack.org/meetings/releaseteam/2018/releaseteam.2018-10-26-15.01.log.html | 15:55 |
fungi | thanks smcginnis | 15:56 |
*** a-pugachev_ has joined #openstack-meeting | 15:57 | |
smcginnis | Thanks everyone for attending. | 15:57 |
*** apetrich has joined #openstack-meeting | 15:58 | |
*** Chenjie has quit IRC | 15:59 | |
*** a-pugachev has quit IRC | 15:59 | |
*** a-pugachev_ is now known as a-pugachev | 15:59 | |
*** lpetrut has quit IRC | 16:00 | |
*** e0ne has quit IRC | 16:10 | |
*** kopecmartin is now known as kopecmartin|off | 16:13 | |
*** bnemec is now known as beekneemech | 16:13 | |
*** fried_rice is now known as fried_rolls | 16:20 | |
*** mjturek has joined #openstack-meeting | 16:29 | |
*** aojeagarcia has quit IRC | 16:30 | |
*** iyamahat has quit IRC | 16:31 | |
*** mriedem is now known as mriedem_away | 16:34 | |
*** a-pugachev has quit IRC | 16:38 | |
*** yamahata has quit IRC | 16:39 | |
*** iyamahat has joined #openstack-meeting | 16:55 | |
*** iyamahat_ has joined #openstack-meeting | 16:58 | |
*** yamahata has joined #openstack-meeting | 16:58 | |
*** bauwser is now known as bauzas | 17:01 | |
*** iyamahat has quit IRC | 17:01 | |
*** njohnston has quit IRC | 17:01 | |
*** lpetrut has joined #openstack-meeting | 17:08 | |
*** cloudrancher has quit IRC | 17:14 | |
*** cloudrancher has joined #openstack-meeting | 17:15 | |
*** jamesmcarthur has quit IRC | 17:16 | |
*** ralonsoh has quit IRC | 17:23 | |
*** electrofelix has quit IRC | 17:32 | |
*** bobh has quit IRC | 17:36 | |
*** lbragstad is now known as elbragstad | 17:37 | |
*** Swami has joined #openstack-meeting | 17:38 | |
*** njohnston has joined #openstack-meeting | 17:46 | |
*** jamesmcarthur has joined #openstack-meeting | 18:01 | |
*** armstrong has quit IRC | 18:10 | |
*** munimeha1 has quit IRC | 18:11 | |
*** mriedem_away is now known as mriedem | 18:28 | |
*** munimeha1 has joined #openstack-meeting | 18:33 | |
*** apetrich has quit IRC | 18:34 | |
*** apetrich has joined #openstack-meeting | 18:35 | |
*** e0ne has joined #openstack-meeting | 18:35 | |
*** jamesmcarthur has quit IRC | 18:48 | |
*** armax has quit IRC | 19:05 | |
*** fried_rolls is now known as efried | 19:07 | |
*** erlon has quit IRC | 19:09 | |
*** efried is now known as fried_rice | 19:11 | |
*** e0ne has quit IRC | 19:14 | |
*** toabctl has quit IRC | 19:19 | |
*** e0ne has joined #openstack-meeting | 19:19 | |
*** toabctl has joined #openstack-meeting | 19:21 | |
*** e0ne has quit IRC | 19:23 | |
*** lpetrut has quit IRC | 19:37 | |
*** jamesmcarthur has joined #openstack-meeting | 19:46 | |
*** cloudrancher has quit IRC | 19:55 | |
*** cloudrancher has joined #openstack-meeting | 19:55 | |
*** mjturek has quit IRC | 20:26 | |
*** armax has joined #openstack-meeting | 20:28 | |
*** jamesmcarthur has quit IRC | 20:29 | |
*** imacdonn has quit IRC | 20:32 | |
*** imacdonn has joined #openstack-meeting | 20:32 | |
*** mjturek has joined #openstack-meeting | 20:35 | |
*** openstack has joined #openstack-meeting | 20:43 | |
*** ChanServ sets mode: +o openstack | 20:43 | |
*** ttsiouts has joined #openstack-meeting | 20:46 | |
*** awaugama has quit IRC | 20:47 | |
*** munimeha1 has quit IRC | 20:53 | |
*** ttsiouts has quit IRC | 20:58 | |
*** raildo has quit IRC | 21:08 | |
*** dustins has quit IRC | 21:11 | |
*** eharney has quit IRC | 21:12 | |
*** jamesmcarthur has joined #openstack-meeting | 21:13 | |
*** jamesmcarthur has quit IRC | 21:24 | |
*** jbadiapa has quit IRC | 21:34 | |
*** mjturek has quit IRC | 21:50 | |
*** mriedem has quit IRC | 21:52 | |
*** armax has quit IRC | 21:53 | |
*** tpsilva has quit IRC | 22:27 | |
*** bobh has joined #openstack-meeting | 22:28 | |
*** armax has joined #openstack-meeting | 22:59 | |
*** hongbin has quit IRC | 23:01 | |
*** pcaruana has quit IRC | 23:10 | |
*** diablo_rojo has quit IRC | 23:40 | |
*** Swami has quit IRC | 23:43 | |
*** rcernin has joined #openstack-meeting | 23:44 | |
*** jesusaur has quit IRC | 23:45 | |
*** rcernin has quit IRC | 23:51 | |
*** gyee has quit IRC | 23:55 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!