Re: Adding support for per-DeliveryService routing names

2017-08-04 Thread Eric Friedrich (efriedri)
> On Aug 4, 2017, at 3:09 PM, Peters, Rawlin wrote: > > Ok, it makes sense that if it can support fully customized DS domain names, > there would be > nothing stopping the user from entering a HOST_REGEXP > “foo.ds.cdn.company.com” to > essentially pick “foo” as the

Re: Adding support for per-DeliveryService routing names

2017-08-04 Thread Peters, Rawlin
Ok, it makes sense that if it can support fully customized DS domain names, there would be nothing stopping the user from entering a HOST_REGEXP “foo.ds.cdn.company.com” to essentially pick “foo” as the custom routing name. However, I think that misses the point of custom routing names. If the

Re: Adding support for per-DeliveryService routing names

2017-08-04 Thread Dave Neuman
@Eric It looks like Zhilin's proposal is for custom delivery service domains (eg instead of "tr.foo.domain.com" you can have "tr.foo.otherdomain.com") while Rawlins is for custom routing names (eg instead of "tr.foo.domain.com" you can have "bar.foo.domain.com"). I think the two features are

Re: Edge server default config

2017-08-04 Thread Gelinas, Derek
By default config do you mean the configuration after trafficserver installation or the files as generated by traffic ops? What version of traffic ops? On Aug 4, 2017, at 10:13 AM, Burak Sarp > wrote: Hi all, How can i reach

Re: Edge server default config

2017-08-04 Thread Burak Sarp
yes thats it,  thanks,Sarp On Friday, August 4, 2017 5:35 PM, Dewayne Richardson wrote: When:  Read · Fri, Aug 4. [image: Timyo expectation line] I think this is what you are talking about:

Re: Adding support for per-DeliveryService routing names

2017-08-04 Thread Peters, Rawlin
@Dave @JvD Thanks for the feedback. I think I can get on board with defaulting the DS columns to ‘edge’ and ‘tr’. I was thinking the CDN columns might be useful if the user just wants to set it CDN-wide and not individually on each DS, but I guess if we default it as part of the upgrade

Re: Adding support for per-DeliveryService routing names

2017-08-04 Thread Eric Friedrich (efriedri)
As I understand Zhilin’s changes, they are a superset of changing the routing name. Whereas today we must have “tr.ds.cdn.company.com” or “edge.”, with Zhilin’s changes you can set a completely custom DS FQDN. As he puts it in his original email, "And

Re: Adding support for per-DeliveryService routing names

2017-08-04 Thread Durfey, Ryan
Random thought on this… “edge.” Limits our ability to use wildcard ssl certs for DNS routed services for similar customer services which can save a lot of time, cost, and hassle. “tr.” Makes sense for HTTP 302 routed services because you can use wildcard certs for the server hostname that

Re: Adding support for per-DeliveryService routing names

2017-08-04 Thread Peters, Rawlin
@Dave @Eric I have my current code pushed to my fork, and it can be compared against apache/master here [1]. I did see Zhilin’s original proposal on the mailing list, and I also thought it seemed similar but not the same thing as what I’d been working on. In his example, there is a reference

Re: Adding support for per-DeliveryService routing names

2017-08-04 Thread Durfey, Ryan
Yeah, I just rethought that. I was envisioning http://servicename.customername.cdn_domain/ where we could get a cert for “*.customername.cdn_domain/” for multiple customer services. However, we currently have to use the format http://servicename-cusotmername.cdn_domain/ where a wildcard

Re: Edge server default config

2017-08-04 Thread Burak Sarp
Hi, I am using latest version of ops,Actually i need the default config files for trafficserver while installation, where they come from? ThanksSarp Sent from Yahoo Mail for iPhone On Friday, August 4, 2017, 5:14 PM, Gelinas, Derek wrote: By default config do you