Consolidate the persistent and dynamic configuration of s390-specific
network devices by delegating the configuration to the existing framework
zdev from s390-tools.
This is part of a larger consolidation comprising:
https://github.com/ibm-s390-linux/s390-tools/pull/158
https://github.com/dracutdevs/dracut/pull/2534
https://github.com/storaged-project/blivet/pull/1162
https://github.com/rhinstaller/anaconda/pull/5250
https://github.com/steffen-maier/s390utils/commits/zdev
However, there are no dependencies on these other pull requests, so the
change here can go in independently. It only depends on zdev from
s390-tools, which exists since years.
Zdev's job is to perform low-level configuration after which the user gets
architecture-independent objects such as network interfaces. Those can and
should in turn be configured with existing common code mechanisms. So
there's a clear separated layering for configuration duties.
In particular, the s390-specific network devices currently are: ZNET
representing channel-attached network (QETH incl. OSA and HiperSockets,
LCS, CTC). Zdev has a stable command line user interface and abstracts from
sysfs and from a persistent configuration representation. Zdev encapsulates
configuration details. Systems management code can simply delegate
configuration to zdev and thus reduce architecture-specific code.
This improves user experience, serviceability, maintainability, and reduces
test effort.
Steffen Maier (2):
dracut-module-setup: consolidate s390 network device config (#1937048)
dracut-module-setup: remove old s390 network device config (#1937048)
dracut-module-setup.sh | 53 ++++++++++++++----------------------------
1 file changed, 17 insertions(+), 36 deletions(-)
base-commit: 5058cef90c2e24ff3a17a9c5560e16363e3281f5
--
2.39.3