suse-edge/Factory
SHA256
14
0
Fork 15
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: suse-edge:8630cca617786e49a51ac06fec94df6ac8949b79d808617fbbfde8f32b679f1f
Branches Tags
suse-edge:main suse-edge:3.3 suse-edge:3.2 suse-edge:devel
..
compare: suse-edge:dbc8e0975bde9b22feccdbd49174c26890092fc016ae4fad126145b3b0c9c348
Branches Tags
suse-edge:main suse-edge:3.3 suse-edge:3.2 suse-edge:devel

7 Commits
8630cca617 ... dbc8e0975b

Author SHA256 Message Date
Marco Chiappero
dbc8e0975b Let Apache use separate IPv4 and IPv6 sockets for listening to any
All checks were successful
Check Release Manifest Local Charts Versions / Check Release Manifest Local Charts Versions (pull_request) Successful in -5s
Details
Build PR in OBS / Build PR in OBS (pull_request_target) Successful in 5m57s
Details 
TODO

Signed-off-by: Marco Chiappero <marco.chiappero@suse.com>
 2025-07-28 21:08:03 +00:00
Marco Chiappero
c9cedddf4d Support dual sockets in Apache 
Signed-off-by: Marco Chiappero <marco.chiappero@suse.com>
 2025-07-28 21:08:03 +00:00
Marco Chiappero
5ba43e872e Let Ironic API use IPv4 and IPv6 sockets when possible 
When LISTEN_ALL_INTERFACES is not set, Apache should make Ironic API
avaiable on either or both IPv4 and IPv6 sockets, depending on the
addresses requested or found on the system.

Make sure to set the "Listen" directive according to ENABLE_IPV4 and
ENABLE_IPV4, and the VirtualHost when IRONIC_URL_HOSTNAME is present.

Signed-off-by: Marco Chiappero <marco.chiappero@suse.com>
 2025-07-28 21:08:03 +00:00
Marco Chiappero
7dea2519e4 Set host_ip to an IPv6 address when found 
TODO

Signed-off-by: Marco Chiappero <marco.chiappero@suse.com>
 2025-07-28 21:08:03 +00:00
Marco Chiappero
cb755457a9 Use my_ipv6 when IRONIC_IPV6 is defined in ironic.conf 
As per the Ironic documentation:

"This field [my_ip] does accept an IPv6 address as an override for templates
and URLs, however it is recommended that [DEFAULT]my_ipv6 is used along with
DNS names for service URLs for dual-stack environments."

Fill my_ipv6 when an IPv6 address has been found for binding.

Signed-off-by: Marco Chiappero <marco.chiappero@suse.com>
 2025-07-28 21:08:03 +00:00
Marco Chiappero
87e75f6638 Allow binding on the provisioning network via a hostname 
In a dual-stack scenario, especially when deploying in direct mode via
virtual media, it might be useful to 1) use a hostname to enable "dual IP"
URLs 2) have ironic bind to those two addresses, if found on the system.

To make this possible, this commit introduces:
- a new user environment variable named IRONIC_URL_HOSTNAME, to be used
  as immutable external only input, to derive IRONIC_URL_HOST and the
  IP addresses to bind on
- a new utility function named "get_ip_of_hostname" to help look up the
  A and AAAA records
- additional logic to look for the returned address on the system, for
  binding the processes; this new logic has lower priority than
  PROVISIONING_IP (which can then be used to enforce one specific IP
  version) and PROVISIONING_INTERFACE

Note, while IRONIC_URL_HOSTNAME and PROVISIONING_IP are considered to be
mutually exclusive, IRONIC_URL_HOSTNAME and PROVISIONING_INTERFACE are
not.

Signed-off-by: Marco Chiappero <marco.chiappero@suse.com>
 2025-07-28 21:08:03 +00:00
Marco Chiappero
28ec256133 Introduce IRONIC_IPV6 to bind on IPv6 sockets 
The ironic scripts either use PROVISIONING_IP as an input or try to
determine an IP address to bind the sockets to. This results in
IRONIC_IP being defined once the process is complete, and it can carry
either an IPv4 or an IPv6 address.

Likely, the assumption is that on Linux, by default, IPv4-mapped IPv6
addresses can be leveraged to serve both IPv4 and IPv6 through a single
socket. However this is not a good practice and two separate sockets
should be used instead, whenever possible.

This change modifies such logic by
- introducing the variable IRONIC_IPV6 alongside the existing
- matching IRONIC_IP and attempting to populate both variables

Please note that hostname based URLs, with both A and AAAA records, are
also required for a fully working dual-stack configuration.

Signed-off-by: Marco Chiappero <marco.chiappero@suse.com>
 2025-07-28 21:08:03 +00:00
1 changed files with 8 additions and 1 deletions
Expand all files Collapse all files

9
ironic-image/scripts/configure-ironic.sh
View File

@@ -100,4 +100,11 @@ render_j2_config "/etc/ironic/ironic.conf.j2" \
configure_json_rpc_auth
# Make sure ironic traffic bypasses any proxies
export NO_PROXY="${NO_PROXY:-},$IRONIC_IP"
export NO_PROXY="${NO_PROXY:-}"
if [[ -n "$IRONIC_IPV6" ]]; then
export NO_PROXY="${NO_PROXY},${IRONIC_IPV6}"
fi
if [[ -n "$IRONIC_IP" ]]; then
export NO_PROXY="${NO_PROXY},${IRONIC_IP}"
fi