On 10/07/2009 10:40 AM, Jeff Schroeder wrote:
On Wed, Oct 7, 2009 at 7:42 AM, Michael DeHaan <mdehaan@redhat.com> wrote:
  
One would be for
    
enabling rsync vs ssh replication and the other would enable
rsyncd.conf management. What do you think?


      
Do we even need to allow rsync-over-SSH? It seems like it would be rather
slow and the only use case I can think of is either (A) someone not having a
VPN, and (B) being rather concerned about internal data security.

I am not sure having the replicator go over SSH really makes the installs
any more secure than they already were.
    

How does it do it in cobbler 1.6.x? It certainly requires ssh for
something. You don't scp the stuff because it only copies the changes.
The ability to rsync over ssh is preferable in some use cases. Just
don't make it the default.

  

Cobbler uses rsync over SSH for 1.6.   For 2.0, Scott Henson cleaned it all up, so it surfaces distros and such over rsync protocol (not rsync over SSH) automatically, so that when you run replicate you don't need to deal with SSH auth.   I find this much less annoying, and it also enables hitting the replicate button in the webapp or using it over the XMLRPC API more easily.

--Michael