10:40 p.m.
--------------080102010006090400050504
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Current setup:
* 3 identical hosts running on HP GL180 g5 servers
o gluster running 5 volumes in replica 3
* engine running on VMWare Server on another computer (that computer is NOT
available to convert to a host)
Where I want to end up:
* 3 identical hosted-engine hosts running on HP GL180 g5 servers
o gluster running 6 volumes in replica 3
+ new volume will be nfs storage for engine VM
* hosted engine in oVirt VM
* as few changes to current setup as possible
The two pages I found on the wiki are: Hosted Engine Howto
<http://www.ovirt.org/Hosted_Engine_Howto> and Migrate to Hosted Engine
<http://www.ovirt.org/Migrate_to_Hosted_Engine>;. Both were written during
the testing process, and have not been updated to reflect production status.
I don't know if anything in the process has changed since they were written.
Process outlined in above two pages (as I understand it):
have nfs file store ready to hold VM
Do minimal install (not clear if ovirt node, Centos, or Fedora was
used--I am Centos-based)
# yum install ovirt-hosted-engine-setup
# hosted-engine --deploy
Install OS on VM
return to host console
at "Please install the engine in the VM" prompt on host
on VM console
# yum install ovirt-engine
on old engine:
service ovirt-engine stop
chkconfig ovirt-engine off
set up dns for new engine
# engine-backup --mode=backup --file=backup1 --log=backup1.log
scp backup file to new engine VM
on new VM:
# engine-backup --mode=restore --file=backup1 --log=backup1-restore.log
--change-db-credentials --db-host=didi-lap --db-user=engine --db-password
--db-name=engine
# engine-setup
on host:
run script until: "The system will wait until the VM is down."
on new VM:
# reboot
on Host: finish script
My questions:
1. Is the above still the recommended way to do a hosted-engine install?
2. Will it blow up at me if I use my existing host (with glusterfs all set
up, etc) as the starting point, instead of a clean install?
Thank you for letting me benefit from your experience,
Ted Miller
Elkhart, IN, USA
--------------080102010006090400050504
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Current setup:<br>
<ul>
<li>3 identical hosts running on HP GL180 g5 servers</li>
<ul>
<li>gluster running 5 volumes in replica 3<br>
</li>
</ul>
<li>engine running on VMWare Server on another computer (that
computer is NOT available to convert to a host)<br>
</li>
</ul>
Where I want to end up:<br>
<ul>
<li>3 identical hosted-engine hosts running on HP GL180 g5 servers</li>
<ul>
<li>gluster running 6 volumes in replica 3</li>
<ul>
<li>new volume will be nfs storage for engine VM</li>
</ul>
</ul>
<li>hosted engine in oVirt VM</li>
<li>as few changes to current setup as possible</li>
</ul>
<p>The two pages I found on the wiki are: <a
href="http://www.ovirt.org/Hosted_Engine_Howto">Hosted Engine
Howto</a> and <a
href="http://www.ovirt.org/Migrate_to_Hosted_Engine">Migrate to
Hosted Engine</a>. Both were written during the testing
process, and have not been updated to reflect production status.
I don't know if anything in the process has changed since they
were written.<br>
</p>
<p>Process outlined in above two pages (as I understand it):<br>
</p>
<blockquote>
<p>have nfs file store ready to hold VM</p>
<p>Do minimal install (not clear if ovirt node, Centos, or Fedora
was used--I am Centos-based)</p>
# yum install ovirt-hosted-engine-setup<br>
# hosted-engine --deploy<br>
<p>Install OS on VM<br>
</p>
<p>return to host console<br>
</p>
<p>at "Please install the engine in the VM" prompt on
host<br>
</p>
<p>on VM console<br>
# yum install ovirt-engine<br>
</p>
<p>on old engine: <br>
service ovirt-engine stop<br>
chkconfig ovirt-engine off</p>
<p>set up dns for new engine<br>
</p>
<p># engine-backup --mode=backup --file=backup1 --log=backup1.log<br>
scp backup file to new engine VM<br>
</p>
<p>on new VM:<br>
# engine-backup --mode=restore --file=backup1
--log=backup1-restore.log --change-db-credentials
--db-host=didi-lap --db-user=engine --db-password
--db-name=engine<br>
# engine-setup<br>
</p>
<p>on host:<br>
run script until: "The system will wait until the VM is
down."<br>
</p>
<p>on new VM:<br>
# reboot<br>
</p>
<p>on Host: finish script<br>
</p>
</blockquote>
My questions:<br>
<br>
1. Is the above still the recommended way to do a hosted-engine
install?<br>
<br>
2. Will it blow up at me if I use my existing host (with glusterfs
all set up, etc) as the starting point, instead of a clean install?<br>
<br>
Thank you for letting me benefit from your experience,<br>
Ted Miller<br>
Elkhart, IN, USA<br>
<br>
</body>
</html>
--------------080102010006090400050504--