Traffic Server Secondary Streaming IPs Design

[Zhilin Huang (zhilhuan)]

Hi Guys,

This was originally posted in another discussion. Resend this in a standalone 
topic to catch more awareness. The link for the design doc:
https://docs.google.com/document/d/1vgq-pGNoLLYf7Y3cu5hWu67TUKpN5hucrp-ZS9nSsd4/edit?usp=sharing


Short summary for the feature design:
---
There is feature request from market to add secondary IPs support on edge cache 
servers, and the functionality to assign a delivery service to a secondary IP 
of an edge cache.

This feature requires Traffic Ops implementation to support secondary IP 
configuration for edge cache, and delivery service assignment to secondary IP. 

Traffic Monitor should also monitor connectivity of secondary IPs configured. 
And Traffic Router needs support to resolve streamer FQDN to secondary IP 
assigned in a delivery service.

Traffic Server should record the IP serving client request. And should reject 
request to an unassigned IP for a delivery service.

This design has taken compatibility into consideration: if no secondary IP 
configured, or some parts of the system has not been upgraded to the version 
supports this feature, the traffic will be served by primary IPs as before.
---

Much appreciated and welcome to any comments. If no major objections, we 
planned to start coding this week.

Thanks,
Zhilin

Re: ATC Spring Summit 2018 Registration and CFP

[Dave Neuman]

Hey All,
We have a few slots still available to speak at the summit. Let me know if
you are interested!

Thanks,
Dave

On Thu, Mar 29, 2018 at 2:24 PM, Dave Neuman  wrote:

> Hey Everyone,
> Just a reminder that our spring summit is less than a month away and our
> CFP will be closing in just 3 more days!  If you haven't had the
> opportunity to register yet, I encourage you to do so!  There is no
> registration fee, you just need to get yourself to Boston.  If you are
> planning on submitting a talk please do so by April 1st so that I can get a
> schedule out.  Please be assured that we have plenty of speaking slots
> still available.
>
> Register here:  https://cwiki.apache.org/confluence/display/TC/ATC+
> Spring+Summit+-+April+2018%2C+Boxborough%2C+MA.
> 
> Submit a talk by sending an email here:   summits@
> trafficcontrol.incubator.apache.org
> 
>
> Thanks,
> Dave
>
> On Fri, Mar 2, 2018 at 2:51 PM, Dave Neuman  wrote:
>
>> I just wanted to let everyone know that I have updated updated the wiki
>> page with hotel and transportation information.
>>
>> Thanks to everyone that has signed up and I look forward to more people
>> signing up.
>>
>> Thanks,
>> Dave
>>
>> On Sat, Feb 24, 2018 at 9:26 AM, Dave Neuman  wrote:
>>
>>> Hey All,
>>> It's my pleasure to announce that Apache Traffic Control will be having
>>> our spring summit on April 24 and 25 in Boxborough (Boston), Massachusetts!
>>> If you want to learn more about ATC, get some questions answered by
>>> members of the community, or just hang out with us for a few days, please
>>> see the following wiki page to RSVP:  https://cwiki.apache.org/conf
>>> luence/display/TC/ATC+Spring+Summit+-+April+2018%2C+Boxborough%2C+MA.
>>> 
>>>
>>> This email also servers as a CFP (Call for papers/presentations), if you
>>> have a great idea for a presentation let us know at
>>> summ...@trafficcontrol.incubator.apache.org
>>>  by April 1, 2018.  We
>>> will work on publishing a schedule as soon as we start getting submissions.
>>>
>>> Any questions just let me know.
>>>
>>> Thanks and I look forward to seeing everyone there!
>>>
>>> Dave
>>>
>>>
>>
>

Re: Question about the poll model of the Traffic Monitor

[David Neuman]

