Posted	Nick	Remark
#openstack-nova - 2018-05-31
20:21:50	mriedem	it's not like huawei doesn't make changes
20:21:53	cfriesen	mriedem: sorry, missed your earlier question. I was referring to providing CPU pinning (and hugepages) consumption data to an admin user via the API.
20:21:54	mriedem	but i fight the same battle internally
20:22:18	mriedem	cfriesen: sure but on the servers API or the hypervisors API?
20:22:50	cfriesen	mriedem: ours is on the servers API, but we're private cloud and let people see more host-side info
20:23:15	mriedem	well, you could do it on the servers API sure, we expose host/node etc, and that's controlled via policy
20:23:19	mriedem	the same could be done here
20:23:41	mriedem	someone just has to, you know, propose that api change in a spec first
20:24:17	mriedem	artom: thanks for making those changes to the trusted vf series btw
20:24:45	cfriesen	mriedem: http://paste.openstack.org/show/722471/ <-- an example of the stuff we added to "nova show"
20:26:11	artom	mriedem, sure, thank you for finalizing your own nits :)
20:26:21	openstackgerrit	Matt Riedemann proposed openstack/nova master: Match ComputeNode.uuid to ironic node uuid in RT https://review.openstack.org/571535
20:27:25	mriedem	cfriesen_away: those don't seem crazy, and the nics thing is actually something that's been discussed a few times upstream, i.e. cleaning up GET /servers/{id}/ips and making the 'addresses' field in the existing response more useful
20:28:32	melwitt	this is something where I feel like if we had enough info to put together a backlog spec, it might be something various contributors in the community might like to work on
20:30:05	mriedem	reminds me of https://review.openstack.org/#/q/topic:521392+(status:open+OR+status:merged) which was approved, then needed a spec update, and seems to have been abandoned now
20:37:27	dansmith	mriedem: I'm surprised that nics thing doesn't run contrary to your no-proxies leanings
20:39:07	openstackgerrit	Matt Riedemann proposed openstack/nova master: Add osprofiler config options to generated reference https://review.openstack.org/571225
20:39:40	mriedem	dansmith: i lean whichever way the winds of cash blow me
20:39:48	dansmith	oh, well, then
20:40:50	mriedem	we still have things like os-volume_attachments to show bdms attached to an instance, and os-interfaces to show ports attached to an instance,
20:41:03	mriedem	and we've talked about leveraging those to return the tags associated with those devices
20:41:12	mriedem	so we'll still have some things in the API as long as they are per-server
20:41:30	mriedem	definitely not the stuff we had before, like CRUD ops on volumes/images/ports/networks
20:46:46	openstackgerrit	Merged openstack/nova master: PowerVM Driver: vSCSI Fibre Channel volume adapter https://review.openstack.org/526094
20:46:53	openstackgerrit	Merged openstack/nova master: PowerVM snapshot cleanup https://review.openstack.org/568988
20:47:08	dansmith	volume attachments shows the mapping, but exposing things like the mtu is getting pretty specific
20:47:23	dansmith	os-interfaces definitely exposes more stuff like that
20:48:12	dansmith	but I dunno, I just don't know how to answer the question of why we don't have CRUD operations for all the values we expose from other services
20:48:52	dansmith	I get the desire and need to be able to easily get all the IPs for the interfaces associated with the host, but not really network-specific things like mtu
20:48:59	dansmith	s/host/instance/
20:52:50	melwitt	dansmith: last patch for powervm merged so I've updated the runways, if you could do the honors updating the channel topic pls https://etherpad.openstack.org/p/nova-runways-rocky
20:54:27	melwitt	thanks
20:55:17	dansmith	yup
21:04:36	openstackgerrit	Zack Cornelius proposed openstack/nova master: Implement file backed memory for instances in libvirt https://review.openstack.org/567876
21:09:16	cfriesen	dansmith: personally I agree...I'd actually be fine with declaring that you have to pre-create ports in neutron and then pass them to nova. if desired the client could cross-reference with neutron for detailed info.
21:10:41	dansmith	yeah, I also understand the network-id being there to assist in the mapping process, but anything that's not mapping should really be fetched from neutron I think
21:13:17	cfriesen	in case it's not apparent, for dedicated cpus or multi-numa-node instances the "wrs-res:topology" line would have additional information
21:19:44	cfriesen	what's the story with "meta.js" in the guest...is it still expected to work? I thought I remembered something about getting away from file injection.
21:28:37	openstackgerrit	Matt Riedemann proposed openstack/nova master: Mention running rootwrap in daemon mode if hitting vif plug timeouts https://review.openstack.org/571577
21:34:03	openstackgerrit	Julia Kreger proposed openstack/nova master: ironic: add instance_uuid before any other spawn activity https://review.openstack.org/563722
21:54:35	openstackgerrit	Jay Pipes proposed openstack/nova master: placement: always create consumer records https://review.openstack.org/567678
21:54:36	openstackgerrit	Jay Pipes proposed openstack/nova master: add consumers generation field https://review.openstack.org/557958
21:54:37	openstackgerrit	Jay Pipes proposed openstack/nova master: placement: Allocation.consumer field https://review.openstack.org/565405
21:54:38	openstackgerrit	Jay Pipes proposed openstack/nova master: rework allocation handler _allocations_dict() https://review.openstack.org/565407
21:54:39	openstackgerrit	Jay Pipes proposed openstack/nova master: Add a microversion for consumer generation support https://review.openstack.org/565604
21:56:30	openstackgerrit	Jan Gutter proposed openstack/os-vif master: Add multiqueue port profile for VIFGeneric https://review.openstack.org/570959
21:57:21	openstackgerrit	Jan Gutter proposed openstack/nova master: Pass virtio multiqueue info to os-vif plugins https://review.openstack.org/571462
21:57:22	openstackgerrit	Jan Gutter proposed openstack/nova master: Convert vrouter legacy plugging to os-vif https://review.openstack.org/571325
21:58:52	mriedem	cfriesen: personality files (file injection) was deprecated from the api in queens
21:59:18	mriedem	https://specs.openstack.org/openstack/nova-specs/specs/queens/implemented/deprecate-file-injection.html
21:59:56	mriedem	cfriesen: and i assume you meant meta_data.json?
22:00:02	mriedem	you just wouldn't get the 'files' key in there anymore
22:05:28	openstackgerrit	Jay Pipes proposed openstack/nova master: Add a microversion for consumer generation support https://review.openstack.org/565604
23:11:00	openstackgerrit	Merged openstack/nova stable/ocata: Avoid showing password in log https://review.openstack.org/561851
#openstack-nova - 2018-06-01
00:43:47	openstackgerrit	wanghongtao proposed openstack/nova master: Fix the metadata re to match the unicode https://review.openstack.org/536236
01:59:49	openstackgerrit	tianhui proposed openstack/nova master: Fix bug to api-ref https://review.openstack.org/571375
02:25:09	openstackgerrit	Yikun Jiang (Kero) proposed openstack/nova master: Fix invalid raise in test_compute_mgr https://review.openstack.org/571610
02:27:20	openstackgerrit	Merged openstack/nova stable/queens: libvirt: Skip fetching the virtual size of block devices https://review.openstack.org/571425
04:19:18	openstackgerrit	Merged openstack/nova master: libvirt: configure trust mode for vfs https://review.openstack.org/458514
04:23:58	openstackgerrit	Vishakha Agarwal proposed openstack/python-novaclient master: No requirement of –all-tenants while listing servers https://review.openstack.org/569090
04:25:02	openstackgerrit	Vishakha Agarwal proposed openstack/python-novaclient master: No requirement of –all-tenants while listing servers https://review.openstack.org/569090
07:34:16	openstackgerrit	Yikun Jiang (Kero) proposed openstack/nova master: Adapt _validate_instance_group_policy to new policy model https://review.openstack.org/571465
08:23:22	openstackgerrit	Elod Illes proposed openstack/nova stable/pike: placement: Fix HTTP error generation https://review.openstack.org/571218
08:47:56	openstackgerrit	jichenjc proposed openstack/nova master: z/VM Driver: Initial change set of z/VM driver https://review.openstack.org/523387
08:47:57	openstackgerrit	jichenjc proposed openstack/nova master: z/VM Driver: Spawn and destroy function of z/VM driver https://review.openstack.org/527658
08:47:58	openstackgerrit	jichenjc proposed openstack/nova master: z/VM Driver: add snapshot function https://review.openstack.org/534240
08:47:59	openstackgerrit	jichenjc proposed openstack/nova master: z/VM Driver: add power actions https://review.openstack.org/543340
08:48:00	openstackgerrit	jichenjc proposed openstack/nova master: z/VM Driver: add get console output https://review.openstack.org/543344
09:19:25	openstackgerrit	jichenjc proposed openstack/nova master: not reraise DiskNotFound if instance is resized https://review.openstack.org/571410
09:26:08	sahid	jaypipes: hello, if I can ask you, I think we made with matt some good progress with the trsuted-vf feature
09:26:11	sahid	https://review.openstack.org/#/q/topic:bp/sriov-trusted-vfs+(status:open+OR+status:merged)
09:26:23	sahid	can you have a look when you have a moment
09:42:29	openstackgerrit	Stephen Finucane proposed openstack/nova-specs master: Add 'numa-aware-vswitches' spec https://review.openstack.org/541290
09:58:28	sahid	jangutter: if you can address the last comment https://review.openstack.org/#/c/570959/ I will +2 your patch so when sean is comming back that will be approved
10:02:29	jangutter	sahid: thanks! I'm happy to whack that. But, check the nova patches out for another wrinkle, it seems this route might only be useful for some very esoteric cases and not be needed after all.
10:10:39	sahid	jangutter: ok will look at that
11:25:22	openstackgerrit	Chen proposed openstack/nova master: WIP https://review.openstack.org/571472
12:12:54	openstackgerrit	Merged openstack/nova master: libvirt: add vf_trusted field for network metadata https://review.openstack.org/566343
12:16:06	openstackgerrit	Merged openstack/nova master: metadata: add vf_trusted field to device metadata https://review.openstack.org/566344
12:44:56	mriedem	the trusted vf series just has one remaining patch https://review.openstack.org/#/c/458820/
12:45:05	mriedem	and it's pretty simple
13:00:01	mriedem	stephenfin: artom: i've got some questions in the numa-aware vswitch, new ones about live migration support https://review.openstack.org/#/c/541290/
13:03:17	artom	mriedem, dammit, I was hoping I'd get to avoid that massive thing ;)
13:03:30	artom	Nah, I'll check it out, see if I can be useful
13:04:00	mriedem	stephenfin: i think for any move operation, we'll have to modify the request spec to include the current numa-aware interface information from the instance info cache so the NUMATopologyFilter can pick a proper destination host
13:04:46	stephenfin	mriedem: Yeah, I was planning to just build one of those InstanceNUMANetworks objects from instance info cache
13:04:47	mriedem	which kind of makes me wonder, if you can't attach numa-aware interfaces to a running instance, then the instance info_cache should match the original request spec's requested_networks, and then i wonder why we wouldn't persist it for move operations
13:05:05	mriedem	dansmith: ^
13:05:17	stephenfin	mriedem: You can attach them - you just won't get NUMA affinity
13:05:20	mriedem	are you guys all on happy time red hat meeting fun hour right now?
13:05:54	mriedem	stephenfin: ok so if i want to attach new numa-aware instances with affinity, i'd have to do that and then resize my instance to get it to move
13:06:01	stephenfin	I mean, I guess we could enforce that if we wanted to but the spec is already too big for its own good. I want to land _something_ :)
13:06:11	stephenfin	mriedem: At present, yes
13:06:40	stephenfin	mriedem: https://review.openstack.org/#/c/541290/15/specs/rocky/approved/numa-aware-vswitches.rst@405
13:06:49	stephenfin	giblet: Thanks for the reminder
13:07:04	mriedem	finucannot: yeah i know it says that
13:07:55	mriedem	finucannot: i know you want to land something,
13:08:15	mriedem	but i also don't want to land a gaping hole that we don't fix for 4 years like the existing numa stuff
13:09:01	mriedem	so what does the "claim" actually do?
13:09:05	mriedem	since we won't have a claim during live migration

Earlier   Later