Hi, IPv6 would be a dramatic improvement for Cloudstack networking, and I would like to spend some dev cycles on it in the upcoming weeks. However, "IPv6" is a fairly wide topic. So I would like to gather some feedback from the community in order to understand what is a priority, what is a "desirable plus", and what is instead a "meh".
When I look at IPv6 in Cloudstack, I tend to look at it along two directions: nature of traffic and network protocols. For traffic types, do we want to support guest traffic only, or support IPv6 on storage and public traffic too? We might think of supporting it for management traffic as well, but I think we might end up with limited supported for IPv6 as some of the hypervisors cloudstack supports don't allow management on IPv6 addresses yet. As concerns Network protocols, I guess we want to make sure at least that the services which are running on the VR, mainly DHCP and DNS, keep working on IPv6 as well. Do you reckon this is a priority as well? Cloudstack however, allows some network services to be provided by external network elements. In your opinion, would support for IPv6 addressing of such network elements be part of the first implementation of IPv6 support? Moreover, what is your opinion about IPv6-specific features such as stateless autoconfiguration, or intserv/diffserv (QoS)? Regards, Salvatore
