Neutron-LBaaS v2: PortID should be returned with Loadbalancer resource (API)

Bug #1584209 reported by Davide Agnello on 2016-05-20
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
octavia
Incomplete
Wishlist
Satya Pavan Nelakanti

Bug Description

When creating a new loadbalancer with lbaas v2 (Octavia provider) and would like to create a floating ip attached to the vip port for loadbalancer. Currently have to lookup the port id based on the ip address associated with the loadbalancer. It would greatly simplify the workflow if the Port ID is returned in the loadbalancer API, similar to vip API in lbaas v1.

tags: added: lbaas
Reedip (reedip-banerjee) on 2016-05-23
summary: - Neutron-LBaaS v2: PordID should be returned with Loadbalancer resource
+ Neutron-LBaaS v2: PortID should be returned with Loadbalancer resource
(API)
Brandon Logan (brandon-logan) wrote :

This is probably only exclusive to using the octavia driver. I found this comment [1] in the code that I apparently wrote, but I don't totally remember the problem. I think in this particular case it's that if octavia is responsible for creating the VIP then it owns the VIP and octavia has to delete the load balancer to delete the port.

Testing this out real quick it looks like the vip_port_id gets populated when the allocates_vip option is False, which is what it is by default. Do you have this set to true in the config?

[1] https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/drivers/octavia/driver.py#L80

Changed in neutron:
assignee: nobody → Satya Pavan Nelakanti (nelakanti11)
Changed in neutron:
status: New → In Progress
Changed in neutron:
status: In Progress → Incomplete
importance: Undecided → Wishlist
affects: neutron → octavia
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers