Re: [ovirt-users] Some questions

It depends on the supportedENGINEs which getVdsCaps will return. Generally, VDSM for 3.x should keep supporting its 3.x previous minor versions. Regards, Maor ----- Original Message ----- From: "David cano bailen" <davidcano92@gmail.com> To: "Maor Lipchuk" <mlipchuk@redhat.com> Sent: Thursday, August 14, 2014 6:02:17 PM Subject: Re: [ovirt-users] Some questions hi, my concern is that we have some critical MV. If the node enters into non -operational state after upgrading the engine. Will be machines up? I've been searching and upgrading should be progressive, 3.0 to 3.1, 3.1 to 3.2 .... I guess if the nodes VDSM update to the latest version, and later I'll update the engine version by version nodes wouldnt enter on non-operational state and not suffer any court in MV. Am I right? Thank you very much for your help 2014-08-14 11:10 GMT+02:00 Maor Lipchuk <mlipchuk@redhat.com>:
Hi David,
See my answers inline
Regards, Maor
From: "David cano bailen" <davidcano92@gmail.com> To: users@ovirt.org Sent: Wednesday, August 13, 2014 2:04:10 PM Subject: [ovirt-users] Some questions
Hi, i installed Engine 3.0 and Node Ovirt 2.6, but it seems very unestable. Sometimes machines doesnt starts, nodes doesnt vinculate or UI doesnt work fine. I have only 2 nodes and storage its on the same physical machine
----- Original Message ----- than
engine.
-¿Does Node Ovirt 3.4 work with Engine 3.0? Engine 3.0 should support backward compatibility for ovirt 3.4. You can verify that on the node be executing the following command : "vdsClient -s 0 getVdsCaps" (-s for secure), There, you should see a supportedENGINEs list. -¿Its necessary shutdown Nodes to do engine upgrade? no, but take in consideration that after upgrade, those hosts might get into non-operational state, in case VDSM version should be upgraded also. -¿Are there any problem having the same physical machine for engine and storage? ¿what are advantages have on diferents machines? There is no limitation of doing that, it's simply a question of the architecture you want to support. Separating the engine from the Storage server, might be useful to make it more high available.
Thank you
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

this is not true for vdsm 4.14. on ovirt-engine 3.3.z see this bugzilla entry: https://bugzilla.redhat.com/show_bug.cgi?id=1120267 Am 14.08.2014 17:51, schrieb Maor Lipchuk:
It depends on the supportedENGINEs which getVdsCaps will return. Generally, VDSM for 3.x should keep supporting its 3.x previous minor versions.
Regards, Maor
-- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
participants (2)
-
Maor Lipchuk
-
Sven Kieske