On Sat, Aug 22, 2020 at 4:01 PM David White via Users <[email protected]> wrote: > > >by standalone do you mean all-in-one? or separate engine and hosts? > > I THINK all-in-one. :) > > > The following are the commands that I ran: > > sudo yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm > sudo yum module -y enable javapackages-tools pki-deps postgresql:12 > sudo yum install ovirt-engine > sudo engine-setup > sudo mkdir -p /data/images > sudo mkdir /data/iso > sudo chown 36:36 /data/iso > sudo chmod 0755 /data/iso > > >In 4.4 the change in imageio means it's not compatible with all-in-one > >anymore. > > Yes, in reading through your recent email thread here, that's what I picked > up on. > I was pretty sure that I hit the same bug, but wasn't positive. > > So, what's the point of all-in-one if you cannot upload ISOs and boot VMs off > of ISOs? > Is there an alternative way to setup a VM in all-in-one, such as boot from > PXE or something? > > > Regardless, the all-in-one setup was just for learning purposes. > I may try a different install approach, and try to get the self-hosted engine > working. That said, I'm still unclear on the exact differences between the > "self-hosted engine" and the standalone Manager. I'll go re-read earlier > responses to my questions on that, as well as the glossary of sorts that Didi > was so kind to write in your earlier thread on the imageio issue.
Let me clarify (again?): All-in-one, meaning - both (standalone) engine and actual VM processes (vdsm/libvirtd/etc. and your VM's qemu processes) on the same machine - is not supported since 4.0 and is not tested routinely and systematically. The fact that it does usually work, and the fact that people sometimes report successes with this, is very nice to know, but does not change the situation :-) If all you have is a single physical machine that you want to use for oVirt, you have, basically, two options: 1. Use HCI (meaning, hosted-engine + gluster). That's, I guess, what most people do, at least in production. When it works (usually, and we definitely aim for always!), it's the easiest way to install and get things going, but is more complex under the hood and harder to understand/debug if you do not know quite well how things work internally. 2. Use some other virtualization method - I think most people use plain virt-manager - to create separate VMs, and imitate multiple-machines setup using these VMs. E.g. one machine for the (standalone) engine, another for storage (e.g. nfs/iscsi/gluster), a few more as hosts (with nested-kvm), etc. Latter, (2.), is what we use in CI - see projects lago and ovirt-system-tests if interested. Re the imageio upload issue: If it's indeed a result of using all-in-one, then please wait until Michael's bug is fixed, or see the other thread, or see above for using not-all-in-one :-) (But feel free to keep debugging this with Michael's help if both of you feel like it!). Best regards, > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Saturday, August 22, 2020 7:49 AM, Michael Jones <[email protected]> > wrote: > > > I see you are using 4.4 standalone; > > > > > by standalone do you mean all-in-one? or separate engine and hosts? > > > > > In 4.4 the change in imageio means it's not compatible with all-in-one > > anymore, i'll be raising a bug request to support this later today (but > > officially all-in-one support ended in 4.0 so i don't know if the bug > > will be actioned). > > > > > Kind Regards, > > > > > Mike > > > > > On 22/08/2020 12:06, David White via Users wrote: > > > > > > Ok, that at least got the certificate trusted. > > > Thank you for the fast response on that! > > > The certificate is now installed and trusted, and I removed the exception > > > in Firefox. > > > (Screenshots attached) > > > Unfortunately, the upload is still not working. > > > I'm still getting the same error message that "Connection to > > > ovirt-imageio-proxy service has failed." > > > > > 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/QSUGX7LWYR7WSGEIRDE7LARKTSLC7NPA/ > > _______________________________________________ > 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/ETYIYCPOQ7UATD5DHO3SL6DECIFRAIPQ/ -- 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/TQH2NE4GFACMVNCDIFWQ33ESTL7RXS6I/
