Bug 2057921 - ipv6 management network for Octavia
Summary: ipv6 management network for Octavia
Keywords:
Status: ON_QA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: tripleo-ansible
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ga
: ---
Assignee: Tom Weininger
QA Contact: Bruna Bonguardo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-24 08:08 UTC by Gregory Thiemonge
Modified: 2023-08-16 10:34 UTC (History)
11 users (show)

Fixed In Version: tripleo-ansible-3.3.1-1.20230322222820.b65b485.el9ost
Doc Type: Technology Preview
Doc Text:
In RHOSP 17.1, a technology preview is available for creating load balancers over an IPv6 management network. Using a private IPv6 management network for the Load-balancing service (octavia) may simplify edge deployments.
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 845729 0 None MERGED Add support for IPv6 lb management network 2023-02-03 14:10:52 UTC
OpenStack gerrit 872650 0 None MERGED Add support for IPv6 lb management network 2023-03-03 09:54:55 UTC
Red Hat Issue Tracker OSP-13115 0 None None None 2022-02-24 08:18:55 UTC

Internal Links: 1961850

Description Gregory Thiemonge 2022-02-24 08:08:29 UTC
Octavia uses an ipv4 subnet (/16) for its management network.
When dealing with Edge deployments, it needs additional subnets (networks) with similar parameters (/16), so it requires the pre-allocation of a lot of routable IP addresses and it may be complicated to find an unused /16 private range.

To mitigate this issue, Octavia should be able to use a private ipv6 subnet for the management network. This ipv6 management network would not be enabled by default, but an option in Tripleo would enable it.

Additional considerations:
- need to think about the update from an ipv4 to an ipv6 management network
- need to add a CI job with this option

Comment 11 Lon Hohberger 2023-08-16 10:34:19 UTC
According to our records, this should be resolved by tripleo-ansible-3.3.1-1.20230518201535.el9ost.  This build is available now.


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