Re: Delivery Service Origin Refactor

Location and Origin columns were listed out in my more detailed initial proposal [1]. In there I proposed having either a DeliveryService FK in the Origin table or a new deliveryservice_origin table to support many-to-many. But I think keeping the DS FK in the Origin table is the right thing to

Re: Delivery Service Origin Refactor

> On Mar 22, 2018, at 12:27 PM, Rawlin Peters wrote: > > This Origin Refactor proposal was probably too much to parse at once. > Here's a slightly shorter version: > 1. Split Locations out of the Cachegroup table into their own table EF> Location is latitude/longitude?

Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2

Ah, thanks for the clarification. Ok, the 2.0.0 RPMs have been removed from dist, and the webpage links updated to archive.apache.org. On Mon, Mar 19, 2018 at 5:48 PM, sebb wrote: > On 19 March 2018 at 19:01, Robert Butts wrote: > > MD5s have been

Re: Delivery Service Origin Refactor

This Origin Refactor proposal was probably too much to parse at once. Here's a slightly shorter version: 1. Split Locations out of the Cachegroup table into their own table 2. Split Origins out of the Server and Delivery Service tables into their own table (Origin would have a FK to