Posted	Nick	Remark
#openstack-nova - 2018-05-30
22:31:32	mriedem	NUMA and CPU pinning stuff will eventually be expressed in the placement API
22:31:38	eandersson	Nice
22:31:51	mriedem	there used to be an os-pci API added back in juno and removed later in i think pike (or maybe older)
22:31:55	mriedem	since it never did anything
22:32:43	mriedem	eandersson: btw, was it you or someone else from your company that asked about the TypeAffinityFilter being removed during the nova project update session in vancouver?
22:32:48	mriedem	or just totally coincidental?
22:33:14	eandersson	One of my guys asked about it, but heard that someone else also asked about it
22:33:29	eandersson	as well
22:34:12	mriedem	i heard someone named their first born "TypeAffinityFilter" they loved it so much
22:34:17	eandersson	haha
22:34:45	eandersson	To be fair the version in nova stinks, especially since it's based on uuid
22:35:19	mriedem	uuid? the one that was in tree was based on the flavor.id primary key
22:35:26	mriedem	which is pretty much the reason it was removed
22:35:29	eandersson	Yea
22:35:35	eandersson	Our version was always based on name, not id
22:35:49	mriedem	because i can create flavorid=foo with id=1, delete it and recreate it with the same flavorid but now it's id=2
22:35:54	mriedem	and your affinity stuff is all busted
22:36:01	mriedem	ok
22:36:03	mriedem	well, fyi http://lists.openstack.org/pipermail/openstack-operators/2018-May/015277.html
22:36:45	mriedem	https://review.openstack.org/#/c/569247/ will cause a perf penalty on out of tree filters that need to access any fields on HostState.instances values
22:37:03	mriedem	so if people (ops at large) are needing a type affinity filter, one should probably be proposed upstream
22:40:03	eandersson	btw unrelated but was a feature to allow rebuild to move the VM to a new compute?
22:40:15	eandersson	or even restart (similar to how Amazon does it)
22:40:24	eandersson	ever discussed?
22:41:09	eandersson	We are trying to find a strategy to make it easier for our customers when we need to bring a compute down for maintenance
22:42:49	mriedem	eandersson: that's the evacuate API
22:43:14	eandersson	Yea - I guess it's the same thing.
22:43:22	mriedem	that's after nova-compute is down though
22:43:30	mriedem	https://docs.openstack.org/nova/latest/admin/evacuate.html
22:44:13	eandersson	Our ideal scenario would be that if we want to do maintenance on compute X, we mark it as "going down in 7 days", and anyone that hits rebuild on their VM on that host gets moved to a new compute
22:44:24	eandersson	and after 7 days they would just automatically get rebuilt and moved
22:44:48	mriedem	i think you could build that on top of existing APIs in an external service
22:45:00	eandersson	Yea - that is our general plan of action for now
22:45:03	mriedem	you can force a compute service down so new things can't go to it but the existing VMs continue to run
22:45:27	mriedem	https://developer.openstack.org/api-ref/compute/#update-forced-down
22:45:46	mriedem	so you can force it down to evacuate things off it,
22:45:50	mriedem	or disable it so new things can't go to it
22:45:53	eandersson	Nice
22:46:24	mriedem	rebuild to the same host will work while the service is disabled, it won't auto-migrate it
22:46:45	mriedem	non-admins can only move during things like shelve_offload/unshelve and resize
22:47:08	mriedem	your external thing could mark the compute as disabled/down, and then after 7 days, trigger a cold migration
22:47:17	mriedem	or live if you support that
22:48:13	mriedem	actually if you disable the compute, shelve all the instances, unshelve them, you get the same thing you're asking for
22:48:38	mriedem	with some additional glance snapshot traffic, but otherwise the same as rebuild
23:20:10	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in libvirt/test_driver.py (6) https://review.openstack.org/571330
23:52:06	openstackgerrit	karim proposed openstack/nova master: Handle rebuild of instances with image traits https://review.openstack.org/569498
23:59:45	openstackgerrit	Ken'ichi Ohmichi proposed openstack/nova master: Add "must" to automatic names for multiple servers https://review.openstack.org/571335
#openstack-nova - 2018-05-31
00:20:29	openstackgerrit	Merged openstack/nova master: add parameter docstring for 'params' to libvirt.guest.Guest.migrate() https://review.openstack.org/571236
00:45:42	openstackgerrit	Merged openstack/nova master: mirror nova host aggregate members to placement https://review.openstack.org/553597
00:45:52	openstackgerrit	Merged openstack/nova master: Remove mox in libvirt/test_driver.py (3) https://review.openstack.org/569320
00:46:00	openstackgerrit	Merged openstack/nova master: libvirt: Skip fetching the virtual size of block devices https://review.openstack.org/569062
00:50:44	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in test_compute_api.py (3) https://review.openstack.org/568184
00:50:57	openstackgerrit	Takashi NATSUME proposed openstack/nova master: Remove mox in test_compute_api.py (4) https://review.openstack.org/568462
01:00:17	eandersson	mriedem_afk, we do something similar already for upgrades
01:00:40	eandersson	we move computes into a upgrade aggregate and once there are no more vms we autoamtically upgrade os, firmware etc
01:01:24	eandersson	(we just don't enforce a timelimit yet at least :p)
01:01:56	openstackgerrit	Yikun Jiang (Kero) proposed openstack/nova master: Change the anti-affinity Filter to adapt to new policy https://review.openstack.org/571166
01:36:58	openstackgerrit	wanghongtao proposed openstack/nova master: Fix the metadata re to match the unicode https://review.openstack.org/571352
01:36:58	openstackgerrit	wanghongtao proposed openstack/nova master: Fix the metadata re to match the unicode https://review.openstack.org/536236
01:44:53	openstackgerrit	tianhui proposed openstack/nova master: Fix some wrong urls in doc https://review.openstack.org/571147
02:16:49	openstackgerrit	Artom Lifshitz proposed openstack/nova master: metadata: add vf_trusted field to device metadata https://review.openstack.org/566344
02:16:50	openstackgerrit	Artom Lifshitz proposed openstack/nova master: network: update pci request spec to handle trusted tags https://review.openstack.org/458820
02:28:34	openstackgerrit	Artom Lifshitz proposed openstack/nova master: metadata: add vf_trusted field to device metadata https://review.openstack.org/566344
02:28:35	openstackgerrit	Artom Lifshitz proposed openstack/nova master: network: update pci request spec to handle trusted tags https://review.openstack.org/458820
03:35:55	bhagyashris	efried; yes
03:36:03	bhagyashris	efried: yes
03:53:00	openstackgerrit	Artom Lifshitz proposed openstack/nova master: metadata: add vf_trusted field to device metadata https://review.openstack.org/566344
03:53:01	openstackgerrit	Artom Lifshitz proposed openstack/nova master: network: update pci request spec to handle trusted tags https://review.openstack.org/458820
03:57:46	openstackgerrit	tianhui proposed openstack/nova master: Fix bug to api-ref https://review.openstack.org/571375
04:16:27	openstackgerrit	Jay Pipes proposed openstack/nova master: placement: always create consumer records https://review.openstack.org/567678
04:16:28	openstackgerrit	Jay Pipes proposed openstack/nova master: add consumers generation field https://review.openstack.org/557958
04:16:29	openstackgerrit	Jay Pipes proposed openstack/nova master: placement: Allocation.consumer field https://review.openstack.org/565405
04:16:30	openstackgerrit	Jay Pipes proposed openstack/nova master: rework allocation handler _allocations_dict() https://review.openstack.org/565407
04:16:32	openstackgerrit	Jay Pipes proposed openstack/nova master: Add a microversion for consumer generation support https://review.openstack.org/565604
04:34:39	openstackgerrit	Merged openstack/nova stable/pike: Fix shelving a paused instance https://review.openstack.org/569651
05:13:43	openstackgerrit	Vishakha Agarwal proposed openstack/python-novaclient master: No requirement of –all-tenants while listing servers https://review.openstack.org/569090
06:24:42	openstackgerrit	Nguyen Hai proposed openstack/nova-specs master: Follow the new PTI for document build https://review.openstack.org/551802
07:08:05	openstackgerrit	Jan Gutter proposed openstack/os-vif master: Add multiqueue field to InstanceInfo https://review.openstack.org/570959
07:45:58	openstackgerrit	tianhui proposed openstack/nova master: Fix bug to api-ref https://review.openstack.org/571375
08:32:16	naichuans	bauzas, Hi, Sylvain. I have some questions about your email: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130783.html. You said keep old and new rps, do you mean we will have an old compute node rp and a new compute node rp? or just a new compute node rp but keep old inventory in it?
08:34:03	bauzas	naichuans: no, I was considering to keep the same behaviour for providing the VGPU RC to the compute inventory for the first type
08:34:24	bauzas	naichuans: and just create a child RP with a new inventory for a second or more type
08:37:35	naichuans	bauzas: got it. But when could we delete it? if we use n-rp as that, the compute node rp will always have the old inventory, it prevent us from use a true n-rp implement.
08:38:14	openstackgerrit	jichenjc proposed openstack/nova master: not reraise DiskNotFound if instance is resized https://review.openstack.org/571410
08:38:41	bauzas	naichuans: by providing an online migration in Rocky
08:38:57	bauzas	naichuans: I mean, upgrading shouldn't modify the existing
08:39:05	openstackgerrit	jichenjc proposed openstack/nova master: not reraise DiskNotFound if instance is resized https://review.openstack.org/571410
08:39:28	bauzas	naichuans: but then, operators would need to use a CLI online migration for passing the VGPU inventory to a new child in between Rocky and Stein
08:41:26	naichuans	bauzas: not sure about "passing the VGPU inventory to a new child", could you explain more? thanks.
08:41:41	bauzas	naichuans: do you know about online migrations ?
08:42:36	naichuans	bauzas: no, it's something about upgrade?
08:43:21	bauzas	naichuans: yup
08:43:43	bauzas	naichuans: DB online migrations help operators to modify the DB during a cycle
08:44:40	bauzas	instead of needing to upgrade the DB offline, they just need to run the schema upgrades when upgrading offline, but then they can run the online migrations when they want
08:44:50	bauzas	after running again the computes
08:46:46	naichuans	bauzas: operator use this to modify the DB to remove old inv?
08:48:31	naichuans	bauzas: if so, we don't need to return old inv to placement in driver. we can directly move to new n-rp implement, and let operator modify DB after upgrade?
08:51:25	bauzas	naichuans: if we do that, operators need to run that upgrade script *before* restarting the compute after upgrading, which is not something we want, right?
08:56:48	naichuans	bauzas: could you give a rough flow? modify DB -> upgrade -> retarting service?
08:58:45	openstackgerrit	zhulingjie proposed openstack/nova master: Update overriden to overridden https://review.openstack.org/571418

Earlier   Later