Activity log for bug #1491317

Date Who What changed Old value New value Message
2015-09-02 09:52:44 Gal Sagie bug added bug
2015-09-02 09:53:16 Gal Sagie neutron: assignee Gal Sagie (gal-sagie)
2015-09-02 09:53:30 Gal Sagie tags rfe
2015-09-08 19:35:20 Carl Baldwin description 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 current master. I have recently came across this requirement for various use cases, one of them is providing feature compliance with Docker port-mapping feature (for Kuryr), and saving floating IP's space. There has been many discussions in the past that require this feature, so i assume there is a demand to make this formal, just a small examples [6], [7], [8], [9] The idea in a nutshell is to support port forwarding (TCP/UDP ports) on the external router leg from the public network to internal ports, so user can use one Floating IP (the external gateway router interface IP) and reach different internal ports depending on the port numbers. This should happen on the network node (and can also be leveraged for security reasons). I think that the POC implementation in the Stackforge project shows that this needs to be implemented inside the L3 parts of the current reference implementation, it will be hard to maintain something like that in an external repository. (I also think that the API/DB extensions should be close to the current L3 reference implementation) I would like to renew the efforts on this feature and propose a spec for this to the next release. And of course if any of the people interested or any of the people that worked on this before want to join the effort, you are more then welcome to join and comment. [1] https://blueprints.launchpad.net/neutron/+spec/router-port-forwarding [2] https://blueprints.launchpad.net/neutron/+spec/fip-portforwarding [3] https://review.openstack.org/#/c/60512/ [4] https://github.com/stackforge/networking-portforwarding [5] https://review.openstack.org/#/q/port+forwarding,n,z [6] https://ask.openstack.org/en/question/75190/neutron-port-forwarding-qrouter-vms/ [7] http://www.gossamer-threads.com/lists/openstack/dev/34307 [8] http://openstack.10931.n7.nabble.com/Neutron-port-forwarding-for-router-td46639.html [9] http://openstack.10931.n7.nabble.com/Neutron-port-forwarding-from-gateway-to-internal-hosts-td32410.html 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 current master. I have recently came across this requirement for various use cases, one of them is providing feature compliance with Docker port-mapping feature (for Kuryr), and saving floating IP's space. There has been many discussions in the past that require this feature, so i assume there is a demand to make this formal, just a small examples [6], [7], [8], [9] The idea in a nutshell is to support port forwarding (TCP/UDP ports) on the external router leg from the public network to internal ports, so user can use one Floating IP (the external gateway router interface IP) and reach different internal ports depending on the port numbers. This should happen on the network node (and can also be leveraged for security reasons). I think that the POC implementation in the Stackforge project shows that this needs to be implemented inside the L3 parts of the current reference implementation, it will be hard to maintain something like that in an external repository. (I also think that the API/DB extensions should be close to the current L3 reference implementation) I would like to renew the efforts on this feature and propose a spec for this to the next release. And of course if any of the people interested or any of the people that worked on this before want to join the effort, you are more then welcome to join and comment. [1] https://blueprints.launchpad.net/neutron/+spec/router-port-forwarding [2] https://blueprints.launchpad.net/neutron/+spec/fip-portforwarding [3] https://review.openstack.org/#/c/60512/ [4] https://github.com/stackforge/networking-portforwarding [5] https://review.openstack.org/#/q/port+forwarding,n,z [6] https://ask.openstack.org/en/question/75190/neutron-port-forwarding-qrouter-vms/ [7] http://www.gossamer-threads.com/lists/openstack/dev/34307 [8] http://openstack.10931.n7.nabble.com/Neutron-port-forwarding-for-router-td46639.html [9] http://openstack.10931.n7.nabble.com/Neutron-port-forwarding-from-gateway-to-internal-hosts-td32410.html
2015-11-24 12:05:46 Henry Gessau summary Add port fowrading extension to L3 [RFE] Add TCP/UDP port forwarding extension to L3
2015-11-24 13:42:05 Akihiro Motoki neutron: importance Undecided Wishlist
2015-11-24 13:42:12 Akihiro Motoki neutron: status New Confirmed
2015-12-15 02:03:29 Armando Migliaccio neutron: status Confirmed Incomplete
2015-12-15 02:03:32 Armando Migliaccio neutron: assignee Gal Sagie (gal-sagie)
2016-03-04 04:17:19 Launchpad Janitor neutron: status Incomplete Expired
2016-08-23 12:24:41 Oleg Ilin neutron: status Expired Incomplete
2016-08-23 12:24:41 Oleg Ilin neutron: assignee Oleg Ilin (oilyin)
2016-08-23 12:25:04 Oleg Ilin neutron: status Incomplete Opinion
2016-08-23 21:42:04 Armando Migliaccio neutron: status Opinion Incomplete
2016-08-23 21:42:17 Armando Migliaccio neutron: status Incomplete Confirmed
2016-08-24 12:00:51 Oleg Ilin neutron: assignee Oleg Ilin (oilyin)
2016-08-24 12:01:12 Oleg Ilin neutron: assignee Oleg Ilin (oilyin)
2016-08-24 12:03:07 ilnurgi neutron: assignee Oleg Ilin (oilyin) ilnurgi (ilnurgi87)
2016-10-08 09:36:39 lant bug added subscriber lant
2016-10-08 09:38:54 lant removed subscriber lant
2016-10-08 09:39:04 lant bug added subscriber lant
2016-10-08 09:39:42 lant removed subscriber lant
2016-10-08 09:40:28 lant bug added subscriber lant
2016-10-08 09:40:51 lant removed subscriber lant
2016-11-22 06:23:45 lant bug added subscriber lant
2016-11-23 05:25:31 ilnurgi neutron: assignee ilnurgi (ilnurgi87)
2017-01-12 14:12:30 Matt Coleman bug added subscriber Matt Coleman
2017-01-19 21:22:53 Armando Migliaccio neutron: status Confirmed Incomplete
2017-01-20 02:48:05 Reedip neutron: assignee Reedip (reedip-banerjee)
2017-01-25 11:01:46 Reedip description 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 current master. I have recently came across this requirement for various use cases, one of them is providing feature compliance with Docker port-mapping feature (for Kuryr), and saving floating IP's space. There has been many discussions in the past that require this feature, so i assume there is a demand to make this formal, just a small examples [6], [7], [8], [9] The idea in a nutshell is to support port forwarding (TCP/UDP ports) on the external router leg from the public network to internal ports, so user can use one Floating IP (the external gateway router interface IP) and reach different internal ports depending on the port numbers. This should happen on the network node (and can also be leveraged for security reasons). I think that the POC implementation in the Stackforge project shows that this needs to be implemented inside the L3 parts of the current reference implementation, it will be hard to maintain something like that in an external repository. (I also think that the API/DB extensions should be close to the current L3 reference implementation) I would like to renew the efforts on this feature and propose a spec for this to the next release. And of course if any of the people interested or any of the people that worked on this before want to join the effort, you are more then welcome to join and comment. [1] https://blueprints.launchpad.net/neutron/+spec/router-port-forwarding [2] https://blueprints.launchpad.net/neutron/+spec/fip-portforwarding [3] https://review.openstack.org/#/c/60512/ [4] https://github.com/stackforge/networking-portforwarding [5] https://review.openstack.org/#/q/port+forwarding,n,z [6] https://ask.openstack.org/en/question/75190/neutron-port-forwarding-qrouter-vms/ [7] http://www.gossamer-threads.com/lists/openstack/dev/34307 [8] http://openstack.10931.n7.nabble.com/Neutron-port-forwarding-for-router-td46639.html [9] http://openstack.10931.n7.nabble.com/Neutron-port-forwarding-from-gateway-to-internal-hosts-td32410.html 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 current master. I have recently came across this requirement for various use cases, one of them is providing feature compliance with Docker port-mapping feature (for Kuryr), and saving floating IP's space. There has been many discussions in the past that require this feature, so i assume there is a demand to make this formal, just a small examples [6], [7], [8], [9] The idea in a nutshell is to support port forwarding (TCP/UDP ports) on the external router leg from the public network to internal ports, so user can use one Floating IP (the external gateway router interface IP) and reach different internal ports depending on the port numbers. This should happen on the network node (and can also be leveraged for security reasons). I think that the POC implementation in the Stackforge project shows that this needs to be implemented inside the L3 parts of the current reference implementation, it will be hard to maintain something like that in an external repository. (I also think that the API/DB extensions should be close to the current L3 reference implementation) I would like to renew the efforts on this feature and propose a spec for this to the next release. And of course if any of the people interested or any of the people that worked on this before want to join the effort, you are more then welcome to join and comment. [1] https://blueprints.launchpad.net/neutron/+spec/router-port-forwarding [2] https://blueprints.launchpad.net/neutron/+spec/fip-portforwarding [3] https://review.openstack.org/#/c/60512/ [4] https://github.com/stackforge/networking-portforwarding [5] https://review.openstack.org/#/q/port+forwarding,n,z [6] https://ask.openstack.org/en/question/75190/neutron-port-forwarding-qrouter-vms/ [7] http://www.gossamer-threads.com/lists/openstack/dev/34307 [8] http://openstack.10931.n7.nabble.com/Neutron-port-forwarding-for-router-td46639.html [9] http://openstack.10931.n7.nabble.com/Neutron-port-forwarding-from-gateway-to-internal-hosts-td32410.html Some more descriptions: https://review.openstack.org/#/c/224727/2/specs/mitaka/port_forwarding.rst https://review.openstack.org/#/q/status:abandoned+project:openstack/neutron+branch:master+topic:bp/router-port-forwarding
2017-06-03 06:10:42 OpenStack Infra neutron: status Incomplete In Progress
2017-06-13 07:05:33 Kevin Benton neutron: status In Progress Triaged
2017-06-15 22:23:47 Kevin Benton tags rfe rfe-approved
2017-08-08 05:15:05 OpenStack Infra neutron: status Triaged In Progress
2017-10-19 11:22:09 OpenStack Infra neutron: assignee Reedip (reedip-banerjee) zhaobo (zhaobo6)
2017-11-17 02:54:57 OpenStack Infra neutron: assignee zhaobo (zhaobo6) Reedip (reedip-banerjee)
2017-11-28 00:42:53 OpenStack Infra neutron: assignee Reedip (reedip-banerjee) zhaobo (zhaobo6)
2017-12-14 07:33:33 OpenStack Infra neutron: assignee zhaobo (zhaobo6) Reedip (reedip-banerjee)