Tuesday, 2020-04-28

*** igordc has joined #openstack-nova00:02
*** mlavalle has quit IRC00:09
*** ociuhandu has joined #openstack-nova00:10
*** ociuhandu has quit IRC00:20
*** igordc has quit IRC00:34
*** lbragstad has joined #openstack-nova00:37
*** ircuser-1 has joined #openstack-nova00:49
songwenping_Hi, gibi.00:58
songwenping_i have a issue with filter_scheduler with accelerators. pls see the detail at https://etherpad.opendev.org/p/filter_scheduler_issue_with_accelerators01:00
songwenping_the relate fix patch is https://review.opendev.org/#/c/722651/01:01
songwenping_the relate bug reported is https://bugs.launchpad.net/nova/+bug/1874664. pls help me have a look.01:02
openstackLaunchpad bug 1874664 in OpenStack Compute (nova) "Boot more than one instances failed with accelerators in its flavor" [Medium,Confirmed] - Assigned to Wenping Song (wenping1)01:02
*** songwenping__ has joined #openstack-nova01:16
*** songwenping_ has quit IRC01:19
*** Liang__ has joined #openstack-nova01:19
*** songwenping_ has joined #openstack-nova01:21
*** songwenping__ has quit IRC01:24
*** yaawang has quit IRC01:29
*** yaawang has joined #openstack-nova01:29
*** ociuhandu has joined #openstack-nova01:57
*** ociuhandu has quit IRC02:10
*** yaawang has quit IRC02:14
*** yaawang has joined #openstack-nova02:15
*** artom has quit IRC02:26
*** mkrai has joined #openstack-nova02:29
*** yaawang has quit IRC02:32
*** yaawang has joined #openstack-nova02:33
*** brinzhang has quit IRC02:55
*** brinzhang has joined #openstack-nova02:55
*** ociuhandu has joined #openstack-nova02:57
*** jangutter has joined #openstack-nova03:00
*** jangutter_ has quit IRC03:01
*** ociuhandu has quit IRC03:05
*** huaqiang has joined #openstack-nova03:12
*** threestrands has joined #openstack-nova03:12
*** psachin has joined #openstack-nova03:18
*** ociuhandu has joined #openstack-nova03:53
*** ociuhandu has quit IRC04:00
*** brinzhang_ has joined #openstack-nova04:02
*** ratailor has joined #openstack-nova04:13
*** songwenping__ has joined #openstack-nova04:20
*** brinzhang has quit IRC04:23
*** songwenping_ has quit IRC04:23
*** brinzhang has joined #openstack-nova04:24
*** ircuser-1 has quit IRC04:33
*** evrardjp has quit IRC04:35
*** evrardjp has joined #openstack-nova04:35
*** brinzhang_ has quit IRC04:40
*** brinzhang_ has joined #openstack-nova04:41
*** vishalmanchanda has joined #openstack-nova04:57
openstackgerritArthur Dayne proposed openstack/nova-specs master: new a test  https://review.opendev.org/72379405:02
*** songwenping_ has joined #openstack-nova05:21
*** brinzhang_ has quit IRC05:24
*** brinzhang_ has joined #openstack-nova05:24
*** songwenping__ has quit IRC05:24
*** brinzhang_ has quit IRC05:25
*** brinzhang has quit IRC05:26
*** brinzhang_ has joined #openstack-nova05:26
*** brinzhang has joined #openstack-nova05:26
*** ociuhandu has joined #openstack-nova05:37
*** links has joined #openstack-nova05:38
*** ociuhandu has quit IRC05:50
*** ociuhandu has joined #openstack-nova06:00
*** mkrai has quit IRC06:05
*** dpawlik has joined #openstack-nova06:06
*** mkrai has joined #openstack-nova06:06
*** songwenping__ has joined #openstack-nova06:13
*** ociuhandu has quit IRC06:15
*** ociuhandu has joined #openstack-nova06:15
*** songwenping_ has quit IRC06:17
*** damien_r has joined #openstack-nova06:28
*** ociuhandu has quit IRC06:30
*** damien_r has quit IRC06:33
*** udesale has joined #openstack-nova06:37
*** ttsiouts has joined #openstack-nova06:39
*** ociuhandu has joined #openstack-nova06:49
*** ttsiouts has quit IRC06:53
*** slaweq has joined #openstack-nova06:53
*** nightmare_unreal has joined #openstack-nova06:54
*** ttsiouts has joined #openstack-nova06:55
*** maciejjozefczyk has joined #openstack-nova06:56
gibigood morning07:02
gibisongwenping__: ack, I will look at it shortly07:02
songwenping__thanks, gibi.07:03
*** damien_r has joined #openstack-nova07:04
*** ccamacho has joined #openstack-nova07:10
bauzasgood morning Nova07:11
aarentsgood morning07:13
bauzasfwiw, I'm a bit on and off this week due to children vacations at home07:14
bauzasfortunately, it's after RC1 :)07:15
gibibauzas: a quick question. If we have a bug in the cyborg integration code https://bugs.launchpad.net/nova/+bug/1874664 and that code was added in Ussuri then Am I correct that such bug is an RC2 candidate?07:18
openstackLaunchpad bug 1874664 in OpenStack Compute (nova) "Boot more than one instances failed with accelerators in its flavor" [Medium,Confirmed] - Assigned to Wenping Song (wenping1)07:18
* bauzas clicks07:18
bauzasgibi: MHO is that I don't think it's an urgent regression07:19
bauzasgibi: given we weren't supporting Cyborg by Train07:20
gibibauzas: so it is a regression but it targets a small portion of a user base and it definetly does not break upgrade07:20
bauzasgibi: do we have already a fix ?07:20
gibibauzas: there is a patch https://review.opendev.org/#/c/722651/07:20
gibibut I haven't looked it yet how complex it is07:21
bauzasgibi: if not, we could just ask brinzhang to modify the documentation to say that Nova won't support more than one instance for Cyborg in Ussuri07:21
bauzasand then we could backport the fix to a Ussuri later .z07:21
gibibauzas: good point. if the fix is problematic in RC timeframe then we can do a documentation patch07:21
gibibauzas: thanks for the consultation07:22
bauzasgibi: anyway, it's just my opinion07:23
bauzasbrinzhang: are you around ?07:23
AJaegermorning, any nova core available to review two tiny cleanups related to Babel/translations, please? https://review.opendev.org/#/c/723206/2 and https://review.opendev.org/#/c/720725/1 ?07:25
*** ociuhandu has quit IRC07:26
bauzasAJaeger: ack, will look07:26
brinzhangbauzas, gibi: ack07:26
brinzhangbauzas, gibi: I can add that in accelerator support docs, to limit mutil create instances07:27
*** tesseract has joined #openstack-nova07:27
brinzhangsongwenping__ post the etherpad, I think that true, and he has some idea to fix this issue.07:28
brinzhangI agree with bauzas, we can try to fix this issue, than consider to backport to U later ^07:29
AJaegerthanks, bauzas07:29
*** songwenping_ has joined #openstack-nova07:29
brinzhangbauzas: That I just need to add the limit to https://docs.openstack.org/api-guide/compute/accelerator-support.html07:30
*** brinzhang has quit IRC07:30
bauzasbrinzhang: yeah, I just provided a bug comment https://bugs.launchpad.net/nova/+bug/187466407:30
openstackLaunchpad bug 1874664 in OpenStack Compute (nova) "Boot more than one instances failed with accelerators in its flavor" [Medium,Confirmed] - Assigned to Wenping Song (wenping1)07:30
*** brinzhang has joined #openstack-nova07:30
*** songwenping_ has quit IRC07:31
bauzasbrinzhang: fwiw, we did it like this for https://docs.openstack.org/nova/latest/admin/virtual-gpu.html07:31
*** songwenping_ has joined #openstack-nova07:31
bauzaserr, sorry this https://docs.openstack.org/nova/latest/admin/virtual-gpu.html#caveats07:31
*** ociuhandu has joined #openstack-nova07:32
*** songwenping__ has quit IRC07:33
*** rpittau|afk is now known as rpittau07:34
bauzasAJaeger: sent to the gate, thanks for clarifying07:35
AJaegerthanks, bauzas07:36
*** tosky has joined #openstack-nova07:36
AJaegercould somebody import translations, please? https://review.opendev.org/72264407:38
gibiAJaeger: does this transaltion patch needs to be backported to stable/ussuri too?07:39
AJaegergibi: there will be a separte one proposed if available07:41
AJaegergibi: in other words: no07:41
AJaegertranslations are special07:41
AJaegergibi: and release notes are only translated on master07:42
gibiAJaeger: thanks.07:42
AJaegerthanks as well, gibi ;)07:43
gibiAJaeger: does it mean that if we have a reno update merged after this point then we need to trigger a re-translation of the reno somehow?07:43
*** ttsiouts has quit IRC07:44
*** ociuhandu has quit IRC07:45
*** ociuhandu has joined #openstack-nova07:45
gibiAJaeger: I mean we need to add at leat an upgrade warning to the ussuri reno due to a bug discovered after RC107:46
*** jraju__ has joined #openstack-nova07:46
*** links has quit IRC07:47
*** ttsiouts has joined #openstack-nova07:47
*** mkrai has quit IRC07:51
*** ralonsoh has joined #openstack-nova07:52
*** brinzhang_ has quit IRC07:55
AJaegergibi: that happens automatically - after each merge, any new strings are send to the translation server and the translators translate at their leisure07:57
AJaegergibi: and if nobody translates, it shows up in English, so will be there for sure07:58
gibiAJaeger: cool thanks07:58
AJaegergibi: so, no worries, continue adding releasenotes ;)07:58
*** ttsiouts has quit IRC08:03
*** brinzhang_ has joined #openstack-nova08:06
*** songwenping__ has joined #openstack-nova08:06
*** songwenping_ has quit IRC08:09
*** brinzhang has quit IRC08:09
*** martinkennelly has joined #openstack-nova08:19
*** mkrai has joined #openstack-nova08:22
*** ttsiouts has joined #openstack-nova08:28
*** happyhemant has joined #openstack-nova08:30
*** derekh has joined #openstack-nova08:32
openstackgerritOpenStack Proposal Bot proposed openstack/nova stable/ussuri: Imported Translations from Zanata  https://review.opendev.org/72316008:35
*** udesale has quit IRC08:36
*** udesale has joined #openstack-nova08:36
gibielod: ^^08:43
*** priteau has joined #openstack-nova08:53
*** jraju__ has quit IRC08:53
*** jraju__ has joined #openstack-nova08:57
*** xek has joined #openstack-nova08:58
gibizigo, gmann, dansmith, stephenfin: replied in https://bugs.launchpad.net/nova/+bug/1875418 let me know if you disagree or if my proposal is not feasible08:59
openstackLaunchpad bug 1875418 in OpenStack Compute (nova) "Generated policy.json in Ussuri is broken by default" [Undecided,In progress] - Assigned to Ghanshyam Mann (ghanshyammann)08:59
gibior if you have any other proposal as a way forward08:59
zigoreading ...09:01
*** links has joined #openstack-nova09:02
*** jraju__ has quit IRC09:02
zigogibi: I very much agree with all you wrote, thanks you !09:03
zigoThat's exactly what I would like to happen.09:04
-openstackstatus- NOTICE: Zuul is currently failing testing, please refrain from recheck and submitting of new changes until this is solved.09:04
*** ChanServ changes topic to "Zuul is currently failing testing, please refrain from recheck and submitting of new changes until this is solved."09:04
gibizigo: let's see what others think about the feasibility09:04
*** rcernin has quit IRC09:04
gibias I have close to zero knowledge about the generator09:04
*** avolkov has joined #openstack-nova09:07
*** songwenping_ has joined #openstack-nova09:12
*** dtantsur|afk is now known as dtantsur09:14
-openstackstatus- NOTICE: Zuul is currently failing all testing, please refrain from approving, rechecking or submitting of new changes until this is solved.09:14
*** ChanServ changes topic to "Zuul is currently failing all testing, please refrain from approving, rechecking or submitting of new changes until this is solved."09:15
*** songwenping__ has quit IRC09:15
gibibauzas: how the vpgus are avoiding the problem what songwenping_ described for accelerators?09:18
gibisongwenping_: do I understand correctly that your bug appers when you create two instances with one singe POST /servers request?09:21
bauzasgibi: which problem, sorry ?09:21
songwenping_yes, gibi.09:21
bauzasgibi: do I have a bug to lookup ?09:22
gibibauzas: same bug you looked at this morning https://bugs.launchpad.net/nova/+bug/187466409:23
openstackLaunchpad bug 1874664 in OpenStack Compute (nova) "Boot more than one instances failed with accelerators in its flavor" [Medium,Confirmed] - Assigned to Wenping Song (wenping1)09:23
gibisongwenping_: thanks09:23
bauzashah09:23
bauzasgibi: for vGPUs, we only ask for one RC09:24
bauzaseg. resources:VGPU=209:24
bauzasso, when calling Placement, it returns some allocations but all the VGPU ones are in the same RP09:25
gibibauzas: in case of instance multi create you need two separate allocation of one VGPUs09:25
gibibauzas: I mean instance multi create with min=2 max=209:26
bauzasah this09:26
bauzasgibi: actually https://bugs.launchpad.net/nova/+bug/1780225 :-)09:27
openstackLaunchpad bug 1780225 in OpenStack Compute (nova) "Libvirt error when using --max > 1 with vGPU" [High,Confirmed] - Assigned to Sylvain Bauza (sylvain-bauza)09:27
gibibauzas: ohh but that leads to a different error in libvirt instead of placement09:27
bauzasgibi: I should be testing it09:28
bauzaslemme try to use the functional test09:28
lyarwooddoes anyone have an example in api-ref where we list some pre-conditions to calling an API? Looking at the evacuate section I wanted to add a pre-condition around the host being fenced and service being reported as down/forced-down.09:29
lyarwoodah found some for reboot nvm09:30
gibibauzas: can we have two PGPU RPs providing the same vgpu types under the same compute RP? If yes then I think the instance multicreate can fail due to running out of VGPU resource on the PGPU in the first allocation candidate09:32
gibiand that would be similar to what songwenping_ reported for accelerators09:32
bauzasgibi: yes of course09:32
bauzasgibi: what do you want me to test ?09:33
bauzas2 RPs with the same vgpu type, each them having, say, 8 vGPUs09:34
bauzasthen asking for 2 instances for 2 vGPUs09:34
bauzasgibi: works with you ?09:34
gibibauzas: give me a sec09:34
bauzasgibi: fwiw I'm just trying to reproduce https://bugs.launchpad.net/nova/+bug/1780225 with the functional tests09:35
openstackLaunchpad bug 1780225 in OpenStack Compute (nova) "Libvirt error when using --max > 1 with vGPU" [High,Confirmed] - Assigned to Sylvain Bauza (sylvain-bauza)09:35
*** sapd1_x has quit IRC09:35
gibibauzas: you could try that case when ask for 2 instance with 2 vGPUs each, then the compute has two PGPUs 2 VGPU each09:37
aarentslyarwood: just FYI http://paste.openstack.org/show/792735/09:38
gibiI now assume that the multi create will try to allocate the resources in placement for the second intance from the same PGPU as for the first instance due to https://github.com/openstack/nova/blob/master/nova/scheduler/filter_scheduler.py#L23809:39
gibibauzas: as we are never considering the second allocation candidate from the a host09:39
gibis/considering/consider/09:39
bauzasgibi: okay, lemme try to do it09:39
gibiOK09:39
gibibauzas: in general I agree that the songwenping_'s bug is not an RC2 candidate. Let's just document it09:40
bauzasgibi: /me just looks how to simulate multi create with functests09:40
gibibauzas: test_create_multiple_servers09:41
gibibauzas: https://github.com/openstack/nova/blob/be9afebd6a6c400d2c7f7a13dfe25c8c641c1baa/nova/tests/functional/test_servers.py#L58909:41
bauzasthanks, I know we had it09:41
bauzasbut I was trying to find the test :)09:41
bauzastest_servers <309:42
openstackgerritLee Yarwood proposed openstack/nova master: docs: Add evacuation pre-conditions around the src host  https://review.opendev.org/72385309:42
lyarwoodaarents: ack thanks09:42
lyarwoodaarents: so it's always adding that additional block09:43
lyarwoodaarents: ah sorry you snipped the output09:45
lyarwoodaarents: so sometimes it did?09:45
aarentslyarwood: not always.. that's odd, in the paste only 7% of times and it depend of size you fallocate09:45
aarentslyarwood: yep09:45
lyarwoodaarents: right my bad09:45
lyarwoodaarents: yeah that's weird09:45
gibibrinzhang, songwenping_ : so I assume that some of you will propose patach that documents the limitation about multi create with accelerators09:47
bauzasgrrrr, /me raises hand at tox.ini when you change dependencies and then you only have DSL 7Mbps bandwidth09:47
gibibrinzhang_, songwenping_: let me know if you need help09:47
*** sapd1_x has joined #openstack-nova09:51
*** tkajinam has quit IRC09:54
*** ttsiouts has quit IRC09:55
bauzasgibi: interesting, when trying to multi create 2 instances asking for 1 vGPU each, I get no exceptions but it tells me 4 vGPUs instead of 209:56
*** brinzhang has joined #openstack-nova09:56
bauzas(one compute, 2 pGPUs with a capacity of 8 each)09:57
brinzhanggibi: later, we will propose a patch, to note the multi create in https://docs.openstack.org/api-guide/compute/accelerator-support.html09:57
*** ttsiouts has joined #openstack-nova09:58
bauzasgibi: ahah, no, that's just my test which is wrong, we create 2 mdevs :p09:58
*** brinzhang_ has quit IRC10:00
bauzasgibi: so, I can't reproduce https://bugs.launchpad.net/nova/+bug/1780225 with my functional test10:00
openstackLaunchpad bug 1780225 in OpenStack Compute (nova) "Libvirt error when using --max > 1 with vGPU" [High,Confirmed] - Assigned to Sylvain Bauza (sylvain-bauza)10:00
bauzasgiven it was for Rocky, I think it was fixed by the fact that in Stein we have a RP per pGPU10:05
*** Liang__ has quit IRC10:10
*** rpittau is now known as rpittau|bbl10:10
gibibrinzhang: ack, thanks a lot10:13
brinzhanggibi: np10:14
gibibauzas: do you try that with the libvirt driver or with the fake driver? I think the placement issue can be recreated with the fake driver10:15
bauzasgibi: i use the fakelibvirt driver10:15
bauzasnot the fake driver itself10:15
gibiI see10:15
gibianyhow it is not burning hot issue right now and songwenping_ PoC seems to be a step in the good direction10:16
gibias soon as we have a func recreate for the accelerator case we can adapt that for the VGPU case as well (with the fake driver)10:17
openstackgerritSylvain Bauza proposed openstack/nova master: WIP: Test multi create with vGPUs  https://review.opendev.org/72385810:24
bauzasgibi: ^10:24
gibibauzas: ack, I will look10:24
bauzasgibi: I'll provide a new revision for it with testing what happens when you ask for 2 vGPUs in multicreate but each pGPU can only create one10:24
kashyaplyarwood: Hi, I'm just digging into the Q35 failure with 'virt-preview': seems like the logs are already gone10:25
gibibauzas: OK10:25
bauzasgibi: tbc, placement doesn't support sharding resources over RPs but here this is not the issue10:26
kashyaplyarwood: I take it that you haven't had a chance to look at them  I just did a 'recheck' for it to reun10:26
kashyaps/reun/rerun/10:26
gibibauzas: yeah, if we have two instance requesting one VGPU each then we never allocate two VGPUs in the same placement request so no sharding is needed from placement10:27
*** jaosorior has joined #openstack-nova10:30
*** dasp has quit IRC10:32
lyarwoodkashyap: I haven't sorry10:34
bauzasgibi: interesting, we don't have the problem for multi-create with vGPUs filling up capacity10:35
*** dasp has joined #openstack-nova10:35
* bauzas just uploads the new revision10:35
openstackgerritSylvain Bauza proposed openstack/nova master: Test multi create with vGPUs  https://review.opendev.org/72385810:39
bauzasgibi: see above, I created two instances with 8 vGPUs each10:39
kashyapyarwood: No problem; I'll dig in10:39
bauzasoh snap10:42
* bauzas facepalms10:43
bauzas(I just ran the older test and now the new one)10:43
bauzasah, reproduced10:45
*** brinzhang_ has joined #openstack-nova10:48
openstackgerritSylvain Bauza proposed openstack/nova master: Test multi create with vGPUs  https://review.opendev.org/72385811:04
bauzasbrinzhang: songwenping_: gibi: confirmed the issue for vGPUs11:05
bauzassee the above patch https://review.opendev.org/72385811:05
bauzasso the problem is not related to cyborg but rather for all nested resource providers11:05
bauzasanyway, not a RC regression  given we had the same issue in Train for vGPUs (and possibly bandwidth-aware instances,wdyt gibi ?)11:06
* bauzas goes lunching11:06
*** brtknr has quit IRC11:07
*** ociuhandu has quit IRC11:11
*** brtknr has joined #openstack-nova11:15
gibibauzas: thanks for the reporoduction11:16
*** ociuhandu has joined #openstack-nova11:19
*** brtknr has quit IRC11:23
*** tosky has quit IRC11:23
brinzhang_gibi: my partner proposed a bug, see https://bugs.launchpad.net/nova/+bug/187562411:25
openstackLaunchpad bug 1875624 in OpenStack Compute (nova) "the vms can not be force deleted when vm_status is soft-delete and task-state=deleting" [Undecided,New] - Assigned to xuyuanhao (thourch)11:25
brinzhang_gibi: can you check11:25
gibibrinzhang_: will check soon11:25
brinzhang_gibi: thanks11:25
*** iurygregory has quit IRC11:26
*** iurygregory has joined #openstack-nova11:26
*** brtknr has joined #openstack-nova11:28
*** tkajinam has joined #openstack-nova11:34
gibibrinzhang_: confirmed the bug.11:40
*** ociuhandu has quit IRC11:42
*** ociuhandu has joined #openstack-nova11:44
*** ttsiouts has quit IRC11:45
*** mgariepy has joined #openstack-nova11:54
*** tosky has joined #openstack-nova11:54
*** ociuhandu has quit IRC11:55
*** ociuhandu has joined #openstack-nova11:57
*** nweinber has joined #openstack-nova11:58
*** belmoreira has joined #openstack-nova11:58
*** dklyle has quit IRC12:00
*** mgariepy has quit IRC12:02
*** raildo has joined #openstack-nova12:03
*** rpittau|bbl is now known as rpittau12:08
*** ociuhandu has quit IRC12:11
*** derekh has quit IRC12:13
*** mgariepy has joined #openstack-nova12:16
*** songwenping__ has joined #openstack-nova12:17
*** happyhemant has quit IRC12:20
*** songwenping_ has quit IRC12:20
*** ociuhandu has joined #openstack-nova12:21
*** ChanServ changes topic to "Current runways: https://etherpad.openstack.org/p/nova-runways-ussuri -- This channel is for Nova development. For support of Nova deployments, please use #openstack."12:27
-openstackstatus- NOTICE: Zuul has been restarted, all events are lost, recheck or re-approve any changes submitted since 9:50 UTC.12:27
bauzasgibi: brinzhang: FWIW, I think we should change the title of bug 1874664 to make it clear it's for all nested Resource Providers12:30
openstackbug 1874664 in OpenStack Compute (nova) "Boot more than one instances failed with accelerators in its flavor" [Medium,Confirmed] https://launchpad.net/bugs/1874664 - Assigned to Wenping Song (wenping1)12:30
openstackgerritBrin Zhang proposed openstack/nova master: Add nested resource providers limit for multi create  https://review.opendev.org/72388412:30
gibibauzas: I agree12:31
*** artom has joined #openstack-nova12:32
bauzaschanged https://bugs.launchpad.net/nova/+bug/187466412:32
openstackLaunchpad bug 1874664 in OpenStack Compute (nova) "Instance multi-create doesn't support available resources spread between children RPs" [Medium,Confirmed] - Assigned to Wenping Song (wenping1)12:32
bauzasgibi: have you tested it for bandwidth-aware instances ?12:33
bauzasactually, that's traits, right?12:33
gibibauzas: multi create with neutron ports are not supported even without bandwidth12:34
gibimulti create with neutron net is supported without bandwidth12:34
bauzasack ok12:35
bauzasfwiw, multi-create works with vGPUs if one RP has all the capacity for all the instances12:35
brinzhang_bauzas, gibi: I am now confused (dazzled) ^^12:35
bauzasand I guess it's the same for cyborg resources12:36
*** dpawlik has quit IRC12:36
gibibrinzhang_, bauzas: I have to jump on a call, sorry. I will read back later12:36
*** songwenping__ has quit IRC12:36
brinzhang_bauzas: you mean change "Add" to "All"?12:36
brinzhang_bauzas: if possiable, you can edit that patch, or you can leave comments inline, I have to go home now, it's too later for me, I am sorry12:38
brinzhang_gibi, bauzas: thanks ^^12:38
*** dpawlik has joined #openstack-nova12:40
bauzasbrinzhang: see the bug description modification https://bugs.launchpad.net/nova/+bug/187466412:40
openstackLaunchpad bug 1874664 in OpenStack Compute (nova) "Instance multi-create doesn't support available resources spread between children RPs" [Medium,Confirmed] - Assigned to Wenping Song (wenping1)12:40
brinzhang_bauzas: I think that use you write in bug description in my patch12:47
brinzhang_it looks better12:47
brinzhang_an easy to understand12:47
*** jsuchome has joined #openstack-nova12:47
brinzhang_s/an/and12:47
*** alistarle has joined #openstack-nova12:48
*** ratailor has quit IRC12:48
AJaegerThe nova ussuri translations are at https://review.opendev.org/723160, any stable nova core to import them, please?13:01
*** dklyle has joined #openstack-nova13:02
nightmare_unrealcan someone review this : https://review.opendev.org/#/c/715395/ Thanks13:02
*** alistarle has quit IRC13:05
*** vesper11 has quit IRC13:06
*** vesper has joined #openstack-nova13:06
*** mkrai has quit IRC13:11
elodAJaeger: about https://review.opendev.org/723160 : if I understand correctly it is safe to merge now and don't really need any extra review. Am I right?13:18
*** derekh has joined #openstack-nova13:18
AJaegerelod: it's safe to merge now and most projects have single core review.13:20
AJaegerelod: let me grab you a link for the safe...13:20
AJaegerelod: http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014437.html has "For projects with translations, watch for any translation patches coming through and merge them quickly"13:21
elodAJaeger: thanks! reading13:21
elodohh, the release countdown mail, i see, thanks13:23
AJaegeryep, that one13:23
elodAJaeger: approved13:24
*** eharney has quit IRC13:25
artomstephenfin, any chance I could get you to revisit https://review.opendev.org/#/c/687404/20 ?13:30
*** ttsiouts has joined #openstack-nova13:32
*** eharney has joined #openstack-nova13:34
AJaegerthanks, elod13:41
openstackgerritMarcin Juszkiewicz proposed openstack/nova stable/train: Add default cpu model for AArch64  https://review.opendev.org/72390013:43
*** psachin has quit IRC13:46
elodwell, thanks for calling my attention to that patch. I've already had a look at it, but saw that zuul was in bad shape so waited for zuul to get back to normal13:48
stephenfinartom: sure13:53
*** ttsiouts has quit IRC13:56
*** hamzy has joined #openstack-nova14:00
* gibi jumps from one call to another14:02
* kashyap waits for gibi to report "video fatique" :D14:04
kashyaps/fatique/fatigue/14:04
*** mriedem has joined #openstack-nova14:12
*** ttsiouts has joined #openstack-nova14:12
* gibi has covid fatigue14:16
artomstephenfin, thanks :)14:17
gmanngibi: thanks, i added comment. i think changing 'oslopolicy-sample-generator' depends how we change it, say adding deprecated rules by default or based on request. because there might be operator who are using this tool for no-deprecated-rules usage14:21
*** ttsiouts has quit IRC14:22
gmannwhich was the only way to move to new defaults and stop old token to pass via deprecated rule until we introduced new flag in oslo.policy 'oslo_policy.enforce_new_defaults'14:22
stephenfindansmith: Now that we've branched, could you take a look at https://review.opendev.org/#/c/537414/ and https://review.opendev.org/#/c/530905/ again?14:22
gmannmay be bnemec and stephenfin can input how we can accommodate both use case of 'oslopolicy-sample-generator' here.14:23
gmanni mean adding deprecated based on request can be done but if it solve the zigo case.14:23
dansmithstephenfin: ack14:23
stephenfindansmith: ta14:23
dansmithgmann: I thought it was said that the generator wasn't going to get that new mode14:23
dansmithor at least, not in time14:24
gmanndansmith: yeah that was my understanding but gibi opinion is to do that if we can.14:25
bnemecI'm not a big fan of adding a feature to support an anti-pattern in deploying OpenStack.14:25
stephenfinCould we just handwrite a policy.json file and include it in our sdist for this release?14:26
dansmithgmann: the problem I see is that the oslo tool will not do that by default, but our default in nova is to need the deprecated rules,14:26
stephenfinzigo could consume that instead of using the oslopolicy tool14:26
gmannwe have to carefully things of way for operator to move to new defaults was only overwrite the rule in policy file which is this case we taken as broken14:26
dansmithso we're requiring a lot of people to know to disable one default and override another, to get a consistent set of defaults that will work14:26
artomstephenfin, thanks :)14:27
gmannexactly14:27
artomdansmith, https://review.opendev.org/#/c/672595/73 pretty please? When your queue gets to it14:27
*** udesale_ has joined #openstack-nova14:27
dansmithstephenfin: I think that's more obscure for people that aren't already looking for a sample file, but maybe easier to get themselves out of the hole once they realize they've deployed and screwed themselves up14:27
* artom wonders if the NUMA LM func tests can beat the device tagging tempest tests record14:27
dansmithartom: ack14:28
*** udesale has quit IRC14:29
gmanngibi: I will update the patch for reno comments and will keep bug open. and we can discuss the best possible approach about policy file usage in cross project sessions in PTG what bnemec added in oslo etherpad and i linked in nova ptg ethrepad too.14:31
gmanngibi: zigo that works for you ^^ ?14:32
*** rpittau is now known as rpittau|brb14:32
*** links has quit IRC14:34
dansmithstephenfin: oh right, yeah I'm not going to approve those completely inconsistent style things in the middle of a file, but I'm sure someone else will14:35
stephenfinhuh?14:36
dansmiththe "black says this ugly style is cool, so I'll just break from the rest of nova conventions here for the new code I'm adding" thing in your tests14:37
stephenfinum, those are entirely new tests?14:37
dansmithin a file with a style, in a project with a style14:37
stephenfinreally?14:38
dansmithyou're not even consistent within those tests14:38
stephenfinwe're inconsistent all over the place14:39
stephenfinyou're not going to hammer me for style, surely?14:39
*** bauzas has quit IRC14:43
artomstephenfin, dansmith, hey, I may be late to the party, but those .contains("nova_object.name") searches...14:43
*** bauzas has joined #openstack-nova14:43
artomThis kind of substring search is notoriously slow in SQL, no?14:43
artomFor the compute nodes, it's probably fine, since there aren't that many of them, but for instances...14:43
dansmithartom: they're not indexed, so yes14:43
artomSo we're just accepting that?14:45
artomI dunno if that's been talked about before, as I said, I'm late to the party14:45
stephenfinI don't think we've a choice. There's no other heuristic we can use to differentiate the legacy entries from the non-legacy ones14:46
dansmithI guess if we did it in python, despite being slower, it's load on the machine running the nova-manage, instead of the DB server itself, which is probably better14:46
*** bauzas has quit IRC14:47
dansmithalthough maybe we'd have no filter at that point and basically return all the instances14:47
dansmithso yeah I dunno14:47
*** mlavalle has joined #openstack-nova14:47
*** bauzas has joined #openstack-nova14:48
openstackgerritGhanshyam Mann proposed openstack/nova master: Clarify the policy new defaults upgrade notes  https://review.opendev.org/72364514:49
gmanndansmith: gibi zigo updated , please check - https://review.opendev.org/#/c/723645/14:49
artomdansmith, stephenfin, I guess there's no way to do "pagination" when selecting instance_extra?14:50
dansmithartom: what would that help?14:50
artomdansmith, select all instance_extra in steps of 100 or whatever, do the filtering in Python, find the instance UUIDs that way, then with those go back to the database?14:51
artomApparently you can do stuff with LIMIT: https://stackoverflow.com/questions/3799193/mysql-data-best-way-to-implement-paging14:52
dansmithartom: but we'd still end up selecting every instance out of the database every time right?14:53
dansmithevery instance, in groups of 10014:53
artomYeah, but at least it's spread out over time?14:53
artomYou're not filtering on all X thousands instances in a single query14:53
dansmithartom: well, the migrations are supposed to be idempotent, so ideally you can run this over and over and have less and less impact14:53
gmannmelwitt: all setup for devstack and grenade now. we can approve this - https://review.opendev.org/#/c/704364/514:54
gmannand then backport14:54
dansmithartom: I think I'd rather the string filter in the query than just continually select every instance out of the database on every run, only to find that none are needed14:54
gmann*done now14:54
dansmithartom: I'd have to iterate every instance in the DB every time you asked me "are you done?"14:54
artomdansmith, but isn't that what the string filter in the query is doing anyways, behind the scenes?14:55
artomLooking at every instance in the database?14:55
dansmithartom: no, it's looking at every value in a table14:55
dansmithwhich is massively less expensive than selecting multiple tables, feeding those to python, constructing tons and tons of objects, for us to go through and do...that same string comparison14:56
artomdansmith, right sorry - but what's what I was suggesting we do in python - select instance_uuid, numa_topology from instance_extra <in steps of 100>, fitler in python, use those instance_uuids for the actual update14:56
*** rpittau|brb is now known as rpittau14:57
artomBut maybe ^^^ is impossible with our models/sqlalchemy?14:57
dansmithyou mean a direct query and not an ORM one? that's better, but you're still sending the results of all those queries across the network every time14:57
dansmithno, we can do it without an ORM query, we do that in places14:57
*** ociuhandu has quit IRC14:57
artomdansmith, yeah :/14:58
artomI guess we'd need metrics of how long the string filter would take, as a function of # of instances14:59
artomTo see if we're making a mountain our of a molehill14:59
dansmithit'll definitely be faster for the db server to do it, the only benefit I can see is you offload the cpu processing to another machine, but you pay the penalty of increasing latency and definitely network traffic14:59
dansmithbesides, stephenfin will want to nuke this migration in a cycle or two anyway, so it won't be run forever15:00
*** ociuhandu has joined #openstack-nova15:00
gibiaway15:01
* gibi is reading back15:01
artomdansmith, I suppose asking CERN to test this for us is not an option ;)15:02
dansmithartom: sure you can ask them for their opinion on the pain15:03
dansmithI dunno what the alternative is though15:03
artomYeah, valid point15:03
dansmithespecially in cern's case, the impact of sending their massive amount of data over the network is not likely better15:03
dansmithand, they have upgrade windows where they can handle this kind of thing15:03
dansmithartom: well, one alternative is to avoid doing this, which is valid15:04
dansmithartom: this is cleanup that we don't need to do, other than to address stephenfin's OCD15:04
artomI tend to like stephenfin OCD ;)15:04
dansmithwhich while this seems like a good one to do, because it's data at rest, it's not *really* costing us much to maintain the compatibility15:04
artomdansmith, I don't suppose doing it on the fly is an option?15:05
*** ociuhandu has quit IRC15:05
dansmithartom: we're already doing it on the fly, that's my point15:05
artomLike, every time we call those legacy dict methods, update the DB?15:05
*** ociuhandu has joined #openstack-nova15:05
artomSeriously?15:05
artomYeeeaaahhh15:05
artomI have to say, that sways me the other way around15:05
dansmithwe're doing it on read, and if we save it for some reason (like a migration) then we update it15:05
dansmithwe could do update-on-read too, which we've done in other places15:06
artomUpdate on read would be nice15:06
dansmithI'd be cool with that15:06
dansmithdespite this looking nicer, it really isn't *necessary* to update this.. these compat routines have been here for ages15:06
artomI'd be less worried if the hit to the DB was less15:07
artomIf jaypipes was still around he could set us straight15:07
artomMaybe I'm paranoid for nothing15:07
dansmithyeah, I think it's a good insight.. I honestly hadn't really considered it, but I think you've got a good point15:07
dansmithif it was something we really had to do, then I'd be for this approach, let the DB server do the hard bit, but...15:08
dansmiththe other thing about this, is for instances created since like 2018, this is just pain for no reason15:08
dansmithor whenever we moved to the new format15:08
dansmiththis is really just looking for super ancient instances that have been nursed for a long time,15:08
dansmithwhich definitely puts it into perspective for me15:09
stephenfin201415:09
dansmithhah15:09
artomstephenfin, your call I guess - looks like update on read might be a more acceptable solution, though with it we'd never be 100% sure we got all of those ancient instances15:12
stephenfinAnd this isn't OCD. I've to maintain the hardware.py module and uglier corners of libvirt driver code, and I'm continuously trying to burn down tech debt inflicted upon me by others to make that job easier15:12
*** udesale_ has quit IRC15:13
openstackgerritMerged openstack/nova master: Imported Translations from Zanata  https://review.opendev.org/72264415:13
stephenfinartom: personally, I was for deleting all the compat code to handle instances that hadn't been _touched_ since 2014, but dansmith said that wasn't good enough so I did this15:14
stephenfinand have been working on it for two years15:14
artomstephenfin, sorry dude, didn't mean to sabotage it :(15:14
artomBut it would have been dishonest to silence my concern15:14
artombelmoreira, around? We're having a DB performance discussion, and figured CERN's scale might shed some light15:15
*** tkajinam has quit IRC15:17
belmoreiraartom I just need to leave now. If you can I will be around tomorrow15:17
artombelmoreira, ok, I'll ping you again earlier tomorrow morning (I'm on EDT)15:17
artomI'm trying to read up on LIKE performance, which I *assume* is what sqlalchemy boils down .contains() to...15:20
dansmithlike is a little more expensive than a strstr() I think, although it might collapse to that if mysql notices there are no pattern characters15:21
*** gyee has joined #openstack-nova15:21
*** mgariepy has quit IRC15:24
gibidansmith, gmann, stephenfin, zigo: OK so I see that the change in the policy generator is not feasible before ussuri GA and might also seemed as a step backward to have that change in V. Then are we suggesting to zigo that his use case is not really valid / supported in Ussuri and in Victoria?15:25
gibior what is the way forward top of the reno update?15:25
*** mgariepy has joined #openstack-nova15:26
dansmithgibi: no, I think zigo's case is very valid, and common15:26
dansmithgibi: I think we've screwed up here, and I think all I've said is that I don't think we have a lot of good options15:26
gmannbut should we consider the "new policy file generated without deprecated rules to switch to new defaults" are not valid ?15:27
gmannbecause in both cases, policy file can be used that way15:28
gibidansmith: thanks. I feel that we have no good options15:28
dansmithindeed :/15:28
gibigmann: do you mean that use the new generated file and configure nova and keystone with scopes?15:29
gibigmann: I think that is a valid use case15:29
dansmithwe can't do that in the upgrade I think15:29
dansmithbecause people with non-scoped current policy files will break15:29
gmannyes. and in past also if we deprecate any policy rule and operator want to move to new defalt, policy overwrite is the option they had15:30
gibidansmith: true, not for the upgrade, but for the new deployments15:30
dansmithgibi: only distros have the ability to do something different for upgrade vs. new I think15:30
dansmithgibi: we the nova project have to assume upgrade15:30
gmannyeah15:30
dansmithI think what we can do is set up for the most default case, which is where we are now, and accept that the case where you're using the generation tool is going to break15:30
dansmithit's likely common, but less common than all the other cases I think15:31
dansmithaccept, and document/warn about the potential problem I mean15:32
openstackgerritMerged openstack/nova stable/ussuri: Imported Translations from Zanata  https://review.opendev.org/72316015:32
gibiOK, I see. thanks. I will summarize it in the bug15:32
gmanndansmith: i agree it might be common to re-generate policy file and end up no deprecated rule but is not that wrong usage ? and some point we have to tell them its not right one15:32
dansmithgmann: no, I don't think it's wrong.. it's not what we want people to do, but what we want them to do isn't very convenient or user-friendly, which is why I think it's likely common15:33
*** mgariepy has quit IRC15:33
dansmithgibi: also the other action item is to switch to yaml policy by default going forward I think, and encourage people to move to that15:33
gmannand it is like it was not reported before when few policy default were changed. i am not sure if new default were superset of old so that same problem would occur15:33
gmanndansmith: +1 on switch  yaml.15:34
gmannand this bug - https://bugs.launchpad.net/oslo.policy/+bug/185317015:34
openstackLaunchpad bug 1853170 in oslo.policy "Need documentation on recommended operator workflow for deprecated policies" [High,Triaged]15:34
gibidansmith: good point about yaml, adding that to the PTG etherpad15:34
dansmithgmann: this we can all agree on :P15:34
gmannwe need some consistent  usage guide also15:34
gmanngibi: its there, in cross project section15:35
gibigmann: even the yaml usage?15:35
*** AJaeger has left #openstack-nova15:35
gmanngibi: ah i thought it is written in description but i missed. please add15:36
gibidone :)15:36
gmannthanks15:36
gmanndansmith: gibi new flag aded in ussuri (https://bugs.launchpad.net/nova/+bug/1875418) to switch to new default instead of overwriting the policy file can improve the usage at some extend.15:38
openstackLaunchpad bug 1875418 in OpenStack Compute (nova) "Generated policy.json in Ussuri is broken by default" [High,In progress] - Assigned to Ghanshyam Mann (ghanshyammann)15:38
gmannsorry, this flag - 'oslo_policy.enforce_new_defaults'15:38
dansmithgmann: this is separate from the full switch to only scoped policies right15:39
dansmith?15:39
gmanndansmith: yes.15:39
dansmithso, I think maybe we should just go ahead and shut the door in V on using the old stuff15:39
dansmithbecause this is now a failure on the upgrade "policy" we should just hard pivot over to the new stuff in V,15:40
dansmithapologize for the short notice, and move on15:40
dansmithand maybe our U renos need to state that.. "might as well go ahead and convert in U to avoid this again in V"15:40
*** belmoreira has quit IRC15:40
bauzasgibi: others: procedural question but https://bugs.launchpad.net/nova/+bug/1875418 should have a ussuri-rc-candidate tag or not ?15:41
openstackLaunchpad bug 1875418 in OpenStack Compute (nova) "Generated policy.json in Ussuri is broken by default" [High,In progress] - Assigned to Ghanshyam Mann (ghanshyammann)15:41
gmanndansmith: yeah mentioning V upgrade in reno is good idea. but removing old stuff in V might be difficult now as we have conveyed the old support till W in few wanrings and original reno15:42
gibibauzas: as far as I see we will keep the bug open after Ussuri so it should not be tagged15:42
dansmithgmann: we still have time to correct those warnings though right?15:42
gmanndansmith: humm, we can do and bakport. but i am thinking if that is too early for people not re-generating the file. i mean they need to adopt new scope token which is very new things.15:43
gibiI've updated the policy bug with the current agreement above. I have to leave for today, will read back tomorrow15:43
bauzashonestly, this bug scares me15:43
bauzascouldn't we just tell that we won't support new policies until V ?15:44
dansmithgmann: well, it just feels like extending this any longer than necessary is worse than concentrating al the pain15:44
dansmithbauzas: we've already broken a set of users though,15:44
bauzaschances are that operators wouldn't read relnotes15:44
bauzasdansmith: :(15:44
dansmithso I was going to say instead of breaking 25% of them now, and then 75% of them later, we should just get it over with15:45
bauzaslike, "take a pill, and suffer in silence" ? :)15:45
dansmithor "rip off the bandage"15:45
bauzasI guess we can't obviously make it a pre-upgrade check15:46
gmannor we add the oslo guide on best handle the deprecated rule in file - https://bugs.launchpad.net/oslo.policy/+bug/185317015:46
openstackLaunchpad bug 1853170 in oslo.policy "Need documentation on recommended operator workflow for deprecated policies" [High,Triaged]15:46
bauzasthis would require us to write some Train patch and a release15:46
*** mgariepy has joined #openstack-nova15:46
bauzasbut this would be nice, they'd get the warnings before upgrading to U15:47
dansmithbauzas: we could definitely do some nova-status guessing, yeah15:47
dansmithbauzas: not a train patch, a U patch.. nova-status from U helps warn about things from T->U15:48
bauzasdansmith: but this would be a pre-Victoria check, right ? (unless we backport to Train the patch itself)15:48
openstackgerritMerged openstack/nova master: Switch to TOX_CONSTRAINTS_FILE  https://review.opendev.org/72281415:48
openstackgerritMerged openstack/nova master: Test multi create with vGPUs  https://review.opendev.org/72385815:48
bauzasmmmm, amiwrong ?15:48
dansmithbauzas: depends on which bit you're talking about warning for15:48
openstackgerritMerged openstack/nova master: Update contributor guide for Victoria  https://review.opendev.org/72264715:48
dansmithbauzas: the stuff we're breaking in U would be a nova-status U patch to warn the T people15:48
bauzasthis would require a U install somewhere but okay15:49
dansmiththat's the way nova-status works15:49
bauzasI'm then confused15:49
bauzasthen, it's all good15:49
bauzaslet's make it a nova-status upgrade check and yell something is wrong15:49
bauzasdouble this with relnotes15:50
bauzasand gosh saves the rest15:50
*** brinzhang_ has quit IRC15:50
bauzasgmann: ^15:50
*** brinzhang_ has joined #openstack-nova15:50
jsuchomeefried, bauzas, dansmith: Hi, could we please get  https://review.opendev.org/#/c/572805/ reopen _again_ ?15:51
gmannhow we will differentiate the upgrade with re-generated file vs new deployment/upgrade moving to new system15:51
openstackgerritStephen Finucane proposed openstack/nova master: objects: Add online migration for legacy NUMA objects  https://review.opendev.org/53741415:51
bauzasgmann: greenfields don't run the nova-status check15:51
dansmithah, yeah I guess gmann has a point15:52
bauzasmake it a flag (c)15:52
efriedgmann: restored15:52
dansmithjsuchome: are you going to work on it yourself?15:53
jsuchomeunless tobiash has time to pick it up ...15:53
stephenfinartom: I switched that to startswith which is as optimal as I can get, aside from enumerating every possible legacy NUMA topology configuration :)15:53
artomstephenfin, hehe15:54
gmannI still feel (dansmith might be angry on me saying this again and again ) this usage of re-generated file is wrong thought common and telling them to use it in right way (with consistent guide on oslo side) can correct the things for long term too.15:54
gmann*though15:54
dansmithgmann: the right way is to switch to yaml, fully commented :)15:54
bauzasgmann: the ship has sailed.15:55
dansmithbauzas: agree :)15:56
gmannyeah, yaml and they can un-comment the rule with new values if they want. Honestly satying, that the way i was thinking people using policy file after policy-in-code15:56
gmannhumm15:56
bauzasgmann: can you please clarify the problem you have for distinguishing the different upgrade cases ?15:56
bauzasI see three cases15:57
bauzas1/ Ussuri greenfields15:57
jsuchomedansmith: so last time it was tobiash, let's wait if we wants to continue and if not, I would start myself15:57
bauzas2/ T->U and no policy.json changes15:57
bauzas3/ T->U and specific policy.json15:57
artomstephenfin, yeah, I left a follow-up comment. I guess I just don't know enough in this case, and what I've been able to learn isn't enough15:57
bauzasgmann: amirite ?15:57
gmannbauzas:  policy file with new defaults only (no deprecated old default)  cover two case 1. this broken case 2. people move to new defaults intentionally.15:57
dansmithjsuchome: okay15:57
gmannbauzas: 3rd one has ^^ above cases15:58
bauzasgmann: sure, but that's not the case you wanna warn, right?15:58
tobiashjsuchome: feel free to take it, atm I unfortunately I don't have time to work on it15:58
stephenfinzzzeek: I know you're busy, but any chance you'd be able to shine a light on https://review.opendev.org/#/c/537414/ at some point?15:58
stephenfinzzzeek: please and thank you :)15:58
*** klindgren has quit IRC15:59
*** lpetrut has joined #openstack-nova15:59
gmannbauzas: yeah, so we just say in nova-status what we are saying in reno ?15:59
*** klindgren has joined #openstack-nova15:59
gmanni mean new reno - https://review.opendev.org/#/c/723645/15:59
* bauzas looks16:00
bauzasgmann: but basically, yeah, code in python what you write in restructuredtext16:00
bauzasbecause parsers aren't good with english syntax16:00
zzzeekstephenfin: whats the quesiton, is contains() or startswith() faster?16:01
stephenfinzzzeek: Yes, if there isn't an index on the column16:01
zzzeekstephenfin: both contains() / startswith() are based on LIKE which is going to need a table scan16:01
artomzzzeek, and more generally, if we're stuck doing text filtering on a column without an index, what would be the lest sucky way?16:02
artom*least16:02
bauzasgmann: I briefly looked at the note16:02
zzzeekI don't see the db/model files here that we're talking about I just see objects files, is there a SQL query in those ?16:02
zzzeekand is the issue that you don't wnat to add a new column with the indexed information you need ?16:02
bauzasgmann: and unless I'm wrong, I don't see a technical problem for providing a nova-status check command verifying this16:02
stephenfinzzzeek: sec, lemme drag up the model16:02
zzzeekoh i see it16:03
zzzeekcompute_nodes = (context.session.query(models.ComputeNode)16:03
zzzeek        .filter(models.ComputeNode.numa_topology != null())16:03
zzzeek        .filter(~models.ComputeNode.numa_topology.startswith(16:03
zzzeek            '{"nova_object.name"'))16:03
zzzeekthat ?  yeah that's not great :)16:03
zzzeekdepends on number of rows16:03
zzzeek< 1000, no problem16:03
bauzasgmann: ie. look at the file, and if you find both old-style and new-style, yell it16:03
artomzzzeek, well, all instances16:03
artomSo multiple thousands, maybe into the millions for large deployments16:03
zzzeekincluding old ones that are offline ?16:03
zzzeekartom: yeah that's not going to be fast16:03
stephenfinartom: not deleted instances16:03
stephenfintbc16:04
zzzeekyou want to get the # of rows as low as possible before applying a like on it16:04
artomstephenfin, does that filtering happen before or after the string filter?16:04
gmannbauzas: ok, let me add in nova-status also16:04
bauzasgmann: if you wanna some examples, go over there https://github.com/openstack/nova/blob/master/nova/cmd/status.py#L36416:04
zzzeekthere are other ways to do this, mysql/mariadb might ahve a MATCH operator but that requires changes16:04
stephenfinI actually don't know /o\ Does filter ordering matter?16:04
artomzzzeek, yeah, IIUC MATCH needs full text index, no?16:05
zzzeekbut ideally you'd have the information you need captured in some dedicated column, or if for example the "numa_topology" were a forieng key to some collection table, you could limit the rows on that side to a list of posible foreign key ids, that kind of thing16:05
zzzeekartom: yes16:05
gmannbauzas: sure, thanks16:06
bauzasanyway, /me calls it a day16:06
stephenfinzzzeek: Unfortunately this is a JSON blob rather than an actual table. No foreign keys here16:07
zzzeekso as far as LIKE '%foo%' vs. LIKE 'foo%', I don't know the details of what mysql/mariadb would do, we would imagine the second is "faster" but i dont know that it can use indexes for that16:07
stephenfinand we're trying to move from one format of JSON blob to another16:07
artomzzzeek, we can't play around with the schema for this, we need to work with the columns/indeces that we have16:07
artomOr don't have :(16:07
zzzeekstephenfin: Mysql /mariadb have JSON operators now, do those apply here?16:08
zzzeeke.g. you can extract values from a json structure16:08
stephenfindo those apply if the column type is just TEXT?16:08
zzzeekstephenfin: yes there is no JSON type on both backends, there's ...some kind of keyword on one of htem16:08
dansmithzzzeek: is that really faster than a string comparison? I would expect that would require reading the whole text, more cpu to parse, and then run the comparison16:09
zzzeekmysql has a native JSON mariasdb does not but the json operators should work on either16:09
zzzeekdansmith: I dunno, would need to read some docs16:09
dansmithI would be absolutely blown away if so :)16:09
zzzeekhttps://mariadb.com/kb/en/json_value/16:10
zzzeekdansmith: Postgresql JSON type probably builds some index16:10
artomstephenfin, I don't support looking at updated_date is enough?16:10
artom*suppose16:10
zzzeekMysqls' might as well16:10
artomOr can help in any way?16:10
zzzeekmariadb, not too sure16:10
dansmithzzzeek: sure, if the column type is json then maybe16:10
stephenfinartom: I considered that, but I don't know when someone upgraded16:10
stephenfinso if ~in theory~ someone was on Juno for ages - say, until 2016, and eventually decided to upgrade, and are now upgrading that same cloud to Victoria16:11
artomstephenfin, actually - what about a two step approach? 1. the update on read thing we talked about earlier 2. let it sit for a cycle or two, then do a query with udpated_at earlier than time spent sitting16:11
zzzeekdansmith: oh here's an intersting approahc, uisng a generated column to index parts of the json document when they are inserted16:12
zzzeekhttps://www.compose.com/articles/mysql-for-json-generated-columns-and-indexing/16:12
dansmithzzzeek: that doesn't help this case16:12
stephenfinand are moving the instance for the first time since before that upgrade off of Juno :)16:12
zzzeekdansmith: brcause....table cannot be changed, right?16:12
dansmithzzzeek: we're specifically looking at old data yeahg16:12
*** brinzhang_ has quit IRC16:12
zzzeekdansmith: old data can be copied into...new tables and columns?16:12
*** brinzhang_ has joined #openstack-nova16:13
dansmithzzzeek: no, we might as well convert it if we're going to read it16:13
zzzeekdansmith: yup.  if you have a big old JSON blob and you want to pull things out of it and performance is an issue then you would need to put this data into some indexable format somewhere else16:13
*** ociuhandu has quit IRC16:13
zzzeekstephenfin: ^^^16:14
dansmithartom: updated_at is on the instance_extra row, right? so it doesn't really mean we've updated any one or all columns necessarily16:14
stephenfinzzzeek: okay, thanks for the input :)16:15
artomdansmith, hrmm, yeah - I guess I was assuming "update on read" would trigger for any read of any column of that row16:16
artomNot just instance_extra.numa_topology reads16:16
dansmithinstance_extra was really supposed to be individually queried and updated, although I dunno how much that really happens.. it was mostly for lazy-loadable blobby things originally16:16
artomIs this is the first time we're hitting this problem?16:17
artomApparently so - at least using .contains()16:17
*** rpittau is now known as rpittau|afk16:18
* artom -> lunch16:19
*** ociuhandu has joined #openstack-nova16:20
*** ociuhandu has quit IRC16:25
zigoIf you guys think we don't have enough time before the final release (which I can agree on), why not just delay this for 21.0.1 or something?16:29
zigoMy biggest concern is not being able to actually "see" what's set by what we have in defaults.16:30
zigoYes, it's documented, but it's not the same.16:30
zigoI'll try using policy.yaml though ... :P16:30
dansmithzigo: delay "this" meaning the policy stuff in general?16:30
zigoYeah.16:31
dansmithzigo: it was a large number of patches.. reverting it now would be .. huge.16:31
zigodansmith: I thought it'd be just a simple patch to the oslo-policy-sample-generator ... :P16:32
zigoMaybe I'm being naive.16:32
dansmithzigo: the change in question was on the nova side, not oslo.. we'd need new code on the oslo side to allow generating the policy file with the now-deprecated original defaults16:35
*** evrardjp has quit IRC16:35
*** evrardjp has joined #openstack-nova16:35
zigoNow I see what you guys were talking about for the yaml thing: it's by default generated with everything commented out ...16:37
zigo(I just tried...)16:37
zigoThat's probably nicer indeed, and probably good enough for operators, and also maybe more easy to have a policy.d16:37
zigoThough the last time I tried, it wouldn't load ... :/16:37
* zigo tries again this time.16:37
*** ociuhandu has joined #openstack-nova16:38
*** dtantsur is now known as dtantsur|afk16:40
zigoLooks like it works as one would expect... :)16:41
jsuchomedansmith: ok, so it seems it's up to me, so if you could reopen and reassign it ... thanks16:41
dansmithjsuchome: all you need to do is propose the changes yourself16:42
jsuchomeso should I just cherry pick to my branch?16:43
*** sapd1_x has quit IRC16:43
zigoAll this would be great if the Debian infrastructure wasn't completely down today ... :/16:44
dansmithjsuchome: just grab the latest version of that patch into your tree, make changes, git review.16:44
*** lyarwood has quit IRC16:45
*** vishalmanchanda has quit IRC16:45
*** maciejjozefczyk has quit IRC16:50
*** lpetrut has quit IRC16:51
*** derekh has quit IRC16:52
*** hoonetorg has joined #openstack-nova17:00
*** sapd1_x has joined #openstack-nova17:11
*** nightmare_unreal has quit IRC17:25
artomdansmith, answers provided: https://review.opendev.org/#/c/672595/7317:33
artom(Hopefully)17:33
gmannzigo: nice. +1 thanks for checking.17:33
*** martinkennelly has quit IRC17:37
*** martinkennelly has joined #openstack-nova17:38
artom\o/17:43
artomI have a 1:1 in 15 minutes, otherwise it'd be beer time17:44
*** ociuhandu has quit IRC17:44
*** ociuhandu has joined #openstack-nova17:46
*** dpawlik has quit IRC17:48
*** ociuhandu has quit IRC17:51
gmannzigo: and you generated with same tool right ?17:53
*** tesseract has quit IRC17:53
zigogmann: Yeah, just --format yaml. Now, I'll have to set policy.yaml as default in nova.conf17:54
zigoThough as I wrote earlier, Debian @UBC is down, so can't do anything right now ... :(17:54
*** lee1 has joined #openstack-nova17:54
zigoNo Git to play with.17:55
gmann+117:55
*** gryf has quit IRC17:56
zigoAlso, this clashes with puppet-openstack which uses .json.17:57
zigoIt's going to be fun time to fix too ...17:57
*** alistarle has joined #openstack-nova18:06
openstackgerritGhanshyam Mann proposed openstack/nova master: Clarify the policy new defaults upgrade notes  https://review.opendev.org/72364518:08
openstackgerritMerged openstack/nova master: Remove Babel requirement  https://review.opendev.org/72072518:11
openstackgerritMerged openstack/nova master: Remove translation sections from setup.cfg  https://review.opendev.org/72320618:11
*** alistarle has quit IRC18:15
*** sapd1_x has quit IRC18:17
*** ociuhandu has joined #openstack-nova18:23
*** takamatsu has quit IRC18:26
*** sapd1_x has joined #openstack-nova18:30
*** brinzhang has quit IRC18:34
*** brinzhang has joined #openstack-nova18:34
*** sapd1_x has quit IRC18:44
*** ralonsoh has quit IRC18:51
*** priteau has quit IRC18:53
openstackgerritArtom Lifshitz proposed openstack/nova stable/queens: DNM: Partial cherry-pick of report client changes  https://review.opendev.org/72375018:57
openstackgerritArtom Lifshitz proposed openstack/nova stable/queens: DNM: Add a placement audit command  https://review.opendev.org/72375118:57
*** ociuhandu has quit IRC18:57
*** jangutter has quit IRC19:04
*** jangutter has joined #openstack-nova19:04
*** ociuhandu has joined #openstack-nova19:13
*** xek has quit IRC19:13
*** lee1 is now known as lyarwood19:24
*** ccamacho has quit IRC19:42
*** jsuchome has quit IRC19:47
*** JamesBenson has quit IRC20:02
*** JamesBenson has joined #openstack-nova20:07
*** threestrands has quit IRC20:09
*** rchurch has joined #openstack-nova20:16
*** xek has joined #openstack-nova20:24
melwittgmann: I thought you wanted to wait for these first? https://review.opendev.org/#/q/topic:qa-ussuri-release+status:open20:31
gmannmelwitt: devstack and grenade setup mainly which are merged. devstack-gate changes is for legacy jobs which this patch replacing20:32
melwittoh ok20:32
*** dustinc has joined #openstack-nova20:34
*** raildo_ has joined #openstack-nova20:37
sean-k-mooneyam https://bugs.launchpad.net/nova/+bug/1875418 have we ever support a policy.yaml?20:39
openstackLaunchpad bug 1875418 in OpenStack Compute (nova) "Generated policy.json in Ussuri is broken by default" [High,In progress] - Assigned to Ghanshyam Mann (ghanshyammann)20:39
*** raildo has quit IRC20:39
sean-k-mooneyi tought we only supported policy files in json format20:39
sean-k-mooneyi ask because teh " [puppet][packaging] Switching to policy.yaml (over policy.json)" thread seams to imply that is a thing20:41
sean-k-mooneybut i did not think we supported a policy.yaml file instead of policy.json20:41
*** martinkennelly has quit IRC20:42
sean-k-mooneyhuh i guess its a thing https://docs.openstack.org/oslo.policy/latest/admin/policy-yaml-file.html20:42
bnemecWe've been recommending yaml since policy in code happened.20:43
bnemecApparently we need to work on our PR though. :-)20:44
gmannyeah, and not much attention on that  and this issue came up now20:45
sean-k-mooneyya i mean yaml is probably nice to work with in terms of generating and reading the file and form a python point of view it makes little difference as we will jsut load it into a python dict in etierh case then process it20:45
sean-k-mooneybut i never heard that we added supprot for parseing yaml files instead20:45
sean-k-mooneybnemec: it might be something that woudl be worth make a comuntiy goal20:46
sean-k-mooneyto get everyone to move to policy.yaml espeically the deployment tools20:46
openstackgerritMerged openstack/nova master: Functional tests for NUMA live migration  https://review.opendev.org/67259520:46
gmannit is supported in oslo side right20:46
bnemecsean-k-mooney: It was: https://governance.openstack.org/tc/goals/selected/queens/policy-in-code.html20:46
sean-k-mooneyalthough i guest they should not be setting one by default20:46
bnemecOh, deployment tools.20:46
sean-k-mooneybnemec: well plocy in code was20:47
*** nweinber has quit IRC20:47
sean-k-mooneybnemec: i was more thinking of makeing sure our docs advise to use policy.yaml files20:47
sean-k-mooneyand any deployment tools that currently supprot customising policy.json use policy.yaml20:48
bnemecThey do: https://docs.openstack.org/oslo.policy/latest/admin/policy-json-file.html ;-)20:48
bnemecBut yeah, clearly we need to push it harder.20:48
sean-k-mooneybnemec: do the nova docs?20:48
gmannbnemec: and that happen when things get broken otherwise its less chance people read doc or be in sync on new things20:49
bnemecThat I don't know. The only in-project policy doc I'm aware of is the policy sphinx plugin.20:49
sean-k-mooneyhttps://docs.openstack.org/nova/rocky/configuration/policy.html i gues it just list the polices20:49
sean-k-mooneyand the sample kind of looks like yaml https://docs.openstack.org/nova/rocky/configuration/sample-policy.html20:49
gmannsean-k-mooney: the file form mentioned is yaml one -https://docs.openstack.org/nova/latest/configuration/sample-policy.html20:50
sean-k-mooneyok it is a yaml file20:50
bnemecYep, that's the yaml sample policy output.20:50
sean-k-mooneyya you can download it https://docs.openstack.org/nova/rocky/_downloads/nova.policy.yaml.sample20:50
sean-k-mooneyok im just used to people saying policy.json the whole time20:50
sean-k-mooneywe still refer to it as policy.json here https://docs.openstack.org/nova/rocky/configuration/20:52
*** jmlowe has joined #openstack-nova20:54
bnemecYeah, and unfortunately policy.json is still the default name in oslo.policy. We've had discussions about making it look for both json and yaml, but it has security implications if we guess wrong.20:54
*** xek has quit IRC20:55
sean-k-mooneyso does it only look for one of them20:55
gmannfirst it look for json and then yaml, if i am not wrong20:56
sean-k-mooneyok so if you have both it will use the json file20:56
sean-k-mooneyor will it load the default form code then load the json then the yaml20:56
sean-k-mooneyboth would be vaild but im not really sure which would be more suprising20:57
sean-k-mooneyi kind of would expect the second option with an error if there was a conflit between the json and yaml file20:57
sean-k-mooneyour just error if both were there20:57
sean-k-mooneythat will be less surprising i guess20:58
sean-k-mooneyhaving multiple souces of policy is a beacon for bugs20:58
bnemecIt only looks for policy.json. It will parse files in either format in the order gmann said.20:59
bnemecSo if you say policy_file=policy.something it will first attempt to parse it as json, and if that fails try again as yaml.20:59
sean-k-mooneyok so to use https://docs.openstack.org/oslo.policy/latest/admin/policy-yaml-file.html you need to chagne the policy_file in the main config file to point to policy.yaml21:00
gmannyeah and default are loaded only if the registered rule is not in file21:00
bnemecRight21:00
sean-k-mooneyok that is not obvious form the docs but i can see why you might have chosen that design21:01
sean-k-mooneywell good to know21:01
gmannbnemec: i think we can change the default value to policy.yaml and start error if not present and no fallback to policy.json ?21:01
gmanni mean in Victoria21:01
bnemecWorth noting that it can be overridden by individual projects. I believe cinder has done that.21:01
bnemecI don't know how much pain it caused their users when they switched, or if they were lucky enough to start out with it that way.21:01
sean-k-mooneybnemec: right oslo.config support progomatic overrides21:01
sean-k-mooneyso we could do set_default in nova to point it to a different default for nova21:02
bnemecgmann: But we can't error on a missing policy file because that's perfectly valid.21:02
gmannbnemec: ah, that's right.21:03
sean-k-mooneylike this right https://docs.openstack.org/oslo.config/4.0.0/faq.html#why-are-configuration-options-not-part-of-a-library-s-api21:03
bnemecsean-k-mooney: There's an api provided for it: https://github.com/openstack/oslo.policy/blob/master/oslo_policy/opts.py#L12121:03
bnemecGenerally speaking, consumers shouldn't mess with library opts directly.21:03
sean-k-mooneyyep i just linked to the docs for it21:03
bnemecYes, exactly.21:04
bnemecasync communication. :-)21:04
sean-k-mooneyand ya i agree because it make debuging it a pain for the lib maintainer21:04
bnemecAnd it will break if we ever rename the opt, even with deprecation.21:04
bnemecBecause the in-code references don't have deprecation logic.21:04
sean-k-mooneyyou could proably make that work bust defineing an atribute that was initalsed to the other one21:05
sean-k-mooneybut also good to know21:05
sean-k-mooneyim not sure we actully ever do this in nova21:05
sean-k-mooneyor in any other code i have looked at21:06
sean-k-mooneyhum actully we are for things in our own config.... im going to pretend i didnt see that and move on21:09
*** JamesBenson has quit IRC21:24
*** raildo_ has quit IRC21:26
*** bbowen has quit IRC21:29
*** bbowen has joined #openstack-nova21:34
*** ociuhandu has quit IRC21:34
*** ociuhandu has joined #openstack-nova21:34
*** JamesBenson has joined #openstack-nova21:38
*** slaweq has quit IRC21:41
*** ociuhandu has quit IRC21:41
*** mriedem has left #openstack-nova21:56
openstackgerritGhanshyam Mann proposed openstack/nova master: Add nova-status upgrade check and reno for policy new defaults  https://review.opendev.org/72364522:08
*** JamesBenson has quit IRC22:15
openstackgerritMerged openstack/nova master: zuul: Switch to the Zuulv3 grenade job  https://review.opendev.org/70436422:20
openstackgerritsean mooney proposed openstack/nova master: silence amqp heartbeat warning  https://review.opendev.org/72418822:28
openstackgerritGhanshyam Mann proposed openstack/nova stable/ussuri: zuul: Switch to the Zuulv3 grenade job  https://review.opendev.org/72418922:29
gmannlyarwood: melwitt backported to ussuri ^^ to have single grenade job running in ussuri as grenade zuulv3 job merged in ussuri22:30
sean-k-mooneymelwitt: im not sure if https://review.opendev.org/#/c/724188/1/nova/config.py will work but assuming it does it would be good to get your input on if we should drop that log message as the patch currently does or just reduce the log level to debug22:31
*** rcernin has joined #openstack-nova22:33
gmanndansmith: bauzas gibi added the upgrade check also for policy stuff - https://review.opendev.org/#/c/723645/22:35
*** ociuhandu has joined #openstack-nova23:04
*** JamesBenson has joined #openstack-nova23:06
*** JamesBenson has quit IRC23:11
*** ociuhandu has quit IRC23:17
*** avolkov has quit IRC23:27
*** tosky has quit IRC23:39

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