<div dir="ltr">You're welcome... :-)<div><br></div><div>In fact, this is precisely what I'm trying to achieve here at my cloud, I mean, "vlan + vxlan" (or gre) simultaneously...</div><div><br></div><div>
Apparently, for Flat (or VLAN Provider Network), we need a dedicated interface for its bridge_mappings, like "physnet1:br-eth1" (if with VLAN, just tag it at the switch port where your br-eth1 is plugged in, nothing more) and, for VXLAN / GRE, we need a second dedicated interface, for the tunnels, like "local_ip = 192.168.20.30", where this "<a href="http://192.168.20.0/20">192.168.20.0/20</a>" subnet of vxlan/gre is configured using eth2 (eth1 is for Flat / VLAN). And the eth0 might me used for regular Internet access and/or Management / Glance Image downloads / etc...</div>
<div><br></div><div><br></div><div>Here is how I'm creating my "VLAN Provider Networks":</div><div><br></div><div>---</div><div>neutron net-create --tenant-id XXXXXX --provider:physical_network=physnet1 --provider:network_type=vlan --provider:segmentation_id=500 physnet1-vlan500<br>
</div><div><br></div><div>neutron net-create --tenant-id YYYYYY --provider:physical_network=physnet1 --provider:network_type=vlan --provider:segmentation_id=501 physnet1-vlan501<br></div><div><br></div><div>neutron net-create --tenant-id WWWW --provider:physical_network=physnet1 --provider:network_type=vlan --provider:segmentation_id=502 physnet1-vlan502<br>
</div><div>---</div><div><br></div><div><br></div><div>NOTE: Your upstream router also needs to have those VLANs configured on it, since it will be the Instance's gateway.</div><div><br></div><div><br></div><div>At my switch, the ports connected at "br-eth1" interface (of Network and Compute Nodes) have those tags (500-1000).</div>
<div><br></div><div>BTW, I'm using static IPv6 within my VLANs! ;-)</div><div><br></div><div>Now, I'm trying to enable VXLAN side-by-side with VLAN, just for fun... Let me know if you have success!</div><div><br>
</div><div><br></div><div>Info: <a href="http://developer.rackspace.com/blog/neutron-networking-vlan-provider-networks.html">http://developer.rackspace.com/blog/neutron-networking-vlan-provider-networks.html</a></div><div>
<br></div><div><br></div><div>Best!</div><div>Thiago</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 10 June 2014 16:30, Randy <span dir="ltr"><<a href="mailto:amps@djlab.com" target="_blank">amps@djlab.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div style="font-family:Verdana,Geneva,sans-serif">
<p>Thanks for the reply, </p>
<p>So, it *should* be possible to pull in public network(s) over flat/vlan to the VMs WITHOUT NAT, while still using GRE for private networking (two NIC per VM... one public with no NAT, the other private via GRE)?</p>
<p>I guess I'm trying to see if this is even possible - I think it should be, but XenServer is making this more complicated and there are no decent ML2-based XenServer examples out there.</p>
<p>I'm still not sure how to expose a trunk port to a guest to use VLAN networking on the network guest...</p>
<p>~Randy</p><div><div class="h5">
<p>On 06/10/2014 1:32 pm, Martinx - ジェームズ wrote:</p>
<blockquote type="cite" style="padding-left:5px;border-left:#1010ff 2px solid;margin-left:5px">
<div dir="ltr">Hello Randy,
<div> </div>
<div>Just for the record, I'm using Flat Networks (very similar with VLAN Provider Networks), with a working Metadata connectivity... Instances get a route to the Metadata network through DHCP, in my case...</div>
<div> </div>
<div>Flat Networks, AFAIK, requires a "dedicated bridge map", using different physical ethernet from the one used by your GRE/VXLAN tunnels...</div>
<div> </div>
<div>Here is a working howto about Flat Networks with Metadata: <a href="https://gist.github.com/tmartinx/9177697" target="_blank">https://gist.github.com/tmartinx/9177697</a> - Easy to convert it to VLAN Provider Networks...</div>
<div> </div>
<div>Cheers!</div>
</div>
<div class="gmail_extra"><br><br>
<div class="gmail_quote">On 10 June 2014 09:17, Randy <span><<a href="mailto:amps@djlab.com" target="_blank">amps@djlab.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've got the 3-node Icehouse/Juno setup using Neutron (ml2/GRE) networking on Xenserver, like this:<br><br><a href="http://docs.openstack.org/trunk/install-guide/install/apt/content/basics-networking-neutron.html" target="_blank">http://docs.openstack.org/<span style="text-decoration:underline"></span>trunk/install-guide/install/<span style="text-decoration:underline"></span>apt/content/basics-networking-<span style="text-decoration:underline"></span>neutron.html</a><br>
<br> Everything works fine with the floating IPs and all...but now I want to introduce a flat network (with external router) that doesn't require NAT or floating IPs. Like this:<br><br><a href="http://docs.openstack.org/havana/install-guide/install/apt/content/section_use-cases-mixed.html" target="_blank">http://docs.openstack.org/<span style="text-decoration:underline"></span>havana/install-guide/install/<span style="text-decoration:underline"></span>apt/content/section_use-cases-<span style="text-decoration:underline"></span>mixed.html</a><br>
<br> Using the flat network, DHCP works but there's no metadata or connectivity in or out of the VMs.<br><br> ACTUAL QUESTION: If we introduce the flat network to the network node on a dedicated interface, will it tunnel the flat network over GRE to each compute node? Or do we need to physically connect and bridge map each flat network on every compute node separately?<span><span style="color:#888888"><br>
<br> -- <br> ~Randy<br><br> ______________________________<span style="text-decoration:underline"></span>_________________<br> Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<span style="text-decoration:underline"></span>cgi-bin/mailman/listinfo/<span style="text-decoration:underline"></span>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/<span style="text-decoration:underline"></span>cgi-bin/mailman/listinfo/<span style="text-decoration:underline"></span>openstack</a><br>
</span></span></blockquote>
</div>
</div>
</blockquote>
<p> </p>
</div></div><span class="HOEnZb"><font color="#888888"><div>
<pre>-- <br>~Randy</pre>
</div>
</font></span></div>
</blockquote></div><br></div>