SCIENTIFIC-LINUX-USERS Archives

June 2021

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Nico Kadel-Garcia <[log in to unmask]>
Reply To:
Nico Kadel-Garcia <[log in to unmask]>
Date:
Sun, 27 Jun 2021 07:09:11 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
On Thu, Jun 24, 2021 at 1:08 PM Dave Dykstra <[log in to unmask]> wrote:
>
> The installer gives choices for different levels of installs, and for
> partitioning.  Of course you can always add packages later too.  Try it.
>
> As in the past, upgrading a RHEL-based minor release can be done in
> place but upgrading major releases (e.g. 7 -> 8) need fresh installs.
>
> Dave

Doing a better job of RHEL 8's published graphical installer could be
done, but it would no longer be directly Red Hat based. Frankly, I
gave up on the things for large environments, and published PXE setups
with kickstart files that had *much* finer resolution of deployment,
especially using multiple %post scripts to keep the operations in sane
source control, to set varieties of PXE configs for distinct setups,
and that did basic things like running "yum -y update" or "yum -y
install epel-release && yum -y install [ useful bits ]" as needed.

Since what actually gets installed by the RHEL 7 or RHEL 8 option is
never explicitly listed, it's useful to do a reference audito with
"yum list" right after the system is built, and keep a copy for
reference with the different selected options. This is where
"infrastructure as code" becomes your friend, because you can keep
copies of this stuff in a relevant git repo.

ATOM RSS1 RSS2