You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficcontrol.apache.org by Andy Schmidt <za...@gmail.com> on 2018/05/25 00:57:26 UTC
[TC-69] Upgrade Tomcat Version for Traffic Router (#925)
Hello,
I have submitted a PR (#2331) for this major upgrade. We are looking to
make this part of the TC 3.0 release because it is a large change and the
update will automatically uninstall older versions of Traffic Router. The
update will upgrade the Tomcat to 8.5.28+ and will require Java 8, CentOs 7
and the installation of OpenSSL, Tomcat Native and APR. Most of this will
be taken care of by the RPM. Here is the migration documentation :
Traffic Router - Migrating to 3.0 <#contents>
Contents
- Traffic Router - Migrating to 3.0 <#traffic-router-migrating-to-3-0>
- Release Notes v3.0 <#release-notes-v3-0>
- System Requirements <#system-requirements>
- Upgrade Procedure <#upgrade-procedure>
- Development Environment Upgrade <#development-environment-upgrade>
Release Notes v3.0 <#contents>
- Replaced custom Java SNI implementation with a native implementation
using tomcat-native, apr (Apache Portable Runtime) and OpenSSL This should
significantly improve the performance of routing ‘https’ delivery services.
- Upgraded to Tomcat 8.5.30
- Separated the Traffic Router installation from the Tomcat deployment
and created a new ‘tomcat’ package for installing Tomcat. Traffic Router
and Tomcat can now be upgraded independently
- Converted Traffic Router to a ‘systemd’ service
- Modified the development test and dev deployment processes to be more
consistent with production
System Requirements <#contents>
- Centos 7.2
- OpenSSL >= 1.0.2 installed
- JDK >= 8.0 installed or available in Yum repository
- APR (Apache Portable Runtime) >= 1.4.8-3 installed or available in Yum
repository
- Tomcat Native >= 1.2.16 installed or available in Yum repository
- tomcat >= 8.5-28 installed or available in Yum repository (This
package is created automatically by the Traffic Router build process)
Upgrade Procedure <#contents>
- upload tomcat.rpm to a Yum repository
- update the traffic_router package
- restore property files
Upload tomcat.rpm
The ‘tomcat’ package gets created when you build Traffic Router. You must
either add it to the yum repo where you keep all of the Traffic Control
packages, or manually copy it to the servers where you will be installing
Traffic Router and run yum install [path to package] It is preferable that
you add it to your Yum repository because then it will be installed
automatically when you perform the Traffic Router update.
Update the traffic_router Package
If openssl, apr, tomcat-native, jdk and tomcat_tr packages are all in an
available repository then you just need to run: yum update traffic_router.
This will first cause the apr, tomcat-native, jdk and tomcat packages to be
installed. When the ‘tomcat’ package runs, it will cause any older versions
of traffic_router or tomcat to be uninstalled. This is because the previous
versions of the traffic_router package included an untracked installation
of tomcat.
Restore Property Files
Replace the Traffic Router properties files with the correct ones for the
CDN. The properties files from the previous install can be found at:
/opt/traffic_router/conf/traffic_ops.properties.rpmsaved &
traffic_monitor.properties.rpmsaved.
Development Environment Upgrade <#contents>
If you already have a development environment set up for the previous
version of Traffic Router, then you will need to get and install these
libraries on your workstation: openssl, apr and tomcat-native. Also,
whenever you run either ‘mvn clean verify’ or ‘TrafficRouterStart’ you will
need to pass a command line parameter telling Java where to look for the
‘tomcat-native’ libraries:mvn clean verify -Djava.library.path=[tomcat
native library path on your box]java -Djava.library.path=[tomcat native
library path on your box] TrafficRouterStart
Re: [EXTERNAL] Re: [TC-69] Upgrade Tomcat Version for Traffic Router (#925)
Posted by Steve Malenfant <sm...@gmail.com>.
Jeff,
It's working as-is for me (functionality). I don't mind creating issues
about installation/upgrade after it is merged.
Steve
On Thu, Jun 14, 2018 at 12:42 PM Jeff Elsloo <el...@apache.org> wrote:
> FYI we currently have a production trial of this PR underway, and will
> be continuing in that direction. I do plan to merge this PR in the
> near future, hopefully next week, so please chime in if you have
> concerns. I expect that we will run into a few issues around some
> install/upgrade cases, and may have to tweak things as we learn more.
> --
> Thanks,
> Jeff
>
>
> On Mon, Jun 4, 2018 at 4:00 PM, Dave Neuman <ne...@apache.org> wrote:
> > +1 on dropping support and updating all versions. Traffic Ops already
> only
> > supports Centos7.0. We talked about this at the summit and I was supposed
> > to start a thread, I apologize for neglecting to do so. I can start a
> new
> > thread if Jeff doesn’t.
> >
> > Thanks,
> > Dave
> >
> > On Mon, Jun 4, 2018 at 17:06 Jeff Elsloo <el...@apache.org> wrote:
> >
> >> There's also the issue of no systemd in CentOS 6.x, so we would have
> >> to not only maintain a different set of dependencies for CentOS 6.x,
> >> but also would have to have separate tooling for both. We used init
> >> previously and moved to systemd with this update, which is yet another
> >> reason to move away from 6.x.
> >>
> >> Also, it appears I misspoke and we cannot version separately like I
> >> had hoped. It appears as though we'd have to update everything to 3.0.
> >> --
> >> Thanks,
> >> Jeff
> >>
> >>
> >> On Mon, Jun 4, 2018 at 1:39 PM, Schmidt, Andrew (Contractor)
> >> <An...@comcast.com> wrote:
> >> > Steve,
> >> > The trickiest part about installing this on centos 6 is getting a the
> >> tomcat-native 1.2.16+ rpm. They don't have one in the EPEL repo for
> centos
> >> 6 so you have to build one for yourself. I did not go that far. So I
> can't
> >> guarantee that someone could actually get this working on 6.x.
> >> >
> >> > I do like the idea of having Traffic Router move to 3.0 before the
> rest
> >> of Traffic Control if that is a real option.
> >> >
> >> > Andy
> >> >
> >> > On 6/4/18, 11:45 AM, "Steve Malenfant" <sm...@gmail.com> wrote:
> >> >
> >> > Jeff,
> >> >
> >> > I have no problem dropping support for 6.x even in 2.3 for Traffic
> >> Router.
> >> > Seems like we drop support for the RPM generation but somebody
> might
> >> still
> >> > be able to install on their 6.x installation manually?
> >> >
> >> > I'll make up some time to test this week.
> >> >
> >> > Steve
> >> >
> >> > On Mon, Jun 4, 2018 at 12:33 PM, Jeff Elsloo <el...@apache.org>
> >> wrote:
> >> >
> >> > > Hi all,
> >> > >
> >> > > It sounds like the main gating item for this is a decision on
> >> whether
> >> > > we can drop support for CentOS prior to 7.x and if that
> >> necessitates
> >> > > updating Traffic Router to 3.0. Then, the larger issue is
> whether
> >> we
> >> > > also update the other components to 3.0 at the same time.
> Should we
> >> > > call a vote for dropping 7.x support and moving to 3.0 for just
> >> > > Traffic Router, or should we do that across the board?
> >> > >
> >> > > Does anyone have any objections to what Andy outlined above?
> >> > > Additionally, I want to be clear that we introduced a new
> >> dependency
> >> > > on an EPEL package (tomcat-native), we packaged Tomcat in its
> own
> >> RPM,
> >> > > and changed the service name from `tomcat` to `traffic_router`.
> >> Most
> >> > > of Tomcat's config now lives right next to the Traffic Router
> >> > > configuration. Other than that, this is a drop in replacement
> for
> >> > > Traffic Router that currently runs on Tomcat 6.0.33.
> >> > >
> >> > > If anyone has the free time to pull down the code, build it, and
> >> test
> >> > > it in their environment, we would really appreciate it.
> >> > > --
> >> > > Thanks,
> >> > > Jeff
> >> > >
> >> > >
> >> > > On Fri, May 25, 2018 at 4:36 PM, Schmidt, Andrew (Contractor)
> >> > > <An...@comcast.com> wrote:
> >> > > > Sounds good Dave. The technical requirement for the version
> >> number is
> >> > > that it needs to have a greater minor number than the version it
> >> replaces
> >> > > so that the RPM install can properly clean up the previous one.
> >> This means
> >> > > it needs to be the first build we release on the new version.
> >> > > >
> >> > > > Andy
> >> > > >
> >> > > > On 5/25/18, 12:38 PM, "Dave Neuman" <ne...@apache.org>
> wrote:
> >> > > >
> >> > > > This is great news, thanks Andy! I am excited to see this
> >> finally
> >> > > get
> >> > > > merged into Traffic Control.
> >> > > > We haven't formally discussed making the next release 3.0,
> >> so I will
> >> > > make
> >> > > > sure to get an email out about that. I think it is the
> >> right thing
> >> > > to do.
> >> > > >
> >> > > > Thanks,
> >> > > > Dave
> >> > > >
> >> > > > On Thu, May 24, 2018 at 6:57 PM, Andy Schmidt <
> >> zapdivi@gmail.com>
> >> > > wrote:
> >> > > >
> >> > > > > Hello,
> >> > > > > I have submitted a PR (#2331) for this major upgrade. We
> >> are
> >> > > looking to
> >> > > > > make this part of the TC 3.0 release because it is a
> large
> >> change
> >> > > and the
> >> > > > > update will automatically uninstall older versions of
> >> Traffic
> >> > > Router. The
> >> > > > > update will upgrade the Tomcat to 8.5.28+ and will
> require
> >> Java 8,
> >> > > CentOs 7
> >> > > > > and the installation of OpenSSL, Tomcat Native and APR.
> >> Most of
> >> > > this will
> >> > > > > be taken care of by the RPM. Here is the migration
> >> documentation :
> >> > > > >
> >> > > > > Traffic Router - Migrating to 3.0 <#contents>
> >> > > > >
> >> > > > > Contents
> >> > > > >
> >> > > > > - Traffic Router - Migrating to 3.0
> >> > > <#traffic-router-migrating-to-3-0>
> >> > > > > - Release Notes v3.0 <#release-notes-v3-0>
> >> > > > > - System Requirements <#system-requirements>
> >> > > > > - Upgrade Procedure <#upgrade-procedure>
> >> > > > > - Development Environment Upgrade
> >> <#development-environment-
> >> > > upgrade>
> >> > > > >
> >> > > > > Release Notes v3.0 <#contents>
> >> > > > >
> >> > > > > - Replaced custom Java SNI implementation with a
> native
> >> > > implementation
> >> > > > > using tomcat-native, apr (Apache Portable Runtime)
> and
> >> OpenSSL
> >> > > This
> >> > > > > should
> >> > > > > significantly improve the performance of routing
> ‘https’
> >> > > delivery
> >> > > > > services.
> >> > > > > - Upgraded to Tomcat 8.5.30
> >> > > > > - Separated the Traffic Router installation from the
> >> Tomcat
> >> > > deployment
> >> > > > > and created a new ‘tomcat’ package for installing
> >> Tomcat.
> >> > > Traffic Router
> >> > > > > and Tomcat can now be upgraded independently
> >> > > > > - Converted Traffic Router to a ‘systemd’ service
> >> > > > > - Modified the development test and dev deployment
> >> processes to
> >> > > be more
> >> > > > > consistent with production
> >> > > > >
> >> > > > > System Requirements <#contents>
> >> > > > >
> >> > > > > - Centos 7.2
> >> > > > > - OpenSSL >= 1.0.2 installed
> >> > > > > - JDK >= 8.0 installed or available in Yum repository
> >> > > > > - APR (Apache Portable Runtime) >= 1.4.8-3 installed
> or
> >> > > available in Yum
> >> > > > > repository
> >> > > > > - Tomcat Native >= 1.2.16 installed or available in
> Yum
> >> > > repository
> >> > > > > - tomcat >= 8.5-28 installed or available in Yum
> >> repository
> >> > > (This
> >> > > > > package is created automatically by the Traffic
> Router
> >> build
> >> > > process)
> >> > > > >
> >> > > > > Upgrade Procedure <#contents>
> >> > > > >
> >> > > > > - upload tomcat.rpm to a Yum repository
> >> > > > > - update the traffic_router package
> >> > > > > - restore property files
> >> > > > >
> >> > > > > Upload tomcat.rpm
> >> > > > >
> >> > > > > The ‘tomcat’ package gets created when you build Traffic
> >> Router.
> >> > > You must
> >> > > > > either add it to the yum repo where you keep all of the
> >> Traffic
> >> > > Control
> >> > > > > packages, or manually copy it to the servers where you
> >> will be
> >> > > installing
> >> > > > > Traffic Router and run yum install [path to package] It
> is
> >> > > preferable that
> >> > > > > you add it to your Yum repository because then it will
> be
> >> installed
> >> > > > > automatically when you perform the Traffic Router
> update.
> >> > > > > Update the traffic_router Package
> >> > > > >
> >> > > > > If openssl, apr, tomcat-native, jdk and tomcat_tr
> packages
> >> are all
> >> > > in an
> >> > > > > available repository then you just need to run: yum
> update
> >> > > traffic_router.
> >> > > > > This will first cause the apr, tomcat-native, jdk and
> >> tomcat
> >> > > packages to be
> >> > > > > installed. When the ‘tomcat’ package runs, it will cause
> >> any older
> >> > > versions
> >> > > > > of traffic_router or tomcat to be uninstalled. This is
> >> because the
> >> > > previous
> >> > > > > versions of the traffic_router package included an
> >> untracked
> >> > > installation
> >> > > > > of tomcat.
> >> > > > > Restore Property Files
> >> > > > >
> >> > > > > Replace the Traffic Router properties files with the
> >> correct ones
> >> > > for the
> >> > > > > CDN. The properties files from the previous install can
> be
> >> found
> >> > > at:
> >> > > > >
> /opt/traffic_router/conf/traffic_ops.properties.rpmsaved &
> >> > > > > traffic_monitor.properties.rpmsaved.
> >> > > > > Development Environment Upgrade <#contents>
> >> > > > >
> >> > > > > If you already have a development environment set up for
> >> the
> >> > > previous
> >> > > > > version of Traffic Router, then you will need to get and
> >> install
> >> > > these
> >> > > > > libraries on your workstation: openssl, apr and
> >> tomcat-native.
> >> > > Also,
> >> > > > > whenever you run either ‘mvn clean verify’ or
> >> ‘TrafficRouterStart’
> >> > > you will
> >> > > > > need to pass a command line parameter telling Java where
> >> to look
> >> > > for the
> >> > > > > ‘tomcat-native’ libraries:mvn clean verify
> >> > > -Djava.library.path=[tomcat
> >> > > > > native library path on your box]java
> >> -Djava.library.path=[tomcat
> >> > > native
> >> > > > > library path on your box] TrafficRouterStart
> >> > > > >
> >> > > >
> >> > > >
> >> > >
> >> >
> >> >
> >>
>
Re: [EXTERNAL] Re: [TC-69] Upgrade Tomcat Version for Traffic Router (#925)
Posted by Jeff Elsloo <el...@apache.org>.
FYI we currently have a production trial of this PR underway, and will
be continuing in that direction. I do plan to merge this PR in the
near future, hopefully next week, so please chime in if you have
concerns. I expect that we will run into a few issues around some
install/upgrade cases, and may have to tweak things as we learn more.
--
Thanks,
Jeff
On Mon, Jun 4, 2018 at 4:00 PM, Dave Neuman <ne...@apache.org> wrote:
> +1 on dropping support and updating all versions. Traffic Ops already only
> supports Centos7.0. We talked about this at the summit and I was supposed
> to start a thread, I apologize for neglecting to do so. I can start a new
> thread if Jeff doesn’t.
>
> Thanks,
> Dave
>
> On Mon, Jun 4, 2018 at 17:06 Jeff Elsloo <el...@apache.org> wrote:
>
>> There's also the issue of no systemd in CentOS 6.x, so we would have
>> to not only maintain a different set of dependencies for CentOS 6.x,
>> but also would have to have separate tooling for both. We used init
>> previously and moved to systemd with this update, which is yet another
>> reason to move away from 6.x.
>>
>> Also, it appears I misspoke and we cannot version separately like I
>> had hoped. It appears as though we'd have to update everything to 3.0.
>> --
>> Thanks,
>> Jeff
>>
>>
>> On Mon, Jun 4, 2018 at 1:39 PM, Schmidt, Andrew (Contractor)
>> <An...@comcast.com> wrote:
>> > Steve,
>> > The trickiest part about installing this on centos 6 is getting a the
>> tomcat-native 1.2.16+ rpm. They don't have one in the EPEL repo for centos
>> 6 so you have to build one for yourself. I did not go that far. So I can't
>> guarantee that someone could actually get this working on 6.x.
>> >
>> > I do like the idea of having Traffic Router move to 3.0 before the rest
>> of Traffic Control if that is a real option.
>> >
>> > Andy
>> >
>> > On 6/4/18, 11:45 AM, "Steve Malenfant" <sm...@gmail.com> wrote:
>> >
>> > Jeff,
>> >
>> > I have no problem dropping support for 6.x even in 2.3 for Traffic
>> Router.
>> > Seems like we drop support for the RPM generation but somebody might
>> still
>> > be able to install on their 6.x installation manually?
>> >
>> > I'll make up some time to test this week.
>> >
>> > Steve
>> >
>> > On Mon, Jun 4, 2018 at 12:33 PM, Jeff Elsloo <el...@apache.org>
>> wrote:
>> >
>> > > Hi all,
>> > >
>> > > It sounds like the main gating item for this is a decision on
>> whether
>> > > we can drop support for CentOS prior to 7.x and if that
>> necessitates
>> > > updating Traffic Router to 3.0. Then, the larger issue is whether
>> we
>> > > also update the other components to 3.0 at the same time. Should we
>> > > call a vote for dropping 7.x support and moving to 3.0 for just
>> > > Traffic Router, or should we do that across the board?
>> > >
>> > > Does anyone have any objections to what Andy outlined above?
>> > > Additionally, I want to be clear that we introduced a new
>> dependency
>> > > on an EPEL package (tomcat-native), we packaged Tomcat in its own
>> RPM,
>> > > and changed the service name from `tomcat` to `traffic_router`.
>> Most
>> > > of Tomcat's config now lives right next to the Traffic Router
>> > > configuration. Other than that, this is a drop in replacement for
>> > > Traffic Router that currently runs on Tomcat 6.0.33.
>> > >
>> > > If anyone has the free time to pull down the code, build it, and
>> test
>> > > it in their environment, we would really appreciate it.
>> > > --
>> > > Thanks,
>> > > Jeff
>> > >
>> > >
>> > > On Fri, May 25, 2018 at 4:36 PM, Schmidt, Andrew (Contractor)
>> > > <An...@comcast.com> wrote:
>> > > > Sounds good Dave. The technical requirement for the version
>> number is
>> > > that it needs to have a greater minor number than the version it
>> replaces
>> > > so that the RPM install can properly clean up the previous one.
>> This means
>> > > it needs to be the first build we release on the new version.
>> > > >
>> > > > Andy
>> > > >
>> > > > On 5/25/18, 12:38 PM, "Dave Neuman" <ne...@apache.org> wrote:
>> > > >
>> > > > This is great news, thanks Andy! I am excited to see this
>> finally
>> > > get
>> > > > merged into Traffic Control.
>> > > > We haven't formally discussed making the next release 3.0,
>> so I will
>> > > make
>> > > > sure to get an email out about that. I think it is the
>> right thing
>> > > to do.
>> > > >
>> > > > Thanks,
>> > > > Dave
>> > > >
>> > > > On Thu, May 24, 2018 at 6:57 PM, Andy Schmidt <
>> zapdivi@gmail.com>
>> > > wrote:
>> > > >
>> > > > > Hello,
>> > > > > I have submitted a PR (#2331) for this major upgrade. We
>> are
>> > > looking to
>> > > > > make this part of the TC 3.0 release because it is a large
>> change
>> > > and the
>> > > > > update will automatically uninstall older versions of
>> Traffic
>> > > Router. The
>> > > > > update will upgrade the Tomcat to 8.5.28+ and will require
>> Java 8,
>> > > CentOs 7
>> > > > > and the installation of OpenSSL, Tomcat Native and APR.
>> Most of
>> > > this will
>> > > > > be taken care of by the RPM. Here is the migration
>> documentation :
>> > > > >
>> > > > > Traffic Router - Migrating to 3.0 <#contents>
>> > > > >
>> > > > > Contents
>> > > > >
>> > > > > - Traffic Router - Migrating to 3.0
>> > > <#traffic-router-migrating-to-3-0>
>> > > > > - Release Notes v3.0 <#release-notes-v3-0>
>> > > > > - System Requirements <#system-requirements>
>> > > > > - Upgrade Procedure <#upgrade-procedure>
>> > > > > - Development Environment Upgrade
>> <#development-environment-
>> > > upgrade>
>> > > > >
>> > > > > Release Notes v3.0 <#contents>
>> > > > >
>> > > > > - Replaced custom Java SNI implementation with a native
>> > > implementation
>> > > > > using tomcat-native, apr (Apache Portable Runtime) and
>> OpenSSL
>> > > This
>> > > > > should
>> > > > > significantly improve the performance of routing ‘https’
>> > > delivery
>> > > > > services.
>> > > > > - Upgraded to Tomcat 8.5.30
>> > > > > - Separated the Traffic Router installation from the
>> Tomcat
>> > > deployment
>> > > > > and created a new ‘tomcat’ package for installing
>> Tomcat.
>> > > Traffic Router
>> > > > > and Tomcat can now be upgraded independently
>> > > > > - Converted Traffic Router to a ‘systemd’ service
>> > > > > - Modified the development test and dev deployment
>> processes to
>> > > be more
>> > > > > consistent with production
>> > > > >
>> > > > > System Requirements <#contents>
>> > > > >
>> > > > > - Centos 7.2
>> > > > > - OpenSSL >= 1.0.2 installed
>> > > > > - JDK >= 8.0 installed or available in Yum repository
>> > > > > - APR (Apache Portable Runtime) >= 1.4.8-3 installed or
>> > > available in Yum
>> > > > > repository
>> > > > > - Tomcat Native >= 1.2.16 installed or available in Yum
>> > > repository
>> > > > > - tomcat >= 8.5-28 installed or available in Yum
>> repository
>> > > (This
>> > > > > package is created automatically by the Traffic Router
>> build
>> > > process)
>> > > > >
>> > > > > Upgrade Procedure <#contents>
>> > > > >
>> > > > > - upload tomcat.rpm to a Yum repository
>> > > > > - update the traffic_router package
>> > > > > - restore property files
>> > > > >
>> > > > > Upload tomcat.rpm
>> > > > >
>> > > > > The ‘tomcat’ package gets created when you build Traffic
>> Router.
>> > > You must
>> > > > > either add it to the yum repo where you keep all of the
>> Traffic
>> > > Control
>> > > > > packages, or manually copy it to the servers where you
>> will be
>> > > installing
>> > > > > Traffic Router and run yum install [path to package] It is
>> > > preferable that
>> > > > > you add it to your Yum repository because then it will be
>> installed
>> > > > > automatically when you perform the Traffic Router update.
>> > > > > Update the traffic_router Package
>> > > > >
>> > > > > If openssl, apr, tomcat-native, jdk and tomcat_tr packages
>> are all
>> > > in an
>> > > > > available repository then you just need to run: yum update
>> > > traffic_router.
>> > > > > This will first cause the apr, tomcat-native, jdk and
>> tomcat
>> > > packages to be
>> > > > > installed. When the ‘tomcat’ package runs, it will cause
>> any older
>> > > versions
>> > > > > of traffic_router or tomcat to be uninstalled. This is
>> because the
>> > > previous
>> > > > > versions of the traffic_router package included an
>> untracked
>> > > installation
>> > > > > of tomcat.
>> > > > > Restore Property Files
>> > > > >
>> > > > > Replace the Traffic Router properties files with the
>> correct ones
>> > > for the
>> > > > > CDN. The properties files from the previous install can be
>> found
>> > > at:
>> > > > > /opt/traffic_router/conf/traffic_ops.properties.rpmsaved &
>> > > > > traffic_monitor.properties.rpmsaved.
>> > > > > Development Environment Upgrade <#contents>
>> > > > >
>> > > > > If you already have a development environment set up for
>> the
>> > > previous
>> > > > > version of Traffic Router, then you will need to get and
>> install
>> > > these
>> > > > > libraries on your workstation: openssl, apr and
>> tomcat-native.
>> > > Also,
>> > > > > whenever you run either ‘mvn clean verify’ or
>> ‘TrafficRouterStart’
>> > > you will
>> > > > > need to pass a command line parameter telling Java where
>> to look
>> > > for the
>> > > > > ‘tomcat-native’ libraries:mvn clean verify
>> > > -Djava.library.path=[tomcat
>> > > > > native library path on your box]java
>> -Djava.library.path=[tomcat
>> > > native
>> > > > > library path on your box] TrafficRouterStart
>> > > > >
>> > > >
>> > > >
>> > >
>> >
>> >
>>
Re: [EXTERNAL] Re: [TC-69] Upgrade Tomcat Version for Traffic Router (#925)
Posted by Dave Neuman <ne...@apache.org>.
+1 on dropping support and updating all versions. Traffic Ops already only
supports Centos7.0. We talked about this at the summit and I was supposed
to start a thread, I apologize for neglecting to do so. I can start a new
thread if Jeff doesn’t.
Thanks,
Dave
On Mon, Jun 4, 2018 at 17:06 Jeff Elsloo <el...@apache.org> wrote:
> There's also the issue of no systemd in CentOS 6.x, so we would have
> to not only maintain a different set of dependencies for CentOS 6.x,
> but also would have to have separate tooling for both. We used init
> previously and moved to systemd with this update, which is yet another
> reason to move away from 6.x.
>
> Also, it appears I misspoke and we cannot version separately like I
> had hoped. It appears as though we'd have to update everything to 3.0.
> --
> Thanks,
> Jeff
>
>
> On Mon, Jun 4, 2018 at 1:39 PM, Schmidt, Andrew (Contractor)
> <An...@comcast.com> wrote:
> > Steve,
> > The trickiest part about installing this on centos 6 is getting a the
> tomcat-native 1.2.16+ rpm. They don't have one in the EPEL repo for centos
> 6 so you have to build one for yourself. I did not go that far. So I can't
> guarantee that someone could actually get this working on 6.x.
> >
> > I do like the idea of having Traffic Router move to 3.0 before the rest
> of Traffic Control if that is a real option.
> >
> > Andy
> >
> > On 6/4/18, 11:45 AM, "Steve Malenfant" <sm...@gmail.com> wrote:
> >
> > Jeff,
> >
> > I have no problem dropping support for 6.x even in 2.3 for Traffic
> Router.
> > Seems like we drop support for the RPM generation but somebody might
> still
> > be able to install on their 6.x installation manually?
> >
> > I'll make up some time to test this week.
> >
> > Steve
> >
> > On Mon, Jun 4, 2018 at 12:33 PM, Jeff Elsloo <el...@apache.org>
> wrote:
> >
> > > Hi all,
> > >
> > > It sounds like the main gating item for this is a decision on
> whether
> > > we can drop support for CentOS prior to 7.x and if that
> necessitates
> > > updating Traffic Router to 3.0. Then, the larger issue is whether
> we
> > > also update the other components to 3.0 at the same time. Should we
> > > call a vote for dropping 7.x support and moving to 3.0 for just
> > > Traffic Router, or should we do that across the board?
> > >
> > > Does anyone have any objections to what Andy outlined above?
> > > Additionally, I want to be clear that we introduced a new
> dependency
> > > on an EPEL package (tomcat-native), we packaged Tomcat in its own
> RPM,
> > > and changed the service name from `tomcat` to `traffic_router`.
> Most
> > > of Tomcat's config now lives right next to the Traffic Router
> > > configuration. Other than that, this is a drop in replacement for
> > > Traffic Router that currently runs on Tomcat 6.0.33.
> > >
> > > If anyone has the free time to pull down the code, build it, and
> test
> > > it in their environment, we would really appreciate it.
> > > --
> > > Thanks,
> > > Jeff
> > >
> > >
> > > On Fri, May 25, 2018 at 4:36 PM, Schmidt, Andrew (Contractor)
> > > <An...@comcast.com> wrote:
> > > > Sounds good Dave. The technical requirement for the version
> number is
> > > that it needs to have a greater minor number than the version it
> replaces
> > > so that the RPM install can properly clean up the previous one.
> This means
> > > it needs to be the first build we release on the new version.
> > > >
> > > > Andy
> > > >
> > > > On 5/25/18, 12:38 PM, "Dave Neuman" <ne...@apache.org> wrote:
> > > >
> > > > This is great news, thanks Andy! I am excited to see this
> finally
> > > get
> > > > merged into Traffic Control.
> > > > We haven't formally discussed making the next release 3.0,
> so I will
> > > make
> > > > sure to get an email out about that. I think it is the
> right thing
> > > to do.
> > > >
> > > > Thanks,
> > > > Dave
> > > >
> > > > On Thu, May 24, 2018 at 6:57 PM, Andy Schmidt <
> zapdivi@gmail.com>
> > > wrote:
> > > >
> > > > > Hello,
> > > > > I have submitted a PR (#2331) for this major upgrade. We
> are
> > > looking to
> > > > > make this part of the TC 3.0 release because it is a large
> change
> > > and the
> > > > > update will automatically uninstall older versions of
> Traffic
> > > Router. The
> > > > > update will upgrade the Tomcat to 8.5.28+ and will require
> Java 8,
> > > CentOs 7
> > > > > and the installation of OpenSSL, Tomcat Native and APR.
> Most of
> > > this will
> > > > > be taken care of by the RPM. Here is the migration
> documentation :
> > > > >
> > > > > Traffic Router - Migrating to 3.0 <#contents>
> > > > >
> > > > > Contents
> > > > >
> > > > > - Traffic Router - Migrating to 3.0
> > > <#traffic-router-migrating-to-3-0>
> > > > > - Release Notes v3.0 <#release-notes-v3-0>
> > > > > - System Requirements <#system-requirements>
> > > > > - Upgrade Procedure <#upgrade-procedure>
> > > > > - Development Environment Upgrade
> <#development-environment-
> > > upgrade>
> > > > >
> > > > > Release Notes v3.0 <#contents>
> > > > >
> > > > > - Replaced custom Java SNI implementation with a native
> > > implementation
> > > > > using tomcat-native, apr (Apache Portable Runtime) and
> OpenSSL
> > > This
> > > > > should
> > > > > significantly improve the performance of routing ‘https’
> > > delivery
> > > > > services.
> > > > > - Upgraded to Tomcat 8.5.30
> > > > > - Separated the Traffic Router installation from the
> Tomcat
> > > deployment
> > > > > and created a new ‘tomcat’ package for installing
> Tomcat.
> > > Traffic Router
> > > > > and Tomcat can now be upgraded independently
> > > > > - Converted Traffic Router to a ‘systemd’ service
> > > > > - Modified the development test and dev deployment
> processes to
> > > be more
> > > > > consistent with production
> > > > >
> > > > > System Requirements <#contents>
> > > > >
> > > > > - Centos 7.2
> > > > > - OpenSSL >= 1.0.2 installed
> > > > > - JDK >= 8.0 installed or available in Yum repository
> > > > > - APR (Apache Portable Runtime) >= 1.4.8-3 installed or
> > > available in Yum
> > > > > repository
> > > > > - Tomcat Native >= 1.2.16 installed or available in Yum
> > > repository
> > > > > - tomcat >= 8.5-28 installed or available in Yum
> repository
> > > (This
> > > > > package is created automatically by the Traffic Router
> build
> > > process)
> > > > >
> > > > > Upgrade Procedure <#contents>
> > > > >
> > > > > - upload tomcat.rpm to a Yum repository
> > > > > - update the traffic_router package
> > > > > - restore property files
> > > > >
> > > > > Upload tomcat.rpm
> > > > >
> > > > > The ‘tomcat’ package gets created when you build Traffic
> Router.
> > > You must
> > > > > either add it to the yum repo where you keep all of the
> Traffic
> > > Control
> > > > > packages, or manually copy it to the servers where you
> will be
> > > installing
> > > > > Traffic Router and run yum install [path to package] It is
> > > preferable that
> > > > > you add it to your Yum repository because then it will be
> installed
> > > > > automatically when you perform the Traffic Router update.
> > > > > Update the traffic_router Package
> > > > >
> > > > > If openssl, apr, tomcat-native, jdk and tomcat_tr packages
> are all
> > > in an
> > > > > available repository then you just need to run: yum update
> > > traffic_router.
> > > > > This will first cause the apr, tomcat-native, jdk and
> tomcat
> > > packages to be
> > > > > installed. When the ‘tomcat’ package runs, it will cause
> any older
> > > versions
> > > > > of traffic_router or tomcat to be uninstalled. This is
> because the
> > > previous
> > > > > versions of the traffic_router package included an
> untracked
> > > installation
> > > > > of tomcat.
> > > > > Restore Property Files
> > > > >
> > > > > Replace the Traffic Router properties files with the
> correct ones
> > > for the
> > > > > CDN. The properties files from the previous install can be
> found
> > > at:
> > > > > /opt/traffic_router/conf/traffic_ops.properties.rpmsaved &
> > > > > traffic_monitor.properties.rpmsaved.
> > > > > Development Environment Upgrade <#contents>
> > > > >
> > > > > If you already have a development environment set up for
> the
> > > previous
> > > > > version of Traffic Router, then you will need to get and
> install
> > > these
> > > > > libraries on your workstation: openssl, apr and
> tomcat-native.
> > > Also,
> > > > > whenever you run either ‘mvn clean verify’ or
> ‘TrafficRouterStart’
> > > you will
> > > > > need to pass a command line parameter telling Java where
> to look
> > > for the
> > > > > ‘tomcat-native’ libraries:mvn clean verify
> > > -Djava.library.path=[tomcat
> > > > > native library path on your box]java
> -Djava.library.path=[tomcat
> > > native
> > > > > library path on your box] TrafficRouterStart
> > > > >
> > > >
> > > >
> > >
> >
> >
>
Re: [EXTERNAL] Re: [TC-69] Upgrade Tomcat Version for Traffic Router (#925)
Posted by Jeff Elsloo <el...@apache.org>.
There's also the issue of no systemd in CentOS 6.x, so we would have
to not only maintain a different set of dependencies for CentOS 6.x,
but also would have to have separate tooling for both. We used init
previously and moved to systemd with this update, which is yet another
reason to move away from 6.x.
Also, it appears I misspoke and we cannot version separately like I
had hoped. It appears as though we'd have to update everything to 3.0.
--
Thanks,
Jeff
On Mon, Jun 4, 2018 at 1:39 PM, Schmidt, Andrew (Contractor)
<An...@comcast.com> wrote:
> Steve,
> The trickiest part about installing this on centos 6 is getting a the tomcat-native 1.2.16+ rpm. They don't have one in the EPEL repo for centos 6 so you have to build one for yourself. I did not go that far. So I can't guarantee that someone could actually get this working on 6.x.
>
> I do like the idea of having Traffic Router move to 3.0 before the rest of Traffic Control if that is a real option.
>
> Andy
>
> On 6/4/18, 11:45 AM, "Steve Malenfant" <sm...@gmail.com> wrote:
>
> Jeff,
>
> I have no problem dropping support for 6.x even in 2.3 for Traffic Router.
> Seems like we drop support for the RPM generation but somebody might still
> be able to install on their 6.x installation manually?
>
> I'll make up some time to test this week.
>
> Steve
>
> On Mon, Jun 4, 2018 at 12:33 PM, Jeff Elsloo <el...@apache.org> wrote:
>
> > Hi all,
> >
> > It sounds like the main gating item for this is a decision on whether
> > we can drop support for CentOS prior to 7.x and if that necessitates
> > updating Traffic Router to 3.0. Then, the larger issue is whether we
> > also update the other components to 3.0 at the same time. Should we
> > call a vote for dropping 7.x support and moving to 3.0 for just
> > Traffic Router, or should we do that across the board?
> >
> > Does anyone have any objections to what Andy outlined above?
> > Additionally, I want to be clear that we introduced a new dependency
> > on an EPEL package (tomcat-native), we packaged Tomcat in its own RPM,
> > and changed the service name from `tomcat` to `traffic_router`. Most
> > of Tomcat's config now lives right next to the Traffic Router
> > configuration. Other than that, this is a drop in replacement for
> > Traffic Router that currently runs on Tomcat 6.0.33.
> >
> > If anyone has the free time to pull down the code, build it, and test
> > it in their environment, we would really appreciate it.
> > --
> > Thanks,
> > Jeff
> >
> >
> > On Fri, May 25, 2018 at 4:36 PM, Schmidt, Andrew (Contractor)
> > <An...@comcast.com> wrote:
> > > Sounds good Dave. The technical requirement for the version number is
> > that it needs to have a greater minor number than the version it replaces
> > so that the RPM install can properly clean up the previous one. This means
> > it needs to be the first build we release on the new version.
> > >
> > > Andy
> > >
> > > On 5/25/18, 12:38 PM, "Dave Neuman" <ne...@apache.org> wrote:
> > >
> > > This is great news, thanks Andy! I am excited to see this finally
> > get
> > > merged into Traffic Control.
> > > We haven't formally discussed making the next release 3.0, so I will
> > make
> > > sure to get an email out about that. I think it is the right thing
> > to do.
> > >
> > > Thanks,
> > > Dave
> > >
> > > On Thu, May 24, 2018 at 6:57 PM, Andy Schmidt <za...@gmail.com>
> > wrote:
> > >
> > > > Hello,
> > > > I have submitted a PR (#2331) for this major upgrade. We are
> > looking to
> > > > make this part of the TC 3.0 release because it is a large change
> > and the
> > > > update will automatically uninstall older versions of Traffic
> > Router. The
> > > > update will upgrade the Tomcat to 8.5.28+ and will require Java 8,
> > CentOs 7
> > > > and the installation of OpenSSL, Tomcat Native and APR. Most of
> > this will
> > > > be taken care of by the RPM. Here is the migration documentation :
> > > >
> > > > Traffic Router - Migrating to 3.0 <#contents>
> > > >
> > > > Contents
> > > >
> > > > - Traffic Router - Migrating to 3.0
> > <#traffic-router-migrating-to-3-0>
> > > > - Release Notes v3.0 <#release-notes-v3-0>
> > > > - System Requirements <#system-requirements>
> > > > - Upgrade Procedure <#upgrade-procedure>
> > > > - Development Environment Upgrade <#development-environment-
> > upgrade>
> > > >
> > > > Release Notes v3.0 <#contents>
> > > >
> > > > - Replaced custom Java SNI implementation with a native
> > implementation
> > > > using tomcat-native, apr (Apache Portable Runtime) and OpenSSL
> > This
> > > > should
> > > > significantly improve the performance of routing ‘https’
> > delivery
> > > > services.
> > > > - Upgraded to Tomcat 8.5.30
> > > > - Separated the Traffic Router installation from the Tomcat
> > deployment
> > > > and created a new ‘tomcat’ package for installing Tomcat.
> > Traffic Router
> > > > and Tomcat can now be upgraded independently
> > > > - Converted Traffic Router to a ‘systemd’ service
> > > > - Modified the development test and dev deployment processes to
> > be more
> > > > consistent with production
> > > >
> > > > System Requirements <#contents>
> > > >
> > > > - Centos 7.2
> > > > - OpenSSL >= 1.0.2 installed
> > > > - JDK >= 8.0 installed or available in Yum repository
> > > > - APR (Apache Portable Runtime) >= 1.4.8-3 installed or
> > available in Yum
> > > > repository
> > > > - Tomcat Native >= 1.2.16 installed or available in Yum
> > repository
> > > > - tomcat >= 8.5-28 installed or available in Yum repository
> > (This
> > > > package is created automatically by the Traffic Router build
> > process)
> > > >
> > > > Upgrade Procedure <#contents>
> > > >
> > > > - upload tomcat.rpm to a Yum repository
> > > > - update the traffic_router package
> > > > - restore property files
> > > >
> > > > Upload tomcat.rpm
> > > >
> > > > The ‘tomcat’ package gets created when you build Traffic Router.
> > You must
> > > > either add it to the yum repo where you keep all of the Traffic
> > Control
> > > > packages, or manually copy it to the servers where you will be
> > installing
> > > > Traffic Router and run yum install [path to package] It is
> > preferable that
> > > > you add it to your Yum repository because then it will be installed
> > > > automatically when you perform the Traffic Router update.
> > > > Update the traffic_router Package
> > > >
> > > > If openssl, apr, tomcat-native, jdk and tomcat_tr packages are all
> > in an
> > > > available repository then you just need to run: yum update
> > traffic_router.
> > > > This will first cause the apr, tomcat-native, jdk and tomcat
> > packages to be
> > > > installed. When the ‘tomcat’ package runs, it will cause any older
> > versions
> > > > of traffic_router or tomcat to be uninstalled. This is because the
> > previous
> > > > versions of the traffic_router package included an untracked
> > installation
> > > > of tomcat.
> > > > Restore Property Files
> > > >
> > > > Replace the Traffic Router properties files with the correct ones
> > for the
> > > > CDN. The properties files from the previous install can be found
> > at:
> > > > /opt/traffic_router/conf/traffic_ops.properties.rpmsaved &
> > > > traffic_monitor.properties.rpmsaved.
> > > > Development Environment Upgrade <#contents>
> > > >
> > > > If you already have a development environment set up for the
> > previous
> > > > version of Traffic Router, then you will need to get and install
> > these
> > > > libraries on your workstation: openssl, apr and tomcat-native.
> > Also,
> > > > whenever you run either ‘mvn clean verify’ or ‘TrafficRouterStart’
> > you will
> > > > need to pass a command line parameter telling Java where to look
> > for the
> > > > ‘tomcat-native’ libraries:mvn clean verify
> > -Djava.library.path=[tomcat
> > > > native library path on your box]java -Djava.library.path=[tomcat
> > native
> > > > library path on your box] TrafficRouterStart
> > > >
> > >
> > >
> >
>
>
Re: [EXTERNAL] Re: [TC-69] Upgrade Tomcat Version for Traffic Router
(#925)
Posted by "Schmidt, Andrew (Contractor)" <An...@comcast.com>.
Steve,
The trickiest part about installing this on centos 6 is getting a the tomcat-native 1.2.16+ rpm. They don't have one in the EPEL repo for centos 6 so you have to build one for yourself. I did not go that far. So I can't guarantee that someone could actually get this working on 6.x.
I do like the idea of having Traffic Router move to 3.0 before the rest of Traffic Control if that is a real option.
Andy
On 6/4/18, 11:45 AM, "Steve Malenfant" <sm...@gmail.com> wrote:
Jeff,
I have no problem dropping support for 6.x even in 2.3 for Traffic Router.
Seems like we drop support for the RPM generation but somebody might still
be able to install on their 6.x installation manually?
I'll make up some time to test this week.
Steve
On Mon, Jun 4, 2018 at 12:33 PM, Jeff Elsloo <el...@apache.org> wrote:
> Hi all,
>
> It sounds like the main gating item for this is a decision on whether
> we can drop support for CentOS prior to 7.x and if that necessitates
> updating Traffic Router to 3.0. Then, the larger issue is whether we
> also update the other components to 3.0 at the same time. Should we
> call a vote for dropping 7.x support and moving to 3.0 for just
> Traffic Router, or should we do that across the board?
>
> Does anyone have any objections to what Andy outlined above?
> Additionally, I want to be clear that we introduced a new dependency
> on an EPEL package (tomcat-native), we packaged Tomcat in its own RPM,
> and changed the service name from `tomcat` to `traffic_router`. Most
> of Tomcat's config now lives right next to the Traffic Router
> configuration. Other than that, this is a drop in replacement for
> Traffic Router that currently runs on Tomcat 6.0.33.
>
> If anyone has the free time to pull down the code, build it, and test
> it in their environment, we would really appreciate it.
> --
> Thanks,
> Jeff
>
>
> On Fri, May 25, 2018 at 4:36 PM, Schmidt, Andrew (Contractor)
> <An...@comcast.com> wrote:
> > Sounds good Dave. The technical requirement for the version number is
> that it needs to have a greater minor number than the version it replaces
> so that the RPM install can properly clean up the previous one. This means
> it needs to be the first build we release on the new version.
> >
> > Andy
> >
> > On 5/25/18, 12:38 PM, "Dave Neuman" <ne...@apache.org> wrote:
> >
> > This is great news, thanks Andy! I am excited to see this finally
> get
> > merged into Traffic Control.
> > We haven't formally discussed making the next release 3.0, so I will
> make
> > sure to get an email out about that. I think it is the right thing
> to do.
> >
> > Thanks,
> > Dave
> >
> > On Thu, May 24, 2018 at 6:57 PM, Andy Schmidt <za...@gmail.com>
> wrote:
> >
> > > Hello,
> > > I have submitted a PR (#2331) for this major upgrade. We are
> looking to
> > > make this part of the TC 3.0 release because it is a large change
> and the
> > > update will automatically uninstall older versions of Traffic
> Router. The
> > > update will upgrade the Tomcat to 8.5.28+ and will require Java 8,
> CentOs 7
> > > and the installation of OpenSSL, Tomcat Native and APR. Most of
> this will
> > > be taken care of by the RPM. Here is the migration documentation :
> > >
> > > Traffic Router - Migrating to 3.0 <#contents>
> > >
> > > Contents
> > >
> > > - Traffic Router - Migrating to 3.0
> <#traffic-router-migrating-to-3-0>
> > > - Release Notes v3.0 <#release-notes-v3-0>
> > > - System Requirements <#system-requirements>
> > > - Upgrade Procedure <#upgrade-procedure>
> > > - Development Environment Upgrade <#development-environment-
> upgrade>
> > >
> > > Release Notes v3.0 <#contents>
> > >
> > > - Replaced custom Java SNI implementation with a native
> implementation
> > > using tomcat-native, apr (Apache Portable Runtime) and OpenSSL
> This
> > > should
> > > significantly improve the performance of routing ‘https’
> delivery
> > > services.
> > > - Upgraded to Tomcat 8.5.30
> > > - Separated the Traffic Router installation from the Tomcat
> deployment
> > > and created a new ‘tomcat’ package for installing Tomcat.
> Traffic Router
> > > and Tomcat can now be upgraded independently
> > > - Converted Traffic Router to a ‘systemd’ service
> > > - Modified the development test and dev deployment processes to
> be more
> > > consistent with production
> > >
> > > System Requirements <#contents>
> > >
> > > - Centos 7.2
> > > - OpenSSL >= 1.0.2 installed
> > > - JDK >= 8.0 installed or available in Yum repository
> > > - APR (Apache Portable Runtime) >= 1.4.8-3 installed or
> available in Yum
> > > repository
> > > - Tomcat Native >= 1.2.16 installed or available in Yum
> repository
> > > - tomcat >= 8.5-28 installed or available in Yum repository
> (This
> > > package is created automatically by the Traffic Router build
> process)
> > >
> > > Upgrade Procedure <#contents>
> > >
> > > - upload tomcat.rpm to a Yum repository
> > > - update the traffic_router package
> > > - restore property files
> > >
> > > Upload tomcat.rpm
> > >
> > > The ‘tomcat’ package gets created when you build Traffic Router.
> You must
> > > either add it to the yum repo where you keep all of the Traffic
> Control
> > > packages, or manually copy it to the servers where you will be
> installing
> > > Traffic Router and run yum install [path to package] It is
> preferable that
> > > you add it to your Yum repository because then it will be installed
> > > automatically when you perform the Traffic Router update.
> > > Update the traffic_router Package
> > >
> > > If openssl, apr, tomcat-native, jdk and tomcat_tr packages are all
> in an
> > > available repository then you just need to run: yum update
> traffic_router.
> > > This will first cause the apr, tomcat-native, jdk and tomcat
> packages to be
> > > installed. When the ‘tomcat’ package runs, it will cause any older
> versions
> > > of traffic_router or tomcat to be uninstalled. This is because the
> previous
> > > versions of the traffic_router package included an untracked
> installation
> > > of tomcat.
> > > Restore Property Files
> > >
> > > Replace the Traffic Router properties files with the correct ones
> for the
> > > CDN. The properties files from the previous install can be found
> at:
> > > /opt/traffic_router/conf/traffic_ops.properties.rpmsaved &
> > > traffic_monitor.properties.rpmsaved.
> > > Development Environment Upgrade <#contents>
> > >
> > > If you already have a development environment set up for the
> previous
> > > version of Traffic Router, then you will need to get and install
> these
> > > libraries on your workstation: openssl, apr and tomcat-native.
> Also,
> > > whenever you run either ‘mvn clean verify’ or ‘TrafficRouterStart’
> you will
> > > need to pass a command line parameter telling Java where to look
> for the
> > > ‘tomcat-native’ libraries:mvn clean verify
> -Djava.library.path=[tomcat
> > > native library path on your box]java -Djava.library.path=[tomcat
> native
> > > library path on your box] TrafficRouterStart
> > >
> >
> >
>
Re: [EXTERNAL] Re: [TC-69] Upgrade Tomcat Version for Traffic Router (#925)
Posted by Steve Malenfant <sm...@gmail.com>.
Jeff,
I have no problem dropping support for 6.x even in 2.3 for Traffic Router.
Seems like we drop support for the RPM generation but somebody might still
be able to install on their 6.x installation manually?
I'll make up some time to test this week.
Steve
On Mon, Jun 4, 2018 at 12:33 PM, Jeff Elsloo <el...@apache.org> wrote:
> Hi all,
>
> It sounds like the main gating item for this is a decision on whether
> we can drop support for CentOS prior to 7.x and if that necessitates
> updating Traffic Router to 3.0. Then, the larger issue is whether we
> also update the other components to 3.0 at the same time. Should we
> call a vote for dropping 7.x support and moving to 3.0 for just
> Traffic Router, or should we do that across the board?
>
> Does anyone have any objections to what Andy outlined above?
> Additionally, I want to be clear that we introduced a new dependency
> on an EPEL package (tomcat-native), we packaged Tomcat in its own RPM,
> and changed the service name from `tomcat` to `traffic_router`. Most
> of Tomcat's config now lives right next to the Traffic Router
> configuration. Other than that, this is a drop in replacement for
> Traffic Router that currently runs on Tomcat 6.0.33.
>
> If anyone has the free time to pull down the code, build it, and test
> it in their environment, we would really appreciate it.
> --
> Thanks,
> Jeff
>
>
> On Fri, May 25, 2018 at 4:36 PM, Schmidt, Andrew (Contractor)
> <An...@comcast.com> wrote:
> > Sounds good Dave. The technical requirement for the version number is
> that it needs to have a greater minor number than the version it replaces
> so that the RPM install can properly clean up the previous one. This means
> it needs to be the first build we release on the new version.
> >
> > Andy
> >
> > On 5/25/18, 12:38 PM, "Dave Neuman" <ne...@apache.org> wrote:
> >
> > This is great news, thanks Andy! I am excited to see this finally
> get
> > merged into Traffic Control.
> > We haven't formally discussed making the next release 3.0, so I will
> make
> > sure to get an email out about that. I think it is the right thing
> to do.
> >
> > Thanks,
> > Dave
> >
> > On Thu, May 24, 2018 at 6:57 PM, Andy Schmidt <za...@gmail.com>
> wrote:
> >
> > > Hello,
> > > I have submitted a PR (#2331) for this major upgrade. We are
> looking to
> > > make this part of the TC 3.0 release because it is a large change
> and the
> > > update will automatically uninstall older versions of Traffic
> Router. The
> > > update will upgrade the Tomcat to 8.5.28+ and will require Java 8,
> CentOs 7
> > > and the installation of OpenSSL, Tomcat Native and APR. Most of
> this will
> > > be taken care of by the RPM. Here is the migration documentation :
> > >
> > > Traffic Router - Migrating to 3.0 <#contents>
> > >
> > > Contents
> > >
> > > - Traffic Router - Migrating to 3.0
> <#traffic-router-migrating-to-3-0>
> > > - Release Notes v3.0 <#release-notes-v3-0>
> > > - System Requirements <#system-requirements>
> > > - Upgrade Procedure <#upgrade-procedure>
> > > - Development Environment Upgrade <#development-environment-
> upgrade>
> > >
> > > Release Notes v3.0 <#contents>
> > >
> > > - Replaced custom Java SNI implementation with a native
> implementation
> > > using tomcat-native, apr (Apache Portable Runtime) and OpenSSL
> This
> > > should
> > > significantly improve the performance of routing ‘https’
> delivery
> > > services.
> > > - Upgraded to Tomcat 8.5.30
> > > - Separated the Traffic Router installation from the Tomcat
> deployment
> > > and created a new ‘tomcat’ package for installing Tomcat.
> Traffic Router
> > > and Tomcat can now be upgraded independently
> > > - Converted Traffic Router to a ‘systemd’ service
> > > - Modified the development test and dev deployment processes to
> be more
> > > consistent with production
> > >
> > > System Requirements <#contents>
> > >
> > > - Centos 7.2
> > > - OpenSSL >= 1.0.2 installed
> > > - JDK >= 8.0 installed or available in Yum repository
> > > - APR (Apache Portable Runtime) >= 1.4.8-3 installed or
> available in Yum
> > > repository
> > > - Tomcat Native >= 1.2.16 installed or available in Yum
> repository
> > > - tomcat >= 8.5-28 installed or available in Yum repository
> (This
> > > package is created automatically by the Traffic Router build
> process)
> > >
> > > Upgrade Procedure <#contents>
> > >
> > > - upload tomcat.rpm to a Yum repository
> > > - update the traffic_router package
> > > - restore property files
> > >
> > > Upload tomcat.rpm
> > >
> > > The ‘tomcat’ package gets created when you build Traffic Router.
> You must
> > > either add it to the yum repo where you keep all of the Traffic
> Control
> > > packages, or manually copy it to the servers where you will be
> installing
> > > Traffic Router and run yum install [path to package] It is
> preferable that
> > > you add it to your Yum repository because then it will be installed
> > > automatically when you perform the Traffic Router update.
> > > Update the traffic_router Package
> > >
> > > If openssl, apr, tomcat-native, jdk and tomcat_tr packages are all
> in an
> > > available repository then you just need to run: yum update
> traffic_router.
> > > This will first cause the apr, tomcat-native, jdk and tomcat
> packages to be
> > > installed. When the ‘tomcat’ package runs, it will cause any older
> versions
> > > of traffic_router or tomcat to be uninstalled. This is because the
> previous
> > > versions of the traffic_router package included an untracked
> installation
> > > of tomcat.
> > > Restore Property Files
> > >
> > > Replace the Traffic Router properties files with the correct ones
> for the
> > > CDN. The properties files from the previous install can be found
> at:
> > > /opt/traffic_router/conf/traffic_ops.properties.rpmsaved &
> > > traffic_monitor.properties.rpmsaved.
> > > Development Environment Upgrade <#contents>
> > >
> > > If you already have a development environment set up for the
> previous
> > > version of Traffic Router, then you will need to get and install
> these
> > > libraries on your workstation: openssl, apr and tomcat-native.
> Also,
> > > whenever you run either ‘mvn clean verify’ or ‘TrafficRouterStart’
> you will
> > > need to pass a command line parameter telling Java where to look
> for the
> > > ‘tomcat-native’ libraries:mvn clean verify
> -Djava.library.path=[tomcat
> > > native library path on your box]java -Djava.library.path=[tomcat
> native
> > > library path on your box] TrafficRouterStart
> > >
> >
> >
>
Re: [EXTERNAL] Re: [TC-69] Upgrade Tomcat Version for Traffic Router (#925)
Posted by Jeff Elsloo <el...@apache.org>.
Hi all,
It sounds like the main gating item for this is a decision on whether
we can drop support for CentOS prior to 7.x and if that necessitates
updating Traffic Router to 3.0. Then, the larger issue is whether we
also update the other components to 3.0 at the same time. Should we
call a vote for dropping 7.x support and moving to 3.0 for just
Traffic Router, or should we do that across the board?
Does anyone have any objections to what Andy outlined above?
Additionally, I want to be clear that we introduced a new dependency
on an EPEL package (tomcat-native), we packaged Tomcat in its own RPM,
and changed the service name from `tomcat` to `traffic_router`. Most
of Tomcat's config now lives right next to the Traffic Router
configuration. Other than that, this is a drop in replacement for
Traffic Router that currently runs on Tomcat 6.0.33.
If anyone has the free time to pull down the code, build it, and test
it in their environment, we would really appreciate it.
--
Thanks,
Jeff
On Fri, May 25, 2018 at 4:36 PM, Schmidt, Andrew (Contractor)
<An...@comcast.com> wrote:
> Sounds good Dave. The technical requirement for the version number is that it needs to have a greater minor number than the version it replaces so that the RPM install can properly clean up the previous one. This means it needs to be the first build we release on the new version.
>
> Andy
>
> On 5/25/18, 12:38 PM, "Dave Neuman" <ne...@apache.org> wrote:
>
> This is great news, thanks Andy! I am excited to see this finally get
> merged into Traffic Control.
> We haven't formally discussed making the next release 3.0, so I will make
> sure to get an email out about that. I think it is the right thing to do.
>
> Thanks,
> Dave
>
> On Thu, May 24, 2018 at 6:57 PM, Andy Schmidt <za...@gmail.com> wrote:
>
> > Hello,
> > I have submitted a PR (#2331) for this major upgrade. We are looking to
> > make this part of the TC 3.0 release because it is a large change and the
> > update will automatically uninstall older versions of Traffic Router. The
> > update will upgrade the Tomcat to 8.5.28+ and will require Java 8, CentOs 7
> > and the installation of OpenSSL, Tomcat Native and APR. Most of this will
> > be taken care of by the RPM. Here is the migration documentation :
> >
> > Traffic Router - Migrating to 3.0 <#contents>
> >
> > Contents
> >
> > - Traffic Router - Migrating to 3.0 <#traffic-router-migrating-to-3-0>
> > - Release Notes v3.0 <#release-notes-v3-0>
> > - System Requirements <#system-requirements>
> > - Upgrade Procedure <#upgrade-procedure>
> > - Development Environment Upgrade <#development-environment-upgrade>
> >
> > Release Notes v3.0 <#contents>
> >
> > - Replaced custom Java SNI implementation with a native implementation
> > using tomcat-native, apr (Apache Portable Runtime) and OpenSSL This
> > should
> > significantly improve the performance of routing ‘https’ delivery
> > services.
> > - Upgraded to Tomcat 8.5.30
> > - Separated the Traffic Router installation from the Tomcat deployment
> > and created a new ‘tomcat’ package for installing Tomcat. Traffic Router
> > and Tomcat can now be upgraded independently
> > - Converted Traffic Router to a ‘systemd’ service
> > - Modified the development test and dev deployment processes to be more
> > consistent with production
> >
> > System Requirements <#contents>
> >
> > - Centos 7.2
> > - OpenSSL >= 1.0.2 installed
> > - JDK >= 8.0 installed or available in Yum repository
> > - APR (Apache Portable Runtime) >= 1.4.8-3 installed or available in Yum
> > repository
> > - Tomcat Native >= 1.2.16 installed or available in Yum repository
> > - tomcat >= 8.5-28 installed or available in Yum repository (This
> > package is created automatically by the Traffic Router build process)
> >
> > Upgrade Procedure <#contents>
> >
> > - upload tomcat.rpm to a Yum repository
> > - update the traffic_router package
> > - restore property files
> >
> > Upload tomcat.rpm
> >
> > The ‘tomcat’ package gets created when you build Traffic Router. You must
> > either add it to the yum repo where you keep all of the Traffic Control
> > packages, or manually copy it to the servers where you will be installing
> > Traffic Router and run yum install [path to package] It is preferable that
> > you add it to your Yum repository because then it will be installed
> > automatically when you perform the Traffic Router update.
> > Update the traffic_router Package
> >
> > If openssl, apr, tomcat-native, jdk and tomcat_tr packages are all in an
> > available repository then you just need to run: yum update traffic_router.
> > This will first cause the apr, tomcat-native, jdk and tomcat packages to be
> > installed. When the ‘tomcat’ package runs, it will cause any older versions
> > of traffic_router or tomcat to be uninstalled. This is because the previous
> > versions of the traffic_router package included an untracked installation
> > of tomcat.
> > Restore Property Files
> >
> > Replace the Traffic Router properties files with the correct ones for the
> > CDN. The properties files from the previous install can be found at:
> > /opt/traffic_router/conf/traffic_ops.properties.rpmsaved &
> > traffic_monitor.properties.rpmsaved.
> > Development Environment Upgrade <#contents>
> >
> > If you already have a development environment set up for the previous
> > version of Traffic Router, then you will need to get and install these
> > libraries on your workstation: openssl, apr and tomcat-native. Also,
> > whenever you run either ‘mvn clean verify’ or ‘TrafficRouterStart’ you will
> > need to pass a command line parameter telling Java where to look for the
> > ‘tomcat-native’ libraries:mvn clean verify -Djava.library.path=[tomcat
> > native library path on your box]java -Djava.library.path=[tomcat native
> > library path on your box] TrafficRouterStart
> >
>
>
Re: [EXTERNAL] Re: [TC-69] Upgrade Tomcat Version for Traffic Router
(#925)
Posted by "Schmidt, Andrew (Contractor)" <An...@comcast.com>.
Sounds good Dave. The technical requirement for the version number is that it needs to have a greater minor number than the version it replaces so that the RPM install can properly clean up the previous one. This means it needs to be the first build we release on the new version.
Andy
On 5/25/18, 12:38 PM, "Dave Neuman" <ne...@apache.org> wrote:
This is great news, thanks Andy! I am excited to see this finally get
merged into Traffic Control.
We haven't formally discussed making the next release 3.0, so I will make
sure to get an email out about that. I think it is the right thing to do.
Thanks,
Dave
On Thu, May 24, 2018 at 6:57 PM, Andy Schmidt <za...@gmail.com> wrote:
> Hello,
> I have submitted a PR (#2331) for this major upgrade. We are looking to
> make this part of the TC 3.0 release because it is a large change and the
> update will automatically uninstall older versions of Traffic Router. The
> update will upgrade the Tomcat to 8.5.28+ and will require Java 8, CentOs 7
> and the installation of OpenSSL, Tomcat Native and APR. Most of this will
> be taken care of by the RPM. Here is the migration documentation :
>
> Traffic Router - Migrating to 3.0 <#contents>
>
> Contents
>
> - Traffic Router - Migrating to 3.0 <#traffic-router-migrating-to-3-0>
> - Release Notes v3.0 <#release-notes-v3-0>
> - System Requirements <#system-requirements>
> - Upgrade Procedure <#upgrade-procedure>
> - Development Environment Upgrade <#development-environment-upgrade>
>
> Release Notes v3.0 <#contents>
>
> - Replaced custom Java SNI implementation with a native implementation
> using tomcat-native, apr (Apache Portable Runtime) and OpenSSL This
> should
> significantly improve the performance of routing ‘https’ delivery
> services.
> - Upgraded to Tomcat 8.5.30
> - Separated the Traffic Router installation from the Tomcat deployment
> and created a new ‘tomcat’ package for installing Tomcat. Traffic Router
> and Tomcat can now be upgraded independently
> - Converted Traffic Router to a ‘systemd’ service
> - Modified the development test and dev deployment processes to be more
> consistent with production
>
> System Requirements <#contents>
>
> - Centos 7.2
> - OpenSSL >= 1.0.2 installed
> - JDK >= 8.0 installed or available in Yum repository
> - APR (Apache Portable Runtime) >= 1.4.8-3 installed or available in Yum
> repository
> - Tomcat Native >= 1.2.16 installed or available in Yum repository
> - tomcat >= 8.5-28 installed or available in Yum repository (This
> package is created automatically by the Traffic Router build process)
>
> Upgrade Procedure <#contents>
>
> - upload tomcat.rpm to a Yum repository
> - update the traffic_router package
> - restore property files
>
> Upload tomcat.rpm
>
> The ‘tomcat’ package gets created when you build Traffic Router. You must
> either add it to the yum repo where you keep all of the Traffic Control
> packages, or manually copy it to the servers where you will be installing
> Traffic Router and run yum install [path to package] It is preferable that
> you add it to your Yum repository because then it will be installed
> automatically when you perform the Traffic Router update.
> Update the traffic_router Package
>
> If openssl, apr, tomcat-native, jdk and tomcat_tr packages are all in an
> available repository then you just need to run: yum update traffic_router.
> This will first cause the apr, tomcat-native, jdk and tomcat packages to be
> installed. When the ‘tomcat’ package runs, it will cause any older versions
> of traffic_router or tomcat to be uninstalled. This is because the previous
> versions of the traffic_router package included an untracked installation
> of tomcat.
> Restore Property Files
>
> Replace the Traffic Router properties files with the correct ones for the
> CDN. The properties files from the previous install can be found at:
> /opt/traffic_router/conf/traffic_ops.properties.rpmsaved &
> traffic_monitor.properties.rpmsaved.
> Development Environment Upgrade <#contents>
>
> If you already have a development environment set up for the previous
> version of Traffic Router, then you will need to get and install these
> libraries on your workstation: openssl, apr and tomcat-native. Also,
> whenever you run either ‘mvn clean verify’ or ‘TrafficRouterStart’ you will
> need to pass a command line parameter telling Java where to look for the
> ‘tomcat-native’ libraries:mvn clean verify -Djava.library.path=[tomcat
> native library path on your box]java -Djava.library.path=[tomcat native
> library path on your box] TrafficRouterStart
>
Re: [TC-69] Upgrade Tomcat Version for Traffic Router (#925)
Posted by Dave Neuman <ne...@apache.org>.
This is great news, thanks Andy! I am excited to see this finally get
merged into Traffic Control.
We haven't formally discussed making the next release 3.0, so I will make
sure to get an email out about that. I think it is the right thing to do.
Thanks,
Dave
On Thu, May 24, 2018 at 6:57 PM, Andy Schmidt <za...@gmail.com> wrote:
> Hello,
> I have submitted a PR (#2331) for this major upgrade. We are looking to
> make this part of the TC 3.0 release because it is a large change and the
> update will automatically uninstall older versions of Traffic Router. The
> update will upgrade the Tomcat to 8.5.28+ and will require Java 8, CentOs 7
> and the installation of OpenSSL, Tomcat Native and APR. Most of this will
> be taken care of by the RPM. Here is the migration documentation :
>
> Traffic Router - Migrating to 3.0 <#contents>
>
> Contents
>
> - Traffic Router - Migrating to 3.0 <#traffic-router-migrating-to-3-0>
> - Release Notes v3.0 <#release-notes-v3-0>
> - System Requirements <#system-requirements>
> - Upgrade Procedure <#upgrade-procedure>
> - Development Environment Upgrade <#development-environment-upgrade>
>
> Release Notes v3.0 <#contents>
>
> - Replaced custom Java SNI implementation with a native implementation
> using tomcat-native, apr (Apache Portable Runtime) and OpenSSL This
> should
> significantly improve the performance of routing ‘https’ delivery
> services.
> - Upgraded to Tomcat 8.5.30
> - Separated the Traffic Router installation from the Tomcat deployment
> and created a new ‘tomcat’ package for installing Tomcat. Traffic Router
> and Tomcat can now be upgraded independently
> - Converted Traffic Router to a ‘systemd’ service
> - Modified the development test and dev deployment processes to be more
> consistent with production
>
> System Requirements <#contents>
>
> - Centos 7.2
> - OpenSSL >= 1.0.2 installed
> - JDK >= 8.0 installed or available in Yum repository
> - APR (Apache Portable Runtime) >= 1.4.8-3 installed or available in Yum
> repository
> - Tomcat Native >= 1.2.16 installed or available in Yum repository
> - tomcat >= 8.5-28 installed or available in Yum repository (This
> package is created automatically by the Traffic Router build process)
>
> Upgrade Procedure <#contents>
>
> - upload tomcat.rpm to a Yum repository
> - update the traffic_router package
> - restore property files
>
> Upload tomcat.rpm
>
> The ‘tomcat’ package gets created when you build Traffic Router. You must
> either add it to the yum repo where you keep all of the Traffic Control
> packages, or manually copy it to the servers where you will be installing
> Traffic Router and run yum install [path to package] It is preferable that
> you add it to your Yum repository because then it will be installed
> automatically when you perform the Traffic Router update.
> Update the traffic_router Package
>
> If openssl, apr, tomcat-native, jdk and tomcat_tr packages are all in an
> available repository then you just need to run: yum update traffic_router.
> This will first cause the apr, tomcat-native, jdk and tomcat packages to be
> installed. When the ‘tomcat’ package runs, it will cause any older versions
> of traffic_router or tomcat to be uninstalled. This is because the previous
> versions of the traffic_router package included an untracked installation
> of tomcat.
> Restore Property Files
>
> Replace the Traffic Router properties files with the correct ones for the
> CDN. The properties files from the previous install can be found at:
> /opt/traffic_router/conf/traffic_ops.properties.rpmsaved &
> traffic_monitor.properties.rpmsaved.
> Development Environment Upgrade <#contents>
>
> If you already have a development environment set up for the previous
> version of Traffic Router, then you will need to get and install these
> libraries on your workstation: openssl, apr and tomcat-native. Also,
> whenever you run either ‘mvn clean verify’ or ‘TrafficRouterStart’ you will
> need to pass a command line parameter telling Java where to look for the
> ‘tomcat-native’ libraries:mvn clean verify -Djava.library.path=[tomcat
> native library path on your box]java -Djava.library.path=[tomcat native
> library path on your box] TrafficRouterStart
>