The LBaaS VIP ports (device_owner=neutron:LOADBALANCER) appear in the Instances' "Manage Floating IP Associations" dialog

[Rami Vaknin]

Version
=======
Havana on rhel

Description
===========
The LBaaS VIP ports appear in the Instances' "Manage Floating IP Associations" dialog for floating ip association, however they are not related to instances hence they should not appear there at all.

Note that they appear with the "None" prefix (the prefix usually denotes the instance name).

[Akihiro Motoki (amotoki)]

Floating IP management form itself is not specific to VM instances. Ports from Load Balancer or something others are valid floating IP targets. IMO the list should not be limited to VM instances only.

The following minor things you pointed are worth fixed.
- A name "None" is confusing.
- The help message "Select the IP address you with to associate with the selected instance".

However, IMO the main reported issue is not a bug.
Could you clarify what is the problem?

[Rami Vaknin (rvaknin)]

The main problem is that I can access this floating ip management only from the "More" button of a *specific instance*, which means that if one wants to assign a floating ip to his VIP - he probably won't look for this functionality over there.
If there was a central location for floating IPs allocations - it would mitigate this bug.

In addition, the minor things you've mentioned don't make the admin's life easier.

[Akihiro Motoki (amotoki)]

Regarding the main problem, I believe we already have "a central localtion for floating IPs allocation. Don't you see "Associate" button in Floating IP table at "Floating IPs" tab of "Access & Security". The exactly same implementation is used for both menu. We can associate an floating IP to VIP here.

Of course, when "Manage Floating IP Associations" is invoked from an instance menu, it is better to list only fixed IPs of instances.

[Rami Vaknin (rvaknin)]

Thanks, I didn't remember that "Floating IPs" exists under "Access & Security" :-)
So we only left with the "None" and help message (from your comment #2) and filtering the vip from the instance's floating ip view.

[Akihiro Motoki (amotoki)]

What we should do is to filter out ports not related to the instance when Instances' "Manage Floating IP Associations" dialog is selected.

[Lin Hua Cheng (lin-hua-cheng)]

Akihiro: Is the fix here to filter out the port "None:XXX" (lbaas) from the dropdown of Floating IP Association panel?

[Timur Sufiev (tsufiev-x)]

@Lin, it seems to me that the original issue was fixed in bug 1252403.

[Timur Sufiev (tsufiev-x)]

I cannot reproduce the situation, no ViP is suggested when I'm associating floating IP to an instance.

[Lin Hua Cheng (lin-hua-cheng)]

@Timur, maybe we just close the bug now since it has already been fixed by the other bug report.

@Rami, it would be great if you can confirm if that fixes your issue. Thanks!

[Launchpad Janitor (janitor)]

[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]