I feel that we are getting quite far away from supporting my use case. Use
case: VM wants to connect to different 'normal' Neutron networks from one
VNIC. VLANs are proposed in blueprint since it's a common way to separate
'networks'. It is just a way to connect to different Neutron networks, it
do
I think we have two different cases here - one where a 'trunk' network
passes all VLANs, which is potentially supportable by anything that's not
based on VLANs for separation, and one where a trunk can't feasibly do that
but where we could make it pass a restricted set of VLANs by mapping.
In the
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
On 19 December 2013 06:35, Isaku Yamahata 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.
>
Ian,
Could you unlock your doc at
https://docs.google.com/document/d/16DDJLYHxMmbCPO5LxW_kp610oj4goiic_oTakJiXjTs?
It require a permission to read.
Thanks
Yi
On 12/18/13, 4:20 AM, Ian Wells wrote:
A Neutron network is analagous to a wire between ports. We can do
almost everything with this wi
Hi Ian.
I can't see your proposal. Can you please make it public viewable?
Some comments inlined below.
On Wed, Dec 18, 2013 at 01:20:50PM +0100,
Ian Wells wrote:
> A Neutron network is analagous to a wire between ports. We can do almost
> everything with this wire - we can pass both IP and
A Neutron network is analagous to a wire between ports. We can do almost
everything with this wire - we can pass both IP and non-IP traffic, I can
even pass MPLS traffic over it (yes, I tried). For no rational reason, at
least if you live north of the API, I sometimes can't pass VLAN traffic
ove
On 12/17/13, 6:36 AM, Erik Moe wrote:
Hi,
thanks for your comments.
see answers below.
Thanks,
Erik
On Tue, Dec 17, 2013 at 6:17 AM, Isaku Yamahata
mailto:isaku.yamah...@gmail.com>> wrote:
Added openstack-dev
The document is view-only. So I commented below.
- 2 Modeling p
Hi,
thanks for your comments.
see answers below.
Thanks,
Erik
On Tue, Dec 17, 2013 at 6:17 AM, Isaku Yamahata wrote:
> Added openstack-dev
>
> The document is view-only. So I commented below.
>
> - 2 Modeling proposal
> What's the purpose of trunk network?
> Can you please add a use case
On Dec 16, 2013, at 11:17 PM, Isaku Yamahata wrote:
> Added openstack-dev
>
> On Mon, Dec 16, 2013 at 11:34:05PM +0100,
> Erik Moe wrote:
>
>> Hi,
>>
>> I have added a new document to the launchpad. Document should now be more
>> in line with what we discussed at the Icehouse summit.
>>
>> ht
Added openstack-dev
On Mon, Dec 16, 2013 at 11:34:05PM +0100,
Erik Moe wrote:
> Hi,
>
> I have added a new document to the launchpad. Document should now be more
> in line with what we discussed at the Icehouse summit.
>
> https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms
>
> Doc:
11 matches
Mail list logo
