Earlier  
Posted Nick Remark
#openstack-nova - 2018-02-21
17:19:21 hrw jaypipes: 0 pcie ports == unbootable machine
17:19:41 hrw unless all you want is uefi shell on serial port
17:20:21 hrw and if you want such setup then nova is at least one layer too high
17:21:10 hrw jaypipes: I probably should expand option's comment
17:33:51 openstack Launchpad bug 1750084 in OpenStack Compute (nova) "Report client associations include non-sharing providers" [Undecided,In progress] - Assigned to Eric Fried (efried)
17:33:51 melwitt mriedem: I added https://bugs.launchpad.net/nova/+bug/1750084 to the rc todos etherpad because it was tagged as queens-rc-potential, fyi
17:35:06 mriedem efried_omalley: why is that rc potential?
17:36:00 efried_omalley mriedem: Because it hits on every update_compute_node, and in situations where you have big aggregates, you'll be wiring and caching a lot of unnecessary data.
17:36:17 efried_omalley mriedem: I suppose if we make the argument that people aren't going to be using aggregates in Q, we don't need it.
17:36:44 efried_omalley But that discussion needed to happen, hence "potential" :)
17:37:07 mriedem the only case i know of where people might use aggregates in placement is routed networks via neutron uses them
17:37:17 efried_omalley How big can those get?
17:37:20 mriedem idk
17:38:11 efried_omalley For each aggregate-associated provider, we get the provider record, its inventory, its traits, and its aggregates (just the UUIDs, not associated providers).
17:38:36 hrw jaypipes: need to do some testing and then will push update to config stuff
17:38:40 openstackgerrit Dan Smith proposed openstack/nova master: Avoid exploding if guest refuses to detach a volume https://review.openstack.org/546423
17:38:49 efried_omalley So that's four unnecessary API calls, and caching the concomitant data, per non-sharing aggregate-associated provider.
17:41:04 mriedem efried_omalley: so if i'm working on my local CN1 and it's shared via aggregate to another provider SSP, it's also going to pull down anything related to SSP?
17:41:24 efried_omalley Yes.
17:41:41 mriedem and anything that is also related to SSP?
17:41:50 mriedem anything else i mean, like if CN2 is also shared with SSP?
17:41:52 efried_omalley Yes, with the bug, it'll also pull down CN2-CN999 if they're in the same aggregate as CN1
17:41:56 openstackgerrit Marcin Juszkiewicz proposed openstack/nova master: Allow to configure amount of PCIe ports https://review.openstack.org/545034
17:41:58 mriedem ffs
17:42:17 mriedem well then i guess it is probably worth doing an RC3
17:42:21 hrw jaypipes: config part left
17:42:42 efried_omalley Did I drop the ball here? Was I supposed to tag it sooner? Or manually alert someone to look at it?
17:43:25 mriedem RC2 was friday so you wouldn't have had time anyway
17:44:37 efried_omalley when did I tag it?
17:44:48 mriedem you created the bug on saturday
17:44:53 mriedem anyway, i'm going to be busy for the next hour or so
17:45:01 mriedem so someone else is going to have to dig into it from the core team
17:50:33 openstackgerrit Jay Pipes proposed openstack/os-traits master: Add compute capabilities traits https://review.openstack.org/546713
17:50:40 jaypipes mriedem: ^
18:03:45 melwitt dansmith: you're familiar with the placement provider tree stuff right? if so, it would be good if you could review this bug fix from efried_omalley https://review.openstack.org/545494
18:06:26 melwitt it's a candidate for rc3
18:07:41 dansmith I'm not really, but I'll try to look in a sec
18:08:51 kukacz hi, what determines where nova instance configdrive is stored? is it tied to image storage backend as set in `images_type` in nova-compute.conf?
18:09:17 melwitt dansmith: noted. thanks
18:10:35 dansmith melwitt: ah, this isn't specifically tree related stuff
18:11:14 melwitt the other rc3 candidate is https://review.openstack.org/#/c/545478 which is a simple one to handle specific multiattach exceptions in compute/api
18:12:33 dansmith melwitt: that one is just to avoid raising InvalidBDMVolume for those cases?
18:12:41 dansmith are those caught in the api layer and handled differently?
18:12:42 melwitt yes
18:13:48 melwitt yeah, catch them and reraise them instead of letting it fall through to Exception where it raises a generic unhelpful InvalidBDMVolume
18:14:36 dansmith jebus that's a huge list of exceptions caught around create_server
18:14:37 dansmith oof
18:17:12 melwitt dansmith: which? that there will be 4 now?
18:17:52 dansmith melwitt: no, where it's caught in the api: https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/servers.py#L576-L625
18:18:12 melwitt oh, yes. that's an epic list
18:21:40 melwitt mriedem: both rc3 changes are traveling gateward. I'll propose the release patch when I know which hash to use
18:30:04 cdent johnthetubaguy: is this permanently dead, or may come back to life? https://review.openstack.org/#/c/438640/ (spot instances). Or is blazar taking its place, or maybe preemptible as cern's doing it? http://openstack-in-production.blogspot.co.uk/2018/02/maximizing-resource-utilization-with.html
18:31:50 openstackgerrit melanie witt proposed openstack/nova stable/queens: Fix error handling in compute API for multiattach errors https://review.openstack.org/546729
18:34:16 melwitt efried_omalley: do you want to propose the backport for your bug fix to stable/queens?
18:34:32 efried_omalley melwitt: I'd be happy to. Did we decide it's backport-worthy?
18:34:47 melwitt I think it has to be if it's for queens rc3
18:36:12 melwitt backing up, yes, based on what you and mriedem said about the severity earlier I think we should
18:36:26 efried_omalley melwitt: Roger wilco, stand by.
18:36:40 melwitt thanks
18:39:10 efried_omalley melwitt: Quit standing by. Gonna be a manual one.
18:39:41 melwitt ah, bummer. good luck
18:44:25 efried_omalley ahjeez, it's because of all our diligent work getting contexts passed around everywhere.
18:44:56 efried_omalley some of which is in Q, some not.
18:55:58 efried_omalley ...which would have to be redone if we plan to merge https://review.openstack.org/#/q/project:openstack/nova+topic:bug/1734625+branch:stable/queens -- mriedem, melwitt thoughts?
18:56:43 openstackgerrit Eric Fried proposed openstack/nova stable/queens: Only pull associated *sharing* providers https://review.openstack.org/546740
18:56:48 efried_omalley melwitt: ^
18:56:54 melwitt efried_omalley: can we just backport more things to stable/queens to provide the needed base? or is it more than a few patches?
18:57:21 efried_omalley melwitt: See commit message.
18:57:31 efried_omalley The additonal backport would be smallish.
18:57:38 efried_omalley But I've already done the un-rebase :)
18:57:49 efried_omalley melwitt: So it's your call, o great and powerful.
18:59:58 melwitt okay. I think we'd usually just pull in the prereq patches too, assuming they meet stable branch requirements. I'd like mriedem's recommendation when he's around
19:00:24 melwitt we've got some time before the changes on master merge anyway
19:01:14 cdent efried_omalley: is the blocker still the context stuff? having the rest of that is a useful backport
19:01:25 efried_omalley cdent: Not a blocker, but yes.
19:13:54 cdent edleafe, efried_omalley, jaypipes: I'm going off-grid as much as possible until sunday evening shortly. Anything I should attend before I do?
19:14:29 efried_omalley cdent: I think you've +1ed all the stuff I care about :)
19:14:50 efried_omalley So yeah, quick, go offline before you change your mind about any of it.
19:14:52 cdent oh, that's just my efried+1 bot, not me
19:22:32 efried_omalley I need to let ubuntu upgrade a bunch of software. So I may not be back. Wish me luck.
19:25:34 mriedem ok so what's going on? we need https://review.openstack.org/#/q/project:openstack/nova+topic:bug/1734625+branch:stable/queens to make the backport of https://review.openstack.org/545494 clean?
19:27:13 mriedem we could take those for rc3, they are just large and i figured they weren't super high priority for an RC
19:29:45 openstackgerrit Mohammed Naser proposed openstack/nova master: Ensure attachment_id always exists for block device mapping https://review.openstack.org/546398
19:29:50 melwitt yeah. backport was messy/manual because that refactor isn't in stable/queens
19:29:57 jaypipes cdent: nope, see you in Dublin
19:30:06 cdent
19:35:05 ingy
19:40:28 openstackgerrit Hongbin Lu proposed openstack/nova master: Skip placement on rebuild in same host https://review.openstack.org/546357
19:40:59 efried woot
19:45:31 openstackgerrit Hongbin Lu proposed openstack/nova master: Handle IpAddressAlreadyAllocated exception https://review.openstack.org/535532
19:53:47 melwitt efried, mriedem: upon looking at the backport now I think it's good as-is
19:54:09 edleafe cdent: we got it.
20:10:47 Nasir Hi i needed assistance trying to figure out why I cannot retrieve the serial console of my ironic/baremetal instance from nova, even though its configured properly in ironic
20:12:32 Nasir This is what i see when i try to do "nova get-serial-console 'https://thepasteb.in/p/pghQLXy7ZkmHR
20:13:17 Nasir https://thepasteb.in/p/NxhVxv9661JiN
20:18:28 Nasir Can anyone assist please ? Thanks
20:29:50 melwitt Nasir: this is a nova development channel, please see topic
20:30:20 mnaser melwitt: just fyi https://review.openstack.org/#/c/546689/ -- this okay with you? :)
20:32:41 melwitt mnaser: looks cool to me
20:32:48 mriedem melwitt: this is also going to be in RC3 https://review.openstack.org/#/c/533212/

Earlier   Later