| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-09-29 | |||
| 16:09:41 | mriedem | melwitt: i wasn't planning on proposing a specific nova upgrades one no, i figured some of that will be covered in cells/placement sessions on what happened in pike and the focus for queens | |
| 16:09:46 | mriedem | feel free though | |
| 16:10:07 | openstackgerrit | John Garbutt proposed openstack/nova master: Re-use existing ComputeNode on ironic rebalance https://review.openstack.org/508555 | |
| 16:10:10 | superdan | so, | |
| 16:10:33 | superdan | since we don't get to prioritize these (right?) I'd hate to lose one of these important sessions for an upgrade one that we've hit many times before | |
| 16:10:40 | superdan | if we have space, it's always good to have one of those, | |
| 16:10:51 | superdan | but if the TC is picking, I don't want them to choose that over, say, the cells or placement one | |
| 16:11:03 | superdan | could we maybe indicate a preferred ordering somehow? comments? | |
| 16:11:13 | mriedem | comments are about all you get | |
| 16:11:26 | mriedem | NOVA PRIORITY: 5 | |
| 16:11:32 | johnthetubaguy | did you make the placement one sound cross project-ey? | |
| 16:11:50 | johnthetubaguy | that might be a good way to keep a good session | |
| 16:11:54 | mriedem | i didn't propose a placement one because of http://forumtopics.openstack.org/cfp/details/50 | |
| 16:12:23 | mriedem | ^ is both generic and too specific | |
| 16:12:47 | mriedem | what i think that is, is talking about how nested resource providers and custom resource classes will let you do all kinds of external scheduling things | |
| 16:12:49 | johnthetubaguy | yeah, it is. | |
| 16:12:55 | mriedem | which is not what i was going to propose | |
| 16:13:09 | mriedem | i guess i'll just propose my own | |
| 16:13:12 | johnthetubaguy | I would tempted to add a good one, and note its a duplicate? | |
| 16:13:16 | melwitt | okay. my thinking was if ppl are recently having trouble installing or upgrading nova, that was important and I wanted to gather action items on whether we need to improve docs, relnotes, nova-manage commands, etc | |
| 16:14:37 | mriedem | melwitt: bauwser has one for docs and relnotes specifically | |
| 16:14:52 | mriedem | i see your point | |
| 16:15:15 | mriedem | are people recently having trouble beyond ocata? | |
| 16:15:21 | mriedem | i know ocata was tough for some people | |
| 16:15:54 | melwitt | yeah, I saw that. docs and relnotes generic session without a target like install/upgrade I'm not sure what will come out of that | |
| 16:16:37 | mriedem | "the release notes don't have enough information!" | |
| 16:16:44 | mriedem | "the release notes have too much information" | |
| 16:16:48 | mriedem | that's what will come out of that | |
| 16:16:56 | superdan | yep | |
| 16:17:25 | superdan | and what will come of the upgrade one is much of the same we've heard before I think, which is why I care less about it than the other things | |
| 16:17:35 | melwitt | but I understand everyone's point. I really wish I knew if operators were suffering on newton/ocata/pike and what we could do to ease that. I don't remember discussing that span of releases in a session but I do remember a lot of ppl coming into our channel with issues | |
| 16:17:35 | superdan | if we have space for it, then I'm certainly happy to have it | |
| 16:18:39 | melwitt | we responded to the issues and improved our docs and nova-manage commands. and now it's our best assumption that everything is okay but I wasn't sure if it is since we haven't had anyone tell us. it's more like lack of complaint | |
| 16:19:14 | melwitt | just thinking aloud mostly | |
| 16:20:18 | melwitt | how can we tell if we have space for more proposals? we can't right? | |
| 16:20:33 | mriedem | melwitt: we can't | |
| 16:21:04 | mriedem | there is a fast forward upgrades session | |
| 16:21:14 | mriedem | so my guess would be a nova-specific upgrade session would be asking for FF upgrades | |
| 16:21:36 | mriedem | ttx: how many slots are there for forum topics? | |
| 16:21:51 | mriedem | s/topics/sessions/ | |
| 16:22:54 | mriedem | i would also love feedback on where we've sucked it up perf-wise, | |
| 16:22:58 | mriedem | but, | |
| 16:23:00 | mriedem | ... | |
| 16:23:48 | melwitt | yeah. this is weird that we can't control what we have sessions about and have to worry that some sessions would bump others out | |
| 16:24:27 | mriedem | and as a result we don't propose as many | |
| 16:24:37 | mriedem | meanwhile there are like 4+ overlapping sessions about HPC and NFV | |
| 16:25:37 | itlinux | hello all.. I have a docker image that I installed the clients on and I have the endpoints running on HTTPS.. when I do nova list on that box I get an error.. if I use my virtualbox with openstack installed I can query my remote openstack with the nova list just fine.. any tips? | |
| 16:25:42 | openstackgerrit | Dan Smith proposed openstack/nova master: Fix minor input items from previous patches https://review.openstack.org/506416 | |
| 16:25:49 | superdan | mriedem: so, in my fixing of your fields thing in ^ | |
| 16:26:06 | superdan | I found another place we were implicitly querying for a ton of extra stuff when all we want was metadata | |
| 16:26:32 | johnthetubaguy | fried_rice: leakypipes: superdan: thanks for your help with the ironic placement bug, fix up for review, not had chance to test it yet, something for next week: https://review.openstack.org/#/c/508555 | |
| 16:26:35 | superdan | "ton" being "four" instead of "one" | |
| 16:26:36 | superdan | you know, apply my normal exaggeration descaling filter | |
| 16:28:12 | superdan | johnthetubaguy: cool | |
| 16:29:33 | ttx | mriedem: not sure, maybe thingee or flaper87 know | |
| 16:30:50 | mriedem | johnthetubaguy: superdan: leakypipes: cdent: figleaf: fyi http://forumtopics.openstack.org/cfp/details/60 | |
| 16:31:33 | superdan | mriedem: you posted that on the cells one, did you mean to do it on a placement one? | |
| 16:31:53 | leakypipes | ack, will do johnthetubaguy | |
| 16:32:06 | mriedem | superdan: you mean this? https://review.openstack.org/#/c/506416/13/nova/compute/api.py@3755 | |
| 16:32:16 | mriedem | crap yes | |
| 16:32:20 | superdan | mriedem: yes that | |
| 16:33:03 | mriedem | superdan: have you seen https://review.openstack.org/#/c/508299/ | |
| 16:33:10 | superdan | mriedem: there's a test that failed if we don't pass something to that now that we're doing the fields calculation early, but it means we stop taking the obvious default | |
| 16:33:33 | superdan | mriedem: heh, okay, well, I need it for the change in that patch | |
| 16:33:39 | superdan | mriedem: so whichever one wins the race I guess | |
| 16:34:39 | mriedem | there is an issue with yours | |
| 16:34:56 | mriedem | maybe we should slide https://review.openstack.org/#/c/508299/ in underneath? | |
| 16:36:01 | superdan | ah, I didn't see that it called that | |
| 16:36:25 | superdan | let's just try to get yours in so I don't have to intertwine those two series | |
| 16:36:44 | superdan | still no jenkins run on that one.. is it worth rechecking now or no? | |
| 16:37:10 | mriedem | no idea | |
| 16:37:14 | mriedem | i don't see it queued up | |
| 16:37:20 | mriedem | i'm going to lunch | |
| 16:43:30 | openstackgerrit | Eric Fried proposed openstack/nova master: WIP: Use ksa adapter for cinder client https://review.openstack.org/508345 | |
| 16:50:51 | openstackgerrit | Eric Fried proposed openstack/nova master: WIP: Use ksa adapter for cinder client https://review.openstack.org/508345 | |
| 16:54:04 | cdent | mriedem: you aware of this interoperability tag thingie for nova? it wants your +1: https://review.openstack.org/#/c/506255/ | |
| 17:15:41 | cdent | leakypipes: if you’ve got a chance this (shared rp fix from alex) probably wants your eyes: https://review.openstack.org/#/c/480379/ | |
| 17:23:14 | leakypipes | cdent: ah, yes, thanks for the reminder | |
| 17:23:23 | cdent | ✔ | |
| 17:46:51 | pino | penick: mriedem: (and Jay Pipes, can't find his handle) a few days ago I asked about injecting dynamically generated SSH certificates into the host. You pointed me to vendordata, cloud-init (and the novajoin example). I've played with it and have some more questions/issues. Do you have a few minutes? | |
| 17:47:14 | leakypipes | pino: I'm leakypipes on Fridays :) | |
| 17:47:19 | pino | Specifically, I'm worried about the SSH host certificate. | |
| 17:47:36 | pino | leakypipes: :-) | |
| 17:48:18 | pino | So, the problem with the host certificate is that you need to pass the host public key to the Host CA signing service to generate the certificate, then inject it back. | |
| 17:49:02 | pino | But vendor data doesn't take any arguments, so you're forced to either generate the host keys off the instance, or you need to expose a service directly to the instance. | |
| 17:50:31 | pino | Both are problematic: exposing the signing service to the instance means the instance has to be able to authenticate itself to the service (chicken-and-egg problem). | |
| 17:50:34 | mriedem | interop tag?! | |
| 17:50:55 | pino | Is that comment for me? | |
| 17:51:00 | mriedem | no | |
| 17:51:02 | mriedem | sorry | |
| 17:53:33 | pino | Maybe an e-mail would be more effective... | |
| 17:53:50 | pino | I'll write it all up and send to the mailing list instead. | |
| 17:53:58 | mriedem | pino: to the openstack-dev mailing yeah, probably | |
| 18:02:05 | mriedem | leakypipes: the explanations for https://review.openstack.org/#/c/506093/ are in the commit message | |
| 18:02:13 | mriedem | the functional test fails without those changes to the fake virt driver | |
| 18:02:22 | leakypipes | mriedem: I still couldn't understand the explanation. | |
| 18:02:30 | leakypipes | mriedem: which is what I said in the comment../. | |
| 18:02:39 | mriedem | if you do live migration with block_migration=auto, | |
| 18:02:45 | mriedem | that passes block_migration=None, | |
| 18:02:55 | mriedem | which you can't set on MigrateData b/c it's not a nullable=True field | |