Earlier  
Posted Nick Remark
#openstack-nova - 2017-08-16
13:50:23 jaypipes dansmith: the patch from pas-ha?
13:51:04 jaypipes dansmith: oh, the one from dtantsur. yeah, I'm good on that oie.
13:51:05 jaypipes one.
13:58:23 dansmith jaypipes: dtantsur: backport is here: https://review.openstack.org/#/c/494216/1
13:58:31 dtantsur nice, thanks!
13:58:33 dtantsur vdrok: ^^^
13:58:51 dtantsur I'll be out for PTO the next two days, vdrok will be your contact point wrt scheduling :)
13:58:51 vdrok oh, thanks dansmith ! also morning
13:58:58 dansmith vdrok: :P
14:33:03 mnaser in preparing for a newton -> ocata upgrade and to avoid accidentally having nova-compute instances that were somehow not running newton, is it reliable/accurate to verify the `version` field in the `services` table?
14:33:17 mnaser it looks like version 15 was newton, so assuming they're all 15, should be good to go
14:37:08 dansmith mnaser: meaning verify that if service.version==15, that means they're all running newton (i.e. no un-upgraded mitaka computes still left) ?
14:37:16 mnaser dansmith correct
14:37:46 dansmith mnaser: yeah that's a reasonably legit thing to do
14:38:00 mnaser dansmith also thinking now it would be nice if this is part of nova-status upgrade check
14:38:03 dansmith mnaser: you can get the number by looking at nova/objects/service.py
14:38:04 mnaser (but im sure contributions welcome)
14:38:21 mnaser yeah, i found that part, looks like master is up to 17, ocata is 16
14:38:34 dansmith it's not one per release, fyi,
14:38:47 dansmith but each release should have some terminal number which won't change until the next one
14:39:02 mnaser yeah i was going off the number in stable/<x>
14:39:14 mnaser which i assume won't change unless something major is going on
14:41:50 openstackgerrit Balazs Gibizer proposed openstack/nova master: Clean up resources at shelve offload https://review.openstack.org/493834
14:41:50 openstackgerrit Balazs Gibizer proposed openstack/nova master: test shelve and shelve offload with placement https://review.openstack.org/493062
14:42:52 openstackgerrit Balazs Gibizer proposed openstack/nova master: replace chance with filter scheduler in func tests https://review.openstack.org/491529
14:43:24 gibi jaypipes: If fixed your comments in the shelve offload bugfix ^^
14:43:33 gibi jaypipes: s/If/I/
15:15:26 openstackgerrit Pavlo Shchelokovskyy proposed openstack/nova master: Shuffle best hosts from weighed hosts https://review.openstack.org/494136
15:23:01 openstackgerrit Merged openstack/nova master: Fix reporting inventory for provisioned nodes in the Ironic driver https://review.openstack.org/492964
15:23:47 dtantsur dansmith: ^^^ w00t
15:24:01 dansmith hah
15:24:25 dansmith jaypipes: dtantsur: can you throw a +1 on the backport?
15:24:26 dansmith https://review.openstack.org/#/c/494216/1
15:24:33 dtantsur totally, lemme see
15:24:42 dansmith I think I'm the only one around that can land that so it'd be good to have some backup +1s on there :)
15:28:00 dtantsur mind is there :)
15:28:20 dtantsur I've wait for an ironic job before, but I have no idea what exactly it's going to run, given that ironic does not have stable/pike yet..
15:28:31 dtantsur so it may fail for a random reason
15:29:17 dansmith sorry, are you saying we should wait?
15:32:49 dtantsur dansmith: no, I'm saying we unfortunately cannot..
15:32:56 dansmith ack
16:09:24 dansmith I guess we won't be getting jay then
16:09:58 cdent dansmith: is he on weird hours right now? I saw reviews from him at 8am-ish my time this morning
16:10:15 dansmith yeah he's in russia or whatever
16:12:12 cdent somewhere eastness
16:16:18 dansmith johnthetubaguy: still around?
16:29:42 melwitt dansmith: the stable/ocata stack is all merged, so we just need to approve stable/newton here https://review.openstack.org/#/c/491844/
16:30:03 melwitt or tonyb ^
16:31:12 dansmith melwitt: yep done
16:31:30 melwitt ty
16:32:33 dansmith also assuming we're punting the cells meeting again today
16:33:31 melwitt yep same
16:33:40 melwitt we are mriedemless
16:37:00 melwitt speaking of that, I'm going to be out on PTO mon-wed next week, FYI
16:37:20 openstackgerrit John Griffith proposed openstack/nova master: Implement new attach Cinder flow https://review.openstack.org/330285
16:37:51 dansmith okay
16:40:59 openstackgerrit John Griffith proposed openstack/nova master: Implement new attach Cinder flow https://review.openstack.org/330285
16:47:22 openstackgerrit Chris Dent proposed openstack/nova master: WIP: Account for shared storage in the report client https://review.openstack.org/491098
16:47:23 openstackgerrit Chris Dent proposed openstack/nova master: WIP: Add functional resize tests using shared storage https://review.openstack.org/490733
17:18:55 openstackgerrit David Rabel proposed openstack/nova master: Adds support for gracefull shutdown for VMware instances https://review.openstack.org/494169
17:22:43 openstackgerrit Ken'ichi Ohmichi proposed openstack/nova master: Fix contributor documentation https://review.openstack.org/494277
17:42:35 openstackgerrit Pavlo Shchelokovskyy proposed openstack/nova master: Shuffle best hosts from weighed hosts https://review.openstack.org/494136
18:28:29 dansmith melwitt: you wanna send this? https://review.openstack.org/#/c/493963/4
18:28:44 dansmith it's just a "don't end up with things that sum to zero 'cause placement will reject it" sort of deal
18:34:17 melwitt dansmith: on it
18:42:08 melwitt dansmith: +W
18:42:15 dansmith thanks
18:42:21 dansmith cdent: you gonna propose the backport?
18:42:28 cdent can do, sure
18:42:32 dansmith it'd be nice if someone else would since I have to +2+W these
18:42:33 dansmith thanks
18:47:14 cdent dansmith: oh, am I supposed to wait until it merges? it seems that not doing so has meant it doesn’t get the nice references to the commit. oops.
18:47:40 dansmith cdent: you should be fine to use the current hash with cherry-pick -x
18:48:30 dansmith which shouldn't change unless we have to modify the current one
18:48:34 dansmith which is unlikely
18:48:56 melwitt dansmith: have you seen this or heard of some discussion about it? it makes the scheduler always spread instead of pack https://review.openstack.org/#/c/494136
18:49:32 dansmith melwitt: I think someone poked jay about that this morning but I havent' looked at all
18:49:44 melwitt okay. I'm just surprised by it
18:50:04 dansmith cdent: if you can update that backport with the header that'd be cool, otherwise I'll just wait and do it when it merges.. at least you'll be the owner that way
18:50:12 cdent yeah, wil do
18:50:18 dansmith I'll check on it when I get back from lunch
18:50:22 dansmith thanks
18:53:10 cdent never try to interact with gerrit while also trying to interact with panicking daugher and mother
19:11:33 cdent melwitt, dansmith: why is it that some people love pack so much?
19:11:49 cdent that fix looks right on for the ironic case
19:12:23 cdent (because it is only randomize those hosts in the weighted list that match the first weight)
19:14:01 melwitt cdent: I'm not certain how much they love it but it's currently possible to pack and after this change I think it's not, correct? the use case for fill-first is the ability to schedule large instances. in spread-first, you could easily lose the ability to schedule large instances
19:14:32 melwitt yeah, I understand for ironic it would be fine. but this is changing it across the board, right?
19:15:01 cdent if you want a resource provider to be for large instances, just set min_unit > 1 on it’s resource?
19:15:33 cdent I’m slightly kidding on that. I know that we have to maintain existing behaviors and expectations, but still… also s/'//
19:15:35 melwitt at the very least, there should be a release note that explains that fill-first is no longer possible to signal the change in behavior
19:16:38 melwitt this is the sort of thing we'd usually email the operators ML about to get a quick check if anyone cares about fill-first anymore
19:18:27 melwitt and if there's a way to address the use case with resource provider settings, then that's probably fine. something to include in the release note
19:19:04 dansmith cdent: spreading uses more power, means lower utilization on your hosts, and in the case of windows, makes you bleed on the license fee like crazy
19:20:25 cdent there’s an easy fix to that windows problem :) no, I get it, I just, meh, reality...
19:21:35 cdent hmm, so right now in libvirt at least, we provide now way to control min_unit. I guess we’ll want to change that eventually
19:22:23 melwitt yeah, and I want to know why setting host_subset_size isn't sufficient. that's the knob for adjusting the spread or pack
19:22:41 melwitt it's mentioned in the commit message but I didn't get what it means
19:26:21 cdent melwitt: do jay and pavlo cover that in their discussion on ps2?
19:27:35 cdent heh, and simultaneously jay said the same thing on the review

Earlier   Later