----- Original Message -----
From: "Nathan Stratton" <nathan@robotics.net> To: "Dan Yasny" <dyasny@redhat.com> Cc: users@ovirt.org, "Andrew Cathrow" <acathrow@redhat.com> Sent: Monday, 27 February, 2012 4:13:54 PM Subject: Re: [Users] Using virsh on the node
On Mon, 27 Feb 2012, Dan Yasny wrote:
So the engine is a VM in that same cluster, along with the VMs it manages?
Yes, the only thing I have not been able to figure out is how to let the ovirt-engine know that ovirt-engine is running. :) I thought that it would see via libvirt, but it does not. I also tried setting it in the db, but it keeps getting cleared. Any idea on how to let ovirt-engine know that a host has been started manually?
Seriously, not a good idea. The Engine is supposed to be looking at the setup, and not be in the setup, where it may be affected by the problems that might occur to the setup. I'm pretty sure there's lots of though being devoted to removing this limitation, but when we say it's a bad idea, it really is, it's not like we simply want you to run an extra machine
What do you use for storage?
That's easier than block storage, but still, what happens if the host where the engine was running failed - who would update VM statuses and restart the HA VMs?
NFS:
mount 10.13.0.4:/images/ /rhev/data-center/mnt/10.13.0.4:_images mount 10.13.0.4:/iso/ /rhev/data-center/mnt/10.13.0.4:_iso
Dan Yasny Red Hat Israel +972 9769 2280
<> Nathan Stratton CTO, BlinkMind, Inc. nathan at robotics.net nathan at blinkmind.com http://www.robotics.net http://www.blinkmind.com
-- Regards, Dan Yasny Red Hat Israel +972 9769 2280