On Mon, Nov 19, 2018 at 6:20 AM Michal Skrivanek <michal.skrivanek@redhat.com> wrote:


> On 18 Nov 2018, at 11:17, Yedidyah Bar David <didi@redhat.com> wrote:
>
> On Sat, Nov 17, 2018 at 6:32 PM, Shawn Weeks <sweeks@weeksconsulting.us> wrote:
>> The only issue with the UI is I’m on VPN so uploading from my local machine
>> would be extremely slow. I discovered the –insecure flag for the cli and
>> that seems to have worked.
>
> Please note that we intend to deprecate this tool. Please try the api/sdk
> as suggested by Nir and tell us if you have any comments/issues etc. Thanks.
>
> Actually I thought we already deprecated it in 4.2, but I now searched and
> can't find anything like [1][2] (which was for the image uploader) or a note
> in the release notes [3]. Adding Sandro. Is it too late now to deprecate
> in 4.2 (so that we can remove in 4.3)?

There are still some shortcomings about ISOs on data domains which need to be addressed. As long as we keep ISO domain we have to keep the uploader, because the UI upload doesn’t support ISO domain. And we need to keep ISO domain because none of the  non-engine flows have been changed - There’s no REST API to get an ISO list anymore

Which is currently an open bug for people who are now using VM Portal and putting their ISOs on a data domain. Seems to me this is a very large gap.
 
- you would have to iterate through every single SD which doesn’t scale at all. virt-v2v is not changed, remote-viewer hasn’t been changed, any other 3rd party tool interacting with oVirt doing anything with ISOs likely didn’t change

>
> See also [4][5], which are for RHV.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1306637
> [2] https://www.ovirt.org/release/4.0.0/#ovirt-image-uploader
> [3] https://ovirt.org/release/4.2.0/
> [4] https://bugzilla.redhat.com/show_bug.cgi?id=1579119
> [5] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/administration_guide/sect-the_iso_uploader_tool
>
> Thanks and best regards,
>
>>
>>
>>
>> Thanks
>>
>> Shawnk
>>
>>
>>
>> From: Nir Soffer <nsoffer@redhat.com>
>> Sent: Saturday, November 17, 2018 8:43 AM
>> To: Shawn Weeks <sweeks@weeksconsulting.us>
>> Cc: users <users@ovirt.org>; Daniel Erez <derez@redhat.com>
>> Subject: Re: [ovirt-users] Engine ISO Uploader - SSL Peer Not Trusted
>>
>>
>>
>> On Sat, Nov 17, 2018, 02:45 Shawn Weeks <sweeks@weeksconsulting.us wrote:
>>
>> Trying to upload an iso using engine-iso-uploader on a hosted-engine
>> instance and I’m getting an SSL Error.  I followed the directions at
>> https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL/ to setup
>> SSL and am able to login to the Admin console without an issue. Also checked
>> that things like curl recognize the CA correctly. Not sure where
>> engine-iso-uploader is getting it’s trust store.
>>
>>
>>
>> [root@cloud ~]# engine-iso-uploader list
>>
>> Please provide the REST API password for the admin@internal oVirt Engine
>> user (CTRL+D to abort):
>>
>> ERROR: Unable to connect to REST API at
>> https://cloud.dev.example.com:443/ovirt-engine/api due to SDK error
>>
>> Message: Error while sending HTTP request: (60, "Peer's certificate issuer
>> has been marked as not trusted by the user.")
>>
>>
>>
>> What am I missing?
>>
>>
>>
>> If you ate using 4.2, you can upload iso files to data domains. You can
>> upload directly from the UI:
>>
>>
>>
>> 1. Open storage > disks
>>
>> 2. Click Upload > Start
>>
>> 3. Select file and fill in the form
>>
>>
>>
>> For faster upload or automation, you can use the SDK. See this example code:
>>
>>
>>
>> https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk.py
>>
>>
>>
>> With some configuration changes you can use this as command line tool for
>> uploading iso or other images.
>>
>>
>>
>> Nir
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-leave@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/MHEE6MQR2PFKPHFUKVUKMNLN36OU5PQZ/
>>
>
>
>
> --
> Didi
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AUXTIGNWFZJMWKFO55TXIM555PCSPWAH/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UPAS2H6QRWTQHW6HDPCI7CZPZNXV272B/


--

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA

gshereme@redhat.com    IRC: gshereme