trafodion.org domain/servers

[Steve Varnau <st...@esgyn.com>]

Agree with what Hans said about the sandbox. Changing topics now, related to
the downloads page Hans mentioned.
As a Apache (incubating) project, we won't be distributing binaries, and so
the downloads page needs to go away, or at least migrate to downstream
vendors.

Likewise, the entire trafodion.org domain is part of the trademarks being
transferred to ASF. So, we need to clean up the disposition of all the
related sites/servers using that domain.

I looked through the DNS records, and I think things fall into 3 buckets.

1) Servers that are already obsolete and no longer used. (e.g., review.t.o,
zuul.t.o)

2) Sites replaced by Apache resources, and can go away after content is
migrated. (e.g., wiki.t.o) Though a redirect would be nice to keep in place
for some time.

3) Things that move to downstream vendors (binary downloads) or are
development resources donated to the community by vendors (daily build
convenience binaries, test environment). Migrating everything to ASF Jenkins
environment is a big project. Currently, the cloud resources to run the
project automated testing is donated by vendor where many of the
contributors work (previously paid for by HP, now paid for by Esgyn).  My
thinking is that these would move to esgyn.com domain, unless ASF enables it
to remain as trafodion.org. Either way, they'll be resources providing
service to development community.

I'm taking my cue from Apache Spark who has QA infrastructure hosted by
Berkeley:
https://cwiki.apache.org/confluence/display/SPARK/Spark+QA+Infrastructure

Anybody familiar with this situation? Am I going down right path?

--Steve

-----Original Message-----
From: Hans Zeller [mailto:hans.zeller@esgyn.com]
Sent: Wednesday, July 29, 2015 3:32 PM
To: dev <de...@trafodion.incubator.apache.org>
Subject: Re: Draft for August Trafodion podling status report

Hi,

IMHO, the recipe for creating the sandbox should be on the wiki and
therefore open source. Since the sandbox itself is a binary, the term
open-source probably does not apply to it. There could be multiple people
and organization offering a sandbox binary, either as a downloadable OVA
file or through a shareable Amazon AMI or an equivalent with other cloud
providers. I don't think ASF needs to provide this binary directly.

The sandbox image contains GPL-licensed software like Linux, etc., plus
Apache-licensed things like Hadoop and Trafodion. Then there are a few items
that may require special licenses, like Cloudera Manager or the code to
create TPC-DS data files. Those could be mentioned in a recipe, but could
not be distributed freely as an image. As far as I know, it's ok to
distribute a sandbox with Hortonworks installed on it, so the sandbox should
probably be based on that.

In case some people don't know, there is currently an OVA file available for
download at http://downloads.trafodion.org.

Thanks,

Hans

On Wed, Jul 29, 2015 at 3:12 PM, Dave Birdsall <da...@esgyn.com>
wrote:

