Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC8)

[Jan van Doorn]

Hi Justin, 

Thanks again for your time checking our release, and sorry we’re still not 
there. 

We’ve been running https://creadur.apache.org/rat/ 
  - is there anything else that you use that 
we can also use? Any tips you have for us to get through this?

Best Regards,
JvD


> On Jan 20, 2017, at 4:20 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> Sorry but it’s -1 (binding) as licensing issues and file headers reported 
> last release that were not fixed.
> 
> I checked:
> - names include incubating
> - signature and hashes are OK
> - disclaimer exits
> - LICENSE still has issues brought up from last release
> - NOTICE is OK but has wrong year
> - Source files have ASF header. A couple of files have them incorrectly.
> - No unexpected binary files in release.
> 
> While some of the issues brought up in last release have been fixed, there a 
> large number that look like they haven’t.
> 
> LICENSE Is still missing licenses for jQuery UI, normalize.css, angular 
> loading bar, lz-string (which also incorrectly has an ASF header on it), 
> pretty print  (and which also has an incorrectly added ASF header) and 
> modernizr. They may be others. Also the dual licensing for select2.js has not 
> been dealt with and nor has the licensing of multiple font files.
> 
> LICENSE also includes WebAppers Progress Bar which as pointed out last 
> release is Category B and cannot be included in a source release.
> 
> Re licensing around the MaxMind DB GeoLite2 Database [1] (under a CC 
> share-alike license) also IMO needs to be sorted. I’m not sure it classifies 
> as "unmodified media”, best to ask on legal discuss.
> 
> Thanks,
> Justin
> 
> 1. ./traffic_router/core/src/test/resources/geo/GeoLite2-City.mmdb.gz
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

[RESULT][VOTE] Accept Traffic Control into the Apache Incubator

[Jan van Doorn]

The results are in and voting is now closed. The votes:

[7] +1 Accept Traffic Control into the Apache Incubator

  Phil Sorber (binding)
  Leif Hedstrom (binding)
  Josh Elser (binding)
  Pierre Smits (non-binding)
  Jacky Li (non-binding)
  Nick Kew (binding)
  Daniel Gruno (binding)

[0] +/-0 Not overly bothered either way

[0] -1 DO NOT accept Traffic Control into the Apache Incubator

Thanks to everyone who voted and reviewed our proposal.

Traffic Control has been accepted into the Incubator!

The [VOTE] thread can be found here:
https://lists.apache.org/thread.html/b9c118f59a825024ca20f8b0b4500b4456c154b34295d94de058e834@%3Cgeneral.incubator.apache.org%3E
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Traffic Control into the Apache Incubator

[Jan van Doorn]

> On Jul 8, 2016, at 12:27, Nick Kew  wrote:
> 
> Just wondering if you could elaborate on one point:
> 
> "We don't want to become a sub-project of ATS though, because we
> believe we should add other caching proxies as they are deemed to be a
> valuable addition to the Traffic Control CDN. "
> 
> To me that raises a couple of questions:
> - Would association with ATS really hold you back?
> - How much overlap is there between the dev communities?
> I'm wondering if the experience of separating HTTPD and APR
> might just be relevant to this issue.
> 

I don't think the association with ATS would hold us back, but I do think it 
could give prospective users of Traffic Control the impression that it only 
works with ATS. This is true now, but won't be in the future.

Only one or two people actively work on both projects, the development 
communities are mostly separate.

I'm not familiar with the HTTPD and APR history, is there a lesson we should 
learn from that?

Thanks,
JvD

(apologies if you get this twice, I sent this out earlier, but never saw it 
make the list)


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Accept Traffic Control into the Apache Incubator

