Wednesday, 2024-04-10

opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Use native DictOpt for disk_cachemode  https://review.opendev.org/c/openstack/nova/+/91539002:38
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Validate valid cache mode at config input layer  https://review.opendev.org/c/openstack/nova/+/91539102:47
*** srelf_ is now known as Continuity08:22
opendevreviewElod Illes proposed openstack/nova stable/2023.2: [ironic] Partition & use cache for list_instance*  https://review.opendev.org/c/openstack/nova/+/90615509:51
opendevreviewMerged openstack/nova stable/2024.1: Fix nova-manage image_property show unexpected keyword  https://review.opendev.org/c/openstack/nova/+/91467111:03
*** blarnath is now known as d34dh0r5312:28
opendevreviewMerged openstack/nova stable/zed: Remove outdated comment about allocation ratios  https://review.opendev.org/c/openstack/nova/+/90869212:38
*** mklejn_ is now known as mklejn12:48
bauzasfwiesel: tkajinam: hey, which one of you both would want to start to discuss about your topics ?12:52
bauzasExtending memory encryption support or Nova Metadata Optimization ?12:53
fwieselbauzas: No strong preference. It would just be good to be finished with the metadata optimization before the neutron cross project call.12:57
tkajinamthe other 3 topis are mine it seems so I'm fine with metadata discussion going first12:57
bauzasfwiesel: tkajinam: cool, we'll start with the metadata, thanks12:58
opendevreviewMerged openstack/nova stable/2023.1: pwr mgmt: make API into a per-driver object  https://review.opendev.org/c/openstack/nova/+/91322513:50
opendevreviewMerged openstack/nova stable/2023.2: Fix nova-manage image_property show unexpected keyword  https://review.opendev.org/c/openstack/nova/+/91476514:11
zigoI still have this bug open, unaddress since 2021: https://bugs.debian.org/98224114:33
zigoCan nova use something else than genisoimage? If not, it'd be a good idea to make it support xorriso ...14:33
tkajinamzigo, ROD switched to xorriso. probably you can follow the same patch. There is a patch to update the default but has been stall. if other distros follow that switch then we can move the defualt switch forward14:34
zigotkajinam: Just switching the config option is enough?14:34
*** gouthamr_ is now known as gouthamr14:35
clarkbzigo: if that is for config drive building then I think nova can also make a fat32 instead of an iso9660 image14:36
zigoclarkb: Well, grep -r genisoimage points to config drive building indeed.14:53
zigoI'd prefer if I could just switch to xorriso easily... :/14:54
zigotkajinam: Do you have the patch handy?14:54
tkajinamzigo, I'm in ptg sessions so will update you sometime later14:54
zigoThanks.14:55
tkajinambauzas, I'll take some break during cross project discussion with neutron so please ping me when we resume nova discussions15:02
bauzas++15:02
tkajinamI'll try to summarize the discussion during that time, too. sorry I was mostly listening but there were some good points raised during the time15:02
opendevreviewMerged openstack/nova stable/2023.1: Reproducer test for live migration with power management  https://review.opendev.org/c/openstack/nova/+/91322615:03
kashyaptkajinam: Hi, a note on that AMD SEV-ES thing: when you get time, see my comments on the spec - https://review.opendev.org/c/openstack/nova-specs/+/90770215:14
kashyaptkajinam: The main question to think of is: SEV-ES processors are vulnerable to attestation attacks (see the links I provided).  SEV-SNP fixes those problems.15:15
kashyaptkajinam: So we should be careful in not investing too much effort on something that will soon be "replaced" / taken over by its next-gen tech (SEV-SNP)15:16
kashyapYou can write your thoughts on the spec.  I mentioned my concerns there too.15:16
tkajinamkashyap, thanks !15:17
kashyapIt looks like, we won't get to that topic today.  So let's keep the discussion on the Etherpad / spec :-)15:17
kashyaptkajinam: A year ago or so, I've spent some time testing SEV-SNP.  I need to refresh on it, though.  I'll do some more analysis on where are various low-level projects on it, and get back15:17
tkajinam(I'll post the same comments in etherpad and spec but) I agree that we should be careful about the investment. tbvh this work to support SEV-ES is more like a practice of extending the current implementation so that we can quickly work on SEV-SNP15:18
tkajinamonce the whole implementations are merged in upstream15:19
kashyapYeah, I see your point, but we shouldn't go deep into ES-specific impl details in Nova.15:22
tkajinamWe have already built PoC with patched kernel/qemu/libvirt/openstack to test SEV-SNP and the proposal is based on the learning in that work. the items specific to SEV-ES is the detection of ES capability and additional policy flag bit in libvirt and the other parts will be reused by SEV-SNP15:25
bauzastkajinam: Extending memory encryption support is planned at 1545UTC15:28
bauzasnow this is break time15:28
tkajinambauzas, ack. thanks15:29
dansmithmelwitt: the glance encryption thing will be in the cinder room, fyi15:30
melwittdansmith: ah ok, thanks15:30
dansmithmelwitt: nowish15:31
melwittoh, k15:31
dansmithif you can15:31
bauzastobias-urdin: oh shit, just saw you weren't available neither today or tomorrow :(17:15
bauzasany possibility tho to join us for only one hour ?17:15
bauzasI can arrange ourselves on a specific time for you17:15
bauzasstephenfin: are you okay discussing your topic tomorrow ?17:17
kashyapbauzas: I missed the 17:45 slot :( But I added my thoughts in the Etherpad and the spec17:18
bauzasnp17:19
kashyaptkajinam: Okay, we can talk more tomm.  So you've also been testing SNP based on upstream on-list patches?  I'm not sure who you mean by "we" :)17:21
tkajinamkashyap, sure17:22
tkajinamkashyap, I'm now part of a small team here in NTT DATA(my current employer), we have been using kernel/qemu/ovmf maintained in https://github.com/AMDESE (I think these contain patches proposed in lists) with libvirt and OpenStack additionally patched.17:24
kashyaptkajinam: Ah, I see.  Nice.  I work w/ some of the confidential computing folks at RHT.  Although, I'm not up2date on this area now, I poked some the SEV-SNP stuff w/ `sevtool`, etc back on Oct 2022.17:26
tkajinamWe've built a small PoC system which provides VM with its memory and disk encrypted and protected from hosts. Because we wanted some mechanism to detect any tampered bootchain elements(like kernel with any backdoor installed) we decided to use SEV-SNP which was most heading last year. I saw some works have done recently by Intel and am planning to try Intel TDX this year as well.17:27
kashyaps/back on/back in/17:27
kashyaptkajinam: I see, nice.  Do you also care about the whole attestation / measured boot thing?  (I'm guessing you do)17:28
tkajinamkashyap, yeah, I read their articles actually during my on-boarding process.17:28
kashyaptkajinam: Nice.  Shameless plug, I once wrote this too, but I'm a bit out-of-date now :D - https://lwn.net/Articles/838488/17:29
kashyapSome of the tools mentioned at the end got deprecated, or new tools came in.  And the "remote attestation" problem noted there is still a bit of a "beast" upstream, w/ various vendors coming up with their schemes.17:29
kashyaptkajinam: Consolidating on one approach to remote attestation seems to be a multi-year effort.17:30
tkajinamkashyap, yeah. we built a PoC which releases disk encryption key based on successful remote attestation, which uses attestation reports containing boot chain measurement.17:30
tkajinamkashyap, yeah but an interesting point is that hyperscalers already created their own services. that's why we are looking into it17:31
tkajinamone of our current main strategies, after we finished PoC, is to make sure we work closely with upstream and contribute anything we can. that's why I'm starting some work in nova and would probably spend some time in lower layers such as libvirt17:32
kashyaptkajinam: Huh, I see.  So you have your own remote-attestation mechanism too? :)17:32
kashyaptkajinam: Do you use tools like 'sev-snp-measure'?17:33
kashyaptkajinam: I see, fair enough.  Hyperscalars will come around once the dust settles upstream, I guess17:33
tkajinamI use sev-snp-measure or a few other tools for testing but mainly we built remote attestation api, which is created from the one maintained in https://github.com/confidential-containers/trustee17:35
kashyaptkajinam: Good to hear!  BTW, I also saw your mail on the upstream 'libvirt-devel' list about exposing SEV-ES via the new 'model' element17:35
tkajinamyeah. that's one of the "practices" I'm doing for the overall work17:35
tkajinamkashyap, In our PoC we inject a script into geust which reads attestation report and send it to that remote attestation api, and then remote attestation api returns disk encryption key only when it can verify the report.17:36
kashyapOkay, good to know that your aim is to work with the relevant upstreams.  As you know, there are many moving parts here: kernel, OVMF, QEMU, libvirt, and Nova.17:36
tkajinamyeah17:36
tkajinamhonestly speaking I'm not much familiar with the lower level things like kernel or even qemu, but am hoping that I can work on more control-plane layers like libvirt or nova because resource coordination is one of the topics for which I've been working for some time.17:37
kashyaptkajinam: Okay, cool.  One last thing before I go out: on your libvirt thing: I saw DanPB's response on using "maxESGuests" to detect number of SEV-ES availability.  I also saw your response; let's see what the other maintainers say there.17:39
tkajinamkashyap, thanks! I was wondering if I made something wrong which caused no response for some time but probably people are just busy17:40
kashyaptkajinam: I'm also not an expert on those; but I work w/ KVM/QEMU/libvirt devs on other areas, so I can ping the "right person" if nedeed on an upstream thread17:40
kashyaptkajinam: No, you didn't do anything wrong.  Dan Berrange seems to be away for a few days.  17:41
tkajinamgood to hear :-)17:41
kashyaptkajinam: I can ping him once he's back; I don't see him around.17:41
tkajinamkashyap, it'd be nice if I can have some conversations with Red Hat people working in this area, to discuss plans in both sides (if possible and interesting). I also find recent working about TDX in CentOS quite interesting and was willing to have some conversation about its status and future plan.17:42
kashyaptkajinam: I saw your v2; don't hesitate to send a "3rd ping" on the list after a few more days.  That's how it works on that list sometimes.17:42
tkajinamkashyap, ack. will do !17:42
kashyaptkajinam: Sure, you can join #virt on OFTC. 17:42
kashyaptkajinam: And the SEV measurement folks hang out on Matrix, #virtee: https://virtee.io/17:42
kashyapI need to step out now; back later :)17:43
tkajinamok. yeah I know VirTEE but haven't looked into its communication channel. will check it !17:43
tkajinamkashyap, thanks. I'm stepping away too now. Have a good day ahead :-)17:43
opendevreviewMark Goddard proposed openstack/nova master: Support creating servers with RBAC SGs  https://review.opendev.org/c/openstack/nova/+/81152118:23
tkajinamzigo, hmm. it seems the problem is a bit more tricky in debian and ubuntu. 20:52
tkajinamxorriso package in CentOS provides the simple mkisofs command. IIUC this is a wrapper internally calls 'xorriso -as mkisofs'20:53
tkajinambecause current nova doesn't allow adding additional options we need such single command replacing genisoimage. probably is the xorrisofs command the one ?20:56
tkajinamthe package in CentOS provides xorriso, too, it seems, so probably switching to it is the wise option20:58
tkajinamI thought I saw a patch to update the default but I could not find it for some reason.20:58

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!