On 10/07/2009 10:19 AM, Jeff Schroeder wrote:
On Wed, Oct 7, 2009 at 7:14 AM, Michael DeHaanmdehaan@redhat.com wrote:
On 10/07/2009 09:31 AM, Joshua T Corbin wrote:
Date: Wed, 07 Oct 2009 08:57:18 -0400 From: Michael DeHaanmdehaan@redhat.com To: cobbler development listcobbler-devel@lists.fedorahosted.org Subject: Re: [PATCH 1/2] Restore the ability to disable rsync management User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Thunderbird/3.0b2
On 10/07/2009 08:06 AM, Joshua T Corbin wrote:
Functionality originally in 60fe75a5, but reverted by 4a7eee30 and 9113a190 amidst a raft of other changes.
I somewhat disagree with this patch. I want to have a minimum of settings to configure out of the box.
As a major cobbler replicate and rsyncd user I've got a few comments.
You shouldn't be wanting a high-availability configuration "out of the box" since that's not at all a simple setup, and one in which the admin needs to care a whole lot to set it up. This feature is only used by the replication sub-system of cobbler as far as I'm aware.
Replicate isn't just for HA.
It's also for backup, or seperate geographies, or an easy way to share data between a stage and production server.
Michael really hits home here. You don't want to pxe hosts in China over the wan to the united states or something really far away like that. Just getting the rpms takes ages if thats the case. There are some really big linux shops using cobbler out there so replicate is good stuff.
And it is pretty easy to set up.
I suppose part of the problem is that you are worried about cloberring a previous rsync config? Can you elaborate?
Yes indeed, these patches are a direct result of on-the-ground pain; for now it can be worked around by obliterating the rsyncd.conf template, but having cobbler regenerating the file constantrly is less than desirable.
Hmm, I'll think about this.
Would it be possible to have cobbler check look in the rsyncd.conf and see if the right modules are defined? That way it would be really straightforward for an admin to setup and wouldn't clobber the rsyncd.conf. A lot of people will scream if cobbler messes up the rsyncd.conf here and having a bunch of seperate templates for the rsyncd.conf in different geographic locations is undesirable. Ideally I'm seeing 2 settings for rsync replication... One would be for enabling rsync vs ssh replication and the other would enable rsyncd.conf management. What do you think?
Yeah, I was just thinking about that. What if we have a statement in our generated version that says "generated by cobbler" or something in the template (as a comment), and if that is /not found/ we don't overwrite the file *if existing*, and then in that case have cobbler check spit out a warning rather than overwrite it?
That could be pretty simple.
--Michael