The code hasn't been merged into hadoop-common trunk, once that happens
there's a possibility of getting the jars from there. For now the CDN
works.
On Thu, Aug 22, 2013 at 2:17 PM, Sergey Lukjanov wrote:
> Ok, let's start from storing jars in CDN.
>
> Sincerely yours,
> Sergey Lukjanov
> Savann
Ok, let's start from storing jars in CDN.
Sincerely yours,
Sergey Lukjanov
Savanna Technical Lead
Mirantis Inc.
On Aug 21, 2013, at 23:16, Matthew Farrellee wrote:
> IMHO, the jars should be served from the Apache Hadoop community. I don't
> know what hoops have to jumped through for that thou
IMHO, the jars should be served from the Apache Hadoop community. I
don't know what hoops have to jumped through for that though. It may be
far simpler to put them in the mirantis CDN.
Best,
matt
On 08/21/2013 02:21 PM, Sergey Lukjanov wrote:
Agreed that storing Hadoop-Swift integration jar
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 t
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,
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 pac
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@lists.openstack.org
http:
