cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sheng Yang <>
Subject Re: [RFC][ACS41] "ipv6" branch
Date Tue, 29 Jan 2013 22:17:37 GMT
Is every networkguru should own it's IP database? In that case, I'd
like to call it "direct_ipv6_address"...

I haven't done anything especially for AAAA, just add the name to
hosts file like we did before. Is there anything else we need to do?


On Tue, Jan 29, 2013 at 12:40 PM, Chiradeep Vittal
<> wrote:
> Although the ipv4 namespace is polluted with the "Public" prefix, I prefer
> that we do not carry over this convention to ipv6. The network can be a
> "private" or "public" network. I would just drop the "public" notation.
> Are you updating the AAAA records as well in dnsmasq?
> On 1/29/13 11:43 AM, "Sheng Yang" <> wrote:
>>I am still working on the branch, but I want to get people's notice
>>now, for your comments, in order to get it merge back to MASTER in
>>The FS is at:
>>Current code targeted at phase 1: advance shared network only.
>>Basically, I've set up a new table, "public_ipv6_address", which is
>>used to track IPv6 allocation. I didn't reuse the old
>>"user_ip_address" because it's impossible to allocate all the
>>unassigned IPv6 address in the table, like we did for IPv4 public ips.
>>"public_ipv6_address" table would keep track to the all public IPv6 ip
>>we've already allocated.
>>I also update nics, vlan, and networks table to accommodate IPv6
>>Mostly the code didn't touch the current ipv4 path.
>>I've tested basic IP assignment on XenSever. We have some troubles on
>>KVM side, but seems there are bugs come from master branch.
>>And it's API only version for now. And you would need a updated
>>version of dnsmasq to get it work. I've built the template for who
>>want to try it. But I am not sure where to upload.

View raw message