+1
Lab Testing:
- Docker build - Could not figure out how to get all components to build at once
- build/build.sh on CentOS 6 - all components built successfully
- Upgraded Traffic Monitor (2.2.0.d7e588 -> 2.2.0.6ea850)
- Could pull up UI and it connects to all cache servers
- Upgraded Traffic
Hank, fyi -- from the top level of trafficcontrol, `./pkg -v` will build
all components.
-dan
On Thu, Mar 8, 2018 at 6:34 AM, Hank Beatty wrote:
> +1
>
> Lab Testing:
>
> - Docker build - Could not figure out how to get all components to build
> at once
> - build/build.sh on CentOS 6 - all comp
There has been some discussion for quite some time regarding an overhaul of
the TO access control model. I'd like to refresh eveyone's memory on that
discussion.
*Current system:*
Since the beginning, resources (or routes (UI and API)) have been locked
down by role, or more specifically, privile
So I've done some more thinking about client-steering geo-ordering,
and I think the geo-sorting part should be summarized as follows:
Sort the geo-steering targets ascending by the total distance from
[client -> edge -> origin]. For targets where the total distance is
equal, prefer the target with