<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">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 class="h5">
> server.<br>
<br>
</div></div>Right, but that assumes router control.<br></blockquote><div><br></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><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
> 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>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><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>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>