| Newsgroups |
gmane.comp.sysutils.cfengine.general |
| Message-ID |
<[email protected]> |
We're at the early stages of exploring RHEL9. (My earlier thread "RHEL9?"
was simply about the earliest stages of getting CFE started on RHEL9 at
all. This is now reasonably in hand. This new thread is different: it is
about a particular detail in a running RHEL9/CFE.)
RHEL systems up to and including RHEL8 have used "KEY=value" "ifcfg" files
in "/etc/sysconfig/network-scripts/". We could cleanly and easily apply
minor adjustments to the existing files via CFEngine, from CFE
"slist"/"data".
But at RHEL9 that directory is now empty, and the replacement mechanism
seems to be similar files in "/etc/NetworkManager/system-connections/".
But these are different. For example:
- The file is now in "INI" format with several sections
- So different "KEY=value" need to be in *different* sections
- It looks as though some "KEY" names have changed, probably also some
values; for instance "ONBOOT={yes,no}" seems to be
"{autoconnect={true,false}"
- "KEY" capitalisation seems to have changed from upper-case to
lower-case
This means that local policy now needs to be able to handle two very
different ways of working. Imagine, for instance, gradually upgrading a
set of machines from (old) RHEL{6,7,8} to (new RHEL9) while wishing to keep
the same logical configuration. Do we local sysadmins really need to have
to maintain the same CFE data in two different formats?
So...
Is there a CFE library that might be able to take a single set of data
entries (imagine these as abstracted, relatively high-level) and
automatically apply it (on the ground, low-level) the old way to old
RHEL{6,7,8} machines and the new way to new RHEL9 machines?
-- David Lee
-- Diamond
--
You received this message because you are subscribed to the Google Groups "help-cfengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/help-cfengine/6472c3e5-b922-4308-bbdb-344977a6fafbn%40googlegroups.com.