Thursday, 2021-12-16

opendevreviewMerged openstack/neutron stable/wallaby: bw-limit: Pass int parameters to Open vSwitch  https://review.opendev.org/c/openstack/neutron/+/82061200:19
opendevreviewTakashi Kajinami proposed openstack/neutron stable/victoria: bw-limit: Pass int parameters to Open vSwitch  https://review.opendev.org/c/openstack/neutron/+/82189500:28
opendevreviewshanyunfan33 proposed openstack/neutron master: Add wait event for metadataagent sb_idl  https://review.opendev.org/c/openstack/neutron/+/82192702:50
opendevreviewOpenStack Proposal Bot proposed openstack/neutron-vpnaas-dashboard stable/victoria: Imported Translations from Zanata  https://review.opendev.org/c/openstack/neutron-vpnaas-dashboard/+/82193003:46
opendevreviewMerged openstack/neutron-tempest-plugin master: Update irrelevant-files for stadium project's tests  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/82141406:41
opendevreviewyatin proposed openstack/neutron master: List ports when attempt to delete network with ports  https://review.opendev.org/c/openstack/neutron/+/82193506:49
opendevreviewNitish Venkata Patcherla proposed openstack/neutron-lib master: Add api-ref for tap service and tap flow  https://review.opendev.org/c/openstack/neutron-lib/+/82193707:27
ralonsohbcafarel, https://bugs.launchpad.net/neutron/+bug/195501008:20
ralonsohwe have a problem with py2708:20
ralonsoh(something expected, to be hones)08:21
ralonsohhonest*08:21
opendevreviewyatin proposed openstack/neutron-tempest-plugin master: Restructure move to nested virt nodes  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/82193908:21
ralonsohthe library failing is python-lazy-object-proxy. What should we do now? Cap this library version in py27 stable releases?08:21
opendevreviewRodolfo Alonso proposed openstack/neutron master: Adopt rehomed QoS FIP extension from neutron-lib 2.18.0  https://review.opendev.org/c/openstack/neutron/+/82183808:24
bcafarelsigh :(08:29
bcafarelralonsoh: that sounds like the way to go yes08:31
ralonsohI'll push a patch, to check if that works08:33
opendevreviewRodolfo Alonso proposed openstack/neutron stable/train: [stable-only] Cap lazy-object-proxy to 1.7.0 in Python 2.7  https://review.opendev.org/c/openstack/neutron/+/82194408:37
bcafarelok so it is "only" functional and UT with python 2.7? (looking at recent train backports)08:37
bcafarelhopefully this can be capped easily with these jobs :)08:38
ralonsohbcafarel, https://review.opendev.org/c/openstack/neutron/+/82156608:38
ralonsohtools like, yes08:38
ralonsohonly UT and FT in py2708:38
opendevreviewRodolfo Alonso proposed openstack/neutron stable/train: [stable-only] Cap lazy-object-proxy to 1.6.0 in Python 2.7  https://review.opendev.org/c/openstack/neutron/+/82194409:32
opendevreviewMerged openstack/neutron master: Add upgrade check for floating IP QoS inheritance from network  https://review.opendev.org/c/openstack/neutron/+/81839910:08
fricklerralonsoh: this may be intersting to you, because you kind of triggered it: https://bugs.launchpad.net/neutron/+bug/195438410:16
fricklernot sure yet whether to mark the bug as invalid or whether you would at least want to document the change better10:17
ralonsohfrickler, let me check10:17
frickleractually, some change is needed, because this code part will now never be triggered anymore https://opendev.org/openstack/neutron/src/branch/master/neutron/plugins/ml2/extensions/dns_integration.py#L375-L37610:20
ralonsohok, I'll check the code in dns-integration and I'll document the change. But the VLAN range expansion was something needed by the VLAN driver10:23
ralonsohand actually that was the assumption: when no vlan ranges are specified, all are available to this network10:23
fricklerralonsoh: the difference lies in what happens when you run "openstack network create test --provider-network-type vlan". in victoria this fails, because you need to explicitly specify vlan ID and physnet10:30
fricklerwith master, it will choose a random vlan ID and physnet public (in the default devstack setup)10:31
ralonsohthat's what was addressed with this change10:31
ralonsohand now we reserver all VLAN IDs when Neutron server starts10:31
ralonsohthat was the intended behaviour10:32
ralonsohI'll update the config option description10:32
fricklerthe thing is, that with the current code, dns_integration assumes that all these vlans can now be created by tenants and thus disallows dns entries to be created10:33
ralonsohfrickler, that's ok, the admin should restrict the VLAN range in the config10:33
fricklerhmm, maybe it should check tenant_network_types in addition10:34
ralonsohwhere in the code?10:34
ralonsohI'm not following you10:34
fricklerprobably right at the start of _is_vlan_tenant_network()10:35
fricklerlet me propose a patch, that'll make it easier to discuss10:35
fricklermight take a bit though, meetings upcoming10:35
ralonsohfor sure, that will be better to check a patch10:36
opendevreviewRodolfo Alonso proposed openstack/neutron master: Do not announce any DNS resolver if "0.0.0.0" or "::" provided  https://review.opendev.org/c/openstack/neutron/+/82085810:51
opendevreviewyatin proposed openstack/neutron master: List ports when attempt to delete network with ports  https://review.opendev.org/c/openstack/neutron/+/82193511:02
opendevreviewRodolfo Alonso proposed openstack/neutron master: Amend "network_vlan_ranges" configuration option help text  https://review.opendev.org/c/openstack/neutron/+/82195911:09
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Update secure RBAC policies accrodingly to the new guidelines  https://review.opendev.org/c/openstack/neutron/+/82120811:17
opendevreviewMerged openstack/neutron master: When creating a VXLAN interface, a device is mandatory  https://review.opendev.org/c/openstack/neutron/+/82127111:22
opendevreviewyatin proposed openstack/neutron-tempest-plugin master: [DNM] Test switch  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/82196511:31
*** averdaguer is now known as averdaguer|brb11:31
*** averdaguer|brb is now known as averdaguer11:31
opendevreviewRodolfo Alonso proposed openstack/neutron stable/train: [stable-only] Cap lazy-object-proxy to 1.6.0 in Python 2.7  https://review.opendev.org/c/openstack/neutron/+/82194411:34
opendevreviewRodolfo Alonso proposed openstack/neutron stable/xena: Remove the expired reservations in a separate DB transaction  https://review.opendev.org/c/openstack/neutron/+/82196711:39
ralonsohbcafarel, https://a52a7f35e59a2014d9da-da3f945bb6e5ca02e53e7fc9f3f751d2.ssl.cf1.rackcdn.com/821944/3/check/requirements-check/e46574d/job-output.txt11:42
ralonsohERROR: Requirement '{Requirement(package='lazy-object-proxy', location='', specifiers='<=1.6.0', markers="python_version=='2.7'", comment='# BSD', extras=frozenset())}' not in openstack/requirements11:42
ralonsohI don't know if we can modify requirements project for this11:42
ralonsohto add "lazy-object-proxy" to the blacklist11:43
ralonsohor is there a way to define a local backlist in Neutron?11:43
ralonsohI'm going to ask in openstack-dev11:44
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Allocate IPs in bulk requests in separate transactions  https://review.opendev.org/c/openstack/neutron/+/82172711:45
ralonsohslaweq, ^^11:48
ralonsohsame question here, the problem we have in py27 and Train11:48
ralonsohwith a library I want to cap: lazy-object-proxy. But that will fail in requirements-check11:48
ralonsohI'm asking this in openstack-dev, to know the correct procedure11:49
bcafarelralonsoh: I think it is ok to go in requirements for it, like https://review.opendev.org/c/openstack/requirements/+/73300711:50
ralonsohbcafarel, thanks! I was looking for something like this11:50
ralonsohthanks a lot, I'll push a patch for requirements11:50
bcafarelnp, I guess it will also be useful at some point for other projects, we are probably not the only ones using that11:52
ralonsohhttps://review.opendev.org/c/openstack/requirements/+/82197212:02
slaweqralonsoh: sorry, I missed Your ping earlier12:27
slaweqI agree with bcafarel here and I hope it can be accepted in requirements repo12:28
ralonsohthanks!12:29
opendevreviewRodolfo Alonso proposed openstack/neutron master: Do not announce any DNS resolver if "0.0.0.0" or "::" provided  https://review.opendev.org/c/openstack/neutron/+/82085813:20
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Allocate IPs in bulk requests in separate transactions  https://review.opendev.org/c/openstack/neutron/+/82172713:24
opendevreviewRodolfo Alonso proposed openstack/neutron stable/xena: Remove the expired reservations in a separate DB transaction  https://review.opendev.org/c/openstack/neutron/+/82196713:35
opendevreviewBence Romsics proposed openstack/neutron master: Make the dead vlan actually dead  https://review.opendev.org/c/openstack/neutron/+/82089714:03
bcafarel^ zombie vlan :)14:51
holtgreweI have a question regarding policies. I'm running xena. I have a custom policy >>"create_port:fixed_ips:ip_address": "rule:context_is_advsvc or rule:network_owner or role:admin and system_scope:all or role:admin and project_id:%(project_id)s or rule:shared"<<. I have a project "hpc" and provide the RBAC policy action=access_as_shared target project=hpc network=private.15:05
holtgreweWait, wrong channel.15:05
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Remove _safe_plug_new method from the interface driver  https://review.opendev.org/c/openstack/neutron/+/82199816:05
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN][Placement] Make the Placement reporter compatible with OVN  https://review.opendev.org/c/openstack/neutron/+/82185516:49
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN][Placement] Read the initial config in the maintenance worker  https://review.opendev.org/c/openstack/neutron/+/82186516:49
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Add floating IP pools extension to OVN L3  https://review.opendev.org/c/openstack/neutron/+/82181816:54
opendevreviewRodolfo Alonso proposed openstack/neutron master: [WIP] [OVN][Placement] Drive binding by placement allocation  https://review.opendev.org/c/openstack/neutron/+/78647817:10
*** tbachman_ is now known as tbachman17:24
*** tbachman_ is now known as tbachman17:32
opendevreviewMerged openstack/neutron-tempest-plugin master: Add test_create_and_update_port_with_dns_name  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/82107917:35
opendevreviewLuis Tomas Bolivar proposed openstack/neutron master: Use Port_Binding up column to set Neutron port status  https://review.opendev.org/c/openstack/neutron/+/82154417:44
*** tbachman_ is now known as tbachman17:55
opendevreviewMerged openstack/neutron master: Update placement allocation of bound ports when network QoS policy is changed  https://review.opendev.org/c/openstack/neutron/+/81888920:13
rm_workmlavalle: mind taking a glance at https://review.opendev.org/c/openstack/neutron/+/821779 and telling me if you think it's trivial enough to get merged without too much of a debate? 😀20:34
mlavallerm_work: I think it is. I'll look at it carefully latter today20:35
mlavalle:-)20:35
rm_work\o/ thanks20:37
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Remove _safe_plug_new method from the interface driver  https://review.opendev.org/c/openstack/neutron/+/82199820:57
opendevreviewArnau Verdaguer proposed openstack/neutron master: [ovn] Specify port type if it's a router port when updating  https://review.opendev.org/c/openstack/neutron/+/82140121:00
opendevreviewSlawek Kaplonski proposed openstack/neutron master: [Functional] Fix expected number of the enqueue_state_change calls  https://review.opendev.org/c/openstack/neutron/+/82205121:30
opendevreviewMerged openstack/neutron master: Fix stackalytics' link  https://review.opendev.org/c/openstack/neutron/+/82170421:54

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