Re: [Users] 3.1 to 3.2 migration

24 Jan 2013

      This is a multi-part message in MIME format.
--------------080509060906050806010200
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

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" <avladulescu@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.
--------------080509060906050806010200
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix"><br>
      Dear Adrian,<br>
      <br>
      <br>
      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.<br>
      <br>
      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.<br>
      <br>
      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.<br>
      <br>
      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.<br>
      <br>
      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.<br>
      <br>
      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).<br>
      <br>
      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).<br>
      <br>
      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.<br>
      <br>
      <br>
      Any thoughts on this ?<br>
      <br>
      <br>
      My regards to you all,<br>
      Alex.<br>
      <br>
      On 01/24/2013 02:26 AM, Adrian Gibanel wrote:<br>
    </div>
    <blockquote
      cite="mid:15617682.96.1358987201946.JavaMail.adrian@adrianworktop"
      type="cite">
      <style type="text/css">p { margin: 0; }</style>
      <div style="font-family: arial,helvetica,sans-serif; font-size:
        10pt; color: #000000">
        <hr id="zwchr">
        <blockquote id="DWT388" style="border-left:2px solid rgb(16, 16,
255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>De:
          </b>"Alexandru Vladulescu" <a class="moz-txt-link-rfc2396E" href="mailto:avladulescu@bfproject.ro"><avladulescu@bfproject.ro></a><br>
          <b>Para: </b>"users" <a class="moz-txt-link-rfc2396E" href="mailto:users@ovirt.org"><users@ovirt.org></a><br>
          <b>Enviados: </b>Martes, 22 de Enero 2013 20:47:55<br>
          <b>Asunto: </b>[Users] 3.1 to 3.2 migration<br>
          <br>
          Hi everybody,<br>
          <br>
          This might seem to be a stupid question but I might just give
          it a shot <br>
          and ask you if has anybody tried so far to migrate a 3.1
          stable to a 3.2 <br>
          alpha release ? On my side I have no luck.<br>
        </blockquote>
        What do you mean by migrating? Updating packages on the same
        machine?<br>
        Migrating from one machine to another one?<br>
        You mean you want to update/migrate ovirt-engine, isn't it ?<br>
        <blockquote id="DWT389" style="border-left: 2px solid rgb(16,
          16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0,
          0, 0); font-weight: normal; font-style: normal;
          text-decoration: none; font-family:
          Helvetica,Arial,sans-serif; font-size: 12pt;">Might have found
          a bug as well, but that is what you need to confirm to <br>
          me. I had the jboss setup running on port http 8080 and for
          https 8443. <br>
          After the upgrade, everything I try besides the port 80 and
          443 doesn't <br>
          work. If I try to reconfigure the previous used ports, I find
          java <br>
          listening on port 8080 for http, but when I try to log in and
          switch to <br>
          https on admin portal there is nothing listening out there and
          I get <br>
          "Page cannot be displayed".<br>
        </blockquote>
        How do you try to reconfigure it? What commands do you run? Or
        what files do you edit?<br>
        <blockquote id="DWT390" style="border-left: 2px solid rgb(16,
          16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0,
          0, 0); font-weight: normal; font-style: normal;
          text-decoration: none; font-family:
          Helvetica,Arial,sans-serif; font-size: 12pt;">If we cannot
          consider migration, would it be sufficient to insert the <br>
          dump from the 3.1 into 3.2 current alpha release ?</blockquote>
        As I said above we don't know what you mean by migration.<br>
        <br>
        -- <br>
        <div><span name="x"></span><font style="font-weight: bold;"
            size="3"><a moz-do-not-send="true" style="color: rgb(0, 0,
              0);" href="http://www.btactic.com/"><span id="DWT100"><font
                  class="Apple-style-span" face="verdana, helvetica,
                  sans-serif"><span class="Apple-style-span"
                    style="background-color: rgb(255, 255, 255);"></span></font></span></a></font><font
            style="font-family: 'Times New Roman';" color="#5f5f5f"
            face="Arial" size="1"><font size="3"><span
                style="font-family: verdana,helvetica,sans-serif; color:
                rgb(0, 0, 0);"><font style="font-family: helvetica;"
                  size="2"><strong>Adrián Gibanel</strong><br>
                  I.T. Manager<br>
                  <br>
                  +34 675 683 301<br>
                  <a moz-do-not-send="true" href="http://btactic.com/">www.btactic.com</a></font><br>
                <br>
              </span></font></font><font color="#008000" face="Arial"
            size="1"><img moz-do-not-send="true"
              src="http://www.btactic.com/signaturabtacticmail/btacticsignature.png"
              style="border-width: 0px;"><br>
          </font><font class="Apple-style-span" face="Arial"><b><span
                class="Apple-style-span" style="font-family: Verdana;
                font-weight: normal;"><span
                  id="bc4bed34-88ab-466b-a731-c40f5c09ab6c"><font
                    color="#5f5f5f" face="Arial" size="1"><br>
                    Ens podeu seguir a/Nos podeis seguir en:<br>
                    <br>
                  </font></span><a moz-do-not-send="true"
href="http://www.facebook.com/pages/btactic/118651634826400?v=app_9953271133"><img
                    moz-do-not-send="true" style="border: 0pt none;"
src="http://www.btactic.com/wp-content/themes/btactic/img/facebookfoot.jpg"></a>
                i <a moz-do-not-send="true"
                  href="http://twitter.com/btactic"><img
                    moz-do-not-send="true" style="border: 0pt none;"
src="http://www.btactic.com/wp-content/themes/btactic/img/twitterfoot.jpg"></a></span></b></font><br>
          <font color="#008000" face="Arial" size="1"><br>
          </font>
          <div><font color="#008000" face="Arial" size="1">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. </font><font color="#5f5f5f"
              face="Arial" size="1"><br>
              <br>
              AVIS: <br>
              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 <span class="Object" id="OBJ_PREFIX_DWT103">al
                remitent
                i que procediu a destruir el missatge</span>.<br>
              <br>
              AVISO:<br>
              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
              <span class="Object" id="OBJ_PREFIX_DWT104">al remitente y
                que procedan a destruir el mensaje</span>.</font>
          </div>
          <span name="x"></span><br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
    </blockquote>
    <br>
  </body>
</html>

--------------080509060906050806010200--