Activity log for bug #1723026

Date Who What changed Old value New value Message
2017-10-12 07:53:05 zhaobo bug added bug
2017-10-12 07:54:39 Zhenyu Zheng neutron: assignee Zhenyu Zheng (zhengzhenyu)
2017-10-12 07:54:48 zhaobo tags rfe
2017-10-12 07:55:00 zhaobo neutron: assignee Zhenyu Zheng (zhengzhenyu) zhaobo (zhaobo6)
2017-11-06 11:42:10 Armando Migliaccio neutron: status New Confirmed
2017-11-06 11:42:13 Armando Migliaccio neutron: importance Undecided Wishlist
2017-11-06 11:42:19 Armando Migliaccio neutron: assignee zhaobo (zhaobo6)
2018-01-12 20:20:01 hongbin neutron: assignee hongbin (hongbin034)
2018-01-12 23:53:33 OpenStack Infra neutron: status Confirmed In Progress
2018-01-15 23:21:19 Miguel Lavalle neutron: status In Progress Confirmed
2018-01-17 19:05:39 OpenStack Infra neutron: status Confirmed In Progress
2018-01-17 19:05:39 OpenStack Infra neutron: assignee hongbin (hongbin034) Hongbin Lu (hongbin.lu)
2018-01-18 21:55:04 Hongbin Lu neutron: status In Progress Confirmed
2018-01-25 11:55:28 YAMAMOTO Takashi tags rfe rfe rfe-confirmed
2018-02-01 23:00:30 Miguel Lavalle tags rfe rfe-confirmed rfe rfe-triaged
2018-03-08 01:53:29 zhaobo description [problem] Cannot get the device_id when query floatingip directly, users/admin need to query the specific Floating IP address to find the FloatingIP resources, then find the associated port_id, show port, finally get the device_id. Provide a way to get the device_id from floatingip could be very useful for nova to query the instance by Floating IP address in high performance. [Use cases] In cloud env, the cloud admin find there is some abnormal traffics from source IP(Floating IP) in the external FW/Router/Network health check tools. Cloud admin need a ability to find the abnormal vnic and the VM owner to notify that the VM may be under virus attack. So the admin need to stop VM or take other rescue way to process it. Nova cloud query the instance by floatingip with regex matching filtering, this is also very useful for this destination. Nova store these infos into the network_infocache, it is hard to query instance like this. Proposal ======== * Support list/get floatingip show the related ports' device_id * Adding regex matching support in DB layer using "LIKE" SQL phrase. [problem] Cannot get the device_id when query floatingip directly, users/admin need to query the specific Floating IP address to find the FloatingIP resources, then find the associated port_id, show port, finally get the device_id. Provide a way to get the device_id from floatingip could be very useful for users/external tools to query the instance by Floating IP address in high performance. [Use cases] In cloud env, the cloud admin find there is some abnormal traffics from source IP(Floating IP) in the external FW/Router/Network health check tools. Cloud admin need a ability to find the abnormal vnic and the VM owner to notify that the VM may be under virus attack. So the admin need to stop VM or take other rescue way to process it. Proposal ======== * Support list/get floatingip show the related ports' device_id
2018-04-06 17:29:34 Miguel Lavalle tags rfe rfe-triaged rfe rfe-approved
2018-04-09 20:26:38 OpenStack Infra neutron: status Confirmed In Progress
2020-03-24 21:40:05 Slawek Kaplonski neutron: status In Progress Fix Released
2020-03-24 21:40:13 Slawek Kaplonski tags rfe rfe-approved rfe-approved