------=_Part_1917943_185222171.1391852636417 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable ----- Mail transf=C3=A9r=C3=A9 ----- De: "Nathana=C3=ABl Blanchet" <blanchet(a)abes.fr&gt;=20 =C3=80: "Ren=C3=A9 Koch" <rkoch(a)linuxland.at&gt;=20 Envoy=C3=A9: Samedi 8 F=C3=A9vrier 2014 10:41:56=20 Objet: Re: [Users] oVirt or RHEV ?=20 Hi Ren=C3=A9, thanks for your answer.=20 My first idea wasn't to redistribute a repackaging of RHEV, but to bring a = more stable build of rhev than the one from ovirt. My idea was to do the sa= me as other project such as centos or scientific linux with RHEL. Yes they = have removed all Red Hat trademarks, it seems to be a hard work. I began ye= sterday, I met a lot of dependance issues, you're right I can't waste such = a time with this kind of work alone, a collaborate work would be better, bu= t unuseful because of the ovirt project. That's why I think centos make a v= ery great job.=20 ----- Mail transf=C3=A9r=C3=A9 ----- De: "Ren=C3=A9 Koch" <rkoch(a)linuxland.at&gt;=20 =C3=80: "Nathana=C3=ABl Blanchet" <blanchet(a)abes.fr&gt;, "Martijn Grendelman" = <martijn.grendelman(a)isaac.nl&gt;=20 Cc: users(a)ovirt.org=20 Envoy=C3=A9: Vendredi 7 F=C3=A9vrier 2014 23:58:48=20 Objet: Re: [Users] oVirt or RHEV ?=20 Hi Nathana=C3=ABl,=20 Imho you need a lot of manpower to make this happen.=20 You have to remove all Red Hat trademarks if you want to distribute it - th= is 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.=20 Next you should have to support each release for 3 years which means in 2 y= ears 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 s= till have to test it manually, too.=20 I'm unsure if someone would do this work. Just speaking for me and the comp= any I work for - RHEV and oVirt is working fine for us, so I wouldn't see m= uch benefit of repackaging RHEV. Contributing to oVirt project with Nagios = plugins, presentations, meetups,... makes more sense for us. Again just spe= aking about us, but I think other companies think in a same way...=20 Regards,=20 Ren=C3=A9=20 On 07.02.2014 10:33, Nathana=C3=ABl Blanchet wrote:=20 Hi everybody,=20 We could consider a third way : why not building RHEV from SRPMs since redh= at provides them on ftp://ftp.redhat.com/redhat/rhev-m/3.x/SRPMS/ ? this ca= n be a compromise between stability of rhev and ovirt free of charge.=20 I'm surprised that nobody has got this idea before.=20 Le 06/02/2014 19:53, Ren=C3=A9 Koch a =C3=A9crit :=20 <blockquote> 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=C3=A9 On Thu, 2014-02-06 at 16:06 +0100, Martijn Grendelman wrote:=20 <blockquote> 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(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/= users=20 _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/= users=20 </blockquote> --=20 Nathana=C3=ABl Blanchet Supervision r=C3=A9seau P=C3=B4le exploitation et maintenance D=C3=A9partement des syst=C3=A8mes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 =09 T=C3=A9l. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr=20 </blockquote> ------=_Part_1917943_185222171.1391852636417 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><style type=3D'text/css'>p { margin: 0; }</style></head><body><= div style=3D'font-family: times new roman,new york,times,serif; font-size: = 12pt; color: #000000'><br><br><hr id=3D"zwchr"><div style=3D"color:#000;fon= t-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetic= a,Arial,sans-serif;font-size:12pt;"><b>De: </b>"Nathana=C3=ABl Blanchet" &l= t;blanchet(a)abes.fr&amp;gt;&lt;br&gt;&lt;b&gt;=C3=80: </b>"Ren=C3=A9 Koch" &lt;rkoch@linuxla= nd.at&gt;<br><b>Envoy=C3=A9: </b>Samedi 8 F=C3=A9vrier 2014 10:41:56<br><b>= Objet: </b>Re: [Users] oVirt or RHEV ?<br><br><style>p { margin: 0; }</styl= e><div style=3D"font-family: times new roman,new york,times,serif; font-siz= e: 12pt; color: #000000">Hi Ren=C3=A9, thanks for your answer.<br>My first = idea wasn't to redistribute a repackaging of RHEV, but to bring a more stab= le build of rhev than the one from ovirt. My idea was to do the same as oth= er project such as centos or scientific linux with RHEL. Yes they have remo= ved all Red Hat trademarks, it seems to be a hard work. I began yesterday, = I met a lot of dependance issues, you're right I can't waste such a time wi= th this kind of work alone, a collaborate work would be better, but unusefu= l because of the ovirt project. That's why I think centos make a very great= job.<br><br><hr id=3D"zwchr"><div style=3D"color:#000;font-weight:normal;f= ont-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-seri= f;font-size:12pt;"><b>De: </b>"Ren=C3=A9 Koch" &amp;lt;rkoch(a)linuxland.at&amp;gt;&lt;b= r><b>=C3=80: </b>"Nathana=C3=ABl Blanchet" &amp;lt;blanchet(a)abes.fr&amp;gt;, "Marti= jn Grendelman" &amp;lt;martijn.grendelman(a)isaac.nl&amp;gt;&lt;br&gt;&lt;b&gt;Cc: </b>users@ovir= t.org<br><b>Envoy=C3=A9: </b>Vendredi 7 F=C3=A9vrier 2014 23:58:48<br><b>Ob= jet: </b>Re: [Users] oVirt or RHEV ?<br><br> =20 =20 =20 =20 Hi Nathana=C3=ABl,<br> <br> Imho you need a lot of manpower to make this happen.<br> <br> 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.<br> <br> 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.<br> <br> 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...<br> <br> <br> Regards,<br> Ren=C3=A9<br> <br> <br> <div class=3D"moz-cite-prefix">On 07.02.2014 10:33, Nathana=C3=ABl Blan= chet wrote:<br> </div> <blockquote cite=3D"mid:52F4A868.7040901@abes.fr"> =20 <font size=3D"-1">Hi everybody, <br> <br> We could consider a third way : why not building RHEV from SRPMs since redhat provides them on <a class=3D"moz-txt-link-freetext" hr= ef=3D"ftp://ftp.redhat.com/redhat/rhev-m/3.x/SRPMS/" target=3D"_blank">ftp:= //ftp.redhat.com/redhat/rhev-m/3.x/SRPMS/</a> ? this can be a compromise between stability of rhev and ovirt free of charge.<br> I'm surprised that nobody has got this idea before.<br> <br> </font> <div class=3D"moz-cite-prefix">Le 06/02/2014 19:53, Ren=C3=A9 Koch a =C3=A9crit&nbsp;:<br> </div> <blockquote cite=3D"mid:20140206185356.EDA1C1682@mail.linuxland.de"> <pre>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 -&gt; 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=C3=A9 On Thu, 2014-02-06 at 16:06 +0100, Martijn Grendelman wrote: </pre> <blockquote> <pre>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 <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Users@ovirt.org" targe= t=3D&quot;_blank&quot;&gt;Users(a)ovirt.org&lt;/a&gt; <a class=3D"moz-txt-link-freetext" href=3D"http://lists.ovirt.org/mailman/l= istinfo/users" target=3D"_blank">http://lists.ovirt.org/mailman/listinfo/us= ers</a> </pre> </blockquote> <pre>_______________________________________________ Users mailing list <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Users@ovirt.org" targe= t=3D&quot;_blank&quot;&gt;Users(a)ovirt.org&lt;/a&gt; <a class=3D"moz-txt-link-freetext" href=3D"http://lists.ovirt.org/mailman/l= istinfo/users" target=3D"_blank">http://lists.ovirt.org/mailman/listinfo/us= ers</a> </pre> </blockquote> <br> <pre class=3D"moz-signature">--=20 Nathana=C3=ABl Blanchet Supervision r=C3=A9seau P=C3=B4le exploitation et maintenance D=C3=A9partement des syst=C3=A8mes d'information 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 =09 T=C3=A9l. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:blanchet@abes.fr" targ= et=3D&quot;_blank&quot;&gt;blanchet(a)abes.fr&lt;/a&gt; </pre> </blockquote> <br> =20 </div><br></div></div><br></div></body></html> ------=_Part_1917943_185222171.1391852636417--