Wednesday, 2021-11-24

artomWell crap, https://review.opendev.org/c/openstack/nova/+/817303 passed now00:52
* artom tries to remember to check tomorrow whether it's due to same host resize00:53
fricklerartom: seems you only define the job now and don't actually run it05:27
opendevreviewLee Yarwood proposed openstack/nova-specs master: libvirt: Allow Manila shares to be directly attached to instances  https://review.opendev.org/c/openstack/nova-specs/+/81318006:18
opendevreviewHemanth N proposed openstack/nova master: clear dhcp_server in network_info when dhcp is disabled  https://review.opendev.org/c/openstack/nova/+/81906908:50
DK4im still having problems creating instances in a new deployment. instance is stuck in creating/spawning state, any hints or advices? 10:51
opendevreviewLee Yarwood proposed openstack/nova-specs master: libvirt: Allow Manila shares to be directly attached to instances  https://review.opendev.org/c/openstack/nova-specs/+/81318011:20
lyarwoodDK4:  Use `openstack server event list $instance` to find the request-id associated with the creation request and trace that through the system if you have access11:23
lyarwoodDK4: you can also use openstack server event show $instance $request-id to dump any details about the create request and associated events if you don't have access to the env11:23
lyarwoodDK4: but tbh either way it's likely a messaging issue in your env between the conductor and computes11:24
opendevreviewDr. Jens Harbott proposed openstack/nova master: Add nova-next-hybrid-plug job  https://review.opendev.org/c/openstack/nova/+/81730312:06
DK4lyarwood: thank your for help. im testing on proxmox7 it worked there before. i guess one of the kernel updates on proxmox host itself broke something instead.12:12
DK4lyarwood: the pvekernel 5.13 seems to break my openstack deployments. after switching back to 5.11 it starts to work again. thank you for your input!12:25
artomfrickler, *facepalm* yep, thanks for the fix :(13:04
artomErr, :)13:04
fricklerartom: np, I've left the more interesting part of actually fixing the job for you ;) but I like the idea of testing that scenario, because that's how some of my deployments still look like13:42
ralonsohsean-k-mooney, hi! Can I ask you about https://review.opendev.org/c/openstack/neutron/+/818338/3/neutron/agent/linux/interface.py#369 ?13:49
ralonsohwhen using DPDK, the interfaces connected to a namespace are type=TAP?13:50
ralonsohwell, not the interfaces but the ports13:51
*** whoami-rajat__ is now known as whoami-rajat13:57
sean-k-mooneyyou mean for dhcp agent and l3 agent router instnaces13:57
sean-k-mooneyralonsoh: with ovs-dpdk we do not supprot vnic_type normal13:57
sean-k-mooneyonly  vhost-user offically 13:57
ralonsohsean-k-mooney, yeah but the Interface type=tap??13:58
ralonsohin this patch13:58
sean-k-mooneybut the dhcp server and l3 agent can create port which should get create on ovs as interface_type=internal13:58
ralonsohis that correct?13:58
sean-k-mooneyno13:58
ralonsohok then, I'll comment on the BZ13:58
ralonsohsean-k-mooney thanks a lot13:59
sean-k-mooneyin ovs its interface_type=internal which will create a tap device but there is not ovs interface of type tap13:59
ralonsohright13:59
sean-k-mooneyand we do not use vif_type=tap13:59
sean-k-mooneyralonsoh: do you have the bz link13:59
ralonsohsean-k-mooney, no, this is only U/S13:59
ralonsohhttps://launchpad.net/bugs/195149313:59
sean-k-mooneyob you said BZ so i got confused14:00
ralonsohsorry, my bad14:00
sean-k-mooneyno worries14:00
sean-k-mooneyso ovs is not namespace aware14:01
ralonsohwell, once we create the port, we move it to the namespace14:01
sean-k-mooneyif if ovs-vswitchd is restarted then  i can see this happening14:01
ralonsohbut that could not work with dpdk14:01
sean-k-mooneyit will14:02
ralonsohI mean that interface doesn't exist in the kernel namespace14:02
ralonsohif this port is an OVS DPDK port14:02
sean-k-mooneybut the issue is for some reason when ovs-vswitchd is restart the tap is not remvoed14:02
sean-k-mooneyin this case it wil14:02
sean-k-mooneythe agents are usign interface tyep internal14:03
sean-k-mooneyand that can then be moved14:03
ralonsohyes14:03
sean-k-mooneywhen ovs-dpdk stops it shoudl delete the tap14:03
sean-k-mooneythe l3/dhcp shoudl then pool for it to be recated and move it again once ovs starts again14:03
sean-k-mooneythat or ovs-dpdk need to check alls network namespace and reconenct14:04
ralonsohwell, this "_ovs_add_port" method should check that14:04
ralonsohso we should check for the namespace and use the existing port, right?14:05
ralonsohexisting tap port created inside the namespace14:05
sean-k-mooneyso this https://review.opendev.org/c/openstack/neutron/+/818338/3/neutron/agent/linux/interface.py seams somewhat valid but     attrs.insert(0, ('type', 'tap')) is not 14:05
sean-k-mooneyleft comments on https://review.opendev.org/c/openstack/neutron/+/818338/3/neutron/agent/linux/interface.py14:06
ralonsohthanks!14:07
ralonsohsean-k-mooney, but L419 should be conditional14:07
ralonsohdepending on the datapath type14:07
ralonsohwe can't execute this if netdev14:08
ralonsohbut setting the netns option in the namespace14:08
ralonsoh*in the interface options14:08
sean-k-mooneythis https://review.opendev.org/c/openstack/neutron/+/818338/3/neutron/agent/linux/interface.py#149 ?14:09
sean-k-mooneydeleting the ip address?14:10
sean-k-mooneywhy woudl that fail14:10
sean-k-mooneywehn we are suign prot with type internal even with ovs-dpdk these are kerenle interfaces14:10
sean-k-mooneyso we can treat them like any other kernel interface14:11
sean-k-mooneyoh i miss read that14:11
sean-k-mooneyyou ment https://review.opendev.org/c/openstack/neutron/+/818338/3/neutron/agent/linux/interface.py#41914:11
sean-k-mooneyi think that shoudl also work for ovs-dpdk14:12
ralonsohOK, I'll comment that in the review. Actually this should be present in the namespace14:12
sean-k-mooneyaddint the device to a network namespace shoudl work fine however it likely shoudl haveppn after the network namespaces is set on the ovs db and that shoudl eb done during prot add14:12
sean-k-mooneyif we set the netns namespace option one woudl think so yes14:13
ralonsohperfect, so first execute "_ovs_add_port" adding the netns and then ensuring the TAP port namespace14:13
*** weechat1 is now known as amorin15:01
opendevreviewJulia Kreger proposed openstack/nova master: WIP Ironic - Handle instance/node host on rebalance  https://review.opendev.org/c/openstack/nova/+/81389718:08
opendevreviewDmitrii Shcherbakov proposed openstack/nova master: [yoga] Add PCI VPD Capability Handling  https://review.opendev.org/c/openstack/nova/+/80819920:02
opendevreviewDmitrii Shcherbakov proposed openstack/nova master: [yoga] Support remote-managed SmartNIC DPU ports  https://review.opendev.org/c/openstack/nova/+/81211120:02
sdmitriev1Hello there! Guys, what has to be done to get this one merged https://review.opendev.org/c/openstack/nova/+/710848/ ?20:03
sdmitriev1We're suffering from bug https://bugs.launchpad.net/nova/+bug/1860555 and that patch seems to able to resolve it20:04
dmitriissean-k-mooney: commented on https://review.opendev.org/c/openstack/nova-specs/+/787458/comment/21a5f948_b415eeea/ and added a pre-filter implementation that takes presence of remote_managed device pools into account in patch set 8 https://review.opendev.org/c/openstack/nova/+/812111/820:12
opendevreviewGhanshyam proposed openstack/nova master: Updating tests with Yoga testing runtime  https://review.opendev.org/c/openstack/nova/+/81919422:51

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