Hi Itamar,

yep i expected some problems, but i didnt plan to mix rhev-h and ovirt-nodes in within the same cluster. as long as i dont have to expect to break other clusters i whould give it a try. subscriptions for the lab/staging are nonsense in that case, just not needed. and a 2nd management node, based on ovirt is also overkill.

lets see if its killing my petsĀ 


On Fri, Nov 1, 2013 at 12:35 AM, Itamar Heim <iheim@redhat.com> wrote:
On 10/31/2013 12:02 AM, squadra wrote:

i run a fully subscribed rhev 3.2 cluster, meaning rhev-m + rhev-h
nodes. but, as most or all of you might understand it whould be wishable
to use the free opensourced version for a extra pair of hostsystems
which will be used as lab / testing envirement before live deploy of our

so, anyone got experienice in compatibility of ovirt-node images and
rhev-m (3.2 in my case). does this simply work?




Sent from the Delta quadrant using Borg technology!

Users mailing list

rhev-m makes assumptions on the compatibility level. not all rhev versions are 1:1 with ovirt version as some features get disabled or backported to rhev.
I wouldn't recommend mixing the two together.

Sent from the Delta quadrant using Borg technology!