<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2020-06-29 19:55, Brian Haley wrote:<br>
</div>
<blockquote type="cite"
cite="mid:6eb59b06-9492-2581-b0b0-b5545361f745@gmail.com">
<blockquote type="cite" style="color: #000000;"><br>
But some sort of pool of "additional" <s>public</s>
globally unique
<br>
prefixes that can be requested, bound and routed to an instance
would be
<br>
nice - kinda like
<br>
<a class="moz-txt-link-freetext"
href="https://www.terraform.io/docs/providers/openstack/r/compute_floatingip_v2.html#example-usage"
moz-do-not-send="true">https://www.terraform.io/docs/providers/openstack/r/compute_floatingip_v2.html#example-usage</a>
<br>
.
<br>
</blockquote>
<br>
We made a conscious decision to not support floating IPv6 in the
base reference implementation, although it is available in one of
the third-party drivers (Midonet?). Making the tenant IPv6
subnets reachable directly was instead the goal, which happens
when PD is used.
<br>
</blockquote>
<p>I suppose you are talking about this fip64 feature -
<a class="moz-txt-link-freetext" href="https://docs.midonet.org/docs/latest-en/operations-guide/content/fip64.html">https://docs.midonet.org/docs/latest-en/operations-guide/content/fip64.html</a>
//
<a class="moz-txt-link-freetext" href="https://docs.openstack.org/networking-midonet/latest/user/features.html">https://docs.openstack.org/networking-midonet/latest/user/features.html</a>
?<br>
</p>
<p>Just in case there might be a misunderstanding in what I
described ... "floating ip" for IPv4 would translate to "floating
prefix" (out of a pool, with a limit on the number of those a
tenant might use/request) in my suggested case and the routing
sending the traffic of that prefix to an interface.<br>
Certainly no single ipv6 addresses / 128 shall be "floating"
around or be mapped to a fixed IPv4 to make things even more
complicated.</p>
<p>It's just a about being able to provide an instance with a global
prefix of its own to do networky things.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:6eb59b06-9492-2581-b0b0-b5545361f745@gmail.com">
<br>
<blockquote type="cite" style="color: #000000;">What would be the
process of getting such a feature into a working
<br>
specification in case one was interested in implementing this?
<br>
</blockquote>
<br>
It's outlined in the neutron docs, but basically it starts with a
bug describing the feature you'd like to add, it's then discussed
at a weekly meeting each Friday.
<br>
<br>
<a class="moz-txt-link-freetext"
href="https://docs.openstack.org/neutron/ussuri/contributor/policies/blueprints.html"
moz-do-not-send="true">https://docs.openstack.org/neutron/ussuri/contributor/policies/blueprints.html</a>
<br>
<br>
-Brian
</blockquote>
<p><br>
</p>
<p>Thanks for that immediate pointer.<br>
I shall be discussing this with some folks here and might get back
to writing one of those blueprints.</p>
<p><br>
</p>
<p><br>
</p>
<p>Regards</p>
<p><br>
</p>
<p>Christian<br>
</p>
<br>
</body>
</html>