<div dir="ltr"><div>I've started a wiki page here, please feel free to flesh it out with more detail:<br></div><div><br></div><div><a href="https://wiki.openstack.org/wiki/Packaging/GenericTooling">https://wiki.openstack.org/wiki/Packaging/GenericTooling</a><br></div><div><br></div><div>Looking at the OpenStack meetings page, the schedule is very packed with Mondays being a little less loaded. How about 1500 UTC on Mondays? This clashes with Satori and Zaqar, which I hope has minimal overlap with our group. The #openstack-operators room would be an appropriate venue, but I think we should move to one of the openstack meeting channels if the first meeting proves useful and there is a desire for more. If we make our first meeting on the 7th of December, that gives us plenty of time to list discussion topics.</div><div><br></div><div>Since I'm on the wrong side of the world, would anyone like to volunteer to lead the discussion? I have created an agenda etherpad here, again feel free to add things : <a href="https://etherpad.openstack.org/p/openstack-operators-meeting-071214-agenda">https://etherpad.openstack.org/p/openstack-operators-meeting-071214-agenda</a></div><div><br></div><div>I'd like to examine each of the tools to see which requirements they don't satisfy, and what the shortest path to getting one that ticks every (reasonable) box might be.</div><div><br></div><div> - Michael</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 28, 2014 at 10:53 PM, Emrah Aslan <span dir="ltr"><<a href="mailto:e.aslan@logicom.com.tr" target="_blank">e.aslan@logicom.com.tr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Any progress on reduce the fragmentation ?<br>
<br>
Kind Regards<br>
<br>
Emrah ASLAN<br>
Cisco/Citrix System Engineer<br>
<br>
<br>
<br>
<br>
<br>
<br>
Değerli İş Ortaklarımız,<br>
Logicom kampanyaları , fırsat, duyuru ve stok bilgilerinin sizlere düzenli ulaşması için aşağıdaki linki tıklayarak e-mail adresinizi güncellemenizi rica ediyoruz.<br>
<a href="http://visitor.r20.constantcontact.com/manage/optin?v=001t9egDEMH10MEulnTu-Lzln0RXbiYIgR2HnLd_hpHmPb0K44ZxJOya0FvCOF3TI8c2qeErt1Xrn3PlZqntTSqiSTW40PTK2XQ8OlOUe4qYOE%3D" target="_blank">http://visitor.r20.constantcontact.com/manage/optin?v=001t9egDEMH10MEulnTu-Lzln0RXbiYIgR2HnLd_hpHmPb0K44ZxJOya0FvCOF3TI8c2qeErt1Xrn3PlZqntTSqiSTW40PTK2XQ8OlOUe4qYOE%3D</a><br>
<span class="im HOEnZb"><br>
-----Original Message-----<br>
From: Derek Higgins [mailto:<a href="mailto:derekh@redhat.com">derekh@redhat.com</a>]<br>
Sent: Friday, November 28, 2014 12:35 PM<br>
To: Jay Pipes; <a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a><br>
Subject: Re: [Openstack-operators] Operations project: Packaging<br>
<br>
</span><div class="HOEnZb"><div class="h5">On 27/11/14 15:06, Jay Pipes wrote:<br>
> On 11/24/2014 06:58 AM, Derek Higgins wrote:<br>
>> On 18/11/14 06:16, Michael Chapman wrote:<br>
>>> Hi all,<br>
>>><br>
>>> Packaging was one of the biggest points of interest in the Friday<br>
>>> Paris meeting, and I'd like to use this thread to have a centralised<br>
>>> discussion and/or argument regarding whether there is a packaging<br>
>>> system that is flexible enough that we can adopt it as a community<br>
>>> and reduce the fragmentation. This conversation began in Paris, but<br>
>>> will likely continue for some time.<br>
>>><br>
>>> The Friday session indicates that as operators we have common<br>
>>> requirements:<br>
>>><br>
>>> A system that takes the sources from upstream projects and produces<br>
>>> artifacts (packages or images).<br>
>>><br>
>>> There are numerous projects that have attempted to solve this problem.<br>
>>> Some are on stackforge, some live outside. If you are an author or a<br>
>>> user of one of these systems, please give your opinion.<br>
>><br>
>> To throw another project into the mix, I've been working on building<br>
>> master packages with delorean[1] for a last few months(currently<br>
>> building for fedora but planning on adding more), the specs being<br>
>> uses are based off the RDO packaging.<br>
>><br>
>> The plan we're slowly working towards will be to allow this packaging<br>
>> hopefully become the upstream of the RDO packaging for the released<br>
>> projects. We're also hoping to allow contributions from the whole RDO<br>
>> community via gerrithub [2].<br>
>><br>
>> If anybody is interested the packaging we are maintaining is on<br>
>> github[3], with a yum repository being created for every commit into<br>
>> the monitored openstack projects[4]<br>
>><br>
>> So ya count me in for any discussions happening.<br>
>><br>
>> [1] <a href="https://github.com/openstack-packages/delorean" target="_blank">https://github.com/openstack-packages/delorean</a><br>
>> [2] <a href="https://review.gerrithub.io/" target="_blank">https://review.gerrithub.io/</a><br>
>> [3] <a href="https://github.com/openstack-packages" target="_blank">https://github.com/openstack-packages</a><br>
>> [4] <a href="http://209.132.178.33/repos/report.html" target="_blank">http://209.132.178.33/repos/report.html</a> (DNS pending)<br>
><br>
> Any reason stackforge wasn't chosen instead of another Github organization?<br>
<br>
While trying to figure out the process having it on a github org was an advantage for a number of reasons for example we started out with a small set of packaging repositories and added as needed, creating these is a lot quicker on github, adding stackforge repositories would have been slower, we've also renamed a couple of repositories and deleted others<br>
<br>
In future as things settle down and we get a better view of whats needed, I'm open to moving to stackforge.<br>
<br>
><br>
> Best,<br>
> -jay<br>
><br>
> _______________________________________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operator" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operator</a><br>
> s<br>
<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</div></div></blockquote></div><br></div>