David Cassany Viladomat

Just verified in #1074 that increasing the timeout helps, but still fails time to time... Looks like VirtualBox is not that stable for EFI... Now I got a [failure](https://github.com/rancher-sandbox/cOS-toolkit/runs/4968588256?check_suite_focus=true) while...

> The suggested scenario sounds instead: "Can I upgrade from an old version X (latest master) to the one produced in the PR", which sounds more like an _"integration test"_...

Closing there is already a first iteration of the architecture documentation. Specific issues should be opened for missing details.

All right, the bare minimum `elemental build-iso` requires is a set of three images (or local folders or luet packages). See the manifest.yaml file below: ```yaml iso: uefi: - channel:live/grub2-efi-image...

> What is in `live/grub2-efi-image` and `live/grub2` that wouldn't be available in SLE Micro for Rancher ? thinking `live/grub2` contains the grub configuration files for the live boot and `live/grub2-efi-image`...

Some comments regarding the above discussion: * creating ISOs from the elemental-operator is an unrelated topic, an interesting feature though, but requires a proper design as this is not alight...

Done by rancher/elemental-cli#316 and some follow ups to adapt rancher/elemental. Opening a new card to ensure the code is also adapted in rancher/elemental-toolkit.

Just did a quick run of a teal build of `system/cos` including `shim` and `mokutil` packages and I can verify this is not enough to boot with secure boot enabled...

The SUSE way of doing it is by calling the `/usr/sbin/shim-install` helper script which is part of the shim package. However I doubt this is an option for our use...

> Now, Im not sure how the CD/DVD boots on EFI+secureboot... With some xorriso black magic... just run `man xorriso`, grab a cup of tea or coffee and start reading...