<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Adding a dns server adds more complexity into the mix. You need to support both a dns server and a metadata server at that point.<br>
<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF287084"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Kevin Benton [blak111@gmail.com]<br>
<b>Sent:</b> Friday, September 04, 2015 1:25 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Neutron] cloud-init IPv6 support<br>
</font><br>
</div>
<div></div>
<div>
<div dir="ltr">Thanks for pointing that out. I like the DNS option too. That has to be done carefully though to make sure it's not easy for an attacker to get the name of the DNS entry that the instance tries to look up.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Sep 4, 2015 at 10:53 AM, Henry Gessau <span dir="ltr">
<<a href="mailto:gessau@cisco.com" target="_blank">gessau@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div bgcolor="#FFFFFF">
<div>Some thought has been given to this. See<br>
<a href="https://bugs.launchpad.net/neutron/+bug/1460177" target="_blank">https://bugs.launchpad.net/neutron/+bug/1460177</a><br>
<br>
I like the third option, a well-known name using DNS.
<div>
<div class="h5"><br>
<br>
On Thu, Sep 03, 2015, Kevin Benton <a href="mailto:blak111@gmail.com" target="_blank">
<blak111@gmail.com></a> wrote:<br>
</div>
</div>
</div>
<div>
<div class="h5">
<blockquote type="cite">
<div dir="ltr">I think that's different than what is being asked here. That patch appears to just add IPv6 interface information if it's available in the metadata. This thread is about getting cloud-init to connect to an IPv6 address instead of 169.254.169.254
for pure IPv6 environments.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Sep 3, 2015 at 11:41 AM, Joshua Harlow <span dir="ltr">
<<a href="mailto:harlowja@outlook.com" target="_blank">harlowja@outlook.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
I'm pretty sure this got implemented :)<br>
<br>
<a href="http://bazaar.launchpad.net/%7Ecloud-init-dev/cloud-init/trunk/revision/1042" rel="noreferrer" target="_blank">http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/1042</a> and
<a href="https://bugs.launchpad.net/cloud-init/+bug/1391695" rel="noreferrer" target="_blank">
https://bugs.launchpad.net/cloud-init/+bug/1391695</a><br>
<br>
That's the RHEL support, since cloud-init translates a ubuntu style networking style the ubuntu/debian style format should also work.
<div>
<div><br>
<br>
Steve Gordon wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
----- Original Message -----<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
From: "Kevin Benton"<<a href="mailto:blak111@gmail.com" target="_blank">blak111@gmail.com</a>><br>
<br>
When we discussed this before on the neutron channel, I thought it was<br>
because cloud-init doesn't support IPv6. We had wasted quite a bit of time<br>
talking about adding support to our metadata service because I was under<br>
the impression that cloud-init already did support IPv6.<br>
<br>
IIRC, the argument against adding IPv6 support to cloud-init was that it<br>
might be incompatible with how AWS chooses to implement IPv6 metadata, so<br>
AWS would require a fork or other incompatible alternative to cloud-init in<br>
all of their images.<br>
<br>
Is that right?<br>
</blockquote>
<br>
That's certainly my understanding of the status quo, I was enquiring primarily to check it was still accurate.<br>
<br>
-Steve<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
On Thu, Sep 3, 2015 at 7:30 AM, Sean M. Collins<<a href="mailto:sean@coreitpro.com" target="_blank"></a><a href="mailto:sean@coreitpro.com" target="_blank">sean@coreitpro.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
It's not a case of cloud-init supporting IPv6 - The Amazon EC2 metadata<br>
API defines transport level details about the API - and currently only<br>
defines a well known IPv4 link local address to connect to. No well known<br>
link local IPv6 address has been defined.<br>
<br>
I usually recommend config-drive for IPv6 enabled clouds due to this.<br>
--<br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
</blockquote>
</blockquote>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>
<div>Kevin Benton</div>
</div>
</div>
<br>
<fieldset target="_blank"></fieldset> <br>
<pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<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>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div>Kevin Benton</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>