Bug 2064797 - [OVN Octavia Provider] Load balancer multiple VIP addresses from the same network
Summary: [OVN Octavia Provider] Load balancer multiple VIP addresses from the same net...
Keywords:
Status: CLOSED DUPLICATE of bug 2060387
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-ovn-octavia-provider
Version: 18.0 (Zed)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On: 1813559
Blocks: 2060387
TreeView+ depends on / blocked
 
Reported: 2022-03-16 15:02 UTC by Nate Johnston
Modified: 2022-03-16 15:13 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1813559
Environment:
Last Closed: 2022-03-16 15:09:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-13975 0 None None None 2022-03-16 15:13:52 UTC

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 ***


Note You need to log in before you can comment on or make changes to this bug.