Friday, 2022-08-19

*** dmellado_ is now known as dmellado00:10
*** dmellado_ is now known as dmellado02:14
*** dmellado_ is now known as dmellado02:47
opendevreviewliuyulong proposed openstack/neutron stable/ussuri: Fix migration failed due TypeError of new_vlan_tag  https://review.opendev.org/c/openstack/neutron/+/85375005:18
opendevreviewliuyulong proposed openstack/neutron stable/train: Fix migration failed due TypeError of new_vlan_tag  https://review.opendev.org/c/openstack/neutron/+/85375105:18
opendevreviewliuyulong proposed openstack/neutron stable/stein: Fix migration failed due TypeError of new_vlan_tag  https://review.opendev.org/c/openstack/neutron/+/85375205:18
opendevreviewliuyulong proposed openstack/neutron stable/rocky: Fix migration failed due TypeError of new_vlan_tag  https://review.opendev.org/c/openstack/neutron/+/85375305:18
opendevreviewliuyulong proposed openstack/neutron stable/rocky: Fix migration failed due TypeError of new_vlan_tag  https://review.opendev.org/c/openstack/neutron/+/85375305:19
opendevreviewliuyulong proposed openstack/neutron stable/queens: Fix migration failed due TypeError of new_vlan_tag  https://review.opendev.org/c/openstack/neutron/+/85375405:20
*** amoralej|off is now known as amoralej06:21
opendevreviewLajos Katona proposed openstack/neutron-tempest-plugin master: DNM: Check stein branch  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/85379407:58
opendevreviewLajos Katona proposed openstack/neutron stable/stein: DNM: check stein branch fixes  https://review.opendev.org/c/openstack/neutron/+/85360808:01
opendevreviewLajos Katona proposed openstack/neutron stable/stein: DNM: check stein branch fixes  https://review.opendev.org/c/openstack/neutron/+/85360808:01
*** dmellado_ is now known as dmellado09:03
opendevreviewLajos Katona proposed openstack/neutron-tempest-plugin master: DNM: Check stein branch  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/85379409:08
opendevreviewSlawek Kaplonski proposed openstack/neutron master: [S-RBAC] Remove system scope from the API policies  https://review.opendev.org/c/openstack/neutron/+/85379809:41
opendevreviewSlawek Kaplonski proposed openstack/neutron master: [S-RBAC] Use ADMIN rule instead of PROJECT_ADMIN in the new policies  https://review.opendev.org/c/openstack/neutron/+/85379909:41
opendevreviewSlawek Kaplonski proposed openstack/neutron master: [S-RBAC] Rename ProjectAdmin* unit tests to Admin*  https://review.opendev.org/c/openstack/neutron/+/85380009:41
opendevreviewSlawek Kaplonski proposed openstack/neutron master: [S-RBAC] Remove definitions of not used roles  https://review.opendev.org/c/openstack/neutron/+/85380109:41
ralonsohslaweq, ^^ those patches should be for Zed release?09:46
slaweqralonsoh IMO it would be good if we could include them there09:47
ralonsohperfect09:47
slaweqbut I would like first gmann to check them09:48
slaweqI think it's all what we need to align with recent changes in the community goal update09:48
opendevreviewLajos Katona proposed openstack/neutron-tempest-plugin master: DNM: Check stein branch  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/85379409:57
opendevreviewMerged openstack/neutron-tempest-plugin master: Use StatefulConnection class to verify connectivity in SG tests  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/85320310:00
slaweqfrickler hi, You asked me few days ago about things which we miss in Cirros to be able to use only that image in neutron scenario tests10:10
slaweqhere's list https://paste.opendev.org/show/b4xNSkBoPDDF4EayMiVA/10:10
slaweqI hope I didn't missed anything from it10:10
ralonsohfrickler, and one request, if possible, apart from the requirements sent by slaweq 10:24
ralonsohis it possible to have "ping" command with -i (interval), accepting values under a second10:24
fricklerslaweq: ralonsoh: I will check those things, thanks for your feedback10:46
opendevreviewLajos Katona proposed openstack/neutron-tempest-plugin master: DNM: Check stein branch  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/85379411:30
lajoskatonabcafarel: Hi, Some trials for the stein issue: https://review.opendev.org/c/openstack/neutron/+/853608 & https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/85379411:42
lajoskatonabcafarel: the neutron patch is actually testing the n-t-p patch, and it contains the comments to stop grenade11:42
lajoskatonabcafarel: by this doc grenade is experimental by QA team on older branches: https://docs.openstack.org/grenade/latest/stable_branch_testing_policy.html11:44
*** dmellado_ is now known as dmellado11:44
bcafarellajoskatona: +1 and grenade on these old releases is less important we do not have large changes in so upgrades should not break on these11:45
lajoskatonabcafarel: one of the famous last sentences? But I agree, we have many jobs to keep working and master to keep it in shape for the features and bugs also11:47
bcafarel:) yes hopefully I have not jinxed it (especially for really old branches with limited number of backports)11:47
bcafareland n-t-p looks similar to https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/843799 (train)11:48
*** tbachman_ is now known as tbachman13:10
*** dmellado_ is now known as dmellado13:20
*** amoralej is now known as amoralej|lunch13:39
*** dasm|off is now known as dasm13:59
lajoskatona#startmeeting neutron_drivers14:00
opendevmeetMeeting started Fri Aug 19 14:00:14 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'neutron_drivers'14:00
mlavalleo/14:00
lajoskatonaHi!14:00
ralonsohhi14:00
obondarevhi14:00
slaweqhi14:00
lajoskatonaAs I see we have quorum14:02
lajoskatonaLet's start14:02
haleybhi14:02
lajoskatonaWe have 2 RFEs for today14:02
lajoskatona[RFE] Add possibility to define default security group rules (#link https://bugs.launchpad.net/neutron/+bug/1983053 )14:02
slaweqthat's proposed by me14:03
lajoskatonaI think we discussed something like this but I was not able to find it in logs :-(14:03
slaweqduring one of the PTGs I think we discussed that default rules aren't the greates14:04
slaweqbut conclusion was to not change them to not break backward compatibility14:04
lajoskatonaahh, ok so it was one of the PTGs14:05
slaweqbut recently we discussed that internall again and we think that it could be made better than it's now with hardcoded rules14:05
slaweqIMO the best way would be to add API resource like "default SG rule"14:05
slaweqand those would be stored in Neutron database and used for every new SG14:05
slaweqinstead of currently used hardcoded rules14:06
slaweqonly admin would be able to change those default rules14:06
obondarevsorry, for every new SG or project14:06
obondarev?14:06
ralonsohgood question14:06
lajoskatonaproject as I understand14:06
slaweqobondarev there are 2 things here14:06
slaweq1. Default SG which is created automatically for every new project14:07
slaweqthat one have always 4 rules added automatically14:07
obondarevyep14:07
slaweq2. Every other SG created by user - this one has 2 rules added by Neutron automatically14:07
slaweqso, we can add possibility to define by admin new rules for both of those types of security groups14:08
ralonsohwhere/how those generic default rules are created?14:08
haleybTwo questions - 1) Why can't this just be a post project create task by the admin, which could work today?  2) Is the user not allowed to change these rules?14:10
slaweqhttps://github.com/openstack/neutron/blob/b551516e30ad7ccd38a0ef651741c307fa4e8216/neutron/db/securitygroups_db.py#L8014:10
*** amoralej|lunch is now known as amoralej14:10
obondarevI guess these 14:10
obondarevsorry, disregard please14:10
slaweqthis is method which creates security group and adds rules to it14:10
ralonsohno no I mean, how do you propose it?14:11
ralonsohhow do you propose to create those default rules?14:11
slaweqhaleyb users can remove/change those rules14:11
slaweqbut:14:11
slaweqa) we had some requests from customers that admin would like to define for users some other set of the rules added automatically to the new SGs14:12
haleybSo not just to the default SG when the project is created?14:12
slaweqb) default SG rules which are added today aren't great, we know that rules with remote_group_id aren't scale well,14:12
slaweqhaleyb I think we can allow to define set of rules which will be added for each new SG and some "special" set of the rules which will be added also to each new "Default" SG14:13
slaweqthat shouldn't be problem14:13
haleybOk, the bug only mentions the default SG is why I ask14:14
lajoskatonaPersonally I tend also to think that this can be solved neatly with hot templates or other tools, but can accept that this will be better for customers14:14
lajoskatonaperhaps Neutron API is good place for such customization and default settings for sec-groups14:16
slaweqhaleyb sorry, it was probably my "shortcut" when I was writing RFE14:16
lajoskatonaBasically I am ok with this RFE, but I think we need a spec to see the details14:18
haleybslaweq: is there much of a use case for the non-default SG? for example, if I create a new SG for say secure access, do we want extra rules added there?14:18
haleybI could see adding icmp and ssh to default since we all do it first thing anyways, but that doesn't need a code change, just a heat template14:19
slaweqhaleyb not everyone is using heat14:19
slaweqI know it can be automated with some script14:20
slaweqbut we had such request to allow such modification14:20
slaweqand IMO it's reasonable request as it would be better instead of hardcoded things14:20
haleybslaweq: well, it could even just be in my create-project.sh script as a post-create step like you mention. just playing devils advocate14:21
obondarevmy 2 cents: I also know customers that are suffering from a "remote_group_id" rules in default SG14:22
ralonsohyeah, I'm ok with the feature (needed by some customers) but I waiting for the implementation details14:23
mlavalleyeah, that's a scuge14:23
mlavallescurge14:24
lajoskatonaSo let's have a spec and see the details for it14:25
mlavalle+114:25
slaweqof course I will write spec with proposed API changes first if this will be accepted14:25
haleybobondarev: ack, and this is maybe a more attractive option of doing this spec to not create those rules14:25
haleybif it was just adding rules it would be different (to me)14:25
lajoskatonaOk, let's vote than to see if we are ok with the RFE with the condition of a spec14:26
lajoskatona+1 from me14:26
ralonsoh+114:27
mlavalle+114:27
obondarev+114:27
haleyb+114:27
lajoskatonaok, thanks, I will update the RFE14:28
lajoskatonaThe 2nd one:14:28
lajoskatona[rfe][fwaas]support standard_attrs for firewall_group (#link https://bugs.launchpad.net/neutron/+bug/1986906 )14:28
slaweqthank You14:28
lajoskatonaAs I see this RFE is quite simple: let's have standard attrs for fwaas_groups14:30
slaweqI agree with lajoskatona and I have no objections for it14:31
ralonsohI'm ok too, looks an easy change14:31
obondarevyeah, looks pretty straightforward, no questions from me14:32
lajoskatonamlavalle, haleyb: what do you think?14:33
mlavalle+114:33
mlavallepretty straightforward14:33
mlavallewe don't need a spec, do we?14:34
mlavallejust kidding :-)14:34
lajoskatona:-)14:34
haleyb+1 as this should be on most objects14:34
lajoskatonaOk, I will update this RFE also, thanks for discussing it :-)14:34
lajoskatona#topic On Demand Agenda14:34
lajoskatonaDo you have anything more which we can discuss ?14:35
slaweqnothing from me14:35
mlavallenothing from me14:35
atimminshey all - looking for another review of https://review.opendev.org/c/openstack/neutron-specs/+/85160714:35
obondarevnope14:35
mlavalleatimmins: I'll review it today14:35
atimminsThanks!14:36
slaweqatimmins added to my review list14:36
slaweqbut I will check it next week probably14:36
lajoskatonaatimmins: I will check it also (perhaps early next week)14:36
lajoskatonaIf nothing more we can close the meeting14:36
lajoskatona#endmeeting14:36
opendevmeetMeeting ended Fri Aug 19 14:36:55 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:36
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-08-19-14.00.html14:36
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-08-19-14.00.txt14:36
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-08-19-14.00.log.html14:36
ralonsohbye14:36
lajoskatonaBye, have a nice weekend14:37
obondarevbye!14:37
slaweqo/14:37
mlavalleo/14:37
slaweqhave a nice weekend14:37
opendevreviewMerged openstack/neutron master: Add vpnaas to extensions supported by ovn  https://review.opendev.org/c/openstack/neutron/+/84700514:53
opendevreviewMerged openstack/neutron stable/ussuri: Fix migration failed due TypeError of new_vlan_tag  https://review.opendev.org/c/openstack/neutron/+/85375014:58
opendevreviewMerged openstack/neutron stable/train: Fix migration failed due TypeError of new_vlan_tag  https://review.opendev.org/c/openstack/neutron/+/85375114:58
*** amoralej is now known as amoralej|off15:10
opendevreviewArnau Verdaguer proposed openstack/neutron master: [Trunk] Update the trunk status with the parent status  https://review.opendev.org/c/openstack/neutron/+/85377915:40
fricklerslaweq: ralonsoh: I created https://etherpad.opendev.org/p/cirros-for-neutron-tempest-plugin for tracking, some things should already work, for some I've made PRs, but python3 is questionable. will do some further sizing tests next week16:59
ralonsohfrickler, thanks17:00
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN][QoS] Add minimum bandwidth rule support to ML2/OVN  https://review.opendev.org/c/openstack/neutron/+/84229217:13
opendevreviewJakub Libosvar proposed openstack/neutron master: ovn: Don't fail db sync if new IP allocation fails for metadata  https://review.opendev.org/c/openstack/neutron/+/85384020:24
*** dasm is now known as dasm|off21:33
opendevreviewMerged openstack/neutron master: [S-RBAC] Remove system scope from the API policies  https://review.opendev.org/c/openstack/neutron/+/85379823:31
opendevreviewMerged openstack/neutron master: [S-RBAC] Use ADMIN rule instead of PROJECT_ADMIN in the new policies  https://review.opendev.org/c/openstack/neutron/+/85379923:31
opendevreviewMerged openstack/neutron master: [S-RBAC] Rename ProjectAdmin* unit tests to Admin*  https://review.opendev.org/c/openstack/neutron/+/85380023:31

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!