> Hi,
>
> Is the Sandbox open source?
>
> Dave
>
> On Wed, Jul 29, 2015 at 12:24 PM, Qifan Chen <qi...@esgyn.com> wrote:
>
> > On community development (the 1st most important issue), I wonder if
> > we
> can
> > mention the following.
> >
> > 1. Actively help Trafodion users to develop skills and knowhow to
> > use Trafdoion (the cases of user Layla and Radu) 2. Sandbox develop
> > method (on Windows) ready
> >
> > The report looks good.
> >
> > --Qifan
> >
> > On Wed, Jul 29, 2015 at 1:39 PM, Roberta Marton <
> roberta.marton@esgyn.com>
> > wrote:
> >
> > > Thanks for putting this together, it looks good.
> > > I believe Rohit will be talking at ApacheCon in Budapest (Ken
> confirmed),
> > > should we include this?
> > >
> > > On Wed, Jul 29, 2015 at 9:54 AM, Dave Birdsall <
> dave.birdsall@esgyn.com>
> > > wrote:
> > >
> > > > Hi Suresh,
> > > >
> > > > Looks good. A couple more notes:
> > > >
> > > > On wiki migration, it's expected that relevant content from the
> > > pre-Apache
> > > > Trafodion wiki will be contributed to the project shortly and
> > > > that
> > > content
> > > > integrated into the new Apache wiki and web site over the next
> > > > month
> or
> > > so.
> > > >
> > > > On licensing issues, JIRA TRAFODION-28 will update all source
> > > > files
> to
> > > > bring licenses into ASF compliance. That should happen by the
> > > > end of August.
> > > >
> > > > Dave
> > > >
> > > >
> > > >
> > > > On Wed, Jul 29, 2015 at 8:40 AM, Suresh Subbiah <
> > > > suresh.subbiah60@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > Please give your feedback on this status report. I copied the
> > > > > July
> > > > version
> > > > > and made some edits.
> > > > >
> > > > > Thank you
> > > > > Suresh
> > > > >
> > > > >
> > > > >
> > > > > Trafodion
> > > > >
> > > > > Trafodion is a webscale SQL-on-Hadoop solution enabling
> transactional
> > > > > or operational workloads on Hadoop.
> > > > >
> > > > > Trafodion has been incubating since 2015-05-24.
> > > > >
> > > > > Four most important issues to address in the move towards
> graduation:
> > > > >
> > > > > 1. Develop community and a deeper understanding of the Apache Way.
> > Move
> > > > all
> > > > > communication to project public dlists.
> > > > > 2. Complete wiki migration and build website.
> > > > > 3. Resolve remaining license conflicts.
> > > > > 4. Make our first Apache (incubating) release.
> > > > >
> > > > >
> > > > > Any issues that the Incubator PMC (IPMC) or ASF Board
> > > > > wish/need to
> be
> > > > aware
> > > > > of?
> > > > >
> > > > > None.
> > > > >
> > > > > How has the community developed since the last report?
> > > > >
> > > > > All issues are now discussed through JIRAs.
> > > > > An on boarding process for new contributors has been
> > > > > documented in
> > the
> > > > > wiki.
> > > > > We have 30 contributors from more than 4 organizations.
> > > > > Invited to present at Hadoop Conference in China (name?)
> > > > >
> > > > >
> > > > > How has the project developed since the last report?
> > > > >
> > > > > Website up at http://trafodion.incubator.apache.org/
> > > > > 5 pages added to the wiki at
> > > > > https://cwiki.apache.org/confluence/display/TRAFODION/
> > > > > Daily builds are being done using a CI system outside of ASF
> > > > > Infrastructure.
> > > > > 17 authors have made 29 commits to master in July. 165 files
> changed,
> > > > 9518
> > > > > lines additions, 5742 deletions.
> > > > > With migration from previous issue tracking system completed
> > > > > we
> have
> > > 1415
> > > > > JIRAs created and 36 resolved in July 2015
> > > > >
> > > > > Date of last release:
> > > > >
> > > > > We have not done a release of Trafodion since incubation.
> > > > >
> > > > > When were the last committers or PMC members elected?
> > > > >
> > > > > Steve Varnau elected as committer on July 16, 2015.
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Regards, --Qifan
> >
>

Re: trafodion.org domain/servers

[Roman Shaposhnik <ro...@shaposhnik.org>]

On Wed, Jul 29, 2015 at 11:15 AM, Steve Varnau <st...@esgyn.com> wrote:
> Agree with what Hans said about the sandbox. Changing topics now, related to
> the downloads page Hans mentioned.
> As a Apache (incubating) project, we won't be distributing binaries,

I don't know what gave you that impressions, but you can distribute
binary convenience artifacts IN ADDITION to your source releases
just fine. A lot of projects do that. Of course, for a C/C++ project it
get more complex, but doable.


> Likewise, the entire trafodion.org domain is part of the trademarks being
> transferred to ASF. So, we need to clean up the disposition of all the
> related sites/servers using that domain.
>
> I looked through the DNS records, and I think things fall into 3 buckets.
>
> 1) Servers that are already obsolete and no longer used. (e.g., review.t.o,
> zuul.t.o)
>
> 2) Sites replaced by Apache resources, and can go away after content is
> migrated. (e.g., wiki.t.o) Though a redirect would be nice to keep in place
> for some time.
>
> 3) Things that move to downstream vendors (binary downloads) or are
> development resources donated to the community by vendors (daily build
> convenience binaries, test environment). Migrating everything to ASF Jenkins
> environment is a big project. Currently, the cloud resources to run the
> project automated testing is donated by vendor where many of the
> contributors work (previously paid for by HP, now paid for by Esgyn).  My
> thinking is that these would move to esgyn.com domain, unless ASF enables it
> to remain as trafodion.org. Either way, they'll be resources providing
> service to development community.
>
> I'm taking my cue from Apache Spark who has QA infrastructure hosted by
> Berkeley:
> https://cwiki.apache.org/confluence/display/SPARK/Spark+QA+Infrastructure
>
> Anybody familiar with this situation? Am I going down right path?

It makes sense (aside from the point I made above). Feel free to reach out to
me  for advice on DNS transfer issues. I'm doing that for Geode right now.

Thanks,
Roman.