Earlier  
Posted Nick Remark
#openstack-nova - 2019-08-23
03:54:56 openstackgerrit Merged openstack/nova master: objects: Rename 'nova.objects.instance_numa_topology' https://review.opendev.org/671789
03:55:04 openstackgerrit Merged openstack/nova master: libvirt: Remove unnecessary try-catch around 'getCPUMap' https://review.opendev.org/671790
03:55:13 openstackgerrit Merged openstack/nova master: libvirt: Remove unnecessary argument https://review.opendev.org/674396
03:55:23 openstackgerrit Merged openstack/nova master: claims: Remove useless caching https://review.opendev.org/671791
05:40:17 openstackgerrit zhufl proposed openstack/nova master: [Trivial]Remove unused helper get_vif_devname_with_prefix https://review.opendev.org/678136
06:16:03 openstackgerrit Yongli He proposed openstack/nova master: Add server sub-resource topology API https://review.opendev.org/621476
06:19:51 openstackgerrit Yongli He proposed openstack/nova master: Add server sub-resource topology API https://review.opendev.org/621476
07:41:13 AJaeger nova stable cores, could you review https://review.opendev.org/677178, https://review.opendev.org/677176 https://review.opendev.org/677177 ? Those remove experimental openSUSE 42.3 jobs since the distro is end-of-life now.
07:43:55 lyarwood AJaeger: ack, I'll take a look now
07:45:08 lyarwood AJaeger: nothing on stable/stein?
07:45:36 AJaeger lyarwood: no, that one uses the newer opensuse-150 job already
07:45:45 AJaeger thanks, lyarwood
07:46:27 lyarwood Ib0b49fead613d06001df348831c022edfe8d0fd1 - got it, thanks
08:47:28 openstackgerrit Yongli He proposed openstack/nova master: Add server sub-resource topology API https://review.opendev.org/621476
08:51:44 cervigni hello
08:51:52 cervigni I am playing around with vgpu
08:52:11 cervigni It seems that the nova scheduler does not assign properly the cpu-> gpu
08:52:33 cervigni essentially the first vgpu that is always created by the scheduler, goes to my 2nd gpu
08:52:46 cervigni while the cores are assigned to first cpu (first numa node)
08:53:22 cervigni is there a way to tweak the scheduling algorithm or to specify somehow that there is an affinity between CPU and VGPUs ?
08:53:52 cervigni as it stands, instances always get first cpus / second gpu
08:54:17 cervigni therefore there is a big numa issue and performance penality where instances are communicating with the "opposite" numa node in the other cpu socket
08:56:15 cervigni it seems to me a real nova scheduling issue, but I would like someone to confirm that is the case before opening a bug report
08:56:24 openstackgerrit Mitsuhiro Tanino proposed openstack/nova master: Smaller project quota value than user quota value can't be set https://review.opendev.org/678183
08:57:35 cervigni GPU 0 has a pci id lower than GPU 1, but for reasons I don't understand, the VGPUs are always first assigned to GPU1
08:57:39 cervigni |===============================+======================+======================|
08:57:39 cervigni | 0 Tesla V100-PCIE... On | 00000000:37:00.0 Off | Off |
08:57:39 cervigni | N/A 38C P0 27W / 250W | 39MiB / 16383MiB | 0% Default |
08:57:39 cervigni +-------------------------------+----------------------+----------------------+
08:57:39 cervigni | 1 Tesla V100-PCIE... On | 00000000:86:00.0 Off | Off |
08:57:39 cervigni | N/A 35C P0 29W / 250W | 51MiB / 16383MiB | 0% Default |
08:57:42 cervigni +-------------------------------+----------------------+----------------------+
08:59:02 openstackgerrit Mitsuhiro Tanino proposed openstack/nova master: Smaller project quota value than user quota value can't be set https://review.opendev.org/678183
09:05:25 openstackgerrit Mitsuhiro Tanino proposed openstack/nova master: Smaller project quota than user quota shouldn't be set https://review.opendev.org/678183
09:53:31 openstackgerrit Bhagyashri Shewale proposed openstack/nova master: Ignore root_gb for BFV in simple tenant usage API https://review.opendev.org/612626
10:48:52 stephenfin alex_xu: You should probably look at https://review.opendev.org/#/c/674894/ given your comments at https://review.opendev.org/#/c/664420/42/nova/scheduler/request_filter.py@206
11:18:52 efried sean-k-mooney: I agree. I skimmed over your review last night, sounds like what I was expecting.
11:19:28 sean-k-mooney efried: i might try and submit a basic patch to show how to do it as i suggested instead
11:19:41 sean-k-mooney efried: i assume we are talking about cyborg privsep
11:19:48 efried yes
11:20:46 sean-k-mooney i think i was a little harsh in the review but i also have strong feeling about this topic.
11:26:28 efried Swhy I was hoping you would look at it.
11:47:05 sean-k-mooney efried: well i review in cyborg octionally and is mostly negitve when i do. not alway but my +/- raition there is proably not that positive. so i do try to make sure my review that i do there are at least constructive rather then saying "no this is all terible" and suggest how it can be improved. but if i do my usuall 50 billion comments on each indiviaual issue that can come across badly if in a
11:47:07 sean-k-mooney "drive by" review.
11:53:30 openstackgerrit Eric Fried proposed openstack/nova master: Use SDK for setting instance id https://review.opendev.org/659690
11:53:31 openstackgerrit Eric Fried proposed openstack/nova master: Use SDK for add/remove instance info from node https://review.opendev.org/659691
11:53:31 openstackgerrit Eric Fried proposed openstack/nova master: Use SDK for getting network metadata from node https://review.opendev.org/670213
11:54:53 efried sean-k-mooney: Any update on that libvirt attribute ordering bug? Not sure if I missed something going past...
11:58:12 sean-k-mooney efried: its still on my todo list. i was dealing with a downstream backport the last day or two but i should get to it today or monday.
11:58:50 efried cool, thanks. It's a "requirements freeze" thing fwiw.
11:59:12 sean-k-mooney oh ya when is that next week?
11:59:31 sean-k-mooney i was aware of that but i proably should expidite looking at it
11:59:56 sean-k-mooney non-client lib frezee shoudl m3 -2 weeks
11:59:57 efried oh, I thought it was, but no, it's the week of Sept 9
12:00:05 sean-k-mooney and oslo shoudl be m3 -3
12:00:16 sean-k-mooney i guess requirement freeze is m3-1
12:01:12 sean-k-mooney actully it looks like its m3
12:01:35 sean-k-mooney so september 12th
12:01:58 sean-k-mooney but ill try and repoduce anyway this/next week and get a patch up so we dont run up against it
12:03:20 sean-k-mooney is this a shorter release by the way. it feels a little compressed. the freeze dates are all 1 week later then i expect in my head
12:04:29 sean-k-mooney maybe im just used to makeing sure everythin is in os-vif on time and i naturally try to have the last week to make sure we dont have any bugs before the freeze
12:49:53 dougsz nova-manage db online_data_migrations <- Do I need to run that per cell, or is that a top level only thing? Ref: https://docs.openstack.org/nova/latest/user/upgrade.html
12:51:01 AJaeger nova stable cores, could I get a second +2 on https://review.opendev.org/677178, https://review.opendev.org/677176 https://review.opendev.org/677177, please ? Those remove experimental openSUSE 42.3 jobs since the distro is end-of-life now.
12:54:22 sean-k-mooney AJaeger: do we have a replacement suse job either based on tumbelweed or a more recent leap release
12:55:21 sean-k-mooney AJaeger: or rather do we have opensuse node sets so a replacment job could be built if needed
12:57:12 AJaeger sean-k-mooney: yes, in master and stein already
12:57:25 sean-k-mooney cool
12:57:51 AJaeger but I didn't want to add new distro support to old stable branches that only have an experimental job
12:58:08 sean-k-mooney ya makes sense
12:58:27 AJaeger sean-k-mooney: there's job tempest-full-py3-opensuse150:
12:58:39 AJaeger (still experimental) in master and stein
12:59:17 sean-k-mooney im not sure experimental jobs add much value on stable as they will be used even less often then master. but its still better then nothing
13:01:28 sean-k-mooney or in other words removing an experimal job form stable that is on an unsupproted os/is broken is pretty safe
13:02:46 AJaeger agreed
13:57:18 openstackgerrit Balazs Gibizer proposed openstack/nova master: Do not log token in the novncproxy logs https://review.opendev.org/678234
14:05:37 openstackgerrit Eric Fried proposed openstack/nova master: Update SDK fixture for openstacksdk 0.35.0 https://review.opendev.org/678237
14:11:49 openstackgerrit Matt Riedemann proposed openstack/nova master: Process [compute] in $NOVA_CPU_CONF in nova-next https://review.opendev.org/672800
14:11:53 alex_xu stephenfin: nice
14:13:25 alex_xu mriedem: I replied your email, let me know what can make you have more confidence on this
14:15:46 dansmith artom: you've got a bunch of legit unit test fails
14:16:15 artom dansmith, yeah, those have been fixed locally
14:16:16 dansmith artom: I'm also concerned about the validity of some of the other tests that aren't failing even though you're using the wrong dst_numa_config in some of the code and/or tests
14:16:37 dansmith artom: okay cool, I just lightly dusted the bottom several patches with more comments
14:16:41 artom dansmith, I think that's because I was asserting obj.dst_numa_config and setting it as well
14:16:46 dansmith up to the one you said was the top of the things you've updated
14:17:08 artom So the code sets dst_numa_config, and the test checks it as well
14:17:12 dansmith artom: okay, I guess just setting a non-field property on the object, okay
14:17:20 artom dansmith, yeah
14:17:34 dansmith well, let's make sure to get all those right :D
14:17:45 artom dansmith, so you're saying I need to squash the RPC changes into the top patch?
14:17:49 dansmith I guess no real testing was done with the updated set since the top weren't updated anyway
14:17:58 artom I split them to keep patch size as small as possible
14:18:04 artom But looks like it'll be unavoidable here :(
14:18:11 artom dansmith, yeah, grep took care of that
14:18:45 dansmith artom: squash the rpc one with the top one because of the version/capability advertisement?
14:18:52 artom dansmith, yeah
14:19:18 dansmith that's probably too obtuse of a solution.. I mean it'll work I guess, but hopefully we can split them a little more than that
14:19:37 dansmith flipping their order is probably better
14:20:03 artom Ohhh
14:20:11 dansmith get the code in place, just don't allow it to be called from RPC until the second one, where you actually bump the versions and add the params

Earlier   Later