Implement a standard for public IPv6 north-south connectivity

[fzakfeld]

As a IaaS user, I want my workload to have IPv6 connectivity to and from the internet, so that I can offer dual-stack connectivity to the end users.

Definition of Ready:

• User Story is small enough to be finished within one sprint
• User Story is clear and understood by the whole team
• Acceptance criteria are defined
• Acceptance criteria are clear and understood by the whole team

Definition of Done:

• All acceptance criteria are met
• Changes have been reviewed
• CI tests have run successfully
• Documentation has been updated
• Release Notes have been updated

[fzakfeld]

My suggestion for this standard would be as follows:

• A subnet pool capable of issuing IPv6 GUA (public) prefixes of the size /64 must be present
• Subnets created from the subnet pool, connected to a router must be reachable from the internet
• Some sort of alternative to DHCP must be provided (IMO it makes sense to require DHCPv6-Stateless)

The routing can be achived with neutron-dynamic-routing (SDN agnostic, via BGP) or other solutions like ovn-bgp-agent. IPv6 space is generally free for ISPs.

Feel free to share any thoughts

[toothstone]

I would like to see a clarification, that such a standard would only apply to clouds that are connected to the internet. Otherwise air-gapped private clouds will be categorically excluded from SCS compliance, which seems like collateral damage we should avoid.

Also looking at the description at the top, I would avoid any mention of IPv4 and dual-stack, to keep the scope on the specific thing we want to ensure for SCS users, which in my understanding is IPv6 internet connectivity. No need to further cement IPv4 by accidentally requiring dual-stack.