Monday, 2019-08-12

*** brinzhang has joined #openstack-nova00:33
*** yedongcan has joined #openstack-nova03:03
*** brinzhang_ has joined #openstack-nova03:25
*** brinzhang has quit IRC03:30
*** psachin has joined #openstack-nova03:35
*** udesale has joined #openstack-nova04:04
*** ash2307 has quit IRC04:15
*** ash2307 has joined #openstack-nova04:18
*** toabctl has quit IRC04:21
*** toabctl has joined #openstack-nova04:24
openstackgerritLuyao Zhong proposed openstack/nova master: Add the virt driver interface for claim and unclaim the devices  https://review.opendev.org/67078205:02
openstackgerritLuyao Zhong proposed openstack/nova master: Moves the allocation retrieving early  https://review.opendev.org/67078305:02
openstackgerritLuyao Zhong proposed openstack/nova master: Calling the virt driver's claim/unclaim_for_instance in resource tracker  https://review.opendev.org/67078405:02
openstackgerritLuyao Zhong proposed openstack/nova master: Add DeviceManager to the libvirt virt driver  https://review.opendev.org/67138805:02
openstackgerritLuyao Zhong proposed openstack/nova master: Populates the existing mediated devices in the libvirt device manager  https://review.opendev.org/67078705:02
openstackgerritLuyao Zhong proposed openstack/nova master: Using the claim/unclaim_for_instance for mdevs  https://review.opendev.org/67122205:02
openstackgerritLuyao Zhong proposed openstack/nova master: Adds functional test for creating the instance with vgpus  https://review.opendev.org/67139805:02
openstackgerritLuyao Zhong proposed openstack/nova master: Add functional tests for resize with VGPU  https://review.opendev.org/67510605:02
openstackgerritLuyao Zhong proposed openstack/nova master: Indroduce new LibvirtConfigGuestPMEM  https://review.opendev.org/67295605:02
openstackgerritLuyao Zhong proposed openstack/nova master: Populates existing pmems in libvirt device manager  https://review.opendev.org/67295705:02
openstackgerritLuyao Zhong proposed openstack/nova master: Report pmem namespaces resources by provider tree  https://review.opendev.org/63455105:02
openstackgerritLuyao Zhong proposed openstack/nova master: Support instance creation and resize with pmems  https://review.opendev.org/67295805:02
openstackgerritLuyao Zhong proposed openstack/nova master: Add functional tests for persistent memory  https://review.opendev.org/67559205:02
*** pcaruana has joined #openstack-nova05:29
*** ratailor has joined #openstack-nova05:35
*** pcaruana has quit IRC05:37
*** janki has joined #openstack-nova05:48
*** pcaruana has joined #openstack-nova05:50
*** dpawlik has joined #openstack-nova06:08
*** mkrai has joined #openstack-nova06:11
*** markvoelker has joined #openstack-nova06:31
*** slaweq has joined #openstack-nova06:33
*** markvoelker has quit IRC06:36
*** mkrai has quit IRC06:45
*** mkrai_ has joined #openstack-nova06:45
*** yaawang has quit IRC07:00
*** yaawang has joined #openstack-nova07:01
*** mjozefcz has joined #openstack-nova07:04
*** ivve has joined #openstack-nova07:05
*** luksky has joined #openstack-nova07:09
*** rcernin has quit IRC07:13
*** tesseract has joined #openstack-nova07:14
lennybstephenfin: Hi, please review #https://review.opendev.org/#/c/675776/  revert that broke MacVtap.07:17
*** aojea has joined #openstack-nova07:18
*** aojeagarcia has joined #openstack-nova07:18
*** damien_r has joined #openstack-nova07:23
*** aojea has quit IRC07:27
*** panda has quit IRC07:30
*** panda has joined #openstack-nova07:33
openstackgerritBrin Zhang proposed openstack/nova-specs master: Support re-configure deleted_on_termination in server  https://review.opendev.org/58033607:40
*** zbr is now known as zbr|flu07:47
*** mkrai_ has quit IRC07:54
*** helenafm has joined #openstack-nova07:54
*** rpittau|afk is now known as rpittau07:54
*** mkrai has joined #openstack-nova07:55
*** cdent has joined #openstack-nova08:12
*** janki has quit IRC08:16
*** janki has joined #openstack-nova08:17
*** jchhatbar has joined #openstack-nova08:18
*** janki has quit IRC08:22
*** cdent has quit IRC08:33
*** cdent has joined #openstack-nova08:33
*** derekh has joined #openstack-nova08:37
*** tesseract has quit IRC08:42
*** slaweq has quit IRC08:42
*** ash2307 has quit IRC08:42
*** brinzhang_ has quit IRC08:42
*** yedongcan has quit IRC08:42
*** irclogbot_1 has quit IRC08:42
*** yonglihe has quit IRC08:42
*** mordred has joined #openstack-nova08:43
*** brinzhang_ has joined #openstack-nova08:43
*** slaweq has joined #openstack-nova08:43
*** ash2307 has joined #openstack-nova08:43
*** tesseract has joined #openstack-nova08:43
*** brinzhang_ has quit IRC08:43
*** brinzhang_ has joined #openstack-nova08:44
*** jchhatbar has quit IRC08:44
*** brinzhang has joined #openstack-nova08:45
*** openstackgerrit has quit IRC08:45
*** yedongcan has joined #openstack-nova08:47
*** irclogbot_1 has joined #openstack-nova08:47
*** yonglihe has joined #openstack-nova08:47
*** irclogbot_1 has quit IRC08:49
*** irclogbot_3 has joined #openstack-nova08:52
*** ociuhandu has joined #openstack-nova09:05
*** jaosorior has joined #openstack-nova09:07
*** ociuhandu has quit IRC09:17
*** ociuhandu has joined #openstack-nova09:22
*** tssurya has joined #openstack-nova09:40
*** ociuhandu has quit IRC09:41
*** shilpasd has joined #openstack-nova09:45
*** mvkr has joined #openstack-nova09:47
*** xek has joined #openstack-nova09:57
*** ociuhandu has joined #openstack-nova09:59
*** ociuhandu has quit IRC10:01
*** ociuhandu has joined #openstack-nova10:01
*** brinzhang_ has joined #openstack-nova10:08
*** sapd1_x has joined #openstack-nova10:08
*** markvoelker has joined #openstack-nova10:09
*** brinzhang has quit IRC10:12
*** markvoelker has quit IRC10:14
*** kaisers has quit IRC10:16
*** sapd1_x has quit IRC10:16
*** artom has joined #openstack-nova10:17
*** kaisers has joined #openstack-nova10:18
*** ociuhandu has quit IRC10:20
*** ociuhandu has joined #openstack-nova10:21
*** ksdean has joined #openstack-nova10:28
*** ksdean has quit IRC10:28
*** ksdean has joined #openstack-nova10:29
sean-k-mooney /away10:38
*** openstackgerrit has joined #openstack-nova10:41
openstackgerritBalazs Gibizer proposed openstack/nova master: re-calculate provider mapping during migration  https://review.opendev.org/65511210:41
*** pcaruana has quit IRC10:43
openstackgerritBalazs Gibizer proposed openstack/nova master: update allocation in binding profile during migrate  https://review.opendev.org/65642210:43
*** pcaruana has joined #openstack-nova10:43
openstackgerritBalazs Gibizer proposed openstack/nova master: Extend NeutronFixture to handle migrations  https://review.opendev.org/65511410:45
openstackgerritBalazs Gibizer proposed openstack/nova master: prepare func test env for moving servers with bandwidth  https://review.opendev.org/65510910:47
openstackgerritBalazs Gibizer proposed openstack/nova master: func test for migrate server with ports having resource request  https://review.opendev.org/65511310:49
*** yonglihe has quit IRC10:49
openstackgerritBalazs Gibizer proposed openstack/nova master: Allow migrating server with port resource request  https://review.opendev.org/67149710:51
*** jaosorior has quit IRC10:54
*** janki has joined #openstack-nova11:08
*** whoami-rajat has joined #openstack-nova11:08
sean-k-mooneystephenfin: im going to move the validate_trait function form https://review.opendev.org/#/c/665775/10 into the first patch https://review.opendev.org/#/c/666914/6 and cache it. once its cached i can then vaildate the traits more libarlly as i am creating them.11:13
sean-k-mooneywhat should be the behavior for invalid traits11:14
sean-k-mooneyskip them and log a warning or  something else11:14
*** udesale has quit IRC11:18
openstackgerritLuyao Zhong proposed openstack/nova master: Add functional tests for persistent memory  https://review.opendev.org/67559211:21
*** ratailor has quit IRC11:24
*** ociuhandu has quit IRC11:27
*** ociuhandu has joined #openstack-nova11:27
*** ociuhandu_ has joined #openstack-nova11:28
*** ociuhandu has quit IRC11:32
*** cooldharma06 has joined #openstack-nova11:36
cooldharma06hi all is nova rebuild option support uerdata.?11:37
sean-k-mooneycooldharma06: i cant recall if we added support for that or ssh keys recently but it support one fo the two11:40
sean-k-mooneycooldharma06: it support both  on master https://docs.openstack.org/api-ref/compute/?expanded=rebuild-server-rebuild-action-detail#rebuild-server-rebuild-action11:41
sean-k-mooneyNew in version 2.5711:41
*** ociuhandu_ has quit IRC11:44
cooldharma06sean-k-mooney: https://review.opendev.org/#/c/431052/ in this commit they mentioned like it will be added later11:45
cooldharma06i need to add some extra routes during nova rebuild so i thought i can acheive using rebuild11:46
sean-k-mooneythat is a spec from pike i think we implemented it seperatly11:46
cooldharma06ok thank you. In nova rebuild cli is there any explicit parameter or i need to pass userdata in some other form.?11:48
sean-k-mooneykey pairs was added with https://specs.openstack.org/openstack/nova-specs/specs/queens/implemented/rebuild-keypair-reset.html in queens i dont see a spec for user data but sicne it was added in a later micro version it was added in or after queens11:49
cooldharma06sean-k-mooney oops i am using pike in my environment11:51
*** janki has quit IRC11:51
sean-k-mooneyon master you can do nova rebuild --os-compute-api-version '2.57' --user-data <data in base64>11:52
sean-k-mooneypike does not have support for this sorry11:52
sean-k-mooneycooldharma06: normally you would add routes via neutron11:52
sean-k-mooneynot via userdata11:52
sean-k-mooneyyou would update teh subnet with addtional routes11:53
sean-k-mooneyand they will be served via dhcp11:53
*** janki has joined #openstack-nova11:53
*** brinzhang_ has quit IRC11:53
*** brinzhang_ has joined #openstack-nova11:54
cooldharma06actually i want to add route to only to that particular exiting machine11:58
cooldharma06so i thought to try with rebuild option with extra routes11:58
sean-k-mooneya post boot ansible sricpt/ssh is proably a better option.11:59
cooldharma06post boot will work i think.. thank you i ll try this one12:00
cooldharma06thanks for your time and info.. :)12:01
*** ociuhandu has joined #openstack-nova12:03
*** jaosorior has joined #openstack-nova12:03
*** ash2307 has left #openstack-nova12:04
*** ociuhandu has quit IRC12:08
*** pas-ha has quit IRC12:13
*** pas-ha has joined #openstack-nova12:14
*** vdrok has quit IRC12:14
*** vdrok has joined #openstack-nova12:14
*** priteau has joined #openstack-nova12:20
openstackgerritBalazs Gibizer proposed openstack/nova master: allow getting resource request of every bound ports of an instance  https://review.opendev.org/65511012:23
*** mjozefcz has quit IRC12:23
openstackgerritBalazs Gibizer proposed openstack/nova master: Pass network API to the conducor's MigrationTask  https://review.opendev.org/65511112:25
*** mjozefcz has joined #openstack-nova12:26
*** mjozefcz has quit IRC12:26
openstackgerritBalazs Gibizer proposed openstack/nova master: Add request_spec to server move RPC calls  https://review.opendev.org/65572112:27
*** mjozefcz has joined #openstack-nova12:27
*** markvoelker has joined #openstack-nova12:28
openstackgerritBalazs Gibizer proposed openstack/nova master: re-calculate provider mapping during migration  https://review.opendev.org/65511212:28
*** edleafe has joined #openstack-nova12:29
openstackgerritBalazs Gibizer proposed openstack/nova master: update allocation in binding profile during migrate  https://review.opendev.org/65642212:30
openstackgerritBalazs Gibizer proposed openstack/nova master: Extend NeutronFixture to handle migrations  https://review.opendev.org/65511412:30
openstackgerritBalazs Gibizer proposed openstack/nova master: prepare func test env for moving servers with bandwidth  https://review.opendev.org/65510912:34
*** nweinber has joined #openstack-nova12:34
openstackgerritBalazs Gibizer proposed openstack/nova master: func test for migrate server with ports having resource request  https://review.opendev.org/65511312:36
openstackgerritBalazs Gibizer proposed openstack/nova master: Allow migrating server with port resource request  https://review.opendev.org/67149712:36
*** ociuhandu has joined #openstack-nova12:36
*** nweinber_ has joined #openstack-nova12:37
*** nweinber has quit IRC12:40
*** ociuhandu has quit IRC12:41
*** jchhatbar has joined #openstack-nova12:47
*** jchhatbar has quit IRC12:48
*** jchhatbar has joined #openstack-nova12:48
*** janki has quit IRC12:50
openstackgerritEric Fried proposed openstack/nova master: Introduces SDK to IronicDriver and uses for node.get  https://review.opendev.org/64289912:50
*** _mmethot_ is now known as mmethot12:52
*** jchhatbar has quit IRC12:52
openstackgerritMerged openstack/nova master: Cache host to cell mapping in HostManager  https://review.opendev.org/66338812:55
openstackgerritMerged openstack/nova master: Update comments in HostManager._get_instance_info  https://review.opendev.org/67492912:55
*** jroll has quit IRC13:01
*** jroll has joined #openstack-nova13:02
*** yedongcan has left #openstack-nova13:03
*** beagles has joined #openstack-nova13:05
*** slaweq has quit IRC13:08
*** luksky has quit IRC13:08
*** janki has joined #openstack-nova13:09
*** efried_pto is now known as efried13:09
*** slaweq has joined #openstack-nova13:11
*** cooldharma06 has quit IRC13:15
*** mriedem has joined #openstack-nova13:18
*** frickler has quit IRC13:18
*** brinzhang_ has quit IRC13:18
*** priteau has quit IRC13:18
*** brinzhang_ has joined #openstack-nova13:18
*** priteau has joined #openstack-nova13:19
*** mchlumsky has joined #openstack-nova13:25
stephenfinsean-k-mooney:13:29
stephenfinsean-k-mooney: I think we just skip them?13:29
sean-k-mooneyok13:29
stephenfinThe alternative is to hardcode a mapping of vif types to traits, but maybe that's needlessly complex?13:29
stephenfinOr we can just add a unit test to validate things13:30
*** udesale has joined #openstack-nova13:30
sean-k-mooneywell i am validating them13:30
sean-k-mooneyjust later13:30
sean-k-mooneywhen i am doing the actual update13:30
sean-k-mooneysorry im validating them in the filter13:30
sean-k-mooneynot in the dirver13:31
stephenfinOh, if they're already validated somewhere then it doesn't matter13:31
sean-k-mooneyanyway ill skip them and log a warning13:31
sean-k-mooneyi should filter them out in the driver13:31
sean-k-mooneybut i want to cache the validation function as its not that cheap and i dont want to pay the cost on every request/update13:32
sean-k-mooneyit would also be nice to be able to add new vif_models without needing ot update placement first13:32
sean-k-mooneyi should still poing out however the validation only ensure that the version of placemetn install in the nova compute node thinks its valid not that the plamcent service thinks its valid13:33
*** frickler has joined #openstack-nova13:34
sean-k-mooneywe really dont want to be making restcall to placemetn to validate it direclty13:35
sean-k-mooneythat would be more expesive then the current validation13:35
*** boxiang has quit IRC13:37
mriedemlyarwood: can you hit this queens backport https://review.opendev.org/#/c/659247/ and then we can release queens13:38
alex_xuefried: dansmith, good morning, I updated the vpmem spec https://review.opendev.org/67502413:38
efriednoted13:39
sean-k-mooneyoh disabling limit for affinity. i remember talking about that at the ptg13:39
lyarwoodmriedem: ack done13:40
*** mkrai has quit IRC13:41
sean-k-mooneylyarwood: actully we had a customer issue related to no valid host with anti-affinity that coudl be releated too that? although have said that i dont think we set a limmit so the defualt would be 1000 and then had like 50 host so proably not13:42
sean-k-mooneythat would be good for larger deployment in anycase.13:42
lyarwoodsean-k-mooney: I can't recall it if we did13:43
sean-k-mooneydhill was handeling it but i tink we concluded they were just running out of space.13:43
sean-k-mooneye.g. the only host that still had enough capsaity were the host the anti afinity filter elminated13:44
sean-k-mooneyi dont think there was actully something broken in the end.13:45
*** ociuhandu has joined #openstack-nova13:50
*** mchlumsky has quit IRC13:52
openstackgerritEric Fried proposed openstack/nova master: Multiple API cleanup changes  https://review.opendev.org/66688913:52
*** mchlumsky has joined #openstack-nova13:53
*** beekneemech is now known as bnemec13:54
efriedstephenfin and/or johnthetubaguy, That ^ is pretty much a "rebase" if you want to reapprove.13:54
*** KeithMnemonic has joined #openstack-nova13:54
*** nweinber__ has joined #openstack-nova13:56
*** janki has quit IRC13:57
*** BjoernT has joined #openstack-nova13:59
*** nweinber_ has quit IRC13:59
*** mkrai has joined #openstack-nova13:59
*** atmark has joined #openstack-nova14:00
stephenfinefried: Sure thing14:00
efriedthanks14:01
*** BjoernT_ has joined #openstack-nova14:04
*** BjoernT has quit IRC14:05
openstackgerritStephen Finucane proposed openstack/nova master: DRY get_flavor in flavor manage tests  https://review.opendev.org/66828114:06
*** luksky has joined #openstack-nova14:06
*** udesale has quit IRC14:06
*** udesale has joined #openstack-nova14:08
*** udesale has quit IRC14:08
*** udesale has joined #openstack-nova14:08
*** eharney has joined #openstack-nova14:15
efriedstephenfin, johnthetubaguy: If y'all are still in a reviewy mood, this series has my +2 all the way up and its runway slot expires today: https://review.opendev.org/#/q/topic:bp/placement-req-filter-forbidden-aggregates+(status:open+OR+status:merged)14:16
efriedfor whatever reason, I think it's a pretty cool feature14:16
efriedmriedem: Wanna move cross-cell resize into the runway?14:17
*** dpawlik has quit IRC14:17
mriedemsure14:18
openstackgerritFilippo Inzaghi proposed openstack/nova-specs master: Add Python 3 Train unit tests  https://review.opendev.org/67590814:20
*** slaweq has quit IRC14:20
*** slaweq has joined #openstack-nova14:21
stephenfinmriedem, efried: Dumb question, but the semaphore here means literally every other kind of operation (delete, (live) migrate, resize, etc.) on that instances is prevented until this eventually, returns, yeah? https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1867-L186814:21
stephenfinAssuming those operations are all wrapped with the same semaphore14:21
mriedemstephenfin: you can't live migrate/resize an instance that's being built14:22
mriedemdelete yes https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L280114:22
stephenfinOkay, cool. I'm trying to invent reproducers for both https://review.opendev.org/#/c/663382/ and https://review.opendev.org/#/c/667294/14:23
stephenfinSomething that doesn't involve Heat, that is14:24
stephenfinand trying to grok what could be stomping on what. Fun times :)14:25
tssuryaefried, mriedem: whenever you have time could you circle back to https://review.opendev.org/#/c/645611/ ? I think you were mostly ok on it, but just want to confirm if there is anything more to do there before I go on vacation14:28
tssuryathanks in advance14:28
*** mkrai has quit IRC14:35
mriedemtssurya: i won't +2 that until the ironic side is happy, since without that there is no point in the nova changes14:35
tssuryamriedem: they are afaik, I will ask them to leave a comment in today's meeting14:36
*** tbachman has joined #openstack-nova14:37
dansmithmriedem: tssurya who is/are the ironic person(s) that we should look to for sign-off there?14:38
mriedemtssurya: also, you're going to have to rebase https://review.opendev.org/#/c/666889/14:38
tssuryadansmith: dtantsur, TheJulia are the ones who have been reviewing it14:39
dansmithokay14:39
tssuryamriedem: gdi, thanks for letting me know14:39
dansmithhah14:40
tssuryathat means I need to again change the version on the ironic side also14:40
dansmithwe've ruined tssurya  :)14:40
tssuryadansmith: tear emoji14:40
mriedemused to be so innocent14:40
mriedemhttps://review.opendev.org/#/q/file:%255Enova/api/openstack/compute/rest_api_version_history.rst+status:open14:40
dansmithtssurya: I meant ruined because we've got you swearing when api versions change :P14:40
tssuryadansmith: true that14:41
dansmithtssurya: I say rebase that one on the cleanup to fix the version, and the ironic side, and let's push to get the acks in place so we can try to get it landed before it happens again14:41
tssuryamy office mate thinks I am swearing at him14:41
dansmithheh14:41
tssuryadansmith: ack, on it14:41
*** mlavalle has joined #openstack-nova14:41
TheJuliatssurya: will order of merging matter? Trying to figure out if I should try and get more eyes on the ironic side this week14:45
tssuryanova one has to land first technically, but they just want to know if the ironic client side change looks good14:46
tssuryaTheJulia: more eyes this week would be great14:47
dansmithwhat tssurya said14:47
TheJuliatssurya: ack14:47
*** aojeagarcia has quit IRC14:50
efriedtssurya: Do you have someone to take over for you if changes are needed while you're sipping mai tais on the beach?14:50
*** ash2307 has joined #openstack-nova14:51
*** ash2307 has left #openstack-nova14:52
*** belmoreira has joined #openstack-nova14:53
*** nweinber_ has joined #openstack-nova14:54
*** nweinber__ has quit IRC14:57
cdentmriedem, dansmith : What do you imagine the consequences of moving the get_by_host_node in _update_available_resource out from under the COMPUTE_RESOURCE_SEMAPHORE would be? https://github.com/openstack/nova/blob/52b9359d6c6f387b8b9728c723c9a2501136d605/nova/compute/resource_tracker.py#L74414:58
cdenton a host with many insgtn14:58
cdentoopes14:58
cdentoh a host with many instances, that lock blocks new instance creation14:58
cdentand a large portion of the time under the lock is spent in get_by_host_and_node assuming the is_bfv cache is hot (if it's cold it is _all_ there)15:00
sean-k-mooneycdent: you might be able to optimise it without fully removing the lock. e.g. caulate the usage for each instance without the lock and keep track of the instace checked. aquire the lock and check that all instace check are still present and no others have been added then update the usage and release the lock.15:01
sean-k-mooneyif an instance has been added or removed then you can just make that update under the lock.15:01
mriedemcdent: the consequence could be a race where we don't report usage or claim properly because the underlying resource usage changed since we got the lock15:02
cdentmriedem: are you certain? I'm not saying remove the lock. I'm saying not use the lock while getting the list of instances used by _update_available_resources15:03
mriedemi know what you're asking15:03
cdentlock _after_ getting the list15:03
mriedemyou're saying move the get here https://github.com/openstack/nova/blob/52b9359d6c6f387b8b9728c723c9a2501136d605/nova/compute/resource_tracker.py#L71015:03
mriedemand pass the instances into _update_available_resource15:04
mriedemsean-k-mooney: how would you know if an instance has been added or removed?15:04
mriedembetween the time you got the list and got the lock?15:04
mriedemcdent: presumably you could have:15:05
sean-k-mooneyyou would have to key two list of instances. one that you got outside the lock and then inside it you would get the list again15:05
sean-k-mooneyyou can then caulated teh added and removed instances15:05
mriedemt0: thread 1 is getting the list of instances on the host, t1: thread 2 gets the lock and is adding a new instance claim to the host which won't be in the list returned in thread 1, t2: thread 1 gets the lock with a list of instances that doesn't include the one from thread215:05
mriedemsean-k-mooney: getting hte list again within the lock defeats the purpose of what cdent is trying to do15:06
sean-k-mooneyif the list are the same the pending updats shoudl be correct if not you either need to recaulate it entirely or comute the delta15:06
mriedemwhich is reduce the amount of time spent *within* the lock15:06
cdentyes, that is the goal15:06
mriedemb/c vcenter has 1000+ instances on the same compute service host / RT15:06
mriedemso getting 1000+ instances for every instance operation on the same host is blocked by this big lock15:06
sean-k-mooneygetting the list shouldnt be the moest expensive part though right its caulating the useage?15:06
mriedemit's 1000+ instances + several joins to other tables15:07
sean-k-mooneye.g. https://github.com/openstack/nova/blob/52b9359d6c6f387b8b9728c723c9a2501136d605/nova/compute/resource_tracker.py#L751-L75215:07
mriedemover rpc as well....15:07
mriedemcdent: i'm curious, what does vio set for rpc_response_timeout?15:07
mriedemconsidering something like this has to pull 1K instances from the db over rpc15:07
cdentgetting the instances is by far the most expensive chunk of _update_avail when you have many instances15:07
mriedemreminds me of this https://review.opendev.org/#/c/633042/15:08
cdentmriedem: something relatively high, but it's not _that_ slow as to cause a problem, rather that the lock can be around for a long time15:08
sean-k-mooneymriedem: 1000+ on vmware because its clustering multiple server under one compute service15:08
mriedemsean-k-mooney: yes15:08
mriedemcdent: but over the default 60 seconds?15:08
*** ociuhandu has quit IRC15:08
sean-k-mooneycdent: ok that is surprising to me but if that is the most expesnive part then yes my suggestion wont help15:09
cdentmriedem: I don't have the details to hand, but yes15:09
mriedemcdent: you could potentially detect if you lost a race if there is something in self.tracked_instances that isn't in the list of instances you just pulled from the db15:09
cdentsean-k-mooney: it depends on whether you are doing the loop the first time or subsequence times. 1st time is_bfv is the expensive part15:09
*** ociuhandu has joined #openstack-nova15:10
sean-k-mooneyi had expected self._update_usage_from_instances ot be more costly15:10
cdentsean-k-mooney: yes, when bfv cache is cold, not but not otherwise15:10
mriedemcdent: i'm assuming is_bfv is expensive since it has to make the is_volume_backed call which needs to get the bdms15:10
cdentmriedem: yes15:10
cdentand 1000 of those adds up15:10
mriedemyeah...there is a change floating around where i asked someone if they could put a sqla joined field on the instances model to detect in a join query if an instance is volume-backed so we could optimize that15:11
mriedemsec15:11
mriedemthe logic is pretty simple i think - is there a boot_index=0 bdm with destination_type=volume for this instance15:11
mriedemif so, it's bfv15:11
cdentonce the cache is hot, it disappears as a problem which suggests that a similar instance cache would have similar properties...15:12
cdentbut managing such a cache is...tricky15:12
mriedemwell, my point is,15:12
cdentbut is exactly what I would think a "resource tracker" would do...15:12
mriedemrather than (1) big InstanceList.get and then (2) big is_bfv cache build, if we could get the is_bfv value per instance in (1) then we avoid (2)15:12
mriedemhttps://review.opendev.org/#/c/612626/10/nova/db/sqlalchemy/api.py15:13
cdentsure, but that only helps on the first trip, right?15:13
efriedtssurya: I left a handful of comments as well15:14
cdentbtw: have you seen my comments about how the eventlet profiler gets all chundered up when RPC is in play?15:14
mriedemno15:14
efriedcdent: just commented on that, I don't think n-cpu is supposed to talk to the db.15:14
cdentturning off the indirection_api fixes it15:14
cdentefried: only for hypervisor isolation, which is not a problem for vsphere...15:15
* efried crawls back into ignorant hole15:15
mriedemcdent: efried: it's not just isolation, it's also to support rolling upgrades15:15
cdentand for profiling/testing is not an issue15:15
*** ociuhandu has quit IRC15:15
cdentwhich vsphere doesn't do either :)15:15
mriedemtemporarily disabling for profilng is one thing15:15
*** tbachman has quit IRC15:15
cdentyeah, I wouldn't suggest there being some kind of config setting for it15:16
mriedemwe need a mogan for nova+ironic and a vogan for nova+vmware15:16
mriedemand nova can then just be kvm like it already is15:16
cdenti actually think that's probalby a good idea, sadly15:16
cdenttrying to be all things to many things is terrible15:16
mriedemcdent: anyway, i'd probably investigate trying to detect races by comparing the instances you get from the db to the set of tracked_instances in the rt after you get the lock15:17
mriedemand determine if you need to adjust your 'instances' like which might just be re-getting it15:17
mriedemand then, like run rally against that to see if you can break it? idk.15:17
cdentI'm still unclear on where a lost race experiences a problem. what breaks15:17
mriedemclaims related stuff, which at this point is numa/pci i think,15:18
sean-k-mooneyi think it woudl only be an issue for resouce that are not tracked in placmenet15:18
mriedemsince we just removed the cpu/ram/disk claims15:18
*** tssurya has quit IRC15:18
mriedemtracked_migrations could also be wonky but on a smaller scale / tighter race15:20
*** ociuhandu has joined #openstack-nova15:20
* mriedem is fixing a bug in the RT as we speak15:20
cdentgo RT15:20
*** dave-mccowan has joined #openstack-nova15:20
sean-k-mooneywell anythin relying  on the perodic task to fix up allocation could be off but it should get fixed on the next run15:21
*** tssurya has joined #openstack-nova15:21
sean-k-mooneymissing frees is not that concuerning but missing claims would be15:21
cdentsean-k-mooney: yeah, which ought to be fine15:21
mriedemsean-k-mooney: the periodic doesn't fix up allocations...15:21
mriedemnot since ocata/pike anyway15:21
sean-k-mooneyout side of the migration ones? i though it healed allcoation for instace once the migration was conrimed15:22
mriedemthe rt does not do that15:23
cdentsure it does: it spends lots of time in here: https://github.com/openstack/nova/blob/52b9359d6c6f387b8b9728c723c9a2501136d605/nova/compute/resource_tracker.py#L131415:23
mriedemthe compute manager explicitly does stuff with migration-based allocations15:23
cdentorphans15:23
cdentever single allocation for instance.uuid is compared to each instance on the host15:23
mriedemcdent: that's about it since all of the other allocation "healing" code was removed15:23
cdentthat chunk can get really loud becuase of https://github.com/openstack/nova/blob/52b9359d6c6f387b8b9728c723c9a2501136d605/nova/compute/resource_tracker.py#L134015:24
cdentcommenting out that line can save a bunch of log noise15:24
*** tbachman has joined #openstack-nova15:24
mriedemdebug("things are working normally")15:24
cdentand 1372 there is one last remove15:24
sean-k-mooneymriedem: i dont know im suspios that we normally would print that :P15:25
*** luksky has quit IRC15:26
sean-k-mooneybut yes that does not really add much value15:26
cdentif you both agree, I can put up a patch to remove it?15:26
cdentmeanwhile, I will create 1000 fake instances again15:26
mriedemthere used to be an audit level which is lower than debug, i'm not sure i'm totally in favor of removing it,15:27
mriedemas the comment at the top says,15:27
mriedem# NOTE(jaypipes): All of this code sucks.15:27
mriedembut when i'm debugging rt issues, the more logging i have the better15:27
cdenttrue15:27
mriedemi frequently have to add logging to the rt when i'm debugging functional test fialures that involve it (like i was on friday for at least 2 hours)15:27
cdentme too15:27
cdenti have at least 6 additional LOG.debug in there right now15:28
sean-k-mooneyya that is fair15:28
mriedemhttps://review.opendev.org/#/c/366422/15:28
sean-k-mooneywe do have a way to filter out log messages via config too right15:28
*** slaweq has quit IRC15:28
mriedemi said AUDIT but i was thinking TRACE15:28
redkrieglyarwood: Are you around by chance?  I found your blueprint for stable disk devices in rescue mode and it's exactly what I need to offer my customers reliable ISO support.  Just wanted to know what the status is and whether there's anything I can work on related to it to get it in a release in the future: https://blueprints.launchpad.net/nova/+spec/virt-rescue-stable-disk-devices15:29
*** slaweq has joined #openstack-nova15:30
sean-k-mooneyjust based on the ordering in the gate logs http://logs.openstack.org/38/671338/5/check/tempest-full-py3/12e1ea1/controller/logs/screen-n-cpu.txt.gz15:30
sean-k-mooneyi would have guess audit and trace were both higher then info/debug15:31
mriedemi don't know how to filter specific messages from logging config15:31
sean-k-mooneyi think we can do it at the module level but i dont know if we can do it at the function level. we cant do it on indigiual message via config so it proably too course for this usecase15:32
sean-k-mooneyi.e. we dont want to jsut make the RT be info and everything else debug15:32
sean-k-mooneyi guess that message does serve a use in confiming which branch is taken15:33
sean-k-mooneybut for ops that run at debug level in production its proably noisier then they would like15:34
openstackgerritBalazs Gibizer proposed openstack/nova master: Avoid timeout from service update notification tests  https://review.opendev.org/67593515:36
mriedemlow-hanging-fruit test-only bug https://bugs.launchpad.net/nova/+bug/183985315:40
openstackLaunchpad bug 1839853 in OpenStack Compute (nova) "Misuse of nova.objects.base.obj_equal_prims in tests" [Medium,Confirmed]15:40
openstackgerritJing Zhang proposed openstack/nova master: Remove the current host from cold migration target host list  https://review.opendev.org/67502515:41
*** belmoreira has quit IRC15:44
*** priteau has quit IRC15:45
*** mkrai has joined #openstack-nova15:48
*** factor has joined #openstack-nova15:48
*** tbachman has quit IRC15:49
openstackgerritBalazs Gibizer proposed openstack/nova master: Avoid timeout from service update notification tests  https://review.opendev.org/67593515:51
*** helenafm has quit IRC15:53
*** gyee has joined #openstack-nova15:54
*** tbachman has joined #openstack-nova15:54
*** udesale has quit IRC15:56
*** damien_r has quit IRC15:56
*** dave-mccowan has quit IRC15:56
mriedemcdent: up your vmware alley https://review.opendev.org/#/c/675025/215:56
cdentsounds a bit rude, that15:56
mriedemha15:57
mriedemdansmith: efried: melwitt: what do you think about the [workarounds]/allow_cold_migrate_to_same_host idea in https://review.opendev.org/#/c/675025/ as a backportable thing until we can be smarter about scheduling for cold migrate based on compute capabilities / traits filtering?15:58
*** dtruong has quit IRC15:59
*** dtruong has joined #openstack-nova16:00
dansmithmriedem: meaning different behavior for cold migrate vs. resize?16:00
mriedemyeah16:01
mriedemthe existing option conflates them which is bad for everything except vmware16:01
dansmiththe intent of cold migration is always to land it on a different host, so I guess I'm not sure why the patch is wrong (in intent, I haven't looked at the reasoning)16:01
mriedemthat's true for everything except vcenter16:02
dansmithokay so the workaround config knob would only need tweaking for vmware?16:02
cdentyet another raeson for vogan16:02
mriedemdansmith: yeah16:02
melwittI'm not opposed to the patch but isn't this a super latent thing or? surprised this hasn't come up before16:02
mriedemand is a backportable thing until we can be smarter about filtering based on traits16:02
mriedemmelwitt: it is,16:03
mriedemthere are a bunch of related bugs16:03
dansmithmriedem: and that workaround would be read/honored in api or conductor when assembling the request to scheduler/16:03
mriedemwe just never do anything about fixing it :)16:03
melwittheh, wow16:03
mriedemdansmith: api16:03
mriedemdansmith: same place that allow_resize_to_same_host is read16:03
dansmithyeah16:03
dansmithfor some reason I feel like workarounds are usually per-host and thus read by the compute16:04
dansmithand further,16:04
dansmithif you have one vmware compute and a bunch of libvirt computes, you likely don't want that to be a global policy16:04
mriedemsure, but we already do,16:04
dansmithfor resize you mean16:04
mriedemand that's why i think long-term we replace the workaround option with traits-based compute capability filtering,16:04
mriedemyes, but we treat reaize == cold migrate in the api from this regard16:05
dansmithsure, but the stated goal of allowing resize to same host makes more sense as a global I think16:05
dansmithbut anyway, what I'm saying is:16:05
dansmithmaybe the knob should be read by compute and factor in to what traits it exposes and then let the control side throw some required or forbidden trait in there16:06
mriedemyou can't backport that16:06
dansmithsure16:06
mriedembut yes, that's what i'm saying we do with https://review.opendev.org/#/c/666604/16:06
mriedemcompute exposes a trait for if it can do a thing, api reads that and configures the request spec for scheduler filtering appropriately,16:06
dansmithbut if we add it as honored by control, then backport that, then we kinda need deprecation or a dance to move to the per-compute way16:06
mriedemwhich replaces the workaround thing i'm suggesting for backports16:06
mriedemcorrect16:07
mriedemworkaround option -> backports -> eventual deprecation with the new thing https://review.opendev.org/#/c/666604/16:07
dansmithright, so point is, since this is latent since the beginning of time, I don't care so much about the backport16:07
dansmithbut if it's super important to you then, I guess whatever16:07
mriedemit's not super important to me, it's just i've dealt with it more than once and it continues to come up as a bug for *us*16:08
mriedemmy fear is the longer we don't do something, the more hack patches like this show up16:08
dansmithack16:08
sean-k-mooneymriedem: speaking about https://review.opendev.org/#/c/666604/?16:09
mriedemrelated yes16:10
mriedemprompted by https://review.opendev.org/#/c/675025/16:10
sean-k-mooneywe spoke about it a bit on irc and understand the motivaition more now16:10
mriedemthe royal we?16:10
sean-k-mooneyas in i pinging you about it last week16:10
sean-k-mooneyor the week before16:10
sean-k-mooneyand you explained what it was for16:10
sean-k-mooneyit is not a trait i would expect to see in a flavor or image16:11
sean-k-mooneybut i can see how it could be useful in this specific case16:11
melwittI'm ok with the wokraround conceptually, I'm not sure why we didn't just do that years ago. I'm assuming it's a really simple change to consider resize different than cold migrate for "allow same host"16:12
mriedemsean-k-mooney: nor are several of our compute-capability based traits16:12
mriedemmelwitt: yeah i think it would be a small change16:13
mriedemif allow_resize_to_same_host:16:13
mriedem   if cold_migrate and allow_cold_migrate_to_same_host:16:13
sean-k-mooneya workaround config option has the benifit that it could be backported were as the trait could not16:13
mriedemdude16:13
melwittlol16:13
sean-k-mooneyi know dansmith just said he does not care16:14
sean-k-mooneyand ye just finished that conversation16:14
sean-k-mooneybut it is a minor pluse to the workaround still for me16:14
sean-k-mooney*workaround conf16:15
melwittthe reason I ask is because I wouldn't support a workaround like this for a super latent thing if it's a big complicated change. but if it's a tiny one liner and would solve a lot of pain for people, then it seems like a worthwhile thing to do16:15
*** rpittau is now known as rpittau|afk16:15
melwittmy concern would be more like, do we really expect to deprecate it from [workarounds] or not16:16
dansmithI don't think it's a lot of people, and I just want to avoid the deprecation dance, effectively introducing something as deprecated16:16
dansmithbut yes, it's small and the deprecation is the major impact, so whatever16:16
*** mkrai has quit IRC16:16
dansmithmelwitt: I assume we'd land it, and deprecate it in the next patch, then just backport the first one16:17
melwittoh, right, I see16:17
mriedemyes that would be what i'd do16:17
sean-k-mooneydansmith: that depend on the long term fix no? e.g. if we make it work transparently in the fureure then the deprecation/removal should not break people16:18
dansmithsean-k-mooney: we can't16:18
dansmithsean-k-mooney: we're talking about moving what honors the thing from global/scheduler to local/compute16:18
dansmithdidn't we already discuss that part?16:18
sean-k-mooneyoh i missed that part of the discussion. ill go back to fixing my typos :)16:19
sean-k-mooneyi had assumed the workaround option would be set globally16:20
melwittif the trait thing is simple and we're sure we're going to land it this cycle, then deprecate immediately "works". immediate deprecation is definitely a weird thing to do having left it latent for so long, but if it's such a minor tiny change, I'm not opposed about it16:21
melwitt*backport + immediate deprecation16:22
sean-k-mooneyit would not be the first workaound option that has been in that state16:22
sean-k-mooneye.g the numa migration one was intended to be intoduced backported and deprecated all in one cycle16:23
openstackgerritMerged openstack/nova stable/queens: Disable limit if affinity(anti)/same(different)host is requested  https://review.opendev.org/65924716:24
sean-k-mooneywe even change default behavior with that backport16:24
openstackgerritMatt Riedemann proposed openstack/nova master: rt: only map compute node if we created it  https://review.opendev.org/67570416:29
openstackgerritMatt Riedemann proposed openstack/nova master: Add functional regression recreate test for bug 1839560  https://review.opendev.org/67570516:29
openstackbug 1839560 in OpenStack Compute (nova) "ironic: moving node to maintenance makes it unusable afterwards" [High,In progress] https://launchpad.net/bugs/1839560 - Assigned to Matt Riedemann (mriedem)16:29
sean-k-mooneyif we treated the new can_cold_migrate_to_same_node workaround option the same way as enable_numa_live_migration is there a reason we cant just set this gloably the scheduler?16:30
sean-k-mooneyi know that would not be desirebal for mix hyperviors16:30
sean-k-mooneybut its simplifies thing greatly16:31
dansmithsean-k-mooney: could you read the backscroll please?16:31
dansmithwe've already discussed that too16:31
dansmithor even the comments on the patch16:31
sean-k-mooneyok im just confused why we would treat this differently then enable_numa_live_migration which is effectivly the same16:31
sean-k-mooneyill read both16:32
dansmithit probably should be the same, I haven't really seen anything about that knob myself16:32
*** Sundar has joined #openstack-nova16:33
*** dklyle_ is now known as dklyle16:34
sean-k-mooneyenable_numa_live_migration is used in the api i think and reject any live migration if the instnace has a numa toplogy when set to false which we made the defaul.16:35
sean-k-mooneythe reasoning being while it was a behavior change teh people that understand how to deploy numa toployg are the people that modify thing in the config anyway and we whould not let most people break things by migaint with out understandint its broken with numa16:36
sean-k-mooneywe may have done the check late in teh scheduler in teh enable_numa_live_migration case but i cant see why we would not have done it in the api16:37
openstackgerritStephen Finucane proposed openstack/nova master: Unplug VIFs as part of cleanup of networks  https://review.opendev.org/66338216:37
*** mjozefcz has quit IRC16:40
SundarHi dansmith: Thanks for your reviews. For https://review.opendev.org/#/c/631243/30/nova/objects/flavor.py@230, I am trying to understand the alternative you recommend. "Let the versioned fields be properties" --> extra_specs is just a DictOfStrings, so how do you propose to change that to include a devic eprofile name explicitly?16:40
mriedemsean-k-mooney: it's not in the api, it's in conductor,16:41
mriedemand it's after we've picked a host to check if it's qemu16:41
mriedemthe allow resize to same host option is read in the api before calling the scheduler16:41
sean-k-mooneymriedem: oh yep your right16:42
mriedemefried: https://review.opendev.org/#/c/675935/16:43
mriedemeasy test fix to make func job runs go faster16:43
efriedmriedem, gibi: Left a comment in there. If you disagree, I'll +W16:46
dansmithSundar: just access the extra specs whenever you're going to look at the device profile16:48
dansmithSundar: i.e. code should be: flavor.extra_specs['device_profile'] ... instead of flavor.device_profile16:48
openstackgerritSurya Seetharaman proposed openstack/nova master: API microversion 2.76: Add 'power-update' external event  https://review.opendev.org/64561116:54
dansmithtssurya: found something I think is a problem that wasn't obvious until your clean-up16:58
*** tbachman has quit IRC16:58
dansmithtssurya: let me know if I'm missing something there16:59
tssuryadansmith: checking16:59
*** derekh has quit IRC17:01
mriedemefried: i'm ok either way17:01
efriedmriedem, gibi: I just don't like lambda *a, **k: None if we don't need it.17:01
mriedemefried: if you want to change i'll test it and approve17:01
efried...17:01
efriedmriedem: f it, would need to import (the real) fixtures. +W17:03
mriedemheh17:03
tssuryadansmith: replied, hope I am not messing something up17:04
*** shilpasd has quit IRC17:08
*** ociuhandu_ has joined #openstack-nova17:09
dansmithtssurya: ah, I was confused, yeah, but in your comment you mean avoid L4768 not 4770 right?17:10
dansmithyou're trying to avoid queuing this event because it's a no-op?17:10
tssuryadansmith: right sorry I am trying to avoid L476817:10
tssuryadansmith: yes I don't want the event to go down to the manager17:11
dansmithso I was going to say this earlier, but I'm not really sure why we need to do the (almost) silent drop of those in the api17:11
tssuryaI am being strict with the task/vm/power states of the vm17:11
dansmithbecause it seems like the manager/driver would know better about whether or not that is still important17:11
dansmithbut, the thing I -1d for is wrong, so I'll drop that17:11
tssuryaI understand your point, but since I sort of copied the start/stop logic in the api,17:12
tssuryait would blow up here: https://review.opendev.org/#/c/645611/11/nova/compute/api.py@470517:12
tssuryawhen I save the instance since the expected state is None and so on17:12
tssuryaits mostly because when I was testing if there is a power sync/receving of event almost close to each it could mess up things17:13
*** ociuhandu has quit IRC17:13
tssuryamostly a fail safe that I did in the beginning itself17:13
*** ociuhandu_ has quit IRC17:14
dansmithtssurya: ah, okay that's fair17:16
dansmithtssurya: I'll let mriedem lead with a +2 on the api stuff and versioning bits but otherwise I think I'm good with it17:20
tssuryadansmith: thank you :D ! yea let's wait for the CI to run17:21
*** nweinber__ has joined #openstack-nova17:21
*** BjoernT_ is now known as BjoernT17:23
*** nweinber_ has quit IRC17:24
*** tbachman has joined #openstack-nova17:26
*** ivve has quit IRC17:27
*** ociuhandu has joined #openstack-nova17:28
*** nweinber_ has joined #openstack-nova17:32
*** ociuhandu has quit IRC17:32
*** nweinber__ has quit IRC17:35
*** whoami-rajat has quit IRC17:38
*** tssurya has quit IRC17:42
*** ircuser-1 has joined #openstack-nova17:43
*** cdent has quit IRC17:49
*** rouk has joined #openstack-nova17:53
*** atmark has quit IRC17:59
*** atmark has joined #openstack-nova18:00
*** ociuhandu has joined #openstack-nova18:04
*** luksky has joined #openstack-nova18:12
*** markvoelker has quit IRC18:13
*** mjozefcz has joined #openstack-nova18:19
*** markvoelker has joined #openstack-nova18:20
openstackgerritsean mooney proposed openstack/nova master: Libvirt: add support for vPMU configuration.  https://review.opendev.org/67133818:20
sean-k-mooneygibi: stephenfin mriedem i think i have adress most of the comments18:20
mriedemok18:34
*** dpawlik has joined #openstack-nova18:36
*** markvoelker has quit IRC18:39
*** markvoelker has joined #openstack-nova18:40
openstackgerritMatt Riedemann proposed openstack/nova master: Restore soft-deleted compute node with same uuid  https://review.opendev.org/67549618:41
mriedemmnaser: ^18:43
mnasermriedem: seems very sane18:46
openstackgerritsean mooney proposed openstack/nova master: WIP: Add a placement audit command  https://review.opendev.org/67011218:53
*** ociuhandu has quit IRC18:54
sean-k-mooneycdent i think i have adressed your comments on ^ but im not fully sure what sylvain was trying to do so ill take a look again tomorow after i read the bug18:55
*** ociuhandu has joined #openstack-nova18:55
*** ivve has joined #openstack-nova18:58
*** ociuhandu has quit IRC19:00
*** bbowen has quit IRC19:12
*** ociuhandu has joined #openstack-nova19:12
openstackgerritMatt Riedemann proposed openstack/nova stable/stein: Add useful error log when _determine_version_cap raises DBNotAllowed  https://review.opendev.org/67571419:12
*** eharney has quit IRC19:14
*** factor has quit IRC19:17
*** abaindur has joined #openstack-nova19:21
*** ociuhandu has quit IRC19:25
*** ociuhandu has joined #openstack-nova19:26
*** igordc has joined #openstack-nova19:26
*** Sundar has quit IRC19:30
*** ociuhandu has quit IRC19:32
*** tesseract has quit IRC19:32
*** psachin has quit IRC19:37
*** igordc has quit IRC19:41
*** mjozefcz has quit IRC19:51
*** dave-mccowan has joined #openstack-nova19:54
mriedemdansmith: melwitt: just had another thought on this allow cold-migrate to same host thing, which wouldn't involve a workaround and soon-to-be-deprecated config option,19:54
mriedemif allow_resize_to_same_host=true, get the compute node for the instance and check it's hypervisor type, if it's anything besides vcenter we don't allow it19:55
mriedemthat would be a hack fix for any in-tree drivers and could be replaced with the more dynamic traits filtering later19:55
mriedemdon't allow cold migration to the same host that is19:56
mriedemmaybe that's *too* hacky19:58
dansmiththat check in the api seems like a high crime19:58
mriedemimpeachable?20:00
dansmithautomatic impeachment20:00
dansmithand subsequent special counsel investigation20:00
mriedemheh20:00
dansmithall your dirty laundry will be aired20:01
mriedembnemec: for a BoolOpt, is it possible to leave it unset so you can set the default at runtime somehow, e.g. it's based on another options value?20:01
*** eharney has joined #openstack-nova20:01
bnemecmriedem: It is. I believe the default for BoolOpt is actually None, which implies that it was unset since that's not a valid boolean value.20:02
bnemecWhich I actually think is a bug (https://bugs.launchpad.net/oslo.config/+bug/1764782) but as Doug points out there's no way to know if people have been relying on that behavior.20:02
openstackLaunchpad bug 1764782 in oslo.config "BoolOpt defaults to None" [Medium,Triaged]20:02
mriedemah i see, looks like boolean type opts are really str opt under the covers and they get cast to booleans20:03
mriedemsomething like strutils.bool_from_string20:03
mriedemok in my case i want to add a new option but have it's default be backward compatible to whatever is set for another option20:04
mriedemunless you explicitly override it20:04
*** ccamacho has quit IRC20:05
bnemecI guess I should note that the more "correct" way to do this is to use get_location: https://docs.openstack.org/oslo.config/latest/reference/api/oslo_config.html#oslo_config.cfg.ConfigOpts.get_location20:06
bnemecThat will tell you if a user set the option or not in an unambiguous way.20:06
bnemecOr maybe even better, use set_default and set the new opt's default to the value of the old opt: https://docs.openstack.org/oslo.config/latest/reference/api/oslo_config.html#oslo_config.cfg.ConfigOpts.set_default20:08
mriedemthe get_location stuff is relatively new right?20:10
mriedemlike, newer than ocata?20:10
*** igordc has joined #openstack-nova20:11
mriedemyeah rocky https://review.opendev.org/#/c/537397/20:13
mriedemi don't plan on backporting this nova workaround too far, but it is super latent (much older than ocata anyway)20:13
bnemecYeah, although set_default has been around forever and is probably the right thing to do here conceptually.20:21
bnemecYou're setting a default for an opt based on a thing calculated in code (in this case from the value of another opt) but want the user to be able to override it if they set the opt explicitly.20:22
mriedemwhere would i call set_default? where i'm using the new option?20:23
bnemecSometime between when you register the old opt and when you use the new one.20:23
mriedemiow it's like dict.set_default20:23
mriedem*setdefault20:23
bnemecSomething like that, but you just call it once and the config object remembers that you overrode the default for that opt.20:25
bnemecI guess dict inserts the key with the default so that is actually the same.20:26
mriedemthis is what i've got right now http://paste.openstack.org/show/756357/20:26
*** nweinber_ has quit IRC20:27
*** tbachman has quit IRC20:27
mriedemthis is probably better to avoid calling set_default when i don't need to20:28
mriedemhttp://paste.openstack.org/show/756358/20:28
mriedemotherwise i have to do this somewhere in wsgi init after parsing options and starting the service20:28
mriedemwhich takes it quite far away from where it's used, which is ok but kind of hard to remember all of this20:29
bnemecHeh, if you're still checking for None then I'm not sure you gain much from using set_default.20:29
bnemecBut either should work.20:29
*** bbowen has joined #openstack-nova20:31
mriedemyeah true :/20:33
bnemecIt's probably not worth satisfying my pet peeve about the BoolOpt default by moving the setdefault call to some weird location though.20:35
*** efried has quit IRC20:39
sean-k-mooneydict not only set the defult i return the value in the dict. so if it was already set it returns the value that was found in the dict and if not it returns you default after setting it in the dict20:39
sean-k-mooneyyou can discard the return if you dont care but its a nice behavior to have20:40
*** efried has joined #openstack-nova20:40
sean-k-mooneyso if we had a CONF.set_default it would be nice to keep  it the same20:40
sean-k-mooneythat would change your example to http://paste.openstack.org/show/756359/20:41
*** dpawlik has quit IRC20:42
sean-k-mooneyits a minor change but its basicly free to return the value and it makes the useage terser20:43
*** artom has quit IRC20:46
*** pcaruana has quit IRC20:56
*** gryf has quit IRC20:58
*** xek has quit IRC21:02
*** mjozefcz has joined #openstack-nova21:02
*** mjozefcz has quit IRC21:11
*** markvoelker has quit IRC21:24
*** tbachman has joined #openstack-nova21:25
openstackgerritMatt Riedemann proposed openstack/nova master: Allow disabling cold migration to the same host  https://review.opendev.org/67602221:31
*** ociuhandu has joined #openstack-nova21:36
*** abaindur has quit IRC21:38
*** abaindur has joined #openstack-nova21:39
*** ociuhandu has quit IRC21:42
*** slaweq has quit IRC21:46
openstackgerritMatt Riedemann proposed openstack/nova master: Add nova-lxc job to the experimental queue  https://review.opendev.org/67602422:02
mriedemdonnyd: sean-k-mooney: ^ and now i'm out o/22:02
*** mriedem is now known as mriedem_afk22:03
*** markvoelker has joined #openstack-nova22:03
donnydYesssss22:05
*** BjoernT has quit IRC22:07
*** lbragstad has joined #openstack-nova22:09
*** vishwanathj has quit IRC22:10
*** mchlumsky has quit IRC22:14
*** spatel has joined #openstack-nova22:14
openstackgerritMerged openstack/nova stable/queens: libvirt: move checking CONF.my_ip to init_host()  https://review.opendev.org/67216122:16
*** mlavalle has quit IRC22:16
openstackgerritMerged openstack/nova master: Avoid timeout from service update notification tests  https://review.opendev.org/67593522:16
*** lbragstad has quit IRC22:17
openstackgerritEric Fried proposed openstack/nova master: Use SDK for node.list  https://review.opendev.org/65602722:22
*** ociuhandu has joined #openstack-nova22:30
*** ivve has quit IRC22:33
*** ociuhandu has quit IRC22:35
*** markvoelker has quit IRC22:35
*** spatel has quit IRC22:37
*** hoonetorg has quit IRC22:48
*** hoonetorg has joined #openstack-nova22:50
openstackgerritEric Fried proposed openstack/nova master: Add nova-lxc job to the experimental queue  https://review.opendev.org/67602422:52
*** hoonetorg has quit IRC22:57
*** vishwanathj has joined #openstack-nova22:58
*** macz has joined #openstack-nova23:00
*** markvoelker has joined #openstack-nova23:00
*** hoonetorg has joined #openstack-nova23:01
*** vishwanathj has quit IRC23:03
*** abaindur has quit IRC23:04
*** markvoelker has quit IRC23:05
*** abaindur has joined #openstack-nova23:05
openstackgerritEric Fried proposed openstack/nova master: WIP: Limit get_sdk_adapter to requested service type  https://review.opendev.org/67467823:09
*** rcernin has joined #openstack-nova23:11
*** dave-mccowan has quit IRC23:17
*** markvoelker has joined #openstack-nova23:18
*** mriedem_afk has quit IRC23:19
*** luksky has quit IRC23:31
*** dave-mccowan has joined #openstack-nova23:37
*** takashin has joined #openstack-nova23:38
openstackgerritTakashi NATSUME proposed openstack/nova stable/stein: Retrun 400 if invalid query parameters are specified  https://review.opendev.org/67602623:40
openstackgerritTakashi NATSUME proposed openstack/nova stable/rocky: Retrun 400 if invalid query parameters are specified  https://review.opendev.org/67602723:53
*** spatel has joined #openstack-nova23:54
*** alex_xu has quit IRC23:57
*** spatel has quit IRC23:59
*** alex_xu has joined #openstack-nova23:59
openstackgerritTakashi NATSUME proposed openstack/nova stable/queens: Retrun 400 if invalid query parameters are specified  https://review.opendev.org/67602823:59

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