From tmiller at hcjb.org Tue Apr 1 15:40:46 2014 Content-Type: multipart/mixed; boundary="===============0352728936259516130==" MIME-Version: 1.0 From: Ted Miller To: users at ovirt.org Subject: [Users] Migrate cluster 3.3 -> 3.4 hosted on existing hosts Date: Tue, 01 Apr 2014 15:40:38 -0400 Message-ID: <533B1636.2070603@hcjb.org> --===============0352728936259516130== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable --------------080102010006090400050504 Content-Type: text/plain; charset=3D"ISO-8859-1"; format=3Dflowed 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 N= OT 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 = and 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=3Dbackup --file=3Dbackup1 --log=3Dbackup1.log scp backup file to new engine VM on new VM: # engine-backup --mode=3Drestore --file=3Dbackup1 --log=3Dbackup1-resto= re.log --change-db-credentials --db-host=3Ddidi-lap --db-user=3Dengine --db-pa= ssword --db-name=3Dengine # 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=3D"ISO-8859-1" Content-Transfer-Encoding: 7bit Current setup:

3 identical hosts running on HP GL180 g5 servers

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
- gluster running 6 volumes in replica 3
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 and 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=3Dbackup --file=3Dbackup1 --log=3Dbackup1.l= og
scp backup file to new engine VM

