[Engine-devel] hosted engine in 3.4

[Jiri Moskovcak]

On 03/13/2014 02:54 PM, Yedidyah Bar David wrote:
> ----- Original Message -----
>> From: "Jiri Moskovcak" <jmoskovc at redhat.com>
>> To: "engine-devel" <engine-devel at ovirt.org>
>> Sent: Thursday, March 13, 2014 3:27:11 PM
>> Subject: [Engine-devel] hosted engine in 3.4
>>
>> Hi,
>> I was testing the hosted-engine in 3.4 and ran into some troubles, so
>> I'm going to share the results to get some help (or ideas how to fix
>> those problems)
>>
>> Minor:
>> 1. You need to have some MAC address with static ip and FQDN, otherwise
>> you have to change /etc/hosts at least for the first part of the setup
>>
>> - I think the setup wizard should be improved to do this workaround
>> automatically
>
> Not sure what you refer to - the host? VM? Both?
>
> deploy lets you change the MAC for the VM if you want, and also shows you
> the random MAC it have chosen. Both of these should allow you to config
> your dhcp/dns server at that point and have the VM automatically get the
> right ip/hostname during OS installation.
>
> Not sure what you mean exactly - we never edit /etc/hosts files, and
> generally expect a stable dhcp/dns installation. That's true also for a
> normal engine installation.
>

- the VM, I was in the situation where I didn't have the chance to 
change the dhcp config at the time when I was installing the VM, so the 
only way for me was to change the /etc/hosts to cheat the setup wizard

>>
>> 2. When the VM install is complete I would expect the setup wizard to
>> install the engine to the VM automatically - which at least in my case -
>> doesn't happen
>
> We intend to supply some image (iso/ovf) that will include everything
> needed. Not sure when this will be ready. For the time being, you do
> everything by yourself - install the OS, add repos, install and setup
> the engine, etc. Note that you can choose network boot and make everything
> automated.
>

- I'm talking about the engine install inside the VM. I have the VM with 
the os, so the hosted-engine-setup can ask for the root password and 
simply install all the packages and configure the engine (I don't 
consider this a bug more like a idea for improvements)

>>
>> - I found a mallformed fedora-virt-prerelease.repoo file on the
>> installed vm, which might be the cause:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1075963
>>
>> Major:
>> 1. once I managed to install the engine to the vm it tried to add the
>> host it was running on to the engine and it failed with a message "Host
>> compatibility version doesn't match the cluster compatibility version",
>> and then it marked the host as non operational which killed the vm with
>> the engine, so the engine actually committed suicide...
>>
>> - the host and the engine were installed from the same repo, so I guess
>> the incompatibility was caused by the CPU family, and even if I made the
>
> That's probably because you have a problem with the repo (as pointed above)
> and install different versions on the host and VM.

- no, when I found the broken repo file I've fixed it to use the same as 
the host and only after that I've installed the engine

>
>> mistake I think the engine should be a bit more clever and not kill itself
>
> I might agree here, but generally this should not happen.
>
> You are of course more than welcome to open bugs where relevant!
>

I will, just want to try that once more, to get more details.

Thanks,
Jirka