little bit.
George
-Original Message-
From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
Sent: Friday, September 19, 2014 3:13 AM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] Question about VXLAN support
Thanks for this clarification.
Just wondering: Do multiple network
on
> subnets, but you would hit other limits by then.
>
>
>
> George
>
>
>
>
> __
> From: BYEONG-GI KIM [mailto:kimbyeon...@gmail.com]
> Sent: Wednesday, September 17, 2014 10:41 PM
> To: George Mihaiescu; openstack@lists.openstack.org
> Subje
: [Openstack] Question about VXLAN support
Dear George
Thank you for the reply.
I'm a little confused about your reply.
Can be the same tag number assigned to different tenant? For example, I assume
the situation where a subnet 1 assigned tag number 1 and it belongs to tenant
A,
I haven’t done this on a VXLAN deployment but I did a packet capture on a
Grizzly GRE environment to see exactly what it looks like on the wire and the
results are below (although the color coding will probably be lost.) What we
have with GRE is 802.1q inside the encapsulated payload so if the 4
Dear George
Thank you for the reply.
I'm a little confused about your reply.
Can be the same tag number assigned to different tenant? For example, I
assume the situation where a subnet 1 assigned tag number 1 and it belongs
to tenant A, and a subnet b is also assigned tag number 1 and it belongs
The internal VLAD ID is indeed limited to 4096 but this internal tag number is
used to isolate different neutron subnets, not tenants.
A tenant could create 10 neutron networks each with its own subnet and then
start 10 instances each attached to a separate net/subnet. If these instances
would
