You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficcontrol.apache.org by Jeff Elsloo <el...@apache.org> on 2018/06/05 16:03:54 UTC
[VOTE] Update Traffic Control to Version 3.0
In light of the major changes introduced into Traffic Router with PR
2331, I would like to call a vote to increase the major version of the
project to 3.0.0. Also note that this version would represent the
first release without official support for CentOS 6.x, though
components might still continue to work. From 3.0.0 forward, only
CentOS 7.x will be officially supported by the project.
This impacts versioning of all components, so if other components are
not ready to make major breaking changes during this transition, we
would need to do so under another major version change in the future.
I'd like to call this vote on Friday, so I will leave this open for 72 hours.
--
Thanks,
Jeff
Re: [EXTERNAL] Re: [VOTE] Update Traffic Control to Version 3.0
Posted by "Schmidt, Andrew (Contractor)" <An...@comcast.com>.
+1
On 8/13/18, 8:52 AM, "Jeff Elsloo" <el...@apache.org> wrote:
Hi all,
It's a little late, but I finally opened the PR to update the version
of the Traffic Control project to 3.0.0 [1]. Please let me know if you
have any issues or concerns.
As this vote has already passed, my intent is to get this merged
quickly, followed closely by the Tomcat 8.5 PR [2], which necessitated
the change.
[1] https://github.com/apache/trafficcontrol/pull/2660
[2] https://github.com/apache/trafficcontrol/pull/2331
--
Thanks,
Jeff
On Fri, Jun 8, 2018 at 10:12 AM Jeff Elsloo <el...@apache.org> wrote:
>
> I'm calling this vote as passed as we received no -1s and 6 +1s.
> Thanks to everyone for participating in the discussion, and as
> mentioned, our hope is that the transition is as painless as possible.
>
> We will coordinate the actual act of updating to 3.0.0 so that it
> isn't a surprise when the commit comes through. I was planning to do
> this myself, perhaps next week.
> --
> Thanks,
> Jeff
>
>
> On Fri, Jun 8, 2018 at 9:35 AM, Dan Kirkwood <da...@gmail.com> wrote:
> > +1
> >
> > On Fri, Jun 8, 2018 at 9:19 AM Eric Friedrich (efriedri) <ef...@cisco.com>
> > wrote:
> >
> >> +1
> >>
> >> With the caveat that we maintain an upgrade process when we start
> >> deprecating APIs between components.
> >>
> >> —Eric
> >>
> >> > On Jun 7, 2018, at 2:11 PM, Dewayne Richardson <de...@apache.org>
> >> wrote:
> >> >
> >> > +1, this will allow us to do a better job with the API's
> >> >
> >> > On Tue, Jun 5, 2018 at 10:03 AM Jeff Elsloo <el...@apache.org> wrote:
> >> >
> >> >> In light of the major changes introduced into Traffic Router with PR
> >> >> 2331, I would like to call a vote to increase the major version of the
> >> >> project to 3.0.0. Also note that this version would represent the
> >> >> first release without official support for CentOS 6.x, though
> >> >> components might still continue to work. From 3.0.0 forward, only
> >> >> CentOS 7.x will be officially supported by the project.
> >> >>
> >> >> This impacts versioning of all components, so if other components are
> >> >> not ready to make major breaking changes during this transition, we
> >> >> would need to do so under another major version change in the future.
> >> >>
> >> >> I'd like to call this vote on Friday, so I will leave this open for 72
> >> >> hours.
> >> >> --
> >> >> Thanks,
> >> >> Jeff
> >> >>
> >>
> >>
Re: [VOTE] Update Traffic Control to Version 3.0
Posted by Jeff Elsloo <el...@apache.org>.
Hi all,
It's a little late, but I finally opened the PR to update the version
of the Traffic Control project to 3.0.0 [1]. Please let me know if you
have any issues or concerns.
As this vote has already passed, my intent is to get this merged
quickly, followed closely by the Tomcat 8.5 PR [2], which necessitated
the change.
[1] https://github.com/apache/trafficcontrol/pull/2660
[2] https://github.com/apache/trafficcontrol/pull/2331
--
Thanks,
Jeff
On Fri, Jun 8, 2018 at 10:12 AM Jeff Elsloo <el...@apache.org> wrote:
>
> I'm calling this vote as passed as we received no -1s and 6 +1s.
> Thanks to everyone for participating in the discussion, and as
> mentioned, our hope is that the transition is as painless as possible.
>
> We will coordinate the actual act of updating to 3.0.0 so that it
> isn't a surprise when the commit comes through. I was planning to do
> this myself, perhaps next week.
> --
> Thanks,
> Jeff
>
>
> On Fri, Jun 8, 2018 at 9:35 AM, Dan Kirkwood <da...@gmail.com> wrote:
> > +1
> >
> > On Fri, Jun 8, 2018 at 9:19 AM Eric Friedrich (efriedri) <ef...@cisco.com>
> > wrote:
> >
> >> +1
> >>
> >> With the caveat that we maintain an upgrade process when we start
> >> deprecating APIs between components.
> >>
> >> —Eric
> >>
> >> > On Jun 7, 2018, at 2:11 PM, Dewayne Richardson <de...@apache.org>
> >> wrote:
> >> >
> >> > +1, this will allow us to do a better job with the API's
> >> >
> >> > On Tue, Jun 5, 2018 at 10:03 AM Jeff Elsloo <el...@apache.org> wrote:
> >> >
> >> >> In light of the major changes introduced into Traffic Router with PR
> >> >> 2331, I would like to call a vote to increase the major version of the
> >> >> project to 3.0.0. Also note that this version would represent the
> >> >> first release without official support for CentOS 6.x, though
> >> >> components might still continue to work. From 3.0.0 forward, only
> >> >> CentOS 7.x will be officially supported by the project.
> >> >>
> >> >> This impacts versioning of all components, so if other components are
> >> >> not ready to make major breaking changes during this transition, we
> >> >> would need to do so under another major version change in the future.
> >> >>
> >> >> I'd like to call this vote on Friday, so I will leave this open for 72
> >> >> hours.
> >> >> --
> >> >> Thanks,
> >> >> Jeff
> >> >>
> >>
> >>
Re: [VOTE] Update Traffic Control to Version 3.0
Posted by Jeff Elsloo <el...@apache.org>.
I'm calling this vote as passed as we received no -1s and 6 +1s.
Thanks to everyone for participating in the discussion, and as
mentioned, our hope is that the transition is as painless as possible.
We will coordinate the actual act of updating to 3.0.0 so that it
isn't a surprise when the commit comes through. I was planning to do
this myself, perhaps next week.
--
Thanks,
Jeff
On Fri, Jun 8, 2018 at 9:35 AM, Dan Kirkwood <da...@gmail.com> wrote:
> +1
>
> On Fri, Jun 8, 2018 at 9:19 AM Eric Friedrich (efriedri) <ef...@cisco.com>
> wrote:
>
>> +1
>>
>> With the caveat that we maintain an upgrade process when we start
>> deprecating APIs between components.
>>
>> —Eric
>>
>> > On Jun 7, 2018, at 2:11 PM, Dewayne Richardson <de...@apache.org>
>> wrote:
>> >
>> > +1, this will allow us to do a better job with the API's
>> >
>> > On Tue, Jun 5, 2018 at 10:03 AM Jeff Elsloo <el...@apache.org> wrote:
>> >
>> >> In light of the major changes introduced into Traffic Router with PR
>> >> 2331, I would like to call a vote to increase the major version of the
>> >> project to 3.0.0. Also note that this version would represent the
>> >> first release without official support for CentOS 6.x, though
>> >> components might still continue to work. From 3.0.0 forward, only
>> >> CentOS 7.x will be officially supported by the project.
>> >>
>> >> This impacts versioning of all components, so if other components are
>> >> not ready to make major breaking changes during this transition, we
>> >> would need to do so under another major version change in the future.
>> >>
>> >> I'd like to call this vote on Friday, so I will leave this open for 72
>> >> hours.
>> >> --
>> >> Thanks,
>> >> Jeff
>> >>
>>
>>
Re: [VOTE] Update Traffic Control to Version 3.0
Posted by Dan Kirkwood <da...@gmail.com>.
+1
On Fri, Jun 8, 2018 at 9:19 AM Eric Friedrich (efriedri) <ef...@cisco.com>
wrote:
> +1
>
> With the caveat that we maintain an upgrade process when we start
> deprecating APIs between components.
>
> —Eric
>
> > On Jun 7, 2018, at 2:11 PM, Dewayne Richardson <de...@apache.org>
> wrote:
> >
> > +1, this will allow us to do a better job with the API's
> >
> > On Tue, Jun 5, 2018 at 10:03 AM Jeff Elsloo <el...@apache.org> wrote:
> >
> >> In light of the major changes introduced into Traffic Router with PR
> >> 2331, I would like to call a vote to increase the major version of the
> >> project to 3.0.0. Also note that this version would represent the
> >> first release without official support for CentOS 6.x, though
> >> components might still continue to work. From 3.0.0 forward, only
> >> CentOS 7.x will be officially supported by the project.
> >>
> >> This impacts versioning of all components, so if other components are
> >> not ready to make major breaking changes during this transition, we
> >> would need to do so under another major version change in the future.
> >>
> >> I'd like to call this vote on Friday, so I will leave this open for 72
> >> hours.
> >> --
> >> Thanks,
> >> Jeff
> >>
>
>
Re: [VOTE] Update Traffic Control to Version 3.0
Posted by "Eric Friedrich (efriedri)" <ef...@cisco.com>.
+1
With the caveat that we maintain an upgrade process when we start deprecating APIs between components.
—Eric
> On Jun 7, 2018, at 2:11 PM, Dewayne Richardson <de...@apache.org> wrote:
>
> +1, this will allow us to do a better job with the API's
>
> On Tue, Jun 5, 2018 at 10:03 AM Jeff Elsloo <el...@apache.org> wrote:
>
>> In light of the major changes introduced into Traffic Router with PR
>> 2331, I would like to call a vote to increase the major version of the
>> project to 3.0.0. Also note that this version would represent the
>> first release without official support for CentOS 6.x, though
>> components might still continue to work. From 3.0.0 forward, only
>> CentOS 7.x will be officially supported by the project.
>>
>> This impacts versioning of all components, so if other components are
>> not ready to make major breaking changes during this transition, we
>> would need to do so under another major version change in the future.
>>
>> I'd like to call this vote on Friday, so I will leave this open for 72
>> hours.
>> --
>> Thanks,
>> Jeff
>>
Re: [VOTE] Update Traffic Control to Version 3.0
Posted by Dewayne Richardson <de...@apache.org>.
+1, this will allow us to do a better job with the API's
On Tue, Jun 5, 2018 at 10:03 AM Jeff Elsloo <el...@apache.org> wrote:
> In light of the major changes introduced into Traffic Router with PR
> 2331, I would like to call a vote to increase the major version of the
> project to 3.0.0. Also note that this version would represent the
> first release without official support for CentOS 6.x, though
> components might still continue to work. From 3.0.0 forward, only
> CentOS 7.x will be officially supported by the project.
>
> This impacts versioning of all components, so if other components are
> not ready to make major breaking changes during this transition, we
> would need to do so under another major version change in the future.
>
> I'd like to call this vote on Friday, so I will leave this open for 72
> hours.
> --
> Thanks,
> Jeff
>
Re: [VOTE] Update Traffic Control to Version 3.0
Posted by Robert Butts <ro...@gmail.com>.
+1 Dropping support is breaking change, and needs a major version
increment, per Semantic Versioning.
On Tue, Jun 5, 2018 at 10:03 AM, Jeff Elsloo <el...@apache.org> wrote:
> In light of the major changes introduced into Traffic Router with PR
> 2331, I would like to call a vote to increase the major version of the
> project to 3.0.0. Also note that this version would represent the
> first release without official support for CentOS 6.x, though
> components might still continue to work. From 3.0.0 forward, only
> CentOS 7.x will be officially supported by the project.
>
> This impacts versioning of all components, so if other components are
> not ready to make major breaking changes during this transition, we
> would need to do so under another major version change in the future.
>
> I'd like to call this vote on Friday, so I will leave this open for 72
> hours.
> --
> Thanks,
> Jeff
>
Re: [VOTE] Update Traffic Control to Version 3.0
Posted by Robert Butts <ro...@gmail.com>.
>Does this also present an opportunity to do some breaking API changes for
Traffic Ops that we’ve been wanting to do?
@jvd Technically yes, but I'd vote we don't, because it's going to add a
lot more work to Self-Service to try to port APIs, maintain two major API
versions for at least a major release, and make the Self-Service changes to
both. I'd vote we wait until Self Service is done modifying the API
implementation, before creating API 2.0.
On Thu, Jun 7, 2018 at 11:45 AM, Eric Friedrich (efriedri) <
efriedri@cisco.com> wrote:
> We need to give our users some short-lived guarantee about backwards
> compatibility because it is necessary for upgrade.
>
> Can we agree
> “All Traffic Control 2.y components will work with a Traffic Ops 3.0”
> with the following constraints:
> - 2.y is the last release in the 2.x train
> - 3.0 is exactly 3.0 and not 3.1, 3.2, 3.3, etc. In 3.1 all the
> deprecated 2.x APIs can get removed.
>
> (Alternately would be “all traffic control 3.0 components will work with a
> Traffic Ops 2.y” but we normally upgrade TO first in each release cycle)
>
> Without this promise, how else would we upgrade from 2 to 3?
>
> —Eric
>
>
>
> > On Jun 7, 2018, at 12:05 PM, Dave Neuman <ne...@apache.org> wrote:
> >
> > Since we are increasing the major version, I would assume that 2.x
> > components will not work with 3.x components. The reality may be that
> they
> > do work together, but I wouldn't count on it.
> >
> > In addition to what was mentioned above I think that we should including
> > deprecating support for the Traffic Ops UI in 3.0. Once 3.0 is released
> we
> > should only be using Traffic Portal as our UI.
> >
> > With that being said, +1 on the move to 3.0
> >
> > Thanks,
> > Dave
> >
> > On Thu, Jun 7, 2018 at 8:48 AM, Eric Friedrich (efriedri) <
> > efriedri@cisco.com> wrote:
> >
> >> For those of us already on Centos7, what does this mean for
> compatibility
> >> between TC releases?
> >>
> >> On Centos7, will we be able to use 3.0 with 2.x releases as is currently
> >> done today.
> >>
> >> If already on Centos7, What is the upgrade story from 2.2 to 3.0?
> >>
> >> —Eric
> >>
> >>> On Jun 5, 2018, at 12:03 PM, Jeff Elsloo <el...@apache.org> wrote:
> >>>
> >>> In light of the major changes introduced into Traffic Router with PR
> >>> 2331, I would like to call a vote to increase the major version of the
> >>> project to 3.0.0. Also note that this version would represent the
> >>> first release without official support for CentOS 6.x, though
> >>> components might still continue to work. From 3.0.0 forward, only
> >>> CentOS 7.x will be officially supported by the project.
> >>>
> >>> This impacts versioning of all components, so if other components are
> >>> not ready to make major breaking changes during this transition, we
> >>> would need to do so under another major version change in the future.
> >>>
> >>> I'd like to call this vote on Friday, so I will leave this open for 72
> >> hours.
> >>> --
> >>> Thanks,
> >>> Jeff
> >>
> >>
>
>
Re: [VOTE] Update Traffic Control to Version 3.0
Posted by "Eric Friedrich (efriedri)" <ef...@cisco.com>.
We need to give our users some short-lived guarantee about backwards compatibility because it is necessary for upgrade.
Can we agree
“All Traffic Control 2.y components will work with a Traffic Ops 3.0”
with the following constraints:
- 2.y is the last release in the 2.x train
- 3.0 is exactly 3.0 and not 3.1, 3.2, 3.3, etc. In 3.1 all the deprecated 2.x APIs can get removed.
(Alternately would be “all traffic control 3.0 components will work with a Traffic Ops 2.y” but we normally upgrade TO first in each release cycle)
Without this promise, how else would we upgrade from 2 to 3?
—Eric
> On Jun 7, 2018, at 12:05 PM, Dave Neuman <ne...@apache.org> wrote:
>
> Since we are increasing the major version, I would assume that 2.x
> components will not work with 3.x components. The reality may be that they
> do work together, but I wouldn't count on it.
>
> In addition to what was mentioned above I think that we should including
> deprecating support for the Traffic Ops UI in 3.0. Once 3.0 is released we
> should only be using Traffic Portal as our UI.
>
> With that being said, +1 on the move to 3.0
>
> Thanks,
> Dave
>
> On Thu, Jun 7, 2018 at 8:48 AM, Eric Friedrich (efriedri) <
> efriedri@cisco.com> wrote:
>
>> For those of us already on Centos7, what does this mean for compatibility
>> between TC releases?
>>
>> On Centos7, will we be able to use 3.0 with 2.x releases as is currently
>> done today.
>>
>> If already on Centos7, What is the upgrade story from 2.2 to 3.0?
>>
>> —Eric
>>
>>> On Jun 5, 2018, at 12:03 PM, Jeff Elsloo <el...@apache.org> wrote:
>>>
>>> In light of the major changes introduced into Traffic Router with PR
>>> 2331, I would like to call a vote to increase the major version of the
>>> project to 3.0.0. Also note that this version would represent the
>>> first release without official support for CentOS 6.x, though
>>> components might still continue to work. From 3.0.0 forward, only
>>> CentOS 7.x will be officially supported by the project.
>>>
>>> This impacts versioning of all components, so if other components are
>>> not ready to make major breaking changes during this transition, we
>>> would need to do so under another major version change in the future.
>>>
>>> I'd like to call this vote on Friday, so I will leave this open for 72
>> hours.
>>> --
>>> Thanks,
>>> Jeff
>>
>>
Re: [VOTE] Update Traffic Control to Version 3.0
Posted by Dave Neuman <ne...@apache.org>.
Since we are increasing the major version, I would assume that 2.x
components will not work with 3.x components. The reality may be that they
do work together, but I wouldn't count on it.
In addition to what was mentioned above I think that we should including
deprecating support for the Traffic Ops UI in 3.0. Once 3.0 is released we
should only be using Traffic Portal as our UI.
With that being said, +1 on the move to 3.0
Thanks,
Dave
On Thu, Jun 7, 2018 at 8:48 AM, Eric Friedrich (efriedri) <
efriedri@cisco.com> wrote:
> For those of us already on Centos7, what does this mean for compatibility
> between TC releases?
>
> On Centos7, will we be able to use 3.0 with 2.x releases as is currently
> done today.
>
> If already on Centos7, What is the upgrade story from 2.2 to 3.0?
>
> —Eric
>
> > On Jun 5, 2018, at 12:03 PM, Jeff Elsloo <el...@apache.org> wrote:
> >
> > In light of the major changes introduced into Traffic Router with PR
> > 2331, I would like to call a vote to increase the major version of the
> > project to 3.0.0. Also note that this version would represent the
> > first release without official support for CentOS 6.x, though
> > components might still continue to work. From 3.0.0 forward, only
> > CentOS 7.x will be officially supported by the project.
> >
> > This impacts versioning of all components, so if other components are
> > not ready to make major breaking changes during this transition, we
> > would need to do so under another major version change in the future.
> >
> > I'd like to call this vote on Friday, so I will leave this open for 72
> hours.
> > --
> > Thanks,
> > Jeff
>
>
Re: [VOTE] Update Traffic Control to Version 3.0
Posted by "Eric Friedrich (efriedri)" <ef...@cisco.com>.
For those of us already on Centos7, what does this mean for compatibility between TC releases?
On Centos7, will we be able to use 3.0 with 2.x releases as is currently done today.
If already on Centos7, What is the upgrade story from 2.2 to 3.0?
—Eric
> On Jun 5, 2018, at 12:03 PM, Jeff Elsloo <el...@apache.org> wrote:
>
> In light of the major changes introduced into Traffic Router with PR
> 2331, I would like to call a vote to increase the major version of the
> project to 3.0.0. Also note that this version would represent the
> first release without official support for CentOS 6.x, though
> components might still continue to work. From 3.0.0 forward, only
> CentOS 7.x will be officially supported by the project.
>
> This impacts versioning of all components, so if other components are
> not ready to make major breaking changes during this transition, we
> would need to do so under another major version change in the future.
>
> I'd like to call this vote on Friday, so I will leave this open for 72 hours.
> --
> Thanks,
> Jeff