Hi,
On 01/24/2013 03:13 PM, Adrian Gibanel wrote:
As far as I know in Fedora you need to upgrade from Fedora 17 to
Fedora 18.
As you you're using CentOS I suppose you don't need to upgrade your
CentOS but I'm not sure at all.
This is not the case, it goes right if installed 3.2 from scratch on a
new machine. Don't think CentOS has a problem here.
Anyways what I've read in the mailing list about 3.1 to 3.2 update is
the following one:
* Update packages
* Run: engine-upgrade command
I don't know how easy it is to update packages in your case (stable to
beta) so you might do it in your way like this:
* Remove 3.1 packages
* Install 3.2 beta packages
* Run: engine-upgrade command
I have removed 3.1 using yum, installed 3.2 using yum and run the
engine-setup and not upgrade command. As seen engine-upgrade, tries
first to locate a mirror through yum.
Anyone tried so far a migration from old to new ?
From what I have read (not an expert) there's a difference between the
old and new database schema (and probably other parts of oVirt) and
the engine-upgrade handles that.
Maybe other list contributors can confirm if I'm missing some other
steps or not.
------------------------------------------------------------------------
*De: *"Alexandru Vladulescu" <[email protected]>
*Para: *"Adrian Gibanel" <[email protected]>
*CC: *"users" <[email protected]>
*Enviados: *Jueves, 24 de Enero 2013 10:59:14
*Asunto: *Re: [Users] 3.1 to 3.2 migration
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.
--
<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
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
--
Alexandru Vladulescu
System Engineer
---------------------------------------------------------------------------------
Bright Future Project Romania
Skype : avladulescu
Mobile : +4(0)726.373.098
---------------------------------------------------------------------------------
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
