Hi,
thanks for your comments.
see answers below.
Thanks,
Erik
On Tue, Dec 17, 2013 at 6:17 AM, Isaku Yamahata isaku.yamah...@gmail.comwrote:
Added openstack-dev
The document is view-only. So I commented below.
- 2 Modeling proposal
What's the purpose of trunk network?
Can you
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
this with a basic bit of gateway code running on a system using
Linuxbridge + GRE, I think - the key seems to be avoiding VLANs in the
overlay and then the problem is drastically simplified.
--
Ian.
On 21 December 2013 23:00, Erik Moe emoe...@gmail.com wrote:
Hi Ian,
I think your VLAN trunking
Hi!
We are looking into how to make it possible for tenant VMs to use VLAN
tagged traffic to connect to different Neutron networks.
The VID on frames sent/received will determine which Neutron network the
frames are connected to.
https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms
I
we should present a trunk
port
and the vlan on a trunk port to Neutron.
Yi
From: Erik Moe [mailto:emoe...@gmail.com]
Sent: Monday, October 28, 2013 1:56 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Neutron] VLAN aware VMs
Hi!
We are looking
From: Erik Moe [mailto:emoe...@gmail.com]
Sent: Monday, October 28, 2013 1:56 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Neutron] VLAN aware VMs
Hi!
We are looking into how to make it possible for tenant VMs to use VLAN
tagged traffic
Hi,
API Design Document
v2https://docs.google.com/document/d/1nGUqEb4CEdabbTDyeL2ECVicnBRNrK3amJcNi-D4Ffo/edit
Includes following example:
Response:
{
qos:
[
{id: 1234-5678-1234-5678,
description: Gold level service,
type: ratelimit,
Hi,
I am also interested.
/Erik
On Fri, May 9, 2014 at 3:43 AM, Mohammad Banikazemi m...@us.ibm.com wrote:
Sounds good. Thanks.
Mohammad
On May 8, 2014, at 3:02 PM, Stephen Wong
*s3w...@midokura.com*s3w...@midokura.com
wrote:
Hi Sean,
Perfect (I assume it is local time, i.e.
Mailing List (not for usage questions)
Cc: Erik Moe; iawe...@cisco.com; calum.lou...@metaswitch.com
Subject: Re: [openstack-dev] [neutron] [nfv] VM-based VLAN trunking blueprints
- Original Message -
From: Kyle Mestery mest...@mestery.com
To: OpenStack Development Mailing List
...@ericsson.commailto:alan.kavan...@ericsson.com wrote:
+1 many thanks to Kyle for putting this as a priority, its most welcome.
/Alan
-Original Message-
From: Erik Moe [mailto:erik@ericsson.commailto:erik@ericsson.com]
Sent: October-22-14 5:01 PM
To: Steve Gordon; OpenStack Development Mailing List
I thought Monday network meeting agreed on that “VLAN aware VMs”, Trunk network
+ L2GW were different use cases.
Still I get the feeling that the proposals are put up against each other.
Here are some examples why bridging between Neutron internal networks using
trunk network and L2GW IMO
From: Ian Wells [mailto:ijw.ubu...@cack.org.uk]
Sent: den 31 oktober 2014 23:35
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] [nfv] VM-based VLAN trunking blueprints
On 31 October 2014 06:29, Erik Moe
erik@ericsson.commailto:erik
] [neutron] [nfv] VM-based VLAN trunking blueprints
Hello, will this topic be discussed in the design session?
Richard
On Mon, Nov 3, 2014 at 10:36 PM, Erik Moe
erik@ericsson.commailto:erik@ericsson.com wrote:
I created an etherpad and added use cases (so far just the ones in your email
network, what they expect neutron to do, is much like what the flat
network does(so I call it extended flat): just keep the packets as is
bidirectionally between wire and vnic.
From: Erik Moe [erik@ericsson.com]
Sent: Tuesday, November 04, 2014 5:36 AM
Hi,
I also agree, IMHO we need flow synchronization method so we can avoid network
downtime and stray flows.
Regards,
Erik
From: Germy Lure [mailto:germy.l...@gmail.com]
Sent: den 5 november 2014 10:46
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
of flows unknown to the l2 agent).
In the meanwhile, I hope you won't mind if we go ahead and start making flow
reset optional - so that we stop causing downtime upon agent restart.
Salvatore
On 5 November 2014 11:57, Erik Moe
erik@ericsson.commailto:erik@ericsson.com wrote:
Hi,
I also
November 2014 11:57, Erik Moe
erik@ericsson.commailto:erik@ericsson.com wrote:
Hi,
I also agree, IMHO we need flow synchronization method so we can avoid network
downtime and stray flows.
Regards,
Erik
From: Germy Lure [mailto:germy.l...@gmail.commailto:germy.l...@gmail.com]
Sent: den 5
One reason for trying to get an more complete API into Neutron is to have a
standardized API. So users know what to expect and for providers to have
something to comply to. Do you suggest we bring this standardization work to
some other forum, OPNFV for example? Neutron provides low level
Hi,
I have not been able to work with upstreaming of this for some time now. But
now it looks like I may make another attempt. Who else is interested in this,
as a user or to help contributing? If we get some traction we can have an IRC
meeting sometime next week.
Thanks,
Erik
From: Scott
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [neutron]Anyone looking at support for VLAN-aware
VMs in Liberty?
On 05/08/2015 09:29 AM, Erik Moe wrote:
Hi,
I have not been able to work with upstreaming of this for some time now.
But now it looks like I may make another
20 matches
Mail list logo
