Dear Adrian,
By migration I mean to say "migration of the products from 3.1 to 3.2 --
or upgrade of the Ovirt platform". The test upgrade was done, in my
case, on a machine that only acts as a node controller in the system,
therefore there is no ISO domains, local storage volumes or vdsm daemon
for hypervisior purpose running.
Using, dreyou's repo, I included the 3.2 alpha release, removed the 3.1
version clean from the system, install all the 3.2 ovirt packages
version and run engine-setup on the new installation.
I did not run engine-cleanup, therefore the DB was untouched and running
engine-setup, I saw that the DB initialization sequence was pushing new
table & data updates on the running DB from postgres as the new size
went from 10MB to 15MB.
After completing the setup, I was only able to login into the http
section configured to port 80, but going to admin portal on 443 proved
to be impossible as the "page could not be displayed" was listed.
In 3.1 I am using port 8080 for http and 8443 for https, but in the 3.2
version, trying to configure in the engine-setup to run same or other
ports different from 80 and 443, proved to make the (jboss server) not
listening on https connections when tried to log in.
As a remark, I saw a different integration mechanism between 3.1 and 3.2
versions, on how jboss interacts with ovirt-engine process. In 3.1 the
jboss was running (if configured) on -server daemon process (in
netstat); and if not configured as java; and in 3.2 the jboss process I
guess it's started withing the engine-service process (seen that in
netstat -tupan).
I might add, that I don't want to strictly run the jboss with https
adding in apache files in conf.d the ovirt-engine.conf (where the
ProxyPass is added).
Reading the list, I could not find any threads open so far for the 3.1
to 3.2 migration (upgrade/update platform), therefore I had open this in
hope that someone else has tested this so far.I'm guessing the 3.2 as we
know it, it not a stable release yet, so, some bugs or incompatibility
issues might arise during the upgrade/swap versions process.
Any thoughts on this ?
My regards to you all,
Alex.
On 01/24/2013 02:26 AM, Adrian Gibanel wrote:
------------------------------------------------------------------------
*De: *"Alexandru Vladulescu" <avladule...@bfproject.ro>
*Para: *"users" <users@ovirt.org>
*Enviados: *Martes, 22 de Enero 2013 20:47:55
*Asunto: *[Users] 3.1 to 3.2 migration
Hi everybody,
This might seem to be a stupid question but I might just give it a
shot
and ask you if has anybody tried so far to migrate a 3.1 stable to
a 3.2
alpha release ? On my side I have no luck.
What do you mean by migrating? Updating packages on the same machine?
Migrating from one machine to another one?
You mean you want to update/migrate ovirt-engine, isn't it ?
Might have found a bug as well, but that is what you need to
confirm to
me. I had the jboss setup running on port http 8080 and for https
8443.
After the upgrade, everything I try besides the port 80 and 443
doesn't
work. If I try to reconfigure the previous used ports, I find java
listening on port 8080 for http, but when I try to log in and
switch to
https on admin portal there is nothing listening out there and I get
"Page cannot be displayed".
How do you try to reconfigure it? What commands do you run? Or what
files do you edit?
If we cannot consider migration, would it be sufficient to insert the
dump from the 3.1 into 3.2 current alpha release ?
As I said above we don't know what you mean by migration.
--
<http://www.btactic.com/>*Adrián Gibanel*
I.T. Manager
+34 675 683 301
www.btactic.com <http://btactic.com/>
*
Ens podeu seguir a/Nos podeis seguir en:
<http://www.facebook.com/pages/btactic/118651634826400?v=app_9953271133>
i <http://twitter.com/btactic>*
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.
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
