<div dir="ltr">A bit more...<div><br></div><div><br></div><div>I have OpenStack IceHouse with Trusty up and running, <b><i>almost</i></b> in an IPv6-Only environment, <u>there is only one place</u> that I'm still using IPv4, which is:</div>
<div><br></div><div><br></div><div>1- For Metadata Network.</div><div><br></div><div><br></div><div>This means that, soon as OpenStack enables Metadata over IPv6, I'll kiss goodbye IPv4. For real, I can not handle IPv4 networks anymore... So many NAT tables and overlay networks, that it creeps me out!! lol</div>
<div><br></div><div><br></div><div>NOTE: I'm using "VLAN Provider Networks" with static (no support for SLAAC upstream routers in OpenStack yet) IPv6 address for my tenants, so, I'm not using GRE/VXLAN tunnels, and that is another place of OpenStack that still depends on IPv4, for its tunnels...</div>
<div><br></div><div><br></div><div>As I said, everything else is running over IPv6, like RabbitMQ, MySQL, Keystone, Nova, Glance, Cinder, Neutron (API endpoint), SPICE Consoles and Servers, the entire Management Network (private IPv6 address space - fd::/64) and etc... So, why do we need IPv4? I don't remember... :-P</div>
<div><br></div><div>Well, Amazon doesn't support IPv6... Who will be left behind with smelly IPv4 and ugly "VPCs topologies"?! Not us. ;-)</div><div><br></div><div>Best!</div><div>Thiago</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On 7 July 2014 15:50, Ian Wells <span dir="ltr"><<a href="mailto:ijw.ubuntu@cack.org.uk" target="_blank">ijw.ubuntu@cack.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="">On 7 July 2014 11:37, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> When it's on a router, it's simpler: use the nexthop, get that metadata<br><div><div>
> server.<br>
<br>
</div></div>Right, but that assumes router control.<br></blockquote><div><br></div></div><div>It does, but then that's the current status quo - these things go on Neutron routers (and, by extension, are generally not available via provider networks).<br>
<br></div><div class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
> In general, anyone doing singlestack v6 at the moment relies on<br>
> config-drive to make it work. This works fine but it depends what<br>
> cloud-init support your application has.<br>
<br>
</div>I think it's also important to realize that the metadata service isn't<br>
OpenStack invented, it's an AWS API. Which means I don't think we really<br>
have the liberty to go changing how it works, especially with something<br>
like IPv6 support.<br></blockquote><div><br></div></div><div>Well, as Amazon doesn't support ipv6 we are the trailblazers here and we can do what we please. If you have a singlestack v6 instance there's no compatibility to be maintained with Amazon, because it simply won't work on Amazon. (Also, the format of the metadata server maintains compatibility with AWS but I don't think it's strictly AWS any more; the config drive certainly isn't.)<br>
<br></div><div class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm not sure I understand why requiring config-drive isn't ok. In our<br>
upstream testing it's a ton more reliable than the metadata service due<br>
to all the crazy networking things it's doing.<br>
<br>
I'd honestly love to see us just deprecate the metadata server.</blockquote><div><br></div></div><div>The metadata server could potentially have more uses in the future - it's possible to get messages out of it, rather than just one time config - but yes, the config drive is so much more sensible. For the server, and once you're into Neutron, then you end up with many problems - which interface to use, how to get your network config when important details are probably on the metadata server itself...<br>
</div></div></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>