Wednesday, 2019-09-04

*** gyee has quit IRC00:21
*** altlogbot_1 has quit IRC00:23
*** irclogbot_3 has quit IRC00:23
*** edleafe has quit IRC00:24
*** takashin has joined #openstack-nova00:26
openstackgerritArtom Lifshitz proposed openstack/nova master: NUMA live migration support  https://review.opendev.org/63460600:27
openstackgerritArtom Lifshitz proposed openstack/nova master: Deprecate CONF.workarounds.enable_numa_live_migration  https://review.opendev.org/64002100:27
openstackgerritArtom Lifshitz proposed openstack/nova master: Functional tests for NUMA live migration  https://review.opendev.org/67259500:27
*** threestrands has quit IRC00:32
*** adriant7 has quit IRC00:32
*** adriant7 has joined #openstack-nova00:32
*** adriant7 has quit IRC00:32
*** markvoelker has joined #openstack-nova00:55
*** Sundar has joined #openstack-nova00:56
*** nicolasbock has quit IRC00:57
openstackgerritMerged openstack/nova master: re-calculate provider mapping during migration  https://review.opendev.org/65511201:00
*** markvoelker has quit IRC01:01
*** Roamer` has quit IRC01:09
*** igordc has quit IRC01:16
*** BjoernT has joined #openstack-nova01:19
*** adriant has joined #openstack-nova01:21
*** irclogbot_3 has joined #openstack-nova01:34
*** irclogbot_3 has quit IRC01:39
*** irclogbot_2 has joined #openstack-nova01:41
*** irclogbot_2 has quit IRC01:43
*** BjoernT_ has joined #openstack-nova01:54
*** BjoernT has quit IRC01:55
*** tetsuro has joined #openstack-nova01:56
*** gbarros has joined #openstack-nova02:29
*** gbarros has quit IRC02:33
*** gbarros has joined #openstack-nova02:35
openstackgerritArtom Lifshitz proposed openstack/nova master: NUMA live migration support  https://review.opendev.org/63460602:39
openstackgerritArtom Lifshitz proposed openstack/nova master: Deprecate CONF.workarounds.enable_numa_live_migration  https://review.opendev.org/64002102:39
openstackgerritArtom Lifshitz proposed openstack/nova master: Functional tests for NUMA live migration  https://review.opendev.org/67259502:39
*** spsurya has joined #openstack-nova02:44
*** irclogbot_0 has joined #openstack-nova02:54
*** BjoernT_ has quit IRC02:56
*** irclogbot_0 has quit IRC02:59
*** markvoelker has joined #openstack-nova03:01
*** markvoelker has quit IRC03:05
*** tetsuro has quit IRC03:15
*** irclogbot_2 has joined #openstack-nova03:34
*** irclogbot_2 has quit IRC03:39
*** mkrai has joined #openstack-nova03:49
*** larainema has joined #openstack-nova03:56
*** mvkr has joined #openstack-nova04:02
*** irclogbot_1 has joined #openstack-nova04:02
*** tetsuro has joined #openstack-nova04:04
*** irclogbot_1 has quit IRC04:07
*** ricolin_ has joined #openstack-nova04:08
*** tetsuro has quit IRC04:08
*** ricolin_ has quit IRC04:08
*** ricolin has joined #openstack-nova04:10
openstackgerritBrin Zhang proposed openstack/nova master: Add delete_on_termination to volume-attach API  https://review.opendev.org/67313304:15
*** gbarros has quit IRC04:18
*** udesale has joined #openstack-nova04:19
*** irclogbot_2 has joined #openstack-nova04:22
*** irclogbot_2 has quit IRC04:33
*** cfriesen has quit IRC04:35
*** bhagyashris has quit IRC04:37
*** Luzi has joined #openstack-nova05:00
*** cervigni has joined #openstack-nova05:10
cervigniHello, I have a dual socket server. Each cpu with two numa nodes. I would like to have the host to have a cpu overallocation of 2.0. At the same time I would like each flavor to stay bounded to its own numa node05:10
cervigniIs there a way to achieve that? This would mean 2x instances on each numa nodes05:10
cervigniI did not find a way to do that05:10
cervigniThis is because each of the CPU is connected on the pci-e bus on a GPU05:10
cervigniand i need to respect the numa nodes configuration05:11
*** Sundar has quit IRC05:20
*** irclogbot_2 has joined #openstack-nova05:21
*** Sundar has joined #openstack-nova05:21
*** irclogbot_2 has quit IRC05:25
*** rcernin_ has joined #openstack-nova05:31
*** rcernin has quit IRC05:33
openstackgerritDustin Cowles proposed openstack/nova master: Provider Config File: YAML file loading and schema validation  https://review.opendev.org/67334105:39
openstackgerritDustin Cowles proposed openstack/nova master: WIP: Provider Config File: Public method to retrieve custom resources  https://review.opendev.org/67602905:39
openstackgerritDustin Cowles proposed openstack/nova master: WIP: Provider Config File: Update provider tree with new custom resources  https://review.opendev.org/67652205:39
*** ivve has quit IRC05:46
*** ratailor has joined #openstack-nova06:07
*** ratailor has quit IRC06:07
*** ratailor has joined #openstack-nova06:08
*** ricolin_ has joined #openstack-nova06:15
*** udesale has quit IRC06:15
*** irclogbot_3 has joined #openstack-nova06:17
*** ricolin has quit IRC06:17
*** irclogbot_3 has quit IRC06:21
*** udesale has joined #openstack-nova06:22
*** ratailor has quit IRC06:24
*** irclogbot_0 has joined #openstack-nova06:25
*** irclogbot_0 has quit IRC06:29
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove unused methods  https://review.opendev.org/67991806:30
*** markvoelker has joined #openstack-nova06:34
*** markvoelker has quit IRC06:39
openstackgerritYongli He proposed openstack/python-novaclient master: Microversion 2.78 - show server topology  https://review.opendev.org/67079006:49
*** slaweq has joined #openstack-nova06:51
*** maciejjozefczyk has joined #openstack-nova06:54
*** markvoelker has joined #openstack-nova06:56
cervigniguys, could you help me find out if this is a bug before I submit something stupid on Launchpad?06:58
cervignihttps://pastebin.com/SfD63LgJ06:58
*** zbr has quit IRC06:58
cervigniit seems that a flavour configured as in the logs, continusly allocate cores only on the first numa node, instead of checking the actual cpus already allocated in that node06:59
*** markvoelker has quit IRC07:00
*** rcernin_ has quit IRC07:01
gibicervigni: do you want dedicated physical cpu cores for your servers?07:02
*** bbowen_ has joined #openstack-nova07:02
cervigniI need to do an overallocation of 2x but that does not go out of its own numa node07:03
cervignithe virsh vcpuinfo for first instance is correct, for the second one is correct, but from the third one should start allocating on another numa node, since there is not available RAM left on numa node 107:03
cervigniI don't know how it can allocate further vcpus on that numa node since there is no ram available07:04
*** bbowen has quit IRC07:04
* gibi looking at the ram side of the log07:04
cervignican I give you any more logs?07:05
gibicervigni: so you don't have memory overallocation configured07:05
cervignino07:05
cervignimemory allocation is 1.007:05
gibicervigni: and you have the NUMATopologyFilter configured for the scheduler07:07
cervigni/etc/nova/nova.conf:enabled_filters=RetryFilter,AvailabilityZoneFilter,CoreFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter,DifferentHostFilter,NUMATopologyFilter,AggregateInstanceExtraSpecsFilter,PciPassthroughFilter,AggregateMultiTenancyIsolation07:07
cervigniyes07:07
gibithen this feels like a bug, yes.07:08
cervigniI am using rocky07:08
cervignioh dear :(07:08
cervignishould the scheduler fill a first round of the four numa nodes before overallocating?07:08
*** ivve has joined #openstack-nova07:08
gibicervigni: I don't think so. If there is overallocation then the scheduler can overallocate before it fills the other numa nodes. The only rule is I know of that a server cannot overallocate against itself07:09
*** zbr has joined #openstack-nova07:10
*** ratailor has joined #openstack-nova07:10
cervigniok07:10
cervigniso I will report it as a bug07:10
cervigniThanks gibi07:10
cervigniI don't know if it relates of the VGPU side07:10
cervigniI hope not07:10
gibicervigni: could you reporduce the problem without the VGPU resource in the flavor?07:11
gibicervigni: thanks for reporting the bug07:11
cervigniI'll do it now07:11
*** toabctl has quit IRC07:11
cervignigibi exactly same issue without VGPU07:13
cervigniany idea if there is a workaround I can use while the problem is fixed?07:13
*** toabctl has joined #openstack-nova07:16
*** mdbooth_ has quit IRC07:19
gibiunfortunately you cannot control the numa allocation directly from the outside07:22
cervignihttps://bugs.launchpad.net/nova/+bug/184261607:22
openstackLaunchpad bug 1842616 in OpenStack Compute (nova) "NUMA vcpus not correctly allocated against numa regions" [Undecided,New]07:22
cervigniI put you in the watchlist as well gibi07:23
cervigniOk, for the moment I will leave no NUMA affinity, but with vgpus will be very messy07:23
cervigniGuess Stein will have the same issue?07:23
*** luksky has joined #openstack-nova07:26
gibiunfortunately I cannot try to reproduce it as I don't have numa + VGPU capable machine. I might get hold of a 2 numa nodes machine ...07:26
*** tetsuro has joined #openstack-nova07:26
gibianyhow thanks for the report07:26
cervigniVGPU is irrelevant it seems07:26
*** ratailor has quit IRC07:30
*** irclogbot_1 has joined #openstack-nova07:31
*** brinzhang has quit IRC07:32
*** brinzhang has joined #openstack-nova07:32
*** irclogbot_1 has quit IRC07:35
*** tetsuro has quit IRC07:38
*** Sundar has quit IRC07:38
*** brault has joined #openstack-nova07:41
*** pcaruana has joined #openstack-nova07:42
*** udesale has quit IRC07:42
*** udesale has joined #openstack-nova07:43
*** tetsuro has joined #openstack-nova07:46
*** irclogbot_1 has joined #openstack-nova07:51
*** irclogbot_1 has quit IRC07:53
*** ralonsoh has joined #openstack-nova07:55
*** ociuhandu has joined #openstack-nova07:57
*** ociuhandu has quit IRC07:59
*** ociuhandu has joined #openstack-nova08:00
kashyapaspiers: Catching up with the relevant conversation w/ Eric in the scrollback.08:01
openstackgerritBalazs Gibizer proposed openstack/nova master: update allocation in binding profile during migrate  https://review.opendev.org/65642208:04
*** yan0s has joined #openstack-nova08:04
openstackgerritBalazs Gibizer proposed openstack/nova master: prepare func test env for moving servers with bandwidth  https://review.opendev.org/65510908:06
*** tkajinam has quit IRC08:07
*** damien_r has joined #openstack-nova08:09
*** damien_r has quit IRC08:09
openstackgerritBalazs Gibizer proposed openstack/nova master: Func test for migrate server with ports having resource request  https://review.opendev.org/65511308:09
*** damien_r has joined #openstack-nova08:10
openstackgerritBalazs Gibizer proposed openstack/nova master: Make _rever_allocation nested allocation aware  https://review.opendev.org/67613808:12
openstackgerritBalazs Gibizer proposed openstack/nova master: Support reverting migration / resize with bandwidth  https://review.opendev.org/67614008:15
openstackgerritBalazs Gibizer proposed openstack/nova master: Func test for migrate re-schedule with bandwidth  https://review.opendev.org/67697208:18
*** Sundar has joined #openstack-nova08:18
openstackgerritBalazs Gibizer proposed openstack/nova master: Support migrating SRIOV port with bandwidth  https://review.opendev.org/67698008:20
*** irclogbot_2 has joined #openstack-nova08:23
openstackgerritBalazs Gibizer proposed openstack/nova master: Allow migrating server with port resource request  https://review.opendev.org/67149708:23
*** ricolin_ is now known as ricolin08:25
*** irclogbot_2 has quit IRC08:25
openstackgerritBalazs Gibizer proposed openstack/nova master: Do not query allocations twice in finish_revert_resize  https://review.opendev.org/67882708:26
SundarHi gibi, hoaw are you doing?08:27
openstackgerritBalazs Gibizer proposed openstack/nova master: Allow resizing server with port resource request  https://review.opendev.org/67901908:29
*** takashin has quit IRC08:31
openstackgerritAdrian Chiris proposed openstack/nova master: Revert "vif: Resolve a TODO and update another"  https://review.opendev.org/67577608:34
*** markvoelker has joined #openstack-nova08:36
*** derekh has joined #openstack-nova08:36
*** ratailor has joined #openstack-nova08:39
*** mkrai has quit IRC08:39
*** ratailor has quit IRC08:39
*** markvoelker has quit IRC08:40
SundarRe. Cyborg notifications, I noticed that, once Nova kicks off the binding of ARQs, the CYborg event comes almost immediately if no programming is involved. The event gets lost because there are no waiters: I am doing the wait in the virt driver during spawn, The logs are here: http://paste.openstack.org/show/770470/08:40
*** ratailor has joined #openstack-nova08:40
openstackgerritLiang Fang proposed openstack/nova master: [WIP] Leverage openCAS cache framework for VM disks  https://review.opendev.org/66354208:42
Sundargibi: ^ I am proposing to move the create/bind ARQs from build_and_run_instance (https://review.opendev.org/#/c/631244/37/nova/compute/manager.py@1940) to _build_resources (https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2392).08:43
Sundargibi: This has 2 benefits: (a) The instance has th right host and hostname after resource claim, and (b) if VM spawn fails, there is a good place to delete the ARQs in flight.08:44
*** priteau has joined #openstack-nova08:45
SundarThe problem I am facing is this: can the logic be like http://paste.openstack.org/show/770481/? If non-ARQ-related stuff is not under the with, then the with statement is going to just kick off the binding and then wait till the resolution happens. Nothing else is going on during the wait.08:47
*** tetsuro has quit IRC08:53
*** ociuhandu has quit IRC08:55
*** ratailor has quit IRC08:55
*** ociuhandu has joined #openstack-nova08:56
*** brault has quit IRC08:56
*** mdbooth has joined #openstack-nova08:58
*** ociuhandu has quit IRC09:00
*** trident has quit IRC09:01
*** shilpasd has joined #openstack-nova09:03
gibiSundar: on a call, I have to get back to you in 15 minutes09:04
*** irclogbot_2 has joined #openstack-nova09:09
*** trident has joined #openstack-nova09:10
openstackgerritBrin Zhang proposed openstack/nova master: Add delete_on_termination to volume-attach API  https://review.opendev.org/67313309:11
*** irclogbot_2 has quit IRC09:11
*** Roamer` has joined #openstack-nova09:16
*** slaweq has quit IRC09:16
gibiSundar: there is already a wait_for_instance_events call in nova.virt.libvirt.driver.LibvirtDriver._create_domain_and_network (called from spawn())09:18
gibiSundar: or you only want to wait for the cyborg specific event in _build_resources ?09:20
*** dtantsur|afk is now known as dtantsur09:22
gibiSundar: but yeah, the goal is that you kick of the binding and while you are waiting for the response let other things progress for the build up until the point where you really need the ARQs to be bound09:27
*** amrith has joined #openstack-nova09:27
*** amrith has left #openstack-nova09:28
gibiSundar: I might try to add the with wait_for_instance_events under with _build_resources call in https://github.com/openstack/nova/blob/cbaea3bd690c683e83a063acfa69919668eaa123/nova/compute/manager.py#L223309:30
gibiSundar: I'm not sure how the the two context manager would combine if you put the wait_for_instance call inside the _build_resources without trying09:32
*** slaweq has joined #openstack-nova09:33
*** ricolin has quit IRC09:34
*** ricolin has joined #openstack-nova09:35
kashyapHuh, this commit added the CPU instruction: https://opendev.org/openstack/nova/commit/866ca1468dfa35f319f520d0f7b93b2d0fe32f6209:36
kashyap(trait, i.e.)09:36
kashyapBut it does _not_ exist in os-traits yet :-(09:37
kashyapThere's no such trait as HW_CPU_X86_AVX512VNNI in 'os-traits'09:37
kashyapHmm, never mind ... there _is_ the trait, and it is merged: https://review.opendev.org/#/c/672888/1/os_traits/hw/cpu/x86/__init__.py09:39
*** cdent has joined #openstack-nova09:44
aspierssometimes I have to pip install the latest os-traits in my tox envs09:45
aspiersit's quicker than a --recreate09:45
gibiI guess tox did not pick up the os-traits >= 0.16.0 change in the requirements.txt09:46
gibithe nova master has it, maybe you need to rebase your patch09:46
*** kaliya has joined #openstack-nova09:47
aspierstox doesn't seem good at noticing when to update anyway09:47
aspiersIME at least09:47
*** shilpasd has quit IRC09:47
*** kaliya has quit IRC09:51
*** shilpasd has joined #openstack-nova10:07
openstackgerritBrin Zhang proposed openstack/python-novaclient master: Microversion 2.78: Add delete_on_termination to volume-attach API  https://review.opendev.org/67348510:09
kashyapaspiers: Yeah, I see what you mean; what I found was that in my venv:10:14
kashyap>>> import os_traits10:14
kashyap>>> print os_traits.HW_CPU_X86_AVX512VNNI10:14
kashyapHW_CPU_X86_AVX512VNNI10:14
kashyap(I _think_ I manually 'pip'-installed os-traits in there, I guess.  I already forget)10:14
*** irclogbot_0 has joined #openstack-nova10:29
*** shilpasd has quit IRC10:30
brinzhangWhile run functional test cases, either execute tox or python -m testtools.run command, it will be raise "AssertionError: There is no script for 401 version", details http://paste.openstack.org/show/770633/10:32
*** udesale has quit IRC10:32
brinzhangHow can I avoid this issue?10:32
*** udesale has joined #openstack-nova10:32
*** irclogbot_0 has quit IRC10:33
Sundargibi, Yes, we want to maximize the overlap by  kicking off the binding as early as possible and wait for the ARQs as late as possible, but that is not easy without major surgery. So, I'll be content with dong it inside or after _build_resources. However, if we do: "with .... : foo(); bar()", then only foo() and bar() are done concurrently while wai10:35
Sundarting for the event, right? Also, foo and bar must both be CYborg-related.10:35
*** Sundar has quit IRC10:36
sean-k-mooneybrinzhang: "tox -e functional-py36 -- nova.tests.functional.api_sample_tests.test_quota_sets.NoopQuotaSetsSampleJsonTests.test_show_quotas" this works for me10:36
sean-k-mooneybrinzhang: you might need to add -r  to recreate the tox env.10:36
gibiSundar: yes, only foo and bar will be parallel because when the with wait context manager exits it waits for the events10:36
brinzhangsean-k-mooney: I will have try, thanks10:36
artombrinzhang, did you play with database migrate versions? Because it looks like you bumped the version but didn't provide a migration file10:37
brinzhangartom: I am not update the db10:37
gibiSundar: I don't see why foo and bar needs to be Cyborg related10:39
artombrinzhang, well, that's where the problem seems to be based on the paste you linked10:39
artombrinzhang, the stuff in nova/db/sqlalchemy/migrate_repo/versions/10:40
brinzhangartom: yeah, that why I am confusing10:40
*** markvoelker has joined #openstack-nova10:41
*** irclogbot_2 has joined #openstack-nova10:43
*** markvoelker has quit IRC10:45
*** irclogbot_2 has quit IRC10:45
brinzhangsean-k-monney: http://paste.openstack.org/show/770638/10:46
sean-k-mooneybrinzhang: do you have local changes?10:47
sean-k-mooneyi ran those tests against master10:47
*** dave-mccowan has joined #openstack-nova10:47
brinzhangEmm.. I am in https://review.opendev.org/#/c/673133/14 this patch10:48
brinzhangI will test in master now10:48
sean-k-mooneyif you have a typo like incorrect indentaion or other syntax errors test discovery will fail10:49
brinzhanghttp://paste.openstack.org/show/770638/ it's a wrong director10:49
sean-k-mooneyit will also fail if you if you have tempory filtes create by some edirtor like emacs where it adds a # to the filename10:50
*** Sundar has joined #openstack-nova10:50
Sundargibi, Yes, we want to maximize the overlap by kicking off the binding as early as possible and wait for the ARQs as late as possible, but that is not easy without major surgery. So, I'll be content with dong it inside or after _build_resources. However, if we do: "with .... : foo(); bar()", then only foo() and bar() are done concurrently while wait10:51
Sundaring for the event, right? Also, foo and bar must both be Cyborg-related.10:51
gibiSundar: yes, only foo and bar will be parallel because when the with wait context manager exits it waits for the events10:51
gibiSundar: I don't see why foo and bar needs to be Cyborg related10:51
brinzhangsean-k-mooney: I will delete the edit patch https://review.opendev.org/#/c/673133/14, and then re-fetch it.10:52
Sundargibi: The timeout in the with will cover both foo and bar. Is it reasonable to impose that Cyborg ARQ bind timeout on non-Cyborg activities? it is 300 seconds by default. If it is ok, it will get us more concurrency.10:53
*** irclogbot_3 has joined #openstack-nova10:59
gibiSundar: the timeout is not for foo and bar it is for waiting for the events11:00
gibiSundar: also if the boot process cannot procede without such events then it is OK to wait for the events11:01
*** ociuhandu has joined #openstack-nova11:01
*** irclogbot_3 has quit IRC11:02
Sundargibi: What do you think of waiting for the events in _build_resources, but actually querying Cyborg for ARQs only in the virt driver's spawn? If we do the query when the event comes, we have to store the ARQs in the instance object (or elsewhere), which will require changes to objects and db.11:03
*** nicolasbock has joined #openstack-nova11:04
*** trident has quit IRC11:04
gibiSundar: I think it is better to wait earlier than potenitally loosing notifications as we start waiting too late11:05
gibiSundar: I think you should also ask others, like dansmith about this problem11:05
gibiSundar: if you start waiting in _build_resources then I would do the query in the virt driver instead of passing the ARQ down11:07
gibiSundar: to limit the impact11:07
Sundargibi: Great. That's what I had in mind. :)11:07
SundarThank you very much, gibi.11:08
SundarHave a good day.11:08
gibiSundar: same to you11:08
*** Sundar has quit IRC11:10
*** shilpasd has joined #openstack-nova11:11
*** udesale has quit IRC11:12
*** trident has joined #openstack-nova11:13
sean-k-mooneygibi: would you have time to review https://review.opendev.org/#/q/topic:bp/image-metadata-prefiltering+(status:open+OR+status:merged) today? im aiming to get that merged and free up a runway slot by the end of the week11:14
sean-k-mooneythe 3 remaining pataches are relitivly short11:15
gibisean-k-mooney: I will try...11:15
sean-k-mooneygibi: thanks if you dont get to it its ok i have others to bug too like bauzas11:16
*** mkrai has joined #openstack-nova11:17
sean-k-mooneybauzas: feel like re reviewing https://review.opendev.org/#/q/topic:bp/image-metadata-prefiltering+(status:open)11:17
kashyapaspiers: gibi: Commented here: https://review.opendev.org/#/c/644565/49/nova/virt/libvirt/utils.py@54611:20
sean-k-mooneyartom: i see you currently dont have any ci jobs running using the multi numa job so im going to swap it over too the new lables for FN11:21
artomsean-k-mooney, sure11:21
sean-k-mooneyim also going to reduce the concurance to 111:21
artomsean-k-mooney, unless I'm missing something, the ball's in the reviewers's court11:22
sean-k-mooneyassuming you are happy with them for testingin im going to then swap to testing the cpu work stephen has been doinging11:22
gibikashyap: thanks!11:22
*** zbr is now known as zbr|swimming11:23
artomThough I need to play with the func test some more - the RPC pinning tests didn't pick up a thing they should have picked up11:23
artomsean-k-mooney, yep, that's fair, again much thanks for all your help11:23
sean-k-mooneythats the last patch in the seriese right e.g. it wont block other patches landing11:24
artomFunc tests? Don't think so11:24
artomWe can still land tests after FF, right?11:24
sean-k-mooneyyes11:24
artomEven assuming the worst and  don't get them sorted before then11:24
sean-k-mooneyalthough its better to do it before11:24
*** tbachman has quit IRC11:24
artomThat's the plan :)11:24
brinzhangsean-k-mooney, artom: I remember the unit test or functional test can run any linux env, depend on the devstack or openstack env is not necessary, is that?11:32
sean-k-mooneybrinzhang: correct11:32
sean-k-mooneyyou do not need openstack or devstack to run them11:33
brinzhangsean-k-mooney, artom: I checked to the master and run the test, also report the error11:33
sean-k-mooneywhat os are you running on?11:33
brinzhangCentos711:33
sean-k-mooneybrinzhang: you might want to clone a clean copy of nova and try it again11:33
sean-k-mooneybrinzhang: ok i tested on popos and it worked fine11:34
sean-k-mooneyi can check on rhel811:34
brinzhangOn Monday, It runs ok, but today I git pull11:34
sean-k-mooneyi know some test fail in rhel8 but i think that is due to the version of python it uses11:35
brinzhangEmm, in my env, I was installed py27 and py37,the default is py2711:35
sean-k-mooneyno i mean that using py36 on rhel8 some things fail that pass on py36 on pop_os/ubunutu11:37
brinzhangClone the clean code is so slowly, sometimes maybe disconnect, I don’t want to do that.11:37
sean-k-mooneybrinzhang: well i was only suggesting that since it might be related to unclean files in your working directory11:37
sean-k-mooneyhave you checked there are no tempory files created by your ide/editor11:38
sean-k-mooneyim checking master on rhel8 now11:38
sean-k-mooneyi guess i can check with a centos container too11:38
brinzhangI will check again in my working directory too, and try to clone it in another directory11:39
sean-k-mooneyyou can do a local clone by the way11:40
sean-k-mooneye.g. mkdir temp; cd temp; git clone ~/repos/nova; cd nova; tox -e ...11:40
sean-k-mooneyit passed for me on rhel811:41
sean-k-mooneywith no failurs at all11:41
sean-k-mooneywhich is better then it normally does11:42
aspierssean-k-mooney: the issue with stestr and temporary editor files (e.g. from emacs) is fixed11:42
sean-k-mooneyaspiers: as of when11:43
aspierssean-k-mooney: https://github.com/mtreinish/stestr/issues/23811:43
*** irclogbot_0 has joined #openstack-nova11:43
aspiers2 weeks ago11:43
sean-k-mooneyaspiers: i have hit its since march11:43
aspiersor 311:43
aspiersyeah you need to upgrade your stestr11:43
aspiers2.5.011:43
sean-k-mooneymaybe im just using whicever version tox installs11:44
aspiersTurns out that reporting bugs sometimes helps get them fixed ;-)11:44
sean-k-mooneyalthough i have not recreate all my envs since then11:44
aspiersstestr>=1.0.0 # Apache-2.011:44
aspiersfrom test-requirements11:44
aspierswe should bump that11:44
brinzhangsean-k-mooney: yeah, cloning, but so slowly...11:44
sean-k-mooneybrinzhang: if your doing it locally it should be fast11:44
sean-k-mooneye.g. the file system clone i suggested above11:45
*** xek has joined #openstack-nova11:45
brinzhang git clone ~/repos/nova what do you mean? isnot use git clone https://review.opendev.org/openstack/nova clone to another directory?11:46
brinzhangthis is the clone speed "Receiving objects:   3% (21352/550825), 6.94 MiB | 27.00 KiB/s"11:47
*** irclogbot_0 has quit IRC11:47
openstackgerritEric Fried proposed openstack/nova master: Bump min for oslo.service & .privsep to fix SIGHUP  https://review.opendev.org/67997411:50
openstackgerritSilvan Kaiser proposed openstack/nova stable/stein: Exec systemd-run without --user flag in Quobyte driver  https://review.opendev.org/66070511:53
*** tesseract has joined #openstack-nova12:03
*** larainema has quit IRC12:09
*** tbachman has joined #openstack-nova12:11
*** markvoelker has joined #openstack-nova12:13
*** xek has quit IRC12:21
sean-k-mooneybrinzhang: git can use filesystem urls12:26
*** tbachman has quit IRC12:26
sean-k-mooneybrinzhang: so if you have a copy of a git repo you can clone a second copy using the file sytem path12:26
sean-k-mooneyso for example i keep my dev repos under ~/repos12:27
sean-k-mooneyif i do "mkdir ~/temp; cd temp"12:27
efriedalex_xu, luyao: Are you around?12:27
sean-k-mooneythen do "git clone ~/repos/openstack/nova"12:28
sean-k-mooneyit give me a clean copy of the nova git tree in ~/temp/nova12:29
brinzhangsean-k-moony: Clone completed in another directory, and run tox -e ok, you are right, maybe the  tempory file cause this issue.12:29
luyaoefried: I'm here12:30
brinzhangsean-k-moony: I know your mean now, and I do it like you were said :P12:30
efriedluyao: Do you need any help to make progress on the vpmem series at this point? Do you understand what dansmith is asking for on the bottom two patches?12:35
luyaoefried: I do have some questions on the patch anout DB change.12:38
efriedluyao: Okay. I don't have a good understanding of such things, but dansmith usually arrives on the scene in about 20 minutes. I know it's late for you...12:39
luyaoefried: Ii'll wait for him, and I was going to wait. haha :)12:41
efriedokay12:41
*** zbr|swimming is now known as zbr12:42
*** etp has joined #openstack-nova12:44
*** eharney has quit IRC12:46
*** udesale has joined #openstack-nova12:48
sean-k-mooneybrinzhang: for what it is worth. whenever i hit test issue like that i first create a second local clone and test on the clean repo with master and with my patch branch if i still hit the issue i then check in a conainter.12:49
openstackgerritLuyao Zhong proposed openstack/nova master: db: Add resources column in instance_extra table  https://review.opendev.org/67844712:49
openstackgerritLuyao Zhong proposed openstack/nova master: object: Introduce Resource and ResouceList objs  https://review.opendev.org/67844812:49
openstackgerritLuyao Zhong proposed openstack/nova master: Add resources dict into _Provider  https://review.opendev.org/67844912:49
openstackgerritLuyao Zhong proposed openstack/nova master: Retrieve the allocations early  https://review.opendev.org/67845012:49
openstackgerritLuyao Zhong proposed openstack/nova master: Claim resources in resource tracker  https://review.opendev.org/67845212:49
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Enable driver discovering PMEM namespaces  https://review.opendev.org/67845312:49
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: report VPMEM resources by provider tree  https://review.opendev.org/67845412:49
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Support VM creation with vpmems and vpmems cleanup  https://review.opendev.org/67845512:49
openstackgerritLuyao Zhong proposed openstack/nova master: Parse vpmem related flavor extra spec  https://review.opendev.org/67845612:49
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Enable driver configuring PMEM namespaces  https://review.opendev.org/67964012:49
openstackgerritLuyao Zhong proposed openstack/nova master: Add functional tests for virtual persistent memory  https://review.opendev.org/67847012:50
*** ociuhandu has quit IRC12:50
brinzhangsean-k-mooney: Good experience, got it.12:51
*** luksky has quit IRC12:53
*** pas-ha has joined #openstack-nova12:54
*** markvoelker has quit IRC12:54
*** ociuhandu has joined #openstack-nova12:55
*** mkrai has quit IRC12:56
*** nweinber has joined #openstack-nova12:57
*** markvoelker has joined #openstack-nova13:00
*** tbachman has joined #openstack-nova13:03
*** mriedem has joined #openstack-nova13:04
*** markvoelker has quit IRC13:05
mriedembauzas: can you push this simple refactor through? https://review.opendev.org/#/c/679651/13:09
bauzasmriedem: sure thing13:10
luyaodansmith: Are you around?13:10
*** spatel has joined #openstack-nova13:11
bauzasmriedem: gibi: I was paying attention to the qos-bandwith series but I'm a bit lost with it13:17
bauzasgibi: what's the top change ?13:17
bauzashttps://review.opendev.org/#/c/679653/ ?13:17
bauzasbecause I don't see yet changes for cold migrate13:17
openstackgerritsean mooney proposed openstack/nova master: multi numa nfv testing job  https://review.opendev.org/67965613:17
openstackgerritsean mooney proposed openstack/nova master: [DNM] test migration with pinning  https://review.opendev.org/67975413:17
mriedemgibi: replied in https://review.opendev.org/#/c/656422/18/nova/compute/manager.py@212213:18
bauzasnah nevermind https://review.opendev.org/#/c/679019/413:18
bauzasgerrit fucks up with the series13:18
bauzasthere are some branches13:18
gibibauzas: this is the top https://review.opendev.org/#/c/679019/413:18
gibibauzas: but I will respin the whole soonish to fix mriedem's comments13:19
gibimriedem: looking13:19
bauzasgibi: okay i can wait then13:19
mriedemgibi: tl;dr i think you need the service version check in conductor after scheduler picks a dest and also a check in compute in case the compute rpc api versions are pinned in config13:19
mriedemi.e. the compute services can be running train but configured to only send stein level messages during an upgrade13:20
mriedemartom ran into this yesterday13:20
mriedemboth are temporary and can be removed in U13:20
brinzhangmriedem: https://review.opendev.org/#/c/673133/14/nova/compute/api.py@4028, I was updated that comment, found the volume_bdm.save() report an "ObjectActionError: Object action obj_load_attr failed because: attribute id not lazy-loadable"13:21
brinzhangmriedem: That why?13:21
gibimriedem: ack. I will put the checks in the conductor. Good point about that the service version is no enough13:21
mriedembrinzhang: in unit tests or a tempest run?13:21
artom*me meerkats up*13:22
mriedembrinzhang: if unit tests, you need to mock the BlockDeviceMapping.save call13:22
brinzhangmriedem: functioanl test failed13:22
openstackgerritsean mooney proposed openstack/nova master: multi numa nfv testing job  https://review.opendev.org/67965613:22
openstackgerritsean mooney proposed openstack/nova master: [DNM] test migration with pinning  https://review.opendev.org/67975413:22
*** mkrai has joined #openstack-nova13:22
mriedembrinzhang: ok i can look in a bit13:22
gmannbrinzhang: mriedem just commented, it should be passed in via reserve_block_device_name()13:23
artommriedem, I don't think they can be removed in U - dansmith can explain in more detail when he comes online because I'm not sure I understand it fully, but you can't remove a check until the next major version bump13:23
artomOr maybe I'm misunderstanding it13:24
*** gbarros has joined #openstack-nova13:24
mriedemgmann: no it shouldn't13:24
gmannwe can directly save ?13:24
mriedemgmann: see my earlier comments on that very thing - i specifically don't want to do that b/c it adds a lot of unnecessary complexity13:24
mriedemi have to take my kid to the bus stop, will look into this later13:24
gmannohk, did not see the previous comment13:25
brinzhanggmann: that will be change the rpc version, in PS13 do that13:25
gibibauzas: It might take more time to update the bandwidth series than I first aniticipated. I will ping you when the new version is up13:26
gmanni did not see that, checking..13:26
*** markvoelker has joined #openstack-nova13:27
bauzasgibi: no worries, I'm still working on updating the placement audit command13:28
*** lpetrut has joined #openstack-nova13:31
*** Luzi has quit IRC13:32
dansmithartom: to what are you referring?13:35
artomdansmith, all those checks I have about either making sure we got a param that appears in RPC 5.3, or that we can send RPC 5.3, those can only be removed in the next major version bump, right?13:36
artomdansmith, if so, mind explaining why, exactly? It's still not clear in my head why they can't just go away in U13:36
dansmithwell, it's because there are two sets of "rules" at play here:13:37
dansmithThe first is that we don't allow RPC upgrades from N-2 to N in terms of releases13:37
dansmithwe do that not just because of strict rpc compatibility, but because of stuff buried deeper that expects fields to be filled out two releases from now, data migrations to have run, etc13:38
artomdansmith, this means that we don't support Train anything talking to Rocky anything, right? Only Stein13:38
dansmiththe second is that the RPC versioning rules say that within a major version, you must be backwards compatible, able to accept anything back to 5.0 and able to send anything back to 5.0 if asked (by the version pin). If we always bumped versions on every release, then you could always remove stuff two releases from when you added it (since each release would have to bridge between two majors, you could never remove it in the next one)13:39
*** udesale has quit IRC13:39
*** irclogbot_1 has joined #openstack-nova13:39
*** udesale has joined #openstack-nova13:39
dansmithartom: that's what it means, but since the rpc version is all we have, it's really a soft statement of support that we can't validate or quantify,13:39
dansmithespecially since people backport stuff13:40
artomPeople backport RPC stuff?13:40
dansmiththe RPC versioning scheme that we have is why, in many cases, you actually can run N-2 talking to N when things haven't shifted much, and what would save our bacon if we had to start supporting such a thing13:40
dansmithupstream doesn't, but distros have in the past for sure13:41
dansmithhowever,13:41
dansmithit's easy to backport something that doesn't technically affect the rpc interface directly, but definitely changes behavior or semantics13:41
dansmithlike something that causes a field to be filled out that wouldn't have been if the client was really as old as it is, etc13:41
dansmithlike some distro that wanted to backport an api feature that now sends something newer, but doesn't technically need an rpc change to make it work13:42
*** irclogbot_1 has quit IRC13:42
artomSo the reason the first rule doesn't invalidate the second rule is that even if we only allow a mix of N and N-1, there's nothing stopping an older RPC pin from being set?13:42
dansmithyes, but let me state it slightly differently:13:42
dansmiththe first rule is our support policy and the second is the actual mechanical way we make sure our services can sanely talk to each other across versions13:43
artomAh, I see13:43
dansmithso theoretically the mechanical bit should be able to support a wider envelope (rule 2) than we officially say we support (rule 1)13:43
artomIOW, we don't have mechanics in place to enforce our support policy, short of bumping major on every release13:44
dansmithbecause the N->N+2 thing has lots of other implications as well, like database migrations, things that need to check service versions to enable api features, etc, etc13:44
dansmiththat's a true statement13:44
artomAha, so the support policy is not just for RPC, it's for other things as well (that list you just said)13:45
dansmithyup13:45
dansmithbecause the other things are buried deep and don't necessarily even have a direct impact on rpc, but can definitely have an indirect one13:45
dansmithalright, so I've passed the torch of knowledge, now you can be the enforcer right?13:46
artomdansmith, not sure about that, but I'll write it up in https://docs.openstack.org/nova/stein/reference/index.html13:46
mriedemit's already written up in dan's blog...13:46
mriedemif you wanted to condense that, sure13:47
dansmithbut writing it up in our docs would be good13:47
mriedemwhat i was thinking about was https://review.opendev.org/#/c/634606/73/nova/compute/manager.py@6574 specifically is only needed for train,13:47
mriedemsince we don't support Stein -> U13:47
dansmithif my blog is part of the official nova docs, I'm going to throw some ads up there :)13:47
artomdansmith, for AWS :D13:47
dansmithmriedem: that's only the case because of the rule 1 above13:48
mriedemsure,13:48
dansmithmriedem: they can still set the pin lower than train in U and would fail to make that call.. it'd be an unsupported situation, but it's probably good if we just leave it in place13:48
mriedemand law of nova #35 says we'll forget to remove the compat code for 3 releases anyway13:48
dansmithheh13:48
* artom doesn't want to know what rule 34 of nova is13:48
dansmithI can tell  you what rule #1 is13:49
mriedemthere is a rule somewhere that you must have at least 3 different types of BlockDevice(Mapping) objects13:49
dansmith#17 iirc13:49
artomdansmith, you left us hanging on #1 there13:49
dansmithartom: don't talk about nova, obvi13:50
* artom shuts up13:50
*** etp has quit IRC13:50
artomOK, I lied.13:50
alex_xudansmith: let me know I understand this rule correct or not https://review.opendev.org/#/c/678447/7/nova/db/sqlalchemy/migrate_repo/versions/401_add_resources.py@32 :)13:50
artomdansmith, mriedem, just so I'm clear, are we waiting on anything from me and/or CI for the NUMA LM series?13:50
dansmithartom: nope, I had it up to be looking at when I saw your ping13:51
mriedemi've been online for ~45 minutes and already have a full tab queue, so no13:51
luyaodansmith: Hi, I have a question about  https://review.opendev.org/#/c/678447/8 .  Do you mean the script can run out of the nova code, the script will just update DB, then db column is deleted while the updates on nova code have not taken effect.I don't understand how I should do.13:51
alex_xuluyao: i just asked :)13:52
artommriedem, yep, fully away of your overcommitment, as just making sure I understood where we stood :)13:52
artom*was13:52
dansmithalex_xu: yes, scheduled_at is the only field we've removed in a long time since we started doing the model/schema sync, so follow that pattern13:52
*** BjoernT has joined #openstack-nova13:52
alex_xudansmith: ah, got it, leave comment on the model obj, and rename the exisiting field to resources, then remove it next release13:53
alex_xudansmith: thanks!13:53
dansmithalex_xu: rename the field on the model, but you have to add the column to the whitelist so it will be ignored, but yeah.13:53
luyaodansmith: I got this fail on test_models_sync , AssertionError: Models and migration scripts aren't in sync:13:53
mriedem"add the column to the whitelist so it will be ignored"13:53
alex_xudansmith: what the whitelist mean?13:54
*** luksky has joined #openstack-nova13:54
dansmithalex_xu: look in those scheduled_at patches.. there's a whitelist for the test that validates that the model and schema match13:54
*** amrith has joined #openstack-nova13:54
dansmithartom: looks like the ci job on top never really completes because sean-k-mooney is working on it.. got a link to a recent run?13:55
*** mlavalle has joined #openstack-nova13:55
artomdansmith, so I left a comment on PS7 of https://review.opendev.org/#/c/679656/ linking to various signs of success13:56
sean-k-mooneydansmith:  well i just started updateing them again today since there were no running jobs13:56
artomlemme see if I can find something more recent13:56
dansmithartom: yeah that was before the hugepage work right?13:56
artomdansmith, I believe that was after13:56
sean-k-mooneythis was after https://46b5dc7879590352c3ef-b484a2b89d5d2c358f068133dfb2fa14.ssl.cf5.rackcdn.com/679805/2/experimental/nova-nfv-multi-numa-multinode/b040d28/testr_results.html.gz13:56
artomdansmith, 13:12 my time, I was talking to danpb that morning about hugepages13:57
sean-k-mooneythis is from the run where i forced the vcpu_pin_set and cpu_shared_set to be reversed on each host13:58
sean-k-mooneyhttps://46b5dc7879590352c3ef-b484a2b89d5d2c358f068133dfb2fa14.ssl.cf5.rackcdn.com/679805/2/experimental/nova-nfv-multi-numa-multinode/b040d28/compute/logs/etc/nova/nova_conf.txt.gz13:58
luyaodansmith, alex_xu : I found the whitelist. Thanks!13:59
alex_xuluyao: really, I'm not...still looking13:59
*** irclogbot_1 has joined #openstack-nova13:59
alex_xuah, I found it14:00
*** eharney has joined #openstack-nova14:00
luyaoalex_xu: it's in nova/tests/unit/db/test_migrations.py,  def filter_metadata_diff14:00
alex_xuluyao: you win14:00
alex_xudansmith: thanks again14:00
*** irclogbot_1 has quit IRC14:02
yonglihealex_xu: Good evening.14:02
alex_xuyonglihe: good evening too :)14:02
*** mkrai has quit IRC14:02
*** mkrai_ has joined #openstack-nova14:03
*** mkrai_ has quit IRC14:05
*** irclogbot_2 has joined #openstack-nova14:05
*** irclogbot_2 has quit IRC14:08
*** mkrai has joined #openstack-nova14:08
dansmithartom: sean-k-mooney: What're ya'll doing to test the rollback case IRL?14:09
artomdansmith, IRL? nothing. Trying to understand why the func test wasn't picking it up14:10
openstackgerritMatt Riedemann proposed openstack/nova master: Remove Rocky compute compat checks for live migration with port bindings  https://review.opendev.org/68000514:10
dansmithartom: okay, I would expect you'd set up something to fail the migration to make sure the rollback actually happens properly14:10
sean-k-mooneye.g. a failure to migrate, i have inetvertenly tested it by forgettting to exchanged ssh keys and haveing the migrate fail and rollback14:10
sean-k-mooneythat is the only testing of it i did14:10
dansmithsean-k-mooney: is it getting far enough that it actually calls the new method?14:10
sean-k-mooneyyes14:10
dansmithokay14:10
sean-k-mooneyi have not done that on the latest version14:11
sean-k-mooneywant me to do that14:11
sean-k-mooneyi just need to drop the ssh key form autherised keys14:11
*** irclogbot_3 has joined #openstack-nova14:11
dansmithsean-k-mooney: can you also do something else for us? pin the compute version on one machine to 5.2 and migrate both directions to make sure it still works14:11
dansmithbecause we really *really* don't want to break migrations for upgrades14:11
artomdansmith, I suppose I can setup stein/master and try it14:11
sean-k-mooneysure. i can do that in a ci test too14:11
dansmithif we find out late that we did and need to tweak rpc stuff to make it work, life is gonna suck14:12
artomdansmith, oh, just pinning. yeah :)14:12
sean-k-mooneybut ill test both14:12
dansmithsean-k-mooney: okay thanks14:12
sean-k-mooneydansmith: i can also give you acess once i have it set up if you want to poke around14:12
dansmithI see the logs show it actually doing the new stuff so that's cool14:12
dansmithsean-k-mooney: that's okay, I'14:12
artom(Wouldn't func be sufficient - like, I get wanting to see real libvirt with the updated XML, and thank god because it caught bugs)14:12
dansmithsean-k-mooney: I'll trust some pastebin'd logs14:12
artom(But rollback is all compute)14:13
dansmithartom: func is great, but it's not the real thing14:13
dansmithartom: trust me, you don't want to be on a sev1 where you realize you're going to need to add an RPC .z version to fix this14:13
dansmithwe did that in icehouse for a customer and it was not cool14:13
artomFully agree there14:13
*** irclogbot_3 has quit IRC14:14
artomsean-k-mooney, how feasible would it be to modify the grenade job to run with a NUMA flavor?14:14
artomOn FN hardwa14:15
artom*hardware14:15
sean-k-mooneyso i am less familar with legacy jobs but it could be done14:15
sean-k-mooneythe nodeset is not hard but forcing it to use nested virt is the tricky bit14:15
sean-k-mooneydevstack gate is non tivial14:16
*** tbachman has quit IRC14:16
sean-k-mooneyadding grendate on top is harder14:16
sean-k-mooneyif we need to do that we could however14:16
artomsean-k-mooney, well, dansmith said he's satisfied with pastebin, so maybe more long term14:16
sean-k-mooneyi would like to port greadne to a non legacy job at some point14:16
sean-k-mooneywell well i have not updated https://review.opendev.org/#/c/679805/ to pick up the other changes i did this morning14:17
sean-k-mooneyi can updated it and add the different compute versions in that14:17
sean-k-mooneyill try and test it locally first however14:17
*** lpetrut has quit IRC14:19
mriedemspeaking of converting a job to zuulv3, https://review.opendev.org/#/c/674345/ converts the nova-lvm job to zuulv3 and has a +214:19
sean-k-mooneydansmith: do you know how to pin the rpc version of the top of your head. ill look it up in teh config ref if not14:19
mriedemsean-k-mooney: [upgrade_levels]/compute=stein14:20
dansmithyeah that14:20
sean-k-mooneythanks14:20
mriedemhttps://docs.openstack.org/nova/latest/configuration/config.html#upgrade_levels.compute14:20
sean-k-mooneydoes it matter if i do this on the compute or the contoler? e.g. we want the conductor ect to not be pinned right14:21
mriedemonce that nova-lvm change is merged the only legacy jobs we have are the live migration and grenade multinode ones, which i've probably put off b/c of the external script they run, but nova-next was converted and runs an external script so i can probably do similar14:21
sean-k-mooneyjust the source node?14:21
mriedemsean-k-mooney: if you pin in nova-cpu.conf i don't think it matters14:21
mriedemconductor is using a different config14:21
sean-k-mooneyya just want to make sure i dont mess up my local.conf and have to redeploy14:22
sean-k-mooneyill pin it on the dedicated compute node14:22
sean-k-mooneynova-cpu.conf would also work14:22
* mriedem thinks he just said that14:22
sean-k-mooneyyes you did i was agreeing with you14:23
mriedemi can tinker later this afternoon with converting that nova-grenade-multinode job to zuulv314:24
mriedemthose have been on my todo list for awhile14:24
sean-k-mooneyi can also try if you run into issue but i have never actully run greade and i dont know if we have the ansibel playbooks to run it so im not sure how easy that will be14:25
sean-k-mooneyis greade hard to run or is basically the same as devstack14:26
*** edleafe has joined #openstack-nova14:27
*** tesseract has quit IRC14:30
mriedemit's just a set of bash scripts that orchestrates setting up n-1 devstack, creating some resources, shutting down and then running N version devstack and making sure those resources are still around14:32
mriedemi've never run it locally manually, only in CI14:32
gibimriedem: looking at the MigrationTask. When the dest is selected by the scheduler I can check right away if the dest has a new enough compute service version. But if not, then what? simulate a re-schedule locally in the conductor?  https://github.com/openstack/nova/blob/cbaea3bd690c683e83a063acfa69919668eaa123/nova/conductor/tasks/migrate.py#L24814:32
mriedemgibi: you'd have to iterate alternates14:33
sean-k-mooneymriedem: looking at the zuul config they dont have a non legacy way to run it14:33
sean-k-mooneyhttps://opendev.org/openstack/grenade/src/branch/master/.zuul.yaml14:33
mriedemit's times like this that i've thought about having a compute service version filter in the scheduler14:33
mriedemso we can say internally "only give me computes with service version >= x for this feature"14:33
sean-k-mooneymriedem: well if that feature was a compute capablity tratis we could use placemtn for that14:34
gibimriedem: Yeah that was what I mean by simualting a re-schedule locally , as I have to take care of num_retries and the allocations too14:34
mriedemsean-k-mooney: https://review.opendev.org/#/c/548936/14:34
sean-k-mooneylike your multi attach stuff14:34
openstackgerritMerged openstack/nova master: Make _get_cpu_feature_traits() always return a dict  https://review.opendev.org/67956814:34
openstackgerritMerged openstack/nova master: libvirt: Make scheduler filters customizable  https://review.opendev.org/67974514:34
sean-k-mooneymriedem: ya i saw that mentioned on the infra irc yesterday14:34
mriedemgibi: num_retries, you mean max_attempts?14:35
sean-k-mooneyi was not sure how far along it was14:35
mriedemgibi: if so, that's built into the number of alternates you get back from the scheduler14:35
gibimriedem: ohh, good point. If I run out of alternates then raise MaxRetriesExceeded14:35
*** BjoernT_ has joined #openstack-nova14:35
mriedemgibi: yeah, and write it in a separate method so we can drop that in U or V14:36
gibimriedem: sure14:36
sean-k-mooneymriedem: ok it looks like that is passing. i wonder is there a reason it is not merged yet. i should go ask them14:37
*** BjoernT has quit IRC14:37
gibimriedem: also I think I have to check the version of the source compute as well becuase request spec travels like cond -> dest -> source -> dest so if the source is old then the request_spec will not reach the dest at the end14:37
mriedemsean-k-mooney: the scheduler will already filter dest computes that have the required nested inventory for qos bw providers, but we do'nt know if that dest compute is stein or train to support cold migratoin with those things, and i don't think we want to get into a habit of adding a compute capability for every "supports_fancy_unicorn" feature just for rolling upgrade support14:37
*** irclogbot_2 has joined #openstack-nova14:37
mriedemsean-k-mooney: probably b/c grenade cores (of which i'm one) haven't looked at it14:37
mriedemgibi: correct, like the port binding stuff in live migration, you have to check source and dest14:38
gibimriedem: OK. thanks for the help.14:38
mriedemgibi: the source you could check in the API i guess14:38
mriedemand 409 if it's old14:38
gibimriedem: yes, I can do that14:38
* gibi goes back to it's IDE14:39
*** tesseract has joined #openstack-nova14:39
mriedemhis?14:40
*** irclogbot_2 has quit IRC14:40
* mriedem notes gibi just exposed that he's truly a cyborg14:40
*** markvoelker has quit IRC14:41
*** tbachman has joined #openstack-nova14:41
* gibi hates English for the 3 different grammatical genders14:42
*** tesseract has quit IRC14:44
gibi(as a note, in hungarian are no gender specific words for he, she, it, just a single 'Å‘' )14:46
*** luksky has quit IRC14:48
*** shilpasd has quit IRC14:49
*** damien_r has quit IRC14:51
*** irclogbot_1 has joined #openstack-nova14:52
mriedemcould be worse, could be french, right? isn't everything gender specific in french?14:52
*** damien_r has joined #openstack-nova14:52
gibiI know german a bit, and that already worse  :)14:54
*** irclogbot_1 has quit IRC14:54
*** eharney has quit IRC14:54
gibiand I can imagine hungarian being worse on many different level compared to english14:54
*** damien_r has quit IRC14:55
sean-k-mooneygibi: you can almost always use the gender nutral form in english if you prefer although singular they or it  can annoy some14:55
mriedembrinzhang: the reason for the functional test failures is inline https://review.opendev.org/#/c/673133/14:56
stephenfinmriedem, gibi: I need a way to prevent people only setting '[compute] cpu_dedicated_set' on hosts that have non-pinned instances (to prevent https://review.opendev.org/#/c/674895/22/nova/virt/libvirt/driver.py@7358)14:56
sean-k-mooneyfor some reason people dont like to be refered to as "it"14:56
mriedemit's because of stubs in the api samples tests14:56
gibisean-k-mooney: thank. I try to remember to that14:56
mriedemif we were using real compute services and the CinderFixture we wouldn't have that problem, but re-writing those tests is beyond this patch14:56
stephenfinI'm thinking iterating through every single instance on the host in 'LibvirtDriver.init_host' is too expensive14:56
gibistephenfin: don't we already iterating every instance in init_host?14:57
sean-k-mooneywe do in update_resouces or whatevre its called14:57
sean-k-mooneyi thikn we call that as part of init14:57
stephenfingibi: If we do, I don't see it14:57
sean-k-mooneywe iterate over all instance to plug there interfaces14:57
sean-k-mooneyat the very least14:57
stephenfinIt all seems to be basic config opt checks14:58
stephenfinHmm14:58
mriedemgibi might be thinking of ComputeManager.init_host14:58
dansmithartom: check me here: https://review.opendev.org/#/c/634606/7314:58
gibiyeah, I think I remember ComputeManager.init_host14:58
openstackgerritLuyao Zhong proposed openstack/nova master: db: Add resources column in instance_extra table  https://review.opendev.org/67844714:58
openstackgerritLuyao Zhong proposed openstack/nova master: object: Introduce Resource and ResouceList objs  https://review.opendev.org/67844814:58
openstackgerritLuyao Zhong proposed openstack/nova master: Add resources dict into _Provider  https://review.opendev.org/67844914:58
openstackgerritLuyao Zhong proposed openstack/nova master: Retrieve the allocations early  https://review.opendev.org/67845014:58
openstackgerritLuyao Zhong proposed openstack/nova master: Claim resources in resource tracker  https://review.opendev.org/67845214:58
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Enable driver discovering PMEM namespaces  https://review.opendev.org/67845314:58
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: report VPMEM resources by provider tree  https://review.opendev.org/67845414:58
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Support VM creation with vpmems and vpmems cleanup  https://review.opendev.org/67845514:58
openstackgerritLuyao Zhong proposed openstack/nova master: Parse vpmem related flavor extra spec  https://review.opendev.org/67845614:58
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Enable driver configuring PMEM namespaces  https://review.opendev.org/67964014:58
openstackgerritLuyao Zhong proposed openstack/nova master: Add functional tests for virtual persistent memory  https://review.opendev.org/67847014:58
dansmithartom: that's a big nasty patch, so it's a good sign that I only had a couple minor things14:58
mriedemComputeManager.init_host gets all instances https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L125614:59
stephenfinOh, ComputeManager.init_host14:59
stephenfinI was thinking this would have to live in 'LibvirtDriver.init_host'14:59
artomdansmith, witness me!14:59
mriedemstephenfin: is cpu_dedicated_set a new config option in that series?14:59
stephenfinyup15:00
mriedemhow do you determine if an instance is pinned or not?15:00
*** shilpasd has joined #openstack-nova15:00
mriedemlooking at the instance.numa_topology?15:00
cdenttry to lift it up15:01
cdentif it doesn't move...15:01
stephenfinmriedem: Instance.numa_topology.cpu_pinning_requested15:01
* mriedem cues rimshot15:01
mriedemstephenfin: so none of that is libvirt specific yeah?15:01
stephenfintechnically no. It just won't do anything without libvirt15:01
mriedemfor now15:02
stephenfinThat 'cpu_pinning_requested' property would never be set on non-libvirt driver15:02
stephenfinCorrect15:02
mriedemso...add a compute driver capability so a nova-compute running vsphere doesn't have to look at that for 1K+ instances managed by that host15:02
*** amrith has quit IRC15:02
mriedemif self.driver.capabilities.get('supports_some_hw_magic', False):15:03
mriedem   # do expensive thing15:03
*** cfriesen has joined #openstack-nova15:03
stephenfinso not "if CONF.compute_driver == 'libvirt'" ?15:04
mriedemalternatively we change the ComputeDriver.init_host interface to pass the list of instances on that host into the virt driver15:04
openstackgerritLuyao Zhong proposed openstack/nova master: object: Introduce Resource and ResourceList objs  https://review.opendev.org/67844815:04
openstackgerritLuyao Zhong proposed openstack/nova master: Add resources dict into _Provider  https://review.opendev.org/67844915:04
openstackgerritLuyao Zhong proposed openstack/nova master: Retrieve the allocations early  https://review.opendev.org/67845015:04
openstackgerritLuyao Zhong proposed openstack/nova master: Claim resources in resource tracker  https://review.opendev.org/67845215:04
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Enable driver discovering PMEM namespaces  https://review.opendev.org/67845315:04
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: report VPMEM resources by provider tree  https://review.opendev.org/67845415:04
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Support VM creation with vpmems and vpmems cleanup  https://review.opendev.org/67845515:04
openstackgerritLuyao Zhong proposed openstack/nova master: Parse vpmem related flavor extra spec  https://review.opendev.org/67845615:04
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Enable driver configuring PMEM namespaces  https://review.opendev.org/67964015:04
openstackgerritLuyao Zhong proposed openstack/nova master: Add functional tests for virtual persistent memory  https://review.opendev.org/67847015:04
artomstephenfin, eww15:04
mriedemstephenfin: right that ^15:04
artomstephenfin, I have no context, but errr15:04
artom*eww15:04
mriedemwe generally don't ever want to look at that config to make decisions15:04
stephenfinfair fair15:04
mriedem*something something factory pattern*15:04
mriedemanyway, maybe people would prefer to just swap those 3 lines of code in ComputeManager.init_host to pass the InstanceList to the driver and let the driver sort it out15:05
mriedemeither way you're going to explode and kill the start of the service if it's misconfigured correct?15:05
stephenfinyup15:07
luyaodansmith: comments addressed. https://review.opendev.org/#/c/678447/9 and  https://review.opendev.org/#/c/678448/1215:07
*** tbachman has quit IRC15:08
openstackgerritLuyao Zhong proposed openstack/nova master: db: Add resources column in instance_extra table  https://review.opendev.org/67844715:12
openstackgerritLuyao Zhong proposed openstack/nova master: object: Introduce Resource and ResourceList objs  https://review.opendev.org/67844815:12
openstackgerritLuyao Zhong proposed openstack/nova master: Add resources dict into _Provider  https://review.opendev.org/67844915:12
openstackgerritLuyao Zhong proposed openstack/nova master: Retrieve the allocations early  https://review.opendev.org/67845015:12
openstackgerritLuyao Zhong proposed openstack/nova master: Claim resources in resource tracker  https://review.opendev.org/67845215:12
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Enable driver discovering PMEM namespaces  https://review.opendev.org/67845315:12
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: report VPMEM resources by provider tree  https://review.opendev.org/67845415:12
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Support VM creation with vpmems and vpmems cleanup  https://review.opendev.org/67845515:12
openstackgerritLuyao Zhong proposed openstack/nova master: Parse vpmem related flavor extra spec  https://review.opendev.org/67845615:12
openstackgerritLuyao Zhong proposed openstack/nova master: libvirt: Enable driver configuring PMEM namespaces  https://review.opendev.org/67964015:12
openstackgerritLuyao Zhong proposed openstack/nova master: Add functional tests for virtual persistent memory  https://review.opendev.org/67847015:12
*** tesseract has joined #openstack-nova15:14
*** damien_r has joined #openstack-nova15:16
*** damien_r has quit IRC15:16
*** yan0s has quit IRC15:17
*** mkrai has quit IRC15:17
openstackgerritEric Fried proposed openstack/nova master: Bump min for oslo.service & .privsep to fix SIGHUP  https://review.opendev.org/67997415:21
openstackgerritAdam Spiers proposed openstack/nova master: Ensure q35 machine type is used when booting with SEV  https://review.opendev.org/68006515:22
*** damien_r has joined #openstack-nova15:22
kashyapcfriesen: Hi, you or someone you know picking this up? -- https://review.opendev.org/#/c/621646/ ("Preserve UEFI NVRAM variable store")15:23
kashyapOh, actually zhu.boxiang has picked it up lately15:24
cfriesenkashyap: yeah, was just going to say. :)15:25
*** zbr is now known as zbr|out15:25
sean-k-mooneydansmith: i think the cross rpc migration is working. i have not looked at the logs to confim but it succeed via horizon15:30
dansmithsean-k-mooney: okay, with a numa flavor or non-numa flavor?15:30
sean-k-mooneywith cpu pinning enabled15:31
sean-k-mooneyso numa15:31
dansmithokay, so the behavior we expect is for it to work, not claim, and just translate the topo directly over to the other side, for better or worse, correct?15:31
dansmithartom: ^15:31
openstackgerritAdam Spiers proposed openstack/nova master: Ensure q35 machine type is used when booting with SEV  https://review.opendev.org/68006515:31
aspiersefried, kashyap, sean-k-mooney: ^^^ this implements what we agreed yesterday15:31
artomdansmith, yep, aka, what we have now15:32
dansmithyeah, okay15:32
kashyapaspiers: Already reading the code for a couple of mins (while on a call)15:32
aspierskashyap: awesome, I just uploaded PS2 though15:32
aspiersrealised I missed a few little bits out15:32
sean-k-mooneydansmith: do i need to test the sucess case or was it the revert case that you were worried about15:32
dansmithsean-k-mooney: so, one more test you could do is pop all the patches off from one node and just validate that you can still migrate between them (with the version pinned)15:32
artomdansmith, because as soon as we start claiming, it's all or nothing, we need to handle applying the migration context, dropping the claim on rollback, etc15:32
dansmithsean-k-mooney: yeah, that'd be good too15:33
kashyapaspiers: I see that you've put the check in hardware.py15:33
aspierskashyap: yes. This new approach is actually quite a lot cleaner15:33
*** irclogbot_2 has joined #openstack-nova15:33
aspiersso I'm glad we had the discussions15:33
*** ociuhandu has quit IRC15:34
kashyapaspiers: Okay, then.  Because there's a prereq on hardware feature, hardware.py?15:34
aspierskashyap: it's just adding another check alongside the existing 2 extra specs / image props checks15:35
openstackgerritAdam Spiers proposed openstack/nova master: Apply SEV-specific guest config when SEV is required  https://review.opendev.org/64456515:35
stephenfinmriedem: What exception type should I be raising in ComputeManager.init_host if my checks fail. I'm thinking 'InternalError' since it's an operator misconfiguration15:35
sean-k-mooneydansmith: ok so before i check artom code vs master or the revert case. was there somehting in partcal you wanted me to grab form the logs or db15:35
kashyapaspiers: Right; so I can probably put my _guest_machine_type_for_secure_boot() still in utils.py.15:35
dansmithsean-k-mooney:  just want to make sure it's not doing numa migration I guess.. there are a couple logs that indicate it's doing the new stuff15:36
*** irclogbot_2 has quit IRC15:36
aspierskashyap: now I realise why you were asking that15:36
kashyapaspiers: :-)15:36
dansmithsean-k-mooney: you don't really have to pastebin, I trust you, just check to make sure you don't see those on either side15:36
artomsean-k-mooney, dansmith, presence of LibvirtLiveMigrateNUMAInfo is a big sign15:36
dansmithartom: like this one: https://review.opendev.org/#/c/634606/73/nova/virt/libvirt/driver.py@746515:36
dansmithartom: yep15:36
aspierskashyap: yeah I guess yours could still go in utils.py15:36
sean-k-mooneyartom: are you expecting it to regenerat the xml when the RPC version is pinned?15:37
artomWe log the migrate_data all over the place, so if that's not in it, we haven't NUMA live-migrated15:37
artomsean-k-mooney, no15:37
sean-k-mooneyok ill check that so15:37
*** irclogbot_2 has joined #openstack-nova15:37
mriedemstephenfin: i see the libvirt driver init_host raises Invalid, but we already have a InvalidConfiguration so that seems more appropriate15:37
artomAny RPC pin on either source, dest or cond should cause the current half-broken behaviour15:37
mriedemit doesn't really matter though15:37
kashyapaspiers: It's a similar method.  But in your case, I see you're clubbing it all together with the relevant mem encryption- / SEV-related checks15:37
stephenfinack15:37
sean-k-mooneythe config i have would require the xml to be update to be correct so i shoudl see the xml updated in only 1 direction15:37
sean-k-mooneyor not at all15:38
aspierskashyap: right15:38
*** gbarros has quit IRC15:38
kashyapaspiers: I'll just Depends-On yours for the exception class15:39
aspierskashyap: or just make it the child commit15:39
aspierskashyap: isn't Depends-On more for cross-repo stuff?15:39
*** altlogbot_1 has joined #openstack-nova15:39
sean-k-mooneyartom: dansmith: pinned source => unpinned dest no xml updates on migration15:39
kashyapaspiers: True, Depends-On is indeed normally used for cross-repo things15:40
*** macz has joined #openstack-nova15:41
sean-k-mooneyartom: and i get erros in the compute log because the vm xml is invalid for the new host vcpu_pin_set so that is working as we expect15:41
artom"and i get erros in the comput" *panic* "so that is working as we expect" *relief15:41
artomu kill me man15:42
sean-k-mooneyits compliing the vm cpu pinning is not valid for the host in the periodici task that caulates resouce usage15:42
artomWhich is a known bug I think15:42
sean-k-mooneyits compliing the vm cpu pinning is not valid for the host in the periodici task that caulates resouce usage15:42
sean-k-mooneywrong terminal15:43
sean-k-mooneywell its not really a bug so much as use say hay you vm pinning is invalid15:43
*** tbachman has joined #openstack-nova15:44
*** markvoelker has joined #openstack-nova15:45
artomI mean there's a launchpad bug for it somewhere15:45
sean-k-mooneyya there is a patch that sugges we skip updating the resouse if its invalid15:46
sean-k-mooneywhich i think we both nack'd15:46
sean-k-mooneyartom: dansmith same behavior for new source to old dest. no xml update15:47
artomsean-k-mooney, yep15:47
dansmithcool15:47
artomdansmith, well, figured out why my func tests weren't doing the expected thing15:47
artomI was stubbing stuff on the ClientRouter, which is a global singleton15:47
* dansmith waits for it15:47
artomSo *all* 3 services got capped15:48
dansmithah yeah15:48
artomI shouldn't hit the same problem if I replace the actual compute_rpcapi objects, though, right?15:49
dansmithyou can get access to the managers in the services you start right?15:49
dansmithso manager.rpcapi = $newthing15:49
artomI couldn't figure out how to either cap the objects directly, or create new ones and replace. Looks like I have no choice to do that now.15:49
dansmithI think15:49
artomYeah, it's "$newthing" that needs thinking about15:50
artomThere's no __init__, so how do I cap it?15:50
mriedemcompute = self.start_service('compute', host='host1')15:50
mriedemcompute.manager.compute_rpcapi = my_stub15:50
mriedemor something like that15:51
mriedemstub the compute_rcpapi on one of the services in the func test15:51
dansmiththat ^15:51
dansmithI think you could also not stub the full rpcapi, and just stub out can_send_version on the one it sets up for you15:52
openstackgerritAdam Spiers proposed openstack/nova master: Enable booting of libvirt guests with AMD SEV memory encryption  https://review.opendev.org/66661615:53
artomcan_send_version is on the client though15:53
sean-k-mooneyso ... there is one issue. if we live migrate the server to a host where the pinning is invalide.15:53
sean-k-mooneythen we cold migrate it15:53
sean-k-mooneythe cold migrtion fails in resize confim15:53
artomsean-k-mooney, is pinning involved, or master to master?15:53
sean-k-mooneyyes15:54
artomYes to...?15:54
sean-k-mooneynova.exception.CP│15:54
sean-k-mooneyUUnpinningUnknown: CPU set to unpin [12, 15, 4, 7] must be a subset of known CPU set []15:54
artomWouldn't that be a latent thing?15:54
sean-k-mooneyim going to triple check but i think cold migration of a pinned instnace is fine15:54
sean-k-mooneyjsut not one that has been live migrtation to a host with out regenrting the xml if the xml is invalid for that host15:55
*** priteau has quit IRC15:55
artomThat's still a different bug though, and why we moved to block numa live migration by default?15:55
sean-k-mooneyi can check but i think this would happen on master too15:55
*** dtantsur is now known as dtantsur|afk15:55
sean-k-mooneyby the way i was kind of expecting that might fail im just reporing what im finding as i try to break it15:57
artomTotally, this sort of testing is great15:57
openstackgerritAdam Spiers proposed openstack/nova master: Enable booting of libvirt guests with AMD SEV memory encryption  https://review.opendev.org/66661615:57
artomWait, would live migrating to an invalid pinning situation go through?15:58
openstackgerritMerged openstack/nova master: Refactor MigrationTask._execute  https://review.opendev.org/67965115:58
openstackgerritMerged openstack/nova master: unit test: do not fill rp mapping for failed re-schedule  https://review.opendev.org/67965315:58
sean-k-mooneyok cold migration of a new instance works fine15:58
artomI guess as long as the host CPUs are online, we don't check whether they're part of vcpu_pin_set during the LM15:58
sean-k-mooneyill check reverting to master on the compute node then master only15:58
artomSo it'd make sense for that to fail in a subsequent operation15:59
*** gbarros has joined #openstack-nova15:59
*** gyee has joined #openstack-nova15:59
sean-k-mooneyartom: right libvirt checks they are are a thing but libvirt is not aware of the vcpu_pin_set15:59
sean-k-mooneyand i have intentionally configred theyse hsot so the vcpu_pin_sets on each host does not overlap16:00
artomRight, to make sure the old broken behaviour is happening16:00
sean-k-mooneyyes16:01
sean-k-mooneyand to give a really hard edgecase16:01
aspierskashyap: I've just built an image with an experimental kernel and grub secure boot fails due to "invalid signature"16:02
aspierskashyap: any idea how to tell it the signature is trustworthy?16:02
sean-k-mooneyone server is set  up to only allow resouce on numa node 0 the other for node 1 only and it have the cpu_shared_set configure to use the opistie numa node to the vcpu_pin_set16:02
kashyapaspiers: Yeah, "experimental kernal" is the keyword :-)16:03
sean-k-mooneyaspiers: it has not been sgined with a key that is in the secure boot keystore would be my guess16:03
kashyapSo, there is a manual way to make it "trustworthy"16:04
kashyapaspiers: But I don't see a document for it.  Last I checked with an admin who does it, said it's quite tedious16:04
openstackgerritMatt Riedemann proposed openstack/nova master: Add delete_on_termination to volume-attach API  https://review.opendev.org/67313316:05
sean-k-mooneydansmith: artom os i have a proablem with 1 node on master and the other node on artoms code16:05
sean-k-mooneyon startup the agent on master code is raising "ServiceTooOld: This service is older (v39) than the minimum (v40) version of the rest of the deployment."16:05
donnydIs there a way to ask nova for a specific trait on an instance without configuring a flavor first?16:06
openstackgerritAdam Spiers proposed openstack/nova master: Enable booting of libvirt guests with AMD SEV memory encryption  https://review.opendev.org/66661616:06
artomsean-k-mooney, update the database I think16:06
kashyapaspiers: If Secure Boot is not a reqiurement for your test, then I'd suggest to disable it16:06
sean-k-mooneyi guess i need to pin artoms code to the older version?16:06
*** ociuhandu has joined #openstack-nova16:06
aspierskashyap: how?16:06
mriedemdonnyd: required traits are defined on the flavor or image16:06
artomsean-k-mooney, I hit that a few times when I git pulled a new service version, but the version in the database for the service was old16:06
sean-k-mooneyartom: well i didnt use the head of master. i used the version of master your code was bassed on16:06
kashyapaspiers: You mean, "disable how"?16:06
aspierskashyap: yes, how do I disable it16:07
sean-k-mooneye.g. this is the frist commit before your code16:07
dansmithsean-k-mooney: you'll have to delete some service records16:07
sean-k-mooneyah right16:07
dansmithsean-k-mooney: that message is coming because you've got entries in the db that say everything should be upgraded already16:07
sean-k-mooneyif i just stop the agent and do a compute servcie delete that should fix it right16:08
sean-k-mooneyalternitivel i can restack that node16:08
donnydIs there any way to place a custom request in via the sdk?16:08
donnydThe scenario is I use some sort of discovery to populate placement with traits, and I don't want to configure a flavor for each specific type16:08
kashyapaspiers: Don't know top off my head; but let me check with a dev who does this more often16:08
mriedemstephenfin: looking at https://review.opendev.org/#/c/621476/ alex is +2 and you asked for docs fixes in PS61 which are done now, so you might want to hit that again soonish,16:09
mriedemstephenfin: especially b/c i'm +2 on https://review.opendev.org/#/c/673133/15 which is competing for the same microversion16:09
kashyapaspiers: In the BIOS menu, it depends on your vendor16:09
aspierskashyap: we are talking about a VM in nova here, remember16:10
stephenfinmriedem: Sure, I can do that before I leave16:10
aspiersit's some virtual BIOS thing16:10
*** ociuhandu has quit IRC16:11
kashyapaspiers: Right, it's a VM; a quick check -- you're using one of those enrolled "VARS" files shipped by your distro I guess?16:11
kashyapaspiers: If so, the quickest way to disable it is to just start your guest with a non-enrolled (i.e. not signed by MS) "VARS" file.16:12
aspierskashyap: right, as per my comment on https://review.opendev.org/#/c/348394/16:12
sean-k-mooneywe need to update osc to better support service deleteion16:13
aspierskashyap: in that final comment there is a list of all the "code" files16:13
aspierskashyap: which have corresponding "vars" files16:13
aspierskashyap: which one looks most promising?16:13
kashyapLooking16:13
sean-k-mooneyosc only support the id not the service uuid16:13
aspierskashyap: currently I'm using ovmf-x86_64-suse-code.bin and ovmf-x86_64-suse-vars.bin16:13
mriedemsean-k-mooney: that's not accurate16:13
mriedemhttps://docs.openstack.org/python-openstackclient/latest/cli/command-objects/compute-service.html#compute-service-delete16:14
aspierskashyap: I have no idea what "4m" means16:14
kashyapaspiers: I once did research on that SUSE naming, but totally forgot16:14
kashyapaspiers: Hmm, so you _are_ using a non-MS signed one16:14
sean-k-mooneywell the help text in the version i have installed says it thakes the id and the uuid did not work16:14
mriedemsean-k-mooney: you have to specify the microversion with osc16:14
mriedemit defaults to 2.116:14
mriedemso: openstack --os-compute-api-version 2.53 compute service delete <service uuid>16:15
sean-k-mooney oh ya that is a thing16:15
kashyapaspiers: Hint: that "4m" will be described in your RPM spec file; but that's not useful for your immediate prob16:15
sean-k-mooneythe help text does not methion that16:15
*** damien_r has quit IRC16:15
kashyapaspiers: Try this one: ovmf-x86_64.bin (and the corresponding VARS file)16:15
mriedemsean-k-mooney: b/c you have old osc16:15
mriedemi added that recently16:16
sean-k-mooneyah ok im using 3.19.016:16
sean-k-mooneyits not a big deal anyway16:16
*** ivve has quit IRC16:17
aspierskashyap: OK but as per my comment on https://review.opendev.org/#/c/348394/ ovmf-x86_64-code.bin did not work, so not confident that ovmf-x86_64.bin will work either16:17
kashyapaspiers: Reading that; I was relying on the file name suggested by Dirk correct :-(16:17
kashyapaspiers: Also, I find it crazy that the SUSE RPM has _so_ many binaries; you need a simple combination:16:17
kashyapaspiers: (a) a non-SB binary and a non-enrolled VARS file; (b) an SB-binary and an enrolled (MS-signed) VARS file16:18
aspiersyeah I have no clue why it's like that16:18
kashyapaspiers: Can you get a link to the RPM spec file, please?  That will clarify what they are all.16:19
*** zbr|out is now known as zbr16:19
kashyapaspiers: Incidentally, the "light at the end of the tunnel" is it's going to be much easier, once SUSE ships: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=93226916:20
openstackDebian bug 932269 in ovmf "Ship the firmware "descriptor files" as part of the 'ovmf' package" [Normal,Fixed]16:20
kashyap(Debian and Ubuntu now do.  As does Fedora, for a while)16:21
sean-k-mooneyhum so i still get the same error after deleting the compute service16:21
*** jaosorior has joined #openstack-nova16:23
aspierskashyap: https://build.opensuse.org/package/view_file/Virtualization/ovmf/ovmf.spec?expand=116:23
dansmithsean-k-mooney: you have to stop them all, delete them all, then start up the old one first16:23
sean-k-mooneyoh i have stop and delete the compute service on the "new" node too16:24
sean-k-mooneynot just the one im puting ot master16:24
sean-k-mooneyok16:24
donnydmriedem: is there a way to craft custom requests via the sdk?16:24
sean-k-mooneydonnyd: if you mean raw http requests yes16:25
aspierskashyap: do you really think the exception message should refer to "Q35" when the way to fix the exception is to set hw_machine_type=q35 (lowercase) ?16:25
sean-k-mooneydonnyd: you can use the sdk to jsut get a rest client and then perform raw GET|POST|PUT|DELETE|... request with the client with whatever body you want16:26
donnydSo is it possible to craft a raw request that would allow me to ask placement for a node that meets X trait and then tell nova to provision that resource16:26
kashyapaspiers: Thanks for the link; that "4m" corresponds to a 4MB flash image.16:26
aspiersah interesting16:26
kashyapaspiers: On the exception, ah, lowercase is indeed fine.  (Sorry)16:26
aspierskashyap: np, thanks16:27
sean-k-mooneythe first half yes the scond no not direcltly16:27
*** eharney has joined #openstack-nova16:27
sean-k-mooneyif you want nova to schduler a vm to a host with a give trait you can add it as a required trait in etiher the flavor or image16:27
sean-k-mooneyand then nova will include it in the request to placment16:27
sean-k-mooneyyou cant however ask placmenet for an allocation caniate for a vm and tell nova to use it16:28
donnydsean-k-mooney: maybe a little more context would help, this is for baremetal16:28
openstackgerritAdam Spiers proposed openstack/nova master: Ensure q35 machine type is used when booting with SEV  https://review.opendev.org/68006516:28
kashyapaspiers: Also, can you please confirm from the SUSE OVMF pkg maintainer -- *which* of your biaries are built with SECURE_BOOT_ENABLE flag?16:28
sean-k-mooneyyou are trying to land a nova instance on a specific ironic host?16:28
kashyapaspiers: Need to dial into a call; back later.16:29
donnydyes16:29
donnydwithout having to create custom flavors... because it would result in a large # of flavors to manage and maintain16:29
sean-k-mooneydo you want to be able to do it or do you want non admins to be able to do it16:30
donnydCI jobs, so non admin16:30
donnydMaybe have to create some custom policy or something like that16:31
sean-k-mooneyam do you need to jsut deferenciate between ironic nodes and vms or do you need to select a specific host16:31
donnydI need to be able to tell nova to select a specific metal host ( no vm's yet)16:32
sean-k-mooneyok the hacky way to do that is to abuse the availablty zone. but there are other ways16:32
openstackgerritAdam Spiers proposed openstack/nova master: Ensure q35 machine type is used when booting with SEV  https://review.opendev.org/68006516:34
donnydso like nova boot  --availability-zone ZONE:HOST:NODE16:34
sean-k-mooneyyes16:35
donnydefried: shared that with me a while back16:35
sean-k-mooneyim not sure if nodepool supports that16:35
sean-k-mooneyi think it might16:35
openstackgerritAdam Spiers proposed openstack/nova master: Apply SEV-specific guest config when SEV is required  https://review.opendev.org/64456516:35
sean-k-mooneythe other way to do it would be a schduler hint16:35
openstackgerritAdam Spiers proposed openstack/nova master: Enable booting of libvirt guests with AMD SEV memory encryption  https://review.opendev.org/66661616:36
sean-k-mooneyi think you could use the json filter to do this16:36
donnydhow do you do it with the scheduler hint?16:36
sean-k-mooneyso the hoststate object contains the hostname uuid and nodename16:37
sean-k-mooneyhttps://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L109-L11116:37
sean-k-mooneythe json filter can match on any field in the host state object16:37
donnydok cool. Thanks for entertaining my questions :)16:38
aspiersstephenfin, efried: is check_can_live_migrate_destination() the right place to prevent live migration in the SEV case?16:39
sean-k-mooneyi think you do openstack server create --hint query="$host==ironic_host_name"16:40
sean-k-mooneyagain im not sure if the openstack nodepool driver suppots that. or not16:41
sean-k-mooneydonnyd: the json filter is also off by defualt as normally we dont want people to be able to pick specific hosts16:41
*** luksky has joined #openstack-nova16:42
sean-k-mooneybut both the availablity zone and json filters can technically do it16:42
aspiersefried, kashyap: nits with q35 check addressed16:42
donnydWith the json filter, will it fail if it cannot find the specific host?16:42
sean-k-mooneyyes16:42
donnydok, I think both of those two options will work for this case16:43
donnydmuch appreciated sean-k-mooney16:43
sean-k-mooneydonnyd: the json filter basicaly allows you to match on anything in this object https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L109-L159 so you can be very specific16:44
sean-k-mooneydonnyd: you might be able to use https://zuul-ci.org/docs/nodepool/configuration.html#attr-providers.[openstack].pools.labels.instance-properties16:46
sean-k-mooneybut you defintely can use https://zuul-ci.org/docs/nodepool/configuration.html#attr-providers.[openstack].pools.availability-zones16:46
sean-k-mooneywell i have never tired it16:47
*** mdbooth has quit IRC16:50
*** cdent has quit IRC16:51
-openstackstatus- NOTICE: Zuul job logs stored in OVH may fail. We have updated the base job to remove OVH from our storage location. If you have POST_FAILURES a recheck should fix them at this point.16:52
mriedemewww jsonfilter16:52
mriedemi'm not sure how that helps with linking hosts with a given trait16:53
sean-k-mooneymriedem: it does not. donnyd wanted a way per vm to selct a given host16:53
mriedemdonnyd: you can use the placement CLI to filter providers with required traits as well https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-provider-list16:53
donnydask placement for host that matches x trait and then place request in for Host that is returned16:53
mriedemdonnyd: which version of nova?16:54
donnyd.latest atm16:54
*** mdbooth has joined #openstack-nova16:54
sean-k-mooneylatest as in stien not master16:54
donnydThis isn't for FN, its for a different CI I am working on16:54
mriedemso stein or master?16:54
mriedemb/c train has https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id6616:54
donnydProbably going to be train16:54
mriedemwhich would be your easiest thing16:54
mriedemin train the server create api takes a requested host16:55
mriedemand runs it through the scheduler16:55
mriedemotherwise you can use the JsonFilter like sean-k-mooney said or force the host of your choosing with admin creds16:55
sean-k-mooneyya that is the best approch if you can use train. although nodepool wont supprot that16:55
mriedemhttps://docs.openstack.org/nova/latest/admin/availability-zones.html16:55
mriedem^ forced host16:55
donnydsean-k-mooney: Not sure it will be using  nodepool16:56
mriedemheed the JsonFilter warnings https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#jsonfilter16:56
mriedemJsonFilter is pretty common for putting a baremetal instance on a specific baremetal node16:56
mriedem2.74 avoids the need for the JsonFilter for that though, which is nice16:57
sean-k-mooneyyep16:57
donnydmriedem: that is quite precisely the use case. Trying to pick a specific metal host16:57
donnydin train will that work for metal and VM?16:58
mriedemyes16:58
donnydnice16:58
donnydwell then it will be worth the wait16:58
mriedemhost = nova-compute service hostname16:58
donnyd:)16:58
mriedemhypervisor_hostname = node name = ironic uuid16:59
mriedemfor kvm the host and hypervisor_hostname are the same thing16:59
sean-k-mooneydonnyd: by way do you openstack to reinstall the os on the ironic node16:59
*** derekh has quit IRC17:00
sean-k-mooneyif you dont you can also use the static driver if you end up using node pool https://zuul-ci.org/docs/nodepool/configuration.html#static-driver17:00
sean-k-mooneyadding support to the new feature to the openstack driver however could be useful17:01
donnydsean-k-mooney: I openstack for everything in FN17:02
*** shilpasd has quit IRC17:06
*** udesale has quit IRC17:07
*** kaisers has quit IRC17:09
*** ociuhandu has joined #openstack-nova17:22
* aspiers is lost in a twisty maze of API files, all alike17:22
*** ociuhandu has quit IRC17:26
*** kaisers has joined #openstack-nova17:28
*** maciejjozefczyk has quit IRC17:32
sean-k-mooneyartom: dansmit: sorry have been distracted by a headache that developed over the lst hour or two.17:37
sean-k-mooneyi finally gets master compute  + artom code on contoler17:38
sean-k-mooneythe migration was the same as the pinned rpc.17:38
sean-k-mooneyactully its stil pinned ill unpin and check17:38
*** ociuhandu has joined #openstack-nova17:38
aspierssean-k-mooney: can you quickly advise me on where to add a check to refuse API requests to migrate/suspend SEV guests? is nova/compute/api.py the right place?17:38
aspiersit's libvirt-specific so kind of feels like it belongs in the driver17:38
mriedemaspiers: isn't it a generic trait in the flavor though?17:39
mriedemfailing in the driver kind of sucks if you flat out don't support migrating that type of instance17:39
sean-k-mooneymriedem: well there is a generic resouce class17:39
aspiersmriedem: no, typically the trait won't be used until Intel MKTME comes in17:39
mriedemmeaning you'll reschedule to another host that will also fail17:40
aspiersmriedem: right, that's what I was worried about17:40
mriedemwhat makes a sev instance a sev instance?17:40
mriedemsomething in the flavor or image right?17:40
aspiersyes17:40
aspiershw:mem_encryption17:40
sean-k-mooneyyou could block it either in the api by checking for the flavor extra spec17:40
sean-k-mooneyor in a prifilter i guess17:40
aspierssean-k-mooney: that's what I want to do, yep17:40
aspiersI'm just trying to find the right bit of code17:40
mriedempre-filter doesn't work since it doesn't have the context on you doing a move operatoin vs a server create17:41
sean-k-mooneyits the validate_flavor_image_nostatus funciton17:41
mriedemso just failing fast in the api or conductor would be sufficient17:41
sean-k-mooneyor one that it calls17:41
aspiersnova.compute.api.API.live_migrate()?17:41
mriedemwhat about cold migrate? does that work?17:42
aspiersno17:42
sean-k-mooneyaspiers: you can do it the way we do for sriov migration i guess.17:42
aspiersneed to also block suspend17:42
sean-k-mooneyaspiers: no?17:42
sean-k-mooneywhy would cold migration not work17:42
sean-k-mooneysuspenmd i get17:42
aspiersoh sorry17:42
mriedemheh, you might as well just write a decorator then17:42
sean-k-mooneyits doing a managed save17:42
aspiersyeah cold migration probably OK17:42
* aspiers rereads his own spec17:42
aspiershttp://specs.openstack.org/openstack/nova-specs/specs/train/approved/amd-sev-libvirt-support.html#limitations17:42
*** ociuhandu has quit IRC17:42
aspiersyes, cold migration/shelve is OK17:43
aspiersThat's why I explicitly wrote that in the spec - cos I knew I'd forget later ;-)17:43
mriedemdef block_for_sev(func, context, instance, *args, **kwargs): if 'hw:mem_encryption' in instance.flavor.extra_specs: raise OperationNotSupportedForSev()17:44
sean-k-mooneyaspiers: if you do it in the conductor do it here. but if you eant to do it in the api. yuou need to do in a different location17:44
sean-k-mooneyhttps://github.com/openstack/nova/blob/master/nova/conductor/tasks/live_migrate.py#L31817:44
mriedemthen just decorate the methods that don't support sev instances17:44
sean-k-mooneyill see if i can find it17:44
mriedemit would be nice to not duplicate the same checks all over the api and conductor...17:44
aspiersagreed17:44
sean-k-mooneyya17:44
sean-k-mooneysicne we know this just wont work for sev instace right now i think the api is better17:45
aspierspresumably better UX if it's done in the API?17:45
sean-k-mooneyjust flat out block it17:45
sean-k-mooneyyes we will end up doing less work too17:45
aspiersright, so is e.g. nova.compute.api.API.live_migrate() the right place?17:45
aspiersusing a decorator like mriedem suggested17:46
sean-k-mooneythe problem with doing it in the api is when another dirver starts support sev then we need to remove it and move it to the condocor or somethwer else that can be aware of the hypervior type17:46
openstackgerritStephen Finucane proposed openstack/nova master: libvirt: Start reporting PCPU inventory to placement  https://review.opendev.org/67179317:46
openstackgerritStephen Finucane proposed openstack/nova master: libvirt: '_get_(v|p)cpu_total' to '_get_(v|p)cpu_available'  https://review.opendev.org/67269317:46
openstackgerritStephen Finucane proposed openstack/nova master: hardware: Differentiate between shared and dedicated CPUs  https://review.opendev.org/67180017:46
openstackgerritStephen Finucane proposed openstack/nova master: libvirt: Start reporting 'HW_CPU_HYPERTHREADING' trait  https://review.opendev.org/67557117:46
openstackgerritStephen Finucane proposed openstack/nova master: Add support for translating CPU policy extra specs, image meta  https://review.opendev.org/67180117:46
openstackgerritStephen Finucane proposed openstack/nova master: Add reshaper for PCPU  https://review.opendev.org/67489517:46
openstackgerritStephen Finucane proposed openstack/nova master: objects: Add 'InstanceNUMATopology.cpu_pinning' property  https://review.opendev.org/68010617:46
openstackgerritStephen Finucane proposed openstack/nova master: Validate CPU config options against running instances  https://review.opendev.org/68010717:46
openstackgerritStephen Finucane proposed openstack/nova master: objects: Add 'NUMACell.pcpuset' field  https://review.opendev.org/68010817:46
aspierssean-k-mooney: what other driver would start to support SEV?17:47
stephenfinmriedem: If you're interested, there's the startup check I was talking about earlier https://review.opendev.org/68010717:47
sean-k-mooneyhyperv maybe? vmware17:47
sean-k-mooneyi mean its not a kvm tech it hsould  be usable on other hyperviors17:47
stephenfinaspiers: Might be of interest to you, actually ^17:47
stephenfinIt's a similar thing to what you need, I suspect17:47
stephenfinsean-k-mooney can confirm17:47
sean-k-mooneyaspiers: what i would do is write a check in hardware.py17:47
stephenfinthough /me has to go17:47
sean-k-mooneythen call that form the api17:47
sean-k-mooneyand or conductor17:48
aspierssean-k-mooney: there is already a check in hardware.py17:48
sean-k-mooneyaspiers: well we use check in hardware.py from the api for other things17:48
mriedemfwiw i don't see any other virt driver supporting sev anytime soon17:48
aspiersmriedem: agreed17:49
mriedemthe vmware driver is basically maintenance mode17:49
mriedemxen is on the way out17:49
aspierssean-k-mooney: https://opendev.org/openstack/nova/src/branch/master/nova/virt/hardware.py#L114017:49
mriedemoh that reminds me,17:49
mriedemefried: should we formally deprecate the xen driver before releasing train?17:49
dansmithwow17:49
mriedemright now you just get a quality warning in the logs on startup17:49
mriedemdansmith: we talked about that at the ptg17:50
mriedemhasn't had CI in probably a year17:50
dansmithI know17:50
sean-k-mooneymriedem: didnt we say we would at the PTG17:50
dansmithit's just...a big and sad deal17:50
sean-k-mooneymriedem: well if nothing impove in train17:50
mriedemdeprecating doesn't mean we remove in U17:50
mriedemjust that we have the option17:50
dansmithyup17:50
sean-k-mooneymriedem: i dont think testing has impvoed so we proably sue17:51
mriedemwe still need to nix nova-net17:51
sean-k-mooneyshoudl17:51
dansmithdeprecation should be a shot across the bow.. if nobody steps up at that point, then.. the signal is clear17:51
mriedemi'll put it on the meeting agenda for tomorrow so it's in the meeting logs17:51
mriedemand such17:51
mriedemsuch and such and so and so17:51
sean-k-mooneyaspiers: ya so i would just call get_mem_encryption_constraint form the api and reject the live migration if its true17:52
donnydhasn't nova-net been on the chopping block for the better half of a decade?17:52
aspierssean-k-mooney: right, so is nova.compute.api.API.live_migrate() the right method to do the rejection?17:52
mriedemdonnyd: deprecated in newton17:52
aspierssean-k-mooney: and nova.compute.api.API.suspend()?17:52
mriedemdonnyd: nova-net gets hard to remove when it's tendrils are in everything17:52
mriedem*its17:52
donnydmakes sense17:53
melwittdonnyd: did you ever figure out your slow image download problem? I had talked to penick about it and he said with the hardware specs you gave, download should be fast (like you were also thinking)17:53
donnydno17:53
donnydits still slow17:53
melwitthave you tried a simple scp from machine to machine to see if that's similarly slow? he suggested that17:53
melwittto narrow down whether it's related to nova or not17:54
*** ociuhandu has joined #openstack-nova17:54
dansmithI haven't followed this issue, but an scp can be cpu bound and not max out a fast connection17:55
dansmithif it's really bad, then it going faster will tell you something,17:55
dansmithbut if it's 10gE or something, generally iperf or straight netcat will help you go faste17:55
dansmith*faster17:56
melwittoh, ok didn't know that17:56
sean-k-mooneyaspiers: you could add a decorator and ecorate those metods but im not sure what the normal procedure would be17:56
aspierssean-k-mooney: yes I'm writing a decorator as per mriedem's suggestion but I want to make sure I'm decorating the right methods :)17:56
sean-k-mooneyfor cyborge i think we chose not to do this17:56
aspierssean-k-mooney: in the right file17:56
mriedemsean-k-mooney: there isn't really a normal procedure,17:57
sean-k-mooneywe chose to jsut document what ws not supprotted17:57
donnydscp openstack:/var/lib/glance/images/8dd685fd-277d-46fb-8d1c-b05ff7c5ecaa17:57
donnyd8dd685fd-277d-46fb-8d1c-b05ff7c5ecaa                                                                                                                      100% 6212MB 209.1MB/s   00:2917:57
mriedemmost times when we know shit doesn't work we just don't fix it, don't fail fast detect it, or document it17:57
donnydso 2x faster than glance17:57
mriedemover time people eventually get tired of that so they put fail fast checks in place, like the things that don't work in the api with volume-backed servers17:57
donnydbut dansmith is correct. CPU bound on the controller side17:57
sean-k-mooneymriedem: yes so aspiers is breakign the mold by puting the check in place with the code17:58
dansmithdonnyd: scp'ing from and to the same disks on each side presumably?17:58
mriedemsean-k-mooney: not really, like i said, we have "this doesn't work with this type of instance" checks in the API for certain things17:58
*** ociuhandu has quit IRC17:58
mriedemhe's just doing it a bit differently with a decorator, it's the same idea though17:58
sean-k-mooneyya17:59
sean-k-mooneyi understand that and that we do have check like this17:59
sean-k-mooneyaspiers: so what are you going to return to the use17:59
sean-k-mooneya 4**17:59
mriedemthe bw provider qos stuff fails fast in the api for move ops today too17:59
sean-k-mooneyyes18:00
sean-k-mooneyi was looking ot see if i could find that18:00
donnydhttps://www.irccloud.com/pastebin/wQsy8Dyc/18:00
donnydnot likely to be a network issue18:00
mriedemsean-k-mooney: for the bw provider case (supports_port_resource_request_during_move) we return a 40018:00
sean-k-mooneyfor consitnece we proablyt want to fail the migration with the same respoce code18:00
dansmithdonnyd: there are various chunk sizes for the glance backends, which may be too small by default for a fast network18:01
sean-k-mooneyok 400 bad request makes sense i guess18:01
mriedemi'm not sure that 400 was really correct there, 409 might have been better, but ...18:01
*** tesseract has quit IRC18:01
aspierssean-k-mooney: I can't even find the place where migration chooses which error codes to return. There's no mention of migration in nova.api.openstack.compute.servers18:02
sean-k-mooneyi was just looking at 40918:02
sean-k-mooneyhttps://developer.mozilla.org/en-US/docs/Web/HTTP/Status/40918:02
donnyddansmith: using file backend because it performs the fastest18:02
sean-k-mooneyi think we had this conversation for bandwidth too18:02
aspiersoh found it18:03
dansmithdonnyd: yeah, there are chunk size knobs for several of them, filesystem included18:03
aspiersnova.api.openstack.compute.migrate_servers18:03
dansmithdonnyd: 64k by default, apparently, which is pretty dang small18:03
donnydYea that is a little on the small side18:03
dansmithfor 1gE that's probably okay, but not 10gE I'd think..18:04
sean-k-mooneyaspiers: right here https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/migrate_server.py#L61-L6818:04
donnydthe controller side is 40G18:04
aspiersOK so I want the check to go in nova.api.openstack.compute.migrate_servers not nova.compute.api18:04
donnydand each compute is 1018:04
dansmithdonnyd: the rbd default chunk is 8MiB, fwiw18:04
sean-k-mooneyaspiers: or in your case you want the live_migrate check below it18:05
sean-k-mooneyhttps://github.com/openstack/nova/blob/master/nova/api/openstack/compute/migrate_server.py#L127-L13718:05
dansmithalthough it's not clear if that chunk size affects streaming like the filesystem one does18:05
sean-k-mooneyaspiers: so that his proably the method you want to extend to call into hardware.py and check if sev is requested18:05
mriedemaspiers: i don't know that it matters really; i liked the decorator b/c you don't have to copy/paste the validation logic18:06
mriedemif you do it in nova.compute.api.API methods you'll have to handle whatever exception you raise so that the api doesn't return a 50018:06
aspiersmriedem: got it18:06
sean-k-mooneymriedem: well you chould still use a decorator on thos funcitons18:06
mriedemsean-k-mooney: i'd rather not use a decorator on those18:07
aspiersyes, so decorate nova.compute.api.API and handle the new exception in nova.api.openstack.compute.migrate_server18:07
mriedemthe decorator for wsgi stuff is really about wsgi18:07
sean-k-mooneyok18:07
mriedemthe compute API methods already have decorators that do sniff tests18:07
mriedemlike task_state, is locked, etc18:07
aspiersyeah I was copying those18:07
aspiersnow we just have to spend 3 hours bikeshedding the new exception name18:07
sean-k-mooneyaspiers: or just add a method to hardware.py that raise the correct excption18:08
sean-k-mooneythen jsut call it in all the palces you need too18:08
aspiershardware.py doesn't know what operation is being done18:08
sean-k-mooneymost of the exception in hardware.py inherit form the http ones18:08
sean-k-mooneyyes but you can call it form the api and pass in the oppertion if its needed18:09
aspiersthat feels like mixing up layers to me18:09
aspiersI think I have enough hints to get it done now, thanks guys18:09
sean-k-mooneynot sure i helped much18:09
mriedemstephenfin: ok, -1 :)18:10
aspierssean-k-mooney: ;-)18:10
*** markvoelker has quit IRC18:12
*** markvoelker has joined #openstack-nova18:12
openstackgerritDustin Cowles proposed openstack/nova master: Provider Config File: YAML file loading and schema validation  https://review.opendev.org/67334118:13
openstackgerritDustin Cowles proposed openstack/nova master: WIP: Provider Config File: Public method to retrieve custom resources  https://review.opendev.org/67602918:13
openstackgerritDustin Cowles proposed openstack/nova master: WIP: Provider Config File: Update provider tree with new custom resources  https://review.opendev.org/67652218:13
sean-k-mooneydansmith: artom: so live migration form (master) src node to (artoms code) dest node with unpinned or pinned rpc18:13
sean-k-mooneyappears to work the same as if we pin to the old rpc version18:14
sean-k-mooneye.g. no xml updates18:14
sean-k-mooneyand you can live migrate it back too18:15
mriedemhere it comes18:16
openstackgerritMatt Riedemann proposed openstack/nova master: Add prep_snapshot_based_resize_at_dest compute method  https://review.opendev.org/63329318:17
openstackgerritMatt Riedemann proposed openstack/nova master: Add PrepResizeAtDestTask  https://review.opendev.org/62789018:17
openstackgerritMatt Riedemann proposed openstack/nova master: Add prep_snapshot_based_resize_at_source compute method  https://review.opendev.org/63483218:17
openstackgerritMatt Riedemann proposed openstack/nova master: Add PrepResizeAtSourceTask  https://review.opendev.org/62789118:17
openstackgerritMatt Riedemann proposed openstack/nova master: Add finish_snapshot_based_resize_at_dest compute method  https://review.opendev.org/63508018:17
openstackgerritMatt Riedemann proposed openstack/nova master: Add FinishResizeAtDestTask  https://review.opendev.org/63564618:17
openstackgerritMatt Riedemann proposed openstack/nova master: Execute CrossCellMigrationTask from MigrationTask  https://review.opendev.org/63566818:17
openstackgerritMatt Riedemann proposed openstack/nova master: Plumb allow_cross_cell_resize into compute API resize()  https://review.opendev.org/63568418:17
openstackgerritMatt Riedemann proposed openstack/nova master: Filter duplicates from compute API get_migrations_sorted()  https://review.opendev.org/63622418:17
openstackgerritMatt Riedemann proposed openstack/nova master: Start functional testing for cross-cell resize  https://review.opendev.org/63625318:17
openstackgerritMatt Riedemann proposed openstack/nova master: Handle target host cross-cell cold migration in conductor  https://review.opendev.org/64259118:17
openstackgerritMatt Riedemann proposed openstack/nova master: Validate image/create during cross-cell resize functional testing  https://review.opendev.org/64259218:17
openstackgerritMatt Riedemann proposed openstack/nova master: Add zones wrinkle to TestMultiCellMigrate  https://review.opendev.org/64345018:17
openstackgerritMatt Riedemann proposed openstack/nova master: Add negative test for cross-cell finish_resize failing  https://review.opendev.org/64345118:17
openstackgerritMatt Riedemann proposed openstack/nova master: Refresh instance in MigrationTask.execute Exception handler  https://review.opendev.org/66901218:17
openstackgerritMatt Riedemann proposed openstack/nova master: Add negative test for prep_snapshot_based_resize_at_source failing  https://review.opendev.org/66901318:17
openstackgerritMatt Riedemann proposed openstack/nova master: WIP: Add confirm_snapshot_based_resize_at_source compute method  https://review.opendev.org/63705818:17
openstackgerritMatt Riedemann proposed openstack/nova master: WIP: Add ConfirmResizeTask  https://review.opendev.org/63707018:17
sean-k-mooneywhile its on the dest node with the invalid pinning we get the message we expect in the update resouce providers http://paste.openstack.org/show/770652/ whic is the same behavior as master today18:19
sean-k-mooneydansmith: artom im going to lie down and take some panadol and hopefully my headache will go away. let me know if i need to test anything else and i will do it tomorrow18:21
dansmithsean-k-mooney: cool, thanks for these confirmations...18:22
donnydsean-k-mooney: using 2x the ceph defaults to start18:22
donnydwe will see how it goes18:22
sean-k-mooney2x?18:22
dansmithwas that intended for me?18:23
melwittprobably18:23
*** mvkr has quit IRC18:24
sean-k-mooneyoh the rbd defualt chunk size18:24
sean-k-mooneyya that was for dan18:24
mriedemartom: can this be abandoned now? https://review.opendev.org/#/c/634605/18:25
mriedemyour series is kind of hard to follow in gerrit18:25
mriedemespecially when the topic branch no longer matches the bp name18:25
artommriedem, done18:25
sean-k-mooneyi think this is the new topic branch https://review.opendev.org/#/q/topic:bp/numa-aware-live-migration-patch27+(status:open+OR+status:merged)18:25
artommriedem, wtf, where did '-patch27' come from?18:25
artomsean-k-mooney, for your tests?18:26
mriedemartom: guessing you were doing some weird local feature branch rebasing18:26
sean-k-mooneyno18:26
artomI didn't do it intentionally18:26
sean-k-mooneyi mean that sames to be what most of the new ones are tagged with18:26
mriedemis anything using this? https://review.opendev.org/#/c/679319/18:26
sean-k-mooneythis is the last patch https://review.opendev.org/#/c/672595/18:27
artommriedem, nope, abandon away18:27
sean-k-mooneyso that is the 7 pathces theat matter18:27
sean-k-mooneyi guess 6 pathces.18:27
mriedemand https://review.opendev.org/#/c/679656/ is the thing testing it?18:28
* sean-k-mooney really goes to lie down now18:28
melwittI've been wondering what happened to the automatic topic naming in gerrit. it was nice when it used to do that18:28
mriedemwhich is...on a different topic branch18:28
mriedemso hard to find...18:28
sean-k-mooneymriedem: feel free to change it18:28
dansmithmelwitt: that is a function of git-review I think18:28
mriedemhttps://review.opendev.org/#/q/topic:bp/numa-aware-live-migration+(status:open+OR+status:merged)+project:openstack/nova18:29
melwitthm, I didn't think I had changed git-review versions. I will check that18:29
mriedemlooking better18:29
*** brault has joined #openstack-nova18:29
dansmithmelwitt: see the -t section, which says "if not specified, a bug number from the commit summary will be used" https://linux.die.net/man/1/git-review18:30
melwittthank you18:30
mriedemis that only if you're on the master branch?18:31
mriedemi'm always in a topic branch18:31
artommriedem, cleaned it up a bit, sorry for the mess18:31
dansmithmriedem: no18:31
dansmithmriedem: bug takes precedence, otherwise local branch name18:31
melwittI'm not sure what happened but in the past, I never had to worry about my random topic branch name getting pushed to gerrit (as long as I have a bug or bp) but lately I noticed it's not adjusting it anymore18:31
dansmithI never submit from the master branch locally..18:31
mriedemsame, ok i guess i just didn't notice since i'm always using bug/xxx or bp/xxx18:32
sean-k-mooneyit will still take the topic if you do git checkout -b whatever18:33
dansmithsean-k-mooney: only if there is no other tag in the commit message18:33
dansmithsean-k-mooney: go lie down :)18:33
sean-k-mooneya recent version of git-review removed some of the auto topic stuff18:33
sean-k-mooneyya i will but stephenfin change how this works recently18:34
*** brault has quit IRC18:34
melwittaw man18:34
sean-k-mooneyi think they weanted to remvoe the auto topic form the commit message18:34
melwittI need to downgrade then probably18:34
sean-k-mooneybut leave the auto topic form branch name18:34
mriedemi thought sean-k-mooney was going to lie down?18:34
melwittgit-review version 1.28.018:34
sean-k-mooneyok o/18:34
mriedemnow that he's gone,18:35
dansmithhttps://opendev.org/opendev/git-review/commit/af955c932eb97433199781b5d4f7fb5fb5af8a6f18:35
dansmithhttps://opendev.org/opendev/git-review/commit/03768832c4a73c3079ce24d84fecae1da39b2d7118:35
* mriedem can't come up with good exotic hardware joke18:35
dansmith"frequently does the wrong thing" ... not that I ever saw.18:35
melwittyeah like, what?18:36
dansmithmelwitt: that second commit is likely what you've noticed I guess18:36
melwittstephenfin you're killin me18:36
melwittand yeah, I think you're right dansmith18:36
melwittI'm gonna downgrade18:37
dansmiththe story links in that commit are broken,18:37
dansmithand no gerrit links so I dunno what kind of review that stuff gets18:37
melwittfun18:37
dansmithI pretty much always name my local branches with bug/X and bp/Y anyway, so I probably wouldn't notice18:38
dansmithbecause I actually don't like that I end up with them different in gerrit vs. local18:38
melwittI'm a renegade18:38
melwitthttps://en.wikipedia.org/wiki/Renegade_(TV_series)18:39
mriedemwas just thinking that18:39
mriedemi had a friend that couldn't leave the house all summer in middle school because his parents made him babysit his sister,18:39
mriedemand he'd be watching renegade every day18:39
melwittlol, an excellent choice18:40
mriedemso we had to go to his house b/c he coudn't leave, but then we had to watch renegade18:40
mriedemwho is lorenzo roundhouse kicking today?18:42
melwittheh18:43
*** BjoernT_ has quit IRC18:46
*** kaisers has quit IRC18:49
*** ricolin has quit IRC18:50
zbrefried: does https://review.opendev.org/#/c/674057/ look ok now?18:54
*** irclogbot_2 has quit IRC18:54
*** irclogbot_0 has joined #openstack-nova18:55
*** ralonsoh has quit IRC18:55
artomI'm a dumbass18:59
artomI spent literally hours, at this point, trying to stub, mock, or hack __dict__ to pin a compute RPC object18:59
artom(Because def router is an @property that can't be set/stubbed, and it's using a global singleton)19:00
*** amrith has joined #openstack-nova19:00
artomWhen what I *should* have done is just inherited from ComputeAPI and overwrote def router >_<19:00
*** irclogbot_0 has quit IRC19:02
*** kaliya has joined #openstack-nova19:02
dansmithcan't you just kill router on the instance that each one gets?19:02
dansmithservice.manager.rpcapi.router = mock.Mock() ?19:03
dansmithor whatever19:03
*** irclogbot_3 has joined #openstack-nova19:03
artom@property makes it un-settable19:03
dansmithcan you delattr it?19:04
artomHuh, didn't think to try that19:04
dansmithanyway, doesn't matter19:04
*** amrith has quit IRC19:12
*** efried has quit IRC19:18
*** efried has joined #openstack-nova19:20
openstackgerritArtom Lifshitz proposed openstack/nova master: NUMA live migration support  https://review.opendev.org/63460619:30
openstackgerritArtom Lifshitz proposed openstack/nova master: Deprecate CONF.workarounds.enable_numa_live_migration  https://review.opendev.org/64002119:30
openstackgerritArtom Lifshitz proposed openstack/nova master: Functional tests for NUMA live migration  https://review.opendev.org/67259519:30
artomdansmith, ^^19:31
artom(FWIW, I had the -patch27 in my local branch name for some reason, fixed that)19:32
* artom picks up daughter from school, back in a few19:32
dansmithartom: one more thing I didn't catch last time, but it's easy19:36
dansmithartom: otherwise I think it looks good, probably time for mriedem to have a go at it19:36
*** kaisers has joined #openstack-nova19:37
aspierscan anyone point me at where the fake server instance object comes from in https://github.com/openstack/nova/blob/master/nova/tests/unit/api/openstack/compute/test_migrate_server.py#L579 ?19:41
aspiersI've trawled through the test setup code and can't find it19:41
aspiersah19:43
aspiersadmin_only_action_common.py19:43
*** gbarros has quit IRC19:44
*** gbarros has joined #openstack-nova19:46
*** ociuhandu has joined #openstack-nova19:47
*** eharney has quit IRC19:51
aspiersstill don't get it19:53
aspiersif I use _stub_instance_get() then I get "Exception: This test uses methods that set internal oslo_db state, but it does not claim to use the database. This will conflict with the setup of tests that do use the database and cause failures later."19:53
melwittaspiers: is there a link to a patch you're working on that will give more context? my first guess is maybe your new test is accessing an attribute on instance that isn't populated, so it's trying to lazy-load it from the database, which is flagging your test as USES_DB = True19:59
openstackgerritMerged openstack/nova master: Remove unused methods  https://review.opendev.org/67991819:59
*** BjoernT has joined #openstack-nova19:59
aspiersmelwitt: I'll upload20:00
melwittthat error comes from a test inheriting from NoDBTestCase and then accessing the database20:01
aspiersmelwitt: does this test avoid it by patching out the meat of the code path (i.e. resize)? https://github.com/openstack/nova/blob/master/nova/tests/unit/api/openstack/compute/test_migrate_server.py#L12420:05
aspiersso it's effectively only testing the HTTP stuff in the top layer?20:05
melwittprobably, that stub will fill in most of the instance objects attributes. so if anything in the code path accesses the attributes, they are already filled in,20:07
melwittwith objects, if an attribute is *not* filled in and it is accessed, the object will fall back on a read from the database to get the value20:07
openstackgerritMerged openstack/nova master: Convert nova-lvm job to zuul v3  https://review.opendev.org/67434520:08
melwittso it will test the full code path, just not the database accesses (if there were going to be any)20:08
efriedsean-k-mooney: in case this doesn't show up in your inbox/dashboard/whatever, would you please respond to this os-vif release patch: https://review.opendev.org/#/c/680094/20:08
aspiersmelwitt: ahhh maybe that's it20:09
*** ociuhandu has quit IRC20:09
*** ociuhandu has joined #openstack-nova20:10
aspiersmelwitt: maybe it's missing the flavor or image_meta20:10
melwittaspiers: so sometimes what happens is you're working on a new test whose code path will access an attribute that's not stubbed out/filled in, and then it falls back on a read from the db, and if you're inherited from NoDBTestCase, that error will raise20:10
aspiersno, just adding a call to self._stub_instance_get() is enough to trigger this db-related failure, *even* if I don't use the returned fake instance20:11
aspiersso it's not my test code which is triggering the error20:11
melwittyeah if you look in https://github.com/openstack/nova/blob/master/nova/tests/unit/fake_instance.py#L45 you can see what's been filled in20:11
aspiersyeah I spotted that20:11
melwittoh, hm20:12
aspiersbut this makes no sense, because other tests happily call that same method20:12
aspiersmelwitt: uploading now20:13
openstackgerritAdam Spiers proposed openstack/nova master: Reject live migration and suspend on SEV guests  https://review.opendev.org/68015820:13
aspiersthere ^^^20:13
aspiersmelwitt: https://review.opendev.org/#/c/680158/1/nova/tests/unit/api/openstack/compute/test_migrate_server.py@592 causes this db error20:14
aspierswhy do other identical lines in the same file not cause it?20:14
melwittat a glance, I notice the other tests calling _stub_instance_get are also mocking the live_migrate method in compute_api20:16
aspiersright, that's what I was saying earlier20:16
aspiersthey mock the meat of the code path20:16
*** aojea has joined #openstack-nova20:17
aspiersbut the call to _stub_instance_get() isn't inside the mocking?!20:17
aspiersso it can't be that20:17
aspierssuper weird20:17
openstackgerritAdam Spiers proposed openstack/nova master: Reject live migration and suspend on SEV guests  https://review.opendev.org/68015820:18
melwittyou're saying the _stub_instance_get call itself will not return and raises that error?20:18
aspiersyes20:18
melwittO.o20:18
melwittok, that is unexpected20:18
aspiersoh no wait20:19
aspiersOK I get it now20:19
aspiers_stub_instance_get() has side effects of course20:19
aspiersit patches stuff20:19
aspiersso it doesn't matter if I don't use the return value20:19
aspiersyeah it's the lookup of instance.image_meta which fails20:20
mriedemdansmith: artom: ack, probably going to have to be in the morning at this point, just got off a call20:21
*** markvoelker has quit IRC20:21
melwittaspiers: where's the lookup? I'm curious20:21
aspiersmelwitt: https://review.opendev.org/#/c/680158/2/nova/compute/api.py@21820:22
aspiersmelwitt: I think my mocking of that hardware method is broken probably20:22
aspiersmocking in the wrong place is my guess20:22
aspiersneed to mock in nova.compute.api20:22
melwittok, I thought you said _stub_instance_get was blowing up itself20:22
aspiersyeah I was wrong20:22
melwittand I was curious where in there it accesses db20:23
melwittok20:23
aspiersohh doh20:24
aspierspatching hardware.get_mem_encryption_constraint doesn't stop the calculation of the parameters being passed to it20:25
aspiersso I have to patch instance.image_meta too, or just set it20:25
*** aojea has quit IRC20:25
*** markvoelker has joined #openstack-nova20:30
dansmithmriedem: np20:31
*** nweinber has quit IRC20:37
*** ociuhandu has quit IRC20:38
aspiersmelwitt: got it working finally20:41
aspiersmelwitt: thanks for your help :)20:41
melwittyay20:41
openstackgerritMerged openstack/nova master: Modernize nova-lvm job  https://review.opendev.org/67435620:43
*** dannins has quit IRC20:45
*** bbowen_ has quit IRC20:45
*** bbowen_ has joined #openstack-nova20:45
openstackgerritAdam Spiers proposed openstack/nova master: Reject live migration and suspend on SEV guests  https://review.opendev.org/68015820:45
aspiersmelwitt: https://review.opendev.org/#/c/680158/2..3/nova/tests/unit/api/openstack/compute/test_suspend_server.py@4720:46
openstackgerritAdam Spiers proposed openstack/nova master: Enable booting of libvirt guests with AMD SEV memory encryption  https://review.opendev.org/66661620:47
melwittaspiers: oh, so you didn't need to stub compute_api20:48
aspiersmelwitt: right, it was just image_meta20:48
aspiersI didn't want to stub compute_api because that's where the desired exception gets thrown20:48
melwittyeah, makes sense20:49
openstackgerritMatt Riedemann proposed openstack/nova master: FUP for I66d8f06f19c5c631e33208580428aa843abb38d2  https://review.opendev.org/67895120:55
aspiersoh crap, circular imports20:57
*** munimeha1 has joined #openstack-nova21:00
aspierswhat's the ASCII smiley for a facepalm?21:01
*** eharney has joined #openstack-nova21:07
*** slaweq has quit IRC21:08
aspiersefried: make sense if I move sev_enabled() from libvirt.utils to virt.hardware to break the circular import?21:09
efriedaspiers: without looking specifically at the patch, that sounds like a reasonable thing.21:10
aspiersI don't think it's possible to move get_mem_encryption_constraint() and its helpers in the other direction21:10
aspierswhich is a shame, cause they're libvirt-specific21:10
efriedexcept that I still resent that nova.virt.hardware is libvirt-specific21:10
aspiersright21:10
efriedyeah21:10
aspiersthing is, they depend _get_flavor_image_meta which is shared21:10
efriedthat ship has sailed though.21:10
aspiersOK21:10
aspiersefried: I suggested to kashyap yesterday that we actually move the machine type stuff to a separate machine_types file21:11
*** slaweq has joined #openstack-nova21:11
aspierslibvirt.utils is a kinda dumb bag of random shit21:11
efriedif you're just grasping for shit to do, you could factor the libvirt-specific stuff out of nova.virt.hardware and into a nova.virt.libvirt.hardware module, leaving anything that's actually generic (assuming there is anything) in nova.virt.hardware.21:11
* aspiers LOLs at the thought of grasping for shit to do21:12
efriedbut we probably have more important things to do21:12
aspiersbut I dunno, maybe I can21:12
aspiershowever I'm very conscious that once this runway window closes, that's my last chance to land SEV in Train gone21:12
aspiersanyway yet again it's 10pm and I haven't had dinner21:13
aspierstime to tear myself away21:13
aspiersefried: parting thought - once I fix the circular import, in *theory* the patch series is code complete (haha how many times have I said that before)21:14
efriedaspiers: That refactor would have nothing to do with the SEV series, runways, or indeed probably Train, as we would likely prefer to wait until ussuri opens to land it.21:15
aspiersefried: cool21:15
*** spatel has quit IRC21:15
aspierswhat do you think about the machine_types.py idea?21:15
*** slaweq has quit IRC21:15
aspiersnova.virt.machine_types21:16
aspiersI don't even know if it's libvirt-specific actually21:16
aspiersI think not21:16
aspiersbut specific to QEMU so ...21:16
aspiersyeah, qemu-kvm -machine help lists them all21:17
* aspiers goes21:18
*** psachin has joined #openstack-nova21:23
donnydmelwitt: dansmith booya21:24
donnydhttps://usercontent.irccloud-cdn.com/file/OdTlIVXX/image.png21:24
dansmithdonnyd: chunk size or something else?21:24
donnydchunk size numbers are looking much mo betta21:24
* melwitt cues the hallelujah song21:24
dansmithsweet21:24
dansmithdonnyd: let me get you an address where you can send the check...21:24
donnydLOL21:25
donnyd5x faster21:26
donnydthat is a pretty big win21:26
melwittyeah, that's awesome. I didn't know about glance chunk size until today21:27
dansmithdonnyd: that was with 16MiB chunks?21:28
donnydyea21:28
dansmithcool21:28
donnydnot sure if I should turn it up anymore or not21:28
dansmithhigher will increase memory usage on the controllers of course21:29
dansmithby at least $chunk_size per parallel download thread I imagine21:29
donnydI think its probably smart to left this settle in for a day or so21:30
donnydI should know in the next 24 hours21:31
dansmithyeah21:31
*** mdbooth has quit IRC21:39
*** takashin has joined #openstack-nova21:41
*** mdbooth has joined #openstack-nova21:46
*** markvoelker has quit IRC21:47
*** munimeha1 has quit IRC21:50
openstackgerritStephen Finucane proposed openstack/nova master: Validate CPU config options against running instances  https://review.opendev.org/68010721:52
openstackgerritStephen Finucane proposed openstack/nova master: objects: Add 'NUMACell.pcpuset' field  https://review.opendev.org/68010821:52
openstackgerritStephen Finucane proposed openstack/nova master: hardware: Differentiate between shared and dedicated CPUs  https://review.opendev.org/67180021:52
openstackgerritStephen Finucane proposed openstack/nova master: libvirt: Start reporting 'HW_CPU_HYPERTHREADING' trait  https://review.opendev.org/67557121:52
openstackgerritStephen Finucane proposed openstack/nova master: Add support for translating CPU policy extra specs, image meta  https://review.opendev.org/67180121:52
openstackgerritStephen Finucane proposed openstack/nova master: Add reshaper for PCPU  https://review.opendev.org/67489521:52
openstackgerritStephen Finucane proposed openstack/nova master: trivial: Use sane indent  https://review.opendev.org/68022921:52
*** edleafe has left #openstack-nova21:55
*** eharney has quit IRC21:56
donnyddansmith: I couldn't resist22:05
donnyd32m is too high22:05
donnyd16m is the sweet spot, and if you are curious dansmith melwitt I can show the data22:05
*** trident has quit IRC22:05
donnydhttps://grafana.fortnebula.com/d/9MMqh8HWk/openstack-utilization?orgId=2&refresh=30s&from=now-1h&to=now&fullscreen&panelId=1422:06
dansmithdonnyd: you went below 16m too I assume?22:06
donnydNo, I should probably test that direction as well22:06
dansmithyeah22:06
melwittcool donnyd, that's good to know. I've already told penick about it and he's gonna check their settings too :)22:08
donnydThat link i just sent has the data to show the difference in both upload and download speeds at different chunk sizes22:09
*** mriedem has quit IRC22:11
*** slaweq has joined #openstack-nova22:11
donnydmaybe I should note that in the glance docs or something22:11
*** trident has joined #openstack-nova22:14
donnydmaximum d/l speed at 32m is 3Gs / 16m is 8G/s /8m 6.5G/s22:15
donnydso it looks like 16m is the sweet spot for at least my infra22:15
*** slaweq has quit IRC22:15
donnydThanks again.. this was really the only thing i was unhappy with on FN...22:16
donnydwoot woot!!!22:16
melwittyay22:16
donnydhttps://grafana.fortnebula.com/d/9MMqh8HWk/openstack-utilization?orgId=2&from=1567633743742&to=1567635376855&fullscreen&panelId=1422:16
melwittI'm glad to know what the issue was. I've been wondering about it22:16
donnydand here is 32-8 left to right22:16
donnydme too22:17
donnydLOL melwitt22:17
melwitthaha xD22:17
donnydIts that dinner time around here22:17
* donnyd goes to eat dinner with a giant grin22:17
melwitto/22:17
*** mlavalle has quit IRC22:21
*** jhesketh has quit IRC22:27
aspiersefried: hmm, other option for breaking the cycle is to move get_machine_type() from utils to new machine_types.py22:30
aspiersmaybe that's better22:31
*** psachin has quit IRC22:31
aspiers(than moving libvirt-specific sev_enabled() to virt.hardware)22:31
*** jhesketh has joined #openstack-nova22:33
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (13)  https://review.opendev.org/57602022:35
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (14)  https://review.opendev.org/57602722:35
*** markvoelker has joined #openstack-nova22:35
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (15)  https://review.opendev.org/57603122:37
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (16)  https://review.opendev.org/57629922:37
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (17)  https://review.opendev.org/57634422:37
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (18)  https://review.opendev.org/57667322:38
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (19)  https://review.opendev.org/57667622:38
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (20)  https://review.opendev.org/57668922:38
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (21)  https://review.opendev.org/57670922:38
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (22)  https://review.opendev.org/57671222:39
*** markvoelker has quit IRC22:40
*** KeithMnemonic has quit IRC22:43
*** KeithMnemonic1 has joined #openstack-nova22:43
*** macz has quit IRC22:56
*** tkajinam has joined #openstack-nova22:58
*** rcernin has joined #openstack-nova23:04
*** luksky has quit IRC23:09
*** slaweq has joined #openstack-nova23:11
*** slaweq has quit IRC23:16
*** threestrands has joined #openstack-nova23:17
openstackgerritNathan Kinder proposed openstack/nova master: Allow TLS ciphers/protocols to be configurable for console proxies  https://review.opendev.org/67950223:30
*** macz has joined #openstack-nova23:32
*** sapd1_x has joined #openstack-nova23:34
*** ozzzo has joined #openstack-nova23:34
*** macz has quit IRC23:50
*** trident has quit IRC23:52
*** BjoernT has quit IRC23:53
*** BjoernT has joined #openstack-nova23:53
*** BjoernT has quit IRC23:54
*** BjoernT_ has joined #openstack-nova23:54
brinzhangmriedem: pretty good, thanks23:54
*** BjoernT_ has quit IRC23:54
*** BjoernT has joined #openstack-nova23:55
*** BjoernT has quit IRC23:55
*** BjoernT_ has joined #openstack-nova23:55
*** BjoernT_ has quit IRC23:56
*** BjoernT has joined #openstack-nova23:56
*** BjoernT has quit IRC23:57
*** BjoernT_ has joined #openstack-nova23:57
*** BjoernT_ has quit IRC23:58
*** BjoernT has joined #openstack-nova23:58
*** BjoernT has quit IRC23:58
*** BjoernT_ has joined #openstack-nova23:59
*** BjoernT_ has quit IRC23:59
*** BjoernT has joined #openstack-nova23:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!