Upgrade order 3.4.2 -> 3.5.x
------=_NextPartTM-000-7af25c18-adea-4864-b1e3-aaff2cd6666a Content-Type: multipart/alternative; boundary="_000_12EF8D94C6F8734FB2FF37B9FBEDD1735F8B59C6EXCHANGEcollogi_" --_000_12EF8D94C6F8734FB2FF37B9FBEDD1735F8B59C6EXCHANGEcollogi_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, maybe a stupid one. Just want to make sure that nothing goes wrong. We plan to make a rolling upgrade of our landscape going to 3.5.1 in december. So we always need some hypervisor nodes up and running during the process. Looking at older posts I assume that upgrading the engine should be sufficient, while hypervisor nodes with vdsm 4.14.17 (from 3.4 repos) and the active VMs keep on running. The start of the engine after the upgrade should catch up and resync all states. Afterwards I clean hypervisor hosts one by one and clean/reinstall it into the cluster? Thanks in advance. Markus --_000_12EF8D94C6F8734FB2FF37B9FBEDD1735F8B59C6EXCHANGEcollogi_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html dir=3D"ltr"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style type=3D"text/css" id=3D"owaParaStyle"></style> </head> <body fpstyle=3D"1" ocsi=3D"0"> <div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: = 10pt;">Hi, <div><br> </div> <div>maybe a stupid one. Just want to make sure that nothing goes wrong. We= </div> <div>plan to make a rolling <span style=3D"font-size: 10pt;">upgrade of our= </span><span style=3D"font-size: 10pt;">landscape going to 3.5.1 in d= ecember. </span></div> <div><span style=3D"font-size: 10pt;">S</span><span style=3D"font-size: 10p= t;">o we always need </span><span style=3D"font-size: 10pt;">some hype= rvisor nodes up and running during the </span></div> <div><span style=3D"font-size: 10pt;">process. </span></div> <div><br> </div> <div>Looking at older posts I assume that upgrading the engine should be</d= iv> <div>sufficient, while hypervisor nodes with vdsm 4.14.17 (from 3.4 repos) = and</div> <div>the active VMs <span style=3D"font-size: 10pt;">keep on running. = The start of the engine after the upgrade</span></div> <div><span style=3D"font-size: 10pt;">should catch up and </span><span= style=3D"font-size: 10pt;">resync all </span><span style=3D"font-size= : 10pt;">states.</span></div> <div><br> </div> <div>Afterwards I clean hypervisor hosts one by one and clean/reinstall it = into </div> <div>the <span style=3D"font-size: 10pt;">cluster?</span></div> <div><br> </div> <div>Thanks in advance.</div> <div><br> </div> <div>Markus</div> <div><br> </div> <div><br> </div> </div> </body> </html> --_000_12EF8D94C6F8734FB2FF37B9FBEDD1735F8B59C6EXCHANGEcollogi_-- ------=_NextPartTM-000-7af25c18-adea-4864-b1e3-aaff2cd6666a Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" **************************************************************************** Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Über das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 **************************************************************************** ------=_NextPartTM-000-7af25c18-adea-4864-b1e3-aaff2cd6666a--
Hello! What kind of storage domains do you have? On Fri, Oct 31, 2014 at 1:02 PM, Markus Stockhausen <stockhausen@collogia.de
wrote:
Hi,
maybe a stupid one. Just want to make sure that nothing goes wrong. We plan to make a rolling upgrade of our landscape going to 3.5.1 in december. So we always need some hypervisor nodes up and running during the process.
Looking at older posts I assume that upgrading the engine should be sufficient, while hypervisor nodes with vdsm 4.14.17 (from 3.4 repos) and the active VMs keep on running. The start of the engine after the upgrade should catch up and resync all states.
Afterwards I clean hypervisor hosts one by one and clean/reinstall it into the cluster?
Thanks in advance.
Markus
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
------=_NextPartTM-000-a31987f4-cc0d-411b-9735-f0756ed95b6a Content-Type: multipart/alternative; boundary="_000_12EF8D94C6F8734FB2FF37B9FBEDD1735F8B59F2EXCHANGEcollogi_" --_000_12EF8D94C6F8734FB2FF37B9FBEDD1735F8B59F2EXCHANGEcollogi_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, sorry I forgot that: NFS, engine is running in a qemu VM "outside" the clus= ter. Markus ________________________________ Von: Gabi C [gabicr@gmail.com] Gesendet: Freitag, 31. Oktober 2014 12:12 An: Markus Stockhausen Cc: ovirt-users Betreff: Re: [ovirt-users] Upgrade order 3.4.2 -> 3.5.x Hello! What kind of storage domains do you have? On Fri, Oct 31, 2014 at 1:02 PM, Markus Stockhausen <stockhausen@collogia.d= e<mailto:stockhausen@collogia.de>> wrote: Hi, maybe a stupid one. Just want to make sure that nothing goes wrong. We plan to make a rolling upgrade of our landscape going to 3.5.1 in december. So we always need some hypervisor nodes up and running during the process. Looking at older posts I assume that upgrading the engine should be sufficient, while hypervisor nodes with vdsm 4.14.17 (from 3.4 repos) and the active VMs keep on running. The start of the engine after the upgrade should catch up and resync all states. Afterwards I clean hypervisor hosts one by one and clean/reinstall it into the cluster? Thanks in advance. Markus _______________________________________________ Users mailing list Users@ovirt.org<mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users --_000_12EF8D94C6F8734FB2FF37B9FBEDD1735F8B59F2EXCHANGEcollogi_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html dir=3D"ltr"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style type=3D"text/css" id=3D"owaParaStyle"></style> </head> <body fpstyle=3D"1" ocsi=3D"0"> <div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: = 10pt;"> <div>Hi,</div> <div><br> </div> <div>sorry I forgot that: <span style=3D"font-size: 10pt;">NFS, engine= is running in a qemu VM "outside" the cluster.</span></div> <div><span style=3D"font-size: 10pt;"><br> </span></div> <div>Markus<br> <div style=3D"font-family: Times New Roman; color: #000000; font-size: 16px= "> <hr tabindex=3D"-1"> <div id=3D"divRpF270225" style=3D"direction: ltr;"><font face=3D"Tahoma" si= ze=3D"2" color=3D"#000000"><b>Von:</b> Gabi C [gabicr@gmail.com]<br> <b>Gesendet:</b> Freitag, 31. Oktober 2014 12:12<br> <b>An:</b> Markus Stockhausen<br> <b>Cc:</b> ovirt-users<br> <b>Betreff:</b> Re: [ovirt-users] Upgrade order 3.4.2 -> 3.5.x<br> </font><br> </div> <div></div> <div> <div dir=3D"ltr"> <div>Hello!<br> <br> </div> What kind of storage domains do you have?<br> </div> <div class=3D"gmail_extra"><br> <div class=3D"gmail_quote">On Fri, Oct 31, 2014 at 1:02 PM, Markus Stockhau= sen <span dir=3D"ltr"> <<a href=3D"mailto:stockhausen@collogia.de" target=3D"_blank">stockhause= n@collogia.de</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1= px #ccc solid; padding-left:1ex"> <div> <div style=3D"direction:ltr; font-family:Tahoma; color:#000000; font-size:1= 0pt">Hi, <div><br> </div> <div>maybe a stupid one. Just want to make sure that nothing goes wrong. We= </div> <div>plan to make a rolling <span style=3D"font-size:10pt">upgrade of our&n= bsp;</span><span style=3D"font-size:10pt">landscape going to 3.5.1 in decem= ber. </span></div> <div><span style=3D"font-size:10pt">S</span><span style=3D"font-size:10pt">= o we always need </span><span style=3D"font-size:10pt">some hypervisor= nodes up and running during the </span></div> <div><span style=3D"font-size:10pt">process. </span></div> <div><br> </div> <div>Looking at older posts I assume that upgrading the engine should be</d= iv> <div>sufficient, while hypervisor nodes with vdsm 4.14.17 (from 3.4 repos) = and</div> <div>the active VMs <span style=3D"font-size:10pt">keep on running. Th= e start of the engine after the upgrade</span></div> <div><span style=3D"font-size:10pt">should catch up and </span><span s= tyle=3D"font-size:10pt">resync all </span><span style=3D"font-size:10p= t">states.</span></div> <div><br> </div> <div>Afterwards I clean hypervisor hosts one by one and clean/reinstall it = into </div> <div>the <span style=3D"font-size:10pt">cluster?</span></div> <div><br> </div> <div>Thanks in advance.</div> <span class=3D"HOEnZb"><font color=3D"#888888"> <div><br> </div> <div>Markus</div> <div><br> </div> <div><br> </div> </font></span></div> </div> <br> _______________________________________________<br> Users mailing list<br> <a href=3D"mailto:Users@ovirt.org" target=3D"_blank">Users@ovirt.org</a><br=
<a href=3D"http://lists.ovirt.org/mailman/listinfo/users" target=3D"_blank"=
http://lists.ovirt.org/mailman/listinfo/users</a><br> <br> </blockquote> </div> <br> </div> </div> </div> </div> </div> </body> </html>
--_000_12EF8D94C6F8734FB2FF37B9FBEDD1735F8B59F2EXCHANGEcollogi_-- ------=_NextPartTM-000-a31987f4-cc0d-411b-9735-f0756ed95b6a Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" **************************************************************************** Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Über das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 **************************************************************************** ------=_NextPartTM-000-a31987f4-cc0d-411b-9735-f0756ed95b6a--
Hello! I was asking because I use my 3 hypervisor also as providers of glusterfs bricks (replicate) and I have some issue when I upgraded Hypervisor (think about glusterfs packages and vdsm-gluster). In your configuration you you shouldn't have any problems if you do it as per your e-mail. On Fri, Oct 31, 2014 at 1:17 PM, Markus Stockhausen <stockhausen@collogia.de
wrote:
Hi,
sorry I forgot that: NFS, engine is running in a qemu VM "outside" the cluster.
Markus ------------------------------ *Von:* Gabi C [gabicr@gmail.com] *Gesendet:* Freitag, 31. Oktober 2014 12:12 *An:* Markus Stockhausen *Cc:* ovirt-users *Betreff:* Re: [ovirt-users] Upgrade order 3.4.2 -> 3.5.x
Hello!
What kind of storage domains do you have?
On Fri, Oct 31, 2014 at 1:02 PM, Markus Stockhausen < stockhausen@collogia.de> wrote:
Hi,
maybe a stupid one. Just want to make sure that nothing goes wrong. We plan to make a rolling upgrade of our landscape going to 3.5.1 in december. So we always need some hypervisor nodes up and running during the process.
Looking at older posts I assume that upgrading the engine should be sufficient, while hypervisor nodes with vdsm 4.14.17 (from 3.4 repos) and the active VMs keep on running. The start of the engine after the upgrade should catch up and resync all states.
Afterwards I clean hypervisor hosts one by one and clean/reinstall it into the cluster?
Thanks in advance.
Markus
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi,
maybe a stupid one. Just want to make sure that nothing goes wrong. We plan to make a rolling upgrade of our landscape going to 3.5.1 in december. So we always need some hypervisor nodes up and running during the process. This went fairly well with me. I did not loose a single machine and the
On 31.10.2014 12:02, Markus Stockhausen wrote: process was transparent for them (I even had a script running lots of queries against a web server in one vm).
Looking at older posts I assume that upgrading the engine should be sufficient, while hypervisor nodes with vdsm 4.14.17 (from 3.4 repos) and the active VMs keep on running. The start of the engine after the upgrade should catch up and resync all states.
The Engine and VDSM are fully backward compatible to each other [1]. So you should not see any problems there; only missing some features maybe.
Afterwards I clean hypervisor hosts one by one and clean/reinstall it into the cluster?
This what I have done; remember you need to add the 3.5 repos otherwise VDSM will be (re)installed from the latest 3.4 repos and not upgraded to the '3.5' version. Also, this process went like a charm without any issues (let alone loosing guest)
Thanks in advance.
Please keep in mind, upgrading your datacenter(s) to 3.5 might lead to some issues, some of them already fixed for 3.5.1 (I had some more severe ones). I would be careful with this setting in a production env. Also, some featues are available on cluster versions only; not requiring the more invasive datacenter upgrade [2]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1154620#c3 [2] http://www.mail-archive.com/users@ovirt.org/msg22249.html -- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767
On Fri, Oct 31, 2014 at 12:54 PM, Daniel Helgenberger < daniel.helgenberger@m-box.de> wrote:
Afterwards I clean hypervisor hosts one by one and clean/reinstall it into the cluster? This what I have done; remember you need to add the 3.5 repos otherwise VDSM will be (re)installed from the latest 3.4 repos and not upgraded to the '3.5' version. Also, this process went like a charm without any issues (let alone loosing guest)
One question related to host reinstall vs "yum update vdsm*" comes into my mind now.. On one of my all-in-one environments, which started from 3.0 days and now is at 3.5 through progressive updates, I recently noticed some *.rpmnew packages related to both engine and vdsm components. I always updated the host part through "yum update" on this all-in-one server. This situation forced me to compare running .conf file vs .rpmnew ones and to clean then the situation. The question is: in general when you run "reinstall host" from engine gui, does this process run a "yum update" and so you should care about possible change in .conf files format, or does it go through uninstall/install? Thanks Gianluca
On 10/31/2014 04:01 PM, Gianluca Cecchi wrote:
On Fri, Oct 31, 2014 at 12:54 PM, Daniel Helgenberger <daniel.helgenberger@m-box.de <mailto:daniel.helgenberger@m-box.de>> wrote:
> Afterwards I clean hypervisor hosts one by one and clean/reinstall it into > the cluster? This what I have done; remember you need to add the 3.5 repos otherwise VDSM will be (re)installed from the latest 3.4 repos and not upgraded to the '3.5' version. Also, this process went like a charm without any issues (let alone loosing guest) >
One question related to host reinstall vs "yum update vdsm*" comes into my mind now..
On one of my all-in-one environments, which started from 3.0 days and now is at 3.5 through progressive updates, I recently noticed some *.rpmnew packages related to both engine and vdsm components. I always updated the host part through "yum update" on this all-in-one server. This situation forced me to compare running .conf file vs .rpmnew ones and to clean then the situation.
The question is: in general when you run "reinstall host" from engine gui, does this process run a "yum update" and so you should care about possible change in .conf files format, or does it go through uninstall/install?
yum update
participants (5)
-
Daniel Helgenberger -
Gabi C -
Gianluca Cecchi -
Itamar Heim -
Markus Stockhausen