On Wed, May 5, 2021 at 4:20 PM Derek Atkins <derek(a)ihtfp.com> wrote:
Hi,
On Wed, May 5, 2021 1:40 am, Yedidyah Bar David wrote:
>
>> And how about engine storage domain? I have a new NFS mount ready but it
>> did not ask me about which storage domain to use. Will it ask in later
>> stage?
>
> Yes, storage is handled (also asked about) in a later stage, after the
> engine is up and the host added to it.. This is a change from <= 4.2,
> and was done so that we can use the engine (and vdsm) for this,
> instead of duplicating their functionality in the deploy code.
Color me confused... How does this work?
Please review:
https://www.ovirt.org/images/Hosted-Engine-4.3-deep-dive.pdf
If I'm installing CentOS and then the Engine into the Hosted-Engine VM,
don't I need a storage domain for that OS defined in order for me to
install the OS into the VM? This sounds like a bootstrapping problem?
Or do I install into some temporary storage and then once the Engine +
VDSM are up and running I can assign the permanent storage and it will
save/copy the temporary storage over to the permanent storage? But in
the latter case, that would imply the ability to move the hosted-engine
storage domain from one place to another?
Or does 4.4 remove the ability to install the hosted-engine into a CentOS
OS and instead one must always use a Hosted Engine appliance?
NB: I installed back at 4.0 and have been upgrading ever since, so I've
never had to re-install the engine from scratch; I know I will need to do
that if I ever decide to upgrade from 4.3.10 to 4.4 (which, frankly, I am
not looking forward to doing any time soon).
> Good luck and best regards,
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com
www.ihtfp.com
Computer and Internet Security Consultant
--
Didi