[jira] [Updated] (TS-1810) IPv6 for Cluster management
[ https://issues.apache.org/jira/browse/TS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-1810: --- Assignee: (was: Alan M. Carroll) IPv6 for Cluster management --- Key: TS-1810 URL: https://issues.apache.org/jira/browse/TS-1810 Project: Traffic Server Issue Type: Improvement Components: Clustering Reporter: Leif Hedstrom Fix For: sometime It seems the management APIs (at least) for clustering are not IPv6 aware. E.g. {code} typedef int TSNodeHandle_t; typedef void (*TSClusterRPCFunction) (TSNodeHandle_t *node, TSClusterRPCMsg_t *msg, int msg_data_len); typedef void (*TSClusterStatusFunction) (TSNodeHandle_t *node, TSNodeStatus_t s); * Get the struct in_addr associated with the TSNodeHandle_t. * tsapi int TSNodeHandleToIPAddr(TSNodeHandle_t *h, struct in_addr *in); * Get the TSNodeHandle_t for the local node. * tsapi void TSGetMyNodeHandle(TSNodeHandle_t *h); tsapi int TSSendClusterRPC(TSNodeHandle_t *nh, TSClusterRPCMsg_t *msg); {code} As far as I can tell, TSNodeHandle_t is also how we represent the IP of the cluster node. And since it's an int, it can only represent IPv4 addresses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-1810) IPv6 for Cluster management
[ https://issues.apache.org/jira/browse/TS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1810: -- Fix Version/s: (was: sometime) 5.0.0 IPv6 for Cluster management --- Key: TS-1810 URL: https://issues.apache.org/jira/browse/TS-1810 Project: Traffic Server Issue Type: Improvement Components: Clustering Reporter: Leif Hedstrom Fix For: 5.0.0 It seems the management APIs (at least) for clustering are not IPv6 aware. E.g. {code} typedef int TSNodeHandle_t; typedef void (*TSClusterRPCFunction) (TSNodeHandle_t *node, TSClusterRPCMsg_t *msg, int msg_data_len); typedef void (*TSClusterStatusFunction) (TSNodeHandle_t *node, TSNodeStatus_t s); * Get the struct in_addr associated with the TSNodeHandle_t. * tsapi int TSNodeHandleToIPAddr(TSNodeHandle_t *h, struct in_addr *in); * Get the TSNodeHandle_t for the local node. * tsapi void TSGetMyNodeHandle(TSNodeHandle_t *h); tsapi int TSSendClusterRPC(TSNodeHandle_t *nh, TSClusterRPCMsg_t *msg); {code} As far as I can tell, TSNodeHandle_t is also how we represent the IP of the cluster node. And since it's an int, it can only represent IPv4 addresses. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1810) IPv6 for Cluster management
[ https://issues.apache.org/jira/browse/TS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1810: -- Assignee: Alan M. Carroll IPv6 for Cluster management --- Key: TS-1810 URL: https://issues.apache.org/jira/browse/TS-1810 Project: Traffic Server Issue Type: Improvement Components: Clustering Reporter: Leif Hedstrom Assignee: Alan M. Carroll Fix For: 5.0.0 It seems the management APIs (at least) for clustering are not IPv6 aware. E.g. {code} typedef int TSNodeHandle_t; typedef void (*TSClusterRPCFunction) (TSNodeHandle_t *node, TSClusterRPCMsg_t *msg, int msg_data_len); typedef void (*TSClusterStatusFunction) (TSNodeHandle_t *node, TSNodeStatus_t s); * Get the struct in_addr associated with the TSNodeHandle_t. * tsapi int TSNodeHandleToIPAddr(TSNodeHandle_t *h, struct in_addr *in); * Get the TSNodeHandle_t for the local node. * tsapi void TSGetMyNodeHandle(TSNodeHandle_t *h); tsapi int TSSendClusterRPC(TSNodeHandle_t *nh, TSClusterRPCMsg_t *msg); {code} As far as I can tell, TSNodeHandle_t is also how we represent the IP of the cluster node. And since it's an int, it can only represent IPv4 addresses. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1810) IPv6 for Cluster management
[ https://issues.apache.org/jira/browse/TS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1810: -- Fix Version/s: sometime IPv6 for Cluster management --- Key: TS-1810 URL: https://issues.apache.org/jira/browse/TS-1810 Project: Traffic Server Issue Type: Improvement Components: Clustering Reporter: Leif Hedstrom Fix For: sometime It seems the management APIs (at least) for clustering are not IPv6 aware. E.g. {code} typedef int TSNodeHandle_t; typedef void (*TSClusterRPCFunction) (TSNodeHandle_t *node, TSClusterRPCMsg_t *msg, int msg_data_len); typedef void (*TSClusterStatusFunction) (TSNodeHandle_t *node, TSNodeStatus_t s); * Get the struct in_addr associated with the TSNodeHandle_t. * tsapi int TSNodeHandleToIPAddr(TSNodeHandle_t *h, struct in_addr *in); * Get the TSNodeHandle_t for the local node. * tsapi void TSGetMyNodeHandle(TSNodeHandle_t *h); tsapi int TSSendClusterRPC(TSNodeHandle_t *nh, TSClusterRPCMsg_t *msg); {code} As far as I can tell, TSNodeHandle_t is also how we represent the IP of the cluster node. And since it's an int, it can only represent IPv4 addresses. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1810) IPv6 for Cluster management
[ https://issues.apache.org/jira/browse/TS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1810: -- Fix Version/s: (was: sometime) 3.3.3 IPv6 for Cluster management --- Key: TS-1810 URL: https://issues.apache.org/jira/browse/TS-1810 Project: Traffic Server Issue Type: Improvement Components: Clustering Reporter: Leif Hedstrom Fix For: 3.3.3 It seems the management APIs (at least) for clustering are not IPv6 aware. E.g. {code} typedef int TSNodeHandle_t; typedef void (*TSClusterRPCFunction) (TSNodeHandle_t *node, TSClusterRPCMsg_t *msg, int msg_data_len); typedef void (*TSClusterStatusFunction) (TSNodeHandle_t *node, TSNodeStatus_t s); * Get the struct in_addr associated with the TSNodeHandle_t. * tsapi int TSNodeHandleToIPAddr(TSNodeHandle_t *h, struct in_addr *in); * Get the TSNodeHandle_t for the local node. * tsapi void TSGetMyNodeHandle(TSNodeHandle_t *h); tsapi int TSSendClusterRPC(TSNodeHandle_t *nh, TSClusterRPCMsg_t *msg); {code} As far as I can tell, TSNodeHandle_t is also how we represent the IP of the cluster node. And since it's an int, it can only represent IPv4 addresses. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1810) IPv6 for Cluster management
[ https://issues.apache.org/jira/browse/TS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1810: -- Fix Version/s: (was: 3.3.3) sometime IPv6 for Cluster management --- Key: TS-1810 URL: https://issues.apache.org/jira/browse/TS-1810 Project: Traffic Server Issue Type: Improvement Components: Clustering Reporter: Leif Hedstrom Fix For: sometime It seems the management APIs (at least) for clustering are not IPv6 aware. E.g. {code} typedef int TSNodeHandle_t; typedef void (*TSClusterRPCFunction) (TSNodeHandle_t *node, TSClusterRPCMsg_t *msg, int msg_data_len); typedef void (*TSClusterStatusFunction) (TSNodeHandle_t *node, TSNodeStatus_t s); * Get the struct in_addr associated with the TSNodeHandle_t. * tsapi int TSNodeHandleToIPAddr(TSNodeHandle_t *h, struct in_addr *in); * Get the TSNodeHandle_t for the local node. * tsapi void TSGetMyNodeHandle(TSNodeHandle_t *h); tsapi int TSSendClusterRPC(TSNodeHandle_t *nh, TSClusterRPCMsg_t *msg); {code} As far as I can tell, TSNodeHandle_t is also how we represent the IP of the cluster node. And since it's an int, it can only represent IPv4 addresses. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira