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

Bug 2064797

Summary: [OVN Octavia Provider] Load balancer multiple VIP addresses from the same network
Product: Red Hat OpenStack Reporter: Nate Johnston <njohnston>
Component: python-ovn-octavia-providerAssignee: OSP Team <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Eran Kuris <ekuris>
Severity: high Docs Contact:
Priority: high    
Version: 18.0 (Zed)CC: bbonguar, cgoncalves, gthiemon, ihrachys, lpeer, majopela, njohnston, scohen
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1813559 Environment:
Last Closed: 2022-03-16 15:09:38 UTC Type: ---
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: 1813559    
Bug Blocks: 2060387    

Description Nate Johnston 2022-03-16 15:02:42 UTC 
This bug is a sibling of the one it was cloned from to represent work needed in the OVN Octavia provider driver in order to maintain parity with the Amphora driver as this RFE is implemented.

+++ This bug was initially created as a clone of Bug #1813559 +++

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 Nate Johnston 2022-03-16 15:09:38 UTC 

*** This bug has been marked as a duplicate of bug 2060387 ***