-
Notifications
You must be signed in to change notification settings - Fork 90
refactor: use qemuimg2disk #217
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
Conversation
Signed-off-by: Mickaël Canévet <mickael.canevet@proton.me>
eefa088 to
a07ac56
Compare
jacobweinstock
left a comment
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.
Hey @mcanevet, thanks for this! Just one concern/suggestion.
| DEST_DISK: {{ index .Hardware.Disks 0 }} | ||
| IMG_URL: "http://$TINKERBELL_HOST_IP:7173/jammy-server-cloudimg-amd64.raw.gz" | ||
| COMPRESSED: true | ||
| IMG_URL: "https://cloud-images.ubuntu.com/daily/server/jammy/current/jammy-server-cloudimg-amd64.img" |
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.
This location causes my Workflow to timeout. Downloading it and putting it into the same place as the HookOS files works. Mind downloading it and updating this IMG_URL to the local nginx?
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.
It works fine for me:
kubectl get -n tinkerbell workflow playground-workflow --watch
NAME TEMPLATE STATE ACTION AGENT HARDWARE
playground-workflow ubuntu PENDING machine1
playground-workflow ubuntu PENDING stream ubuntu image 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING stream ubuntu image 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING stream ubuntu image 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING grow-partition 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING grow-partition 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING grow-partition 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING grow-partition 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING install openssl 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING install openssl 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING install openssl 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING create user 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING create user 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING create user 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING enable ssh 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING enable ssh 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING enable ssh 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING disable apparmor 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING disable apparmor 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING disable apparmor 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING write netplan 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING write netplan 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING write netplan 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING kexec into os 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu RUNNING kexec into os 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu POST kexec into os 08:00:27:9e:f5:3a machine1
playground-workflow ubuntu SUCCESS kexec into os 08:00:27:9e:f5:3a machine1
Maybe we could try with timeout greater than 600.
The whole point of this simplification is to get rid of the download job, so I can't see the point of adding it back (or maybe I misunderstood what you are suggesting?)
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.
Hey @mcanevet, the existing setup does more than just download the image. It converts it format from a .img to a compressed raw file. This does simplify things but it seems to be to be less reliable. I would prefer to optimize for working reliable for everyone. Also, downloading the .img file would still be simpler than the current way of downloading and converting but i agree, not simpler than what you have here. I'm open to push back or suggestions. Regardless, thanks for using the playground and opening this PR! Very much appreciated.
Description
Simplify vagrant stack by using
qemuimg2diskinstead of a job that download the image and converts it to compressed qemu image.Fixes: #
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have: