On Tue, Aug 18, 2020 at 8:51 PM Michael Jones <mj(a)mikejonesey.co.uk> wrote:
On 18/08/2020 17:58, Nir Soffer wrote:
it does sound as if, my problems are around the fact that i am using an
all-in-one box, (host and engine all in one);
https://www.ovirt.org/download/alternate_downloads.html
This explains how that you can install all-in-one when engine is a VM
running on the single host, not as a program running on the host.
Let's clarify the terminology first. I admit we are not always super-clear
about this.
- Standalone engine - Engine is running on some machine, which it does
not manage by itself. Normally, this is a physical machine, but can be
a VM managed by something else (virsh/virt-manager, another ovirt engine,
vmware/virtualbox/hyperv/xen, etc.).
- Hosted-engine - An engine that is running in a VM, that runs inside
a host, that this engine manages. If it sounds like a chicken-and-egg
problem, it indeed is... See documentation and some presentation slides
on the website for the architecture, if interested.
- All-In-One - a Standalone engine that also manages, as a host, the
machine on which it runs. This used to have official support in the
past, in terms of code helping to implement it (in engine-setup):
https://www.ovirt.org/develop/release-management/features/integration/all...
As above page states, this is long gone. However, over the years,
people did report successes in doing this manually - install and
setup an engine, then add it to itself. I agree it would be nice to
keep it working, and the discussion below indeed clarifies that it's
currently broken, but this is definitely very low priority IMO. The
official answer to the question "How can I setup oVirt on a single
machine?" is: Use Hosted-engine with gluster, a.k.a HCI.
How did you managed to get engine installed on the same host?
I would expect that the installer would fail or at least warn about this.
The alternate install method is essentially, install packages and run engine-setup, which
doesn't setup the hosted vm. The default installer via cockpit always installs engine
as vm.
perhaps a warning is needed on the alternate installer page for epel8.
at the moment there is only a recommendation to use the normal installer.
On 18/08/2020 17:58, Nir Soffer wrote:
the download / upload function is important to me as my backup solution
is dependent on this.
Until the sort this out, you should know that you can transfer images
without the
proxy. The proxy is needed only for the UI, for cases when engine and hosts are
on different networks, so the only way to transfer images is via the
engine host.
I use vprotect which i think is dependent on the proxy, but I'll definitely checkout
the sdk/scripts you linked.
I'll post an update once the new host is setup the normal way / working.
Thanks again.
Michael Jones
--
Didi