Wednesday, 2020-06-10

*** brinzhang has joined #openstack-nova00:02
openstackgerritmelanie witt proposed openstack/nova stable/ussuri: libvirt: Don't delete disks on shared storage during evacuate  https://review.opendev.org/73124800:05
*** hongbin has quit IRC00:14
*** grandchild has quit IRC00:15
*** hongbin has joined #openstack-nova00:16
*** tetsuro has joined #openstack-nova00:33
*** lbragstad has joined #openstack-nova00:34
openstackgerritmelanie witt proposed openstack/nova stable/train: libvirt: Don't delete disks on shared storage during evacuate  https://review.opendev.org/73127300:44
*** lbragstad_ has joined #openstack-nova00:47
*** lbragstad has quit IRC00:50
*** brinzhang_ has joined #openstack-nova01:05
*** xiaolin has joined #openstack-nova01:07
*** brinzhang has quit IRC01:08
*** jawad_axd has joined #openstack-nova01:12
*** brinzhang0 has joined #openstack-nova01:19
*** threestrands has joined #openstack-nova01:19
*** xiaolin has quit IRC01:22
*** brinzhang_ has quit IRC01:23
*** brinzhang_ has joined #openstack-nova01:27
*** xiaolin has joined #openstack-nova01:28
*** brinzhang0 has quit IRC01:30
*** hamalq_ has quit IRC01:32
*** xiaolin has quit IRC01:33
*** sapd1 has joined #openstack-nova01:38
*** jawad_axd has quit IRC01:45
*** brinzhang0 has joined #openstack-nova01:46
*** brinzhang has joined #openstack-nova01:46
*** brinzhang_ has quit IRC01:47
*** brinzhang_ has joined #openstack-nova01:48
*** brinzhang has quit IRC01:51
*** mlavalle has quit IRC02:01
*** lbragstad_ has quit IRC02:05
*** lbragstad_ has joined #openstack-nova02:14
openstackgerritmelanie witt proposed openstack/nova stable/stein: libvirt: Don't delete disks on shared storage during evacuate  https://review.opendev.org/73269602:24
*** tetsuro_ has joined #openstack-nova02:35
*** tetsuro_ has quit IRC02:38
*** brinzhang0 has joined #openstack-nova02:40
openstackgerritsunhao proposed openstack/nova master: Add checks for volume status when rebuilding  https://review.opendev.org/73473402:40
*** brinzhang_ has quit IRC02:43
*** tetsuro has quit IRC02:46
*** brinzhang_ has joined #openstack-nova02:47
openstackgerritmelanie witt proposed openstack/nova stable/rocky: libvirt: Don't delete disks on shared storage during evacuate  https://review.opendev.org/73270802:49
*** brinzhang0 has quit IRC02:50
*** rcernin has quit IRC02:53
*** rcernin_ has joined #openstack-nova02:53
*** brinzhang0 has joined #openstack-nova02:58
*** tetsuro has joined #openstack-nova02:59
*** vishalmanchanda has joined #openstack-nova02:59
*** brinzhang_ has quit IRC03:02
*** brinzhang_ has joined #openstack-nova03:05
openstackgerritmelanie witt proposed openstack/nova stable/queens: libvirt: Don't delete disks on shared storage during evacuate  https://review.opendev.org/73271703:07
*** rcernin_ has quit IRC03:07
*** brinzhang0 has quit IRC03:08
*** tetsuro has quit IRC03:15
*** xiaolin has joined #openstack-nova03:16
*** rcernin_ has joined #openstack-nova03:19
*** xiaolin has quit IRC03:20
*** tetsuro has joined #openstack-nova03:23
*** rcernin_ has quit IRC03:24
*** rcernin has joined #openstack-nova03:25
*** tetsuro has quit IRC03:36
*** psachin has joined #openstack-nova03:40
*** tetsuro has joined #openstack-nova03:40
*** lbragstad_ has quit IRC04:02
*** Liang__ has joined #openstack-nova04:04
*** yaawang has quit IRC04:04
*** yaawang has joined #openstack-nova04:04
*** brinzhang0 has joined #openstack-nova04:22
*** brinzhang_ has quit IRC04:25
*** purplerbot has quit IRC04:27
*** yankcrime has quit IRC04:29
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-nova04:33
*** hongbin has quit IRC04:39
*** yaawang has quit IRC04:40
*** links has joined #openstack-nova04:40
*** yaawang has joined #openstack-nova04:41
*** jawad_axd has joined #openstack-nova04:48
*** ratailor has joined #openstack-nova04:52
*** udesale has joined #openstack-nova04:56
*** dklyle has quit IRC04:57
*** yaawang has quit IRC05:00
*** yaawang has joined #openstack-nova05:01
*** jraju__ has joined #openstack-nova05:09
*** links has quit IRC05:10
*** sapd1 has quit IRC05:55
*** xiaolin has joined #openstack-nova06:02
*** Liang__ has quit IRC06:03
*** Liang__ has joined #openstack-nova06:08
*** Liang__ is now known as LiangFang06:09
*** factor has quit IRC06:17
*** factor has joined #openstack-nova06:17
*** whoami-rajat has quit IRC06:17
*** vesper has quit IRC06:18
*** LiangFang has quit IRC06:18
*** vesper11 has joined #openstack-nova06:18
*** Liang__ has joined #openstack-nova06:18
*** whoami-rajat has joined #openstack-nova06:18
*** sapd1 has joined #openstack-nova06:23
*** Liang__ has quit IRC06:27
*** Liang__ has joined #openstack-nova06:28
*** maciejjozefczyk has joined #openstack-nova06:38
*** Liang__ has quit IRC06:40
*** Liang__ has joined #openstack-nova06:41
tony_sudansmith: A reviewer of ProviderConfigFile patch wanted to understand why additionProperties is set to true by default in the first place. https://review.opendev.org/#/c/673341/45/nova/compute/provider_config_schemas/provider_config_schema_v1.yaml might require your attention. Thanks.06:41
*** jsuchome has joined #openstack-nova06:42
*** links has joined #openstack-nova06:42
*** jraju__ has quit IRC06:43
*** rcernin has quit IRC06:44
*** rcernin_ has joined #openstack-nova06:44
*** rcernin_ has quit IRC06:50
*** slaweq has joined #openstack-nova06:50
*** yikun has joined #openstack-nova06:52
*** rcernin_ has joined #openstack-nova06:52
*** ratailor has quit IRC06:53
*** ratailor has joined #openstack-nova06:56
*** rcernin_ has quit IRC06:59
*** tesseract has joined #openstack-nova07:01
*** xiaolin has quit IRC07:05
bauzasgood morning Nova07:09
*** iurygregory has quit IRC07:11
*** psachin has quit IRC07:12
*** sapd1 has quit IRC07:12
*** ttsiouts has joined #openstack-nova07:13
*** ttsiouts has quit IRC07:14
*** tetsuro has quit IRC07:14
*** ttsiouts has joined #openstack-nova07:16
gibibauzas: good morning07:20
bauzasgibi: morning07:21
bauzasfwiw, just created a blueprint for tracking reshape tooling work for Ussuri https://blueprints.launchpad.net/nova/+spec/offline-reshape-tool07:21
*** rpittau|afk is now known as rpittau07:21
gibibauzas: cool. Do you agree that we had enough discussion about FFU on the PTG so that I can approve that bp without further discussion on the weekly meeting?07:22
openstackgerritsunhao proposed openstack/nova master: Add checks for volume status when rebuilding  https://review.opendev.org/73473407:23
*** rcernin_ has joined #openstack-nova07:23
*** ccamacho has joined #openstack-nova07:24
*** xiaolin has joined #openstack-nova07:27
*** rcernin_ has quit IRC07:28
*** tosky has joined #openstack-nova07:29
bauzasgibi: well, I'm torn about it07:31
bauzasgibi: we discussed at the PTG about how to call placement without having the service running07:31
bauzasbut i'm not sure we had a consensus07:31
bauzaswe have a way to do it that was accepted for the reshape spec in https://specs.openstack.org/openstack/nova-specs/specs/stein/approved/reshape-provider-tree.html#direct-interface-to-placement07:32
*** iurygregory has joined #openstack-nova07:33
*** dustinc has quit IRC07:35
gibibauzas: OK, then let's double check this with the team on the weekly meeting.07:35
bauzasthanks07:35
gibiI will add it to the agenda07:35
*** jraju__ has joined #openstack-nova07:35
bauzasgibi: looking at the spec, looks like we agreed on using PlacementDirect for this07:36
bauzasso if folks agree in the meeting, we can have a specless bp07:36
*** xiaolin has quit IRC07:36
gibibauzas: yes, but on the PTG I was tried to mention that fact and get a pushback because that would require DB access from the compute nodes07:36
*** links has quit IRC07:36
bauzasgibi: PlacementDirect supports oslo.config07:36
bauzasso you would run the nova-manage command that would call PlacementDirect with DB options07:37
gibitrue, but our deployment model does not require db access for compute hosts so far07:37
*** tesseract-RH has joined #openstack-nova07:37
gibiso the db server might not even accessible from the compute hosts07:37
gibie.g network separation07:37
bauzasgibi: surely, but that would be something we would comment07:38
bauzaslike a caveat07:38
bauzasand it's just for FFUs07:38
gibiOK07:38
*** tesseract has quit IRC07:40
*** links has joined #openstack-nova07:42
*** jraju__ has quit IRC07:42
*** ralonsoh has joined #openstack-nova07:45
gibilet's go with the original plan from the spe07:46
gibic07:46
*** jraju__ has joined #openstack-nova07:47
*** links has quit IRC07:47
*** belmoreira has joined #openstack-nova07:51
*** rcernin_ has joined #openstack-nova07:59
*** rcernin_ has quit IRC08:03
*** avolkov has joined #openstack-nova08:08
*** links has joined #openstack-nova08:09
*** jraju__ has quit IRC08:09
*** martinkennelly has joined #openstack-nova08:11
sean-k-mooneygibi: bauzas well ingeneral we whould assume the db server is not accesable from the compute yes08:14
sean-k-mooneythis is why we discussed the need to potentialy  seperate the data collection from the updating of placment or the db08:15
*** xek has joined #openstack-nova08:15
sean-k-mooneye.g. we might need to run something on the compute node to generate some output which is the canges to be done via ssh then do the update from the contoler instead08:16
sean-k-mooneyi think johnthetubaguy brought that up or dansmith in the ptg sesssion08:16
sean-k-mooneygibi: and ya its not even a case of our deployment model does not require it it activly discurages direct db acess form the compute on security grounds08:18
sean-k-mooneyat least it has sicne we got rid fo the local conducor stuff like 2-3 years ago08:18
bauzassean-k-mooney: operators can pipe their needs for just a FFU upgrade if they want08:20
sean-k-mooney"pipe there needs" ?08:21
sean-k-mooneyby the way look like some people from vmware are fixing the vmware nsx ci08:22
*** ravsingh has joined #openstack-nova08:24
*** sapd1 has joined #openstack-nova08:24
*** martinkennelly has quit IRC08:24
sean-k-mooneyhttp://207.189.188.190/logs/58/734658/1/check-vote/ext-nova-zuul/f8d2e76/tempest_results.html.gz08:24
*** martinkennelly has joined #openstack-nova08:24
*** tetsuro has joined #openstack-nova08:25
*** martinkennelly has quit IRC08:25
sean-k-mooneyi think it has to be manually triggered via vmware-recheck-patch but i guess that is still an improvement08:25
*** martinkennelly has joined #openstack-nova08:26
bauzassean-k-mooney: I mean, for example, to do something like piping netcat08:26
sean-k-mooneybauzas: they could but i dont think we sould require direct db access08:27
sean-k-mooneymaking them proxy it via netcat or ssh is a hack IMO08:28
bauzasit's a nova-manage command so we need it anyway :)08:28
bauzasthey need to provide DB creds08:28
sean-k-mooneybauzas: so that means nova-manage is not suitable solution to this probelem08:28
bauzasbut if you need to run this command on a nova-compute (and then you don't have a specific DB cred for it), then you could just use netcat08:29
bauzassean-k-mooney: it would work for any operator that doesn't want to have compute nodes be in a specific network08:30
sean-k-mooneyi think we should be providing a way to pass in some data structro to the nova-manage command which it uses to then do the reshapes08:30
bauzassean-k-mooney: we could do it, that's one of the things we said08:30
bauzashence two commands08:30
*** ttsiouts has quit IRC08:30
*** martinkennelly has quit IRC08:31
bauzasand piping between them (or passing a data structure)08:31
sean-k-mooneyyep once command that you run on the compute node that gets the info form the virt driver and produces the reshap  yaml or whatever and then a second that you run on a node with db access08:31
bauzassean-k-mooney: but tbc, https://specs.openstack.org/openstack/nova-specs/specs/stein/approved/reshape-provider-tree.html#direct-interface-to-placement already thought about it08:31
sean-k-mooneybauzas: that was not thinking about reshapes08:32
*** dtantsur|afk is now known as dtantsur08:32
*** jmlowe has quit IRC08:32
sean-k-mooneyit was thinking about db upgrades08:32
sean-k-mooneythose are very different things08:32
sean-k-mooneywell it mentions reshpaes but we did not have any at that point08:33
*** ttsiouts has joined #openstack-nova08:34
sean-k-mooneyactully i guess look ing at the spec in general this is the resahpe spec08:34
*** bbowen has quit IRC08:34
*** bbowen has joined #openstack-nova08:35
sean-k-mooneyi think it was making the assumtion however that reshaps did not need compute specific infomation08:35
*** jmlowe has joined #openstack-nova08:35
sean-k-mooneylooking at the ironic_flavor_migration examle i dont think that is the same as the libvirt case08:36
sean-k-mooneyhttps://review.opendev.org/#/c/501025/12/nova/cmd/manage.py08:36
sean-k-mooneybecause the ironic virt dirver talks to the ironic api08:36
sean-k-mooneyso the compute serivce virt driver does not need to be colocated on the same host as the hypervior08:37
gibithe spec gives solution for one side of the problem. We don't have a running placement API service during FFU but we need to write into the placement db due to reshape08:37
gibiplacement direct allows that.08:38
sean-k-mooneyyes it will08:38
gibisean-k-mooney is right that collecting the data for the reshape is not solved in tha spec08:38
gibiexcept that it mentions to start up a virt driver, but it does not handle the implication of that statemen08:39
gibit08:39
sean-k-mooneygibi: https://review.opendev.org/#/c/501025/ is the implemeation for ironic08:39
sean-k-mooneybut that is very different then libvirt08:39
sean-k-mooneythe ironic virt dirver is used here https://review.opendev.org/#/c/501025/12/nova/cmd/manage.py@98808:41
*** nightmare_unreal has joined #openstack-nova08:42
gibiinteresting08:42
sean-k-mooneywe cant just call the reshape function in the libvirt dirver however.08:42
sean-k-mooneyironic works because all the info it need is either in the nova db or in the ironic api08:42
sean-k-mooneythis is all that was doing https://github.com/openstack/nova/blob/b6f3d393aa5cb755f30fa70d4acc614c32216c99/nova/virt/ironic/driver.py#L570-L58208:43
sean-k-mooneythats doing an online data migration but its not doing a reshape08:44
gibithe analogous call would be nova.virt.libvirt.driver.LibvirtDriver.update_provider_tree08:46
gibibut that needs a hypervisor connection as far as I see08:46
sean-k-mooneywell yes an no that would update the provider i guess but it would do more then just run the reshapes08:46
sean-k-mooneygibi: yes it need the resouce track and a bunch of other things that reuiqre not just a connection to libvirt but file access too08:47
sean-k-mooneyim pretty sure we need to check /sys for some things08:47
sean-k-mooneylike sev support? we need the compute nodes config for allocation ratio stuff at the very least08:48
gibisean-k-mooney: agree that update_provider_tree does more than what is needed for reshape08:48
gibiI guess we need to see what are the bare minimum information to run each reshape codepath and see how can we provide that08:49
*** lvdombrkr has joined #openstack-nova08:49
sean-k-mooneythe pcpu reshape would need the compute node cpu_shared_set and cpu_dedicated_set config options techincally vcpu_pin_set too08:51
sean-k-mooneyi think the vgpu reshape to have seperate RP per pGPU needs libvirt and the mdev type config options08:51
sean-k-mooneygibi: if we proceeed with numa in placment that is going to need the host numa toplogy info from libfirt08:51
sean-k-mooneygibi: this is the vgpu reshape https://github.com/openstack/nova/blob/b6f3d393aa5cb755f30fa70d4acc614c32216c99/nova/virt/libvirt/driver.py#L775708:54
sean-k-mooneywell actully _update_provider_tree_for_vgpu is the top level function we would be calling and _update_provider_tree_for_pcpu is the cpu one08:56
gibiI see08:58
sean-k-mooney_get_all_assigned_mediated_devices which is used in the vgpu reshape directly read the guest xml https://github.com/openstack/nova/blob/b6f3d393aa5cb755f30fa70d4acc614c32216c99/nova/virt/libvirt/driver.py#L6940-L697308:58
*** jmlowe has quit IRC08:58
*** jmlowe has joined #openstack-nova08:59
*** yikun has quit IRC09:01
*** tetsuro has quit IRC09:01
*** spatel has joined #openstack-nova09:13
*** Luzi has joined #openstack-nova09:13
*** yankcrime has joined #openstack-nova09:14
*** spatel has quit IRC09:18
*** martinkennelly has joined #openstack-nova09:27
*** martinkennelly has quit IRC09:27
*** belmoreira has quit IRC09:29
*** jraju__ has joined #openstack-nova09:29
*** links has quit IRC09:29
*** martinkennelly has joined #openstack-nova09:32
openstackgerritStephen Finucane proposed openstack/nova master: libvirt: Don't allow "reserving" file-backed memory  https://review.opendev.org/73465809:35
openstackgerritMerged openstack/nova stable/ussuri: Add functional test for bug 1550919  https://review.opendev.org/73124709:35
openstackbug 1550919 in OpenStack Compute (nova) ussuri "[Libvirt]Evacuate fail may cause disk image be deleted" [Medium,In progress] https://launchpad.net/bugs/1550919 - Assigned to Lee Yarwood (lyarwood)09:35
stephenfinbauzas: Can you look at https://review.opendev.org/#/c/733668 ?09:36
bauzasstephenfin: ack, will do09:36
bauzasgibi: sean-k-mooney: sorry was on a meeting, saw your discussion09:37
bauzasyup, from a vgpu reshape perspective, we need to lookup the guest XMLs hence libvirt09:38
bauzas(and just not do a DB check)09:38
*** jraju__ has quit IRC09:38
openstackgerritMerged openstack/nova-specs master: Stop to use the __future__ module.  https://review.opendev.org/73287909:39
*** jraju__ has joined #openstack-nova09:40
gibistephenfin: about https://review.opendev.org/#/c/734658 would it worth to add a reno too to communicate a future breaking change?09:51
*** Liang__ has quit IRC09:51
stephenfingibi: Good idea. "upgrade" section?09:51
gibistephenfin: yeah09:51
stephenfinCool. Sec09:52
gibithanks09:52
openstackgerritAlexandre Arents proposed openstack/nova master: Snapshot: offload glance upload in a native thread  https://review.opendev.org/73477609:53
openstackgerritStephen Finucane proposed openstack/nova master: libvirt: Mark e1000e VIF as supported  https://review.opendev.org/73477709:58
stephenfinsean-k-mooney: Can you sanity check that too, please? ^09:58
openstackgerritStephen Finucane proposed openstack/nova master: libvirt: Don't allow "reserving" file-backed memory  https://review.opendev.org/73465810:15
stephenfingibi: ^10:15
stephenfinas requested10:15
stephenfinbauzas: Another (easier) one for your list https://review.opendev.org/#/c/734777/10:16
bauzasstephenfin: the exception one is a bit hairy, I need to make sure you don't forget anything10:16
sean-k-mooneystephenfin: yep ill take a look shortly10:17
*** ociuhandu has joined #openstack-nova10:18
sean-k-mooneystephenfin: did you check if we report hugepages in the host numa toplogy blob10:19
sean-k-mooneywhen file backed memory is enabled10:19
*** rpittau is now known as rpittau|bbl10:19
stephenfinI did not. What would be the implication?10:19
stephenfinJust that we shouldn't do it?10:19
sean-k-mooneywe cant use filebacked memory and hugepages at the same time10:20
sean-k-mooneybut the numa toplogy filter has no idea if this config value is set10:20
sean-k-mooneyso it wont elimiate those hosts10:20
stephenfinHmm, good point. That'd be another good fix10:20
stephenfinLemme go look10:20
sean-k-mooneyso unless we dont report hugepages when there vailable if its set then we could get boot fails i think10:20
sean-k-mooneyya seperate patch if its not done10:21
*** ociuhandu has quit IRC10:21
*** ociuhandu has joined #openstack-nova10:23
stephenfinDoes anyone know how to get a KCS taken down? https://access.redhat.com/solutions/394764110:25
*** ttsiouts has quit IRC10:25
*** ttsiouts_ has joined #openstack-nova10:25
stephenfinFor some daft reason, someone suggested people modify their DB rather than ask us to resolve a trivial bug :-\10:26
stephenfin^ Ignore that. Intended for downstream IRC :)10:30
sean-k-mooneydamit is there way way we can just stop support form publishing kcs artical without having them go through tech review10:37
sean-k-mooneyya i dont know but i reviewd https://review.opendev.org/#/c/734658/310:38
openstackgerritStephen Finucane proposed openstack/nova master: libvirt: Don't allow "reserving" file-backed memory  https://review.opendev.org/73465810:41
*** ociuhandu has quit IRC10:41
stephenfinsean-k-mooney: Addressed doc typo. Let's track the hugepage/total GB issue separately?10:41
sean-k-mooneyyep im cool with that we can just file a seperate bug that patch fixes the bug you have already filed10:42
bauzasstephenfin: https://review.opendev.org/#/c/733668/2 got a -1 because of PEP484 usage be py3 specific10:43
gibistephenfin: thanks for the reno10:43
sean-k-mooneybauzas: we are allowed to use py3 only syntax and feature on master10:44
bauzasI know10:44
stephenfinI was about to say :)10:44
sean-k-mooneybauzas: and this is not enforce excpetion type it adding them10:44
*** xek has quit IRC10:44
stephenfinpersonally, I think this patch is too invasive to backport10:44
bauzasbut then if we backport, we'll get linters shouting at us with no idea why10:44
sean-k-mooneyif we backport we need to drop the type info10:45
stephenfinI think we're just going to have to live with that. I'll just drop the type info if I went back past stable/ussuri10:45
sean-k-mooneywe were holding of on adding it so we did not need to use the comment syntax10:45
stephenfinyeah, exactly10:45
bauzasstephenfin: then, just amend the commit msg and we're all good10:45
stephenfinSure. What should I add?10:46
bauzasI don't want to refrain ourselves to use py3 styles, but I rather just want us to take 5 mins before writing it and consider backportability of such things10:46
sean-k-mooneyit took me a long time to be ok with the type on the right after all the c/c++/java/c# i wrote before learning python but im slowly gettin gused to it10:46
bauzasstephenfin: just tell your decision10:46
sean-k-mooneyit seam like most lanaguges are converging on that order now10:47
bauzasoption A/ this bugfix isn't intended to be backported10:47
bauzasoption B/ if people feel brave enough to backport, there will be a necessary change10:47
bauzasin other words, document your code :)10:47
stephenfinHmm, I _could_ but it does feel like stating the obvious10:48
sean-k-mooneybauzas: so im ok with b if iall it is is removing :<Type>10:48
bauzassean-k-mooney: me too, just my point10:48
bauzasagain, it's just a static check AFAIK10:48
sean-k-mooneyi dont think that need to be in a comit or called out anywhere in the chagne10:48
sean-k-mooneybauzas: well its not even a staitc check10:48
sean-k-mooneythe py2 jobs will fail10:48
sean-k-mooneyit wont parse correctly10:49
*** derekh has joined #openstack-nova10:49
stephenfinWe'd saying if you use Py3 syntax and your commit message has "Closes-Bug" in it, add this boilerplate10:49
sean-k-mooneystephenfin: i would really like to avoid that10:49
stephenfinI mean, we don't say "this bugfix has o.vo implications so you're not allowed backport it" in a commit10:49
sean-k-mooneywe coudld but i dont see the point10:49
sean-k-mooneystephenfin: bauzas we could update the contibutor guide or somehting to call it out i guess10:50
bauzassean-k-mooney: the point is that I'm afraid stable core reviewers could miss such tiny bits that would break10:50
sean-k-mooneybauzas: but it would not pass ci10:50
sean-k-mooneyso it wont get merged at least10:50
bauzasfortunately, in this specific case, agreed, CI won't run10:50
stephenfinFortunately, as sean-k-mooney points out, this will raise a SyntaxError on python 2.710:50
sean-k-mooneybut they might not know why10:50
stephenfinheh, yeah 0:)10:50
bauzasthis10:51
stephenfinhow a contributor guide change?10:51
bauzashonestly, I don't want to bikeshed10:51
stephenfin*about10:51
bauzasyou know what ? I'll just approve the change10:51
stephenfinDo we have a backporting section in that?10:51
bauzasand then people who backport should just see my comment in the review10:51
stephenfin\o/ WFM too :)10:51
bauzasif they don't, then I'll kill them10:52
bauzasseriously10:52
bauzasstephenfin: but for a second, we unnecesseraly added complexity to the existing code by adding a linter check10:52
*** tkajinam has quit IRC10:53
bauzasI could have -1d it by saying 'sorry dude, unrelated to the change'10:53
bauzasstephenfin: so, please refrain yourself to add more than what's necessary ;) :D10:53
stephenfinooooorrr, we're reducing complexity by removing the need to worry about types10:53
sean-k-mooneybauzas: i could argure the opiste10:53
stephenfinlet the compute do the work for you10:54
sean-k-mooneyif you dont add it and added it in a seperate change that is adding uneesisary overhead in revew10:54
stephenfin*computer10:54
stephenfinagreed10:54
stephenfinif I wasn't changing the function signature, this would be unrelated10:54
stephenfinbut because I am, this is a fair change10:54
sean-k-mooneyanyway stephen are you going to chekc the hugepage/file backed memeory thing or will i doit10:54
stephenfinsean-k-mooney: If you've time, go for it. I'm going to lunch shortly as I'm in meetings most of this afternoon :(10:55
stephenfinIf not, I'll aim to do it before EOD10:55
sean-k-mooneywell i want to understand this so that i can figure out how this relates to numa in placmenet10:55
sean-k-mooneyso ill try and doit shortly10:56
sean-k-mooneyfile backed memroy will have to be reported on the ROOT RP10:57
sean-k-mooneysince it has no real numa affintiy10:57
gibiI think we can trust the stable cores to see if a code is not py2 compatible10:59
*** lpetrut has joined #openstack-nova10:59
sean-k-mooneythe fact that we are not using six anymore will liekly cause more issue then type hints11:00
gibialso if there is such code that valid for py2 and py3 but behaves differently, then during the master review we have to make sure we add enough unit test coverage that will break when the patch is blindy backported to py211:00
*** dkehn has quit IRC11:00
sean-k-mooneyyep11:00
gibiin this particular case the interpreter catches the problem11:01
bauzasgibi: sean-k-mooney: what I'm saying is that we somehow opted into thinking more about what we write and what we merge on master now that the ship has sailed11:01
bauzasthat's it.11:01
sean-k-mooneylist vs iterator/view will be one of the main one for like dict.keys()11:01
stephenfinand unicode/bytes11:02
bauzaspreviously, we had no brain knobs to do as we were supporting boh11:02
sean-k-mooneyin that case its not as bad11:02
bauzasboth*11:02
sean-k-mooneyas we are sticter in py311:02
sean-k-mooneybut yes11:02
gibibauzas: sure, we should be aware, but at the same time we should not limit ourselves to write better code on master11:02
bauzasI don't disagree11:02
bauzasI'm just saying we need to ponderate the will of writing nice code with the pragmatism of running such code on different stable releases11:03
bauzasand from someone who sometimes has to backport things down to Newton, I'm thinking about my job for the next 3 years11:03
bauzasif I can ease myself, I'll certainly do11:04
sean-k-mooneystephenfin: so looking at http://paste.openstack.org/show/794558/11:06
sean-k-mooneystephenfin: i think we are good on the numa front11:06
sean-k-mooneystephenfin: this is the relevent virsh output http://paste.openstack.org/show/794560/11:09
sean-k-mooneyso libvirt sees the hugepage i have allocated but we are not reporting any hugepages in the host numa_toplogy blob11:09
sean-k-mooneygibi: by the way inital_ram_allocation_ratio still default to 1.5 :( i think we just changed it to 1 in ooo11:11
sean-k-mooneywe said we chagned it to 1.0 in the ptg but we did not11:12
gibisean-k-mooney: yeah, we mentioned 1.0 but I don't remember the context11:12
gibiI do know that the product I helping downstream set it 1.0 directly since Icehose or Mitaka11:13
sean-k-mooneyya and windriver did too11:13
sean-k-mooneymaybe we should actully chage the upstream default to 1 but we would have to be very vocal and proably add an upgrade check if we did11:13
sean-k-mooney16 for our cpus is also nuts as a defalt. anything over about 4 tends to cause issue when the system is loaded11:15
gibisean-k-mooney: agree about vocalization, but I don't think we should spend too much effort changing this default.11:15
sean-k-mooneychaning initalil_allcoation_raitio actully might be safe as it only matter for new installs11:15
*** threestrands has quit IRC11:16
sean-k-mooneygibi: well i think we change it downstream in our product, you change it in yours and windriver and i think mirantis did in theres11:16
sean-k-mooneyso if everyone changes the default its proably a bad default11:16
sean-k-mooneygibi: but ya we dont need to spend time on it now11:17
sean-k-mooneyi jsut wanted to correct myself11:17
gibiack, thanks for the correction11:17
*** links has joined #openstack-nova11:26
*** jraju__ has quit IRC11:28
*** raildo has joined #openstack-nova11:37
*** zigo has quit IRC11:41
aarentsHi nova,11:42
aarentsbauzas: gibi FYI, As per new element given during PTG regarding my issue https://bugs.launchpad.net/nova/+bug/1874032 , I confirm that offload snapshot upload in a native thread fix it11:42
openstackLaunchpad bug 1874032 in OpenStack Compute (nova) "nova-compute become stuck when doing IO on busy file system" [Wishlist,In progress] - Assigned to Alexandre arents (aarents)11:42
aarents(i'm no more able to get nova-compute hang if file system is busy)11:42
sean-k-mooneystephenfin: actully im going to restart libvirt and test that agian11:45
*** rcernin_ has joined #openstack-nova11:48
aarentsso I propose some thing here: https://review.opendev.org/#/c/734776/1 dansmith was planning to think about it during PTG11:48
*** bbowen_ has joined #openstack-nova11:52
*** rcernin_ has quit IRC11:53
*** bbowen has quit IRC11:53
*** zigo has joined #openstack-nova11:56
*** bbowen_ has quit IRC11:57
*** bbowen_ has joined #openstack-nova11:57
*** lvdombrkr has quit IRC12:04
*** rpittau|bbl is now known as rpittau12:05
*** derekh has quit IRC12:06
*** derekh has joined #openstack-nova12:06
*** ttsiouts_ has quit IRC12:08
*** derekh has quit IRC12:12
*** derekh has joined #openstack-nova12:12
*** raildo has quit IRC12:14
*** raildo has joined #openstack-nova12:14
sean-k-mooneyaarents: right but didnt we agree not to do that and instead just use a new sepmaphore12:15
sean-k-mooneywe have https://github.com/openstack/nova/blob/e954a0569785c941ccb89d31c7b4b847b15b5fc5/doc/source/reference/threading.rst which documents nova threading model12:17
*** bbowen_ has quit IRC12:17
sean-k-mooneythere are a few cases where we have to use explcit treading but we avoid it unless absolutly required12:18
*** bbowen has joined #openstack-nova12:18
*** ravsingh has quit IRC12:20
*** derekh has quit IRC12:24
*** derekh has joined #openstack-nova12:24
aarentssean-k-mooney: thanks for the helpfull link, by new semaphore you mean you mean something limiting max concurrent snapshot ?12:25
sean-k-mooneyyes12:26
sean-k-mooneywe have a config option to limit the max builds on a host12:26
sean-k-mooneyone of the suggestions was to add one for snapshot12:26
sean-k-mooneyaarents: just looking at the eventlet docs12:27
sean-k-mooneyhttps://eventlet.net/doc/threading.html#eventlet.tpool.execute12:27
sean-k-mooneyso it looks like this will still be a blocking call12:27
sean-k-mooneybut it yeild the current greenlet ?12:27
sean-k-mooneye.g. will that internally invoke the function on a native thread12:28
sean-k-mooneyyeild12:28
*** ratailor has quit IRC12:28
sean-k-mooneythen call thread.join at some later point12:28
aarentsI understand more like that: coroutine delegate to native thread (block just waiting native thread finish, but in the maintime yeild to other coroutine always)12:30
*** ttsiouts has joined #openstack-nova12:32
*** ttsiouts has quit IRC12:32
*** ttsiouts has joined #openstack-nova12:32
sean-k-mooneyaarents: if that is how it works then it would be ok but the docs are not clear12:32
*** nweinber has joined #openstack-nova12:32
sean-k-mooneyoh i missed the prelude12:32
sean-k-mooneyThe simplest thing to do with tpool is to execute() a function with it. The function will be run in a random thread in the pool, while the calling coroutine blocks on its completion:12:32
aarentsyep12:34
aarentssean-k-mooney: according the nova doc you share, I'm precisely in case "Yielding the thread in long-running tasks" but my issue is: I can't put smart greenthread.sleep(0) call because IO are in glance.client12:34
sean-k-mooneyaarents: no that is for internal cases12:35
sean-k-mooneynot external io12:35
aarentsk12:35
sean-k-mooneyif we are computing something expensive we are ment to addd sleeps to yeild12:35
aarentsyes, aggree12:36
*** amodi has joined #openstack-nova12:37
sean-k-mooneyaarents: ok left my toughts in the patch. i would proably be ok with that change if we had the config option to limit the number in parralle12:42
stephenfinbauzas: Last ask for the day, I promise, but could you also take a shot at https://review.opendev.org/#/c/728505/ ? It's a re-approval, if that helps12:43
aarentssean-k-mooney: thanks12:43
stephenfinIf you want, will trade for review of your spec :-P12:44
*** damien_r has quit IRC12:49
*** martinkennelly has quit IRC12:50
*** martinkennelly has joined #openstack-nova12:50
*** damien_r has joined #openstack-nova12:52
openstackgerritMerged openstack/nova-specs master: spec update: virtual-persistent-memory  https://review.opendev.org/72628412:52
*** udesale_ has joined #openstack-nova12:54
*** ociuhandu has joined #openstack-nova12:56
*** damien_r has quit IRC12:56
*** udesale has quit IRC12:57
*** eharney has joined #openstack-nova12:57
*** avolkov_ has joined #openstack-nova12:57
*** martinkennelly has quit IRC13:00
*** avolkov has quit IRC13:01
*** rajinir has quit IRC13:01
*** avolkov_ is now known as avolkov13:01
*** ociuhandu has quit IRC13:02
*** rajinir has joined #openstack-nova13:04
bauzasstephenfin: heh no worries13:05
*** ravsingh has joined #openstack-nova13:07
*** ociuhandu has joined #openstack-nova13:09
*** ociuhandu has quit IRC13:11
*** Luzi has quit IRC13:12
*** ociuhandu has joined #openstack-nova13:12
*** lbragstad_ has joined #openstack-nova13:12
aarentssean-k-mooney: dansmith thks, I replied https://review.opendev.org/#/c/734776/113:28
*** ratailor has joined #openstack-nova13:30
sean-k-mooneyaarents: i was thinking more like 4 but 10 might be fine too13:32
sean-k-mooneywhat is the default build limit13:32
sean-k-mooneyah that is 1013:32
*** mriedem has joined #openstack-nova13:32
sean-k-mooneyya so 10 would be fine13:33
aarentsok13:34
dansmith10 seems like a lot to me13:38
dansmithwell, depends on where the bottleneck is I guess13:39
sean-k-mooneyya that is why i was thinking 4 but we consider 10 ok for max_concurrent_builds13:39
sean-k-mooneymaybe it should default to the value of max_concurrent_builds if its not set13:39
sean-k-mooneyto keep them the same13:39
sean-k-mooneywe have done that with some of the periodic intervals13:40
*** ociuhandu has quit IRC13:42
*** ratailor has quit IRC13:42
aarentssean-k-mooney currently we live without limit by defaut, the new idea is to not exhaust thread pool, in that case 10 is fine but we can align with other parameter why not13:46
sean-k-mooneyaarents: well we live without a limit becasue its all in one thread13:46
aarentsk13:47
*** jawad_axd has quit IRC13:47
sean-k-mooneyupdate the patch and either have the default depend on the other config value or select a defalut and we can review that then13:48
openstackgerritDan Smith proposed openstack/nova master: DNM: Try to make a glance multistore job  https://review.opendev.org/73418413:48
aarentssean-k-mooney: ok13:50
sean-k-mooneyif we see Lazy-loading 'pci_devices' on Instance ... mesages on the compute node during spwan is that a bad thing?13:57
*** brinzhang0 has quit IRC13:57
*** Liang__ has joined #openstack-nova13:57
sean-k-mooneyor more is that expected or should we have all the info in the build request?13:57
*** ociuhandu has joined #openstack-nova13:58
*** Liang__ is now known as LiangFang14:00
*** martinkennelly has joined #openstack-nova14:03
*** ociuhandu has quit IRC14:03
*** dklyle has joined #openstack-nova14:03
*** ociuhandu has joined #openstack-nova14:05
*** dkehn has joined #openstack-nova14:08
*** udesale_ has quit IRC14:10
*** ccamacho has quit IRC14:11
dansmithsean-k-mooney: it means something tried to read that field on the instance.. if we're doing that based on something in the request, then it's probably good to lazy-load it, so we're not always passing it regardless of whether or not pci is used14:17
dansmithif we're always looking at that regardless, then the lazy load is just a perf hit and we should pre-join it14:17
sean-k-mooneythis was just before the xml was generated for an instance with no pci requetss or numa policy set14:18
sean-k-mooneyi might take a look at why its doing that in a bit14:19
sean-k-mooneyim currently testing file backed memroy14:19
dansmithin that case, we could either be smarter about when we look at that field to avoid the lazy-load, or we should just pre-join it14:19
*** sapd1 has quit IRC14:20
sean-k-mooneyalex_xu: https://review.opendev.org/#/c/734658/4/doc/source/admin/file-backed-memory.rst@70 i added info about the numa and hugepage behavior14:25
sean-k-mooneynuma more or less works although the numa toplogy filter will be looking at the host ram when considering numa affinity not the file backed memory14:26
sean-k-mooneyi think i a werid way that is actully the correct thing to do14:26
sean-k-mooneyas it will not allow a guests virtual numa node to be large then a hosts numa node14:27
*** LiangFang has quit IRC14:28
sean-k-mooneylibvirt is also passing the correct numa affinity hints to qemu for the files too14:28
*** Liang__ has joined #openstack-nova14:29
sean-k-mooneyso the things we could fix are hugepages, and how the local_GB is reported. both of which could be done via existing config options14:29
sean-k-mooneyso we can just have one more pathc to document it. in the long run we might want to adress this diffrently. we dont need a code change to do the write thing but i think we should warn when we detect you have not set the config options correctly as the current patch does14:31
*** Liang__ is now known as LiangFang14:33
*** links has quit IRC14:35
openstackgerritAlexandre Arents proposed openstack/nova master: Snapshot: offload glance upload in a native thread  https://review.opendev.org/73477614:40
*** liuyulong has joined #openstack-nova14:41
*** mlavalle has joined #openstack-nova14:47
*** LiangFang has quit IRC14:47
*** LiangFang has joined #openstack-nova14:48
*** ociuhandu has quit IRC14:50
*** ccamacho has joined #openstack-nova14:54
*** mandre has joined #openstack-nova14:55
*** jmlowe has quit IRC14:58
*** priteau has joined #openstack-nova14:58
stephenfinCan anyone say why we include "cherry-picked from" lines in stable? They seem like a waste of time, particularly when you've to make changes to the backport15:02
stephenfinand Gerrit already does the linking based on change ID15:02
*** JamesBenson has joined #openstack-nova15:03
sean-k-mooneyconvention15:04
sean-k-mooneybut other then that its not really neeed15:04
sean-k-mooneyalso if you do it via gerrit it does it differrently15:04
sean-k-mooneye.g. it only add the first one15:05
sean-k-mooneyunless you do the backport on by one i think15:05
stephenfinLooks like it's to work around a Gerrit bug that has since been fixed https://docs.openstack.org/project-team-guide/stable-branches.html15:05
stephenfincherry-pick -x option includes ‘cherry-picked from …’ line in the commit message which is required to avoid Gerrit bug15:05
stephenfinwhich points to https://code.google.com/p/gerrit/issues/detail?id=110715:05
sean-k-mooneyits not required by any of our tooling15:05
stephenfinnope15:05
sean-k-mooneyupstream or downstrema15:06
stephenfinI propose we stop doing it. It's annoying and often wrong15:06
stephenfinWill bring up in the next team meeting15:06
sean-k-mooneyso use -X15:06
sean-k-mooneyinstead of -x15:06
openstackgerritMerged openstack/nova-specs master: Encrypted Emulated Virtual TPM  https://review.opendev.org/72850515:08
stephenfinsean-k-mooney: What would -X do? the man page says something about merge strategy15:09
sean-k-mooneygit-review -x add the cherry picked line -X does not15:09
*** lpetrut has quit IRC15:09
sean-k-mooneyoh sorry its the other way around15:10
sean-k-mooney-X adds it and -x does not15:10
stephenfinI don't think the -X is related, actually15:10
stephenfinReading the docs15:10
sean-k-mooneyso if you backporting using git review15:10
stephenfinyou won't get the line unless you specify -x15:10
sean-k-mooneythe workflow is checkout stable/whatever15:10
sean-k-mooneythen do git review -X15:11
stephenfinahhhh15:11
sean-k-mooneyto add the cherry picked lins15:11
stephenfinI just use git-cherrypick15:11
*** dustinc has joined #openstack-nova15:11
sean-k-mooneybut if you do -x it does not add them15:11
*** jmlowe has joined #openstack-nova15:11
sean-k-mooneyya i was talkingbaout the arge for git review15:11
dansmithI guess I'm confused.. why is it not helpful? When I'm browsing history at the command line, it's helpful.. otherwise I have to go into gerrit by change-id to find the siblings15:11
sean-k-mooneynot git cherry-pick15:11
sean-k-mooneydansmith: im assuming stephne it ac case where it was wrong15:12
dansmithwhen is it ever wrong? I can't think of a case.15:12
melwittmost of the time, I like the cherry picked lines because it lets me easily see if the changes were picked from N branch to N - 1 branch. but agreed it's a pain when you have to update one15:12
sean-k-mooneywhen people do it manually and get it wrong15:12
sean-k-mooneyi honestly dont mind either way to be honest15:12
stephenfindansmith: in general they're correct, but things break if you've to make any modification to an earlier patch15:13
sean-k-mooneythe only thing i find annoying is that gerrit does not do it the way we want15:13
dansmithit also helps me see how far something was backported.. like if I'm looking at something on stein and it has N backport lines, I know that came from stein+N15:13
* stephenfin tends to use 'git log --grep=CHANGE_ID' to find patches on different branches15:14
sean-k-mooneystephenfin: maybe try using git review for backport for a while15:14
stephenfinTrue, but you have that information in the cherry picks box on the right15:14
stephenfinin the UI, that is15:14
dansmithnot in the command line tho15:14
dansmithright15:14
stephenfinfair point15:15
stephenfinsean-k-mooney: in general, there's no issue. I just use 'git cherry-pick -x'15:15
stephenfinbut I've been bitten a few times now where I had a stack of stable changes and had to make a tweak to a single patch higher up15:16
stephenfinso you've add the missing mock or the typo in your commit message or whatever else you missed15:16
stephenfinand then you've to go update the cherry-picked lines in every backported patch plus any patch on top in each branch. not fun :)15:17
stephenfinit'd be nice if it was optional15:17
stephenfinas something that's nice-to-have but not really necessary, particularly if it incurs pain15:18
stephenfin*when it incurs pain15:18
dansmithwell, my vote is that it's worthwhile bookkeeping15:21
stephenfinDefinitely worthwhile but not essential. I'd like to be able to loosen the cuffs on the occasion they start hurting15:22
elodif i'm not mistaken, then gerrit adds the cherry-picked lines correctly, iff the original patch has merged. if the patch is not merged yet, it does not add the cherry-picked line, for logical reasons, as it might not be the one that gets merged15:24
stephenfinelod: Ah, so that's how it makes the decision :) Can't confirm but makes sense15:25
stephenfinWaiting for a patch series to land on stable/X before backporting to the stable/X-1 etc. is less than optional though. It causes unnecessary context switching for both submitter and reviewer, assuming the submitter even remembers to keep backporting things15:26
elodthat's true, we had the same discussion in our team :]15:27
stephenfinHa! I'm about to discuss it downstream too 😇15:27
dansmithI'd much prefer to have the bookkeeping right and I think it's very unusual that backports to N releases are that urgent15:27
*** liuyulong has quit IRC15:28
elodotherwise, if a patch needs to be fixed, then all its backports need to be fixed, so that's another extra burden. so there are two sides15:28
*** LiangFang has quit IRC15:28
elodif we stick to policy and do the backporting branch-by-branch, when a patch has merged, then this is not an issue, though15:29
stephenfindansmith: so not including the cherry-picked from line would be very unusual too15:29
stephenfinit'd be exceptional, not the norm15:29
stephenfinelod: yes and no. It really depends on the nature of the change to the higher up patch15:31
*** martinkennelly has quit IRC15:31
stephenfinConsider that series I reviewed from lyarwood yesterday. The extra 'cherry-picked from' line was something that affected all commit messages15:32
stephenfinbut there were other issues that were specific to certain backports like the 'Conflicts' and 'NOTE' sections being the wrong way round15:32
stephenfinit's not black and white15:33
stephenfinanyway, I've made my point :) now to forget about it until next time I hit this15:34
*** yoctozepto has quit IRC15:34
*** yoctozepto has joined #openstack-nova15:34
elodif the editing of a 'middle' patch is allowed, then that could be a source of an inproper backport. i mean most of the time it's not a problem, but sometimes we forget to backport some new changes15:35
elodthe cherry-picked line is good to identify where the backport is coming from15:36
elodand as dansmith said, it's good to see how many previous backports there are15:37
elodbut yes, if we want to backport to multiple branches at the same time, it could be painful :)15:38
stephenfinyup, all fair points15:39
stephenfinit'd just be nice have the optional, is all15:39
stephenfin*the option15:39
*** jaosorior has joined #openstack-nova15:40
*** ociuhandu has joined #openstack-nova15:50
openstackgerritDan Smith proposed openstack/nova master: DNM: Try to make a glance multistore job  https://review.opendev.org/73418415:53
*** gyee has joined #openstack-nova15:54
*** hamalq has joined #openstack-nova16:05
*** rpittau is now known as rpittau|afk16:07
*** hamalq_ has joined #openstack-nova16:08
*** sapd1 has joined #openstack-nova16:08
*** hamalq has quit IRC16:11
openstackgerritJiri Suchomel proposed openstack/nova master: Add ability to download Glance images into the libvirt image cache via RBD  https://review.opendev.org/57430116:13
stephenfinsean-k-mooney: your cherry-picked from lines are wrong in this https://review.opendev.org/#/c/728057/16:16
sean-k-mooneythey may be yes16:19
sean-k-mooneyi did it via the gerrit ui16:19
openstackgerritStephen Finucane proposed openstack/nova stable/train: Silence amqp heartbeat warning  https://review.opendev.org/72805716:23
mandrehi, quick question regarding the hw_scsi_model and hw_disk_bus glance image annotations. Did nova always had support for them? and if we specify a virt driver that the hypervison doesn't support, does it fallback to the default driver?16:23
mandreContext is, I'm wondering if it's safe to set the hw_scsi_model=virtio-scsi and hw_disk_bus=scsi annotations for my images, not knowing what the environment will be.16:24
sean-k-mooneymandre: yes well for several years16:25
sean-k-mooneyit predates icehouse16:25
sean-k-mooneymandre: technically you could detect it via the glance metadta api16:26
sean-k-mooneybut if the could cupport nova v2 api it also support them16:26
sean-k-mooneymandre the issue is that the values are virt driver dependnet16:26
sean-k-mooneyso if you dont know what hyperviror your cloud is using you don tknow what value are vaild16:27
sean-k-mooneyif you know that its libvirt then those values will work16:27
mandrecool, so that answers the first part of the question, we're not deploying on anything that is older that queens I think16:27
sean-k-mooneyas of ussuri maybe train we also report the support models to placment as traits16:28
sean-k-mooneyjust an fyi but plamcnet is an admin only api normally so that may or may not be helpful to you16:28
mandreright, we won't be able to use placement because we need to deploy as tenant16:29
sean-k-mooneyya so if you know its libvirt then as i siad those values will work16:31
mandreis there a way to progmatically discover the hypervisor as a tenant?16:31
sean-k-mooneyno16:31
sean-k-mooneyand that is intentional16:31
sean-k-mooneyas an admin yes16:31
sean-k-mooneyvia the hyperviors api16:31
mandrefair enough, just checking :)16:32
openstackgerritStephen Finucane proposed openstack/nova stable/stein: libvirt: avoid cpu check at s390x arch  https://review.opendev.org/70152616:32
*** boxiang has quit IRC16:32
sean-k-mooneymandre: you can boot a vm and then you can kind fo tell form inside the vm16:33
*** boxiang has joined #openstack-nova16:33
mandreso if I set a driver via hw_scsi_model that the hypervisor doesn't support, it won't be able to boot the VM? or is there a fallback mechanism?16:34
sean-k-mooneyif you set it and its not supported it wont boot16:34
sean-k-mooneybecause we could not fullfile your request16:35
mandreOK16:35
*** ravsingh has quit IRC16:36
sean-k-mooneymandre: if you boot a vm with a default image and run lscpi like this http://paste.openstack.org/show/794593/16:37
sean-k-mooneyand you see 00:02.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port for example16:37
sean-k-mooneyyou basically know it either libvirt/kvm or xen16:37
openstackgerritStephen Finucane proposed openstack/nova stable/stein: Create instance action when burying in cell0  https://review.opendev.org/72953116:37
sean-k-mooneyyou can also infer the hypervior in other ways16:38
mandresean-k-mooney: thanks for the help16:39
sean-k-mooneyhyperv and vmware all have similr things you can look for16:39
sean-k-mooneyif you run lspci on hyperv for example it will almsot be empty16:40
sean-k-mooneythere nics and disk dont show up as pci device in the normal way16:40
sean-k-mooneyin vmware the nic model will be a special vmware one by defualt at least16:40
*** martinkennelly has joined #openstack-nova16:41
sean-k-mooneymandre: so if you are enruling you applcaiton on a generic cloud that is one way to figure it out.16:41
openstackgerritStephen Finucane proposed openstack/nova stable/stein: Add admin doc information about image cache resource accounting  https://review.opendev.org/73254216:42
*** gyee has quit IRC16:42
mandresean-k-mooney: IIUC as a tenant there is no other way than spinning a VM to guess the hypervisor, so we may refrain from adding the image annotations since we won't know the environment in advance16:45
sean-k-mooneywell we are discussing worlad onboarding or VNF onboaridng right16:46
sean-k-mooneyi assume you are a vendor of a product that runs or can run on openstack16:46
*** ociuhandu has quit IRC16:46
sean-k-mooneyif so you have a few options the first is to document your miniurm and recommended setting when onboarnidng your applcation16:47
sean-k-mooneyif you atomate that you can add a config or do auto detection16:47
sean-k-mooneybut its likely that you will have implcit depenencies in your applcation that will only work on some hypervieors so targeting 1 or a limites set will roably be requried jsut from a  vlaidation perspective16:48
sean-k-mooneymost openstack cloud usei libvirt/kvm16:48
sean-k-mooneyand all that use libvirt/kvm will support those options16:49
sean-k-mooneyif you plan to also support vmware, powervm or hyperv then  you have to explore one of the other options16:49
mandreok, that's good info.16:49
sean-k-mooneye.g. confg or docs16:49
mandrethis is for the openshift installer on openstack platforms, so there's a good chance the hypervisor will be libvirt/kvm. If using vmware or hyperv, it's likely they'll deploy directly on vsphere or azure.16:52
*** grandchild has joined #openstack-nova16:53
*** nightmare_unreal has quit IRC16:58
*** derekh has quit IRC17:00
*** priteau has quit IRC17:01
*** gyee has joined #openstack-nova17:08
*** dtantsur is now known as dtantsur|afk17:10
*** sapd1 has quit IRC17:12
openstackgerritMerged openstack/nova master: Add reproducer for bug #1881455  https://review.opendev.org/73366717:16
openstackbug 1881455 in OpenStack Compute (nova) "migrate server reporting list index out of bound" [Undecided,In progress] https://launchpad.net/bugs/1881455 - Assigned to Stephen Finucane (stephenfinucane)17:16
openstackgerritMerged openstack/nova master: Use 'Exception.__traceback__' for versioned notifications  https://review.opendev.org/73366817:17
openstackgerritMerged openstack/nova stable/ussuri: libvirt: Don't delete disks on shared storage during evacuate  https://review.opendev.org/73124817:17
openstackgerritStephen Finucane proposed openstack/nova stable/rocky: Remove 'test_cold_migrate_with_physnet_fails' test  https://review.opendev.org/70311517:17
openstackgerritStephen Finucane proposed openstack/nova stable/rocky: Block rebuild when NUMA topology changed  https://review.opendev.org/70311617:17
openstackgerritStephen Finucane proposed openstack/nova stable/rocky: Disable NUMATopologyFilter on rebuild  https://review.opendev.org/70311717:17
openstackgerritStephen Finucane proposed openstack/nova stable/rocky: FUP for in-place numa rebuild  https://review.opendev.org/70311817:17
stephenfinsean-k-mooney: addressed some nits from elod on that btw ^ Figure we still want it to land17:24
openstackgerritStephen Finucane proposed openstack/nova master: Remove unnecessary retrieval of Migration object  https://review.opendev.org/73035117:27
openstackgerritStephen Finucane proposed openstack/nova master: Remove unused function parameters  https://review.opendev.org/73035217:27
*** tesseract-RH has quit IRC17:32
*** rouk has joined #openstack-nova17:38
elodthanks stephenfin for the many stable reviews and patch updates :)17:41
stephenfinnp :)17:42
*** ociuhandu has joined #openstack-nova17:43
*** tbachman has quit IRC17:45
*** ociuhandu has quit IRC17:48
*** tbachman has joined #openstack-nova18:08
*** vishalmanchanda has quit IRC18:08
*** mlavalle has quit IRC18:22
*** lvdombrkr has joined #openstack-nova18:41
openstackgerritMerged openstack/nova stable/ussuri: compute: Allow snapshots to be created from PAUSED volume backed instances  https://review.opendev.org/72917418:45
openstackgerritMerged openstack/nova stable/ussuri: Remove stale nested backport from InstancePCIRequests  https://review.opendev.org/72593118:45
*** lbragstad_ is now known as lbragstad18:45
*** bbowen has quit IRC19:07
*** lvdombrkr has quit IRC19:13
*** hongbin has joined #openstack-nova19:18
*** ralonsoh has quit IRC19:20
*** jmlowe has quit IRC19:43
*** jsuchome has quit IRC19:44
*** jmlowe has joined #openstack-nova19:45
*** maciejjozefczyk has quit IRC19:46
*** jmlowe has quit IRC19:48
*** hongbin has quit IRC19:55
*** bbowen has joined #openstack-nova20:21
*** bbowen has quit IRC20:30
*** bbowen has joined #openstack-nova20:31
*** nweinber has quit IRC20:34
*** jdillaman has joined #openstack-nova20:36
*** ociuhandu has joined #openstack-nova20:48
*** ociuhandu has quit IRC20:53
*** bbowen has quit IRC20:55
*** bbowen has joined #openstack-nova20:56
*** spatel has joined #openstack-nova21:03
*** bbowen_ has joined #openstack-nova21:06
*** bbowen has quit IRC21:07
*** raildo has quit IRC21:14
*** bbowen_ has quit IRC21:15
*** bbowen_ has joined #openstack-nova21:16
*** jdillaman has quit IRC21:22
*** bbowen_ has quit IRC21:22
*** bbowen_ has joined #openstack-nova21:22
*** mlavalle has joined #openstack-nova21:29
*** spatel has quit IRC21:32
*** bbowen__ has joined #openstack-nova21:32
*** bbowen_ has quit IRC21:34
*** bbowen has joined #openstack-nova21:35
*** bbowen has quit IRC21:37
*** bbowen__ has quit IRC21:38
*** bbowen has joined #openstack-nova21:38
*** bbowen has quit IRC21:48
*** bbowen has joined #openstack-nova21:48
*** martinkennelly has quit IRC21:48
*** bbowen has quit IRC21:50
*** bbowen_ has joined #openstack-nova21:50
*** threestrands has joined #openstack-nova21:55
*** spatel has joined #openstack-nova21:56
*** mriedem has left #openstack-nova21:58
*** rcernin_ has joined #openstack-nova21:59
*** bbowen_ has quit IRC22:01
*** bbowen__ has joined #openstack-nova22:01
*** avolkov has quit IRC22:01
*** rcernin_ has quit IRC22:04
*** rcernin has joined #openstack-nova22:04
*** rcernin is now known as rcernin|brekkie22:05
*** bbowen__ has quit IRC22:07
*** bbowen_ has joined #openstack-nova22:07
*** bbowen_ has quit IRC22:17
*** bbowen has joined #openstack-nova22:17
*** rcernin|brekkie has quit IRC22:19
*** bbowen has quit IRC22:21
*** grandchild has quit IRC22:23
*** bbowen has joined #openstack-nova22:23
*** bbowen has quit IRC22:27
*** bbowen has joined #openstack-nova22:27
*** bbowen has quit IRC22:30
*** bbowen has joined #openstack-nova22:30
*** spatel has quit IRC22:34
*** bbowen has quit IRC22:43
*** ttsiouts has quit IRC22:43
*** tkajinam has joined #openstack-nova22:45
*** hongbin has joined #openstack-nova22:56
*** hongbin has quit IRC23:00
*** rcernin|brekkie has joined #openstack-nova23:09
*** rcernin|brekkie has quit IRC23:10
*** rcernin has joined #openstack-nova23:10
*** hongbin has joined #openstack-nova23:10
*** tosky has quit IRC23:15
*** lbragstad has quit IRC23:22
*** mlavalle has quit IRC23:32
*** tetsuro has joined #openstack-nova23:49

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