258cff836d
With the adoption of IPsec on the management interface, the PXEboot network will play a functional role during system runtime, not just during node installation. Currently, StarlingX doesn't enforce PXEboot network configuration after installation unless the interface is explicitly assigned to its network. This change will implement the following: 1) For systems where the management network is untagged (Ethernet or bonding) and PXEboot network assignment isn't mandatory, the PXEboot interface configuration will be added in the absence of existing assignment. 2) For worker and storage nodes, the PXEboot method will be changed from "manual" to "DHCP." This enables automatic configuration towards the active controller since the management network is being converted to static for IPsec operation. 3) Interface configuration labeling will incorporate a set of rules previously distributed between Sysinv and the apply_network_config.sh script (located in stx-puppet). Unit tests have been corrected to address the database relationships between address pools, addresses, and interfaces." Test Plan: Using the variants: - [mgmt,cluster-host] over same eth port, pxe unassigned - [mgmt,cluster-host,pxeboot] over same eth port - [mgmt,cluster-host] over same bond port, pxe unassigned - [mgmt,cluster-host,pxeboot] over same bond port - [mgmt,cluster-host] over same vlan, pxe unassigned - [mgmt,cluster-host] over same vlan, pxe assigned to base eth - [mgmt,cluster-host] over same vlan, pxe assigned to base bond [PASS] Install Standard IPv4 with the above variants [PASS] Install Standard IPv6 with the above variants Story: 2010940 Task: 49383 Depends-On: https://review.opendev.org/c/starlingx/metal/+/902495 Change-Id: I334fc3ff7ee7c59750362cef803116fe097e062c Signed-off-by: Andre Kantek <andrefernandozanella.kantek@windriver.com>
config
The starlingx/config repository handles the StarlingX configuration management services.
Its key component is the System Inventory Service (Sysinv), which provides the system command-line interface (CLI)1.
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest2.