opendevreview | yatin proposed openstack/networking-ovn stable/train: [OVN] Pin OVS/OVN versions in Octavia job https://review.opendev.org/c/openstack/networking-ovn/+/843477 | 05:13 |
---|---|---|
opendevreview | yatin proposed openstack/networking-ovn stable/train: Revert "Use Port_Binding up column to set Neutron port status" https://review.opendev.org/c/openstack/networking-ovn/+/843391 | 05:29 |
opendevreview | yatin proposed openstack/networking-ovn stable/train: Refactor the OVN revision module to access the DB correctly https://review.opendev.org/c/openstack/networking-ovn/+/843486 | 05:35 |
opendevreview | Lajos Katona proposed openstack/networking-bagpipe master: Remove "distutils" library https://review.opendev.org/c/openstack/networking-bagpipe/+/842369 | 06:37 |
lajoskatona | slaweq, obondarev: when you have some free time could you please check this doc patch to add back fwaas docs to Neutron doc tree: https://review.opendev.org/c/openstack/neutron/+/841748 ? | 06:41 |
obondarev | lajoskatona: sure, done | 06:45 |
lajoskatona | obondarev: thanks | 06:45 |
opendevreview | Fernando Royo proposed openstack/ovn-octavia-provider master: Fix way of calculate LB status after HM event https://review.opendev.org/c/openstack/ovn-octavia-provider/+/843308 | 07:07 |
opendevreview | yatin proposed openstack/neutron master: [WIP] Switch fullstack/functional fips jobs to 9-stream https://review.opendev.org/c/openstack/neutron/+/843245 | 07:34 |
opendevreview | yatin proposed openstack/neutron master: [DNM] fips fullstack/functional test without dbcounter https://review.opendev.org/c/openstack/neutron/+/843252 | 07:37 |
opendevreview | Oleg Bondarev proposed openstack/neutron master: Functional test: wait for dhclient in test_good_address_allocation https://review.opendev.org/c/openstack/neutron/+/843389 | 07:40 |
opendevreview | yatin proposed openstack/neutron master: [WIP] Switch fullstack/functional fips jobs to 9-stream https://review.opendev.org/c/openstack/neutron/+/843245 | 07:53 |
opendevreview | Merged openstack/neutron master: Create an index for "ports.network_id" https://review.opendev.org/c/openstack/neutron/+/841761 | 07:59 |
opendevreview | Edward Hope-Morley proposed openstack/neutron stable/yoga: Partially revert "Do not link up HA router gateway in backup node" https://review.opendev.org/c/openstack/neutron/+/843581 | 08:38 |
opendevreview | Edward Hope-Morley proposed openstack/neutron stable/xena: Partially revert "Do not link up HA router gateway in backup node" https://review.opendev.org/c/openstack/neutron/+/843582 | 08:42 |
opendevreview | yatin proposed openstack/neutron master: [DNM] fips fullstack/functional test without dbcounter https://review.opendev.org/c/openstack/neutron/+/843252 | 08:44 |
ralonsoh | bcafarel, https://review.opendev.org/q/Id1907481077d230e4461906a1a2a1447abac330a if you have some minutes. I've replied to your comments | 08:49 |
ralonsoh | thanks in advance | 08:49 |
ykarel | lajoskatona, slaweq ralonsoh can you please check the revert https://review.opendev.org/c/openstack/neutron/+/843426 | 08:57 |
ralonsoh | ok | 08:58 |
ykarel | squashed multiple commits | 08:58 |
ykarel | thx in advance | 08:58 |
lajoskatona | ykarel: I set https://bugs.launchpad.net/tripleo/+bug/1964940 to have Neutron affected | 09:00 |
ykarel | lajoskatona, okk | 09:01 |
opendevreview | yatin proposed openstack/neutron master: [DNM] fips fullstack/functional test without dbcounter https://review.opendev.org/c/openstack/neutron/+/843252 | 09:10 |
lajoskatona | ykarel: wouldn't it be simpler to revert one-by-one? | 09:14 |
ykarel | lajoskatona, need to backport these till train, after yoga, all these are already squashed | 09:15 |
ykarel | so thought of doing same in yoga/master | 09:15 |
lajoskatona | ykarel: I feared it will be the answer, for future reference I will add comment to review to make it cleaner for the future developers :-) | 09:16 |
ykarel | lajoskatona, ok Thanks | 09:17 |
slaweq | ykarel: +2 | 09:21 |
opendevreview | Fernando Royo proposed openstack/ovn-octavia-provider master: Fix request to OVN NB DB API https://review.opendev.org/c/openstack/ovn-octavia-provider/+/839055 | 09:31 |
opendevreview | yatin proposed openstack/networking-ovn stable/train: [DNM] Test ovn tempest job on nested virt nodes https://review.opendev.org/c/openstack/networking-ovn/+/843588 | 09:34 |
slaweq | lajoskatona: ralonsoh ykarel hi, I'm now looking at https://review.opendev.org/c/openstack/neutron/+/841246 and TBH I think that we should remove requirements.txt file from the irrelevant files list for e.g. scenario jobs | 09:40 |
slaweq | IMO any changes in requirements should be tested with all possible jobs | 09:40 |
ralonsoh | slaweq, agree | 09:41 |
slaweq | I can propose patch for it but I first wanted to know Your opinion about it | 09:41 |
ralonsoh | slaweq, in any case, we usually take the upper versions defined in requirements | 09:41 |
ralonsoh | actually, this version of n-lib is being used right now | 09:41 |
ralonsoh | this patch is only to "consolidate" | 09:41 |
ralonsoh | but I'm ok | 09:42 |
slaweq | yeah, I'm good with this patch | 09:42 |
ralonsoh | please, propose this patch | 09:42 |
slaweq | but I'm talking generally about requirements file | 09:42 |
slaweq | as I just discovered that in that patch :) | 09:42 |
slaweq | ralonsoh++ ok, I will propose it | 09:42 |
opendevreview | Merged openstack/neutron master: [UT][ovn] Access config options after they are registered https://review.opendev.org/c/openstack/neutron/+/843461 | 10:07 |
opendevreview | Slawek Kaplonski proposed openstack/neutron master: Remove requirements.txt from irrelevant files in CI jobs https://review.opendev.org/c/openstack/neutron/+/843594 | 10:09 |
opendevreview | Fernando Royo proposed openstack/ovn-octavia-provider master: Fix Load balancer remains on PENDING_CREATE https://review.opendev.org/c/openstack/ovn-octavia-provider/+/842382 | 10:18 |
opendevreview | Frode Nordahl proposed openstack/neutron master: [OVN] Make binding profile validation more robust https://review.opendev.org/c/openstack/neutron/+/843601 | 10:30 |
opendevreview | Fernando Royo proposed openstack/ovn-octavia-provider master: Fix Load balancer remains on PENDING_CREATE https://review.opendev.org/c/openstack/ovn-octavia-provider/+/842382 | 10:37 |
ykarel | slaweq, almost all jobs already run with upper-constraints | 10:39 |
ykarel | not sure running all those jobs jobs with requirements.txt will really help | 10:40 |
ykarel | dependency related issue should alraedy be caught by the limited functional, tox jobs running there | 10:40 |
ykarel | or there is some case where we can catch some issues with those extra jobs? | 10:40 |
ykarel | i commented just to understand that case, else i think it's just extra load | 10:54 |
ralonsoh | lucasagomes, https://review.opendev.org/c/openstack/networking-ovn/+/843477 please, we need this patch to fix the n-ovn CI | 11:06 |
opendevreview | Elvira García Ruiz proposed openstack/neutron-specs master: Add spec for DNS subdomain support in OVN https://review.opendev.org/c/openstack/neutron-specs/+/832658 | 11:16 |
opendevreview | Merged openstack/neutron master: Remove session active check in "_add_segment_host_mapping_for_segment" https://review.opendev.org/c/openstack/neutron/+/843294 | 11:20 |
opendevreview | Merged openstack/neutron master: Revert "doc: Remove fwaas references from docs" https://review.opendev.org/c/openstack/neutron/+/841748 | 11:20 |
opendevreview | Merged openstack/neutron stable/yoga: Switch to cirros uec image in multinode jobs https://review.opendev.org/c/openstack/neutron/+/843396 | 11:20 |
opendevreview | Merged openstack/neutron stable/xena: Switch to cirros uec image in multinode jobs https://review.opendev.org/c/openstack/neutron/+/843453 | 11:20 |
opendevreview | Merged openstack/neutron stable/wallaby: Switch to cirros uec image in multinode jobs https://review.opendev.org/c/openstack/neutron/+/843456 | 11:20 |
slaweq | ykarel: I don't know any specific case when it can catch some specific issue | 11:20 |
opendevreview | Merged openstack/neutron master: [OVN][FT] Wait until virtual parents are written https://review.opendev.org/c/openstack/neutron/+/841298 | 11:20 |
opendevreview | Elvira García Ruiz proposed openstack/neutron-specs master: Add spec for DNS subdomain support in OVN https://review.opendev.org/c/openstack/neutron-specs/+/832658 | 11:21 |
slaweq | I just tought that it may be good to run all jobs on such changes, e.g. when we are adding/removing something from requirements file | 11:21 |
ykarel | slaweq, ralonsoh pointed out one valid case i.e removing a requirement which may cause tempest failure | 11:22 |
slaweq | yeah, that's what I though too | 11:23 |
lajoskatona | slaweq, ykarel: I agree with slaweq, it is slightly related but now to have some early feedback I created a DNM patch in neutron-tempest-plugin to run all stadiums also with this change | 11:24 |
lajoskatona | slaweq, ykarel: and as it was a depends-on only I have to check if I got really the result which I was looking for | 11:24 |
slaweq | lajoskatona: I think they should be ok, but it's worth to check to be sure | 11:25 |
ykarel | yeap those should be already ok as all should be using u-c | 11:26 |
opendevreview | Rodolfo Alonso proposed openstack/neutron master: Set "type=virtual" for OVN LSP with parent ports https://review.opendev.org/c/openstack/neutron/+/843474 | 11:27 |
lucasagomes | ralonsoh, looking, sorry I was having lunch | 11:58 |
ralonsoh | sure, no rush | 11:59 |
opendevreview | Merged openstack/networking-ovn stable/train: [OVN] Pin OVS/OVN versions in Octavia job https://review.opendev.org/c/openstack/networking-ovn/+/843477 | 12:11 |
opendevreview | Merged openstack/neutron master: Refactor the OVN revision module to access the DB correctly https://review.opendev.org/c/openstack/neutron/+/843478 | 12:12 |
opendevreview | Merged openstack/neutron master: Bump neutron-lib to 2.21.0 https://review.opendev.org/c/openstack/neutron/+/841246 | 12:12 |
opendevreview | yatin proposed openstack/neutron master: [DNM] fips fullstack/functional test without dbcounter https://review.opendev.org/c/openstack/neutron/+/843252 | 12:15 |
opendevreview | yatin proposed openstack/tap-as-a-service master: Make neutron tempest plugin job voting again https://review.opendev.org/c/openstack/tap-as-a-service/+/843615 | 12:31 |
ykarel | lajoskatona, switching back to voting ^ | 12:31 |
lajoskatona | ykarel: thanks, it was on my todo, but just burning my time on meetings :-) | 12:33 |
opendevreview | Frode Nordahl proposed openstack/neutron master: [OVN] Make binding profile validation more robust https://review.opendev.org/c/openstack/neutron/+/843601 | 12:39 |
opendevreview | yatin proposed openstack/neutron master: [WIP] Switch fullstack/functional fips jobs to 9-stream https://review.opendev.org/c/openstack/neutron/+/843245 | 13:07 |
opendevreview | Ghanshyam proposed openstack/neutron-tempest-plugin master: DNM: testing Tempest pin in stable/victoria https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/843299 | 13:51 |
lajoskatona | #startmeeting neutron_drivers | 14:00 |
opendevmeet | Meeting started Fri May 27 14:00:23 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 |
opendevreview | Slawek Kaplonski proposed openstack/neutron master: Use new combined neutron_tempest_plugin as nftables jobs parent https://review.opendev.org/c/openstack/neutron/+/843618 | 14:00 |
lajoskatona | o/ | 14:00 |
mlavalle2 | o/ | 14:00 |
opendevreview | Slawek Kaplonski proposed openstack/neutron master: Update ci jobs docs https://review.opendev.org/c/openstack/neutron/+/843619 | 14:00 |
amotoki | hi | 14:00 |
mtomaska | o/ | 14:00 |
slaweq | o/ | 14:01 |
lajoskatona | I think we can start | 14:02 |
lajoskatona | We have one RFE for today: | 14:02 |
lajoskatona | [RFE] Allow setting --dst-port for all port based protocols at once (#link https://bugs.launchpad.net/neutron/+bug/1973487) | 14:02 |
lajoskatona | the idea seems valid for me | 14:03 |
mtomaska | Background: This came from a customer I have been working with | 14:03 |
lajoskatona | mtomaska: yeah that is mentioned in one of the comments | 14:04 |
slaweq | AFAIK current behaviour is consistent with e.g. iptables | 14:04 |
mtomaska | my main concern is if that option can bring some implications. In another words... | 14:04 |
slaweq | and if we will accept protocol "any" and some port, we will need to apply many rules in e.g. iptables (I'm not sure about ovn and ovs fw) | 14:04 |
amotoki | dst-port is L4 field so it totally depends on L4 protocol. How can we support all L4 protocol? | 14:05 |
amotoki | I am not sure how we can determine if a L4 protocol is port-based. | 14:06 |
ralonsoh | (hi, sorry, network problems) | 14:06 |
mtomaska | Do you see any corner cases such that specifying '--protocol all_l4' would case problems on some systems? The 'all_l4' protocol arg will just iterate over this list of protocols | 14:08 |
mtomaska | https://github.com/openstack/neutron/blob/master/neutron/common/_constants.py#L23-L29 | 14:08 |
mlavalle2 | and maybe we should not get so hung up on the "L4" piece. If we were going to implement this, we would clarify the list of protocols supported by the feature | 14:10 |
mtomaska | I also want to mention that customer was just annoyed that they have to issue cli command for each --protocol (udp | tcp and so on). The counter argument could be that its not hard to automate it :) | 14:10 |
lajoskatona | mlavalle2: aggree the bases of that should be the above constant | 14:11 |
mlavalle2 | yeap | 14:11 |
amotoki | mlavalle2: +1 | 14:11 |
slaweq | there is 5 protocols in that list mtomaska so is it really that hard for the customer to automate it on the client's side? | 14:11 |
obondarev | hi, sorry for being late | 14:12 |
slaweq | IMHO it sounds like something what should be done on the client's side really | 14:12 |
mtomaska | slaweq. IDK but that was my response as well :) | 14:12 |
lajoskatona | Is there any difference if the user call 5 CLIs to issue this or doing the same with one call from iptables or such perspective? | 14:12 |
opendevreview | yatin proposed openstack/neutron master: [WIP] Switch fullstack/functional fips jobs to 9-stream https://review.opendev.org/c/openstack/neutron/+/843245 | 14:12 |
slaweq | otherwise You will then have SG rule with protocol "all_l4" (all whatever else) and will need to use in docs what that exactly means | 14:12 |
lajoskatona | the client side was in my mind also, not sure if HEAT can do such thing for example | 14:13 |
slaweq | I'm not going to block this rfe, but personally I'm not very enthusiastic about it :) | 14:13 |
mlavalle2 | ah,, so implement this somewhere in OpenStack, although not necessarily thorugh the Neutron API | 14:13 |
haleyb | as a data point it doesn't look like iptables allows this behavior, you have to make individual rules using -p individually | 14:14 |
mtomaska | apparently heat only supports tcp. udp and icmp https://docs.openstack.org/heat/latest/template_guide/openstack.html#OS::Neutron::SecurityGroup | 14:14 |
mlavalle2 | but I think that what was meant is that this might be a RFE for Heat, or the clients | 14:15 |
mlavalle2 | regardless of what they support right now | 14:15 |
lajoskatona | mtomaska: so there's thing to do in heat also | 14:15 |
opendevreview | Slawek Kaplonski proposed openstack/neutron-tempest-plugin master: Update OVS and OVN branches used in the CI jobs https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/843622 | 14:15 |
lajoskatona | ok, so if iptables anyway works this way let's say it is better to do it from the client side | 14:17 |
mtomaska | right, we could propose that HEAT supports other two protocols from the list. That is UDP-Lite dccp and sctp | 14:17 |
amotoki | I personally am not very excited with this proposal. this looks like an area where some automation tool (or client side) can cover (as others already mentioned) | 14:17 |
mtomaska | this way the user has few option to automate. Write your own script :), use HEAT, use Ansible | 14:18 |
mtomaska | or whatever they like to use to automate | 14:18 |
mlavalle2 | or even without automation on the part of the operator, if this were to be implemented in the openstack client | 14:19 |
opendevreview | Edward Hope-Morley proposed openstack/neutron stable/xena: Partially revert "Do not link up HA router gateway in backup node" https://review.opendev.org/c/openstack/neutron/+/843582 | 14:19 |
mlavalle2 | the client might be the right place in the stack to implement this | 14:19 |
slaweq | mtomaska exactly, and plus value of such solution is that when he will do SG rules list, he will see all rules which are really created by backend | 14:19 |
lajoskatona | mlavalle2: you mean openstacksdk? | 14:20 |
mlavalle2 | maybe | 14:20 |
mtomaska | ok so who votes for "automate at the client side" ? | 14:21 |
mtomaska | o/ | 14:21 |
mlavalle2 | I think through this discussion we have higlighted that it is not clear where in the stack is the best place to implement this | 14:21 |
amotoki | potentially OSC can accept a list of protocols as --protocol argument. if so, the next question is how osc should behave if a subset of protocols fails (e.g. as dst-port is not supported) | 14:21 |
lajoskatona | slaweq, mtomaska: that is also good point that the list will be clear, and will display all protocol-port pair | 14:21 |
mlavalle2 | but it seems the Neutron API is unlikely to be that place | 14:22 |
lajoskatona | mtomaska: after this discussion I vote to place it to the client side | 14:23 |
haleyb | amotoki: that's a good question, which is maybe why i don't like this proposal | 14:23 |
amotoki | haleyb: yeah | 14:23 |
opendevreview | Slawek Kaplonski proposed openstack/neutron-lib master: Check proper config option to see if scope is enforced or not https://review.opendev.org/c/openstack/neutron-lib/+/839956 | 14:23 |
haleyb | i am curious about the API impact - on a POST today you get back a single object, is returning many even an option? | 14:24 |
ralonsoh | I think amotoki could be a good alternative, IMO | 14:25 |
ralonsoh | amotoki's idea | 14:25 |
amotoki | haleyb: the neutron API supports bulk creation of resources. I think if we would like to create multiple sg rules, bulk creation would be used. | 14:26 |
mlavalle2 | yeap | 14:26 |
haleyb | amotoki: thanks for reminding me of that | 14:26 |
lajoskatona | but no bulk for security-groups or rules | 14:27 |
ralonsoh | not yet, no | 14:28 |
amotoki | ah, I haven't checked which resources support bulk creation | 14:28 |
mlavalle2 | yes, but it means that the concept of bulk creation in general is compatible with the API | 14:29 |
mlavalle2 | it wouldn't be an aberration | 14:29 |
lajoskatona | malavalle2: +1 | 14:29 |
amotoki | mlavalle2: +1 | 14:29 |
lajoskatona | so generally we agree that it is better to be done on the client side, but perhaps Neutron need bulk support for security-groups and rules, am I right? | 14:32 |
amotoki | lajoskatona: it sounds good | 14:32 |
amotoki | IIRC, another point on bulk creation is osc and sdk have no support for bulk creation right now | 14:32 |
mtomaska | sounds good to me | 14:32 |
lajoskatona | amotoki: thanks | 14:33 |
slaweq | +1 | 14:33 |
ralonsoh | I think so if we want to, for example, fail and remove any SG already created | 14:33 |
mlavalle2 | yes, but I don't think we have a pressing need for SG bulk creation | 14:33 |
mlavalle2 | with that clarification +1 | 14:33 |
lajoskatona | thanks | 14:34 |
lajoskatona | summary the RFE is not accepted | 14:34 |
lajoskatona | ok, if no more comments on this we can move on | 14:35 |
lajoskatona | #topic On Demand Agenda | 14:36 |
lajoskatona | (lajoskatona): meaning of option "router_auto_schedule" is ambiguous (#link https://bugs.launchpad.net/neutron/+bug/1973656 ) | 14:36 |
lajoskatona | if I understand well the original question was to rename router_auto_schedule to something else | 14:39 |
lajoskatona | and an intersting discussion is now under this question, with haleyb and obondarev with their good memories :-) | 14:40 |
ralonsoh | according to the LP comments, I think we should improve the documentation | 14:40 |
ralonsoh | but I'm not sure about the name change | 14:40 |
obondarev | +1 for doc improve | 14:41 |
slaweq | I'm looking now at network_auto_schedule option, which is pretty similar but for the networks to be scheduled to the dhcp agents | 14:41 |
slaweq | and it seems from https://github.com/openstack/neutron/blob/aff0a75ecb76e12f240b4ab00a8ecfc75776216b/neutron/db/agentschedulers_db.py#L481 | 14:41 |
ralonsoh | ^^ exactly | 14:41 |
lajoskatona | good analogy | 14:41 |
slaweq | that it would control if neutron should try to schedule networks automatically to the dhcp agents or not | 14:42 |
slaweq | and that works in case when networks are removed from dead agents | 14:42 |
slaweq | and also e.g. for new networks | 14:42 |
slaweq | at least that's how it looks like for me | 14:42 |
amotoki | router_auto_schedule is also used for initial scheduling just after a router is created, right? | 14:42 |
amotoki | https://github.com/openstack/neutron/blob/aff0a75ecb76e12f240b4ab00a8ecfc75776216b/neutron/api/rpc/handlers/l3_rpc.py#L109 | 14:43 |
mlavalle2 | that's my understanding | 14:43 |
lajoskatona | I agree to improve the documentation | 14:44 |
mlavalle2 | seems like a good next step | 14:44 |
mlavalle2 | we really don't know how this is being used in the wild, but since we don't have many complaints, it is not probably wise to mess with it | 14:45 |
mlavalle2 | so let's improve documentation | 14:45 |
lajoskatona | ok, then I add to the bug as comment that the cfg option name is good, but the doc can be improved | 14:45 |
slaweq | IMO this is valid bug | 14:46 |
slaweq | and we should check if that option is enabled e.g. in https://github.com/openstack/neutron/blob/430abde13ec58e611a8752ca579fee5110a0a61d/neutron/db/l3_agentschedulers_db.py#L484 | 14:46 |
slaweq | so it would probably work the same way like network_auto_schedule option for dhcp agents | 14:46 |
lajoskatona | as I see the first step anyway is to document to have it written how it behaves currently and act if there are complaints for that | 14:48 |
amotoki | the router scheduler class have both auto_schedule_routers() and schedule(). I am not sure schedule() should work only when auto_schedule is enabled | 14:49 |
ralonsoh | +1 | 14:49 |
mlavalle2 | yeah, let's make it clear to everybody in doc how it is intended to bahave | 14:49 |
slaweq | lajoskatona I agree, we should check it to be sure, document how it works and then maybe change this behaviour a bit if that will be needed | 14:49 |
amotoki | anyway agree to imporve the doc | 14:49 |
ralonsoh | and yes, we should check amotoki's question | 14:49 |
lajoskatona | ok, let's go this way then, improve the doc first | 14:51 |
mlavalle2 | +1 | 14:51 |
amotoki | +1 | 14:51 |
ralonsoh | +1 | 14:51 |
slaweq | +1 | 14:51 |
haleyb | +1 | 14:51 |
lajoskatona | +1 | 14:51 |
obondarev | +1 | 14:52 |
lajoskatona | ok, thank you very much | 14:52 |
lajoskatona | Is there anything to discuss? | 14:52 |
slaweq | nothing from me | 14:53 |
amotoki | none from me | 14:53 |
mlavalle2 | not from me | 14:53 |
lajoskatona | #endmeeting | 14:53 |
opendevmeet | Meeting ended Fri May 27 14:53:56 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:53 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-05-27-14.00.html | 14:53 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-05-27-14.00.txt | 14:53 |
opendevmeet | Log: https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-05-27-14.00.log.html | 14:53 |
obondarev | o/ | 14:53 |
ralonsoh | have a nice weekend! | 14:54 |
slaweq | o/ | 14:54 |
lajoskatona | Have a nice weekend, and see you next week :-) | 14:54 |
slaweq | have a nice weekend | 14:54 |
haleyb | o/ | 14:54 |
amotoki | o/ | 14:54 |
opendevreview | Rodolfo Alonso proposed openstack/neutron stable/yoga: Remove session active check in "_add_segment_host_mapping_for_segment" https://review.opendev.org/c/openstack/neutron/+/843624 | 14:54 |
opendevreview | Rodolfo Alonso proposed openstack/neutron stable/xena: Remove session active check in "_add_segment_host_mapping_for_segment" https://review.opendev.org/c/openstack/neutron/+/843626 | 14:58 |
opendevreview | Rodolfo Alonso proposed openstack/neutron stable/wallaby: Remove session active check in "_add_segment_host_mapping_for_segment" https://review.opendev.org/c/openstack/neutron/+/843627 | 14:59 |
opendevreview | Rodolfo Alonso proposed openstack/neutron master: Set "type=virtual" for OVN LSP with parent ports https://review.opendev.org/c/openstack/neutron/+/843474 | 15:02 |
opendevreview | Fernando Royo proposed openstack/ovn-octavia-provider master: Fix way of calculate LB status after HM event https://review.opendev.org/c/openstack/ovn-octavia-provider/+/843308 | 15:12 |
opendevreview | Merged openstack/tap-as-a-service master: Code cleaning: make RPC method signatures more meaningful https://review.opendev.org/c/openstack/tap-as-a-service/+/833432 | 15:42 |
opendevreview | Merged openstack/tap-as-a-service master: py310: Add rpm packages to bindep.txt https://review.opendev.org/c/openstack/tap-as-a-service/+/834880 | 15:47 |
opendevreview | Merged openstack/tap-as-a-service master: test: Make py310 passing https://review.opendev.org/c/openstack/tap-as-a-service/+/834928 | 15:47 |
mnaser | hi neutron team, could we have eyes on https://review.opendev.org/c/openstack/neutron-vpnaas/+/444186 ? | 15:48 |
mnaser | it's a really nice change that will clean things up a lot and .. well overdue lol | 15:48 |
opendevreview | Rodolfo Alonso proposed openstack/neutron master: [sqlalchemy-20] Add missing DB contexts in L3 methods https://review.opendev.org/c/openstack/neutron/+/842468 | 15:53 |
opendevreview | Merged openstack/neutron-fwaas master: Remove "distutils" library https://review.opendev.org/c/openstack/neutron-fwaas/+/842371 | 16:33 |
jamesbenson | Can someone help with a networking question? Why does launching an instance to the external subnet fail but on a private subnet local to the tenant pass, then allocate a public ip work? What setting(s) need to change to make an instance able to launch off of the external network? | 16:46 |
opendevreview | Ghanshyam proposed openstack/neutron-tempest-plugin master: Pin neutron-tempest-plugin for ussuri/victoria jobs https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/838053 | 18:29 |
opendevreview | Merged openstack/neutron master: Remove requirements.txt from irrelevant files in CI jobs https://review.opendev.org/c/openstack/neutron/+/843594 | 18:32 |
opendevreview | Ghanshyam proposed openstack/os-vif master: Drop lower-constraints.txt and its testing https://review.opendev.org/c/openstack/os-vif/+/840020 | 18:54 |
opendevreview | Miguel Lavalle proposed openstack/neutron master: [WIP][DNM][OVN] Change the default firewall policy https://review.opendev.org/c/openstack/neutron/+/839066 | 22:52 |
*** jlibosva is now known as Guest541 | 23:16 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!