Investigating the Katello repos, I see there are 4 - pulp, client,
candlepin and katello
At the moment my understanding of what these are:
katello - the foreman plugin, goes on the "foreman/katello server"
(satellite server in RHEL speak)
candlepin - used on the foreman/katello server, not needed on the clients
pulp - used on the foreman/katello server, not needed on the clients
client - the end point that goes on each "enrolled" system. Put onto
systems that have their software managed by Foreman/Katello.
Is that a roughly correct breakdown?
(I'm trying to improve our current Content Views and I want to put some
repos in 'client' and some in 'not client' for various services)
cheers
L.
···
------
The most dangerous phrase in the language is, "We've always done it this
way."
That is correct. The client repo is all you should need on clients.
···
On Dec 6, 2016 12:27 AM, "Lachlan Musicman" wrote:
Hola,
Investigating the Katello repos, I see there are 4 - pulp, client,
candlepin and katello
At the moment my understanding of what these are:
katello - the foreman plugin, goes on the “foreman/katello server”
(satellite server in RHEL speak)
candlepin - used on the foreman/katello server, not needed on the clients
pulp - used on the foreman/katello server, not needed on the clients
client - the end point that goes on each “enrolled” system. Put onto
systems that have their software managed by Foreman/Katello.
Is that a roughly correct breakdown?
(I’m trying to improve our current Content Views and I want to put some
repos in ‘client’ and some in ‘not client’ for various services)
cheers
L.
The most dangerous phrase in the language is, “We’ve always done it this
way.”
