Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1813559

Summary: Load balancer multiple VIP addresses from the same network
Product: Red Hat OpenStack Reporter: Carlos Goncalves <cgoncalves>
Component: openstack-octaviaAssignee: Gregory Thiemonge <gthiemon>
Status: CLOSED MIGRATED QA Contact: Bruna Bonguardo <bbonguar>
Severity: high Docs Contact:
Priority: high    
Version: 17.0 (Wallaby)CC: beagles, gthiemon, gurpsing, ihrachys, lpeer, majopela, njohnston, scohen
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2060387 2064797 (view as bug list) Environment:
Last Closed: 2023-10-10 12:01:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2060387, 2064797    

Description Carlos Goncalves 2020-03-14 13:07:39 UTC
There are use-cases where a load balancer should have multiple VIP addresses allocated from the same Neutron network. Users can specify additional subnet_id/ip_address pairs to bring upon the VIP port. This will allow for situations like having an LB with both IPv4+IPv6 or being exposed to both public and private subnets.

This would extend the load balancer API to support it. Example:

"additional_vips": [
  {
    "ip_address": "10.0.0.2", # This is optional
    "subnet_id": "a0304c3a-4f08-4c43-88af-d796509c97d2"
  },
]

https://storyboard.openstack.org/#!/story/2005608
https://review.opendev.org/#/q/%22Story:+2005608%22

Comment 1 Brian Haley 2021-01-14 19:29:10 UTC
I can take ownership of this one, there is still quite a bit of upstream work required since the initial patch is pretty large and needs a rebase.