On Fri, Nov 1, 2013 at 6:43 AM, Itamar Heim <iheim@redhat.com> wrote:
On 11/01/2013 02:36 AM, squadra wrote:
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

this isn't only about same cluster compatibility, rather potentially trying to use a verb which doesn't exist in ovirt-3.2 and assumed by rhev 3.2. so YMMV, a lot.
for *sure* do not try to put them in same DC, or your rhev cluster/DC may suffer.


okay, stop scaring me ! sadly its the infrastructure without our company simply said is completly down. so i wont try... but something else came to my mind. we are redhat ready partner, so for i got access to nfr subscriptions. will i get in trouble with the rh support when use nfr in lab area controlled by a regular subscription? i know, ask rh support and totally offtopic. sorry for that, but maybe someone knows or got his own experience. especially when it comes to a support case and rh wants log collection.
 


cheers,




On Fri, Nov 1, 2013 at 12:35 AM, Itamar Heim <iheim@redhat.com
<mailto:iheim@redhat.com>> wrote:

    On 10/31/2013 12:02 AM, squadra wrote:

        hi,

        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
        stuff.

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

        cheers,

        juergen

        --

        Sent from the Delta quadrant using Borg technology!



        _________________________________________________
        Users mailing list
        Users@ovirt.org <mailto:Users@ovirt.org>
        http://lists.ovirt.org/__mailman/listinfo/users

        <http://lists.ovirt.org/mailman/listinfo/users>


    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!



_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users





--
Sent from the Delta quadrant using Borg technology!