Open Stack

Agreed that storing Hadoop-Swift integration jars in the git repo is a good practice, any thoughts about where to store them? Currently I have only one option - we can store them at the public CDN (savanna-files.mirantis.com) near the images for vanilla plugin.

As for publishing tarballs with the content of savanna-extra - looks like there are more pros than cons, so, we can do it.

Sincerely yours,
Sergey Lukjanov
Savanna Technical Lead
Mirantis Inc.

On Aug 20, 2013, at 16:31, Matthew Farrellee <matt at redhat.com> wrote:

> Is there a downside to having it? A positive is it gives a snapshot of everything for each release.
> 
> I'm not at fan of having a snapshot of the Hadoop swift patches compiled into a jar and stored in the repository. I'd prefer that it is hosted elsewhere.
> 
> Best,
> 
> 
> matt
> 
> On 08/19/2013 04:37 PM, Sergey Lukjanov wrote:
>> Hi Matt,
>> 
>> it is not an accident that savanna-extra has no tarballs at
>> tarballs.o.o, because this repo is used for storing some date that is
>> only needed for some stuff like building images for vanilla plugin,
>> storing Swift support patch for Hadoop and etc. So, it looks like
>> that we should not package all of them to one heterogeneous tarball.
>> 
>> Sincerely yours,
>> Sergey Lukjanov
>> Savanna Technical Lead
>> Mirantis Inc.
>> 
>> On Aug 20, 2013, at 0:25, Matthew Farrellee <matt at redhat.com> wrote:
>> 
>>> Will someone setup a tarballs.os.o release of savanna-extra's master (https://github.com/stackforge/savanna-extra), and make sure it gets an official release for 0.3?
>>> 
>>> Best,
>>> 
>>> 
>>> matt
>>> 
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>> 
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>