on new VM:
# engine-backup --mode=3Drestore --file=3Dbackup1 --log=3Dbackup1-restore.log --change-db-credentials --db-host=3Ddidi-lap --db-user=3Dengine --db-password --db-name=3Dengine
# 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-- --===============0352728936259516130== Content-Type: multipart/alternative MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="attachment.bin" LS0tLS0tLS0tLS0tLS0wODAxMDIwMTAwMDYwOTA0MDAwNTA1MDQKQ29udGVudC1UeXBlOiB0ZXh0 L3BsYWluOyBjaGFyc2V0PSJJU08tODg1OS0xIjsgZm9ybWF0PWZsb3dlZApDb250ZW50LVRyYW5z ZmVyLUVuY29kaW5nOiA3Yml0CgpDdXJyZW50IHNldHVwOgoKICAqIDMgaWRlbnRpY2FsIGhvc3Rz IHJ1bm5pbmcgb24gSFAgR0wxODAgZzUgc2VydmVycwogICAgICBvIGdsdXN0ZXIgcnVubmluZyA1 IHZvbHVtZXMgaW4gcmVwbGljYSAzCiAgKiBlbmdpbmUgcnVubmluZyBvbiBWTVdhcmUgU2VydmVy IG9uIGFub3RoZXIgY29tcHV0ZXIgKHRoYXQgY29tcHV0ZXIgaXMgTk9UCiAgICBhdmFpbGFibGUg dG8gY29udmVydCB0byBhIGhvc3QpCgpXaGVyZSBJIHdhbnQgdG8gZW5kIHVwOgoKICAqIDMgaWRl bnRpY2FsIGhvc3RlZC1lbmdpbmUgaG9zdHMgcnVubmluZyBvbiBIUCBHTDE4MCBnNSBzZXJ2ZXJz CiAgICAgIG8gZ2x1c3RlciBydW5uaW5nIDYgdm9sdW1lcyBpbiByZXBsaWNhIDMKICAgICAgICAg ICsgbmV3IHZvbHVtZSB3aWxsIGJlIG5mcyBzdG9yYWdlIGZvciBlbmdpbmUgVk0KICAqIGhvc3Rl ZCBlbmdpbmUgaW4gb1ZpcnQgVk0KICAqIGFzIGZldyBjaGFuZ2VzIHRvIGN1cnJlbnQgc2V0dXAg YXMgcG9zc2libGUKClRoZSB0d28gcGFnZXMgSSBmb3VuZCBvbiB0aGUgd2lraSBhcmU6IEhvc3Rl ZCBFbmdpbmUgSG93dG8gCjxodHRwOi8vd3d3Lm92aXJ0Lm9yZy9Ib3N0ZWRfRW5naW5lX0hvd3Rv PiBhbmQgTWlncmF0ZSB0byBIb3N0ZWQgRW5naW5lIAo8aHR0cDovL3d3dy5vdmlydC5vcmcvTWln cmF0ZV90b19Ib3N0ZWRfRW5naW5lPi4gIEJvdGggd2VyZSB3cml0dGVuIGR1cmluZyAKdGhlIHRl c3RpbmcgcHJvY2VzcywgYW5kIGhhdmUgbm90IGJlZW4gdXBkYXRlZCB0byByZWZsZWN0IHByb2R1 Y3Rpb24gc3RhdHVzLiAKSSBkb24ndCBrbm93IGlmIGFueXRoaW5nIGluIHRoZSBwcm9jZXNzIGhh cyBjaGFuZ2VkIHNpbmNlIHRoZXkgd2VyZSB3cml0dGVuLgoKUHJvY2VzcyBvdXRsaW5lZCBpbiBh Ym92ZSB0d28gcGFnZXMgKGFzIEkgdW5kZXJzdGFuZCBpdCk6CgogICAgaGF2ZSBuZnMgZmlsZSBz dG9yZSByZWFkeSB0byBob2xkIFZNCgogICAgRG8gbWluaW1hbCBpbnN0YWxsIChub3QgY2xlYXIg aWYgb3ZpcnQgbm9kZSwgQ2VudG9zLCBvciBGZWRvcmEgd2FzCiAgICB1c2VkLS1JIGFtIENlbnRv cy1iYXNlZCkKCiAgICAjIHl1bSBpbnN0YWxsIG92aXJ0LWhvc3RlZC1lbmdpbmUtc2V0dXAKICAg ICMgaG9zdGVkLWVuZ2luZSAtLWRlcGxveQoKICAgIEluc3RhbGwgT1Mgb24gVk0KCiAgICByZXR1 cm4gdG8gaG9zdCBjb25zb2xlCgogICAgYXQgIlBsZWFzZSBpbnN0YWxsIHRoZSBlbmdpbmUgaW4g dGhlIFZNIiBwcm9tcHQgb24gaG9zdAoKICAgIG9uIFZNIGNvbnNvbGUKICAgICMgeXVtIGluc3Rh bGwgb3ZpcnQtZW5naW5lCgogICAgb24gb2xkIGVuZ2luZToKICAgIHNlcnZpY2Ugb3ZpcnQtZW5n aW5lIHN0b3AKICAgIGNoa2NvbmZpZyBvdmlydC1lbmdpbmUgb2ZmCgogICAgc2V0IHVwIGRucyBm b3IgbmV3IGVuZ2luZQoKICAgICMgZW5naW5lLWJhY2t1cCAtLW1vZGU9YmFja3VwIC0tZmlsZT1i YWNrdXAxIC0tbG9nPWJhY2t1cDEubG9nCiAgICBzY3AgYmFja3VwIGZpbGUgdG8gbmV3IGVuZ2lu ZSBWTQoKICAgIG9uIG5ldyBWTToKICAgICMgZW5naW5lLWJhY2t1cCAtLW1vZGU9cmVzdG9yZSAt LWZpbGU9YmFja3VwMSAtLWxvZz1iYWNrdXAxLXJlc3RvcmUubG9nCiAgICAtLWNoYW5nZS1kYi1j cmVkZW50aWFscyAtLWRiLWhvc3Q9ZGlkaS1sYXAgLS1kYi11c2VyPWVuZ2luZSAtLWRiLXBhc3N3 b3JkCiAgICAtLWRiLW5hbWU9ZW5naW5lCiAgICAjIGVuZ2luZS1zZXR1cAoKICAgIG9uIGhvc3Q6 CiAgICBydW4gc2NyaXB0IHVudGlsOiAiVGhlIHN5c3RlbSB3aWxsIHdhaXQgdW50aWwgdGhlIFZN IGlzIGRvd24uIgoKICAgIG9uIG5ldyBWTToKICAgICMgcmVib290CgogICAgb24gSG9zdDogZmlu aXNoIHNjcmlwdAoKTXkgcXVlc3Rpb25zOgoKMS4gSXMgdGhlIGFib3ZlIHN0aWxsIHRoZSByZWNv bW1lbmRlZCB3YXkgdG8gZG8gYSBob3N0ZWQtZW5naW5lIGluc3RhbGw/CgoyLiBXaWxsIGl0IGJs b3cgdXAgYXQgbWUgaWYgSSB1c2UgbXkgZXhpc3RpbmcgaG9zdCAod2l0aCBnbHVzdGVyZnMgYWxs IHNldCAKdXAsIGV0YykgYXMgdGhlIHN0YXJ0aW5nIHBvaW50LCBpbnN0ZWFkIG9mIGEgY2xlYW4g aW5zdGFsbD8KClRoYW5rIHlvdSBmb3IgbGV0dGluZyBtZSBiZW5lZml0IGZyb20geW91ciBleHBl cmllbmNlLApUZWQgTWlsbGVyCkVsa2hhcnQsIElOLCBVU0EKCgotLS0tLS0tLS0tLS0tLTA4MDEw MjAxMDAwNjA5MDQwMDA1MDUwNApDb250ZW50LVR5cGU6IHRleHQvaHRtbDsgY2hhcnNldD0iSVNP LTg4NTktMSIKQ29udGVudC1UcmFuc2Zlci1FbmNvZGluZzogN2JpdAoKPGh0bWw+CiAgPGhlYWQ+ CgogICAgPG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7 IGNoYXJzZXQ9SVNPLTg4NTktMSI+CiAgPC9oZWFkPgogIDxib2R5IHRleHQ9IiMwMDAwMDAiIGJn Y29sb3I9IiNGRkZGRkYiPgogICAgQ3VycmVudCBzZXR1cDo8YnI+CiAgICA8dWw+CiAgICAgIDxs aT4zIGlkZW50aWNhbCBob3N0cyBydW5uaW5nIG9uIEhQIEdMMTgwIGc1IHNlcnZlcnM8L2xpPgog ICAgICA8dWw+CiAgICAgICAgPGxpPmdsdXN0ZXIgcnVubmluZyA1IHZvbHVtZXMgaW4gcmVwbGlj YSAzPGJyPgogICAgICAgIDwvbGk+CiAgICAgIDwvdWw+CiAgICAgIDxsaT5lbmdpbmUgcnVubmlu ZyBvbiBWTVdhcmUgU2VydmVyIG9uIGFub3RoZXIgY29tcHV0ZXIgKHRoYXQKICAgICAgICBjb21w dXRlciBpcyBOT1QgYXZhaWxhYmxlIHRvIGNvbnZlcnQgdG8gYSBob3N0KTxicj4KICAgICAgPC9s aT4KICAgIDwvdWw+CiAgICBXaGVyZSBJIHdhbnQgdG8gZW5kIHVwOjxicj4KICAgIDx1bD4KICAg ICAgPGxpPjMgaWRlbnRpY2FsIGhvc3RlZC1lbmdpbmUgaG9zdHMgcnVubmluZyBvbiBIUCBHTDE4 MCBnNSBzZXJ2ZXJzPC9saT4KICAgICAgPHVsPgogICAgICAgIDxsaT5nbHVzdGVyIHJ1bm5pbmcg NiB2b2x1bWVzIGluIHJlcGxpY2EgMzwvbGk+CiAgICAgICAgPHVsPgogICAgICAgICAgPGxpPm5l dyB2b2x1bWUgd2lsbCBiZSBuZnMgc3RvcmFnZSBmb3IgZW5naW5lIFZNPC9saT4KICAgICAgICA8 L3VsPgogICAgICA8L3VsPgogICAgICA8bGk+aG9zdGVkIGVuZ2luZSBpbiBvVmlydCBWTTwvbGk+ CiAgICAgIDxsaT5hcyBmZXcgY2hhbmdlcyB0byBjdXJyZW50IHNldHVwIGFzIHBvc3NpYmxlPC9s aT4KICAgIDwvdWw+CiAgICA8cD5UaGUgdHdvIHBhZ2VzIEkgZm91bmQgb24gdGhlIHdpa2kgYXJl OiA8YQogICAgICAgIGhyZWY9Imh0dHA6Ly93d3cub3ZpcnQub3JnL0hvc3RlZF9FbmdpbmVfSG93 dG8iPkhvc3RlZCBFbmdpbmUKICAgICAgICBIb3d0bzwvYT4gYW5kIDxhCiAgICAgICAgaHJlZj0i aHR0cDovL3d3dy5vdmlydC5vcmcvTWlncmF0ZV90b19Ib3N0ZWRfRW5naW5lIj5NaWdyYXRlIHRv CiAgICAgICAgSG9zdGVkIEVuZ2luZTwvYT4uJm5ic3A7IEJvdGggd2VyZSB3cml0dGVuIGR1cmlu ZyB0aGUgdGVzdGluZwogICAgICBwcm9jZXNzLCBhbmQgaGF2ZSBub3QgYmVlbiB1cGRhdGVkIHRv IHJlZmxlY3QgcHJvZHVjdGlvbiBzdGF0dXMuJm5ic3A7CiAgICAgIEkgZG9uJ3Qga25vdyBpZiBh bnl0aGluZyBpbiB0aGUgcHJvY2VzcyBoYXMgY2hhbmdlZCBzaW5jZSB0aGV5CiAgICAgIHdlcmUg d3JpdHRlbi48YnI+CiAgICA8L3A+CiAgICA8cD5Qcm9jZXNzIG91dGxpbmVkIGluIGFib3ZlIHR3 byBwYWdlcyAoYXMgSSB1bmRlcnN0YW5kIGl0KTo8YnI+CiAgICA8L3A+CiAgICA8YmxvY2txdW90 ZT4KICAgICAgPHA+aGF2ZSBuZnMgZmlsZSBzdG9yZSByZWFkeSB0byBob2xkIFZNPC9wPgogICAg ICA8cD5EbyBtaW5pbWFsIGluc3RhbGwgKG5vdCBjbGVhciBpZiBvdmlydCBub2RlLCBDZW50b3Ms IG9yIEZlZG9yYQogICAgICAgIHdhcyB1c2VkLS1JIGFtIENlbnRvcy1iYXNlZCk8L3A+CiAgICAg ICMgeXVtIGluc3RhbGwgb3ZpcnQtaG9zdGVkLWVuZ2luZS1zZXR1cDxicj4KICAgICAgIyBob3N0 ZWQtZW5naW5lIC0tZGVwbG95PGJyPgogICAgICA8cD5JbnN0YWxsIE9TIG9uIFZNPGJyPgogICAg ICA8L3A+CiAgICAgIDxwPnJldHVybiB0byBob3N0IGNvbnNvbGU8YnI+CiAgICAgIDwvcD4KICAg ICAgPHA+YXQgIlBsZWFzZSBpbnN0YWxsIHRoZSBlbmdpbmUgaW4gdGhlIFZNIiBwcm9tcHQgb24g aG9zdDxicj4KICAgICAgPC9wPgogICAgICA8cD5vbiBWTSBjb25zb2xlPGJyPgogICAgICAgICMg eXVtIGluc3RhbGwgb3ZpcnQtZW5naW5lPGJyPgogICAgICA8L3A+CiAgICAgIDxwPm9uIG9sZCBl bmdpbmU6IDxicj4KICAgICAgICBzZXJ2aWNlIG92aXJ0LWVuZ2luZSBzdG9wPGJyPgogICAgICAg IGNoa2NvbmZpZyBvdmlydC1lbmdpbmUgb2ZmPC9wPgogICAgICA8cD5zZXQgdXAgZG5zIGZvciBu ZXcgZW5naW5lPGJyPgogICAgICA8L3A+CiAgICAgIDxwPiMgZW5naW5lLWJhY2t1cCAtLW1vZGU9 YmFja3VwIC0tZmlsZT1iYWNrdXAxIC0tbG9nPWJhY2t1cDEubG9nPGJyPgogICAgICAgIHNjcCBi YWNrdXAgZmlsZSB0byBuZXcgZW5naW5lIFZNPGJyPgogICAgICA8L3A+CiAgICAgIDxwPm9uIG5l dyBWTTo8YnI+CiAgICAgICAgIyBlbmdpbmUtYmFja3VwIC0tbW9kZT1yZXN0b3JlIC0tZmlsZT1i YWNrdXAxCiAgICAgICAgLS1sb2c9YmFja3VwMS1yZXN0b3JlLmxvZyAtLWNoYW5nZS1kYi1jcmVk ZW50aWFscwogICAgICAgIC0tZGItaG9zdD1kaWRpLWxhcCAtLWRiLXVzZXI9ZW5naW5lIC0tZGIt cGFzc3dvcmQKICAgICAgICAtLWRiLW5hbWU9ZW5naW5lPGJyPgogICAgICAgICMgZW5naW5lLXNl dHVwPGJyPgogICAgICA8L3A+CiAgICAgIDxwPm9uIGhvc3Q6PGJyPgogICAgICAgIHJ1biBzY3Jp cHQgdW50aWw6ICJUaGUgc3lzdGVtIHdpbGwgd2FpdCB1bnRpbCB0aGUgVk0gaXMgZG93bi4iPGJy PgogICAgICA8L3A+CiAgICAgIDxwPm9uIG5ldyBWTTo8YnI+CiAgICAgICAgIyByZWJvb3Q8YnI+ CiAgICAgIDwvcD4KICAgICAgPHA+b24gSG9zdDogZmluaXNoIHNjcmlwdDxicj4KICAgICAgPC9w PgogICAgPC9ibG9ja3F1b3RlPgogICAgTXkgcXVlc3Rpb25zOjxicj4KICAgIDxicj4KICAgIDEu IElzIHRoZSBhYm92ZSBzdGlsbCB0aGUgcmVjb21tZW5kZWQgd2F5IHRvIGRvIGEgaG9zdGVkLWVu Z2luZQogICAgaW5zdGFsbD88YnI+CiAgICA8YnI+CiAgICAyLiBXaWxsIGl0IGJsb3cgdXAgYXQg bWUgaWYgSSB1c2UgbXkgZXhpc3RpbmcgaG9zdCAod2l0aCBnbHVzdGVyZnMKICAgIGFsbCBzZXQg dXAsIGV0YykgYXMgdGhlIHN0YXJ0aW5nIHBvaW50LCBpbnN0ZWFkIG9mIGEgY2xlYW4gaW5zdGFs bD88YnI+CiAgICA8YnI+CiAgICBUaGFuayB5b3UgZm9yIGxldHRpbmcgbWUgYmVuZWZpdCBmcm9t IHlvdXIgZXhwZXJpZW5jZSw8YnI+CiAgICBUZWQgTWlsbGVyPGJyPgogICAgRWxraGFydCwgSU4s IFVTQTxicj4KICAgIDxicj4KICA8L2JvZHk+CjwvaHRtbD4KCi0tLS0tLS0tLS0tLS0tMDgwMTAy MDEwMDA2MDkwNDAwMDUwNTA0LS0K --===============0352728936259516130==-- From didi at redhat.com Wed Apr 2 01:58:26 2014 Content-Type: multipart/mixed; boundary="===============0532010598972364701==" MIME-Version: 1.0 From: Yedidyah Bar David To: users at ovirt.org Subject: Re: [Users] Migrate cluster 3.3 -> 3.4 hosted on existing hosts Date: Wed, 02 Apr 2014 01:58:23 -0400 Message-ID: <804007172.2978791.1396418303885.JavaMail.zimbra@redhat.com> In-Reply-To: 533B1636.2070603@hcjb.org --===============0532010598972364701== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- Original Message ----- > From: "Ted Miller" > To: "users" > Sent: Tuesday, April 1, 2014 10:40:38 PM > Subject: [Users] Migrate cluster 3.3 -> 3.4 hosted on existing hosts > = > Current setup: > = > = > * 3 identical hosts running on HP GL180 g5 servers > = > = > * 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 > = > = > * 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 and 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. Basically things remained the same, with some details changing perhaps. > = > = > 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) Fedora/Centos/RHEL are supposed to work. ovirt node is currently not supported - iirc it's planned to be supported soon, not sure. > # 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=3Dbackup --file=3Dbackup1 --log=3Dbackup1.log > scp backup file to new engine VM > = > = > on new VM: Please see [1]. Specifically, if you had a local db, you'll first have to create it yourself. [1] http://www.ovirt.org/Ovirt-engine-backup#Howto > # engine-backup --mode=3Drestore --file=3Dbackup1 --log=3Dbackup1-restore= .log > --change-db-credentials --db-host=3Ddidi-lap --db-user=3Dengine --db-pass= word > --db-name=3Dengine The above assumes a db was already created and ready to use (access etc) using the supplied credentials. You'll naturally have to provide your own. > # 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? Yes. > = > 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? a. Probably yes, for now. I did not hear much about testing such a migration using an existing host - ovirt or gluster or both. I did not test that myse= lf either. If at all possible, you should use a new clean host. Do plan well and test. Also see discussions on the mailing lists, e.g. this one: http://lists.ovirt.org/pipermail/users/2014-March/thread.html#22441 Good luck, and please report back! -- = Didi --===============0532010598972364701==-- From tmiller at hcjb.org Fri May 23 14:41:04 2014 Content-Type: multipart/mixed; boundary="===============5404388308049111685==" MIME-Version: 1.0 From: Ted Miller To: users at ovirt.org Subject: Re: [ovirt-users] [Users] Migrate cluster 3.3 -> 3.4 hosted on existing hosts Date: Fri, 23 May 2014 14:40:50 -0400 Message-ID: <537F9632.9080101@hcjb.org> In-Reply-To: 804007172.2978791.1396418303885.JavaMail.zimbra@redhat.com --===============5404388308049111685== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 4/2/2014 1:58 AM, Yedidyah Bar David wrote: > ----- Original Message ----- >> From: "Ted Miller" >> To: "users" >> Sent: Tuesday, April 1, 2014 10:40:38 PM >> Subject: [Users] Migrate cluster 3.3 -> 3.4 hosted on existing hosts >> >> Current setup: >> * 3 identical hosts running on HP GL180 g5 servers >> * gluster running 5 volumes in replica 3 >> * engine running on VMWare Server on another computer (that compute= r 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 >> * 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 and Migrate to >> Hosted Engine . Both were written during the testing process, and have n= ot >> been updated to reflect production status. I don't know if anything in t= he >> process has changed since they were written. > Basically things remained the same, with some details changing perhaps. > >> 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) > Fedora/Centos/RHEL are supposed to work. ovirt node is currently not > supported - iirc it's planned to be supported soon, not sure. > >> # 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=3Dbackup --file=3Dbackup1 --log=3Dbackup1.log >> scp backup file to new engine VM >> >> >> on new VM: > Please see [1]. Specifically, if you had a local db, you'll first have > to create it yourself. > > [1] http://www.ovirt.org/Ovirt-engine-backup#Howto > >> # engine-backup --mode=3Drestore --file=3Dbackup1 --log=3Dbackup1-restor= e.log >> --change-db-credentials --db-host=3Ddidi-lap --db-user=3Dengine --db-pas= sword >> --db-name=3Dengine > The above assumes a db was already created and ready to use (access etc) > using the supplied credentials. You'll naturally have to provide your own. > >> # 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? > Yes. > >> 2. Will it blow up at me if I use my existing host (with glusterfs all s= et >> up, etc) as the starting point, instead of a clean install? > a. Probably yes, for now. I did not hear much about testing such a migrat= ion > using an existing host - ovirt or gluster or both. I did not test that my= self > either. > > If at all possible, you should use a new clean host. Do plan well and tes= t. > > Also see discussions on the mailing lists, e.g. this one: > > http://lists.ovirt.org/pipermail/users/2014-March/thread.html#22441 > > Good luck, and please report back! I have good news and bad news. I migrated the 3 host cluster from 3.4 to 3.4 hosted. The process went = fairly smoothly. Engine ran, I was able to add the three hosts to the = engine's domain, etc. That was all working about Thursday. (I did not get = fencing set up). Friday, at the end of the day, I shut down the entire system (it is not yet = in production) because I was leaving for a week's vacation/holiday. I am = fairly certain that I put the system into global maintenance mode before = shutting down. I know I shut down the engine before shutting down the host= s. Monday (10 days later) I came back from vacation and powered up the three = machines. The hosts came up fine, but the engine will not start. (I found = some gluster split-brain errors, and chased that for a couple of days, unti= l = I realized that the split-brain was not the fundamental problem.) During bootup /var/log/messages shows: May 21 19:22:00 s2 ovirt-ha-broker mgmt_bridge.MgmtBridge ERROR Failed to g= etVdsCapabilities: VDSM initialization timeout May 21 19:22:00 s2 ovirt-ha-broker mem_free.MemFree ERROR Failed to getVdsS= tats: VDSM initialization timeout May 21 19:22:00 s2 ovirt-ha-broker cpu_load_no_engine.EngineHealth ERROR Fa= iled to getVmStats: VDSM initialization timeout May 21 19:22:00 s2 ovirt-ha-broker engine_health.CpuLoadNoEngine ERROR Fail= ed to getVmStats: VDSM initialization timeout May 21 19:22:03 s2 vdsm vds WARNING Unable to load the json rpc server modu= le. Please make sure it is installed. and then /var/log/ovirt-hosted-engine-ha/agent.log shows: MainThread::ERROR::2014-05-21 19:22:04,198::hosted_engine::414::ovirt_hoste= d_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_vdsm) Failed try= ing to connect storage: MainThread::CRITICAL::2014-05-21 19:22:04,199::agent::103::ovirt_hosted_eng= ine_ha.agent.agent.Agent::(run) Could not start ha-agent Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/agen= t.py", line 97, in run self._run_agent() File "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/agen= t.py", line 154, in _run_agent hosted_engine.HostedEngine(self.shutdown_req= uested).start_monitoring() File "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/host= ed_engine.py", line 299, in start_monitoring self._initialize_vdsm() File "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/host= ed_engine.py", line 415, in _initialize_vdsm raise Exception("Failed trying to connect storage") Exception: Failed trying to connect storage I can manually mount and start storage, but then my = sanlock/gluster/split-brain bites me, and there are no instructions out the= re = on how to recover from this situation. I am starting over the "sanitary" way. The only thing getting reused is th= e = gluster file system. I will migrate one host at a time, and will get the = gluster system running under the hosts as I go, adding the host back into t= he = system as I go along. You were right, :( Ted Miller Elkhart, IN, USA P.S. I hope that the install scripts can eventually be modified to migrate = existing hosts, but I understand that first you must have it stable from a = clean install. --===============5404388308049111685==--