This is an automated email from the ASF dual-hosted git repository.
dgelinas pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/trafficcontrol-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 3aba27c Update for Release 3.0.0
3aba27c is described below
commit 3aba27c2e11ed79825fa960780ef49e20ffe0e97
Author: Derek Gelinas <[email protected]>
AuthorDate: Wed Mar 6 13:13:31 2019 -0500
Update for Release 3.0.0
---
index.html | 3 +-
releases/index.html | 83 ++++++++++++++++++++++++++++++++++++++++++++---------
2 files changed, 71 insertions(+), 15 deletions(-)
diff --git a/index.html b/index.html
index 2b0aebe..5922b1b 100644
--- a/index.html
+++ b/index.html
@@ -105,6 +105,7 @@
<div class="card">
<div class="card-body">
<span class="far fa-newspaper fa-7x float-right" style="color:
#343a40;"></span>
+ <ul><li><strong>March 5, 2019</strong> - Apache Traffic
Control 3.0.0 Released</li></ul>
<ul><li><strong>June 18, 2018</strong> - Apache Traffic Control
2.2.0 Released</li></ul>
<ul><li><strong>May 16, 2018</strong> - Apache Traffic Control
graduates to TLP</li></ul>
<ul>
@@ -227,7 +228,7 @@
class="float-left"
style="margin-right: 15px;"></a>
- Copyright © 2018 <a
href="https://www.apache.org";>The Apache Software Foundation</a>.
+ Copyright © 2019 <a
href="https://www.apache.org";>The Apache Software Foundation</a>.
Licensed under the <a
href="https://www.apache.org/licenses/";>Apache License, Version 2.0</a>
</p>
<p>
diff --git a/releases/index.html b/releases/index.html
index 929d0ca..e19d57b 100644
--- a/releases/index.html
+++ b/releases/index.html
@@ -94,30 +94,47 @@
<div class="card-deck">
<div class="card">
<div class="card-body">
- <h4 class="card-title">Apache Traffic Control 2.2.0</h4>
+ <h4 class="card-title">Apache Traffic Control 3.0.0</h4>
<h5>Release Notes</h5>
- <h6>Per–Delivery Service Routing Names</h6>
+ <h6>Backup Edge Cache Group</h6>
<p class="card-text">
- You can now choose a Delivery Service's Routing Name (rather
than a hardcoded "tr" or "edge" name). This might require a few pre-upgrade
steps detailed <a
href="http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/migration_from_20_to_22.html#per-deliveryservice-routing-names";>here</a>.
+ If the matched group in the CZF is not available, this list
of backup edge cache group configured via Traffic Ops API can be used as
backup. In the event of all backup edge cache groups not available, GEO
location can be optionally used as further backup. APIs detailed <a
href="http://traffic-control-cdn.readthedocs.io/en/latest/development/traffic_ops_api/v12/cachegroup_fallbacks.html";>here</a>.
</p>
- <h6>Delivery Service Requests</h6>
+ <h6>Traffic Ops Golang Proxy Endpoints</h6>
<p class="card-text">
- When enabled, delivery service requests are created when ALL
users attempt to create, update or delete a delivery service. This allows users
with higher level permissions to review delivery service changes for
completeness and accuracy before deploying the changes. See <a
href="https://traffic-control-cdn.readthedocs.io/en/latest/admin/quick_howto/ds_requests.html#ds-requests";>here</a>.
+ <ul>
+ <li>/api/1.3/origins
<code>(GET,POST,PUT,DELETE)</code></li>
+ <li>/api/1.3/coordinates
<code>(GET,POST,PUT,DELETE)</code></li>
+ <li>/api/1.3/staticdnsentries
<code>(GET,POST,PUT,DELETE)</code></li>
+ </ul>
</p>
- <h6>Fair Queuing Pacing</h6>
+ <h6>Delivery Service Origins Refactor</h6>
<p class="card-text">
- Using the FQ Pacing Rate parameter in Delivery Services
allows operators to limit the rate of individual sessions to the edge cache.
This feature requires a Trafficserver RPM containing the fq_pacing experimental
plugin AND setting 'fq' as the default Linux qdisc in sysctl.
+ The Delivery Service API now creates/updates an Origin
entity on Delivery Service creates/updates, and the org_server_fqdn column in
the deliveryservice table has been removed. The org_server_fqdn data is now
computed from the Delivery Service's primary origin (note: the name of the
primary origin is the xml_id of its delivery service).
</p>
- <h6>Backup Edge Cache Group</h6>
+ <h6>Cachegroup-Coordinate Refactor</h6>
<p class="card-text">
- If the matched group in the CZF is not available, this list
of backup edge cache group configured via Traffic Ops API can be used as
backup. In the event of all backup edge cache groups not available, GEO
location can be optionally used as further backup. APIs detailed <a
href="http://traffic-control-cdn.readthedocs.io/en/latest/development/traffic_ops_api/v12/cachegroup_fallbacks.html";>here</a>.
+ The Cachegroup API now creates/updates a Coordinate entity
on Cachegroup creates/updates, and the latitude and longitude columns in the
cachegroup table have been replaced with coordinate (a foreign key to
Coordinate). Coordinates created from Cachegroups are given the name
from_cachegroup_\<cachegroup name\>.
</p>
- <p class="card-text">Apache Traffic Control 2.2.0 is available
here:
+ <h6>Geolocation-based Client Steering</h6>
+ <p class="card-text">
+ Two new steering target types are available to use for
CLIENT_STEERING delivery services: STEERING_GEO_ORDER and STEERING_GEO_WEIGHT.
When targets of these types have an Origin with a Coordinate, Traffic Router
will order and prioritize them based upon the shortest total distance from
client -> edge -> origin. Co-located targets are grouped together and can be
weighted or ordered within the same location using STEERING_GEO_WEIGHT or
STEERING_GEO_ORDER, respectively.
+ </p>
+ <h6>Tenancy</h6>
+ <p>
+ Tenancy is now the default behavior in Traffic Ops. All
database entries that reference a tenant now have a default of the root tenant.
This eliminates the need for the use_tenancy global parameter and will allow
for code to be simplified as a result. If all user and delivery services
reference the root tenant, then there will be no difference from having
use_tenancy set to 0.
+ </p>
+ <h6>Cachegroup Localization Methods</h6>
+ <p class="card-text">
+ The Cachegroup API now supports an optional
localizationMethods field which specifies the localization methods allowed for
that cachegroup (currently 'DEEP_CZ', 'CZ', and 'GEO'). By default if this
field is null/empty, all localization methods are enabled. After Traffic Router
has localized a client, it will only route that client to cachegroups that have
enabled the localization method used. For example, this can be used to prevent
GEO-localized traffic (i.e. most like [...]
+ </p>
+
+ <p class="card-text">Apache Traffic Control 3.0.0 is available
here:
<ul>
- <li><a
href="https://www.apache.org/dyn/closer.cgi/trafficcontrol/2.2.0/apache-trafficcontrol-2.2.0.tar.gz";>Tarball</a></li>
- <li><a
href="https://www.apache.org/dist/trafficcontrol/2.2.0/apache-trafficcontrol-2.2.0.tar.gz.sha512";>SHA-512</a></li>
- <li><a
href="https://www.apache.org/dist/trafficcontrol/2.2.0/apache-trafficcontrol-2.2.0.tar.gz.asc";>ASC</a></li>
- <li><a
href="http://trafficcontrol.apache.org/downloads/profiles/2.2.x/";>Default
Profiles</a></li>
+ <li><a
href="https://www.apache.org/dyn/closer.cgi/trafficcontrol/3.0.0/apache-trafficcontrol-3.0.0.tar.gz";>Tarball</a></li>
+ <li><a
href="https://www.apache.org/dist/trafficcontrol/3.0.0/apache-trafficcontrol-3.0.0.tar.gz.sha512";>SHA-512</a></li>
+ <li><a
href="https://www.apache.org/dist/trafficcontrol/3.0.0/apache-trafficcontrol-3.0.0.tar.gz.asc";>ASC</a></li>
+ <li><a
href="http://trafficcontrol.apache.org/downloads/profiles/3.0.x/";>Default
Profiles</a></li>
</ul>
</p>
</div>
@@ -158,6 +175,44 @@ or
<br/><br/>
<h2>Past Releases</h2>
+ <!-- Release 2.2 -->
+ <div class="row">
+ <div class="col-sm-12">
+ <div class="card-deck">
+ <div class="card">
+ <div class="card-body">
+ <h4 class="card-title">Apache Traffic Control 2.2.0</h4>
+ <h5>Release Notes</h5>
+ <h6>Per–Delivery Service Routing Names</h6>
+ <p class="card-text">
+ You can now choose a Delivery Service's Routing Name (rather
than a hardcoded "tr" or "edge" name). This might require a few pre-upgrade
steps detailed <a
href="http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/migration_from_20_to_22.html#per-deliveryservice-routing-names";>here</a>.
+ </p>
+ <h6>Delivery Service Requests</h6>
+ <p class="card-text">
+ When enabled, delivery service requests are created when ALL
users attempt to create, update or delete a delivery service. This allows users
with higher level permissions to review delivery service changes for
completeness and accuracy before deploying the changes. See <a
href="https://traffic-control-cdn.readthedocs.io/en/latest/admin/quick_howto/ds_requests.html#ds-requests";>here</a>.
+ </p>
+ <h6>Fair Queuing Pacing</h6>
+ <p class="card-text">
+ Using the FQ Pacing Rate parameter in Delivery Services
allows operators to limit the rate of individual sessions to the edge cache.
This feature requires a Trafficserver RPM containing the fq_pacing experimental
plugin AND setting 'fq' as the default Linux qdisc in sysctl.
+ </p>
+ <h6>Backup Edge Cache Group</h6>
+ <p class="card-text">
+ If the matched group in the CZF is not available, this list
of backup edge cache group configured via Traffic Ops API can be used as
backup. In the event of all backup edge cache groups not available, GEO
location can be optionally used as further backup. APIs detailed <a
href="http://traffic-control-cdn.readthedocs.io/en/latest/development/traffic_ops_api/v12/cachegroup_fallbacks.html";>here</a>.
+ </p>
+ <p class="card-text">Apache Traffic Control 2.2.0 is available
here:
+ <ul>
+ <li><a
href="https://www.apache.org/dyn/closer.cgi/trafficcontrol/2.2.0/apache-trafficcontrol-2.2.0.tar.gz";>Tarball</a></li>
+ <li><a
href="https://www.apache.org/dist/trafficcontrol/2.2.0/apache-trafficcontrol-2.2.0.tar.gz.sha512";>SHA-512</a></li>
+ <li><a
href="https://www.apache.org/dist/trafficcontrol/2.2.0/apache-trafficcontrol-2.2.0.tar.gz.asc";>ASC</a></li>
+ <li><a
href="http://trafficcontrol.apache.org/downloads/profiles/2.2.x/";>Default
Profiles</a></li>
+ </ul>
+ </p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+
<!-- Release 2.1 -->
<div class="row">
<div class="col-sm-12">
