Skip to content
This repository has been archived by the owner on Nov 13, 2018. It is now read-only.

Traffic Control Release 1.3.0
Compare
Choose a tag to compare
@PSUdaemon PSUdaemon released this 01 Feb 16:19
· 2418 commits to master since this release
RELEASE-1.3.0
5449654

Release Notes for Traffic Control 1.3.0

The post-install has been cleaned up. As always, a database backup before an upgrade is suggested.

CDN_name migration

If you upgrade from a pre-1.2.0 release, there is a migration from the profile parameter CDN_name to the cdn table. This also means that if a profile didn't have a CDN_name, some components won't show on the UI. Make sure that all profiles in use have a CDN_name parameter prior to upgrade.

In the event where the CDN_name wasn't part of the parameter, you will need to update the servers table with the proper cdn_id.

Content Revalidation

The revalidation feature doesn't work out of the box. The entry id=1 in the job_agent table MUST exist as well as name=PURGE must be present in the job_status table.

Known issues

  • The profiles included in the release for MID caches are not complete or don't work. See #855.
  • A CDN MUST have a Mid cache in release 1.3.0. See #943.
  • To generate a top level domain configuration, a CDN MUST have both a DNS and HTTP Delivery service. See #987. Service, top level domain zone not created
  • ORT - Regex Remap Text not handled. See #968.
  • The RNAME for the SOA record can be configured in Traffic Ops by setting the 'tld.soa.admin' parameter on the Traffic Router profile (e.g. [email protected]). This is backwards compatible so if an email address is not entered it will work as it does currently.
  • The Request Headers you wish to log can be configured at a delivery service or global (CDN) level.
    • To configure at the CDN level, create a parameter called 'LogRequestHeaders' where config file value is 'CRConfig.json' and value is the headers you wish to log separated by RETURN (e.g. 'Accept RETURN Content-Type')
    • To configure at the Delivery Service level, edit the delivery service and set the 'Traffic Router Log Request Headers' field equal to the headers you wish to log separated by RETURN (e.g. 'Accept RETURN Content-Type')
  • Federations Polling Stats are now available in the 'updateTracker' section of css stats: (http://:3333/crs/stats)
  • Federation location information is now available via the crs/stats/ip/:ipAddress API: (http://:3333/crs/stats/ip/)
  • Static Zone and Dynamic Zone cache (Google Guava cache) stats are now available via the following API: (http://:3333/crs/stats/zones/caches)
  • In order to support the new build process, you will need to set a TRAFFIC_CONTROL_VERSION environment variable before running maven in Traffic Router and Traffic Monitor (e.g. export TRAFFIC_CONTROL_VERSION=foo && mvn clean verify)
  • Other parameters:

    • The SOA minimum for the TLD is now propagated to Delivery Services. This value should be set to 30 seconds so that in the case of a NXDOMAIN, the negative response is only cached for 30 seconds.

      tld.soa.minimum CRConfig.json 30

To configure federations, configure the following parameters in Traffic Ops:

federationmapping.polling.url     CRConfig.json     https://${toHostname}/internal/api/1.2/federations.json
federationmapping.polling.interval     CRConfig.json     30000 (30 seconds)

update the following ttys (as part of DNSSEC) :

tld.ttls.DNSKEY   CRConfig.json     30
tld.ttls.DS     CRConfig.json     30

for guava cache:

zonemanager.cache.maintenance.interval     CRConfig.json     300
keystore.maintenance.interval                CRConfig.json        300
dnssec.dynamic.response.expiration            CRConfig.json        300s    <-- note that is 300s, the trailing "s" is 100% necessary here

Optional:

consistent.dns.routing     CRConfig.json     true (default is false)
dynamic.cache.primer.enabled     CRConfig.json     true (default is true)
dynamic.cache.primer.limit     CRConfig.json     1000 (default is 500)
dnssec.allow.expired.keys     CRConfig.json     true (default is true)
keystore.api.url     CRConfig.json     true (default is https://${toHostname}/api/1.1/cdns/name/${cdnName}/dnsseckeys.json)
api.auth.url     CRConfig.json     true (default is https://${toHostname}/api/1.1/user/login)

Changes to properties files:
Properties files:

dns.properties
    Remove dns.sec.keyserver.username
    Remove dns.sec.keyserver.password

traffic_ops.properties
    Modify traffic_ops.password=FIXME

Changes with Traffic Control 1.3.0

#53 - Expose edge fqdn and edge alias fqdn(s) for a delivery service through the traffic ops api
#196 - Traffic Router sends NXDOMAIN for http.routing.name when no caches are assigned to the delivery service
#607 - Enabling bond0 on servers requires Traffic Monitor restart
#619 - Add licenses
#634 - Upped version to match next release.
#655 - Redirect stdout and stderr to a log file
#657 - Remove reference to code.google.com repo
#715 - Content revalidation does not work for "ANY_MAP" deliveryservice.
#800 - Postinstall fails due to unreachable web dependancies (jMenu)
#809 - check for rpmbuild; fix .pl permissions in rpm
#813 - update traffic_router version using env rather than property on cmd line
#817 - remove jmenu entries -- were removed from original source repo
#826 - Backport of changes in master to 1.3.x.
#831 - add missing jmenu files; remove from .gitignore
#839 - Regression: token not being set when submitting a password reset request
#844 - Fixes #839 - regression bug
#848 - Exclude unnecessary transitive dependency wicket-atmosphere from Traffic Monitor
#911 - Traffic Router and Ops backports from master for 1.3.0 RC4 for DNSSEC related bug fixes.
#914 - Backport of bug fix for NetworkNode not correctly dealing with overlapping subnets, which resolves #856.
#918 - set influxdb to specific version ; correct capitalization of Comcast …
#921 - Background DNSSEC key refresh changes
#930 - Fixes an issue where forked processes become defunct rather than exit…
#957 - use ref for hash value

Assets 2
Loading