[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [katello-devel] PATCH: katello-repos for distributing the .repo files

On 09/15/2011 02:37 PM, Mike McCune wrote:
> On 09/15/2011 10:44 AM, Bryan Kearney wrote:
>> On 09/15/2011 03:01 AM, Jan Pazdziora wrote:
>>> On Thu, Sep 15, 2011 at 01:52:50AM -0400, Ohad Levy wrote:
>>>> 1. the repos in puppet need to match the one we provide, otherwise
>>>> puppet would change them (even if the repo url is the same, other
>>>> things such as name etc).
>>> The intended goal is to run the puppet only after all software has
>>> been installed, and skip any .repo manipulation and software
>>> installation when the /usr/sbin/katello-configure approach is used.
>>> That was the next thing I was gonna ask you about -- how do we
>>> restructure the puppet modules to make that possible (while keeping
>>> the .repo modifying and installation pieces there invocable by people
>>> who need them)?
>>>> 2. currently, we trigger the katello database migration when the
>>>> katello package is installed, if you install it upfront, it won't
>>>> migrate the db, I guess we need to consider another way of detecting
>>>> when a schema change is required.
>>> Right.
>> The ueber rpm is good for single machines or appliances.. not so much
>> for splittingit up (HA, fail over, etc)

Agree this implementation limits today, but first steps first... keep it
simple, allowing for modular breakage of stuff over time.

This single RPM could easily be replaced in the future by say 3 or 4
separate RPMS, one for each major component - which sucks in appropriate
puppet module needed.

> and I'm betting 90%+ of Katello installs will be single machines if I
> had to make a bet.
> Mike

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]