14:00:12 #startmeeting nova_scheduler 14:00:12 Meeting started Mon Jul 31 14:00:12 2017 UTC and is due to finish in 60 minutes. The chair is edleafe. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:16 The meeting name has been set to 'nova_scheduler' 14:00:19 o/ 14:00:19 Who's here today? 14:00:25 kinda 14:00:47 o/ 14:00:48 * edleafe hands dansmith some coffee 14:01:17 \o 14:01:17 o/ 14:01:24 o/ 14:02:37 Jay Pipes doesn't seem to be around 14:02:56 Oh well, let's get started 14:02:57 #topic Specs & Reviews 14:03:05 #link Correct allocations https://review.openstack.org/#/c/488510/ 14:03:40 This series is correcting (by removing) allocations from computes 14:04:09 Since Jay isn't around, anyone else have comments on this? 14:04:19 just to be clear, 14:04:20 hey I'm here now, sorry for being late 14:04:43 I think the plan is to land that resize_confirm one, but not the full allocate-ectomy patch for pike 14:04:47 * edleafe smacks jaypipes on the wrist for tardiness 14:05:02 dansmith is correct. the last patch was an exploratory one. 14:05:07 ah 14:05:41 I had read them as a one-two punch 14:05:52 based on the functional test in https://review.openstack.org/#/c/487958/ the confirming the resize does not remove the allocation from the source host 14:06:14 gibi_: that was next up: 14:06:15 #link Test resize with placement API https://review.openstack.org/#/c/487958 14:06:34 I moved that patch to of https://review.openstack.org/#/c/488510/ 14:06:47 and made the periodic tasks run in the test 14:06:50 #undo 14:06:50 Removing item from minutes: #link https://review.openstack.org/#/c/487958 14:06:59 #link Test resize with placement API https://review.openstack.org/#/c/488510 14:07:05 sorry about that 14:07:17 and it is now fails at a stable point 14:07:39 it seems that resource clean up is missing both after confirm and revert 14:08:02 gibi_: any idea where this is going wrong? 14:08:38 what I see is that the source host still has allocations after the resize has been confirmed 14:08:47 even if I let the periodic tasks run 14:08:59 I mean the update_available_resources task 14:09:19 similarly in case of revert the target host keeps the allocation 14:09:24 gibi_: both hosts have allocations or just the source? 14:09:46 both keeping the allocations means the periodic is doing the right thing (not interfering with a migration) 14:10:01 dansmith: I have to check but I think both has the allocation 14:10:05 so I would suspect the confirm/revert logic that is supposed to collapse the double allocation 14:11:06 gibi_: your test is on top of jay's first patch above yes? 14:11:19 yeah 14:11:26 I'll look at those when we're done here 14:11:47 does that code also address resize on same host? 14:11:51 or did we punt on that? 14:11:59 we can't punt on that, 14:12:07 but that's a problem with the scheduler I think, 14:12:16 which I think happens before this 14:12:18 correct 14:12:18 dansmith: yes 14:13:16 geez, I need more coffee. The original link was correct 14:13:18 #undo 14:13:19 Removing item from minutes: #link https://review.openstack.org/#/c/488510 14:13:24 #link Test resize with placement API https://review.openstack.org/#/c/487958 14:14:17 So what's the plan to investigate this? 14:14:43 finish here so we can go look? 14:14:44 I've got a failing tempest+gabbi test that demonstrates the double allocations not happening on same host resize. probably overkill, but I was wanting to flesh out that side of things as a way to start doing multi-node stuff, but seems gibi has figured out a way to do that functionally (yay!) 14:14:54 yeah, I'm currently looking at gibi's work 14:15:11 OK, as long as this is being investigated. 14:15:15 Let's move on 14:15:24 #link Amend spec for Custom Resource Classes in Flavors https://review.openstack.org/#/c/481748/ 14:15:27 This is still not approved, although it seems fine as is. Related to this spec: 14:15:38 #link Ironic Flavor Migration https://review.openstack.org/#/c/487954/ 14:15:41 #link Improve handling of ironicclient failures https://review.openstack.org/#/c/487925/ 14:16:05 edleafe: you mean the spec amendment isn't approved? 14:16:23 dansmith: Nope 14:16:43 nope it's not approved or nope that's not what you mean? 14:16:52 Nope, it's not approved 14:17:15 it just needs some love from nova-specs cores 14:17:36 aye 14:18:29 Just for completeness, these two patch series are on hold until Queens 14:18:32 #link Devstack to use resource classes by default https://review.openstack.org/#/c/476968/ 14:18:35 #link Nested Resource Providers series starting with https://review.openstack.org/#/c/470575/ 14:18:48 why is the devstack one on hold? 14:18:59 I feel like we're not testing what we need to test if we don't do that now 14:20:01 dansmith: dtantsur put a -2 on it, so I'm assuming that it is on hold 14:20:08 it would be good to get that in 14:20:25 he said to just avoid breaking anything 14:20:31 presumably so it didn't merge before it was ready 14:21:19 Well, no activity in over a week, so I assumed it was not going to be in Pike 14:22:16 Anything else for specs/reviews? 14:22:47 #link https://review.openstack.org/#/c/489206/ 14:23:23 ^ I'm working on the common method for allocation candidates and 'GET /resource_providers' about traits 14:23:52 but not finish yet 14:24:11 alex_xu: oh, thanks - I skipped a whole section! 14:24:19 edleafe: np 14:24:22 The following are all related to filtering of RPs by Traits: 14:24:22 #link Traits support in the Allocation Candidates https://review.openstack.org/478464/ 14:24:25 #link Add traits to the ResourceProviders filters https://review.openstack.org/#/c/474602/ 14:24:28 #link Refactor of trait filtering SQLA https://review.openstack.org/#/c/489206/ 14:24:31 #link Correct resource provider set_traits() https://review.openstack.org/#/c/489205/ 14:24:44 These are all for Queens 14:25:00 cool 14:25:59 #topic Bugs 14:25:59 #link Placement bugs https://bugs.launchpad.net/nova/+bugs?field.tag=placement 14:26:25 A few new ones this week 14:27:18 All related to the ongoing allocation work 14:27:35 Anything else to discuss about bugs? 14:28:12 #topic Open discussion 14:28:47 What's on you mind? Anything? 14:29:02 Or are we all anxious to get back to what we were doing? 14:29:39 edleafe: seems the latter, conversations rage over in #openstack-nova 14:30:00 yeah, what I was thinking too 14:30:01 OK then. Thanks everyone! 14:30:01 #endmeeting