Posted	Nick	Remark
#openstack-nova - 2019-02-04
16:11:19	mriedem	kashyap: it showed that you practiced it, very smooth
16:11:25	mriedem	but you were soooo thirsty
16:11:25	kashyap	BTW, on Sunday ran into The Tuba Guy at FOSDEM. He happened to be sitting right behind me
16:11:42	kashyap	mriedem: Darn, there is a story behind that water bottle trick
16:12:19	kashyap	Back when I was in university, some 12 years ago, I had to give my first public talk on USB 3.0 or something...
16:12:35	kashyap	And my throat completely dried out, and the teacher insulted me in front of the whole class:
16:12:43	kashyap	Saying ... "What kind of a talk is that?!"
16:12:53	kashyap	Never forget that experience
16:13:11	kashyap	But more to the bottle: I use it as a trick to forcefully "pause" myself
16:13:15	kashyap	And not drone on-and-on.
16:13:31	kashyap	s/bottle/water bottle/
16:26:23	bauzas	ok, bailing out from upstream after 3 hours working on it \o
16:26:36	bauzas	https://twitter.com/sylvainbauza/status/1092426500434022402
16:27:01	bauzas	at least I dedicated 3 hours for nova since 2 weeks...
16:28:01	sean-k-mooney	bauzas: the vpn outage proably helped somewhat today
16:28:20	bauzas	sean-k-mooney: not really, I planned to work for 3 hours anyway
16:29:07	bauzas	I thought about this from the last weekend
16:29:19	sean-k-mooney	i planned to start backpoting something and did some code review upstream instead
16:29:28	sean-k-mooney	bauzas: its a good idea
16:29:33	bauzas	and finally I think I very need to say "sorry but I need to work upstream *now*'
16:29:43	artom	sean-k-mooney, to answer your downstream channel question, yeah, more work is required to actually generate the new XML
16:29:49	bauzas	because if not, there will be some other priorities again and again
16:29:56	artom	The claims are used to get the new instance NUMA topology
16:30:49	sean-k-mooney	artom: are they actully used currently. i was not sure they were actully being used yet in the code you have pused.
16:31:06	artom	sean-k-mooney, they're not used yet, no
16:31:32	sean-k-mooney	artom: ok because the titile of https://review.openstack.org/#/c/634606/ consufed me a little
16:31:49	artom	I mean, when creating the claim, the new instance NUMA topology is calculated, so it should throw a resources unavailable exception if it can't fit
16:32:03	artom	But then that new topology isn't used anywhere (yet)
16:32:20	sean-k-mooney	artom: ya that makes sense
16:32:35	artom	sean-k-mooney, hrmm, yeah, maybe I'll rephrase it as "create claims" or something
16:32:44	artom	Since as you correctly pointed out, they're not actually used
16:33:05	openstackgerrit	Matt Riedemann proposed openstack/nova master: doc: update the security groups admin doc https://review.openstack.org/634735
16:33:28	sean-k-mooney	ya i spend about 10-15 mins looking to see if they were actully used idrectly some how then my vpn dropped and i got tea
16:34:05	artom	So British (yes, I know you're Irish)
16:34:22	sean-k-mooney	those be fighting words :P
16:34:33	artom	There's no "UK" adjective!
16:34:45	sean-k-mooney	ireland is not in the uk
16:34:52	artom	*facepalm*
16:34:57	artom	You're right, of course.
16:35:04	kashyap	mriedem: If I spend this week on this https://review.openstack.org/#/c/632507/ ([WIP] libvirt: Bump MIN_{LIBVIRT,QEMU}_VERSION for "Stein"), and related clean-ups -- worth getting in before M3?
16:35:51	artom	There's no adjective for "those tea-guzzling bastids" then :D
16:36:07	sean-k-mooney	hehe :)
16:37:32	openstackgerrit	Matt Riedemann proposed openstack/nova master: Change nova-next job to run with python3 https://review.openstack.org/634739
16:39:00	mriedem	kashyap: idk, i generally like to raise minimums at the beginning of the cycle
16:39:08	mriedem	if we're going to raise minimums
16:40:24	mriedem	an operator that was upgrading recently asked me if the last time we raised minimums (in queens i think) was because of any functional reason or just code cleanup since it meant they had a harder upgrade (new centos versions and such on their compute nodes)
16:41:25	mriedem	they were also upgrading from mitaka though i think so likely going to have some of that (OS upgrades etc)
16:42:26	kashyap	mriedem: Yeah, you're totally right -- I completely forgot at the beginning of the cycle about this :-(
16:42:27	stephenfin	mriedem, sean-k-mooney: This feels like something that would warrant a reno given the change in behavior. Thoughts? https://review.openstack.org/#/c/626381
16:42:59	mriedem	"fyi nova-compute will no longer corrupt your database you're welcome'
16:43:13	mriedem	stephenfin: the behavior was shit
16:43:22	mriedem	so if we have a reno, i'd make it a 'fixes' reno to explain the bug being fixed
16:43:41	stephenfin	That it was. And I guess it's not something anyone would have been relying on
16:43:59	mriedem	i.e. if you had allocated pci devices in your whitelist configuration, and then changed your config to remove those whitelisted devices, nova will no longer delete those records from the db since it corrupts the resource tracking for the allocated device
16:44:26	mriedem	but i'm not sure ^ is worth explaining in a release note
16:44:33	mriedem	it might just cause more confusion/concern than necessary
16:44:45	stephenfin	Sweet. If you're happy, so am I
16:45:10	mriedem	i'm not unhappy :)
16:45:20	mriedem	and as you say, i hope no one was relying on this
16:45:46	stephenfin	So do I. I'd ask moshele if he was around but alas, he is not
16:45:57	mriedem	cfriesen might have an opinion
16:46:00	mriedem	but also not around right now
16:46:01	sean-k-mooney	so no new reno? i can add one but i agree with mriedem that it would be in fixes as the old bevahior was not a feature
16:46:16	stephenfin	sean-k-mooney: Nah, mriedem makes a good point. It was rather broken before
16:47:48	stephenfin	sean-k-mooney: I've just held off on the +W in case cfriesen gets a chance to wade in before tomorrow
16:48:05	sean-k-mooney	ok cool thanks
16:51:35	stephenfin	mriedem: I must have misunderstood something but weren't we planning to deprecate this option entirely, relying on alternatives for instance-host mapping use case? https://review.openstack.org/#/c/619953/10/nova/conf/libvirt.py
16:52:05	sean-k-mooney	stephenfin: dan asked that we dont
16:52:10	mriedem	stephenfin: see dansmith's comments in an earlier PS
16:52:21	stephenfin	ack
16:57:53	openstackgerrit	Matt Riedemann proposed openstack/nova master: Follow up for per-instance serial number change https://review.openstack.org/634743
17:29:37	stephenfin	mriedem: Fancy checking this nit fix? https://review.openstack.org/#/c/626930/
17:29:41	stephenfin	*nit doc fix
17:31:53	mriedem	done
17:32:34	stephenfin	ta
17:33:23	mriedem	stephenfin: a couple of nits in the one on top of that
17:34:11	stephenfin	I can fix those now or in a follow-up. Your call
17:34:20	mriedem	do it now and i'll re-approve
17:36:14	openstackgerrit	Stephen Finucane proposed openstack/nova master: doc: Add solution to live migration ssh issues https://review.openstack.org/626931
17:36:19	stephenfin	mriedem: done ^
17:49:09	efried	Hey folks, where are we with NUMA modeling in placement?
17:49:09	efried	Is that still on ice? Has bp/numa-aware-live-migration brought it back into play? Or are we still doing that bp with the old style NUMA modeling?
17:49:09	efried	artom jaypipes cdent sean-k-mooney
17:50:00	sean-k-mooney	the numa aware migration is entirely done via the resource tracker
17:50:13	sean-k-mooney	efried: so its still on ice until train
17:50:37	sean-k-mooney	efried: the RT changes will still be needed in eitehr case
17:51:05	efried	So would it be appropriate to start proposing spec content for train around NUMA modeling in placement? (Again)
17:51:20	sean-k-mooney	bauzas: ^
17:51:50	efried	i.e. using nested providers to represent NUMA nodes, figuring out a way to represent subtree affinity, etc.
17:51:52	sean-k-mooney	efried: i guess but it would be good to take a more holistic aproach i think
17:52:01	efried	holistic in what sense?
17:53:03	sean-k-mooney	well there are a number of feature in the libvirt driver (pinning,hugepages,reatime,emulator threads,numn) all the nfv stuff that are not really placement friendly
17:53:54	sean-k-mooney	efried: i have been wondering for a while if we shoudl create a parallel implmentation of new feature that are placment aware to replace teh existing ones with
17:54:13	efried	not sure how we'll ever get there if we don't.
17:54:36	cdent	yeah, I suspect a parallel leapfrog is the way to go
17:55:20	sean-k-mooney	well my idea was to take the cellsv2 approcah and freeze/keep the exisiting feature set as is and work on a replacement in paralel and then swtich in U
17:55:32	openstackgerrit	Merged openstack/nova master: Reject migrate with port having resource request https://review.openstack.org/630723
17:56:41	sean-k-mooney	it realy has become a problem lately that we have 2 seperate code patchs. 1 for numa awre guess and anotehr for non numa guests and i just feel like have one code path that works for all guesst in a common way might be the way to go
17:57:10	sean-k-mooney	efried: anyway that is slightly different then the question you asked
17:57:48	cdent	sean-k-mooney: I sometimes wonder the opposite: we should have two diferent paths: one for simple vms that normal people use, anothe for the crazy path :)

Earlier   Later