Hi Zhilin,
Is it possible to get this design doc added to our wiki?  I create a design
docs page here (https://cwiki.apache.org/confluence/display/TC/Design+Docs).
I think it would be good to get the document there so it doesn't get lost
over time.

Thanks!
Dave

On Wed, Mar 28, 2018 at 10:41 PM, Zhilin Huang (zhilhuan) <
zhilh...@cisco.com> wrote:

> Hi Guys,
>
> Thanks a lot for the discussion. I should put the design earlier for
> review, and sorry for the delay. Here is the link for the design doc:
> https://docs.google.com/document/d/1vgq-pGNoLLYf7Y3cu5hWu67TUKpN5hucrp
> -ZS9nSsd4/edit?usp=sharing
>
> Short summary for the feature design:
> ---
> There is feature request from market to add secondary IPs support on edge
> cache servers, and the functionality to assign a delivery service to a
> secondary IP of an edge cache.
>
> This feature requires Traffic Ops implementation to support secondary IP
> configuration for edge cache, and delivery service assignment to secondary
> IP.
>
> Traffic Monitor should also monitor connectivity of secondary IPs
> configured. And Traffic Router needs support to resolve streamer FQDN to
> secondary IP assigned in a delivery service.
>
> Traffic Server should record the IP serving client request. And should
> reject request to an unassigned IP for a delivery service.
>
> This design has taken compatibility into consideration: if no secondary IP
> configured, or some parts of the system has not been upgraded to the
> version supports this feature, the traffic will be served by primary IPs as
> before.
> ---
>
> Replies for Robert's comments is embedded in the email thread. Much
> appreciated and welcome to any further comments.
>
> Thanks,
> Zhilin
>
>
>
>
> On 29/03/2018, 10:19 AM, "Neil Hao (nbaoping)" 
> wrote:
>
> Hi Robert/Nir,
>
> Thanks very much for the quick and detail reply, and sorry for that I
> didn’t make the whole feature clearly. Actually, it’s our Secondary IP
> feature, which is a big feature that will bring change to all the
> components in the Traffic Control. I thought our teammate reviewed the
> design with you guys before, but it seems not. And after discussion, we
> will start the whole feature design review with you guys soon, I think it
> will be better to continue the discussion after that.
>
> Thanks,
> Neil
>
> On 3/29/18, 1:16 AM, "Robert Butts"  wrote:
>
> I agree with Nir, it's not as simple as changing a structure to
> `[]URL`,
> it's a bigger architectural design question.
>
> How do you plan to mark caches Unavailable if they're unhealthy on
> one
> interface, but healthy on another?
>
> Right now, Traffic Router needs a boolean for each cache, it
> doesn't know
> anything about multiple network interfaces, IPv4 vs IPv6, etc. It
> only
> knows the FQDN, which is all the clients it's giving DNS records
> to will
> know when they request the cache.
>
> Questions:
> Is a cache marked Unavailable when any interface is unreachable?
> Or all of
> them?
> ZH> Actually, we will care about an IP availability instead of interface
> availability. Please take a look at 3.1.2 of the design doc.
>
> What if an interface is reachable, but one interface reports
> different
> stats than another interface? For example, what if someone
> configures a
> different caching proxy (ATS) on each interface?
> ZH> Will only use 1 ATS to serve traffic from all IPs configured.
>
> How are stats aggregated? Should the monitor aggregate all stats
> from
> different polls and interfaces together, and consider them the same
> "server"? If not, how do we reconcile the different stats with
> what the
> Monitor reports on `CrStates` and `CacheStats`? If so, again, what
> happens
> if different interfaces have different ATS instances, so e.g. the
> byte
> count on one is 100, and the other is 1000, then 101, then 1001.
> It simply
> won't work. Do we handle that? Or just ignore it, and document "all
> interfaces must report the same stats"? Do we try to detect that
> and give a
> useful error or warning?
> ZH> The bandwidth for interfaces will be aggregated. We will only have 1
> ATS to serve traffic from all interfaces. The connectivity check is IP
> based. And the stats collection will be interface based. Please take a look
> at 3.1.2 of the design doc for details.
>
> In Traffic Ops, servers have specific data used for polling.
> Traffic
> Monitor gets the stats URI path from Parameters, and the URI IP
> from the
> Servers table. It doesn't use the FQDN, Server Host or Server
> Domain. Where
> would these other interfaces come from? Parameters? Or another
> table linked
> to the servers table? (I'd really, really rather we didn't put
> more data in
> unsafe Parameters, 

Re: [VOTE] Resolution for Traffic Control graduation to TLP

[Leif Hedstrom]

> On Apr 2, 2018, at 2:11 PM, David Neuman  wrote:
> 
> Dear Traffic Control community members:
> 
> I would like to call a vote on the resolution for Traffic Control to
> graduate from to an Apache TLP.  We have already voted on whether or not we
> should start the graduation process [1] and this is the next step.  Please
> see the resolution below and vote as follows:
> 
> [ ] +1 Graduate Traffic Control from the incubator
> [ ] +0 No Opinion
> [ ] -1 Do not graduate Traffic Control from the incubator (please provide a
> reason)
> 


+1 (binding)

— Leif

Re: [VOTE] Resolution for Traffic Control graduation to TLP

[Nir Sopher]

+1

On Mon, Apr 2, 2018 at 11:24 PM, Gelinas, Derek 
wrote:

> +1
>
> > On Apr 2, 2018, at 4:20 PM, Leif Hedstrom  wrote:
> >
> >
> >> On Apr 2, 2018, at 2:11 PM, David Neuman 
> wrote:
> >>
> >> Dear Traffic Control community members:
> >>
> >> I would like to call a vote on the resolution for Traffic Control to
> >> graduate from to an Apache TLP.  We have already voted on whether or
> not we
> >> should start the graduation process [1] and this is the next step.
> Please
> >> see the resolution below and vote as follows:
> >>
> >> [ ] +1 Graduate Traffic Control from the incubator
> >> [ ] +0 No Opinion
> >> [ ] -1 Do not graduate Traffic Control from the incubator (please
> provide a
> >> reason)
> >>
> >
> >
> > +1 (binding)
> >
> > — Leif
> >
>

Re: [VOTE] Resolution for Traffic Control graduation to TLP

[Phil Sorber]

+1!

On Mon, Apr 2, 2018 at 8:12 PM Dave Neuman  wrote:

> +1
>
> On Mon, Apr 2, 2018 at 2:11 PM, David Neuman 
> wrote:
>
> > Dear Traffic Control community members:
> >
> > I would like to call a vote on the resolution for Traffic Control to
> > graduate from to an Apache TLP.  We have already voted on whether or not
> we
> > should start the graduation process [1] and this is the next step.
> Please
> > see the resolution below and vote as follows:
> >
> > [ ] +1 Graduate Traffic Control from the incubator
> > [ ] +0 No Opinion
> > [ ] -1 Do not graduate Traffic Control from the incubator (please provide
> > a reason)
> >
> > The vote is open for a minimum of 72 hours and will need at least 3 more
> > +1 votes than -1 votes from PMC members to succeed.
> >
> > If this VOTE succeeds, a similar VOTE will be started on the
> > gene...@incubator.apache.org mailing list. If that VOTE succeeds, a
> > resolution will be included in the next Apache Board Meeting.
> >
> > Please feel free to reach out with any questions.
> >
> > Thanks,
> > Dave
> >
> > [1] https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa207
> > 23eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E
> >
> > -
> >
> > Establish the Apache Traffic Control Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to building, monitoring, configuring, and provisioning a large
> > scale content delivery network (CDN)..
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Traffic Control Project", be and
> > hereby is established pursuant to Bylaws of the Foundation; and be it
> > further
> >
> > RESOLVED, that the Apache Traffic Control Project be and hereby is
> > responsible for the creation and maintenance of software related to
> > building, monitoring, configuring, and provisioning a large scale
> > content delivery network (CDN).; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Traffic Control" be
> > and hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache Traffic
> > Control Project, and to have primary responsibility for management of
> > the projects within the scope of responsibility of the Apache Traffic
> > Control Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache Traffic Control
> > Project:
> >
> >  * Dan Kirkwood   
> >  * David Neuman   
> >  * Dewayne Richardson 
> >  * Eric Covener   
> >  * Eric Friedrich 
> >  * Hank Beatty
> >  * Jan van Doorn  
> >  * Jeff Elsloo
> >  * Jeremy Mitchell
> >  * Leif Hedstrom  
> >  * Mark Torluemke 
> >  * Phil Sorber
> >  * Steve Malenfant
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed
> > to the office of Vice President, Apache Traffic Control, to serve in
> > accordance with and subject to the direction of the Board of Directors
> > and the Bylaws of the Foundation until death, resignation, retirement,
> > removal or disqualification, or until a successor is appointed; and be
> > it further
> >
> > RESOLVED, that the initial Apache Traffic Control PMC be and hereby is
> > tasked with the creation of a set of bylaws intended to encourage open
> > development and increased participation in the Apache Traffic Control
> > Project; and be it further
> >
> > RESOLVED, that the Apache Traffic Control Project be and hereby is
> > tasked with the migration and rationalization of the Apache Incubator
> > Traffic Control podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > Traffic Control podling encumbered upon the Apache Incubator PMC are
> > hereafter discharged.
> >
> >
> >
>

Re: [VOTE] Resolution for Traffic Control graduation to TLP

[Gelinas, Derek]

+1

> On Apr 2, 2018, at 4:20 PM, Leif Hedstrom  wrote:
> 
> 
>> On Apr 2, 2018, at 2:11 PM, David Neuman  wrote:
>> 
>> Dear Traffic Control community members:
>> 
>> I would like to call a vote on the resolution for Traffic Control to
>> graduate from to an Apache TLP.  We have already voted on whether or not we
>> should start the graduation process [1] and this is the next step.  Please
>> see the resolution below and vote as follows:
>> 
>> [ ] +1 Graduate Traffic Control from the incubator
>> [ ] +0 No Opinion
>> [ ] -1 Do not graduate Traffic Control from the incubator (please provide a
>> reason)
>> 
> 
> 
> +1 (binding)
> 
> — Leif
> 

Re: Traffic Server Secondary Streaming IPs Design

[Nir Sopher]

Hi Zhilin,

I took a quick look into the spec. Hope to have the opportunity to dive
deeper into it soon so we can further discuss it.

For now I have a 2 questions.
In the spec, you refer to "secondary interfaces", and you have a list of
secondary interfaces added.
IIUC the secondary interfaces are used as long as they are available, and
when down, you move to the primary interface.

Why not, instead of holding a secondary interfaces table, move all
interfaces to a separate table? Primary and secondary.
For each interface you can hold:

   - Server id
   - name (e.g. eth0)
   - IPv6
   - IPv4
   - Priority (Integer as flexible as you wish: e.g. "1" for "secondary",
   "2" for "primary" in your example,)


Additionally, it is not clear to me what happens if one of the interfaces
fails?
Does every interface has a unique DNS name? If an interface fails, are
redirects
sent only to the available (secondary) interfaces?

Thanks,
Nir


On Mon, Apr 2, 2018 at 10:21 AM, Zhilin Huang (zhilhuan)  wrote:

> Hi Guys,
>
> This was originally posted in another discussion. Resend this in a
> standalone topic to catch more awareness. The link for the design doc:
> https://docs.google.com/document/d/1vgq-pGNoLLYf7Y3cu5hWu67TUKpN5hucrp
> -ZS9nSsd4/edit?usp=sharing
>
>
> Short summary for the feature design:
> ---
> There is feature request from market to add secondary IPs support on edge
> cache servers, and the functionality to assign a delivery service to a
> secondary IP of an edge cache.
>
> This feature requires Traffic Ops implementation to support secondary IP
> configuration for edge cache, and delivery service assignment to secondary
> IP.
>
> Traffic Monitor should also monitor connectivity of secondary IPs
> configured. And Traffic Router needs support to resolve streamer FQDN to
> secondary IP assigned in a delivery service.
>
> Traffic Server should record the IP serving client request. And should
> reject request to an unassigned IP for a delivery service.
>
> This design has taken compatibility into consideration: if no secondary IP
> configured, or some parts of the system has not been upgraded to the
> version supports this feature, the traffic will be served by primary IPs as
> before.
> ---
>
> Much appreciated and welcome to any comments. If no major objections, we
> planned to start coding this week.
>
> Thanks,
> Zhilin
>
>

Re: [VOTE] Resolution for Traffic Control graduation to TLP

[Dan Kirkwood]

+1

On Mon, Apr 2, 2018 at 2:12 PM, Dave Neuman  wrote:

> +1
>
> On Mon, Apr 2, 2018 at 2:11 PM, David Neuman 
> wrote:
>
> > Dear Traffic Control community members:
> >
> > I would like to call a vote on the resolution for Traffic Control to
> > graduate from to an Apache TLP.  We have already voted on whether or not
> we
> > should start the graduation process [1] and this is the next step.
> Please
> > see the resolution below and vote as follows:
> >
> > [ ] +1 Graduate Traffic Control from the incubator
> > [ ] +0 No Opinion
> > [ ] -1 Do not graduate Traffic Control from the incubator (please provide
> > a reason)
> >
> > The vote is open for a minimum of 72 hours and will need at least 3 more
> > +1 votes than -1 votes from PMC members to succeed.
> >
> > If this VOTE succeeds, a similar VOTE will be started on the
> > gene...@incubator.apache.org mailing list. If that VOTE succeeds, a
> > resolution will be included in the next Apache Board Meeting.
> >
> > Please feel free to reach out with any questions.
> >
> > Thanks,
> > Dave
> >
> > [1] https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa207
> > 23eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E
> >
> > -
> >
> > Establish the Apache Traffic Control Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to building, monitoring, configuring, and provisioning a large
> > scale content delivery network (CDN)..
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Traffic Control Project", be and
> > hereby is established pursuant to Bylaws of the Foundation; and be it
> > further
> >
> > RESOLVED, that the Apache Traffic Control Project be and hereby is
> > responsible for the creation and maintenance of software related to
> > building, monitoring, configuring, and provisioning a large scale
> > content delivery network (CDN).; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Traffic Control" be
> > and hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache Traffic
> > Control Project, and to have primary responsibility for management of
> > the projects within the scope of responsibility of the Apache Traffic
> > Control Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache Traffic Control
> > Project:
> >
> >  * Dan Kirkwood   
> >  * David Neuman   
> >  * Dewayne Richardson 
> >  * Eric Covener   
> >  * Eric Friedrich 
> >  * Hank Beatty
> >  * Jan van Doorn  
> >  * Jeff Elsloo
> >  * Jeremy Mitchell
> >  * Leif Hedstrom  
> >  * Mark Torluemke 
> >  * Phil Sorber
> >  * Steve Malenfant
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed
> > to the office of Vice President, Apache Traffic Control, to serve in
> > accordance with and subject to the direction of the Board of Directors
> > and the Bylaws of the Foundation until death, resignation, retirement,
> > removal or disqualification, or until a successor is appointed; and be
> > it further
> >
> > RESOLVED, that the initial Apache Traffic Control PMC be and hereby is
> > tasked with the creation of a set of bylaws intended to encourage open
> > development and increased participation in the Apache Traffic Control
> > Project; and be it further
> >
> > RESOLVED, that the Apache Traffic Control Project be and hereby is
> > tasked with the migration and rationalization of the Apache Incubator
> > Traffic Control podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > Traffic Control podling encumbered upon the Apache Incubator PMC are
> > hereafter discharged.
> >
> >
> >
>

Re: [VOTE] Resolution for Traffic Control graduation to TLP

[Dave Neuman]

+1

On Mon, Apr 2, 2018 at 2:11 PM, David Neuman 
wrote:

> Dear Traffic Control community members:
>
> I would like to call a vote on the resolution for Traffic Control to
> graduate from to an Apache TLP.  We have already voted on whether or not we
> should start the graduation process [1] and this is the next step.  Please
> see the resolution below and vote as follows:
>
> [ ] +1 Graduate Traffic Control from the incubator
> [ ] +0 No Opinion
> [ ] -1 Do not graduate Traffic Control from the incubator (please provide
> a reason)
>
> The vote is open for a minimum of 72 hours and will need at least 3 more
> +1 votes than -1 votes from PMC members to succeed.
>
> If this VOTE succeeds, a similar VOTE will be started on the
> gene...@incubator.apache.org mailing list. If that VOTE succeeds, a
> resolution will be included in the next Apache Board Meeting.
>
> Please feel free to reach out with any questions.
>
> Thanks,
> Dave
>
> [1] https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa207
> 23eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E
>
> -
>
> Establish the Apache Traffic Control Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to building, monitoring, configuring, and provisioning a large
> scale content delivery network (CDN)..
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Traffic Control Project", be and
> hereby is established pursuant to Bylaws of the Foundation; and be it
> further
>
> RESOLVED, that the Apache Traffic Control Project be and hereby is
> responsible for the creation and maintenance of software related to
> building, monitoring, configuring, and provisioning a large scale
> content delivery network (CDN).; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Traffic Control" be
> and hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Traffic
> Control Project, and to have primary responsibility for management of
> the projects within the scope of responsibility of the Apache Traffic
> Control Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Traffic Control
> Project:
>
>  * Dan Kirkwood   
>  * David Neuman   
>  * Dewayne Richardson 
>  * Eric Covener   
>  * Eric Friedrich 
>  * Hank Beatty
>  * Jan van Doorn  
>  * Jeff Elsloo
>  * Jeremy Mitchell
>  * Leif Hedstrom  
>  * Mark Torluemke 
>  * Phil Sorber
>  * Steve Malenfant
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed
> to the office of Vice President, Apache Traffic Control, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the initial Apache Traffic Control PMC be and hereby is
> tasked with the creation of a set of bylaws intended to encourage open
> development and increased participation in the Apache Traffic Control
> Project; and be it further
>
> RESOLVED, that the Apache Traffic Control Project be and hereby is
> tasked with the migration and rationalization of the Apache Incubator
> Traffic Control podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Traffic Control podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>
>
>

[VOTE] Resolution for Traffic Control graduation to TLP

[David Neuman]

Dear Traffic Control community members:

I would like to call a vote on the resolution for Traffic Control to
graduate from to an Apache TLP.  We have already voted on whether or not we
should start the graduation process [1] and this is the next step.  Please
see the resolution below and vote as follows:

[ ] +1 Graduate Traffic Control from the incubator
[ ] +0 No Opinion
[ ] -1 Do not graduate Traffic Control from the incubator (please provide a
reason)

The vote is open for a minimum of 72 hours and will need at least 3 more +1
votes than -1 votes from PMC members to succeed.

If this VOTE succeeds, a similar VOTE will be started on the
gene...@incubator.apache.org mailing list. If that VOTE succeeds, a
resolution will be included in the next Apache Board Meeting.

Please feel free to reach out with any questions.

Thanks,
Dave

[1]
https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa20723eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E

-

Establish the Apache Traffic Control Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to building, monitoring, configuring, and provisioning a large
scale content delivery network (CDN)..

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Traffic Control Project", be and
hereby is established pursuant to Bylaws of the Foundation; and be it
further

RESOLVED, that the Apache Traffic Control Project be and hereby is
responsible for the creation and maintenance of software related to
building, monitoring, configuring, and provisioning a large scale
content delivery network (CDN).; and be it further

RESOLVED, that the office of "Vice President, Apache Traffic Control" be
and hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache Traffic
Control Project, and to have primary responsibility for management of
the projects within the scope of responsibility of the Apache Traffic
Control Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Traffic Control
Project:

 * Dan Kirkwood   
 * David Neuman   
 * Dewayne Richardson 
 * Eric Covener   
 * Eric Friedrich 
 * Hank Beatty
 * Jan van Doorn  
 * Jeff Elsloo
 * Jeremy Mitchell
 * Leif Hedstrom  
 * Mark Torluemke 
 * Phil Sorber
 * Steve Malenfant

NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed
to the office of Vice President, Apache Traffic Control, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed; and be
it further

RESOLVED, that the initial Apache Traffic Control PMC be and hereby is
tasked with the creation of a set of bylaws intended to encourage open
development and increased participation in the Apache Traffic Control
Project; and be it further

RESOLVED, that the Apache Traffic Control Project be and hereby is
tasked with the migration and rationalization of the Apache Incubator
Traffic Control podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
Traffic Control podling encumbered upon the Apache Incubator PMC are
hereafter discharged.

Re: Podling Report Reminder - April 2018

[Dave Neuman]

Hey All,
I have published a draft of our report here:
https://wiki.apache.org/incubator/April2018
I know that it is short notice, but please take a look and let me know if
you see anything that you would like updated or fixed.

Thanks,
Dave

On Fri, Mar 30, 2018 at 1:22 AM,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 18 April 2018, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, April 04).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/April2018
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: [VOTE] Resolution for Traffic Control graduation to TLP

[Jan van Doorn]

+1

On 2018/04/02 20:11:55, David Neuman  wrote:
> Dear Traffic Control community members:>
>
> I would like to call a vote on the resolution for Traffic Control to>
> graduate from to an Apache TLP. We have already voted on whether or 
not we>
> should start the graduation process [1] and this is the next step. 
Please>

> see the resolution below and vote as follows:>
>
> [ ] +1 Graduate Traffic Control from the incubator>
> [ ] +0 No Opinion>
> [ ] -1 Do not graduate Traffic Control from the incubator (please 
provide a>

> reason)>
>
> The vote is open for a minimum of 72 hours and will need at least 3 
more +1>

> votes than -1 votes from PMC members to succeed.>
>
> If this VOTE succeeds, a similar VOTE will be started on the>
> gene...@incubator.apache.org mailing list. If that VOTE succeeds, a>
> resolution will be included in the next Apache Board Meeting.>
>
> Please feel free to reach out with any questions.>
>
> Thanks,>
> Dave>
>
> [1]>
> 
https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa20723eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E> 


>
> ->
>
> Establish the Apache Traffic Control Project>
>
> WHEREAS, the Board of Directors deems it to be in the best interests of>
> the Foundation and consistent with the Foundation's purpose to 
establish>
> a Project Management Committee charged with the creation and 
maintenance>

> of open-source software, for distribution at no charge to the public,>
> related to building, monitoring, configuring, and provisioning a large>
> scale content delivery network (CDN)..>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee>
> (PMC), to be known as the "Apache Traffic Control Project", be and>
> hereby is established pursuant to Bylaws of the Foundation; and be it>
> further>
>
> RESOLVED, that the Apache Traffic Control Project be and hereby is>
> responsible for the creation and maintenance of software related to>
> building, monitoring, configuring, and provisioning a large scale>
> content delivery network (CDN).; and be it further>
>
> RESOLVED, that the office of "Vice President, Apache Traffic Control" 
be>

> and hereby is created, the person holding such office to serve at the>
> direction of the Board of Directors as the chair of the Apache Traffic>
> Control Project, and to have primary responsibility for management of>
> the projects within the scope of responsibility of the Apache Traffic>
> Control Project; and be it further>
>
> RESOLVED, that the persons listed immediately below be and hereby are>
> appointed to serve as the initial members of the Apache Traffic Control>
> Project:>
>
> * Dan Kirkwood >
> * David Neuman >
> * Dewayne Richardson >
> * Eric Covener >
> * Eric Friedrich >
> * Hank Beatty >
> * Jan van Doorn >
> * Jeff Elsloo >
> * Jeremy Mitchell >
> * Leif Hedstrom >
> * Mark Torluemke >
> * Phil Sorber >
> * Steve Malenfant >
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed>
> to the office of Vice President, Apache Traffic Control, to serve in>
> accordance with and subject to the direction of the Board of Directors>
> and the Bylaws of the Foundation until death, resignation, retirement,>
> removal or disqualification, or until a successor is appointed; and be>
> it further>
>
> RESOLVED, that the initial Apache Traffic Control PMC be and hereby is>
> tasked with the creation of a set of bylaws intended to encourage open>
> development and increased participation in the Apache Traffic Control>
> Project; and be it further>
>
> RESOLVED, that the Apache Traffic Control Project be and hereby is>
> tasked with the migration and rationalization of the Apache Incubator>
> Traffic Control podling; and be it further>
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator>
> Traffic Control podling encumbered upon the Apache Incubator PMC are>
> hereafter discharged.>
>

Re: [VOTE] Resolution for Traffic Control graduation to TLP

[Eric Covener]

On Mon, Apr 2, 2018 at 4:11 PM, David Neuman  wrote:
> Dear Traffic Control community members:
>
> I would like to call a vote on the resolution for Traffic Control to
> graduate from to an Apache TLP.  We have already voted on whether or not we
> should start the graduation process [1] and this is the next step.  Please
> see the resolution below and vote as follows:
>
> [ ] +1 Graduate Traffic Control from the incubator
> [ ] +0 No Opinion
> [ ] -1 Do not graduate Traffic Control from the incubator (please provide a
> reason)
>

+1

Re: [VOTE] Resolution for Traffic Control graduation to TLP

[Jeff Elsloo]

+1
--
Thanks,
Jeff


On Mon, Apr 2, 2018 at 2:53 PM, Dan Kirkwood  wrote:
> +1
>
> On Mon, Apr 2, 2018 at 2:12 PM, Dave Neuman  wrote:
>
>> +1
>>
>> On Mon, Apr 2, 2018 at 2:11 PM, David Neuman 
>> wrote:
>>
>> > Dear Traffic Control community members:
>> >
>> > I would like to call a vote on the resolution for Traffic Control to
>> > graduate from to an Apache TLP.  We have already voted on whether or not
>> we
>> > should start the graduation process [1] and this is the next step.
>> Please
>> > see the resolution below and vote as follows:
>> >
>> > [ ] +1 Graduate Traffic Control from the incubator
>> > [ ] +0 No Opinion
>> > [ ] -1 Do not graduate Traffic Control from the incubator (please provide
>> > a reason)
>> >
>> > The vote is open for a minimum of 72 hours and will need at least 3 more
>> > +1 votes than -1 votes from PMC members to succeed.
>> >
>> > If this VOTE succeeds, a similar VOTE will be started on the
>> > gene...@incubator.apache.org mailing list. If that VOTE succeeds, a
>> > resolution will be included in the next Apache Board Meeting.
>> >
>> > Please feel free to reach out with any questions.
>> >
>> > Thanks,
>> > Dave
>> >
>> > [1] https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa207
>> > 23eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E
>> >
>> > -
>> >
>> > Establish the Apache Traffic Control Project
>> >
>> > WHEREAS, the Board of Directors deems it to be in the best interests of
>> > the Foundation and consistent with the Foundation's purpose to establish
>> > a Project Management Committee charged with the creation and maintenance
>> > of open-source software, for distribution at no charge to the public,
>> > related to building, monitoring, configuring, and provisioning a large
>> > scale content delivery network (CDN)..
>> >
>> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> > (PMC), to be known as the "Apache Traffic Control Project", be and
>> > hereby is established pursuant to Bylaws of the Foundation; and be it
>> > further
>> >
>> > RESOLVED, that the Apache Traffic Control Project be and hereby is
>> > responsible for the creation and maintenance of software related to
>> > building, monitoring, configuring, and provisioning a large scale
>> > content delivery network (CDN).; and be it further
>> >
>> > RESOLVED, that the office of "Vice President, Apache Traffic Control" be
>> > and hereby is created, the person holding such office to serve at the
>> > direction of the Board of Directors as the chair of the Apache Traffic
>> > Control Project, and to have primary responsibility for management of
>> > the projects within the scope of responsibility of the Apache Traffic
>> > Control Project; and be it further
>> >
>> > RESOLVED, that the persons listed immediately below be and hereby are
>> > appointed to serve as the initial members of the Apache Traffic Control
>> > Project:
>> >
>> >  * Dan Kirkwood   
>> >  * David Neuman   
>> >  * Dewayne Richardson 
>> >  * Eric Covener   
>> >  * Eric Friedrich 
>> >  * Hank Beatty
>> >  * Jan van Doorn  
>> >  * Jeff Elsloo
>> >  * Jeremy Mitchell
>> >  * Leif Hedstrom  
>> >  * Mark Torluemke 
>> >  * Phil Sorber
>> >  * Steve Malenfant
>> >
>> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed
>> > to the office of Vice President, Apache Traffic Control, to serve in
>> > accordance with and subject to the direction of the Board of Directors
>> > and the Bylaws of the Foundation until death, resignation, retirement,
>> > removal or disqualification, or until a successor is appointed; and be
>> > it further
>> >
>> > RESOLVED, that the initial Apache Traffic Control PMC be and hereby is
>> > tasked with the creation of a set of bylaws intended to encourage open
>> > development and increased participation in the Apache Traffic Control
>> > Project; and be it further
>> >
>> > RESOLVED, that the Apache Traffic Control Project be and hereby is
>> > tasked with the migration and rationalization of the Apache Incubator
>> > Traffic Control podling; and be it further
>> >
>> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> > Traffic Control podling encumbered upon the Apache Incubator PMC are
>> > hereafter discharged.
>> >
>> >
>> >
>>

Re: Traffic Server Secondary Streaming IPs Design

[Eric Friedrich (efriedri)]

For our particular use case, it is important that if a secondary IP is down, 
the traffic does not move to the primary IP.

This use case relates to use of the source IP address to differentiate traffic 
for billing purposes. We don’t want traffic to move to the primary IP as this 
would miscategorize the traffic. 

—Eric

> On Apr 2, 2018, at 4:39 PM, Nir Sopher  wrote:
> 
> Hi Zhilin,
> 
> I took a quick look into the spec. Hope to have the opportunity to dive
> deeper into it soon so we can further discuss it.
> 
> For now I have a 2 questions.
> In the spec, you refer to "secondary interfaces", and you have a list of
> secondary interfaces added.
> IIUC the secondary interfaces are used as long as they are available, and
> when down, you move to the primary interface.
> 
> Why not, instead of holding a secondary interfaces table, move all
> interfaces to a separate table? Primary and secondary.
> For each interface you can hold:
> 
>   - Server id
>   - name (e.g. eth0)
>   - IPv6
>   - IPv4
>   - Priority (Integer as flexible as you wish: e.g. "1" for "secondary",
>   "2" for "primary" in your example,)
> 
> 
> Additionally, it is not clear to me what happens if one of the interfaces
> fails?
> Does every interface has a unique DNS name? If an interface fails, are
> redirects
> sent only to the available (secondary) interfaces?
> 
> Thanks,
> Nir
> 
> 
> On Mon, Apr 2, 2018 at 10:21 AM, Zhilin Huang (zhilhuan) > wrote:
> 
>> Hi Guys,
>> 
>> This was originally posted in another discussion. Resend this in a
>> standalone topic to catch more awareness. The link for the design doc:
>> https://docs.google.com/document/d/1vgq-pGNoLLYf7Y3cu5hWu67TUKpN5hucrp
>> -ZS9nSsd4/edit?usp=sharing
>> 
>> 
>> Short summary for the feature design:
>> ---
>> There is feature request from market to add secondary IPs support on edge
>> cache servers, and the functionality to assign a delivery service to a
>> secondary IP of an edge cache.
>> 
>> This feature requires Traffic Ops implementation to support secondary IP
>> configuration for edge cache, and delivery service assignment to secondary
>> IP.
>> 
>> Traffic Monitor should also monitor connectivity of secondary IPs
>> configured. And Traffic Router needs support to resolve streamer FQDN to
>> secondary IP assigned in a delivery service.
>> 
>> Traffic Server should record the IP serving client request. And should
>> reject request to an unassigned IP for a delivery service.
>> 
>> This design has taken compatibility into consideration: if no secondary IP
>> configured, or some parts of the system has not been upgraded to the
>> version supports this feature, the traffic will be served by primary IPs as
>> before.
>> ---
>> 
>> Much appreciated and welcome to any comments. If no major objections, we
>> planned to start coding this week.
>> 
>> Thanks,
>> Zhilin
>> 
>> 

Re: [VOTE] Resolution for Traffic Control graduation to TLP

[Eric Friedrich (efriedri)]

+1
> On Apr 2, 2018, at 4:11 PM, David Neuman  wrote:
> 
> Dear Traffic Control community members:
> 
> I would like to call a vote on the resolution for Traffic Control to
> graduate from to an Apache TLP.  We have already voted on whether or not we
> should start the graduation process [1] and this is the next step.  Please
> see the resolution below and vote as follows:
> 
> [ ] +1 Graduate Traffic Control from the incubator
> [ ] +0 No Opinion
> [ ] -1 Do not graduate Traffic Control from the incubator (please provide a
> reason)
> 
> The vote is open for a minimum of 72 hours and will need at least 3 more +1
> votes than -1 votes from PMC members to succeed.
> 
> If this VOTE succeeds, a similar VOTE will be started on the
> gene...@incubator.apache.org mailing list. If that VOTE succeeds, a
> resolution will be included in the next Apache Board Meeting.
> 
> Please feel free to reach out with any questions.
> 
> Thanks,
> Dave
> 
> [1]
> https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa20723eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E
> 
> -
> 
> Establish the Apache Traffic Control Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to building, monitoring, configuring, and provisioning a large
> scale content delivery network (CDN)..
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Traffic Control Project", be and
> hereby is established pursuant to Bylaws of the Foundation; and be it
> further
> 
> RESOLVED, that the Apache Traffic Control Project be and hereby is
> responsible for the creation and maintenance of software related to
> building, monitoring, configuring, and provisioning a large scale
> content delivery network (CDN).; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Traffic Control" be
> and hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Traffic
> Control Project, and to have primary responsibility for management of
> the projects within the scope of responsibility of the Apache Traffic
> Control Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Traffic Control
> Project:
> 
> * Dan Kirkwood   
> * David Neuman   
> * Dewayne Richardson 
> * Eric Covener   
> * Eric Friedrich 
> * Hank Beatty
> * Jan van Doorn  
> * Jeff Elsloo
> * Jeremy Mitchell
> * Leif Hedstrom  
> * Mark Torluemke 
> * Phil Sorber
> * Steve Malenfant
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed
> to the office of Vice President, Apache Traffic Control, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
> 
> RESOLVED, that the initial Apache Traffic Control PMC be and hereby is
> tasked with the creation of a set of bylaws intended to encourage open
> development and increased participation in the Apache Traffic Control
> Project; and be it further
> 
> RESOLVED, that the Apache Traffic Control Project be and hereby is
> tasked with the migration and rationalization of the Apache Incubator
> Traffic Control podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Traffic Control podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.

Re: [VOTE] Resolution for Traffic Control graduation to TLP

[John Rushford]

+1

> On Apr 2, 2018, at 7:07 PM, Eric Friedrich (efriedri)  
> wrote:
> 
> +1
>> On Apr 2, 2018, at 4:11 PM, David Neuman  wrote:
>> 
>> Dear Traffic Control community members:
>> 
>> I would like to call a vote on the resolution for Traffic Control to
>> graduate from to an Apache TLP.  We have already voted on whether or not we
>> should start the graduation process [1] and this is the next step.  Please
>> see the resolution below and vote as follows:
>> 
>> [ ] +1 Graduate Traffic Control from the incubator
>> [ ] +0 No Opinion
>> [ ] -1 Do not graduate Traffic Control from the incubator (please provide a
>> reason)
>> 
>> The vote is open for a minimum of 72 hours and will need at least 3 more +1
>> votes than -1 votes from PMC members to succeed.
>> 
>> If this VOTE succeeds, a similar VOTE will be started on the
>> gene...@incubator.apache.org mailing list. If that VOTE succeeds, a
>> resolution will be included in the next Apache Board Meeting.
>> 
>> Please feel free to reach out with any questions.
>> 
>> Thanks,
>> Dave
>> 
>> [1]
>> https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa20723eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E
>> 
>> -
>> 
>> Establish the Apache Traffic Control Project
>> 
>> WHEREAS, the Board of Directors deems it to be in the best interests of
>> the Foundation and consistent with the Foundation's purpose to establish
>> a Project Management Committee charged with the creation and maintenance
>> of open-source software, for distribution at no charge to the public,
>> related to building, monitoring, configuring, and provisioning a large
>> scale content delivery network (CDN)..
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> (PMC), to be known as the "Apache Traffic Control Project", be and
>> hereby is established pursuant to Bylaws of the Foundation; and be it
>> further
>> 
>> RESOLVED, that the Apache Traffic Control Project be and hereby is
>> responsible for the creation and maintenance of software related to
>> building, monitoring, configuring, and provisioning a large scale
>> content delivery network (CDN).; and be it further
>> 
>> RESOLVED, that the office of "Vice President, Apache Traffic Control" be
>> and hereby is created, the person holding such office to serve at the
>> direction of the Board of Directors as the chair of the Apache Traffic
>> Control Project, and to have primary responsibility for management of
>> the projects within the scope of responsibility of the Apache Traffic
>> Control Project; and be it further
>> 
>> RESOLVED, that the persons listed immediately below be and hereby are
>> appointed to serve as the initial members of the Apache Traffic Control
>> Project:
>> 
>> * Dan Kirkwood   
>> * David Neuman   
>> * Dewayne Richardson 
>> * Eric Covener   
>> * Eric Friedrich 
>> * Hank Beatty
>> * Jan van Doorn  
>> * Jeff Elsloo
>> * Jeremy Mitchell
>> * Leif Hedstrom  
>> * Mark Torluemke 
>> * Phil Sorber
>> * Steve Malenfant
>> 
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed
>> to the office of Vice President, Apache Traffic Control, to serve in
>> accordance with and subject to the direction of the Board of Directors
>> and the Bylaws of the Foundation until death, resignation, retirement,
>> removal or disqualification, or until a successor is appointed; and be
>> it further
>> 
>> RESOLVED, that the initial Apache Traffic Control PMC be and hereby is
>> tasked with the creation of a set of bylaws intended to encourage open
>> development and increased participation in the Apache Traffic Control
>> Project; and be it further
>> 
>> RESOLVED, that the Apache Traffic Control Project be and hereby is
>> tasked with the migration and rationalization of the Apache Incubator
>> Traffic Control podling; and be it further
>> 
>> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> Traffic Control podling encumbered upon the Apache Incubator PMC are
>> hereafter discharged.
>