+1
Things I tested (Centos 7.2 VM):
-- verified md5
-- verified gpg sig
-- built all RPMs from source tar
-- Traffic Stats installs, starts, and runs
-- Traffic Router installs, starts, serves digs and curls
-- Traffic Ops can be installed and started.
I found a couple issues that should be addres
I think we do want it per DS (and not even per origin) since the asking
customer will potentially have two DSes pointing to the same origin where one
is for in-home traffic and one is for mobile, and they may want different QoS
for each.
Thanks,
Mike Sandman
On 6/19/17, 5:00 PM, "Steve Malenf
Mike,
Is there a requirement to have it configured per delivery service? If not,
would enabling global header rewrite in plugin.config would work for a
specific DSCP value?
Steve
On Mon, Jun 19, 2017 at 1:28 PM, Mike Sandman (misandma) wrote:
> Hi all,
>
> I’m beginning work on a feature to en
+1
I checked:
- git tag verified
- gpg sig is good
- checksums match source tarball
- tarball has correct name and structure
- rpms build from tarball
- traffic_ops installation and postinstall on a clean Centos7 VM
- some basic traffic_ops UI functionality
- docs no longer mention build area to d
Hi all,
I’m beginning work on a feature to enable DSCP marking for traffic between the
mid and edge cache. So far the high level proposed design is:
1. DSCP marking from Mid to Edge will be configurable on a per-DS basis
(like DSCP marking from Edge to Client is today). This means the Mi
