Main Katello server pointing at itself for updates?

Support
1

Hi all,

has anyone pointed your main katello server at katello for updates? I.e.
added the "Required repositories" for katello from
http://www.katello.org/docs/3.0/installation/index.html by adding
Products/repositories, then subscribing the system and removing all
/etc/yum.repos.d/* repositories and have them come via the redhat.repo
file? Is it even a good idea?

Equally, for capsules is that possible/a good idea?

Thanks :slight_smile:
Dylan

2

I found this for Satellite -

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/chap-Red_Hat_Satellite-Installation_Guide-Configuring_a_Self_Registered_Satellite.html

so looks like it is possible

3

Haven't tried, looks like it is possible. But I still can't think of a good
reason to try :slight_smile: You would need to set up an activation key, or manually
activate only the repositories that the Katello installation instructions
activate. There are also priority setttings in the repo files created by
the Katello release package iirc, I am not sure if these can be set by a
content view / activation key? The consequences of having extra
repositories enabled and running a yum update on Katello / Foreman are not
fun to deal with :slight_smile: With Satellite it is more straightforward since there
is just one repo for Satellite. Not Foreman + Puppet + Katello + Plugins +
EPEL.

··· On Tuesday, July 19, 2016 at 4:37:39 AM UTC+10, Dylan Baars wrote: > > Hi all, > > has anyone pointed your main katello server at katello for updates? I.e. > added the "Required repositories" for katello from > http://www.katello.org/docs/3.0/installation/index.html by adding > Products/repositories, then subscribing the system and removing all > /etc/yum.repos.d/* repositories and have them come via the redhat.repo > file? Is it even a good idea? > > Equally, for capsules is that possible/a good idea? > > Thanks :-) > Dylan >