----- Mensaje original -----
De: "Juan Hernandez" <jhernand@redhat.com> Para: "Adrian Gibanel" <adrian.gibanel@btactic.com> CC: "users" <users@ovirt.org> Enviados: Martes, 22 de Enero 2013 9:40:29 Asunto: Re: [Users] Help on an almost migrated ovirt-engine
On 01/22/2013 02:48 AM, Adrian Gibanel wrote:
I need to migrate an ovirt-engine from an All-In-One (AIO) setup to a dedicated machine.
So with an old mailing message I've tried to do it but not finished yet, that's why I ask for help.
I've written a wiki page for the experience so that it becomes a howto which can be found here:
http://www.ovirt.org/User:Adrian15/oVirt_engine_migration
At the last step the one that finally starts ovirt-engine I've decided to ask help here just in case I was missing something important.
So here are my doubts.
* Original message that inspired the howto is here: http://www.mail-archive.com/users@ovirt.org/msg00670.html * What packages should I delete safely from an AIO setup so that it's just an hypervisor once I've migrate the ovirt-engine part?
yum remove 'ovirt-engine-*' 'httpd' 'java-1.7.0-openjdk' 'jboss-as'
I've updated the howto. Thank you!
* Is the right way the one I've used to recreate the database? ** Origin pg_dump -U postgres engine | gzip > engine_db.gz ** Destination pg_dump -U postgres -s -f tempdb.dump engine dropdb -U postgres engine createdb -U postgres engine zcat engine_db.gz | psql -U postgres engine
I think this won't break anything, but if you want to create it exactly the same you can use the -O option of createdb:
createdb -U postgres -O engine engine
I've finally come with: * Origin: pg_dump -U postgres engine | gzip > engine_db.gz * Destination: dropdb -U postgres engine createdb -U postgres -O engine engine zcat engine_db.gz | psql -U postgres engine The last command was run finally with postgres user because using engine user I had these warnings: WARNING: no privileges could be revoked for "public" REVOKE WARNING: no privileges could be revoked for "public" REVOKE WARNING: no privileges were granted for "public" GRANT WARNING: no privileges were granted for "public" GRANT
* Let's read: http://www.mail-archive.com/users@ovirt.org/msg00682.html : WRT certificates, note that hostname should nt change, or SSL will be invalidated. Did he mean the SSL when you connect via http or https to the manager which currently doesn't bother me? Or maybe the SSL to connect to other hosts and communicate to vdsm (sorry if I'm saying something nonsense. I don't understand oVirt architecture completely) which bothers me? * Certificates is: /etc/pki/ovirt-engine ? Something more?
There is some information on how to change certificates here:
http://lists.ovirt.org/pipermail/users/2012-October/004167.html
It is not trivial, so better if you don't change the host name.
Can you please ellaborate why I should make sure that all these certificates know about the new host name? If this was a plain ssh key it would just work by copying and pasting its private key file. That's why my doubts. I don't mind if https at the browser complains about having one certificate for one domain and being another one. Maybe communication with vdsm on hypervisors will not work at all?
* Conf is: /etc/ovirt-engine ? Something more?
Yes, /etc/sysconfig/ovirt-engine, but you should be able to use the one generated during your new installation. The only difference will be the database password. Ok. I'll check that later. I understand that if no difference is found apart from the database password then no need to modify it in the destination.
Thank you! -- -- Adrián Gibanel I.T. Manager +34 675 683 301 www.btactic.com Ens podeu seguir a/Nos podeis seguir en: i Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio ambiente es cosa de todos. AVIS: El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge per error, us agrairem que ho feu saber immediatament al remitent i que procediu a destruir el missatge . AVISO: El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si han recibido este mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al remitente y que procedan a destruir el mensaje .