mitchell852 commented on a change in pull request #2236: update portal info 
bubbles
URL: 
https://github.com/apache/incubator-trafficcontrol/pull/2236#discussion_r187351587
 
 

 ##########
 File path: traffic_portal/app/src/traffic_portal_properties.json
 ##########
 @@ -178,71 +178,71 @@
           "_comments": "This is the text used to configure delivery service 
field titles/descriptions",
           "active": {
             "title": "Active",
-            "desc": "When this is set to false Traffic Router will not serve 
DNS or HTTP responses for this delivery service."
+            "desc": "Whether or not this delivery service is active on the CDN 
and is capable of traffic."
           },
           "cacheurl": {
             "title": "Cache URL expression",
-            "desc": "Cache URL rule to apply to this delivery 
service.<br><br>See <a 
href=\"https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/cacheurl.en.html\";
 target=\"_blank\">ATS documentation on cacheurl...</a>"
+            "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\">cachekey plugin.</a><br><br>See <a href = 
\"https://docs.trafficserver.apache.org/en/6.2.x/admin-guide/plugins/cacheurl.en.html\";
 target=\"_blank\">ATS documentation on cacheurl </a>"
           },
           "ccrDnsTtl": {
             "title": "Delivery Service DNS TTL",
-            "desc": "The Time To Live on the DNS record for the Traffic Router 
A and AAAA records."
+            "desc": "(For DNS routed delivery services only) The Time To Live 
on the DNS record for the Traffic Router A and AAAA records. Default value is 
30 seconds. 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."
+            "desc": "The CDN in which the delivery service belongs."
           },
           "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."
           },
           "deepCachingType": {
             "title": "Deep Caching",
-            "desc": "When to do deep caching for this delivery 
service.<br><br>See <a 
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_router.html#rl-deep-cache\";
 target=\"_blank\">Deep Caching</a> for more details..."
+            "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": "A human-readable name for the delivery service."
+            "desc": "Name of the service that appears in the Traffic portal. 
No character restrictions."
           },
           "dnsBypassCname": {
             "title": "DNS Bypass CNAME",
-            "desc": "Description required"
+            "desc": "(For DNS routed delivery services only) Domain name to 
overflow requests when the the max Bps or Max Tps for this delivery service are 
exceeded."
           },
           "dnsBypassIp": {
             "title": "DNS Bypass IP",
-            "desc": "This is the address to respond to A requests with when 
the max Bps or Max Tps for this delivery service are exceeded."
+            "desc": "(For DNS routed delivery services only) IPv4 address to 
overflow requests when the the max Bps or Max Tps for this delivery service are 
exceeded."
           },
           "dnsBypassIp6": {
             "title": "DNS Bypass IPv6",
-            "desc": "This is the address to respond to AAAA requests with when 
the max Bps or Max Tps for this delivery service are exceeded."
+            "desc": "(For DNS routed delivery services only) IPv6 address to 
overflow requests when the the max Bps or Max Tps for this delivery service are 
exceeded."
           },
           "dnsBypassTtl": {
             "title": "DNS Bypass TTL",
-            "desc": "Description required"
+            "desc": "TTL for the DNS bypass domain or IP when threshold 
exceeded."
           },
           "dscp": {
-            "title": "DSCP",
-            "desc": "The DSCP value to mark IP packets to the client with."
+            "title": "DSCP Tag",
+            "desc": "The Differentiated Services Code Point (DSCP) value to 
mark IP packets to the client with."
           },
           "edgeHeaderRewrite": {
             "title": "Edge Header Rewrite Rules",
-            "desc": "Header Rewrite rules to apply for this delivery service 
at the EDGE tier.<br><br>See <a 
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-header-rewrite\";
 target=\"_blank\">Header Rewrite Options and DSCP...</a>"
+            "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. Examples include:<br><br><ul><li>Action: Set</li><li>Header 
Name: X-CDN</li><li>Header Value: Foo</li><li>Direction: Edge Response to 
Client</li></ul><br><br>See <a 
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#rl-header-rewrite\";
 target=\"_blank\">Header Rewrite Options and DSCP.</a>"
           },
           "geoLimitRedirectURL": {
             "title": "Geo Limit Redirect URL",
             "desc": "This is the URL Traffic Router will redirect to when Geo 
Limit Failure.<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.<br><br><a 
href=\"http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/using.html#delivery-service\";
 target=\"_blank\">See more...</a>"
+            "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": "Description required"
+            "desc": "How (if at all) is this service to be limited by 
geography. Example: CA, IN, PR"
 
 Review comment:
   are these country codes? CA, IN, PR? if so maybe say that.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to