| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-03-15 | |||
| 11:20:36 | kashyap | The re-proposed SEV spec needs some further re-design (to take into account a blocker raised by DanPB): https://review.openstack.org/#/c/641994 | |
| 11:35:47 | stephenfin | mriedem: RE: https://bugs.launchpad.net/nova/+bug/1819794, I assume there's still an open to figure out why https://bugs.launchpad.net/nova/+bug/1819794/comments/2 is happening? | |
| 11:35:47 | openstack | Launchpad bug 1819794 in OpenStack Compute (nova) "nova-next job fail on Ubuntu Bionic" [Medium,Confirmed] | |
| 11:36:02 | mriedem | stephenfin: correct, it's not fixed | |
| 11:36:36 | stephenfin | mriedem: Okidok. Won't get to that today but I'll try take a look next week | |
| 11:44:35 | efried | kashyap: ack, thanks for the info. dansmith, does the dev stage of that project affect your opinion on landing the SEV work? | |
| 11:45:50 | efried | are you thinking we should perhaps call it something more generic, so that when Intel's answer arrives on the scene, we can implement it under the covers without changing the UI at all? | |
| 11:45:51 | kashyap | stephenfin: I'll look at that Bionic thingie; there are two things there (VMX thing and the misconfig of TLS certs) | |
| 11:46:08 | stephenfin | kashyap: It's all yours | |
| 11:46:27 | kashyap | stephenfin: Nod, first clearing out existing queue of stuff | |
| 11:47:03 | kashyap | efried: On the "calling it more generic", that's what I wanted to plant a flag about -- for us (Nova) to consider _if_ we can work out a generic mechanism | |
| 11:48:51 | kashyap | efried: From a quick chat with DanPB yesterday, he said Intel "MKTME" takes quite a different approach to AMD's SEV -- and what we're going to get in common in the end is up in the air. | |
| 11:49:19 | efried | kashyap: Well, yeah, I would think the outward-facing bits, like the compute capability trait?, would be called <generic>, and then under the covers we | |
| 11:49:20 | efried | if <generic>: | |
| 11:49:20 | efried | if AMD: | |
| 11:49:20 | efried | turn on SEV | |
| 11:49:20 | efried | elif Intel: | |
| 11:49:20 | efried | turn on MKTME | |
| 11:49:24 | efried | oh | |
| 11:49:28 | efried | well then | |
| 11:52:47 | kashyap | efried: On the outward-facing bits like the capability trait (although I don't know an awful lot about it) -- yes, it is worth at least calling out in the spec | |
| 11:53:37 | kashyap | ... that shows we've considered Intel's equivalent, with whatever limited info we have now. | |
| 11:53:56 | kashyap | efried: Might want to add your above pseudo-code comment in the spec | |
| 11:54:15 | efried | kashyap: I suppose I'll have to finally *read* the spec :P | |
| 11:54:59 | kashyap | efried: Haha. I'll admit, I was not paying attention to it at all (as my plate is already overflowing with stuff). | |
| 11:55:16 | kashyap | efried: I slowly got into it, as I was pinged about handling machine types, and then I noticed a few things | |
| 11:56:02 | cdent | wonders how kashyap is managing to have just one plate | |
| 11:56:08 | cdent | I will study | |
| 11:56:12 | efried | kashyap: I'm very new to "caring about libvirt at all", and it seemed to be a fairly simple followon to... some other spec I can't remember where we did a capability trait thing. | |
| 11:56:16 | kashyap | And then I saw things (like adding the wrapper around libvirt's getDomainCapabilities() API) could be split out -- as it can be used for other libvirt driver work | |
| 11:56:54 | kashyap | cdent: Hehe, I split my time b/n Nova (Gerrit-based patch workflow) and low-level virt (mailing-list based patch workflow) | |
| 11:57:11 | cdent | sounds very much like two plates | |
| 11:57:41 | kashyap | Yeah, a bit brain-warping. The joy of applying 40 patches from an e-mail thread :-) | |
| 11:57:48 | efried | but yeah, with the plate full thing, stuff involving the bowels of libvirt tends to be the first to slide off the edge. | |
| 11:57:56 | kashyap | But ... if you're using tools like `mutt`, et al. That makes it blazing fast, though | |
| 11:58:54 | kashyap | efried: Can understand on the "caring about libvirt" thing. The "being simple to follow" depends on what one is looking at, though ;-) | |
| 11:59:34 | efried | kashyap: Well, yes, simple from a "how we used the placement-isms" perspective, mainly because I've been right in the middle of that business for a whiile. | |
| 12:01:13 | kashyap | Ah, gotcha; in that sense. | |
| 12:02:18 | openstackgerrit | Matt Riedemann proposed openstack/nova master: docs: cleanup driver parity scope section https://review.openstack.org/643566 | |
| 12:02:53 | kashyap | efried: And thanks for reviewing the cache mode change series. | |
| 12:03:18 | efried | kashyap: Sure thing (speaking of bowels of libvirt) | |
| 12:03:38 | kashyap | :-) | |
| 12:04:18 | kashyap | efried: Warning: That SEV spec has _tons_ of hypervisor-related concepts. So expect to sink some 2 hours or more, if you're reading with full concentration | |
| 12:04:37 | efried | this is probably why I never finished it the first time around. | |
| 12:04:48 | efried | I was like, "whoah, this stuff is over my head; I hope kashyap reviews it." | |
| 12:04:51 | kashyap | (And as we speak, there is potentially one more thing to be fixed in libvirt/QEMU; libvirt folks are testing) | |
| 12:05:25 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Remove resize caveat from conductor docs https://review.openstack.org/643567 | |
| 12:05:44 | kashyap | efried: I've commented on parts of it; for now you can ignore and tackle other high-prio stuff. | |
| 12:06:00 | efried | thanks | |
| 12:06:01 | kashyap | I still need to review all the firmware / OVMF and other memory requirements stuff. | |
| 12:06:07 | kashyap | Will get to it next week | |
| 12:09:29 | stephenfin | mriedem: wrt all things docs, there's a nice albeit lengthy of all things metadata here that could benefit from your attention https://review.openstack.org/#/c/640730/ | |
| 12:09:53 | mriedem | christ almighty | |
| 12:10:17 | stephenfin | blame efried for setting me down that path | |
| 12:10:24 | stephenfin | (PS1 comments) | |
| 12:11:10 | mriedem | i don't see efried commenting in PS1 | |
| 12:11:18 | mriedem | i also see dansmith did some review on this... | |
| 12:12:13 | stephenfin | I must have changed the Change-ID at some point (initial version simply added use of :oslo.config:option: to one of the docs) | |
| 12:13:23 | efried | Yeah, I remember you saying this was interesting to me, and glancing at it, and not fully understanding why, and balking at the size of it, and not getting further into it where I might have been able to answer that question. | |
| 12:18:24 | mriedem | we could benefit from some docs on the object version registry, nova object serializer, how objects are registered into that, how backporting of versioned objects works, conductors role in all that stuff, etc | |
| 12:25:09 | kashyap | stephenfin: Heh, on your docs patch, very dansmith-esque rationale: "Dropped a bunch of random comments in here, surely some of them addd up to a -1" :D | |
| 12:34:33 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Trivial typo fix for REST API in policy enforcement docs https://review.openstack.org/643569 | |
| 12:38:23 | mdbooth | dansmith: You in, yet? | |
| 12:38:45 | kashyap | He should be, it is already 05:40 AM. Too late | |
| 12:38:59 | mdbooth | dansmith: I have confirmed btw that my monkey_patch patch fixes non-wsgi, but not wsgi, and crucially I now understand why | |
| 12:40:02 | mdbooth | It's a good patch, but incomplete. I'm just working on a follow up which I hope should fix everything and bring all our monkey patching hacks into 1 place. I'm happy to keep them separate or merge. Discuss when you get in? | |
| 12:40:25 | mdbooth | kashyap: Heh, for anybody else I wouldn't have bothered to ping at this time ;) | |
| 12:40:36 | kashyap | mdbooth: I know :-) Sorry for trolling | |
| 12:41:33 | mriedem | good god this doc needs updating https://docs.openstack.org/nova/latest/reference/scheduler-evolution.html | |
| 12:41:58 | kashyap | Does anyone here know if Ubuntu maintains Git repo for their Bionic QEMU packages? | |
| 12:42:57 | kashyap | I ask because of this: it seems like a very Ubuntu might've messed something: https://bugs.launchpad.net/nova/+bug/1819794 | |
| 12:42:57 | openstack | Launchpad bug 1819794 in OpenStack Compute (nova) "nova-next job fail on Ubuntu Bionic" [Medium,Confirmed] | |
| 12:42:57 | edleafe | mriedem: updating or deleting? | |
| 12:43:28 | mriedem | edleafe: some of the stuff in there still applies | |
| 12:43:50 | mriedem | but just stuff like "The recent NUMA features" that was written 3 years ago isn't so recent anymore | |
| 12:44:52 | edleafe | mriedem: it just seems that the bits that are still relevant don't merit a whole page in the docs. It's also a page that needs to be updated frequently | |
| 13:13:58 | openstackgerrit | Merged openstack/nova master: Avoid crashing while getting libvirt capabilities with unknown arch names https://review.openstack.org/643458 | |
| 13:24:03 | openstackgerrit | Matthew Booth proposed openstack/nova master: Fix SSL infinite recursion https://review.openstack.org/626952 | |
| 13:25:11 | openstackgerrit | Matthew Booth proposed openstack/nova master: WIP: Assert that we're monkey patching before importing https://review.openstack.org/643579 | |
| 13:25:24 | efried | mordred: dtantsur asked the question about openstacksdk-in-nova via https://review.openstack.org/#/c/642899/ -- which had to come up again sooner or later. When you have a minute, would you mind summarizing what would be involved in plumbing nova to use it? | |
| 13:26:29 | mordred | yes. happy to | |
| 13:26:33 | mordred | want me to do it on the review? | |
| 13:26:43 | openstackgerrit | Matthew Booth proposed openstack/nova master: DNM: What if we just monkey patched at the top level? https://review.openstack.org/643581 | |
| 13:33:49 | mordred | efried, dtantsur: Also - is this a thing you're wanting to squeeze in to stein? or for train? | |
| 13:34:14 | dtantsur | I'd expect Train to avoid surprises | |
| 13:34:35 | mriedem | edleafe: i just reported a bug so i don't lose track of the issues since i don't have time to work on it - those could all be worked as separate changes by interested contributors https://bugs.launchpad.net/nova/+bug/1820283 | |
| 13:34:35 | openstack | Launchpad bug 1820283 in OpenStack Compute (nova) "Scheduler Evolution in nova - the doc needs updating" [Medium,Confirmed] | |
| 13:35:04 | efried | mordred, dtantsur: Oh, yeah, Train fo sho. This first patch only swaps out one API; the work to hit all of them will be fairly extensive. And possibly warrants a blueprint as well. | |
| 13:35:36 | dtantsur | Which reminds me, I need to implement Baremetal Volume API in openstacksdk.. | |
| 13:35:37 | efried | mordred: Here probably better so I can ask questions (like, "whoah, you're assuming I know way more than I actually do") | |
| 13:35:58 | edleafe | mriedem: thanks for recording that. That page needs either a wholesale rewrite or a proper burial | |
| 13:40:34 | mordred | efried: well crap - I just responded to the patch :) | |
| 13:40:59 | mordred | efried: so maybe read that real quick and we can pick it up here | |
| 13:52:12 | efried | mordred: reading now, thanks. | |
| 13:55:53 | efried | mordred: "translating from service name to service type", like https://github.com/openstack/nova/blob/master/nova/utils.py#L1197-L1202 ? | |
| 13:57:29 | mordred | efried: yes. | |
| 13:57:40 | efried | so - already done \o/ | |
| 13:57:42 | efried | more or less | |
| 13:57:53 | mordred | efried: so - basically what we need is a loop that does what that's doing for all of the service types | |
| 13:58:33 | mordred | efried: and then we need to extract the parameters because the ks_loading.load_auth_from_ ... methods don't make sense in this context | |