Delegating and routing an IPv6 prefix to an instance

Ruslanas Gžibovskis ruslanas at lpic.lt
Fri Jun 26 21:37:56 UTC 2020


also, if it is private cloud, maybe just dedicate a vlan as provider net,
and disable port security on that port and no need to reserve ip addresses
:)

On Sat, 27 Jun 2020, 00:20 Ruslanas Gžibovskis, <ruslanas at lpic.lt> wrote:

> well can be /120 :) not all /64
>
> On Fri, 26 Jun 2020, 23:29 Jeremy Stanley, <fungi at yuggoth.org> wrote:
>
>> On 2020-06-26 23:14:11 +0300 (+0300), Ruslanas Gžibovskis wrote:
>> [...]
>> > Create port and later assign some ip addresses to it then again some,
>> then
>> > again... 5 in a go to ne safe, then sleep 60 sec and again openstack
>> port
>> > set fixed-ip or smth like that... set it in a cycle :)
>> [...]
>>
>> Not to break out the math, but I'm gonna hafta break out the math.
>> At that rate, you could assign a full ipv6 /64 network in
>> rough 117 *billion* (okay, US billion not UK billion, but still)
>> years. Not exactly after the estimated heat death of the Universe,
>> but let's just say you're going to need to move your servers out of
>> this solar system pretty early in the process.
>> --
>> Jeremy Stanley
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200627/e430cd31/attachment.html>


More information about the openstack-discuss mailing list