Wednesday, 2023-06-21

*** dmellado170420 is now known as dmellado1704205:05
opendevreviewJakub Skunda proposed openstack/nova master: Drop Fedora support  https://review.opendev.org/c/openstack/nova/+/88659610:11
opendevreviewAmit Uniyal proposed openstack/nova-specs master: Adds cleanup to remove dangling volumes  https://review.opendev.org/c/openstack/nova-specs/+/87875711:37
noonedeadpunkhey folks, I've found this wiki page lately, and it looks like this should be supported by nova, as the `migrate_set_capability` is a command that's passed to the qemu monitor https://wiki.qemu.org/Features/Migration-Multiple-fds11:47
noonedeadpunkSo I was wondering, if that's smth that should be supported by nova, or I can set it in some other way as well?11:48
noonedeadpunkAnd also according to https://bugzilla.redhat.com/show_bug.cgi?id=1968540 it seems there's another way around in progress now. But maybe it's worth mentioning in docs as a note about performance hit by using TLS for migrations?12:02
*** d34dh0r5- is now known as d34dh0r5312:12
*** mgoddard- is now known as mgoddard12:28
bauzasnoonedeadpunk: sorry was barely paying attention to the chan13:43
bauzasnoonedeadpunk: so, basically you have concerns about migration performance ?13:46
noonedeadpunkwell, yes, as they can hardly finish with 1.2gbitp/s13:48
noonedeadpunkIt's slightly different on different hardware, but basically it's always single thread now that's handling migration/encryption13:48
noonedeadpunkI've tried to check if gnutls 3.7.3 (default for ubuntu 22.04) helps (as it has this merged) https://gitlab.com/gnutls/gnutls/-/commit/6462916d2f6810409d5da1e13c4a0720f412c16613:50
noonedeadpunkBut seems that it's not enough to have that only in gnutls, apparently qemu should have smth as well13:50
noonedeadpunkBut was also wondering if anybody heard anything about x-multiple-fds in qemu capabilities13:51
bauzasI'm not really a SME of this matter13:54
bauzasmaybe kashyap may help13:54
* kashyap looks13:55
bauzaskashyap: thanks, tl;dr noonedeadpunk has some concerns by the migration TLS performance due to a QEMU single threading13:56
kashyapnoonedeadpunk: Before I say anything further, please note that the "x-" prefix in QMP commands (like "x-multiple-fds") means it's experimental13:56
kashyapThat _said_: the multiple-fd work did come out of experimental, IIRC.  Lemme check13:56
kashyapbauzas: I see; I missed the earlier context; so would be good to know what kind of performance concerns are these13:56
noonedeadpunkso using TLS for libvirt gives migration speed like 1.2gbitps - 3 gbitps depending on CPU, TCP live migrations are 20gbitps13:57
noonedeadpunk(basically full link)13:57
kashyapnoonedeadpunk: Hmm, I mean I'd definitely expect some loss w/ built-in TLS -- as it involves the additional encryption over head -- but I don't have numbers off-hand as to what's "expected"14:01
kashyapnoonedeadpunk: Can you come to #virt (on OFTC) and ask there too?  More libvirt migration experts hang out there14:02
noonedeadpunkso diffference is quite dramatical14:02
noonedeadpunkyes, sure14:02
kashyapYeah; it's almost 10 fold diff14:02
bauzasnoonedeadpunk: ohoh, good to know14:03
noonedeadpunkenabling auto-convergance kinda solves issue, at least migrations do not fail14:07
noonedeadpunkbut being able to utilize more then 1 cpu would be better ofc...14:08
kashyapAh, that's good to know that auto-convergence did its job at least14:08
kashyapI agree on utilization; let's check w/ the libvirt-QEMU guys14:08
bauzasgtk14:09
noonedeadpunkBut I guess if that's performance diff is kinda confirmed, it might be worth mentioning in nova docs at very least14:14
kashyapnoonedeadpunk: I think you're using an older QEMU by judging the "x-" prefix; so first would be good to upgrade to a newer one that removes the "x-" prefix (experimental)14:16
noonedeadpunkI've taken that from qemu wiki page :)14:17
noonedeadpunkI guess I was testing on qemu 8.0.0 or smth14:17
kashyapYeah, the wiki-page tends to not get updated.  I'm pretty sure it's now out of experimental; otherwise libvirt won't enable it (as you saw on #virt)14:17
kashyapAlso, see this response from danpb: https://listman.redhat.com/archives/libvir-list/2020-January/msg00527.html14:17
noonedeadpunkyup14:17
kashyap(Scroll down a bit)14:17
noonedeadpunkYeah, fair14:22
noonedeadpunkSoooo.... Should we say that it make sense to add `parallel` option support to nova?14:45
noonedeadpunkI would try to check what needs to be done for that... Should be pretty much trivial to add14:54
bauzasnoonedeadpunk: sorry again, but what do you mean ? is it due to a new QEMU release ?14:57
noonedeadpunkbauzas: there's a parallel flag that's for sure already present in 8.0.0: https://libvirt.org/manpages/virsh.html#migrate14:58
noonedeadpunklet me check if it's available even before that14:59
noonedeadpunkIt's also available in 6.0.0, and nova min libvirt version is already beyond that15:01
noonedeadpunkbut we also should be careful with amount of parallel connections not to affect running workloads15:02
bauzasnoonedeadpunk: sounds to me a feature request15:04
bauzasbut yeah, turning on this know could be possible 15:04
kashyapYeah, it's a separate request to enable the parallel connections15:23
opendevreviewMerged openstack/nova stable/wallaby: Remove mentions of removed scheduler filters  https://review.opendev.org/c/openstack/nova/+/85805016:32
melwittstephenfin, sean-k-mooney: just fyi I updated https://review.opendev.org/c/openstack/nova/+/877056 to add the bug and release note and return early+unindent code block. and I've also rechecked the tempest test skip for the unrelated CI failures https://review.opendev.org/c/openstack/tempest/+/88649617:33
opendevreviewJakub Skunda proposed openstack/nova master: Drop Fedora support  https://review.opendev.org/c/openstack/nova/+/88659621:59

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