Earlier  
Posted Nick Remark
#openstack-nova - 2017-12-21
17:24:42 openstackgerrit Matt Riedemann proposed openstack/nova master: Add support for getting volume details with a specified microversion https://review.openstack.org/529656
17:24:43 mriedem ildikov: part 1 ^
17:25:24 openstackgerrit Matt Riedemann proposed openstack/nova master: Add support for getting volume details with a specified microversion https://review.openstack.org/529656
17:57:39 openstackgerrit Matt Riedemann proposed openstack/nova master: Add support for getting volume details with a specified microversion https://review.openstack.org/529656
18:07:05 kashyap A no-brainer, already has +2: https://review.openstack.org/#/c/527691/ ("conf: libvirt: Cleanup CPU modelling related options")
18:08:56 openstackgerrit Merged openstack/nova master: XenAPI: create vGPU for instance https://review.openstack.org/516899
18:21:59 mriedem kashyap: no-brainer huh
18:22:02 mriedem question inline
18:24:34 openstackgerrit Matt Riedemann proposed openstack/nova master: conf: libvirt: Cleanup CPU modelling related options https://review.openstack.org/527691
18:27:32 mriedem jaypipes: can i interest you in some pure uncut alternate hosts https://review.openstack.org/#/c/511358 ?
18:28:14 jaypipes mriedem: sure thing.
18:28:53 jaypipes mriedem: currently have electrician's at my house running new conduit and installing a new dishwasher that went out earlier today. fun! on the day we're doing xmas dinner in the evening. awesome timing, as always.
18:29:55 mriedem make a centerpiece of leftover conduit to lighten the mood
18:30:20 mriedem or something else that's crafty from "at home with amy sedaris"
18:39:34 jaypipes mriedem: :)
18:40:18 mriedem btw, i recommend that you recommend that show to julie
18:41:31 jaypipes mriedem: I'm pretty sure she would already know about it. she loves anything sedaris. amy or david.
18:42:45 openstackgerrit Matt Riedemann proposed openstack/nova master: Add retry_on_deadlock decorator to action_event_start https://review.openstack.org/529672
18:42:47 mriedem then we are kindred spirits
18:52:09 openstackgerrit Matt Riedemann proposed openstack/nova master: libvirt: don't log snapshot success unless it actually happens https://review.openstack.org/529674
19:02:07 jaypipes mriedem: questions for you in that alternate hosts patch
19:09:39 oomichi mriedem: nice guide by https://review.openstack.org/#/c/529618/ just some comments
19:09:46 edleafe jaypipes: answering...
19:10:17 mriedem edleafe: on it already
19:10:20 mriedem but we can compare notes
19:10:30 oomichi mriedem: btw is it difficult to get bp approval of https://blueprints.launchpad.net/nova/+spec/vmware-boot-uefi ? the corresponding code seems ready
19:11:53 edleafe jaypipes: answered. I didn't have a good answer to https://review.openstack.org/#/c/511358/47/nova/compute/manager.py
19:12:01 edleafe maybe mriedem will
19:12:35 mriedem jaypipes: replied
19:13:03 mriedem oomichi: no one ever brought that up for queens,
19:13:13 mriedem in the 2-3 months they could have brought it up
19:13:46 oomichi mriedem: ok, let's skip it
19:14:17 mriedem given how trivial this is we could possibly make an exception
19:14:36 mriedem i just don't generally like to make exceptions because then you do it for one blueprint and everyone else expects it
19:16:57 melwitt there's a pretty simple libvirt driver refactor needing a +W that's en route to native luks encryption if anyone can review https://review.openstack.org/#/c/460243
19:17:01 jaypipes mriedem: k, both bottom patches +Wd
19:17:07 mriedem oomichi: replied
19:17:09 mriedem jaypipes: danka
19:17:16 jaypipes mriedem: bitte
19:18:57 edleafe jaypipes: thx. Guess we'll wait til Jan for the final patch
19:19:07 edleafe (unless you're up for it now!)
19:19:16 mriedem i haven't gone through the final patch yet
19:19:21 jaypipes edleafe: the one that needs a rebase?
19:19:23 mriedem so yeah figured january at this rate
19:19:25 mriedem plus that
19:19:26 mriedem :)
19:19:40 jaypipes mriedem: I'm reading your tc IRC log...
19:20:05 mriedem edleafe: would be cool if you could find an existing functional test for resize + reschedule that we could do the same caching scheduler extension test like i added this morning
19:20:09 mriedem jaypipes: you like that?
19:20:17 mriedem better get comfortable
19:20:27 edleafe mriedem: I'll look
19:20:31 jaypipes mriedem: it's "interesting" so far.
19:20:35 melwitt I read it yesterday
19:20:44 mriedem which tantrum are we talking about?
19:20:48 mriedem several days ago, or yesterday?
19:21:00 jaypipes mriedem: I mean, I already knew everyone hated nova (cores), but ..
19:21:04 jaypipes mriedem: yesterday
19:21:22 mriedem turns out they specifically hated john for one specific thing brought up years ago
19:21:28 melwitt yeah, it was ... illuminating
19:21:29 mriedem but that now includes me and everyone else
19:22:30 edleafe you're all the same
19:24:29 mriedem especially Vek
19:24:36 mriedem he's offendor #1
19:24:48 mriedem *offender
19:25:33 openstackgerrit Ed Leafe proposed openstack/nova master: Don't try to delete build request during a reschedule https://review.openstack.org/528835
19:25:33 openstackgerrit Ed Leafe proposed openstack/nova master: Make conductor pass and use host_lists https://review.openstack.org/511358
19:25:34 openstackgerrit Ed Leafe proposed openstack/nova master: Change compute RPC to use alternates for resize https://review.openstack.org/526436
19:25:52 edleafe mriedem: jaypipes: ^^ the rebase got 'em all
19:27:38 mriedem oomichi: i think "If you need help debugging" is the correct english
19:27:56 mriedem otherwise "If you need help with debugging"?
19:28:21 mriedem granted, i think most people who have english has a second language are probably more knowledgeable of the actual grammar rules :)
19:28:22 oomichi mriedem: "If you need help with debugging" is more easy for me
19:28:56 jroll another option is "if you need help to debug"
19:28:58 mriedem oomichi: 私はそれを変更する
19:29:00 jroll I like with
19:29:15 oomichi mriedem: ありがとう
19:29:43 mriedem oomichi: as for the "API extension" part,
19:29:47 mriedem i know like 'resource'
19:29:57 mriedem but not sure what to use beside extension. handler? controller? just API?
19:30:03 mriedem "route"?
19:35:07 melwitt mriedem: would it not be a REST API "resource"? that's what ppl told me to call it when I added /usages to placement API for example
19:35:22 oomichi mriedem: I think API is better in them. handler, controller and route are just implementation side
19:36:09 mriedem melwitt: but there are several API extensions under nova/api/openstack/compute/ which work on the same resource
19:36:11 mriedem like servers
19:36:25 mriedem consider the user_data, block_device_mapping_v2, etc extensions
19:36:26 melwitt ah, right
19:36:33 mriedem we have a similar modeling in our api samples directories
19:36:37 mriedem which is why i'm trying to show it's a 1:1
19:36:45 melwitt yeah. I was thinking of the os-blah ones that are separate
19:37:16 oomichi API becomes non-extensible, API means a single API, and we don't need to have separated tests for each extension
19:37:46 melwitt there aren't any separate directories under doc/api_samples/servers/ fwiw. just microversion directories
19:38:38 melwitt it's nice to have them separated for organizing and finding them though, IMHO
19:39:35 mriedem oomichi: then what do we call this? https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/user_data.py
19:39:43 mriedem it's an extension of the servers api
19:40:04 mriedem eventually, one day, these should all be collapsed and removed, which sdague started and gmann was working on
19:40:11 oomichi mriedem: hehe, that is a good sample
19:40:11 mriedem but i'm not sure what to call those except 'extensions'
19:40:53 oomichi mriedem: IIUC alex_xu wants to merge these code into main servers.py with json-schema
19:41:03 oomichi to remove these extension code
19:41:31 mriedem yeah i know

Earlier   Later