<html><body><div style="font-family: verdana,helvetica,sans-serif; font-size: 12pt; color: #000000"><div><span name="x"></span><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Martinx - ジェームズ" <thiagocmartinsc@gmail.com><br><b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br><b>Cc: </b>"OpenStack General Mailing List" <openstack@lists.openstack.org><br><b>Sent: </b>Thursday, January 16, 2014 5:41:09 PM<br><b>Subject: </b>Re: [openstack-dev] [Openstack] [Neutron] auto configration of local_ip<br><div><br></div><div dir="ltr">Guys,<div><br></div><div>Let me ask something about this...</div><div><br></div><div>Apparently, VXLAN can be easier to implement/maintain when using it with IPv6 (read about it here: <a href="http://www.nephos6.com/pdf/OpenStack-on-IPv6.pdf" target="_blank">www.nephos6.com/pdf/OpenStack-on-IPv6.pdf</a>), so, I'm wondering if local_ip can be an IPv6 address (for IceHouse-3 / Ubuntu 14.04) and, of course, if it is better in the end of the day.</div>
<div><br></div><div>Thoughts?!</div><div><br></div><div>Cheers!</div><div>Thiago</div></div><div class="gmail_extra"><br></div><div class="gmail_extra">AFAIK the VXLAN draft addresses only IPv4, but IPv6 should be there in the future.<br></div><div class="gmail_extra"><br><div><br></div><div class="gmail_quote">On 16 January 2014 12:58, <a href="mailto:Balaji.P@freescale.com" target="_blank">Balaji.P@freescale.com</a> <span dir="ltr"><<a href="mailto:Balaji.P@freescale.com" target="_blank">Balaji.P@freescale.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">> 2014/1/16 NOTSU Arata <<a href="mailto:notsu@virtualtech.jp" target="_blank">notsu@virtualtech.jp</a>>:<br>
> > The question is, what criteria is appropriate for the purpose. The<br>
> criteria being mentioned so far in the review are:<br>
> ><br>
> > 1. assigned to the interface attached to default gateway 2. being in<br>
> > the specified network (CIDR) 3. assigned to the specified interface<br>
> > (1 can be considered a special case of 3)<br>
> ><br>
><br>
> For a certain deployment scenario, local_ip is totally different among<br>
> those nodes, but if we consider local_ip as local_interface, it may<br>
> match most of the nodes. I think it is more convenient to switch from<br>
> ip to interface parameter.<br>
><br>
</div>[P Balaji-B37839] We implemented this and using in our test setup. We are glad to share this through blue-print/Bug if anybody is interested.<br>
<br>
Regards,<br>
Balaji.P<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
</div></div></blockquote></div><br></div>
<br>_______________________________________________<br>OpenStack-dev mailing list<br>OpenStack-dev@lists.openstack.org<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></div><div><br></div></div></body></html>