[gsoc-dev] [osuosl-mirror-sync] Questions

Pranjal Mittal mittal.pranjal at gmail.com
Tue Mar 18 16:00:38 UTC 2014


On Tue, Mar 18, 2014 at 9:12 PM, Lance Albertson <lance at osuosl.org> wrote:

>
>
>
> On Tue, Mar 18, 2014 at 6:55 AM, Pranjal Mittal <mittal.pranjal at gmail.com>wrote:
>
>> Hi Lance,
>>
>> (1) In the rsyncd-osl.conf [1] file why do we have 2 modules that are
>> exactly same, ie. [all] and [all1]
>>
>
> I can't find a specific reason in the git logs on our end so I imagine it
> may just be for historical purposes. I do see a few references in some of
> the scripts. My impression is that we used to just have one array a long
> time ago.
>
>
>> (2) In the xinetd directory there are 2 files, not sure if I get the
>> purpose of both of them. So we are running 2 rsync daemons one for everyone
>> to use and the other for the ftp hosts?
>>
>
> That is correct. The first one "rsync" is the one everyone uses. The
> primary difference is that it limits the number of instances so that people
> can't DoS the rsync service. We don't want the slaves to run into the same
> limitations so as a way around it we use a separate rsync daemon on a
> different port that is restricted by port and access to only the slaves.
>
>
>>  Also sometimes we rsync is used over ssh like in the case when we create
>> a user for each $project and add the ssh public key for that user to
>> authorized keys.
>>
>
> That is correct, but generally this isn't the norm. I'd say 95% of the
> syncs happen over the rsync proper protocol and not rsync+ssh. SSH is
> generally only used as a trigger for the push-based syncs (i.e.
> debian/ubuntu repos).
>

Ok, this makes things a lot clear. I think we should add this to the docs.
On seeing the "adding project" documentation the first impression that I
got was that we are mainly utilizing rsync over ssh. And I think it makes
sense to use the daemon way since it is faster. We anyways don't need
encryption for mirroring public content.


>
>
>> Since rsync is an important component of the current architecture it
>> would be great if we have some docs on how we are using rsync in different
>> ways for diferent purposes.
>>
>
> I will do my best. Can you give some examples where I need to document
> this better?
>

I think we can add information about this in the adding project page or
maybe make a separate FAQ's page and put these in the form of questions and
answers.

Also on a side note, it will be useful to have a doc page which explains
the repository tree, ie. what does each folder in osuosl-mirror-sync
contain. I'l add whatever I know and push it up on github.


Thanks a lot!



> Thanks-
>
>
>> [1]
>> https://github.com/osuosl/osuosl-mirror-sync/blob/master/rsync/rsyncd-osl.conf
>> [2] https://github.com/osuosl/osuosl-mirror-sync/tree/master/xinetd
>>
>>
>>
>> Thanks,
>>
>> Kind Regards,
>> - Pranjal
>>
>
>
>
> --
> Lance Albertson
> Director
> Oregon State University | Open Source Lab
>


--
Pranjal Mittal
Indian Institute of Technology, B.H.U, Varanasi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/gsoc-dev/attachments/20140318/b11703aa/attachment.html>


More information about the gsoc-dev mailing list