GitHub user jschmerge opened a pull request:

    https://github.com/apache/incubator-trafficcontrol/pull/497

    Allow specification of the 'id' parameter for storage.config

    This patch adds three new parameters to control/configure the seed
    strings for the consistent hash used for cachekey->drive mapping in
    ATS... This allows an arbitrary string to be assigned as the key for
    drives instead of relying on the OS's device node name as the seed for
    the hash. The three parameters added are:
     * Drive_Hash_Id
     * RAM_Drive_Hash_Id
     * SSD_Drive_Hash_Id
    And they specify the id keys for spinning, ram, and ssd devices.
    
    If this parameter is missing from the TO config for a server, the
    generated file ommits any specification of the id parameter (preserving
    the previous file generation behavior).
    
    Also note that the csv id strings for these three new parameters should
    order their entries to match the order of the Drive_Letters parameter.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jschmerge/incubator-trafficcontrol master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafficcontrol/pull/497.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #497
    
----
commit 56c667ccb0338ed8ab34faf0db802d735b509022
Author: John Schmerge <john_schme...@cable.comcast.com>
Date:   2017-04-14T22:35:37Z

    Allow specification of the 'id' parameter for storage.config
    
    This patch adds three new parameters to control/configure the seed
    strings for the consistent hash used for cachekey->drive mapping in
    ATS... This allows an arbitrary string to be assigned as the key for
    drives instead of relying on the OS's device node name as the seed for
    the hash. The three parameters added are:
     * Drive_Hash_Id
     * RAM_Drive_Hash_Id
     * SSD_Drive_Hash_Id
    And they specify the id keys for spinning, ram, and ssd devices.
    
    If this parameter is missing from the TO config for a server, the
    generated file ommits any specification of the id parameter (preserving
    the previous file generation behavior).
    
    Also note that the csv id strings for these three new parameters should
    order their entries to match the order of the Drive_Letters parameter.

----


---
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 have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to