| opendevreview | ZhouHeng proposed openstack/neutron-lib master: [ovn]Floating IP adds distributed attributes https://review.opendev.org/c/openstack/neutron-lib/+/855053 | 01:20 |
|---|---|---|
| opendevreview | ZhouHeng proposed openstack/neutron-tempest-plugin master: list floating ip api contains port forwarding id https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/855608 | 01:30 |
| opendevreview | liujinxin proposed openstack/neutron master: For DvrEdgeRouter, snat namespace should not be created in initialize. https://review.opendev.org/c/openstack/neutron/+/855995 | 02:28 |
| *** ykarel|away is now known as ykarel | 05:01 | |
| lajoskatona | slaweq, ykarel: Hi, Does this patch is needed: https://review.opendev.org/c/openstack/neutron/+/856444 after https://review.opendev.org/c/openstack/neutron/+/856461 is merged? | 06:19 |
| ykarel | lajoskatona, no not needed /me will abandon it | 06:20 |
| lajoskatona | ykarel: ok, thanks | 06:20 |
| opendevreview | Felix Huettner proposed openstack/neutron master: Cleanup fanout queues on ovs agent stop https://review.opendev.org/c/openstack/neutron/+/855851 | 07:03 |
| opendevreview | Felix Huettner proposed openstack/neutron master: Cleanup fanout queues on ovs agent stop (part 2) https://review.opendev.org/c/openstack/neutron/+/856411 | 07:03 |
| opendevreview | Lajos Katona proposed openstack/neutron-fwaas master: Adopt to latest VlanManager and oslo.db changes https://review.opendev.org/c/openstack/neutron-fwaas/+/855891 | 07:30 |
| *** marlinc is now known as Guest2357 | 08:13 | |
| opendevreview | Slawek Kaplonski proposed openstack/neutron master: Reset device namespace when adding to the namespace fails https://review.opendev.org/c/openstack/neutron/+/856261 | 08:28 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron master: Add new role "prepare_functional_tests_logs" https://review.opendev.org/c/openstack/neutron/+/855868 | 08:28 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron stable/yoga: Retry connections to Nova https://review.opendev.org/c/openstack/neutron/+/856578 | 08:34 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron stable/xena: Retry connections to Nova https://review.opendev.org/c/openstack/neutron/+/856579 | 08:35 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron stable/wallaby: Retry connections to Nova https://review.opendev.org/c/openstack/neutron/+/856580 | 08:35 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron stable/victoria: Retry connections to Nova https://review.opendev.org/c/openstack/neutron/+/856606 | 08:37 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron stable/ussuri: Retry connections to Nova https://review.opendev.org/c/openstack/neutron/+/856607 | 08:39 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron stable/train: Retry connections to Nova https://review.opendev.org/c/openstack/neutron/+/856581 | 08:39 |
| ges | Hello! We are thinking about doing rate-limiting on the metadata API (some of our users are just hammering 169.254.169.254 all day long). We came-up with a first solution where we change the metadata's haproxy config to rate-limit clients using stick-tables. Would there be an interest in upstreaming this change? | 09:44 |
| kevko | slaweq: Hi, it looks like you released neutron 20.20.1 for yoga but upper-constraints are not updated ... I am not sure how to propose fix to global-requirements repo | 10:32 |
| slaweq | kevko: hi, You can propose patch to https://opendev.org/openstack/requirements/ via gerrit | 10:33 |
| slaweq | as to any other repo | 10:33 |
| kevko | (building neutron images via kolla build from sources... where 20.2.1 is latest yoga neutron version ..while 20.2.0 is in constraints) | 10:33 |
| kevko | slaweq: well, I know how to deal with it ...but I thought that there is some automatic or semi-automatic process which is updating requirements... part of release process | 10:34 |
| kevko | so i don't want to break something :) | 10:35 |
| kevko | slaweq: because everywhere is Openstack proposal bto | 10:37 |
| kevko | bot | 10:37 |
| slaweq | kevko: I don't know that automation too much TBH but I if it wasn't proposed, You can do it manually probably | 10:38 |
| slaweq | please ask on the #openstack-release channel | 10:39 |
| kevko | slaweq: ok .. but it looks like there is something bad in neutron repo :/ | 10:40 |
| kevko | slaweq: hmm, why tarballs.opendev.org has tarball neutron 20.2.1.dev32 for download ...but 20.2.1 tag is nowhere ... | 10:54 |
| slaweq | kevko: sorry but I have no idea | 10:54 |
| kevko | ok | 10:54 |
| kevko | thanks | 10:54 |
| frickler | that is no git tag, pbr constructs the name as "32 patches after tag 20.2.0" | 10:59 |
| frickler | it references the current head of the stable/yoga branch | 11:00 |
| frickler | the tarball is also named accordingly: https://tarballs.opendev.org/openstack/neutron/neutron-stable-yoga.tar.gz | 11:01 |
| lajoskatona | kevko: yes, if you install the pkg with pip from git repo, and it has commits over 20.2.0 you have the extra .devX | 11:01 |
| kevko | lajoskatona: this is of course expected ...but there is no tag 20.2.1 ..and that's the point :D | 11:02 |
| kevko | lajoskatona: check below | 11:03 |
| kevko | michalarbet@pixla:~/ultimum/git/upstream/neutron$ git tag | grep '20\.2\.[0-9]' | 11:03 |
| kevko | 20.2.0 | 11:03 |
| kevko | michalarbet@pixla:~/ultimum/git/upstream/neutron$ grep -Ri '20\.2\.1' | 11:03 |
| kevko | michalarbet@pixla:~/ultimum/git/upstream/neutron$ grep -Ri '20\.2\.1' . | 11:03 |
| kevko | 20.2.1 nowhere ...no tag exist ..nothing in git tree ...so from where is that 20.2.1 version ? | 11:04 |
| kevko | if instead of 20.2.1.dev32 will be 20.2.0.devXY ..it will work ..but i really don't understand from where 20.2.1 version is .. | 11:05 |
| lajoskatona | kevko: thanks, I can say what slaweq said: no idea in this case, sorry | 11:11 |
| kevko | lajoskatona: thanks, now it is clear ... bdist_wheel is bumping last number in version and adding suffix | 11:12 |
| frickler | lajoskatona: slaweq: the issue is triggered by https://review.opendev.org/c/openstack/requirements/+/846785 . I wonder if there could be a <21.0 cap instead to allow people to still install latest stable/yoga instead of latest release. the other option would be to much more frequently do stable releases, like essentially after every patch | 11:28 |
| frickler | prometheanfire: ^^ this is also a requirements question | 11:28 |
| lajoskatona | frickler: good question, this was triggered by stadium failures as I remember | 11:31 |
| lajoskatona | frickler: the best would be to do not import Neutron, but that is huge work.... | 11:31 |
| opendevreview | OpenStack Release Bot proposed openstack/neutron-lib stable/zed: Update .gitreview for stable/zed https://review.opendev.org/c/openstack/neutron-lib/+/856740 | 11:47 |
| opendevreview | OpenStack Release Bot proposed openstack/neutron-lib stable/zed: Update TOX_CONSTRAINTS_FILE for stable/zed https://review.opendev.org/c/openstack/neutron-lib/+/856741 | 11:47 |
| opendevreview | OpenStack Release Bot proposed openstack/neutron-lib master: Update master for stable/zed https://review.opendev.org/c/openstack/neutron-lib/+/856742 | 11:47 |
| opendevreview | OpenStack Release Bot proposed openstack/neutron-lib master: Add Python3 antelope unit tests https://review.opendev.org/c/openstack/neutron-lib/+/856743 | 11:47 |
| opendevreview | OpenStack Release Bot proposed openstack/os-ken stable/zed: Update .gitreview for stable/zed https://review.opendev.org/c/openstack/os-ken/+/856744 | 11:47 |
| opendevreview | OpenStack Release Bot proposed openstack/os-ken stable/zed: Update TOX_CONSTRAINTS_FILE for stable/zed https://review.opendev.org/c/openstack/os-ken/+/856745 | 11:47 |
| opendevreview | OpenStack Release Bot proposed openstack/os-ken master: Update master for stable/zed https://review.opendev.org/c/openstack/os-ken/+/856746 | 11:47 |
| opendevreview | OpenStack Release Bot proposed openstack/os-ken master: Add Python3 antelope unit tests https://review.opendev.org/c/openstack/os-ken/+/856747 | 11:47 |
| opendevreview | OpenStack Release Bot proposed openstack/ovsdbapp stable/zed: Update .gitreview for stable/zed https://review.opendev.org/c/openstack/ovsdbapp/+/856748 | 11:48 |
| opendevreview | OpenStack Release Bot proposed openstack/ovsdbapp stable/zed: Update TOX_CONSTRAINTS_FILE for stable/zed https://review.opendev.org/c/openstack/ovsdbapp/+/856749 | 11:48 |
| opendevreview | OpenStack Release Bot proposed openstack/ovsdbapp master: Update master for stable/zed https://review.opendev.org/c/openstack/ovsdbapp/+/856750 | 11:48 |
| opendevreview | OpenStack Release Bot proposed openstack/ovsdbapp master: Add Python3 antelope unit tests https://review.opendev.org/c/openstack/ovsdbapp/+/856751 | 11:48 |
| opendevreview | OpenStack Release Bot proposed openstack/python-neutronclient stable/zed: Update .gitreview for stable/zed https://review.opendev.org/c/openstack/python-neutronclient/+/856752 | 11:48 |
| opendevreview | OpenStack Release Bot proposed openstack/python-neutronclient stable/zed: Update TOX_CONSTRAINTS_FILE for stable/zed https://review.opendev.org/c/openstack/python-neutronclient/+/856753 | 11:48 |
| opendevreview | OpenStack Release Bot proposed openstack/python-neutronclient master: Update master for stable/zed https://review.opendev.org/c/openstack/python-neutronclient/+/856754 | 11:48 |
| opendevreview | OpenStack Release Bot proposed openstack/python-neutronclient master: Add Python3 antelope unit tests https://review.opendev.org/c/openstack/python-neutronclient/+/856755 | 11:48 |
| Rick_Zhong | hello | 12:47 |
| *** dasm|off is now known as dasm | 13:20 | |
| haleyb | lajoskatona: i might not be able to attend drivers meeting as i have a repair person that just rang door | 13:53 |
| haleyb | actually it wasn't them but they are coming... :) | 13:54 |
| lajoskatona | haleyb: ok, thanks, I just arrived back with my son also:-) | 13:56 |
| haleyb | just got a text he's running late, so i have until :15 after now | 13:56 |
| lajoskatona | #startmeeting neutron_drivers | 14:00 |
| opendevmeet | Meeting started Fri Sep 9 14:00:10 2022 UTC and is due to finish in 60 minutes. The chair is lajoskatona. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| opendevmeet | The meeting name has been set to 'neutron_drivers' | 14:00 |
| lajoskatona | o/ | 14:00 |
| mlavalle | o/ | 14:00 |
| obondarev | hi | 14:00 |
| skingFD | hi | 14:00 |
| haleyb | hi | 14:00 |
| slaweq | o/ | 14:00 |
| lajoskatona | Let's start we have quoume as I count | 14:02 |
| lajoskatona | We have one RFE for today | 14:02 |
| lajoskatona | [RFE] OVN support for vnic type virtio-forwarder (#link https://bugs.launchpad.net/neutron/+bug/1988542 ) | 14:02 |
| skingFD | Hi, this RFE is reported by me | 14:02 |
| lajoskatona | If I understand well this is realted to some smart-nic feature, am I rigth? | 14:03 |
| lajoskatona | Hi skingFD, thanks for proposing | 14:03 |
| skingFD | Yes, it is a new feature related to smart-nic | 14:03 |
| skingFD | It is a standard already supported by NOVA and some smartnics, while neutron does not | 14:04 |
| lajoskatona | the nova spec speaks about netronome only, and as I remember some work was done in Neutron also | 14:04 |
| lajoskatona | for OVS | 14:04 |
| skingFD | Yes, the ovs plugin already supports it | 14:04 |
| skingFD | but the ovn still does not | 14:04 |
| slaweq | are there any more changes required on neutron side for that, besides what You already proposed? | 14:04 |
| skingFD | I don't think there are more changes needed | 14:05 |
| mlavalle | then it seems like a no brainer to me | 14:05 |
| skingFD | It is a open-sourced vnic type, beside netronome, everyone can use it | 14:05 |
| lajoskatona | Agree | 14:06 |
| obondarev | cool then, +1 from me as well | 14:06 |
| lajoskatona | even an RFE is too much perhaps, but we discussed it and have clear picture | 14:06 |
| lajoskatona | +1 | 14:06 |
| slaweq | thx | 14:07 |
| slaweq | +1 | 14:07 |
| haleyb | +1 | 14:07 |
| mlavalle | to formalize my position.... +1 | 14:07 |
| lajoskatona | We have agreement than :-) | 14:07 |
| mlavalle | I like this type of RFE | 14:08 |
| skingFD | thx | 14:08 |
| lajoskatona | skingFD: thanks for proposing and working on this | 14:08 |
| mlavalle | straightforward | 14:08 |
| slaweq | yeah | 14:08 |
| mlavalle | given the evidence | 14:08 |
| lajoskatona | #topic On Demand Agenda | 14:08 |
| lajoskatona | Do you have anything to discuss today? | 14:08 |
| skingFD | Appreciate more code reviewing on the patch I've supported | 14:08 |
| skingFD | It's my first time contributing to neutron | 14:09 |
| mlavalle | skingFD: I'll take a look soon | 14:09 |
| mlavalle | and thank you for your contribution. we welcome you! | 14:09 |
| skingFD | So more check is needed I guess :) | 14:09 |
| lajoskatona | skingFD: sure, we are now closing the Zed release so next weeks will be busy | 14:09 |
| skingFD | :mlavalle Thanks! | 14:09 |
| ges | Do we have time for another small RFE? | 14:10 |
| lajoskatona | ges: I think yes | 14:11 |
| slaweq | we have plenty of time still :) | 14:11 |
| ges | [rfe] rate-limit metadata API : https://bugs.launchpad.net/neutron/+bug/1989199 | 14:11 |
| mlavalle | keep in time haleyb will drop off soon | 14:11 |
| mlavalle | will we still have quorum? | 14:11 |
| haleyb | mlavalle: i'm still here for now :) | 14:12 |
| mlavalle | ok | 14:12 |
| mlavalle | LOL, this RFE is hot just out of the oven | 14:12 |
| ges | yep! | 14:12 |
| mlavalle | be careful, don't burn yourselves | 14:12 |
| lajoskatona | :-) | 14:13 |
| ges | too early maybe? I understand if we need to wait a bit! | 14:13 |
| mlavalle | naah, I don't think so | 14:14 |
| slaweq | ges: do You want to do it with config option so it will be for all networks or routers on nodes? | 14:14 |
| mlavalle | ges: is this for ml2/ovs | 14:14 |
| mlavalle | ? | 14:14 |
| slaweq | or somehow through API per network or router? | 14:14 |
| slaweq | mlavalle: I think that the same can apply to ovn as well | 14:15 |
| ges | slaweq: in our PoC I have done that with some config options | 14:15 |
| obondarev | I know some users set rate limiting for metadata at the VIP level, having this native does make sense to me | 14:15 |
| lajoskatona | agree | 14:15 |
| slaweq | as we do have haproxy in the ovn-meta namespace there | 14:15 |
| ges | the rate-limiting would be done by source ip | 14:16 |
| haleyb | https://www.haproxy.com/blog/four-examples-of-haproxy-rate-limiting/#sliding-window-rate-limiting | 14:16 |
| obondarev | I think it might worth a spec to discuss options | 14:17 |
| lajoskatona | +1 | 14:17 |
| ges | mlavalle: I'm not sure I understand how it relates to either ml2 or ovs :/ | 14:17 |
| slaweq | I agree | 14:17 |
| slaweq | for example: will it be just config knob to enable/disable rate-limit or will there be knob to configure actual limit of requests | 14:18 |
| lajoskatona | ges: In neutron there's 2 metadata agent now one for OVN and one for all other (OVS, linuxbridge) | 14:18 |
| haleyb | i would think we could enable this by default, if it's by source IP it should be Ok and not impact normal operations, correct? | 14:19 |
| slaweq | haleyb: as long as it will be set to some reasonable value to not affect e.g. cloud-init during boot of the vms | 14:20 |
| ges | lajoskatona: ah I see! We don't use OVN but I suppose it could go there as well | 14:20 |
| lajoskatona | ges: yes, exactly | 14:20 |
| lajoskatona | As I see there's a lot of things which should be clarified in a spec | 14:21 |
| lajoskatona | So to summarize: the RFE generally looks ok, but we need a spec to discuss the details, is that correct? | 14:21 |
| obondarev | +1 | 14:22 |
| haleyb | slaweq: yes, making it large enough to cover the cloud-init case +some% should limit someone doing a DoS after they boot | 14:22 |
| slaweq | +1 for me | 14:22 |
| haleyb | Ok, well my repair guy is here, have to run, i'm fine with this for now... | 14:22 |
| lajoskatona | +1 | 14:22 |
| mlavalle | +1 | 14:22 |
| lajoskatona | haleyb: thanks | 14:22 |
| ges | thanks! | 14:23 |
| lajoskatona | Ok, I wil update the RFE, thanks ges for proposing it | 14:23 |
| ges | yw! next step is to write a spec, right? Should I do it? | 14:24 |
| lajoskatona | ges: yes, here is a template: https://opendev.org/openstack/neutron-specs/src/branch/master/specs/zed/placeholder.rst | 14:25 |
| lajoskatona | soon there will be a new folder for Antelope/2023.1 | 14:25 |
| mlavalle | I think the folder is already there | 14:25 |
| lajoskatona | and it is really there | 14:26 |
| mlavalle | https://opendev.org/openstack/neutron-specs/src/branch/master/specs/2023.1 | 14:26 |
| lajoskatona | thanks mlavalle | 14:26 |
| mlavalle | yeah, I recently approved the patch ;-) | 14:26 |
| ges | Alright! | 14:26 |
| lajoskatona | I looked for the end of alphabet as usual, and we reached the end of it :-) | 14:26 |
| mlavalle | LOL, you just went to the end | 14:26 |
| lajoskatona | Is there anything we can discuss today? | 14:26 |
| slaweq | nothing from me | 14:28 |
| mlavalle | neither from me | 14:28 |
| lajoskatona | If nothing more , let's close the meeting for today | 14:28 |
| lajoskatona | Thanks for coming :-) | 14:28 |
| lajoskatona | #endmeeting | 14:28 |
| opendevmeet | Meeting ended Fri Sep 9 14:28:29 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:28 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-09-09-14.00.html | 14:28 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-09-09-14.00.txt | 14:28 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-09-09-14.00.log.html | 14:28 |
| lajoskatona | o/ | 14:28 |
| slaweq | have a great weekend | 14:28 |
| ges | Thanks everyone ! | 14:28 |
| slaweq | o/ | 14:28 |
| lajoskatona | Have a nice weekend! | 14:28 |
| mlavalle | o/ | 14:28 |
| obondarev | o/ | 14:28 |
| spatel | I am running yoga release and noticed neutron-ovn-metadata consuming more CPU compare to all other process, is that normal? | 14:29 |
| prometheanfire | frickler: we are VERY reluctant to add a cap, but since neutron is a managed project if there were some promise that the project wouldn't need two major releases within a cycle it could work | 14:38 |
| prometheanfire | and only for stable branches | 14:38 |
| prometheanfire | something we could try for zed branches | 14:38 |
| frickler | prometheanfire: well currently there is a hard === pin, switching to <= would actually be weakening the constraint, not strengthening it | 14:46 |
| opendevreview | Merged openstack/python-neutronclient master: Update master for stable/zed https://review.opendev.org/c/openstack/python-neutronclient/+/856754 | 14:53 |
| opendevreview | Merged openstack/neutron-lib master: Update master for stable/zed https://review.opendev.org/c/openstack/neutron-lib/+/856742 | 14:55 |
| prometheanfire | frickler: constraints have to be ===, the global-requirements file is where the cap would go | 14:57 |
| opendevreview | OpenStack Release Bot proposed openstack/os-vif stable/zed: Update .gitreview for stable/zed https://review.opendev.org/c/openstack/os-vif/+/856780 | 15:03 |
| opendevreview | OpenStack Release Bot proposed openstack/os-vif stable/zed: Update TOX_CONSTRAINTS_FILE for stable/zed https://review.opendev.org/c/openstack/os-vif/+/856781 | 15:03 |
| opendevreview | OpenStack Release Bot proposed openstack/os-vif master: Update master for stable/zed https://review.opendev.org/c/openstack/os-vif/+/856782 | 15:03 |
| opendevreview | OpenStack Release Bot proposed openstack/os-vif master: Add Python3 antelope unit tests https://review.opendev.org/c/openstack/os-vif/+/856783 | 15:03 |
| opendevreview | Lajos Katona proposed openstack/neutron-fwaas master: Adopt to latest VlanManager and oslo.db changes https://review.opendev.org/c/openstack/neutron-fwaas/+/855891 | 15:11 |
| opendevreview | Guillaume Espanel proposed openstack/neutron-specs master: Add spec for metadata-rate-limit https://review.opendev.org/c/openstack/neutron-specs/+/856831 | 15:54 |
| opendevreview | Lajos Katona proposed openstack/neutron-vpnaas master: Adopt to oslo.db 12.1.0 https://review.opendev.org/c/openstack/neutron-vpnaas/+/856857 | 19:28 |
| *** dasm is now known as dasm|off | 23:13 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!