+1 Known Issues I had to adapt for: 3181 - SSL certificates not self-signed but lacking SKI & AKI extensions can lead to fatal loss of all Traffic Routers in associated CDN 2828 - Self-signed certificate generation via TP or the associated API endpoint doesn't work
I verified: Using the RC4 tarball, I was able to produce a full set of RPMs Using those RPMs and normal external sources, I was able to install the following topology inside VMs using global IP and DNS 1 Traffic Ops 1 Traffic Portal 2 Traffic Routers 4 Traffic Monitors 1 Traffic Stats 2 Traffic Vaults 3 ATS Edges 2 Grove Edges 2 ATS Mids These were arranged in 1 CDN spanning 4 cachegroups with proper configuration. I also created 28 Delivery services spanning each Content Routing Type (excluding ANY_MAP), each Protocol, each steering/client steering target type, each QString, and various combinations surrounding MSO. Each of which returned a 200 response on a curl through the environment and observable via traffic stats and the traffic portal dashboard. Jonathan G On 2/6/19, 3:28 PM, "Dan Kirkwood" <[email protected]> wrote: +1 Verified the following: - sha checksum correct - gpg signature correct - RELEASE-3.0.0-RC4 tag signed correctly - BUILD_NUMBER file indicates the correct commit count and hash - all components build with `./pkg -v` - saw same problem with `weasel`, but it's pointing out files in `.m2` dir (from TR build `mvn`) and the `BUILD_NUMBER` file -- these should be ignored by weasel, but not an issue for this release - installed TO and TP on a VM -- basic tests pass -dan On Tue, Feb 5, 2019 at 9:27 AM Dave Neuman <[email protected]> wrote: > +1 > I verified the following: > Sha512, > GPG signature (had an warning but that is ok) > Built all components using pkg on a fresh Centos7.5 VM. It looked like > there might be issues with weasel, but I am not going to -1 because of that > because it's not critical to running Traffic Control. > > Thanks, > Dave > > On Fri, Feb 1, 2019 at 11:52 AM Gelinas, Derek <[email protected]> > wrote: > > > Hello All, > > I've prepared a release for v3.0.0-RC4 > > The vote is open for at least 72 hours and passes if a majority of at > > least 3 +1 PPMC votes are cast. > > [ ] +1 Approve the release > > [ ] -1 Do not release this package because ... > > Changes since 2.2 > > > https://github.com/apache/trafficcontrol/compare/2.2.x...RELEASE-3.0.0-RC4 > > This corresponds to git: > > Hash: 91b2edbcb4be8d38902160b7a4e28378aa5fb3f1 > > Tag: RELEASE-3.0.0-RC4 > > Which can be verified with the following: git tag -v RELEASE-3.0.0-RC4 > > My code signing key is available here: > > http://keys.gnupg.net/pks/lookup?search=0x05BE71D9&op=vindex > > Make sure you refresh from a key server to get all relevant signatures. > > The source .tgz file, pgp signature (.asc signed with my key from > > above), and sha512 checksums are provided here: > > https://dist.apache.org/repos/dist/dev/trafficcontrol/3.0.0/RC4/ > > Thanks! > > Derek > > > > >
