Comment 11 for bug 1723026

Revision history for this message
Hongbin Lu (hongbin.lu) wrote :

Zhaobo,

Would I ask for clarification of the following:

  "cloud admin find there is some abnormal traffics from source IP(Floating IP)"

It sounds like the use case is that the cloud admin needs to identify the VM with an exact floating IP (i.e. nova list --ip 172.20.50.10). Then, it seems this can be done in an efficient way. What we need to done in nova is:

1. Query neutron API for the floating IP 172.20.50.10
2. Track down to the nova instance based on the returned floating IP properties

What confused me is why we would like a regex match of floating IP? What are the use cases that requires something like: nova list --ip 172.20.50.* ?