| *** rcernin has quit IRC | 00:05 | |
| *** yasufum has joined #openstack-meeting | 00:26 | |
| *** rcernin has joined #openstack-meeting | 00:31 | |
| *** yasufum has quit IRC | 00:31 | |
| *** yasufum has joined #openstack-meeting | 00:38 | |
| *** zeestrat has quit IRC | 00:57 | |
| *** hillpd has quit IRC | 00:57 | |
| *** zeestrat has joined #openstack-meeting | 01:01 | |
| *** hillpd has joined #openstack-meeting | 01:01 | |
| *** gyee has quit IRC | 01:02 | |
| *** rfolco has quit IRC | 01:08 | |
| *** rfolco has joined #openstack-meeting | 01:15 | |
| *** ociuhandu has joined #openstack-meeting | 01:17 | |
| *** rfolco has quit IRC | 01:19 | |
| *** ociuhandu has quit IRC | 01:21 | |
| *** armax has quit IRC | 01:27 | |
| *** ociuhandu has joined #openstack-meeting | 01:43 | |
| *** ociuhandu has quit IRC | 01:48 | |
| *** rfolco has joined #openstack-meeting | 02:08 | |
| *** hyunsikyang has quit IRC | 02:12 | |
| *** ricolin has quit IRC | 02:15 | |
| *** yaawang has quit IRC | 02:21 | |
| *** ricolin has joined #openstack-meeting | 02:21 | |
| *** yaawang has joined #openstack-meeting | 02:22 | |
| *** moguimar_ has quit IRC | 02:26 | |
| *** rfolco has quit IRC | 02:28 | |
| *** yasufum has quit IRC | 02:45 | |
| *** ociuhandu has joined #openstack-meeting | 02:53 | |
| *** yasufum has joined #openstack-meeting | 02:56 | |
| *** ociuhandu has quit IRC | 02:57 | |
| *** hyunsikyang has joined #openstack-meeting | 02:58 | |
| *** diurnalist has joined #openstack-meeting | 02:59 | |
| *** diurnalist has quit IRC | 03:20 | |
| *** armax has joined #openstack-meeting | 03:28 | |
| *** yasufum has quit IRC | 03:28 | |
| *** psachin has joined #openstack-meeting | 03:37 | |
| *** armax has quit IRC | 03:43 | |
| *** psahoo has joined #openstack-meeting | 03:52 | |
| *** yasufum has joined #openstack-meeting | 03:59 | |
| *** rh-jelabarre has quit IRC | 04:32 | |
| *** rh-jlabarre has joined #openstack-meeting | 04:32 | |
| *** evrardjp has quit IRC | 04:33 | |
| *** rh-jlabarre has quit IRC | 04:33 | |
| *** evrardjp has joined #openstack-meeting | 04:33 | |
| *** rh-jlabarre has joined #openstack-meeting | 04:33 | |
| *** yasufum has quit IRC | 04:44 | |
| *** Lucas_Gray has quit IRC | 04:44 | |
| *** diurnalist has joined #openstack-meeting | 05:01 | |
| *** diurnalist has quit IRC | 05:06 | |
| *** yasufum has joined #openstack-meeting | 05:09 | |
| *** diurnalist has joined #openstack-meeting | 05:16 | |
| *** diurnalist has quit IRC | 05:22 | |
| *** tetsuro has joined #openstack-meeting | 05:25 | |
| *** tetsuro has quit IRC | 05:25 | |
| *** tetsuro has joined #openstack-meeting | 05:26 | |
| *** tetsuro has quit IRC | 05:27 | |
| *** yasufum has quit IRC | 05:41 | |
| *** slaweq has joined #openstack-meeting | 05:52 | |
| *** yaawang has quit IRC | 05:52 | |
| *** yaawang has joined #openstack-meeting | 05:53 | |
| *** ociuhandu has joined #openstack-meeting | 05:59 | |
| *** slaweq has quit IRC | 06:02 | |
| *** yasufum has joined #openstack-meeting | 06:04 | |
| *** masahito has joined #openstack-meeting | 06:05 | |
| *** diurnalist has joined #openstack-meeting | 06:08 | |
| *** diurnalist has quit IRC | 06:12 | |
| *** brtknr has quit IRC | 06:17 | |
| *** moguimar_ has joined #openstack-meeting | 06:30 | |
| *** vishalmanchanda has joined #openstack-meeting | 06:39 | |
| *** yaawang has quit IRC | 06:42 | |
| *** dklyle has quit IRC | 06:42 | |
| *** yaawang has joined #openstack-meeting | 06:42 | |
| *** slaweq has joined #openstack-meeting | 06:57 | |
| *** diurnalist has joined #openstack-meeting | 06:59 | |
| *** diurnalist has quit IRC | 07:04 | |
| *** apetrich has joined #openstack-meeting | 07:27 | |
| *** yonglihe has joined #openstack-meeting | 07:31 | |
| *** yasufum has quit IRC | 07:35 | |
| *** yasufum has joined #openstack-meeting | 07:39 | |
| *** tosky has joined #openstack-meeting | 07:39 | |
| *** ralonsoh has joined #openstack-meeting | 07:40 | |
| *** diurnalist has joined #openstack-meeting | 07:50 | |
| *** diurnalist has quit IRC | 07:55 | |
| *** evrardjp has quit IRC | 08:06 | |
| *** evrardjp has joined #openstack-meeting | 08:08 | |
| *** maciejjozefczyk has joined #openstack-meeting | 08:14 | |
| *** e0ne has joined #openstack-meeting | 08:24 | |
| *** diurnalist has joined #openstack-meeting | 08:41 | |
| *** brtknr has joined #openstack-meeting | 08:46 | |
| *** diurnalist has quit IRC | 08:46 | |
| *** ociuhandu has quit IRC | 08:56 | |
| *** masahito has quit IRC | 08:58 | |
| *** yasufum has quit IRC | 09:06 | |
| *** diurnalist has joined #openstack-meeting | 09:07 | |
| *** diurnalist has quit IRC | 09:12 | |
| *** rcernin has quit IRC | 09:12 | |
| *** Lucas_Gray has joined #openstack-meeting | 09:23 | |
| *** Lucas_Gray has quit IRC | 09:27 | |
| *** Lucas_Gray has joined #openstack-meeting | 09:30 | |
| *** moguimar_ is now known as moguimar | 09:32 | |
| *** ociuhandu has joined #openstack-meeting | 09:33 | |
| *** ociuhandu has quit IRC | 09:37 | |
| *** ociuhandu has joined #openstack-meeting | 09:42 | |
| *** diurnalist has joined #openstack-meeting | 09:58 | |
| *** diurnalist has quit IRC | 10:03 | |
| *** yaawang has quit IRC | 10:06 | |
| *** yaawang has joined #openstack-meeting | 10:07 | |
| *** psahoo has quit IRC | 10:44 | |
| *** diurnalist has joined #openstack-meeting | 10:49 | |
| *** ricolin has quit IRC | 10:52 | |
| *** ykatabam has quit IRC | 10:52 | |
| *** oneswig has joined #openstack-meeting | 10:53 | |
| *** diurnalist has quit IRC | 10:54 | |
| *** psahoo has joined #openstack-meeting | 10:56 | |
| *** bbezak has joined #openstack-meeting | 11:00 | |
| oneswig | #startmeeting scientific-sig | 11:00 |
|---|---|---|
| openstack | Meeting started Wed Jul 29 11:00:53 2020 UTC and is due to finish in 60 minutes. The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot. | 11:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 11:00 |
| *** openstack changes topic to " (Meeting topic: scientific-sig)" | 11:00 | |
| openstack | The meeting name has been set to 'scientific_sig' | 11:00 |
| oneswig | Hi | 11:01 |
| *** b1airo has joined #openstack-meeting | 11:03 | |
| oneswig | I have nothing planned this week, alas | 11:03 |
| oneswig | been overfaced with other stuff | 11:03 |
| b1airo | me either, but hi anyway :-) | 11:03 |
| oneswig | hey b1airo, how's things? | 11:03 |
| oneswig | #chair b1airo | 11:03 |
| openstack | Current chairs: b1airo oneswig | 11:03 |
| b1airo | (i had a late game of water-bug polo so thought i'd drop in before bed) | 11:04 |
| oneswig | water bug? | 11:04 |
| b1airo | was just watching a short talk on funcX | 11:04 |
| b1airo | ha, yeah let me see if i can find a picture to explain... | 11:05 |
| b1airo | #link stuff.co.nz/the-press/sport/104951385/bug-polo-the-unknown-but-longstanding-kiwi-sport | 11:05 |
| oneswig | cool, but why the bug? | 11:10 |
| b1airo | the bugs were invented for whitewater sport use, kinda an alternative to whitewater kayaking. bug-polo is just an excuse to do something else with them | 11:11 |
| oneswig | Are you thinking of a talk for the virtual summit? | 11:12 |
| *** ykatabam has joined #openstack-meeting | 11:13 | |
| b1airo | i hadn't considered one so far, though thinking about it, we might have a new system design fixed enough by that point that we could talk about it. it wouldn't be anything to crazy though, so probably not worth a full talk anyway | 11:14 |
| b1airo | you? must be a few new interesting tidbits from various engagements? | 11:15 |
| oneswig | I'd like to but no ideas as yet | 11:16 |
| b1airo | read the baremetal whitepaper last night - nice work B-) | 11:16 |
| oneswig | ha, thanks - I only contributed to our case study, but they did a great job on the rest of the white paper I think | 11:18 |
| oneswig | b1airo: user stories always seem to go well I think, don't undersell it. | 11:19 |
| oneswig | Shall we wrap up the meeting? Don't want to keep you up for no other reason | 11:20 |
| b1airo | true true, yeah probably time to hit the hay | 11:20 |
| b1airo | i was curious about how the cambridge crew and machines are going, but we could pick that up later | 11:20 |
| oneswig | Sure, there's definitely a good story to tell there. | 11:21 |
| oneswig | OK b1airo, I'll catch you on Slack in due course. Perhaps we can get someone to talk about the Cambridge user story in a meeting soon. | 11:21 |
| oneswig | #endmeeting | 11:21 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 11:21 | |
| openstack | Meeting ended Wed Jul 29 11:21:51 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 11:21 |
| oneswig | cheerio | 11:21 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-07-29-11.00.html | 11:21 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-07-29-11.00.txt | 11:21 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/scientific_sig/2020/scientific_sig.2020-07-29-11.00.log.html | 11:21 |
| b1airo | cya | 11:21 |
| *** psahoo has quit IRC | 11:37 | |
| *** diurnalist has joined #openstack-meeting | 11:40 | |
| *** markvoelker has joined #openstack-meeting | 11:40 | |
| *** raildo has joined #openstack-meeting | 11:44 | |
| *** diurnalist has quit IRC | 11:45 | |
| *** markvoelker has quit IRC | 11:47 | |
| *** rfolco has joined #openstack-meeting | 11:51 | |
| *** psahoo has joined #openstack-meeting | 11:52 | |
| *** moguimar has quit IRC | 12:20 | |
| *** moguimar has joined #openstack-meeting | 12:20 | |
| *** moguimar has quit IRC | 12:20 | |
| *** moguimar has joined #openstack-meeting | 12:21 | |
| *** diurnalist has joined #openstack-meeting | 12:31 | |
| *** diurnalist has quit IRC | 12:36 | |
| *** bbowen has quit IRC | 12:38 | |
| *** bbowen has joined #openstack-meeting | 12:39 | |
| *** lpetrut has joined #openstack-meeting | 12:44 | |
| *** moguimar has quit IRC | 12:45 | |
| *** moguimar has joined #openstack-meeting | 12:45 | |
| *** psahoo has quit IRC | 12:45 | |
| *** markvoelker has joined #openstack-meeting | 12:48 | |
| *** psahoo has joined #openstack-meeting | 12:48 | |
| *** diurnalist has joined #openstack-meeting | 13:01 | |
| *** diurnalist has quit IRC | 13:06 | |
| *** moguimar has quit IRC | 13:21 | |
| *** moguimar has joined #openstack-meeting | 13:23 | |
| *** sluna has quit IRC | 13:27 | |
| *** sluna has joined #openstack-meeting | 13:28 | |
| *** b1airo has quit IRC | 13:31 | |
| *** liuyulong has joined #openstack-meeting | 13:35 | |
| *** moguimar has quit IRC | 13:39 | |
| *** moguimar has joined #openstack-meeting | 13:41 | |
| *** TrevorV has joined #openstack-meeting | 13:50 | |
| liuyulong | #startmeeting neutron_l3 | 14:00 |
| openstack | Meeting started Wed Jul 29 14:00:27 2020 UTC and is due to finish in 60 minutes. The chair is liuyulong. 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_l3)" | 14:00 | |
| openstack | The meeting name has been set to 'neutron_l3' | 14:00 |
| ralonsoh | hi | 14:01 |
| liuyulong | Hi | 14:01 |
| liuyulong | OK, let's start. | 14:01 |
| liuyulong | #topic Announcements | 14:01 |
| *** openstack changes topic to "Announcements (Meeting topic: neutron_l3)" | 14:01 | |
| liuyulong | #link http://eavesdrop.openstack.org/#Neutron_L3_Sub-team_Meeting | 14:01 |
| liuyulong | #link https://review.opendev.org/#/c/741876/2/meetings/neutron-l3-sub-team-meeting.yaml | 14:01 |
| patchbot | patch 741876 - opendev/irc-meetings - Change Neutron L3 Sub-team Meeting frequency (MERGED) - 2 patch sets | 14:01 |
| liuyulong | I changed the L3 meetign frequency last week. | 14:02 |
| slaweq | hi | 14:03 |
| liuyulong | We will have it in every two weeks officially. | 14:03 |
| liuyulong | slaweq, hi | 14:03 |
| * slaweq is updating calendar right now | 14:03 | |
| *** ZhuXiaoYu has joined #openstack-meeting | 14:05 | |
| * slaweq has calendar updated already :) | 14:05 | |
| liuyulong | The irc channel and the time slot are as usual, so it looks good for me now. : ) | 14:05 |
| liuyulong | I should send a new email to the mail list. Will do that later. | 14:06 |
| liuyulong | OK, no more things from me now. | 14:06 |
| liuyulong | Next topic | 14:06 |
| liuyulong | #topic Bugs | 14:07 |
| *** openstack changes topic to "Bugs (Meeting topic: neutron_l3)" | 14:07 | |
| liuyulong | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016112.html | 14:07 |
| liuyulong | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016002.html | 14:07 |
| liuyulong | We have 2 bug lists since we have bi-weekly meeting. | 14:08 |
| liuyulong | Firstly, two bugs related to IPv6 | 14:08 |
| *** yaawang has quit IRC | 14:09 | |
| liuyulong | #link https://bugs.launchpad.net/neutron/+bug/1888256 | 14:09 |
| openstack | Launchpad bug 1888256 in neutron "Neutron start radvd and mess up the routing table when: ipv6_ra_mode=not set ipv6-address-mode=slaac" [Undecided,New] | 14:09 |
| liuyulong | The use case is a bit strange to me, they start a shared network with public IPv4/v6 address. | 14:10 |
| liuyulong | Then directly create instance in it. | 14:10 |
| *** yaawang has joined #openstack-meeting | 14:10 | |
| liuyulong | In order to achive the metadata HA, they choose HA router related data path. | 14:11 |
| liuyulong | So IMO, this case should be changed like this: | 14:12 |
| liuyulong | 1. stop using the neutron router, and move the gateway to the physical world (router). | 14:13 |
| liuyulong | 2. metadata data-path can be achived by dhcp namespace, DHCP instance (namespace and related process) has the auto-reschedule mechanism for the dead agent. | 14:14 |
| ralonsoh | is it possible to reschedule the metadata agent to use the DHCP instead of the router? | 14:15 |
| slaweq | ralonsoh: I think You need to enable isolated metadata on dhcp agent's side | 14:16 |
| slaweq | ralonsoh: but I'm not sure now exactly | 14:17 |
| liuyulong | 3. let the physical router send the NA out | 14:17 |
| liuyulong | sorry, a bit bad network traffic... | 14:17 |
| ralonsoh | that's the point, I don't know if you can do this once the agent is running in the router | 14:18 |
| liuyulong | ralonsoh, for the existing VMs, they may need to change the 169.254.169.254 route rule in the VM. | 14:18 |
| ralonsoh | that's done during the VM boot process | 14:18 |
| slaweq | but my question is: what is exact purpose of "ipv6_ra_mode=None"? | 14:20 |
| slaweq | should radvd be run in such case? | 14:20 |
| ralonsoh | yes | 14:20 |
| ralonsoh | no no, ipv6-address-mode=slaac and ipv6_ra_mode=not set | 14:21 |
| ralonsoh | The instance receives an IPv6 address from the external router (not managed by OpenStack Networking) using SLAAC. | 14:21 |
| ralonsoh | https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_openstack_platform/7/html/networking_guide/sec-ipv6 | 14:21 |
| slaweq | ralonsoh: so why we run radvd in such case? | 14:22 |
| ralonsoh | no idea... | 14:22 |
| slaweq | if we wouldn't run it, there wouldn't be problem IMO | 14:22 |
| slaweq | as there wouldn't be any process on our side which would inject this bad default route | 14:22 |
| liuyulong | yes, no Neutron router should be added to this case | 14:22 |
| ralonsoh | according to this document (similar to the OpenStack documentation) | 14:23 |
| ralonsoh | when ipv6_ra_mode=not set, we don't use radvd | 14:23 |
| slaweq | ralonsoh: so that seems for me like RC of this issue | 14:24 |
| liuyulong | #link https://bugs.launchpad.net/neutron/+bug/1888256/comments/7 | 14:24 |
| openstack | Launchpad bug 1888256 in neutron "Neutron start radvd and mess up the routing table when: ipv6_ra_mode=not set ipv6-address-mode=slaac" [Undecided,New] | 14:24 |
| liuyulong | according to this comment, seems that "AdvSendAdvert on;" is always available. | 14:24 |
| slaweq | but IMO we shouldn't have this section: | 14:25 |
| liuyulong | It is hard code. | 14:25 |
| slaweq | interface qr-a6d7ceab-80 | 14:25 |
| slaweq | { | 14:25 |
| liuyulong | #link https://github.com/openstack/neutron/blob/8c80267bb6699c86e10aade13c54b715e1eae1bf/neutron/agent/linux/ra.py#L41 | 14:25 |
| slaweq | AdvSendAdvert on; | 14:25 |
| slaweq | MinRtrAdvInterval 30; | 14:25 |
| slaweq | MaxRtrAdvInterval 100; | 14:25 |
| slaweq | AdvLinkMTU 1500; | 14:25 |
| slaweq | }; | 14:25 |
| slaweq | in the radvd.conf at all if subnet is configured like that one in LP | 14:25 |
| liuyulong | #link https://github.com/openstack/neutron/blob/master/neutron/agent/linux/ra.py#L41 | 14:26 |
| liuyulong | ^ change to master | 14:26 |
| slaweq | so radvd shouldn't even listen on this interface | 14:26 |
| *** rubasov has quit IRC | 14:28 | |
| liuyulong | I don't know, maybe because it is the gateway. | 14:28 |
| *** rubasov has joined #openstack-meeting | 14:28 | |
| liuyulong | This should be changed to as the action 1. "move the gateway to physical router." | 14:29 |
| *** dklyle has joined #openstack-meeting | 14:29 | |
| liuyulong | From my personal experiences, for such VLAN shared network, we topically did such work, the gateway will not be set on Neutron router. And there is no Neutron router. | 14:30 |
| slaweq | liuyulong: if You want I can take a look into that issue locally and will write a comment and/or propose patch | 14:31 |
| liuyulong | slaweq, great, go ahead, it's yours. : ) | 14:32 |
| slaweq | thx | 14:32 |
| liuyulong | #link https://bugs.launchpad.net/neutron/+bug/1888464 | 14:32 |
| openstack | Launchpad bug 1888464 in neutron "IPv6 PD with DVR does not assign correct snat sg address" [Undecided,New] | 14:32 |
| liuyulong | This is the another IPv6 related bug. | 14:33 |
| liuyulong | Allow me to clarify the fact first, the sg-dev should have an IPv6 address from users internal subnet. | 14:34 |
| liuyulong | While the qg-dev should have an IPv6 address from external network. | 14:35 |
| liuyulong | So from the bug description, we can only see there is an IPv6 subnet from the external network. | 14:35 |
| ralonsoh | so sg-230491ca-5b should have an internal ipv6 address | 14:36 |
| ralonsoh | is that correct? | 14:36 |
| * slaweq is on another meeting but will be lurking here too | 14:36 | |
| liuyulong | So maybe this is not a bug, just because the user does not create the IPv6 subnet for there internal network. | 14:36 |
| liuyulong | If the internal network has 2 subnet (v4 and v6), there should have two sg-devs. | 14:37 |
| liuyulong | So, let me mark it as incomplete for now. | 14:39 |
| *** ricolin has joined #openstack-meeting | 14:40 | |
| liuyulong | ralonsoh, IMO, the user was misunderstanding the network topology. | 14:40 |
| *** mlavalle has joined #openstack-meeting | 14:40 | |
| ralonsoh | I still need to review this part of the code to be 100% sure | 14:40 |
| liuyulong | The subnet uuid, router uuid, fip-network uuid does not match at all. | 14:40 |
| *** Lucas_Gray has quit IRC | 14:41 | |
| ralonsoh | you are right | 14:41 |
| *** rcernin has joined #openstack-meeting | 14:41 | |
| liuyulong | OK, no more bugs from me now. | 14:42 |
| liuyulong | Any updates? | 14:42 |
| ralonsoh | nope | 14:42 |
| liuyulong | OK, let's move on. | 14:43 |
| liuyulong | #topic On demand agenda | 14:43 |
| *** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)" | 14:43 | |
| liuyulong | #link https://review.opendev.org/#/c/658511/ | 14:43 |
| patchbot | patch 658511 - neutron-specs - L3 agent self-service metering - 10 patch sets | 14:43 |
| *** lpetrut has quit IRC | 14:43 | |
| liuyulong | IMO, this was approved before in drivers meeting. | 14:44 |
| liuyulong | So, need more attention. : ) | 14:44 |
| ralonsoh | ok | 14:44 |
| liuyulong | #link https://review.opendev.org/#/c/675654/ | 14:44 |
| patchbot | patch 675654 - neutron - L3 agent metering extension - 7 patch sets | 14:44 |
| liuyulong | This is the patch for it. | 14:44 |
| liuyulong | Yes, it is still in-progress | 14:45 |
| liuyulong | I will continuesly work on this. | 14:45 |
| slaweq | liuyulong: I will try to review it this week | 14:45 |
| liuyulong | Next one should be this | 14:46 |
| liuyulong | #link https://review.opendev.org/#/c/728628/ | 14:46 |
| patchbot | patch 728628 - neutron-specs - L3 router support ndp proxy - 17 patch sets | 14:46 |
| liuyulong | After mine request, I see the author uploaded the POC to gerrit. | 14:46 |
| liuyulong | #link https://review.opendev.org/#/c/743142/ | 14:47 |
| patchbot | patch 743142 - neutron - [WIP][PoC][Server Side] L3 router support ndp proxy - 2 patch sets | 14:47 |
| liuyulong | It is all in one, IMO | 14:47 |
| liuyulong | The patch is including the agent side change. | 14:47 |
| liuyulong | This is good for us to understand the real proposal. | 14:48 |
| liuyulong | And the details about the DVR, HA can be found in that as well. | 14:48 |
| liuyulong | #link https://review.opendev.org/#/c/729532/ | 14:49 |
| patchbot | patch 729532 - neutron-specs - L3 router support ecmp - 28 patch sets | 14:49 |
| liuyulong | Same work for this one, it also has a POC. | 14:49 |
| liuyulong | #link https://review.opendev.org/#/c/743661/ | 14:49 |
| patchbot | patch 743661 - neutron - L3 router support ECMP - 1 patch set | 14:49 |
| ralonsoh | but that wasn't approved | 14:49 |
| *** Lucas_Gray has joined #openstack-meeting | 14:49 | |
| liuyulong | No? | 14:50 |
| liuyulong | I missed that. | 14:50 |
| ralonsoh | https://bugs.launchpad.net/neutron/+bug/1880532 is not approved yet | 14:50 |
| openstack | Launchpad bug 1880532 in neutron "[RFE]L3 Router should support ECMP" [Wishlist,New] - Assigned to XiaoYu Zhu (honglan0914) | 14:50 |
| *** lbragstad_ has joined #openstack-meeting | 14:51 | |
| liuyulong | By the way, thing POC has no control plane related code, just some route related implementation. | 14:51 |
| *** irclogbot_1 has quit IRC | 14:52 | |
| *** rcernin_ has joined #openstack-meeting | 14:52 | |
| *** dklyle has quit IRC | 14:53 | |
| liuyulong | So the reuse of the exsiting route API will be the control method. | 14:53 |
| liuyulong | Looks good to me, it will be small and clear. | 14:54 |
| liuyulong | Last one | 14:55 |
| liuyulong | #link https://review.opendev.org/#/q/topic:ovn/port_forwarding | 14:55 |
| liuyulong | OVN port forwarding is good in progress. | 14:55 |
| ralonsoh | yes, Flavio is working on this full time | 14:56 |
| *** rcernin_ has quit IRC | 14:56 | |
| liuyulong | If anyone is interested, pleae go ahead and do code review. | 14:57 |
| liuyulong | Let's narrow down the gaps. : ) | 14:57 |
| liuyulong | OK, no more things from me now. | 14:57 |
| *** rcernin has quit IRC | 14:58 | |
| ZhuXiaoYu | https://review.opendev.org/#/c/743661/ | 14:58 |
| ZhuXiaoYu | Here is the patch | 14:58 |
| *** lbragstad has quit IRC | 14:58 | |
| patchbot | patch 743661 - neutron - L3 router support ECMP - 1 patch set | 14:58 |
| liuyulong | ZhuXiaoYu, hi, I've mentioned that. : ) | 14:59 |
| *** irclogbot_0 has joined #openstack-meeting | 14:59 | |
| ZhuXiaoYu | :) | 14:59 |
| liuyulong | ZhuXiaoYu, by the way, it will be better if you add some test cases. | 14:59 |
| ZhuXiaoYu | OK, I will. | 15:00 |
| liuyulong | Alright, time is up. | 15:00 |
| liuyulong | Bye | 15:00 |
| ralonsoh | bye | 15:00 |
| liuyulong | #endmeeting | 15:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:00 | |
| openstack | Meeting ended Wed Jul 29 15:00:45 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-07-29-14.00.html | 15:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-07-29-14.00.txt | 15:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-07-29-14.00.log.html | 15:00 |
| *** diurnalist has joined #openstack-meeting | 15:01 | |
| *** liuyulong has quit IRC | 15:01 | |
| *** dklyle has joined #openstack-meeting | 15:01 | |
| *** lajoskatona has joined #openstack-meeting | 15:10 | |
| *** lajoskatona has left #openstack-meeting | 15:11 | |
| *** toabctl has quit IRC | 15:32 | |
| *** toabctl has joined #openstack-meeting | 15:33 | |
| *** psahoo has quit IRC | 15:36 | |
| *** armax has joined #openstack-meeting | 15:37 | |
| *** ykatabam has quit IRC | 16:02 | |
| *** markvoelker has quit IRC | 16:13 | |
| *** ociuhandu_ has joined #openstack-meeting | 16:21 | |
| *** ociuhandu has quit IRC | 16:23 | |
| *** ociuhandu_ has quit IRC | 16:27 | |
| *** gyee has joined #openstack-meeting | 16:28 | |
| *** ociuhandu has joined #openstack-meeting | 16:35 | |
| *** armstrong has joined #openstack-meeting | 16:38 | |
| *** ociuhandu has quit IRC | 16:41 | |
| *** mlavalle has quit IRC | 16:46 | |
| *** mlavalle has joined #openstack-meeting | 16:48 | |
| *** psachin has quit IRC | 16:53 | |
| *** Lucas_Gray has quit IRC | 16:54 | |
| *** ricolin has quit IRC | 17:01 | |
| *** armax has quit IRC | 17:19 | |
| *** armax has joined #openstack-meeting | 17:19 | |
| *** dmacpher_ has joined #openstack-meeting | 17:21 | |
| *** dmacpher has quit IRC | 17:25 | |
| *** maciejjozefczyk has quit IRC | 18:24 | |
| *** vishalmanchanda has quit IRC | 18:29 | |
| *** armstrong has quit IRC | 18:48 | |
| *** ralonsoh has quit IRC | 18:53 | |
| *** lbragstad_ is now known as lbragstad | 19:01 | |
| *** ZhuXiaoYu has quit IRC | 19:06 | |
| *** bbowen has quit IRC | 19:46 | |
| *** moguimar_ has joined #openstack-meeting | 19:55 | |
| *** moguimar has quit IRC | 19:55 | |
| *** moguimar_ has quit IRC | 20:03 | |
| *** moguimar_ has joined #openstack-meeting | 20:04 | |
| *** yaawang has quit IRC | 20:07 | |
| *** yaawang has joined #openstack-meeting | 20:07 | |
| *** ykatabam has joined #openstack-meeting | 20:17 | |
| *** moguimar_ has quit IRC | 20:34 | |
| *** ociuhandu has joined #openstack-meeting | 20:39 | |
| *** ociuhandu has quit IRC | 20:43 | |
| *** zaitcev has joined #openstack-meeting | 20:57 | |
| timburke | #startmeeting swift | 21:03 |
| openstack | Meeting started Wed Jul 29 21:03:18 2020 UTC and is due to finish in 60 minutes. The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:03 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 21:03 |
| *** openstack changes topic to " (Meeting topic: swift)" | 21:03 | |
| openstack | The meeting name has been set to 'swift' | 21:03 |
| timburke | who's here for the swift meeting? | 21:03 |
| mattoliverau | o/ | 21:03 |
| seongsoocho | o/ | 21:03 |
| kota_ | o/ | 21:04 |
| rledisez | hi o/ | 21:04 |
| timburke | clayg, zaitcev, tdasilva? | 21:05 |
| clayg | i'm here! | 21:05 |
| clayg | thanks | 21:05 |
| timburke | agenda's at https://wiki.openstack.org/wiki/Meetings/Swift | 21:06 |
| timburke | first, a couple announcements | 21:06 |
| timburke | #topic ptg | 21:06 |
| *** openstack changes topic to "ptg (Meeting topic: swift)" | 21:06 | |
| zaitcev | It's a storm here but I'm here thus far. | 21:06 |
| timburke | the next ptg will be all-online, like the last one | 21:06 |
| timburke | and there's a poll up for *when* exactly it should be | 21:06 |
| timburke | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016098.html | 21:07 |
| clayg | oh, thanks | 21:07 |
| *** slaweq has quit IRC | 21:07 | |
| zaitcev | Maybe we ought to run our own hackathon in person. Of course, masks, hand sanitizer all around. | 21:07 |
| clayg | small pods | 21:08 |
| timburke | zaitcev, that is *so* tempting for me | 21:08 |
| mattoliverau | Tho that only works for peeps in the same country | 21:08 |
| timburke | and even then, it'll be harder than usual to get employer buy-in | 21:09 |
| timburke | so i think the plan for now should be: do a virtual ptg again | 21:10 |
| timburke | though i fully acknowledge that there's something lost in doing it that way | 21:10 |
| timburke | #topic London OpenInfra virtual meetup | 21:11 |
| *** openstack changes topic to "London OpenInfra virtual meetup (Meeting topic: swift)" | 21:11 | |
| timburke | there's a meetup thing going on tomorrow! seems like it might be worth checking out if anyone has time | 21:11 |
| timburke | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016109.html | 21:11 |
| *** oneswig has quit IRC | 21:12 | |
| timburke | that's all i've got for announcements... on to more swifty things | 21:13 |
| timburke | #topic py3 crypto bug | 21:13 |
| *** openstack changes topic to "py3 crypto bug (Meeting topic: swift)" | 21:13 | |
| timburke | #link https://launchpad.net/bugs/1888037 | 21:13 |
| openstack | Launchpad bug 1888037 in OpenStack Object Storage (swift) "Encryption writes different paths for key_id on py2 and py3" [High,In progress] | 21:13 |
| timburke | currently, there's an availability issue when upgrading from swift-on-py2 to swift-on-py3 | 21:14 |
| zaitcev | \u00f0\u009f\u008c\u00b4 is a WSGI string, isn't it | 21:14 |
| timburke | specifically, any data that was encrypted for a path that included any non-ascii characters will cause 500s | 21:14 |
| timburke | zaitcev, yup :-( | 21:15 |
| timburke | good news is, we've got a fix: https://review.opendev.org/#/c/742033/ | 21:15 |
| patchbot | patch 742033 - swift - py3: Work with proper native string paths in crypt... - 3 patch sets | 21:15 |
| timburke | bad news is, it currently causes a rolling upgrade issue (because it bumps the version number stored in crypto metadata, so anything written by an upgraded proxy won't be able to be read by an old proxy) | 21:16 |
| *** TrevorV has quit IRC | 21:16 | |
| clayg | join the debate! https://etherpad.opendev.org/p/crypto-meta-version-3 | 21:17 |
| timburke | we've done this once before... for https://launchpad.net/bugs/1813725 about a year and a half ago | 21:17 |
| openstack | Launchpad bug 1813725 in OpenStack Object Storage (swift) "Object encryption key truncated sometimes when used with Barbican" [Medium,Confirmed] | 21:17 |
| timburke | but that doesn't mean it was a good thing | 21:17 |
| mattoliverau | wow, it's like py2 and py3 strings bite us again. All when you think it's safe :P | 21:18 |
| clayg | yeah the py2 works with py2 and py3 works with py3 thing in v2 is annoying | 21:19 |
| timburke | i also did a patch to add an option to continue doing things the old way(s): https://review.opendev.org/#/c/742756/ | 21:19 |
| patchbot | patch 742756 - swift - crypto: Add config option to support rolling upgrades - 3 patch sets | 21:19 |
| rledisez | is it not an other argument for checkpoint release? | 21:20 |
| clayg | but the problem of a py2 upgrading to py3 and expecting it in the py3-v2 format is still bad | 21:20 |
| timburke | but i'm realizing that even that won't work well for a rolling py2->py3 upgrade | 21:20 |
| clayg | rledisez: I don't think we have ever done anything we'd call a checkpoint release | 21:20 |
| rledisez | clayg: my point is maybe we should. it would help us a lot when managing legacy code & co. we also know at some point we can drop old code | 21:21 |
| rledisez | (when it's not about data written on disk, of course) | 21:21 |
| clayg | i agree, having a checkpoint release process that's robust and available would be super userful | 21:21 |
| clayg | I think we've mostly juts done like a 4 year deprecation cycle or.. like "never" also works | 21:22 |
| timburke | heh -- reminds me of https://review.opendev.org/#/c/736787/ | 21:23 |
| patchbot | patch 736787 - swift - Rip out pickle support in our memcached client - 1 patch set | 21:23 |
| zaitcev | That's different. It only takes 1 reboot to make sure that old format is no more. But drives can be around for 10 years. | 21:24 |
| timburke | i meant more the 'or.. like "never" also works' ;-) | 21:25 |
| rledisez | zaitcev: in this situation, we could "force" the operator to upgrade to a version that support both v2 and v3 format, before letting him move to a version that use v3 by default | 21:25 |
| clayg | timburke: 🤣 | 21:26 |
| *** raildo has quit IRC | 21:26 | |
| clayg | we probably *could* drop "reading the pickle format from memcache" support - see! eventually it'll seem obvious that we don't have to write v2! | 21:27 |
| timburke | so, back tot he topic at hand: how can we make sure a rolling upgrade is still successful? i guess, more config options that we hope operators never actually need to use? | 21:28 |
| timburke | what should the defaults be? | 21:28 |
| clayg | rledisez: you betcha! a legit checkpoint! there's just the code needed to support the mechanics and the process needed to make sure all the clusters we care about upgrade like we want | 21:28 |
| rledisez | timburke: default should be v2. The operator knows when he upgraded all the cluster and so decides to switch to v3 when he's ready. but we also have to assume that some won't do it and will get bitten one day when v3 become the default | 21:29 |
| clayg | I'm 100% sure continuing to write in the current format is the correct thing todo for current clusters - py2 clusters could even skip the latin-1 shiz; py3 tho won't know if it has py2/v2 or py3/v2 so it'll have to do the extra work | 21:29 |
| clayg | rledisez: as long as they have code that can READ v3 we can start writing it | 21:30 |
| clayg | rledisez: so... like 2 years or whatever... it'll be fine | 21:30 |
| timburke | rledisez, *which* v2? the v2 that py2 would've written down (which is essentially identical to v3), or the v2 that py3 would've written down? | 21:30 |
| clayg | the real suck is if we have a v4 by then - then we have to think about upgrading from something can't read v3 😞 | 21:30 |
| clayg | timburke: v2 will have to continue to be different on py2 vs py3 until after they've upgraded AFICT | 21:31 |
| timburke | and actually -- i kinda feel like it's worth thinking about whether the default *should be* v1 | 21:31 |
| clayg | timburke: I think v1 had a BUG tho - loss of information? and we've made it past the upgrade already? why do we want to go back? | 21:32 |
| timburke | clayg, so to do a py2->py3 transition, you need to go old-swift-on-py2 -> new-swift-on-py2 -> new-swift-on-py3? | 21:32 |
| clayg | i think old-swift-on-py2 to new-swift-on-py3 should be fine as long as they both know how to read the right formats (e.g. current swift py3 can't read old-swift-py2 format) | 21:33 |
| *** bbowen has joined #openstack-meeting | 21:33 | |
| clayg | but once we've cut new code such that new-swift-py3 can read old-swift-py2 format (even if that old-swift-py2 is still writing v2); we should be fine? | 21:34 |
| timburke | clayg, you and i have, certainly. how many clusters are still out there from rocky or earlier? | 21:34 |
| clayg | ok, so there's clusters still writing v1 that haven't upgraded to a swift that's now writing v2 so their yet-to-be-done rolling-upgrade WILL cry when old proxies read v2/v3 for the first time | 21:35 |
| timburke | clayg, the way the patches are currently, new-swift-on-py3 won't be able to write a v2 that old-swift-on-py2 could read | 21:35 |
| clayg | so this is sort of the 'v4 requires code that knows how to read v3 to upgrade" problem... but earlier | 21:36 |
| clayg | timburke: but a new-swift-on-py3 *COULD* write a *v3* that new-swift-on-py2 could read so maybe there's a "min swift version prior to upgrade to py3" | 21:37 |
| clayg | unless you already have... in which case "thanks for helping us find all these bugs!" | 21:37 |
| timburke | i've got this nagging feeling like that version's going to be ever-increasing until we drop support for py2... | 21:38 |
| clayg | timburke: 🤗 | 21:38 |
| clayg | seongsoocho: rledisez: anyone else want to try and jump in? Any questions about the bug report, the wip patch, or the etherpad | 21:39 |
| rledisez | nah, i agree with last comment from timburke (so maybe there's a "min swift version prior to upgrade to py3") | 21:40 |
| timburke | should i squash the two patches together, so there's a nice spot to write a fairly complete UpgradeImpact? | 21:41 |
| clayg | we could try a "checkpoint process" that's mostly convention w/o code to enforce it | 21:41 |
| clayg | but i'm not going to exercise it; cause as soon as we upgrade we'll turn on v3 so if the default changes later it won't effect us. | 21:42 |
| seongsoocho | I'm still try to reproduce this bug in my dev cluster . :-( | 21:42 |
| clayg | you have to write py2 crypto - then read it py3 to see the bug really | 21:43 |
| timburke | seongsoocho, so you're in a fairly unique position (to my knowledge): your cluster's been py3 from the beginning, right? | 21:43 |
| clayg | py2/v2 is unicode from utf8 - py3/v2 is unicode from latin-1 | 21:44 |
| seongsoocho | timburke: I have 3 cluster and the 3rd cluster is py3 from the beginning. | 21:45 |
| timburke | ah, got it. thanks; good to know | 21:45 |
| timburke | do you run with encryption enabled? | 21:45 |
| clayg | oh neat! so you'll definitely want this fixed so you can upgrade the other clusters to py3!!! 💪 | 21:45 |
| clayg | oh... good question... why did I think seongsoocho's cluster was encrypted 🤔 | 21:46 |
| seongsoocho | yes .. actually my cluster doesn't use encrypted. but now i'm build a new cluster (support object encryption) with py3. | 21:47 |
| seongsoocho | Rather than encrypting object on the server, I'm telling our customer to encrypt it on the client. | 21:49 |
| clayg | seongsoocho: excellent recommendation | 21:49 |
| timburke | always a good stance to take :-) | 21:49 |
| seongsoocho | But, new cluster support server-side object encryption.. | 21:49 |
| timburke | ok, i'm running out of steam on this. i'm still not sure what i should be coding | 21:52 |
| clayg | v2 default so we can upgrade w/o having to push a config first! | 21:52 |
| clayg | after we upgrade we'll turn on v3 and we don't have to think about this dumb problem for a little while 🤣 | 21:52 |
| timburke | and release note that you need to upgrade to swift 2.26.0 (or whatever) before switching from py2 to py3? | 21:53 |
| timburke | i can do that. nobody else worried about the v1 upgrade issue? | 21:53 |
| timburke | i guess not ;-) | 21:55 |
| timburke | ok, last few minutes | 21:55 |
| timburke | #topic open discussion | 21:55 |
| *** openstack changes topic to "open discussion (Meeting topic: swift)" | 21:55 | |
| clayg | upgrade *and* be writing v3 I think - unless new-py2 will be able to read the old-py3-default 🤔 | 21:55 |
| timburke | anything else to bring up? | 21:55 |
| clayg | I wanted to tell people I'm trying to simply the config for concurrent gets with ec! | 21:55 |
| clayg | https://review.opendev.org/#/c/737096/ | 21:55 |
| patchbot | patch 737096 - swift - Add concurrent_ec_extra_requests - 4 patch sets | 21:55 |
| seongsoocho | https://bugs.launchpad.net/swift/+bug/1889386 <- Does anyone know about this bug(??)?? | 21:56 |
| openstack | Launchpad bug 1889386 in OpenStack Object Storage (swift) "[ s3 api ] The CreationDate of listing bucket always return '2009-02-03T16:45:09.000Z'" [Undecided,New] | 21:56 |
| zaitcev | to simply? Was it "to simplify" perchance? | 21:56 |
| clayg | now that it doesn't have all that "per replica" crap I'm thinking about squishing the concurrent_ec_extra_requests option into p 711342 | 21:56 |
| patchbot | https://review.opendev.org/#/c/711342/ - swift - Add concurrent_gets to EC GET requests - 14 patch sets | 21:56 |
| timburke | clayg, yeah, new-py2 should be fine to deal with old-py3 | 21:56 |
| clayg | timburke: well, people should still write v3 😁 | 21:56 |
| timburke | oh, for sure | 21:57 |
| clayg | zaitcev: simplify! yes, thank you! | 21:57 |
| timburke | seongsoocho, yeah... that's a sad confusing mess, isn't it... | 21:58 |
| clayg | do the account db's tables not have any kind of date? modified or something? | 21:58 |
| seongsoocho | timburke: yes... I have no idea to fix this problem. | 21:58 |
| timburke | i think we could address it -- add a new key to the json responses the account server sends back, have s3api look for that | 21:58 |
| clayg | seongsoocho: i'd be onboard with a schema update that includes pushing new info up to the listings from the container-updater | 21:59 |
| clayg | anything that makes us more like s3 is helpful! (it's a big patch tho, I don't know how to cheat) | 21:59 |
| timburke | no one's felt enough pressure yet to get it fixed. but i'd be happy to review any patches for it! | 21:59 |
| clayg | ❤️ | 21:59 |
| clayg | timburke: is it a datamodel change too - or just api? | 22:00 |
| timburke | i *think* mostly just api. pretty sure we've already got the create date in the db table, though i ought to double-check | 22:00 |
| clayg | zaitcev: I think the concurrent_ec_extra_requests option will allow for most of the interesting things we might have tried with per-replica-timeouts and will be much easier to configure | 22:01 |
| clayg | oh... shoot - that's time! | 22:01 |
| timburke | i put it up there with ?partNumber=<N> support -- it shouldn't actually be too bad... mostly just a matter of prioritization | 22:01 |
| timburke | so it is | 22:01 |
| timburke | thank you all for coming, and thank you for working on swift! | 22:01 |
| timburke | #endmeeting | 22:01 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 22:01 | |
| openstack | Meeting ended Wed Jul 29 22:01:49 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 22:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-07-29-21.03.html | 22:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-07-29-21.03.txt | 22:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-07-29-21.03.log.html | 22:01 |
| *** zaitcev has left #openstack-meeting | 22:01 | |
| *** e0ne has quit IRC | 22:16 | |
| *** e0ne has joined #openstack-meeting | 22:19 | |
| *** e0ne has quit IRC | 22:20 | |
| *** e0ne has joined #openstack-meeting | 22:31 | |
| *** rcernin_ has joined #openstack-meeting | 22:36 | |
| *** e0ne_ has joined #openstack-meeting | 22:37 | |
| *** e0ne has quit IRC | 22:37 | |
| *** e0ne_ has quit IRC | 22:37 | |
| *** rcernin_ has quit IRC | 22:48 | |
| *** rcernin has joined #openstack-meeting | 22:48 | |
| *** ociuhandu has joined #openstack-meeting | 23:01 | |
| *** ociuhandu has quit IRC | 23:06 | |
| *** tosky has quit IRC | 23:21 | |
| *** diurnalist has quit IRC | 23:59 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!