On Tue, Jul 27, 2021 at 11:56 AM Shani Leviim <[email protected]> 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 <[email protected]> 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 <[email protected]>
>> _______________________________________________
>> Users mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>> 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/[email protected]/message/IDIDY6ZLZCRMVMQTASSKOL4A7VHDZCVI/
>
> _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 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/[email protected]/message/L74BPUBL2IYMT5O5AD562Y63YLENWMUV/



-- 
Didi
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/4FNXGFX7G3M2I7I5F5SM25TMKLVV5NVL/

Reply via email to