Earlier  
Posted Nick Remark
#openstack-nova - 2017-07-27
20:20:58 efried sdague Which we then look up in service-types-authority to get the service_type, which is indeed `image`
20:20:58 mriedem just for testing at this point
20:21:27 sdague efried: ok, I was surprised we couldn't just call it image to start with, but if that's how it is, that's fine
20:21:36 jaypipes mriedem: coo.
20:21:56 sdague efried: do we have a test job running this with api_servers not set in devstack?
20:22:18 mriedem jaypipes: "is recalculate the allocation (which will be the doubled-up thing) on the source host RT and remove all entries in the allocation set that refer to the source compute host UUID" is i thought what dansmith and i were talking about earlier,
20:22:25 mriedem which is similar to what my patch is checkingfor
20:22:43 efried sdague Yeah, now that you're saying it, I admit it feels a tad weird. But the point is that nova.utils.get_endpoint_data needs to be able to use that param to find the appropriate conf to load, as well as to find the service_type if it's not specified in the conf.
20:22:48 dansmith mriedem: well, I was assuming we could do it on the destination host
20:23:03 dansmith mriedem: but it doesn't really matter, so yes it's pretty much what we were saying
20:23:05 mriedem ok, i wasn't - i was thinking this was purely source host
20:23:11 sdague efried: yeh, it would be nice in the future if we could just specify "image" as well
20:23:12 dansmith well, you're just smarter than us
20:23:26 mriedem heh
20:23:52 mriedem i wouldn't go that far
20:23:55 jaypipes I would
20:24:00 efried sdague You can specify it in the conf: [glance] service_type = image
20:24:01 jaypipes in any case, I'm on it.
20:24:02 dansmith hey
20:24:34 efried sdague I think you're saying you want to specify the service type directly to nova.utils.get_endpoint_data
20:25:04 mriedem dansmith: was there more to that hey or just that your feelings were hurt?
20:25:27 efried sdague That would get confusing if the operator did in fact specify [glance] service_type = <whatever>
20:25:27 mriedem dansmith: is this similar to what you were thinking? https://review.openstack.org/#/c/488187/1/nova/scheduler/client/report.py@1085
20:25:29 dansmith mriedem: like, it's okay for me to say you're smarter than me, but not okay for jaypipes to say it
20:25:35 mriedem oh i get it
20:26:00 jaypipes everyone's smarter than me
20:26:02 mriedem feel free to compliment me on my ability to dig up useless pop trivia
20:26:08 mriedem but not my smarts in general
20:26:23 mriedem laura had to explain her work schedule to me for this weekend at least 4 times
20:26:34 dansmith heh
20:27:16 sdague efried: ah
20:27:29 sdague efried: I didn't realize people were allowed to override these
20:27:40 sdague efried: what's the use case there?
20:27:51 dansmith mriedem: yes, that's similar to what I was thinking
20:27:54 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/488034
20:28:09 sdague efried: anyway, on this patch, I think it looks overall good, I want to see a devstack run with api_servers not set to see it working
20:28:23 sdague after which I'll +2
20:28:31 sdague and I'll leave the rest of my questions for mordred
20:28:36 sdague and you at later dates
20:28:42 efried sdague Well, the overall use case is to consolidate/centralize/consistentify (look it up) the way we get clients.
20:29:09 efried sdague So for glance it might be a no-brainer that the service type should always be 'image'.
20:29:13 melwitt mriedem: what type of things will be allowed after today feature freeze? quota cleanups (like test coverage, removing unused stuff, changing the name of recheck_quota config option) or just bug fixes?
20:29:30 efried sdague But we want to be able to do it more or less the same way for e.g. cinder, which (egads) is nowhere near as simple.
20:30:15 sdague efried: yeh, the cinder edge case definitely is a thing.
20:30:50 efried sdague If you want a leetle preview of what that *might* look like: https://review.openstack.org/#/c/487621/1/nova/volume/cinder.py
20:31:02 mriedem melwitt: test coverage is obviously ok, and removing dead code
20:31:27 melwitt k
20:32:14 mriedem jaypipes: let me know before you push anything since i'd like to see a run with https://review.openstack.org/#/c/488187/
20:32:43 mriedem sdague: i think the list_cells thing will have to be a next week thing
20:32:48 mriedem brain is fried on placement stuff today
20:33:05 openstackgerrit OpenStack Proposal Bot proposed openstack/python-novaclient master: Updated from global requirements https://review.openstack.org/488125
20:33:28 sdague mriedem: that's fine, as long as we can still move it in
20:39:49 jaypipes mriedem: will do.
20:40:28 mriedem should have results in ~15 minutes for the live migration job
20:50:50 mriedem sdague: looks like https://review.openstack.org/#/c/487246/ broke the powervm in tree CI
20:50:55 mriedem efried: thorst: ^
20:51:03 mriedem i'm seeing that here http://184.172.12.213/87/488187/1/check/nova-in-tree-pvm/9c61778/logs/
20:51:17 mriedem openstack --os-cloud devstack-admin --os-region RegionOne compute service list --host powervm-ci-powervm-devstacked-28324 --service nova-compute -c ID -f value
20:51:19 efried mriedem looking
20:52:38 mriedem http://logs.openstack.org/46/487246/2/check/gate-tempest-dsvm-ironic-ipa-wholedisk-bios-agent_ipmitool-tinyipa-ubuntu-xenial-nv/bec38d6/logs/devstacklog.txt.gz#_2017-07-26_11_55_57_117
20:52:38 mriedem shit and it killed ironic
20:52:58 sdague mriedem: ah... gah
20:53:37 sdague right, all the compute for multiple hosts drivers
20:54:13 sdague mriedem: ok, hitting revert
20:54:48 mriedem ack
20:54:56 mriedem the one time i actually look at in-tree powervm CI results :)
20:54:59 sdague heh
20:55:13 sdague you get credit for finding it first
20:55:16 mriedem yay
20:55:21 mriedem i have notified the ironicers
20:55:33 sdague well the revert is submitted and approved
20:55:49 mriedem yeah i see it
20:56:17 sdague so... actually, why isn't the host set that way on powervm and ironic?
20:56:32 openstackgerrit Ed Leafe proposed openstack/nova master: Handle hash ring rebalancing in ironic flavor migration https://review.openstack.org/487954
20:56:48 sdague efried: you have a powervm setup somewhere that you can query?
20:57:01 efried esberglu needs to be involved here.
20:59:17 edleafe dansmith: ^^ incorporated rloo's suggestions
20:59:47 efried That powervm failure *might* be unrelated. We shouldn't be trying to connect to localhost.
21:00:01 efried sdague Did that change *when* the compute service gets started?
21:00:02 sdague mriedem: I'm actually not sure why hostname wouldn't match in the db
21:00:15 sdague efried: ??
21:00:23 mriedem efried: no
21:00:27 efried sdague Yeah, I wouldn't have thought so.
21:00:29 mriedem efried: it's polling for the compute node to show up
21:00:31 mriedem by the hostname
21:00:35 efried So the net is, we're looking into it.
21:01:00 sdague efried: I'm ok with a revert atm because it broke ironic, and we had enough breaks on them this week
21:01:10 sdague but I am curious why those don't seem to line up
21:01:55 thorst I think the main thing for powervm is it shouldn't be taking that long to start up...so that's what we're looking into :-/
21:03:02 mriedem oh right i forgot it takes 10 minutes for the powervm node to register
21:03:04 mriedem in init_host
21:03:46 tonyb mikal, sdague, melwitt: I don't knwo if this email was wider distrubuted but you know how we moved last_bytes recently .. it seems it was used by nova-lxd
21:04:15 melwitt I think I saw that email
21:04:17 sdague tonyb: they are out of tree, kind of don't care
21:04:31 tonyb mikal, sdague, melwitt: having the (out of tree) nova-lxd driver call into the libvirt code isn't cool :( so shoudl I revert it?
21:04:42 tonyb sdague: Well that was my initial response
21:04:53 edmondsw mriedem I started a change to get the powervm driver up faster but put it aside when we closed things down for pike
21:05:04 tonyb sdague: especially as when we get to queens we move it again
21:05:09 sdague tonyb: no, show up and interact in the community if you are using internal functions in the rest of the tree
21:05:10 melwitt tonyb: didn't they say they're already copy-pasting it somewhere?

Earlier   Later