cl-k-takahashi commented on issue #3764: Refer pod_ip_range_map table instead of host_pod_ref.decription. URL: https://github.com/apache/cloudstack/pull/3764#issuecomment-568754935 I think you are right, because current code is working well. First, I wanted to make cloudstack support ipv6 addresses for pod and thought that keeping ipv6 addresses in host_pod_ref like "2001::1-2001::99-0-99999,233.233.233.235-233.233.233.236-1-untagged" is not a good idea. So, I intended to split ipv4 range from `host_pod_ref` to `pod_ip_range_map` in this PR and create `pod_ip6_range_map` in future PR. However, of course, this is my own opinion. Keeping ipv6 addresses in `host_pod_ref` is an option, keeping ipv6 addresses in separate table is also an option and not supporting ipv6 pod ip range now is OK.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
