Deprecating katello-remove


#1

Katello ships a katello-remove script, but I’d argue that with the current tools we have make it so easy to create a new machine that it’s easier to create a new one than it is to clean up an old one. From a development point of view it saves us from keeping it up to date, especially when we’re refactoring deployments.

My proposal is to deprecate it with Foreman 1.23 / Katello 3.13.


#2

From a dev standpoint, it is a bit of a PITA to maintain but it definitely has value for our users.

Sadly not all environments are easy to re-provision a host to start over and can often take days waiting to get a fresh host available to re-install. I’d vote we keep it, even if it does take periodic updates to ensure the removal actually gets rid of everything.


#3

What is the value for the users? Do they want to reuse the server for another application or want to start with a fresh Katello installation? If it’s the latter then I’d argue that foreman-installer --scenario [katello|foreman-proxy-content] --reset is the one we should be investing in.


#4

Imho it is the problem of the users’ environments if it takes so long to deploy a new host.
So my vote is “drop it”


#5

they want to re-install Katello and Foreman from scratch with either the same or a different version when unable to re-provision the target host. The installer --reset flag resets data but has no effect on the set of installed RPMs or starts from a completely clean slate.


#6

For installed RPMs I’d say it’s easier to remove the yum repositories and go over yum list extras. Then remove any .rpmsave files. If you want a fresh install, use --reset on the next installer run.