<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">Hi James!</div><div class="gmail_quote"><br></div><div class="gmail_quote">On 20 April 2015 at 18:16, James Denton <span dir="ltr"><<a href="mailto:james.denton@rackspace.com" target="_blank">james.denton@rackspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">Hi Thiago,<div><br></div><div>VXLAN requires an IP address on each host from which to build the overlay mesh between hosts. Some choose to use a dedicated interface/IP/VLAN for this, but its not required. </div></div></blockquote><div><br></div><div>Sure, I'm aware of that.</div><div><br></div><div>What is new for me, is that when using "VXLAN + OpenvSwitch", plains VLANs are not required but, when using "VXLAN + LinuxBridges", then, you'll need plain VLANs as well (and this is new for me).</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>As for ‘vconfig’ missing - It appears that the 'ip link’ command (iproute2) is being used instead to create vlan interfaces. </div></div></blockquote><div><br></div><div>Okay, cool! I'll take a look on that.</div><div><br></div><div>Thank you!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div><span class=""><font color="#888888"><br><div>
<div><div>James</div></div></div></font></span></div></div></blockquote><div><br></div><div>Thiago</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div><span class=""><font color="#888888"><div>
</div>
<br></font></span><div><blockquote type="cite"><div><div class="h5"><div>On Apr 17, 2015, at 10:26 PM, Martinx - ジェームズ <<a href="mailto:thiagocmartinsc@gmail.com" target="_blank">thiagocmartinsc@gmail.com</a>> wrote:</div><br></div></div><div><div><div class="h5"><div dir="ltr">Perfect! I followed the Juno documentation here:<div><br></div><div><a href="http://docs.openstack.org/juno/install-guide/install/apt/content/ch_preface.html" target="_blank">http://docs.openstack.org/juno/install-guide/install/apt/content/ch_preface.html</a><br></div><div><br></div><div>But I have "VXLAN + LinuxBridges", instead of "GRE + OVS", pretty cool!</div><div><br></div><div>I was doing it wrong (of course), I did not realized that VXLAN with LinuxBridges, required plain VLANs to work (Is that right?)...</div><div><br></div><div>Nevertheless, I still do not fully understand this setup, since the "vlan" package and its "vconfig" binary, is not even installed at my Network Node, also, there is nothing at my "/proc/net/vlan...".</div><div><br></div><div>So, how it is working? lol</div><div><br></div><div>Good challenge for the weekend to figure this out! ^_^</div><div><br></div><div>Cheers!</div><div>Thiago</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 17 April 2015 at 23:30, Martinx - ジェームズ <span dir="ltr"><<a href="mailto:thiagocmartinsc@gmail.com" target="_blank">thiagocmartinsc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">BTW, I just found this:<div><br></div><div><a href="https://github.com/madorn/vagrant-juno-linuxbridge-vxlan-vlan" target="_blank">https://github.com/madorn/vagrant-juno-linuxbridge-vxlan-vlan</a></div><div><br></div><div>The problem is that it is for VirtualBox or VMWare, and I'm using exclusively KVM these days... :-/</div><div><br></div><div>But, I believe it will help me anyway... =P</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On 17 April 2015 at 22:01, Martinx - ジェームズ <span dir="ltr"><<a href="mailto:thiagocmartinsc@gmail.com" target="_blank">thiagocmartinsc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hey guys,<div><br></div><div> Where can I find a complete documentation to make use of LinuxBridges, instead of OpenvSwitch, when using it with VXLAN?</div><div><br></div><div> I faced too many problems with OVS in the past (also these days) and now, even Rackspace deploys their RPC v9 and v10 with LinuxBridges but, where are the documents?</div><div><br></div><div> I'm reading now, the following Ansible files, to try to figure this out:</div><div><br></div><div> <a href="https://github.com/stackforge/os-ansible-deployment" target="_blank">https://github.com/stackforge/os-ansible-deployment</a><br></div><div><br></div><div> But, this isn't a documentation... :-P</div><div><br></div><div> The current Juno documents only explain GRE + OVS but, this setup is unstable and slow.</div><div><br></div><div>Cheers!</div><div>Thiago</div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div><span class="">
_______________________________________________<br>Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br></span></div></blockquote></div><br></div></div></blockquote></div><br></div></div>