On 3/6/20 5:18 PM, Arzhel Younsi wrote:
Hi!
CCing Faidon if it's urgent as I'll be out next week.
A /64 for the transport network and a /48 per cloud environment (/site) sounds good to me. Exact prefixes TBD but it should be quick to assign. I don't know (yet) what's OpenStack best practices for v6 but I can probably do some research as well. Instinct tells me that splitting the /48 is more future-proof.
At this early point, I really don't have a strong opinion about prefix length. Whatever works for you, works for me!
You can find some notes on Openstack IPv6 here:
https://wikitech.wikimedia.org/wiki/Wikimedia_Cloud_Services_team/Enhancemen...
(includes a link to upstream docs)
At first it doesn't look like a big deal. We will probably use SLAAC internally. The big deal is to answer this question:
Would it be possible to replace/reduce the IPv4 NAT mechanism to the bare minimum by using IPv6?
That's why I would really like to start playing with this ASAP.
About OKRs, please let me know in advance so I can prioritize accordingly :)
OK. I asked for the allocation of the IPv6 range couple of times already. I honestly didn't expect that the BGP thing would be a blocker (took almost a month!). My expectation is to advance as much as I can in research and design this Q.
regards.