Open Stack

Hi Ian,

I think your VLAN trunking capability proposal can be a good thing, so the
user can request a Neutron network that can trunk VLANs without caring
about detailed information regarding which VLANs to pass. This could be
used for use cases there user wants to pass VLANs between endpoints on a L2
network etc.

For the use case there a VM wants to connect to several "normal" Neutron
networks using VLANs, I would prefer a solution that did not require a
Neutron trunk network. Possibly by connecting a L2-gateway directly to the
Neutron 'vNic' port, or some other solution. IMHO it would be good to map
VLAN to Neutron network as soon as possible.

Thanks,
Erik



On Thu, Dec 19, 2013 at 2:15 PM, Ian Wells <ijw.ubuntu at cack.org.uk> wrote:

> On 19 December 2013 06:35, Isaku Yamahata <isaku.yamahata at gmail.com>wrote:
>
>>
>> Hi Ian.
>>
>> I can't see your proposal. Can you please make it public viewable?
>>
>
> Crap, sorry - fixed.
>
>
>> > Even before I read the document I could list three use cases.  Eric's
>> > covered some of them himself.
>>
>> I'm not against trunking.
>> I'm trying to understand what requirements need "trunk network" in
>> the figure 1 in addition to "L2 gateway" directly connected to VM via
>> "trunk port".
>>
>
> No problem, just putting the information there for you.
>
> --
> Ian.
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131221/c26debc6/attachment.html>