This is an automated email from the ASF dual-hosted git repository.
dangogh pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficcontrol.git
The following commit(s) were added to refs/heads/master by this push:
new e5d6040 removes unused configurable TP ds descriptions (#3652)
e5d6040 is described below
commit e5d60402f1955365cf39e2d4273a6de47bdc4eda
Author: Jeremy Mitchell <[email protected]>
AuthorDate: Wed Jun 5 08:26:54 2019 -0600
removes unused configurable TP ds descriptions (#3652)
---
.../app/src/traffic_portal_properties.json | 207 ---------------------
1 file changed, 207 deletions(-)
diff --git a/traffic_portal/app/src/traffic_portal_properties.json
b/traffic_portal/app/src/traffic_portal_properties.json
index e0b2dc6..1666340 100644
--- a/traffic_portal/app/src/traffic_portal_properties.json
+++ b/traffic_portal/app/src/traffic_portal_properties.json
@@ -165,213 +165,6 @@
"regionalGeoBlocking": false,
"ccrDnsTtl": 30,
"anonymousBlockingEnabled": false
- },
- "descriptions": {
- "_comments": "This is the text used to configure delivery service
field titles/descriptions",
- "active": {
- "title": "Active",
- "desc": "Whether or not this delivery service is active on the CDN
and is capable of traffic."
- },
- "anonymousBlockingEnabled": {
- "title": "Anonymous Blocking",
- "desc": "Set to true to enable blocking of anonymous IPs for this
delivery service. <b>Note:<b> Requires Geolocation provider's Anonymous IP
database."
- },
- "cacheurl": {
- "title": "Cache URL expression",
- "desc": "Allows you to manipulate the cache key of the incoming
requests. Normally, the cache key is the origin domain. This can be changed so
that multiple services can share a cache key, can also be used to preserve
cached content if service origin is changed.<br><b>Note:</b> Only valid in ATS
6. X and earlier. Must be empty if using ATS 7. X and / or the <a href =
\"https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/cachekey.en.html\";
target=\"_blank\">cac [...]
- },
- "ccrDnsTtl": {
- "title": "Delivery Service DNS TTL",
- "desc": "The Time To Live on the DNS record for the Traffic Router
A and AAAA records. Setting too high or too low will result in poor caching
performance."
- },
- "cdnId": {
- "title": "CDN",
- "desc": "The CDN in which the delivery service belongs to."
- },
- "checkPath": {
- "title": "Check Path",
- "desc": "A path (ex: /crossdomain.xml) to verify the connection to
the origin server with. This can be used by Check Extension scripts to do
periodic health checks against the delivery service."
- },
- "consistentHashRegex": {
- "title": "Consistent Hash Regex",
- "desc": "Regex used to extract parts of the request path using
grouping in order to build a consistent request string to be used for cache
selection. If this field is set on a steering delivery service, it will
override the regex set on the target delivery services.<br><br><a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_router.html#pattern-based-consistenthash\";
target=\"_blank\">See Pattern-Based Consistent Hashing</a>"
- },
- "deepCachingType": {
- "title": "Deep Caching",
- "desc": "Enables clients to be routed to the closest possible deep
edge caches on a per Delivery Service basis.<br><br><a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_router.html#rl-deep-cache\";
target=\"_blank\">See Deep Caching</a>"
- },
- "displayName": {
- "title": "Display Name",
- "desc": "Name of the service that appears in the Traffic portal.
No character restrictions."
- },
- "dnsBypassCname": {
- "title": "DNS Bypass CNAME",
- "desc": "Domain name to overflow requests when the Max Bps or Max
Tps for this delivery service exceeds."
- },
- "dnsBypassIp": {
- "title": "DNS Bypass IP",
- "desc": "IPv4 address to overflow requests when the Max Bps or Max
Tps for this delivery service exceeds."
- },
- "dnsBypassIp6": {
- "title": "DNS Bypass IPv6",
- "desc": "IPv6 address to overflow requests when the Max Bps or Max
Tps for this delivery service exceeds."
- },
- "dnsBypassTtl": {
- "title": "DNS Bypass TTL",
- "desc": "TTL for the DNS bypass domain or IP when threshold
exceeds."
- },
- "dscp": {
- "title": "DSCP",
- "desc": "The Differentiated Services Code Point (DSCP) value to
mark IP packets to the client with."
- },
- "edgeHeaderRewrite": {
- "title": "Edge Header Rewrite Rules",
- "desc": "Headers can be added or altered at each layer of the CDN.
You must tell us four things: the action, the header name, the header value,
and the direction to apply. The action will tell us whether we are adding,
removing, or replacing headers. The header name and header value will determine
the full header text. The direction will determine whether we add it before we
respond to a request or before we make a request further up the chain in the
server hierarchy. Example [...]
- },
- "geoLimitRedirectURL": {
- "title": "Geo Limit Redirect URL",
- "desc": "Traffic Router will redirect to this URL when Geo Limit
check fails.<br><br>See <a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_router.html#rl-tr-ngb\";
target=\"_blank\">GeoLimit Failure Redirect</a> feature..."
- },
- "geoLimit": {
- "title": "Geo Limit",
- "desc": "Some services are intended to be limited by geography.
The possible settings are:<br><br><ul><li>None: Do not limit by
geography.</li><li>CZF only: If the requesting IP is not in the Coverage Zone
File, do not serve the request.</li><li>CZF + US: If the requesting IP is not
in the Coverage Zone File or not in the United States, do not serve the
request.</li><br>"
- },
- "geoLimitCountries": {
- "title": "Geo Limit Countries",
- "desc": "How (if at all) is this service to be limited by
geography. Example Country Codes: CA, IN, PR."
- },
- "geoProvider": {
- "title": "Geolocation Provider",
- "desc": "Choose which Geolocation database provider, company that
collects data on the location of IP addresses, to use."
- },
- "globalMaxMbps": {
- "title": "Global Max Mbps",
- "desc": "The maximum bits per second this delivery service can
serve across all EDGE caches before traffic will be diverted to the bypass
destination. For a DNS delivery service, the Bypass Ipv4 or Ipv6 will be used
(depending on whether this was a A or AAAA request), and for HTTP delivery
services the Bypass FQDN will be used."
- },
- "globalMaxTps": {
- "title": "Global Max TPS",
- "desc": "The maximum transactions this delivery service can serve
across all EDGE caches before traffic will be diverted to the bypass
destination. For a DNS delivery service, the Bypass Ipv4 or Ipv6 will be used
(depending on whether this was a A or AAAA request), and for HTTP delivery
services the Bypass FQDN will be used."
- },
- "fqPacingRate": {
- "title": "Fair Queuing Pacing Rate Bps",
- "desc": "The maximum bytes per second a cache will delivery on any
single TCP connection. This uses the Linux kernel's Fair Queuing
setsockopt(SO_MAX_PACING_RATE) to limit the rate of delivery."
- },
- "httpBypassFqdn": {
- "title": "HTTP Bypass FQDN",
- "desc": "Traffic Router will redirect to this FQDN (with the same
path) when the Max Bps or Max Tps for this delivery service exceeds."
- },
- "infoUrl": {
- "title": "Info URL",
- "desc": "Free text field used to enter a URL which provides
information about the service."
- },
- "initialDispersion": {
- "title": "Initial Dispersion",
- "desc": "Determines number of machines content will be placed on
within a cache group. Setting too high will result in poor caching performance."
- },
- "ipv6RoutingEnabled": {
- "title": "IPv6 Routing Enabled",
- "desc": "Default is True, entering False allows you to turn off
CDN response to IPv6 requests"
- },
- "logsEnabled": {
- "title": "Logs Enabled",
- "desc": "Allows you to turn on/off logging for the service"
- },
- "longDesc": {
- "title": "Long Description",
- "desc": "Free text field that describes the purpose of the
delivery service and will be displayed in the portal as a description field."
- },
- "longDesc1": {
- "title": "Long Description 2",
- "desc": "Free text field not currently used in configuration. For
example, you can use this field to describe your customer type."
- },
- "longDesc2": {
- "title": "Long Description 3",
- "desc": "Free text field not currently used in configuration."
- },
- "maxDnsAnswers": {
- "title": "Max DNS Answers",
- "desc": "It is used to restrict the number of cache IP addresses
that the CCR will hand back. A numeric value from 1 to 15 which determines how
many caches your content will be spread across in a particular site. When a
customer requests your content they will get 1 to 15 IP addresses back they can
use. These are rotated in each response. Ideally the number will reflect the
amount of traffic. 1 = trial account with very little traffic, 2 = small
production service. Add 1 more [...]
- },
- "midHeaderRewrite": {
- "title": "Mid Header Rewrite Rules",
- "desc": "Headers can be added or altered at each layer of the CDN.
You must tell us four things: the action, the header name, the header value,
and the direction to apply. The action will tell us whether we are adding,
removing, or replacing headers. The header name and header value will determine
the full header text. The direction will determine whether we add it before we
respond to a request or before we make a request further up the chain in the
server hierarchy. Example [...]
- },
- "missLat": {
- "title": "Geo Miss Default Latitude",
- "desc": "Default Latitude for this delivery service. When client
localization fails for both Coverage Zone and Geo Lookup, the client will be
routed as if it was at this lat."
- },
- "missLong": {
- "title": "Geo Miss Default Longitude",
- "desc": "Default Longitude for this delivery service. When client
localization fails for both Coverage Zone and Geo Lookup, the client will be
routed as if it was at this long."
- },
- "multiSiteOrigin": {
- "title": "Use Multi Site Origin Feature",
- "desc": "Set True/False to enable/disable the Multi Site Origin
feature for this delivery service.<br><br><a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-multi-site-origin\";
target=\"_blank\">See Multi Site Origin.</a>"
- },
- "orgServerFqdn": {
- "title": "Origin Server Base URL",
- "desc": "The Origin Server’s base URL which includes the protocol
(http or https). Example: http://movies.origin.com. Must be a domain only, no
directories or IP addresses"
- },
- "originShield": {
- "title": "Origin Shield (Pipe Delimited String)",
- "desc": "Add another forward proxy upstream of the mid caches.
Example: go_direct=true will allow the Mid to hit the origin directly instead
of failing if the origin shield is down. Experimental Feature."
- },
- "profileId": {
- "title": "Delivery Service Profile",
- "desc": "Only used if a delivery service uses configurations that
specifically require a profile. Example: MSO configurations or cachekey plugin
would require a ds profile to be used."
- },
- "protocol": {
- "title": "Protocol",
- "desc": "The protocol to serve this delivery service to the
clients with:<br><br> <ul><li>HTTP: Deliver only HTTP traffic</li><li>HTTPS:
Deliver only HTTPS traffic </li><li>HTTP AND HTTPS: Deliver both types of
traffic</li><li>HTTP TO HTTPS: Deliver HTTP traffic as HTTPS traffic.
</li></ul><br>"
- },
- "qstringIgnore": {
- "title": "Query String Handling",
- "desc": "How to treat query strings:<br><br><ul><li>0 use in cache
key and hand up to origin: Each unique query string is treated as a unique
URL.</li><li>1 Do not use in cache key, but pass up to origin: 2 URLs that are
the same except for the query string will match and cache HIT, while the origin
still sees original query string in the request.</li><li>2 Drop at edge: 2 URLs
that are the same except for the query string will match and cache HIT, while
the origin will not s [...]
- },
- "rangeRequestHandling": {
- "title": "Range Request Handling",
- "desc": "How to treat range requests.<br><br><ul><li>0: Do not
cache (ranges requested from files that are already cached due to a non range
request will be a HIT)</li><li>1: Use the <a
href=\"https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/background_fetch.en.html\";
target=\"_blank\">background_fetch plugin.</a></li><li>2: Use the
cache_range_requests plugin.</li></ul>"
- },
- "regexRemap": {
- "title": "Regex remap expression",
- "desc": "Allows remapping of incoming requests URL using regex
pattern matching to search/replace text.<br><br><a
href=\"https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_remap.en.html\";
target=\"_blank\">See ATS documentation on regex remap</a><br><b>Note:</b> You
will not be able to save a Regex Remap Expression if you have Query String
Handling set to drop query strings at the edge. <a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin [...]
- },
- "regionalGeoBlocking": {
- "title": "Regional Geoblocking",
- "desc": "Define regional geo-blocking rules for delivery services
in a JSON format and set it to True/False. <a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/quick_howto/regionalgeo.html#configure-regional-geo-blocking-rgb\";
target=\"_blank\">See Regional Geo-blocking</a>"
- },
- "remapText": {
- "title": "Raw remap text",
- "desc": "For HTTP and DNS delivery services, this will get added
to the end of the remap line on the cache verbatim. For ANY_MAP delivery
services this is the remap line."
- },
- "routingName": {
- "title": "Routing Name",
- "desc": "The routing name to use for the delivery FQDN, i.e.
routing-name.deliveryservice.cdn-domain. It must be a valid hostname without
periods."
- },
- "signingAlgorithm": {
- "title": "Signing Algorithm",
- "desc": "Type of URL signing method to sign the
URLs:<br><ul><li>null: token based auth is not enabled for this delivery
service.</li><li>'url_sig': URL Sign token based auth is enabled for this
delivery service.</li><li>'uri_signing': URI Signing token based auth is
enabled for this delivery service.</li></ul><br><br><a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-signed-urls\";
target=\"_blank\">See Token Based Authentication</a>"
- },
- "tenantId": {
- "title": "Tenant",
- "desc": "Name of company or division of company who owns account.
Allows you to group your services and control access. Tenants are setup as a
simple hierarchy where you may create parent / child accounts."
- },
- "trRequestHeaders": {
- "title": "Traffic Router Log Request Headers",
- "desc": "List of header keys on separate lines (or separated by
__RETURN__ to simulate a line ending). Listed headers will be included in TR
access log entries under the 'rh=' token."
- },
- "trResponseHeaders": {
- "title": "Traffic Router Additional Response Headers",
- "desc": "List of header name:value pairs on separate lines (or
separated by __RETURN__ to simulate a line ending). Listed pairs will be
included in all TR HTTP responses."
- },
- "typeId": {
- "title": "Content Routing Type",
- "desc": "DNS is the standard routing type for most CDN services.
HTTP Redirect is a specialty routing service that is primarily used for video
and large file downloads where localization and latency are significant
concerns. A \"Live\" routing type should be used for all live
services.<br><br><a
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-ds-types\";
target=\"_blank\">See Delivery Service Types.</a>"
- },
- "xmlId": {
- "title": "Key (XML ID)",
- "desc": "This id becomes a part of the CDN service domain in the
form http://cdn.service-key.company.com/. Must be all lowercase, no spaces or
special characters. May contain dashes."
- }
}
},
"charts": {
