Re: [openstack-dev] [neutron][chaining][policy] Port-oriented Network service chaining

2014-04-15 Thread Carlos Gonçalves
Hi Kanzhe, First off, thank you for showing interest in discussing this proposal! I’m not fully sure if I understood your point. Could you elaborate a bit more on the L1, L2, L3 part? Regarding the traffic steering API, as I see it the Neutron port is the virtual counterpart of the network

Re: [openstack-dev] [neutron][chaining][policy] Port-oriented Network service chaining

2014-04-15 Thread balaj...@freescale.com
in participating and contributing this BP and Framework. Regards, Balaji.P From: Carlos Gonçalves [mailto:m...@cgoncalves.pt] Sent: Wednesday, April 16, 2014 12:38 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][chaining][policy] Port-oriented Network

Re: [openstack-dev] [neutron][chaining][policy] Port-oriented Network service chaining

2014-04-14 Thread Kanzhe Jiang
Hi Carlos, This is Kanzhe. We discussed your port-based SFC on the Neutron advanced service IRC. I would like to reach out to you to discuss a bit more. As you know, Neutron port is a logic abstraction for network interfaces with a MAC and IP address. However, network services could be used at

[openstack-dev] [neutron][chaining][policy] Port-oriented Network service chaining

2014-03-25 Thread Carlos Gonçalves
Hi, Most of the advanced services and group policy sub-team members who attended last week’s meeting should remember I promised to start a drafting proposal regarding network service chaining. This week I got to start writing a document which is accessible here: