<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 16, 2016 at 9:29 AM, Yedidyah Bar David <span dir="ltr"><<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Jun 16, 2016 at 9:10 AM, Yaniv Kaul <<a href="mailto:ykaul@redhat.com">ykaul@redhat.com</a>> wrote:<br>
><br>
><br>
> On Thu, Jun 16, 2016 at 8:53 AM, Yedidyah Bar David <<a href="mailto:didi@redhat.com">didi@redhat.com</a>> wrote:<br>
>><br>
>> On Thu, Jun 16, 2016 at 5:33 AM, Sandvik Agustin<br>
>> <<a href="mailto:agustinsandvik@gmail.com">agustinsandvik@gmail.com</a>> wrote:<br>
>> > Hi users,<br>
>> ><br>
>> > Good day, is it possible to configure two ovirt-engine to manage one<br>
>> > hypervisor? My purpose for this is what if the first ovirt-engine fails,<br>
>> > I<br>
>> > still have the 2nd ovirt-engine to manage hypervisor.<br>
>> ><br>
>> > is this possible? or any suggestion similar to my purpose?<br>
>><br>
>> The "normal" solution is hosted-engine, which has HA - the engine<br>
>> runs in a VM, and HA daemons monitor it and the hosts, and if there<br>
>> is a problem they can start it on another host.<br>
>><br>
>> There were discussions in the past, which you can find in the list<br>
>> archives,<br>
>> about running two engines against a single database, and current bottom<br>
>> line<br>
>> is that it's not supported, will not work, and iiuc will require some<br>
>> significant development investment to support.<br>
>><br>
>> You might manage to have an active/passive solution - install an engine<br>
>> on two machines, configure both to use the same remote database, but<br>
>> make sure only one of them is active at any given time. Not sure if that's<br>
>> considered "fully supported", but might come close.<br>
><br>
><br>
> That's not enough - they need to share the same set of certificates...<br>
<br>
</span>Best is to simply clone the machine after initial setup then change<br>
what's needed, or backup/restore only files (engine-backup --mode=backup<br>
--scope=files).<br>
<br>
Didn't check, but I do not think they actually need all the certs of<br>
all hosts - that is, that it's not mandatory to keep /etc/pki synced<br>
between them after initial setup. Didn't try that myself.<br></blockquote><div><br></div><div>I'm not sure what happens when you provision a host from Mgmt A, then move to Mgmt B and provision another from it:</div><div>1. Mgmt A won't be aware of that host, from cert req perspective. May not be such a big deal - donno.</div><div>2. Can Mgmt A provision another host? Need to ensure the certificate serial numbers are OK, etc.</div><div><br></div><div>They really need to share the CA DB.</div><div>The backup-restore sounds like good approach to me.</div><div>Y.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
> Y.<br>
><br>
>><br>
>><br>
>> You can find on the net docs/resources about creating a redundant<br>
>> postgresql cluster.<br>
>><br>
>> Best,<br>
>> --<br>
>> Didi<br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
>> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
><br>
<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Didi<br>
</font></span></blockquote></div><br></div></div>