weizhouapache commented on pull request #5786: URL: https://github.com/apache/cloudstack/pull/5786#issuecomment-1067150071
> @weizhouapache yes, IPv6 is not pre-allocated in VPC. Even now it is assigned only when the first IPv6 tier is created. But **IPv4** gets allocated to a VPC as soon as it is created. In most cases this allocated IPv4 can be from a vlan range which does not have a corresponding IPv6 range. @shwstppr OK, so for now (1) if internet protocol of vpc offering is dualstack, allocate an Ipv4 and ipv6 address when create first vpc tier (2) if internal protocol of vpc offering is ipv4, allocate an ipv4 address when create first vpc tier. My idea is, in case 2, when create a vpc tier (second tier) with ipv6, try to allocate an ipv6 address from same vlan as ipv4. if ok then all are good, if not then throw an exception like "unable to fetch public ipv6 address for this vpc, please contact admin to add an ipv6 range". it is much easier and more flexible . updating vpc to another offering is an option. but the public Ipv4 address will be changed to another vlan range with both ipv4 and ipv6, which might cause some issues and is complicated. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
