<div class="xam_msg_class">
<div style="font: normal 13px Arial; color:rgb(31, 28, 27);"><br>
<div><span style="font-family:Arial; font-size:11px; color:#5F5F5F;">Da</span><span style="font-family:Arial; font-size:12px; color:#5F5F5F; padding-left:5px;">: arch-bounces@ovirt.org</span></div>
<div><span style="font-family:Arial; font-size:11px; color:#5F5F5F;">A</span><span style="font-family:Arial; font-size:12px; color:#5F5F5F; padding-left:5px;">: "Dan Kenigsberg" danken@redhat.com,"Adam Litke" alitke@redhat.com</span></div>
<div><span style="font-family:Arial; font-size:11px; color:#5F5F5F;">Cc</span><span style="font-family:Arial; font-size:12px; color:#5F5F5F; padding-left:5px;">: engine-devel@ovirt.org,"arch" arch@ovirt.org,"VDSM Project Development" vdsm-devel@lists.fedorahosted.org</span></div>
<div><span style="font-family:Arial; font-size:11px; color:#5F5F5F;">Data</span><span style="font-family:Arial; font-size:12px; color:#5F5F5F; padding-left:5px;">: Mon, 03 Feb 2014 08:50:12 +0100</span></div>
<div><span style="font-family:Arial; font-size:11px; color:#5F5F5F;">Oggetto</span><span style="font-family:Arial; font-size:12px; color:#5F5F5F; padding-left:5px;">: Re: mom RPMs for 3.4</span></div>
<br>
<div>> Il 01/02/2014 23:48, Dan Kenigsberg ha scritto:</div><div>> > On Fri, Jan 31, 2014 at 04:56:12PM -0500, Adam Litke wrote:</div><div>> >> On 31/01/14 08:36 +0100, Sandro Bonazzola wrote:</div><div>> >>> Il 30/01/2014 19:30, Adam Litke ha scritto:</div><div>> >>>> On 30/01/14 18:13 +0000, Dan Kenigsberg wrote:</div><div>> >>>>> On Thu, Jan 30, 2014 at 11:49:42AM -0500, Adam Litke wrote:</div><div>> >>>>>> Hi Sandro,</div><div>> >>>>>></div><div>> >>>>>> After updating the MOM project's build system, I have used jenkins to</div><div>> >>>>>> produce a set of RPMs that I would like to tag into the oVirt 3.4</div><div>> >>>>>> release. Please see the jenkins job [1] for the relevant artifacts</div><div>> >>>>>> for EL6[2], F19[3], and F20[4].</div><div>> >>>>>></div><div>> >>>>>> Dan, should I submit a patch to vdsm to make it require mom >= 0.4.0?</div><div>> >>>>>> I want to be careful to not break people's environments this late in</div><div>> >>>>>> the 3.4 release cycle. What is the best way to minimize that damage?</div><div>> >>>>></div><div>> >>>>> Hey, we're during beta. I prefer making this requirement explicit now</div><div>> >>>>> over having users with supervdsmd.log retate due to log spam.</div><div>> >>>></div><div>> >>>> In that case, Sandro, can you let me know when those RPMs hit the</div><div>> >>>> ovirt repos (for master and 3.4) and then I will submit a patch to</div><div>> >>>> vdsm to require the new version.</div><div>> >>></div><div>> >>></div><div>> >>> mom 0.4.0 has been built in last night nightly job [1] and published to nightly by publisher job [2]</div><div>> >>> so it's already available on nightly [3]</div><div>> >>></div><div>> >>> For 3.4.0, it has been planned [4] a beta 2 release on 2014-02-06 so we'll include your builds in that release.</div><div>> >></div><div>> >> I presume the scripting for 3.4 release rpms will produce a version</div><div>> >> without the git-rev based suffix: ie. mom-0.4.0-1.rpm?</div><div>> >></div><div>> >> I need to figure out how to handle a problem that might be a bit</div><div>> >> unique to mom. MOM is used by non-oVirt users who install it from the</div><div>> >> main Fedora repository. I think it's fine that we are producing our</div><div>> >> own rpms in oVirt (that may have additional patches applied and may</div><div>> >> resync to upstream mom code more frequently than would be desired for</div><div>> >> the main Fedora repository). Given this, I think it makes sense to</div><div>> >> tag the oVirt RPMs with a special version suffix to indicate that</div><div>> >> these are oVirt produced and not upstream Fedora.</div><div>> >></div><div>> >> For example:</div><div>> >> The next Fedora update will be mom-0.4.0-1.f20.rpm.</div><div>> >> The next oVirt update will be mom-0.4.0-1ovirt.f20.rpm.</div><div>> >></div><div>> >> Is this the best practice for accomplishing my goals? One other thing</div><div>> >> I'd like to have the option of doing is to make vdsm depend on an</div><div>> >> ovirt distribution of mom so that the upstream Fedora version will not</div><div>> >> satisfy the dependency for vdsm.</div><div>> > </div><div>> > What is the motivation for this? You would not like to bother Fedora</div><div>> > users with updates that are required only for oVirt?</div><div>> > </div><div>> > Vdsm itself is built, signed, and distributed via Fedora.</div><div>> > It is also copied into the ovirt repo, for completeness sake. Could MoM</div><div>> > do the same?</div><div>> </div><div>> IMHO, if we're distributing mom and vdsm rpms through Fedora yum repository we should not duplicate it on ovirt yum repository.</div><div>> Fedora package is signed and will differ from the one we're shipping within ovirt repo (which is unsigned)</div><div>> We should provide on resource.ovirt.org only packages not available on "downstream" repositories (like nightly builds).<br><br>why you can't sign your rpms???<br><br>on ovirt web page http://www.ovirt.org/Home you can change:<br><br>Enhanced security: SELinux and Mandatory Access Control for VMs and hypervisor <br><br>with:<br><br>Enhanced security: SELinux and Mandatory Access Control for VMs and hypervisor (but not signed rpms)<br><br>best regards<br>a<br><br></div><div>> </div><div>> </div><div>> > </div><div>> > Dan.</div><div>> > </div><div>> </div><div>> </div><div>> -- </div><div>> Sandro Bonazzola</div><div>> Better technology. Faster innovation. Powered by community collaboration.</div><div>> See how it works at redhat.com</div><div>> _______________________________________________</div><div>> Arch mailing list</div><div>> Arch@ovirt.org</div><div>> http://lists.ovirt.org/mailman/listinfo/arch</div></div>
</div>