-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
osbuild: add support for qemu-secex #3764
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't feel qualified to comment on the osbuild part, though i looked over it and i did not find anything that looked wrong to me.
One question, how is the naming scheme of the patch files, since normally i would expect the numbers to show the order they need to be applied in and for them to unique? But here is see 0001
is used twice?
they are written to stdout using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before going further, should we think about how we'll tackle the prod case since it's very different from the local build case?
osbuild pr: osbuild/osbuild#1806 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Mostly LGTM.
src/0001-stages-add-stage-for-creating-dm-verity-partitions.patch
Outdated
Show resolved
Hide resolved
src/0001-stages-add-stage-for-creating-dm-verity-partitions.patch
Outdated
Show resolved
Hide resolved
src/0001-stages-add-stage-for-creating-dm-verity-partitions.patch
Outdated
Show resolved
Hide resolved
6b22007
to
e5ec67b
Compare
69827fc
to
432ab0c
Compare
@jschintag could you please check the scripts with official |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor comments but LGTM overall.
Nice work on this @nikita-dubrovskii. It's been a long time coming!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably worth a comment here at the top of this file about what this Butane config is for.
Would be nice to put the instructions in the commit message somewhere more visible. Maybe in https://coreos.github.io/coreos-assembler/devel/ ?
Not a blocker/can be a follow-up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spoke OOB with Nikita about this. In a follow-up, he will add logic that will actually start up a VM with that Butane config for the local dev case.
This template coul be used to create genprotimgvm locally. During build this VM is used to generete 'sdboot' image and 'zipl' it on coreos.qemu-secex.s390x.qcow2 image. Put this template, your id_rsa.pub and valid secex-hostkey into same directory and generate Ignition config: ``` butane --pretty --files-dir . genprotimg.bu -o genprotimg.ign ``` Than get rhcos.qemu-secex.s390x.qcow2 and customize it with generated above ignition config.
I have run it on the builder and i could build a secure execution test and run the associated kola tests successfully. |
Great, thx for testing! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Let's do it!
To be safe, I've created a :before-pr3764
tag in Quay.io from the current :latest
tag.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spoke OOB with Nikita about this. In a follow-up, he will add logic that will actually start up a VM with that Butane config for the local dev case.
Discussion also goes in: dustymabe/osbuild#22