[Jan van Doorn]

  *  CPAN package 'PerlIO::utf8_strict'
  *  CPAN package 'PerlIO::via::Timeout'
  *  CPAN package 'Pod::Coverage::CountParents'
  *  CPAN package 'Pod::Coverage::TrustPod'
  *  CPAN package 'Pod::Escapes'
  *  CPAN package 'Pod::Eventual::Simple'
  *  CPAN package 'Pod::Find'
  *  CPAN package 'Pod::Man'
  *  CPAN package 'Pod::Simple'
  *  CPAN package 'Pod::Usage'
  *  CPAN package 'Role::Tiny'
  *  CPAN package 'SQL::Abstract'
  *  CPAN package 'Scalar::Util'
  *  CPAN package 'Scope::Guard'
  *  CPAN package 'Socket'
  *  CPAN package 'Storable'
  *  CPAN package 'String::CamelCase'
  *  CPAN package 'String::ToIdentifier::EN'
  *  CPAN package 'Sub::Exporter'
  *  CPAN package 'Sub::Exporter::Progressive'
  *  CPAN package 'Sub::Identify'
  *  CPAN package 'Sub::Install'
  *  CPAN package 'Sub::Name'
  *  CPAN package 'Sub::Uplevel'
  *  CPAN package 'Sys::Syslog'
  *  CPAN package 'TAP::Formatter::Jenkins'
  *  CPAN package 'Task::Weaken'
  *  CPAN package 'Term::ReadPassword'
  *  CPAN package 'Test'
  *  CPAN package 'Test::Builder::Tester'
  *  CPAN package 'Test::CPAN::Meta'
  *  CPAN package 'Test::Deep'
  *  CPAN package 'Test::Exception'
  *  CPAN package 'Test::Fatal'
  *  CPAN package 'Test::Harness'
  *  CPAN package 'Test::Inter'
  *  CPAN package 'Test::Mojo'
  *  CPAN package 'Test::MockModule'
  *  CPAN package 'Test::MockObject'
  *  CPAN package 'Test::More'
  *  CPAN package 'Test::NoWarnings'
  *  CPAN package 'Test::Pod'
  *  CPAN package 'Test::SharedFork'
  *  CPAN package 'Test::TCP'
  *  CPAN package 'Test::Tester'
  *  CPAN package 'Test::Warn'
  *  CPAN package 'Test::Requires'
  *  CPAN package 'Text::Abbrev'
  *  CPAN package 'Text::Balanced'
  *  CPAN package 'Text::German'
  *  CPAN package 'Text::Glob'
  *  CPAN package 'Text::ParseWords'
  *  CPAN package 'Text::Unidecode'
  *  CPAN package 'Text::Wrap'
  *  CPAN package 'Time::HiRes'
  *  CPAN package 'Time::Local'
  *  CPAN package 'Time::Out'
  *  CPAN package 'Time::Seconds'
  *  CPAN package 'Try::Tiny'
  *  CPAN package 'URI'
  *  CPAN package 'WWW::Curl::Easy'
  *  CPAN package 'WWW::RobotRules'
  *  CPAN package 'XSLoader'
  *  CPAN package 'ExtUtils::Config' # for Net::Riak
  *  CPAN package 'Module::Build::Tiny'  # for Net::Riak
  *  CPAN package 'Net::Riak'
  *  CPAN package 'Crypt::OpenSSL::RSA'
  *  CPAN package 'Crypt::OpenSSL::Bignum'
  *  CPAN package 'Crypt::OpenSSL::Random'
  *  CPAN package 'Net::DNS::SEC::Private'
  *  CPAN package 'LWP::Protocol::https'
  *  CPAN package 'Net::CIDR'
  *  CPAN package 'Data::Validate::IP'

== Cryptography ==

There is no cryptographic code in Traffic Control. We leverage OpenSSL for
all our cryptography needs.

== Required Resources ==

=== Mailing lists ===

We currently use "google groups" to communicate, but we would like to move that
to ASF maintained mailing lists.

Current groups / mailing lists:
 * https://groups.google.com/forum/#!forum/traffic_control
 * https://groups.google.com/forum/#!forum/traffic_control-announce
 * https://groups.google.com/forum/#!forum/traffic_control-discuss

