<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 10/29/2015 05:49 AM, Roy Golan
wrote:<br>
</div>
<blockquote
cite="mid:CAC_JqcmkCAy91h8z_X1YA5eneyEQSRjqAJ4DU_FbBVxhV09Tig@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Oct 29, 2015 at 11:39 AM, Roy
Golan <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:rgolan@redhat.com" target="_blank">rgolan@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote"><span class="">On Wed, Oct
28, 2015 at 10:23 PM, John Florian <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:jflorian@doubledog.org"
target="_blank">jflorian@doubledog.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px
0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Can somebody
please point me to documentation or describe how
I should<br>
proceed with this task? I see lots of pages for
moving from a physical<br>
engine to a VM and vice-versa but am having no
luck finding how to go<br>
about building a new HE to obsolete my original.<br>
<span><font color="#888888"><br>
</font></span></blockquote>
<div><br>
</div>
</span>
<div>using ovirt-hosted-engine-setup you can choose
a setup without using the appliance. So you can
scratch install your VM <br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
<br>
</div>
<div>BTW the ovirt-engine-appliacnce we build [1] is Centos
based. Seems like perfect candidate. <br>
<br>
</div>
<div>#install the appliance <br>
</div>
<div>yum install ovirt-engine-appliance<br>
<br>
</div>
<div>#and then run the setup<br>
</div>
<div>ovirt-hosted-engine-setup<br>
<br>
</div>
<div>choose "disk" in this stage<br>
<pre>Please specify the device to boot the VM from (cdrom, disk, pxe) [cdrom]: disk
</pre>
<pre><span style="font-family:arial,helvetica,sans-serif">it will suggest the downloaded appliance automatically</span>
</pre>
<pre><span style="font-family:arial,helvetica,sans-serif">See this wiki for reference <a moz-do-not-send="true" href="http://www.ovirt.org/Features/HEApplianceFlow#Testing">http://www.ovirt.org/Features/HEApplianceFlow#Testing</a></span>
</pre>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Neat! I was unaware of the HEA so I'm happy to learn of this
offering. However, my concern is focused more on a procedure that I
presently can only imagine looking something akin to:<br>
<br>
1. hosted-engine --set-maintenance --mode=global<br>
2. hosted-engine --vm-poweroff<br>
3. ovirt-hosted-engine-setup ...<br>
4. use the exact same host name and IP address<br>
5. hosted-engine --vm-start<br>
6. hosted-engine --set-maintenance --mode=none<br>
<br>
Or perhaps:<br>
<br>
1. create a new guest<br>
2. inside run foo to deploy the HE packages<br>
3. configure it be aware of existing HE<br>
4. run bar manually or wait for the two HE's to sync their state,
sort of like a RAID mirror<br>
5. power off the original HE guest and allow the new one to be the
sole provider going forward<br>
<br>
My confusion may simply stem from having forgot much of the process
when I deployed my HE back in January this year. But I thought it
best to get started on the right foot for the simplest and/or best
practice.<br>
<pre class="moz-signature" cols="72">--
John Florian
</pre>
</body>
</html>