[Users] oVirt or RHEV ?

Fri Feb 7 22:58:48 UTC 2014

Hi Nathanaël,

Imho you need a lot of manpower to make this happen.

You have to remove all Red Hat trademarks if you want to distribute it - 
this means remove it from RHEV-manager (engine), RHEV-H (node-image) and 
all Windows tools (e.g. USB policy editor, RHEV tools,...) so you not 
only need CentOS 6 build servers, but also Windows ones.

Next you should have to support each release for 3 years which means in 
2 years you maybe have to build packages for 3-6 RHEV releases - again 
takes a lot of time. Even if you can automate fetching, building and 
testing you still have to test it manually, too.

I'm unsure if someone would do this work. Just speaking for me and the 
company I work for - RHEV and oVirt is working fine for us, so I 
wouldn't see much benefit of repackaging RHEV. Contributing to oVirt 
project with Nagios plugins, presentations, meetups,... makes more sense 
for us. Again just speaking about us, but I think other companies think 
in a same way...

Regards,
René

On 07.02.2014 10:33, Nathanaël Blanchet wrote:
> Hi everybody,
>
> We could consider a third way : why not building RHEV from SRPMs since 
> redhat provides them on ftp://ftp.redhat.com/redhat/rhev-m/3.x/SRPMS/ 
> ? this can be a compromise between stability of rhev and ovirt free of 
> charge.
> I'm surprised that nobody has got this idea before.
>
> Le 06/02/2014 19:53, René Koch a écrit :
>> Hi Martijn,
>>
>> That's a good question and not too easy to answer.
>> I work as a Solution Architect and my company is selling both - RHEV and
>> oVirt consulting and support. The reason for doing both is, that we want
>> to give users a choice which solution fits better.
>>
>> The main benefits (in my opinion) of RHEV are:
>>
>> - Support with SLAs
>> Red Hat provides support for RHEV with service levels. For oVirt you
>> have to wait until someone of the developers or community members helps
>> you on the mailing list or in IRC (or you buy support from a company
>> with provides it).
>>
>> - Updates for each release for 3 years
>> You receive for all releases (RHEV 3.1, 3.2,...) 3 years of support and
>> updates. oVirt provides bugfix releases for the actual release (so you
>> want get bugfix updates for 3.2 anymore, you have to upgrade to 3.3).
>> For me this is the biggest advantage of RHEV.
>>
>> - Red Hat Knowledge Base
>> Red Hat Knowledge Base is one of the best knowledge bases and it helps
>> you greatly solving issues and gives useful tips. I use the knowledge
>> base a lot and wouldn't want to miss it for any Red Hat product.
>>
>> - Stability
>> RHEV is tested by a qa team and the releases are really stable. oVirt
>> has newer features which are less tested. I upgrade oVirt release only
>> to .1 releases (e.g. 3.2.x -> 3.3.1), not to .0 to avoid issues.
>>
>> - Guest agents
>> Guest agents and RHEV tools are packaged for RHEL and Windows guests and
>> are working fine. When using oVirt you miss some of the functionality of
>> Windows guest tools or have to copy it from different locations. For
>> other os'es it doesn't matter if using RHEV or oVirt.
>>
>> - Application / os support
>> You should consider if your applications and operating systems are
>> supported in oVirt as well. All apps certified for RHEL are certified
>> for RHEV as well.
>>
>>
>> Main benefits of oVirt:
>>
>> - Newest features
>> oVirt gives you the latest and greatest. So it will take some time until
>> this feature is available in RHEV, too (due to testing).
>>
>> - No subscription coasts
>> You don't have to buy subscriptions for an oVirt environment, so it
>> saves money. But on the other hand it can also cost you more money, if
>> you have to spend a lot of time in troubleshooting or with upgrading
>> (especially with possible upgrading issues) or having down times of your
>> environment.
>>
>>
>> It's not too easy to say if you should use RHEV or oVirt.
>> I hope I could help you making a decision with my explanations above.
>> You could also have both - a RHEV setup for production vms and an oVirt
>> setup for development and qa vms.
>>
>>
>> Regards,
>> René
>>
>>
>>
>> On Thu, 2014-02-06 at 16:06 +0100, Martijn Grendelman wrote:
>>> Hi,
>>>
>>> This may be the wrong place to ask, but I'm looking for input to form an
>>> opinion on an "oVirt or RHEV" question within my company.
>>>
>>> I have been running oVirt for about 5 months now, and I'm quite
>>> comfortable with its features and maintenance procedures. We are now
>>> planning to build a private virtualization cluster for hosting clients'
>>> applications as well as our own. Some people in the company are
>>> questioning whether we should buy RHEV, but at this point, I can't see
>>> the benefits.
>>>
>>> Can anyone on this list shed a light on when RHEV might be a better
>>> choice than oVirt? What are the benefits? The trade-offs?
>>>
>>> I am looking for pragmatic, real-world things, not marketing mumbo
>>> jumbo. That, I can get from redhat.com ;-)
>>>
>>> Best regards,
>>> Martijn.
>>> _______________________________________________
>>> Users mailing list
>>> Users at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
> -- 
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle exploitation et maintenance
> Département des systèmes d'information
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5 	
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14
> blanchet at abes.fr  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140207/06517620/attachment-0001.html>