Proposed ASF maintained lists:
 * priv...@traffic-control.incubator.apache.org (moderated subscriptions)
 * d...@traffic-control.incubator.apache.org
 * comm...@traffic-control.incubator.apache.org
 * notificati...@traffic-control.incubator.apache.org
 * us...@traffic-control.incubator.apache.org

=== Subversion Directory ===

We do not use SVN for source code revision control.

=== Git Repository ===

We would like to use git-wip (git://git.apache.org/traffic_control.git). 


=== Issue Tracking ===

JIRA.

=== Other Resources ===

We have automated tests and continuous integration configurations we would like
to move away from Comcast.

== Initial Committers ==

 * Dan Kirkwood (dangogh at gmail.com)
 * David Neuman (david.neuman64 at gmail.com)
 * Dewayne Richardson (dewrich at gmail.com)
 * Eric Friedrich (eric.friedrich84 at gmail.com)
 * Hank Beatty (Hank.Beatty at cox.com)
 * Jackie Heitzer (jackieheitzer at gmail.com)
 * Jan van Doorn (jvd at knutsel.com)
 * Jeff Elsloo (jeff.elsloo at gmail.com)
 * Jeremy Mitchell (mitchell852 at gmail.com)
 * Mark Torluemke (mark at torluemke.net)
 * Steve Malenfant (steve.malenfant at cox.com)

== Affiliations ==

 * Comcast Cable: Dan Kirkwood, David Neuman, Dewayne Richardson, Jackie 
Heitzer,
 Jan van Doorn, Jeff Elsloo, Jeremy Mitchell, Mark Torluemke

 * Cox Communications: Hank Beatty, Steve Malenfant

 * Cisco: Eric Friedrich

== Sponsors ==

=== Champion ===

 * Leif Hedstrom (zwoop at apache.org)

=== Nominated Mentors ===

 * Phil Sorber (sorber at apache.org)
 * Eric Covener (covener at apache.org)
 * Daniel Gruno (humbedooh at apache.org)
 * J. Aaron Farr (farra at apache.org)

=== Sponsoring Entity ===

We request the Apache Incubator to sponsor this project.


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additio

Re: Traffic Control Incubation Proposal.

[Jan van Doorn]

I updated the proposal to request git-wip and JIRA.

Thanks,
JvD

On Tue, Jun 21, 2016 at 3:05 PM, Leif Hedstrom  wrote:

>
> > On Jun 17, 2016, at 4:58 PM, John D. Ament 
> wrote:
> >
> > Leif,
> >
> > I doubt this is something IPMC can help you with.  As champion, I would
> > recommend that you reach out to infra to see the appetite to support
> > git-dual on a podling.  You will want to explain the scenario with the
> > "partner” project
>
>
> We discussed this with Infra, and the answer is that this podling would
> need to move to Apache Git servers (git-wip).
>
> Jan: Can you update your proposal accordingly please? Specify the
> resources you wish to use, including Jira or Bugzilla if you so choose. You
> could use the Github issues associated with the Github mirror of the
> podling, but that makes it more difficult to manage I think, since you
> would not be able to do things such as assigning issues etc.
>
> Cheers,
>
> — leif
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Traffic Control Incubation Proposal.

[Jan van Doorn]

Hi all,

I would like to discuss the proposal of a new project to the Incubator. 

Traffic Control is a CDN control plane that was open sourced in April of 2015. 

The Proposal is pasted below and can be found on the wiki at: 
https://wiki.apache.org/incubator/TrafficControlProposal 
<https://wiki.apache.org/incubator/TrafficControlProposal>

Best Regards,
Jan van Doorn

---
= Traffic Control Proposal =

== Abstract ==

Traffic Control allows you to build a large scale content delivery network using
open source. 

== Proposal ==

The goal of this proposal is to bring the Traffic Control project into the
Apache Software Foundation.

== Background ==

Initially built around Apache Traffic Server as the caching software, Traffic
Control implements all functions of a modern CDN except the caching software:

 * Traffic Router is a Java Tomcat application that routes clients to the 
closest
 available cache on the CDN using both HTTP and DNS. By using consistent hashing
 it sends requests for the same content to the same cache in a group of caches
 working together in a location. It takes care of routing clients around hot
 spots and problems in the CDN by using the information from Traffic Monitor 
with
 regards to state of all the caches.

 * Traffic Monitor is a Java Tomcat application that implements the CDN health
 protocol. Every cache in the CDN is checked using HTTP for vital stats, and
 based on these stats, caches are declared healthy or unhealthy. This 
information
 is then used by Traffic Router to make its routing decisions.

 * Traffic Ops is a Perl Mojolicious and jQuery UI application for management 
and
 monitoring of all servers in the CDN. All server and content routing 
information
 for the CDN is managed through Traffic Ops. It also exposes RESTful API
 endpoints for consumption by tools and other applications.

 * Traffic Stats is a Go application that is used to acquire and store 
statistics
 about CDNs controlled by Traffic Control. Traffic Stats mines metrics from 
 Traffic Monitor’s JSON APIs and stores the data in InfluxDB, and visualizes 
them 
 using Grafana.

 * Traffic Analytics is a new component we are starting to build for log file 
 analysis, based on Apache Kafka, Heka, and Elastic Search.


Traffic Control was developed by Comcast Cable and released as open source under
the Apache 2.0 license in April of 2015. Traffic Control is deployed at Comcast
and other cable operators.

The Traffic Control project was presented at ApacheCon NA 2016, see 
http://bit.ly/1UwMzmR for additional background information.

== Rationale ==

Even though the traffic on today's CDNs is strictly defined by open standards,
and there are many open source implementations of caches available, CDNs are
still proprietary. The current providers of CDN-as-a-product or
CDN-as-a-service all have their own proprietary implementation of the control
plane.  The CDN control plane of one vendor can't interoperate with the CDN
control plane of another, creating a classic vendor-lockin for CDN-as-a-product
customers. Traffic Control changes that. Emerging standards from IETF (CDNi
working group) and the Streaming Video Alliance Open Caching working group need
an open source reference implementation; Traffic Control will strive to be
that.

== Initial Goals ==

Initial goals of transitioning to ASF is to grow and diversify the community,
and to move to a more open and inclusive development model.

== Current Status ==

Traffic Control is functional and deployed at Comcast and other cable operators.
In the past 12 months 10 major releases have been made.

=== Meritocracy ===

Initial development was done at Comcast Cable. Since April 2015  it has been
open source, and a handful outside contributors have been added.

Our main goal during incubation is to try to create a more diverse group of
contributors and users.

=== Community ===

Traffic Control is being used by a number of cable companies and is being
evaluated by a number of vendors and ISPs. Two vendors have created products
based on Traffic Control and are active in the community.

=== Core Developers ===

Most of the core developers of Traffic Control are currently at Comcast. The
main goal of the incubation is to grow the developer and user group into a
community beyond Comcast and US cable.

=== Alignment ===

Traffic Control is closely aligned with Apache Traffic Server (ATS). The only
supported cache in a Traffic Control CDN at this time is ATS.  One of our
proposed mentors is a committers to ATS, and our proposed champion the ATS PMC
chair.

We don't want to become a sub-project of ATS though, because we believe we
should add other caching proxies as they are deemed to be a valuable addition to
the Traffic Control CDN.

== Known Risks ==

=== Orphaned products ===

Traffic Control is a new system that does not have wide adoption, but at least
two major North American ISPs are committed to the continued development. Two 
vendors have used it to

Wiki write access please?

[Jan van Doorn]

Hello,

Can you please grant write access for https://wiki.apache.org/incubator to for 
user JanVandoorn ?

I would like to start a proposal for Traffic Control. 

Thanks,
JvD
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org