[jira] [Commented] (TC-262) Merge https://github.com/apache/incubator-trafficcontrol/pull/497 into next release
[ https://issues.apache.org/jira/browse/TC-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049370#comment-16049370 ] John Schmerge commented on TC-262: -- I would love someone to apply the pull request > Merge https://github.com/apache/incubator-trafficcontrol/pull/497 into next > release > --- > > Key: TC-262 > URL: https://issues.apache.org/jira/browse/TC-262 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops >Reporter: John Schmerge >Priority: Minor > > 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. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TC-262) Merge https://github.com/apache/incubator-trafficcontrol/pull/497 into next release
[ https://issues.apache.org/jira/browse/TC-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014996#comment-16014996 ] John Schmerge commented on TC-262: -- The single parameter is a comma-separated set of values that correspond 1:1 to the drive letter comma-separated list. If you were to have, for example drive_prefix=/dev/sd drive_letters=a,b,c,d,e drive_hash_id=,,disk3,,disk5 That would result in a storage.config file with the following content: /dev/sda volume=1 /dev/sdb volume=1 /dev/sdc volume=1 id=disk3 /dev/sdd volume=1 /dev/sde volume=1 id=disk5 > Merge https://github.com/apache/incubator-trafficcontrol/pull/497 into next > release > --- > > Key: TC-262 > URL: https://issues.apache.org/jira/browse/TC-262 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops >Reporter: John Schmerge >Priority: Minor > > 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (TC-262) Merge https://github.com/apache/incubator-trafficcontrol/pull/497 into next release
[ https://issues.apache.org/jira/browse/TC-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Schmerge updated TC-262: - Description: 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. > Merge https://github.com/apache/incubator-trafficcontrol/pull/497 into next > release > --- > > Key: TC-262 > URL: https://issues.apache.org/jira/browse/TC-262 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops >Reporter: John Schmerge >Priority: Minor > > 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-262) Merge https://github.com/apache/incubator-trafficcontrol/pull/497 into next release
John Schmerge created TC-262: Summary: Merge https://github.com/apache/incubator-trafficcontrol/pull/497 into next release Key: TC-262 URL: https://issues.apache.org/jira/browse/TC-262 Project: Traffic Control Issue Type: Improvement Components: Traffic Ops Reporter: John Schmerge Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
