[gsoc-dev] GSOC_FTP Mirror Syncing

[Milap Bhojak]

Hello,

As running discussion on IRC i think this Google PubSubHubbub will work. Google
PubSubHubbub is for pushing and in push system. we need them to check, but
we dont need to check as often as before.

Here i attach one file take a look. and ask me questions.


On Tue, Mar 18, 2014 at 11:06 PM, Kennric <kennric at osuosl.org> wrote:

>
>
>
> -------- Original Message --------
> Subject: Re: [gsoc-dev] GSOC_FTP Mirror Syncing
> Date: Tue, 18 Mar 2014 10:29:03 -0700
> From: Kennric <kennric at osuosl.org>
> To: gsoc-dev at lists.osuosl.org
>
> Hello, and thank you for your proposal ideas. We have some questions,
> since we are not very familiar with pubsubhub:
>
> If I understand you, you mean to have the mirror ftp servers subscribe
> to their file resources via a hub, and have the file sources (the
> project where the files originate, like the Debian project, etc) as
> publishers. So when a new set of files is ready from a publisher, the
> publisher pings the hub, and then the hub notifies all the slaves who
> then begin an rsync process pulling files from the master. Is the master
> another subscriber pulling resources directly from the publishers?
>
> Could you perhaps diagram the flow you have in mind to help clarify?
> Some pseudo-code snippets would be helpful too. What tools would use use
> to send http requests to the hub and subscribers?
>
> Pubsubhub also seems to use multicast on the hub to distribute
> resources, how do you see that fitting in here?
>
> Thanks,
> Ken
>
> On 03/18/2014 09:24 AM, Milap Bhojak wrote:
> > Hello,
> >
> > Here After Research i found one awesome thing that can help us in FTP
> > MIRROR SYNCING project.
> >
> > Let me explain :
> >
> > i found Google's PubSubHubbub Protocol
> > <https://code.google.com/p/pubsubhubbub/>. Now how it will help us ? We
> > can do below things.
> >
> > 1. Master Server will acts as Publisher (PubSubHubbub)
> > 2. Mirror Server will acts as Subscriber (PubSubHubbub)
> > 3. Every Time when Master data changes , Master will call back
> >     Subscriber to initiate rSync procedure.
> > 4. For this approach we can use Google PubSubHubbub of Push
> >     message, which will avoid un-neccesory trigers on Master server.
> > 5. (Optional) we can also create File Store Specific Publisher which
> >     will acts as Master server of specific file store
> > 6. Dashboard
> >      1. IP/Region Specific Current Downloads
> >      2. Manage black list
> >      3. Live Bandwidth Bar
> >      4. Live Sync Status
> >      5. Other required information from Log
> >      6. Alerts.
> >
> > I'm Ready for this opportunity. I'm too excite GSOC 2014 with OSUOSL.
> > i'm sending you my proposal in few hours.
> >
> > Looking for Positive Reply :)
> >
> >
> > --
> > Thanks,
> > Milap Bhojak |         Google Developers Group - Gandhinagar  |
> > milapbhojak.exe at gmail.com <mailto:milapbhojak.exe at gmail.com> |
> >        +91-9898855075
> >
> >
> >
> > _______________________________________________
> > gsoc-dev mailing list
> > gsoc-dev at lists.osuosl.org
> > http://lists.osuosl.org/mailman/listinfo/gsoc-dev
> >
>
>
> --
> Kenneth Lett
> Software Engineer                                Open Source Lab
> Information Services                             Oregon State University
> _______________________________________________
> gsoc-dev mailing list
> gsoc-dev at lists.osuosl.org
> http://lists.osuosl.org/mailman/listinfo/gsoc-dev
>
>
>


-- 
Thanks,
Milap Bhojak | Google Developers Group - Gandhinagar |
milapbhojak.exe at gmail.com |
 +91-9898855075
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/gsoc-dev/attachments/20140319/737abeb9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FTP.pdf
Type: application/pdf
Size: 120753 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/gsoc-dev/attachments/20140319/737abeb9/attachment-0001.pdf>