On Wed, Aug 19, 2020 at 12:29 PM Michael Jones <mj@mikejonesey.co.uk> wrote:
On 19/08/2020 06:52, Yedidyah Bar David wrote:
On Tue, Aug 18, 2020 at 8:51 PM Michael Jones <mj@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/allino...
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.
from the link you shared, the status is;
Current status
Included since 3.1 Deprecated since 3.6.0 Removed since 4.0.0
I think there should be a warning that the install is deprecated, traversing;
- https://www.ovirt.org/ - https://www.ovirt.org/download/ (download button) - https://www.ovirt.org/download/alternate_downloads.html (Alternate download options)
There is no warning the method was deprecated and will be missing functionality.
The steps detailed on the alt install page are for the all-in-one running engine-setup.
It's also worth noting this works fine in;
Version 4.3.1.1-1.el7
but not in;
Version 4.4.1.10-1.el8
(el8 has the change in imageio daemons)
The alternate install method is still useful to have, but i think a red warning about all-in-one on el8 on that page would be good.
Kind Regards, Michael Jones
Micheal, can you file a bug for this? If you have a good use case for all-in-one deployment (not using hosted engine), please explain it in the bug. Personally I think simple all-in-one deployment without the complexity of hosted engine is better, and we should keep it, but for this we need to teach engine to handle the case when the proxy and the daemon are the same server. In this case engine will not try to setup a proxy ticket, and image transfer would work directly with the host daemon. I'm not very optimistic that we will support this again, since this feature is not needed for RHV customers, but for oVirt this makes sense. Nir