Suggest do not display the lbaas namespace interface ip when associate floating ip.

[Alan]

1. Create a lb pool and vip.
2. associate vip to a floatingip,then you can see two IPs, one is lb vip, another one is lbaas namespace interface ip address,so suggest only display vip address since lbaas namespace interface ip is not seen for user.

[Martin Hickey (martin-hickey)]

Hi Alan,

I have created LB pool using LBaaS v2 commands from CLI. This automatically generates VIP on the LB.

When I associate a floating IP to the VIP, the following is output:

neutron floatingip-create --port-id=20aa9a11-d4d9-4549-987b-7d6409ece170 public
Created a new floatingip:
+---------------------+--------------------------------------+
| Field | Value |
+---------------------+--------------------------------------+
| fixed_ip_address | 10.0.0.5 |
| floating_ip_address | 172.24.4.3 |
| floating_network_id | ad0a7515-c287-4e77-a804-a8a4c541b73a |
| id | 39c20936-68ea-4ead-8c02-d88487397fd5 |
| port_id | 20aa9a11-d4d9-4549-987b-7d6409ece170 |
| router_id | a1c2cf37-215c-404c-910b-3d8c722e4589 |
| status | DOWN |
| tenant_id | 3a0921d031d54d19b06a7f77166b43c9 |
+---------------------+--------------------------------------+

I am unsure where the 'lbaas namespace interface ip address' is shown. Could you describe how I can display this IP? Is it associated with LBaaS v1 commands?

Thanks,
Martin

[Alan (kaihongd)]

This is reported on LBaas V1 and associate fip from dashboard, lbaas namespace interface ips will be displayed.

[Martin Hickey (martin-hickey)]

I have been unable to reproduce the issue using the latest code base. I created pool, VIP and associated floating IP and did not see this LB namespace IP. I also check for the IP in the LBaaS namespace and did not see it only the CIDR:

sudo ip netns exec qlbaas-f6f89bb7-4b6a-4134-bc89-b27300ddf24a ip ad
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
22: tap21ab1546-83: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
    link/ether fa:16:3e:e9:56:10 brd ff:ff:ff:ff:ff:ff
    inet 10.10.30.5/24 brd 10.10.30.255 scope global tap21ab1546-83
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fee9:5610/64 scope link
       valid_lft forever preferred_lft forever

I have discussed the issue with Alan online. Here is more details on the issue:
In Horizon, Alan has seen the LB namespace IP in the"Port to be associated" dropdown of Compute->Access & Security->Allocate Floating IP->Manage Floating IP Associations dialog. He says it should not be shown, only VIPs and VM IPs.
He also mentioned that he was using Juno release. He is going to check again if he can reproduce the issue.

[Martin Hickey (martin-hickey)]

I have been unable to reproduce this issue on stable kilo release.

[Ryan Moats (rmoats)]

openstack/juno is security support