Github user asfgit commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/497
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/27/
---
If your
Github user asfgit commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/497
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user asfgit commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/497
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user jschmerge commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/497
I thought i had left a comment regarding this patch a few weeks back
answering the question @limited posed...
I'm going to focus on just the Drive_Letters and
Github user limited commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/497
I understand the ATS storage.config parameter, but how is this ID
configured/generated in Traffic Ops? Is there a per-disk ID parameter (i.e. if
i have 72 disks there are now
Github user limited commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/497
What values would one typically set for the *_Hash_Id? Does it need to
correspond to a property of the disks?
---
If your project is set up for it, you can reply to this email
