openstack/horizon — pull request #38 by jpic (2014-06-12 21:02:07+00:00)
Title: LB Pool names don't make it to the FloatingIp management UI

I'd like to say that Horizon is really great, as an old-time Djangonaut I can say that the framework you built looks really awesome and I'm looking forward to learn as much as I can about it ! So, kudos for that !

Consider the following pool:

![2014-06-12-225541_961x292_scrot](https://cloud.githubusercontent.com/assets/94636/3263596/efebe002-f273-11e3-9a0e-5d2ac4a06560.png)

In "Manage Floating IP Associations": the port name for a Vip port is "None" which might be a bit confusing for the user:

![2014-06-12-225337_338x258_scrot](https://cloud.githubusercontent.com/assets/94636/3263587/cdc1ab42-f273-11e3-820b-cb3c22b3706c.png)

If the Vip is attached to a load balancer pool: it could be the name of the pool:

![2014-06-12-225407_333x249_scrot](https://cloud.githubusercontent.com/assets/94636/3263595/deb75b68-f273-11e3-9f53-501f1a68ecda.png)

Once a floating ip associated with an LB pool vip, the "Instance" column for this floating IP in "Access & Security" -> "Floating IPs" is just "-" which might also be a bit confusing for the user:

![2014-06-12-225422_942x173_scrot](https://cloud.githubusercontent.com/assets/94636/3263606/1560ff02-f274-11e3-961d-ce651e87496a.png)

It could be the name of the LB pool again:

![2014-06-12-225432_948x172_scrot](https://cloud.githubusercontent.com/assets/94636/3263611/247cb31e-f274-11e3-846a-317e90449729.png)

What do you think ?

(I know that you can't accept the pull request as is, but if you like the idea I can work on it: tests, refactor, and maybe after I could help with the second point mentioned in fa2e379)

I have never contributed to Horizon nor OpenStack and I'm looking forward to learn ... Thanks a lot for your time and patience !