Direct Linux kernel/initrd boot
I was looking at using direct Linux kernel/initrd booting for a particular automation project, but I'm not sure how to use it. The docs talk about referencing files from an ISO domain, but those are deprecated (and I don't have one). Can the files be in a regular data domain? How would I specify which domain to look in? The docs also say the alternative is to specify a path "on the host", but I guess that requires the files to be copied to the same path on every host that could boot the VM? I guess I can instead make a one-off ISO and upload it to a data domain; it just would be easier to use direct boot. -- Chris Adams <cma@cmadams.net>
Hi Chris, Indeed, the ISO domains are deprecated, and you can use a data domain for uploading iso files (as you've mentioned). To do that, you need to use image-io for uploading images <https://www.ovirt.org/develop/release-management/features/storage/image-upload.html> Here's image-io documentation: http://ovirt.github.io/ovirt-imageio/overview.html. Then you can use the UI (admin portal) or REST API <http://ovirt.github.io/ovirt-engine-api-model/master/#services/image_transfer> for uploading the iso image to the relevant storage domain. *Regards,* *Shani Leviim* On Mon, Jul 26, 2021 at 8:56 PM Chris Adams <cma@cmadams.net> wrote:
I was looking at using direct Linux kernel/initrd booting for a particular automation project, but I'm not sure how to use it. The docs talk about referencing files from an ISO domain, but those are deprecated (and I don't have one). Can the files be in a regular data domain? How would I specify which domain to look in?
The docs also say the alternative is to specify a path "on the host", but I guess that requires the files to be copied to the same path on every host that could boot the VM?
I guess I can instead make a one-off ISO and upload it to a data domain; it just would be easier to use direct boot. -- Chris Adams <cma@cmadams.net> _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IDIDY6ZLZCRMVM...
On Tue, Jul 27, 2021 at 11:56 AM Shani Leviim <sleviim@redhat.com> wrote:
Hi Chris, Indeed, the ISO domains are deprecated, and you can use a data domain for uploading iso files (as you've mentioned). To do that, you need to use image-io for uploading images
Here's image-io documentation: http://ovirt.github.io/ovirt-imageio/overview.html.
Then you can use the UI (admin portal) or REST API for uploading the iso image to the relevant storage domain.
Shani, I think Chris asked specifically about booting from an image. See e.g.: https://bugzilla.redhat.com/show_bug.cgi?id=1122970#c34 Is that intended to be handled? It seems like we gave up on removing the ISO domain concept, perhaps also because of this missing feature - see last few comments of: https://bugzilla.redhat.com/show_bug.cgi?id=1543512 Adding Michal. Michal - IMO we should make up our minds and provide a clear view - either undeprecate the ISO domain - remove deprecation notices from everywhere - or provide concrete plans to fill the missing gaps. Best regards,
Regards, Shani Leviim
On Mon, Jul 26, 2021 at 8:56 PM Chris Adams <cma@cmadams.net> wrote:
I was looking at using direct Linux kernel/initrd booting for a particular automation project, but I'm not sure how to use it. The docs talk about referencing files from an ISO domain, but those are deprecated (and I don't have one). Can the files be in a regular data domain? How would I specify which domain to look in?
The docs also say the alternative is to specify a path "on the host", but I guess that requires the files to be copied to the same path on every host that could boot the VM?
I guess I can instead make a one-off ISO and upload it to a data domain; it just would be easier to use direct boot. -- Chris Adams <cma@cmadams.net> _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IDIDY6ZLZCRMVM...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/L74BPUBL2IYMT5...
-- Didi
On Tue, Jul 27, 2021 at 12:10 PM Yedidyah Bar David <didi@redhat.com> wrote:
On Tue, Jul 27, 2021 at 11:56 AM Shani Leviim <sleviim@redhat.com> wrote:
Hi Chris, Indeed, the ISO domains are deprecated, and you can use a data domain for uploading iso files (as you've mentioned). To do that, you need to use image-io for uploading images
Here's image-io documentation: http://ovirt.github.io/ovirt-imageio/overview.html.
Then you can use the UI (admin portal) or REST API for uploading the iso image to the relevant storage domain.
Shani, I think Chris asked specifically about booting from an image. See e.g.:
https://bugzilla.redhat.com/show_bug.cgi?id=1122970#c34
Is that intended to be handled? It seems like we gave up on removing the ISO domain concept, perhaps also because of this missing feature - see last few comments of:
https://bugzilla.redhat.com/show_bug.cgi?id=1543512
Adding Michal. Michal - IMO we should make up our minds and provide a clear view - either undeprecate the ISO domain - remove deprecation notices from everywhere - or provide concrete plans to fill the missing gaps.
Forcing NFS storage domain in a system with high end FC/iSCSI storage does not make sense, and introduces reliability issues due to NFS unpredictable timeouts. We don't want to go back to having NFS on every system. Uploading to data domain should work for all use cases. If something does not work (booting from kernel image on data domain) it's a bug, probably something that was missed when we add the feature to keep iso disks on block storage. The issue with data domain is sharing the same domain with multiple DCs. This is not supported now since only one SPM can manage the storage domain (e.g create a new disk). But we have the infrastructure to support this. Of course we can support upload to iso domain, this depends on engine setting up the transfer properly, and probably requires new APIs in vdsm to create the file in the iso domain. Nir
Once upon a time, Yedidyah Bar David <didi@redhat.com> said:
Adding Michal. Michal - IMO we should make up our minds and provide a clear view - either undeprecate the ISO domain - remove deprecation notices from everywhere - or provide concrete plans to fill the missing gaps.
From a pure user perspective (never looked at the oVirt code for this)... Right now, it looks like the way to reference the ISO domain is iso://<filename>. Nothing specifies the domain name (I guess there can be only one ISO domain). Maybe an alternative (to get it out being of strictly tied to the one and only ISO domain) would be something like domain://<domain>/<file>, so which storage domain could be specified (and then it doesn't matter if it's an ISO domain or regular storage domain). Anyway, for my short term, it looks like I just need to build ISOs on the fly and upload them to the regular storage domain (since I don't have an ISO domain). -- Chris Adams <cma@cmadams.net>
Hi,
On 27 Jul 2021, at 21:24, Chris Adams <cma@cmadams.net> wrote:
From a pure user perspective (never looked at the oVirt code for this)...
Right now, it looks like the way to reference the ISO domain is iso://<filename>. Nothing specifies the domain name (I guess there can be only one ISO domain).
Maybe an alternative (to get it out being of strictly tied to the one and only ISO domain) would be something like domain://<domain>/<file>, so which storage domain could be specified (and then it doesn't matter if it's an ISO domain or regular storage domain).
Anyway, for my short term, it looks like I just need to build ISOs on the fly and upload them to the regular storage domain (since I don't have an ISO domain).
I think you can use httpisoboot vdsm hook [1] for this [1] https://github.com/oVirt/vdsm/tree/master/vdsm_hooks/httpsisoboot <https://github.com/oVirt/vdsm/tree/master/vdsm_hooks/httpsisoboot> k
participants (5)
-
Chris Adams -
Konstantin Shalygin -
Nir Soffer -
Shani Leviim -
Yedidyah Bar David