Open Stack

You're welcome...   :-)

In fact, this is precisely what I'm trying to achieve here at my cloud, I
mean, "vlan + vxlan" (or gre) simultaneously...

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 "192.168.20.0/20"
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...


Here is how I'm creating my "VLAN Provider Networks":

---
neutron net-create --tenant-id XXXXXX --provider:physical_network=physnet1
--provider:network_type=vlan --provider:segmentation_id=500 physnet1-vlan500

neutron net-create --tenant-id YYYYYY --provider:physical_network=physnet1
--provider:network_type=vlan --provider:segmentation_id=501 physnet1-vlan501

neutron net-create --tenant-id WWWW --provider:physical_network=physnet1
--provider:network_type=vlan --provider:segmentation_id=502 physnet1-vlan502
---


NOTE: Your upstream router also needs to have those VLANs configured on it,
since it will be the Instance's gateway.


At my switch, the ports connected at "br-eth1" interface (of Network and
Compute Nodes) have those tags (500-1000).

BTW, I'm using static IPv6 within my VLANs!   ;-)

Now, I'm trying to enable VXLAN side-by-side with VLAN, just for fun... Let
me know if you have success!


Info:
http://developer.rackspace.com/blog/neutron-networking-vlan-provider-networks.html


Best!
Thiago


On 10 June 2014 16:30, Randy <amps at djlab.com> wrote:

>  Thanks for the reply,
>
> 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)?
>
> 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.
>
> I'm still not sure how to expose a trunk port to a guest to use VLAN
> networking on the network guest...
>
> ~Randy
>
> On 06/10/2014 1:32 pm, Martinx - ジェームズ wrote:
>
> Hello Randy,
>
> 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...
>
> Flat Networks, AFAIK, requires a "dedicated bridge map", using different
> physical ethernet from the one used by your GRE/VXLAN tunnels...
>
> Here is a working howto about Flat Networks with Metadata:
> https://gist.github.com/tmartinx/9177697 - Easy to convert it to VLAN
> Provider Networks...
>
> Cheers!
>
>
> On 10 June 2014 09:17, Randy <amps at djlab.com> wrote:
>
>> I've got the 3-node Icehouse/Juno setup using Neutron (ml2/GRE)
>> networking on Xenserver, like this:
>>
>> http://docs.openstack.org/trunk/install-guide/install/
>> apt/content/basics-networking-neutron.html
>>
>> 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:
>>
>> http://docs.openstack.org/havana/install-guide/install/
>> apt/content/section_use-cases-mixed.html
>>
>> Using the flat network, DHCP works but there's no metadata or
>> connectivity in or out of the VMs.
>>
>> 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?
>>
>> --
>> ~Randy
>>
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
>> openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
>> openstack
>>
>
>
> --
> ~Randy
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140610/7d39a68f/attachment.html>