Wednesday, 2024-07-31

opendevreviewMerged openstack/oslo.log master: Mock time.time_ns in test_rfc5424_isotime_format_no_microseconds for py3.13  https://review.opendev.org/c/openstack/oslo.log/+/92406311:32
opendevreviewMerged openstack/oslo.config master: Add option for generate shell completion script  https://review.opendev.org/c/openstack/oslo.config/+/90647811:54
dansmithtkajinam: thanks for your reviews so far.. anything else I can do to help move this along?13:54
dansmithhappy to try to drum up some non-oslo reviews if it would help13:54
dansmithI'm really hoping we can get this in this cycle and get the other projects rebased on it to avoid a release where backports would have to be made to the embedded versions13:55
dansmithI definitely recognize it's a very sudden/unplanned need to review a bunch of code13:56
tkajinamdansmith, I'm afraid I'm busy till Friday but will spend some time on these till early next week... you can probably ask dansmith or hberaud (and probably stephenfin if he has time) to review give their reviews, too14:00
dansmithtkajinam: damani2 ?14:02
dansmithI'm happy to review :D14:02
tkajinamyes. wrong completion, sorry14:02
opendevreviewTakashi Kajinami proposed openstack/oslo.utils master: Decouple reason from a check instance  https://review.opendev.org/c/openstack/oslo.utils/+/92540314:39
dansmithtkajinam: no need to revise, I just read it wrong because of the name,_ filtering above15:17
dansmithwith your permission to make it a dict, I'll fold that change into the base and get the series updated15:18
tkajinam+1 . I wonder if we want to use an exception instance directly, instead of string-fy-ing it so that we can add more attributes later.15:25
dansmithyeah, that would be better if that's okay15:27
opendevreviewTakashi Kajinami proposed openstack/oslo.utils master: Decouple reason from a check instance  https://review.opendev.org/c/openstack/oslo.utils/+/92540315:27
dansmithtkajinam: I assume you want me to fold your change into the parent patch (with Co-Authored-By) and not just insert it into the stack, right?15:30
dansmiths/fold/squash/15:30
tkajinamyeah that would make the review step easier because I can +215:31
dansmithack will do in a bit, thanks15:32
tkajinamthanks !15:33
tkajinamI'll add my +2 to the updated version and re-add +2 to other patches in the chain once a new versions is submitted. I'll leave the last GPT/MBR inspector to tomorrow because I have to understand the spec first.15:37
dansmiththanks15:39
dansmithI'm also going to collapse safety_checks and safety_check_names into a dict if that's okay, just to avoid them getting out of sync (and because your latest has a typo that requires that stuff to be fixed anyway)15:39
dansmithtkajinam: I'm working on this: https://opendev.org/openstack/os-test-images15:41
dansmithwhich will give you test images to run against if you want15:41
dansmithI also never heard an answer about including the utility in oslo.utils, which would also make it easier to run a tool against a test image from ^ from the command-line15:41
dansmithis that reasonable to be in oslo.utils?15:41
tkajinamdansmith, that's a good idea. alternatively we can create list of names from list of checks but I it's really redundant.15:42
tkajinamchecking it15:42
tkajinamdansmith, it may depends on its expected usage. If the tool is used only in functional/unit tests of oslo.utils then it can be in oslo.utils, but if you aim to use it in any functional tests in other projects (cinder, glance, nova) then probably it's better to keep it in a separate repo15:55
dansmithtkajinam: it would be more like useful for admins I think15:55
dansmithbut yeah, I can put it somewhere else15:55
opendevreviewDan Smith proposed openstack/oslo.utils master: Modularize image safety checks  https://review.opendev.org/c/openstack/oslo.utils/+/92437016:00
opendevreviewDan Smith proposed openstack/oslo.utils master: Reinstate VMDK safety check coverage  https://review.opendev.org/c/openstack/oslo.utils/+/92437116:00
opendevreviewDan Smith proposed openstack/oslo.utils master: Add region-complete signaling for inspectors  https://review.opendev.org/c/openstack/oslo.utils/+/92437216:00
opendevreviewDan Smith proposed openstack/oslo.utils master: Make VMDKInspector support non-sparse formats  https://review.opendev.org/c/openstack/oslo.utils/+/92451216:00
opendevreviewDan Smith proposed openstack/oslo.utils master: Support VMDK sparse with footer  https://review.opendev.org/c/openstack/oslo.utils/+/92452616:00
opendevreviewDan Smith proposed openstack/oslo.utils master: Refactor some things for oslo  https://review.opendev.org/c/openstack/oslo.utils/+/92476616:00
opendevreviewDan Smith proposed openstack/oslo.utils master: Fix qcow2 feature flag checks (for the future)  https://review.opendev.org/c/openstack/oslo.utils/+/92485916:00
opendevreviewDan Smith proposed openstack/oslo.utils master: Add GPT/MBR inspector  https://review.opendev.org/c/openstack/oslo.utils/+/92496316:00
tkajinamMy point is that I don't want the test data generator command (like os-test-image-generator) installed as part of oslo.utils, because of the current scope of oslo.utils which is basically the general core library used by multiple projects.16:00
tkajinamIf the tool is used within the tests of oslo.utils then it can stay in somewhere like tests/tools but if we want to make it more generally available then a separate location sounds better to me16:01
dansmithno, the generation is definitely not going to be in oslo, it's just the utility (for verifying images) that is in question16:04
dansmithand it's not something that would be used in tests, it would be used by admins (or devs) trying to reason about an image16:04
dansmithsince it's not safe to run qemu-img on untrusted images, there's no way for an admin to inspect an image they suspect may be bad and/or confirm what *openstack* will say about its safety,16:05
dansmithaside from like uploading it to glance, which would be crazy :)16:05
dansmithbut anyway, I'll put the tool somewhere, no worries16:05
tkajinamah, ok16:09
tkajinamdansmith, sorry I totally misunderstood the tool you were talking about. ok having a verification CLI in oslo.utils would be ok because it may be used in real use.16:12
dansmithoh okay16:12
tkajinamor probably we can implement a sub command in openstack CLI ? (though I don't know if that's acceptable for SDK people)16:12
dansmithI guess we could but it seems out of scope for openstackclient to me16:12
tkajinamok16:13
dansmithanyway, I can propose it and if it's not reasonable we can add it elsewhere.. it should be plenty portable since it just uses oslo.imageutils.format_inspector regardless of where it is16:13
tkajinamit seems that oslo.utils is required by openstackclient so having the tool in oslo.utils might be easier for people with only clients installed16:13
tkajinam+116:14
dansmithack, well, if it already uses oslo.utils then perhaps16:15
opendevreviewDan Smith proposed openstack/oslo.utils master: Add region-complete signaling for inspectors  https://review.opendev.org/c/openstack/oslo.utils/+/92437217:40
opendevreviewDan Smith proposed openstack/oslo.utils master: Make VMDKInspector support non-sparse formats  https://review.opendev.org/c/openstack/oslo.utils/+/92451217:40
opendevreviewDan Smith proposed openstack/oslo.utils master: Support VMDK sparse with footer  https://review.opendev.org/c/openstack/oslo.utils/+/92452617:40
opendevreviewDan Smith proposed openstack/oslo.utils master: Refactor some things for oslo  https://review.opendev.org/c/openstack/oslo.utils/+/92476617:40
opendevreviewDan Smith proposed openstack/oslo.utils master: Fix qcow2 feature flag checks (for the future)  https://review.opendev.org/c/openstack/oslo.utils/+/92485917:40
opendevreviewDan Smith proposed openstack/oslo.utils master: Add GPT/MBR inspector  https://review.opendev.org/c/openstack/oslo.utils/+/92496317:40

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