Re: [Engine-devel] hosted engine in 3.4
Il 13/03/2014 14:27, Jiri Moskovcak ha scritto:
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)
Hi, thanks for testing Hosted Engine
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
Well, you can have DHCP and DNS configured before starting the deploy process and assign
the MAC address to the VM you're going to create for getting
the right IP and avoid to use /etc/hosts.
But yes, otherwise you need to use static IPs and configure /etc/hosts accordingly.
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
No, it's a manual step, there's no automation for doing that yet.
- 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
Can't reproduce the issue, closed as works for me, please reopen it if you can provide
a sequence for reproducing it.
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...
this is indeed due to malformed fedora-virt-prerelease.repoo. You had VDSM running in 3.3
compatibility mode because you're missing latest libvirt
while the engine is running a cluster in 3.4 compatibility mode.
- 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
mistake I think the engine should be a bit more clever and not kill itself
I think that we can add a check on vdsm compatibility level and create the engine cluster
with the same level, not assuming that people are running
latest libvirt.
BTW I'm not sure about implications in running Hosted Engine in 3.3 compatibility
mode.
CCing VDSM people.
--Jirka
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com