[katello-devel] Foreman Registration Design

[Dominic Cleal]

On 20/12/12 13:20, Bryan Kearney wrote:
> On 12/19/2012 11:32 AM, Dominic Cleal wrote:
>> On 19/12/12 09:38, Lukas Zapletal wrote:
>>> The RPM is generated during configuration of Katello, everything in
>>> there is dynamic (and can be also re-generated with reapplying
>>> katello-configure = puppet).
>>
>> This assumes a single puppetmaster though specified in the RPM upfront.
>>   Foreman supports any number of puppetmasters, which is specified on the
>> host (and might be populated from the hostgroup) and could be installed
>> alongside Foreman or on other hosts with smart proxies.
>>
>> How flexible will Katello be about supported Foreman and Puppet
>> architectures to start with?
>>
> The goal is to follow hte foreman model. Have installers to set up 1-n 
> proxies and 1-n puppet masters on different machines, and then use the 
> katello-ui (which in turn uses the foreman api) to register these 
> proxies and puppet masters.

As there are Puppet classes for the proxy, puppet::server and Katello
itself, I think this could be a fairly generic mechanism, not specific
to puppetmasters.  You could build additional Katello instances simply
from your main Katello instance by adding the relevant modules for the
components (puppetmaster/foreman/pulp etc) to the host, plus some
SSL/CSR magic for service certificates.

Or build them with katello-configure and register them as extensions to
the Katello host.  I'm not sure if the smart proxy bits need exposing to
the user in order to install additional puppetmasters.

> Pulp 2.0 will allows us to migrate puppet content. So, we will then be 
> able to build up content in these puppet masters using content views and 
> promotions.

This will be very exciting for the Puppet community.

-- 
Dominic Cleal
Red Hat Engineering