Posted	Nick	Remark
#openstack-nova - 2017-10-20
16:34:09	finucannot	I thought it was done via the alias but I see the error of my ways now
16:35:04	sean-k-mooney	yes it was foolish to try to understand how our pci passthrough code works :)
16:37:39	leakypipes	superdan: would you be cool with that?
16:41:56	openstackgerrit	Merged openstack/nova master: Cleanup mount / umount and associated rmdir calls https://review.openstack.org/494423
16:44:26	openstackgerrit	Merged openstack/nova master: Move lvm handling to privsep. https://review.openstack.org/495516
16:56:59	openstackgerrit	Ildiko Vancsa proposed openstack/nova master: Implement new attach Cinder flow https://review.openstack.org/330285
17:06:30	openstackgerrit	Elod Illes proposed openstack/nova master: Transform instance.trigger_crash_dump notification https://review.openstack.org/396225
17:13:48	superdan	leakypipes: no real choice so yeah sure :)
17:57:34	openstackgerrit	Andreas Jaeger proposed openstack/nova master: DNM: Test api-refs https://review.openstack.org/513819
17:57:43	cfriesen	when running ironic, does it require configuring nova-scheduler differently than normal? The existance of nova/scheduler/ironic_host_manager.py, makes me wonder.
18:09:49	MikeW	Hey which components of the nova services emit these notifications to rabbitmq: compute.instance.create.end and compute.instance.delete.start?
18:10:20	MikeW	Wondering on what I need to touch to integrate designate-sink in my system and hoping I can void compute hosts, and just modify like nova-scheduler or nova-api
18:43:26	MikeW	Anyone here have experience with nova/designate integration over the message queue?
18:49:01	mriedem	mlavalle: remind me, can you live migrate from an ovs vif type to a linuxbridge vif type, or vice versa, today? or does that require a reboot once the instance is on the dest host?
18:49:30	mriedem	i thought no because the source host doesn't know the dest host vif type to use to configure the guest before the live migration starts - which is part of what sean's spec is trying to fix
18:49:45	mlavalle	that's my understanding as well
18:50:07	mriedem	cool - just working on project update slides
18:50:15	mlavalle	:-)
18:50:19	mriedem	want to make sure i correctly promise the world
18:50:28	mlavalle	LOL
18:58:55	superdan	mriedem: correct
19:13:52	openstackgerrit	Ildiko Vancsa proposed openstack/nova master: Implement new attach Cinder flow https://review.openstack.org/330285
19:31:19	openstackgerrit	Eric Fried proposed openstack/nova master: Refactor test_resource_provider https://review.openstack.org/513834
19:38:13	mriedem	superdan: this doesn't seem kosher https://review.openstack.org/#/c/509107/2/os_vif/objects/subnet.py
19:38:36	superdan	mriedem: that's because it's not
20:15:58	openstackgerrit	Eric Fried proposed openstack/nova master: Include /resource_providers/uuid/allocations link https://review.openstack.org/499826
20:21:16	openstackgerrit	Merged openstack/nova master: console: introduce basic framework for security proxying https://review.openstack.org/345396
20:27:43	mriedem	anthonyper: https://review.openstack.org/#/c/465160/ - talks about only allowing numa in the libvirt driver if using kvm
20:27:48	mriedem	questions in there about numa support for libvirt+xen
20:36:54	openstackgerrit	Eric Fried proposed openstack/nova master: Include /resource_providers/uuid/allocations link https://review.openstack.org/499826
20:40:34	BenderRodriguez	fried_rice: help me fix my issues
20:40:38	BenderRodriguez	installing openstack
20:40:52	fried_rice	BenderRodriguez I think you want the #openstack channel for that.
20:41:56	fried_rice	mriedem Say, do we want to update the channel topic to reference the Queens release schedule at this point?
20:42:19	mriedem	fried_rice: first, "say" is how my 60-something day starts a sentence,
20:42:22	mriedem	second, yes
20:42:25	mriedem	superdan: ^
20:42:32	fried_rice	Dude, what's with all the ageist talk lately?
20:42:33	mriedem	s/day/dad/
20:43:32	fried_rice	whee
20:44:32	BenderRodriguez	Why in the world
20:44:36	BenderRodriguez	is openstack still running on top of 2.7
20:44:41	BenderRodriguez	what is wrong with you developers/
20:44:50	BenderRodriguez	python 2.7 that is
20:44:53	superdan	dang, dropped op a little too early
20:44:57	fried_rice	was gonna say
20:45:05	mriedem	BenderRodriguez: you can run it on 3.5
20:45:08	mriedem	it's not really a nova thing,
20:45:11	mriedem	it's a packaging thing
20:45:14	mriedem	and we don't control the packages
20:45:21	BenderRodriguez	hmmm
20:45:32	BenderRodriguez	what version of python are unit tests run on
20:45:36	BenderRodriguez	pre-deployment
20:45:39	mriedem	27 and 35
20:45:42	BenderRodriguez	ok good
20:45:46	mriedem	unit tests, functional tests and integration tests
20:46:37	openstackgerrit	Matt Riedemann proposed openstack/nova master: propagate OSError to MigrationPreCheckError https://review.openstack.org/469779
20:52:59	openstackgerrit	Ed Leafe proposed openstack/nova master: Add alternate hosts https://review.openstack.org/486215
20:53:00	openstackgerrit	Ed Leafe proposed openstack/nova master: Add Selection objects https://review.openstack.org/499239
20:53:00	openstackgerrit	Ed Leafe proposed openstack/nova master: Return Selection objects from the scheduler driver https://review.openstack.org/495854
20:53:01	openstackgerrit	Ed Leafe proposed openstack/nova master: Change RPC for select_destinations() https://review.openstack.org/510159
20:53:01	openstackgerrit	Ed Leafe proposed openstack/nova master: Move the claim_resources method to scheduler utils https://review.openstack.org/511357
20:53:02	openstackgerrit	Ed Leafe proposed openstack/nova master: Make conductor pass and use host_lists https://review.openstack.org/511358
20:53:02	openstackgerrit	Ed Leafe proposed openstack/nova master: Trivial: fix spelling of allocation_request https://review.openstack.org/513847
21:03:25	openstackgerrit	Matt Riedemann proposed openstack/nova master: Adds 'sata' as a valid disk bus for qemu and kvm hypervisors https://review.openstack.org/459794
21:20:41	openstackgerrit	Jay Pipes proposed openstack/nova master: placement: add nested resource providers https://review.openstack.org/377138
21:20:42	openstackgerrit	Jay Pipes proposed openstack/nova master: placement: allow filter providers in tree https://review.openstack.org/377215
21:20:42	openstackgerrit	Jay Pipes proposed openstack/nova master: placement: adds REST API for nested providers https://review.openstack.org/384807
21:20:43	openstackgerrit	Jay Pipes proposed openstack/nova master: placement: update client to set parent provider https://review.openstack.org/385693
21:34:44	fried_rice	leakypipes Are we gonna forbid changing traits on an RP with allocations?
21:35:37	fried_rice	iow, you have to be able to go back and validate traits constraints of an existing deployment after the fact?
21:38:44	leakypipes	fried_rice: I think *removing* traits where the provider has allocations should be prevented, yes.
21:38:52	leakypipes	fried_rice: adding new ones is cool though
21:39:26	fried_rice	leakypipes So why is it important that trait constraints be satisfied after the deploy has already happened?
21:40:11	fried_rice	leakypipes We already said you could reduce inventory totals / increase reserved amounts / change allocation ratios after the fact, even to the point of being overcommitted, and you would simply not get deployed again until you came out of the red.
21:40:19	fried_rice	leakypipes This seems like an extension of the same principle.
21:40:36	leakypipes	fried_rice: because if you asked for (and got) 10G of DISK_GB and STORAGE_DISK_SSD trait, and we remove that trait from that provider, you no longer satisfy the request that caused you to land on that node.
21:41:04	fried_rice	leakypipes Yeah, so I don't see how that's a problem.
21:41:38	fried_rice	I mean, I don't know that it's a problem to forbid it either; just seems like an unnecessary check.
21:42:25	leakypipes	fried_rice: maybe. honestly, it's 5:45pm on a Friday and I'm burnt out today.
21:42:47	fried_rice	leakypipes Ight, I'll drop the question in the review for later. Have a good weekend.
21:44:35	leakypipes	you too fried_rice
21:45:01	openstackgerrit	Elod Illes proposed openstack/nova master: Transform keypair.import notification https://review.openstack.org/467514
21:46:37	figleaf	fried_rice: You could add that to Open Discussion on https://wiki.openstack.org/wiki/Meetings/NovaScheduler
21:46:48	fried_rice	figleaf Good idea, thanks.
21:47:07	fried_rice	figleaf And split-RC/split-traits
21:47:21	figleaf	fried_rice: and whatever else tickles your fancy
22:09:47	rm_work	Can VMs be migrated to hosts in a different AZ? Does it matter?
22:10:19	rm_work	https://docs.openstack.org/nova/pike/admin/configuring-migrations.html#section-configuring-compute-migrations says: "In a multi-cell cloud, instances can be live migrated to a different host in the same cell, but not across cells."
22:10:31	rm_work	Can one cell belong to multiple AZs?
22:10:35	rm_work	Or am I thinking about this wrong
22:25:09	artom	rm_work, VMs can't be migrated different AZs
22:25:20	artom	(Slight oversimplification, but still)
22:25:23	rm_work	hmm
22:25:27	rm_work	ok
22:25:39	rm_work	would take the slightly less brief explanation if you have time :)
22:26:30	artom	An operator/admin can force it by bypassing the scheduler, I believe
22:26:55	rm_work	^^ johnsom
22:39:43	openstackgerrit	Merged openstack/nova master: Remove doc todo related to bug/1506667 https://review.openstack.org/509315
#openstack-nova - 2017-10-21
00:21:52	openstackgerrit	Elod Illes proposed openstack/nova master: Transform keypair.import notification https://review.openstack.org/467514

Earlier   Later