Re: [openstack-dev] [Neutron] Port Forwarding API

Interesting, I'll have a look. We should get this on the neutron drivers' agenda. The drivers team has been dormant for a couple of weeks but I'm sure it will pick up again very soon. Carl On Sep 20, 2015 12:28 AM, "Gal Sagie" wrote: > Hello All, > > I have sent a spec

[openstack-dev] [Neutron] Port Forwarding API

Hello All, I have sent a spec [1] to resume the work on port forwarding API and reference implementation. Its currently marked as "WIP", however i raised some "TBD" questions for the community. The way i see port forwarding is an API that is very similar to floating IP API and implementation

Re: [openstack-dev] [Neutron] Port Forwarding API

Hi shihanzhang, As mentioned in the spec, this doesnt support distributed FIP's, it will still work if the VMs are on different compute nodes, similar to the way centralized DNAT works (from the network node) Distributing port forwarding entries in my opinion is similar to distributing SNAT, and

Re: [openstack-dev] [Neutron] Port Forwarding API

2) The same FIP address can be used for different mappings, for example FIP with IP X can be used with different ports to map to different VM's X:4001 -> VM1 IP X:4002 -> VM2 IP (This is the essence of port forwarding). So we also need the port mapping

Re: [openstack-dev] [Neutron] Port forwarding

Hi Gal, Congratulations, eventually you understand what I mean. Yes, in bulk. But I don't think that's an enhancement to the API. The bulk operation is more common scenario. It is more useful and covers the single port-mapping scenario. By the way, bulk operation may apply to a subnet, a

Re: [openstack-dev] [Neutron] Port forwarding

Hi Germy, Port forwarding the way i see it, is a way of reusing the same floating ip to access several different Neutron ports (VM's , Containers) So for example if we have floating IP 172.20.20.10 , we can assign 172.20.20.10:4001 to VM1 and 172.20.20.10:4002 to VM2 (which are behind that same

Re: [openstack-dev] [Neutron] Port forwarding

Hi Gal, Thank you for your explanation. As you mentioned, PF is a way of reusing floating IP to access several Neutron ports. I agree with your point of view completely. Let me extend your example to explain where I was going. T1 has 20 subnets behind a router, and one of them is 10.0.0.0/24

Re: [openstack-dev] [Neutron] Port forwarding

Hi Germy, Yes i understand now. What you request is an enahncment to the API to be able to assing these port forwarding rules in bulks per subnet. I will make sure to mention this in the spec that i am writing for this. Thanks! Gal. On Tue, Sep 8, 2015 at 10:33 AM, Germy Lure

Re: [openstack-dev] [Neutron] Port forwarding

On Tue, Sep 1, 2015 at 11:59 PM, Gal Sagie wrote: > Hello All, > > I have searched and found many past efforts to implement port forwarding in > Neutron. I have heard a few express a desire for this use case a few times in the past without gaining much traction. Your

Re: [openstack-dev] [Neutron] Port forwarding

Hi Gal, I'm sorry for my poor English. Let me try again. What operator wants to access is several related instances, instead of only one or one by one. The use case is periodical check and maintain. RELATED means instance maybe in one subnet, or one network, or one host. The host's scene is

Re: [openstack-dev] [Neutron] Port forwarding

Hi, Gal Thank you for bringing this up. But I have some suggestions for the API. An operator or some other component wants to reach several VMs related NOT only one or one by one. Here, RELATED means that the VMs are in one subnet or network or a host(similar to reaching dockers on a host). Via

Re: [openstack-dev] [Neutron] Port forwarding

Hi Germy, I am not sure i understand what you mean, can you please explain it further? Thanks Gal. On Sun, Sep 6, 2015 at 5:39 AM, Germy Lure wrote: > Hi, Gal > > Thank you for bringing this up. But I have some suggestions for the API. > > An operator or some other

[openstack-dev] [Neutron] Port forwarding

Hello All, I have searched and found many past efforts to implement port forwarding in Neutron. I have found two incomplete blueprints [1], [2] and an abandoned patch [3]. There is even a project in Stackforge [4], [5] that claims to implement this, but the L3 parts in it seems older then

[openstack-dev] [Neutron] port-forwarding for router

Hi folks, I'd like to implement port-forwarding for router in l3-agent node, and meanwhile I noticed the related blueprint[1] has been there for long. Unfortunately, the code review[2] has been abandoned. Is there any latest news about this blueprint? AFAIK, this functionality is very

Re: [openstack-dev] [Neutron] port-forwarding for router

Hi, ma li, And, do you target a flexible port-forwarding (like [1], which does mirroring) or something like DNAT (as in the [2])? If the latter, suggest you contact the bp owner to see if can work together. [1] https://review.openstack.org/#/c/96149/6 [2]

Re: [openstack-dev] [Neutron] port-forwarding for router

(not for usage questions) openstack-dev@lists.openstack.org Sent: 星期五, 2014年 7 月 18日 下午 3:52:16 Subject: Re: [openstack-dev] [Neutron] port-forwarding for router Hi, ma li , And, do you target a flexible port-forwarding (like [1], which does mirroring) or something like DNAT (as in the [2

[openstack-dev] [Neutron] port forwarding from gateway to internal hosts

Hi, What's the status of this BP? - https://blueprints.launchpad.net/neutron/+spec/router-port-forwarding will it be ready for I3? The BP is approved but the patch is abandoned Regards Yair ___ OpenStack-dev mailing list

[openstack-dev] [Neutron] port forwarding from gateway to internal hosts

Hi, What's the status of this BP? - https://blueprints.launchpad.net/neutron/+spec/router-port-forwarding will it be ready for I3? The BP is approved but the patch is abandoned Regards Yair ___ OpenStack-dev mailing list