FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 07-08-2008, 01:08 PM
David Timms
 
Default InstantMirror Redesign / current best /simplest way to achieve

A long, long time ago, Kulbir Saini wrote:

Thank a lot for noting down all those points. They helped me to have
a more clear idea of InstantMirror. And thanks for the encouragement
as well


Hi, wondering what is considered _the_ current approach for making an
internal Fedora proxy mirror ?

Does the MirrorManager 0.4 code actually work, eg for 5 PC's ?

Did something else {other than full rsync mirroring} emerge to solve
this type of problem ?


I was wondering if an automated way to get the clients to use the proxy
/ cache would by to implement dns entries for the real yum server names,
that point to your internal ~mirror server; and hence bypass requiring
individual machine proxy setup ?


Regards, DaveT.

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 07-08-2008, 01:16 PM
Suren Karapetyan
 
Default InstantMirror Redesign / current best /simplest way to achieve

On Tue, 2008-07-08 at 23:08 +1000, David Timms wrote:
> A long, long time ago, Kulbir Saini wrote:
> > Thank a lot for noting down all those points. They helped me to have
> > a more clear idea of InstantMirror. And thanks for the encouragement
> > as well
>
> Hi, wondering what is considered _the_ current approach for making an
> internal Fedora proxy mirror ?
> Does the MirrorManager 0.4 code actually work, eg for 5 PC's ?
>
> Did something else {other than full rsync mirroring} emerge to solve
> this type of problem ?
>
> I was wondering if an automated way to get the clients to use the proxy
> / cache would by to implement dns entries for the real yum server names,
> that point to your internal ~mirror server; and hence bypass requiring
> individual machine proxy setup ?
>
> Regards, DaveT.
>

Even with all it's weeknesses InstantMirror could be used with
MirrorManager to do transparent caching/mirroring...
Take a system with enough HDD space, install instantmirror,
go to mirror manager admin page, create a new site, add your ips, and
the mirror.
The get the mirror reporting script and make it run with cron
It isn't perfect but it's much berrer than nothing


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 07-08-2008, 03:14 PM
Warren Togami
 
Default InstantMirror Redesign / current best /simplest way to achieve

Suren Karapetyan wrote:

On Tue, 2008-07-08 at 23:08 +1000, David Timms wrote:

A long, long time ago, Kulbir Saini wrote:

Thank a lot for noting down all those points. They helped me to have
a more clear idea of InstantMirror. And thanks for the encouragement
as well
Hi, wondering what is considered _the_ current approach for making an
internal Fedora proxy mirror ?

Does the MirrorManager 0.4 code actually work, eg for 5 PC's ?

Did something else {other than full rsync mirroring} emerge to solve
this type of problem ?


I was wondering if an automated way to get the clients to use the proxy
/ cache would by to implement dns entries for the real yum server names,
that point to your internal ~mirror server; and hence bypass requiring
individual machine proxy setup ?


Regards, DaveT.



Even with all it's weeknesses InstantMirror could be used with
MirrorManager to do transparent caching/mirroring...
Take a system with enough HDD space, install instantmirror,
go to mirror manager admin page, create a new site, add your ips, and
the mirror.
The get the mirror reporting script and make it run with cron
It isn't perfect but it's much berrer than nothing




I personally use squid in reverse proxy mode instead of InstantMirror.
The main drawback of squid is the cache cannot be shared for other
protocols (like rsync), but it is otherwise better because it handles
cleanup and respects whatever maximum amount of storage you set.
InstantMirror will keep growing and growing until it exhausts all space.
InstantMirror also poorly handles concurrent clients.


Warren

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 07-08-2008, 03:25 PM
"Arthur Pemberton"
 
Default InstantMirror Redesign / current best /simplest way to achieve

On Tue, Jul 8, 2008 at 10:14 AM, Warren Togami <wtogami@redhat.com> wrote:
> Suren Karapetyan wrote:
>>
>> On Tue, 2008-07-08 at 23:08 +1000, David Timms wrote:
>>>
>>> A long, long time ago, Kulbir Saini wrote:
>>>>
>>>> Thank a lot for noting down all those points. They helped me to
>>>> have
>>>> a more clear idea of InstantMirror. And thanks for the encouragement
>>>> as well
>>>
>>> Hi, wondering what is considered _the_ current approach for making an
>>> internal Fedora proxy mirror ?
>>> Does the MirrorManager 0.4 code actually work, eg for 5 PC's ?
>>>
>>> Did something else {other than full rsync mirroring} emerge to solve this
>>> type of problem ?
>>>
>>> I was wondering if an automated way to get the clients to use the proxy /
>>> cache would by to implement dns entries for the real yum server names, that
>>> point to your internal ~mirror server; and hence bypass requiring individual
>>> machine proxy setup ?
>>>
>>> Regards, DaveT.
>>>
>>
>> Even with all it's weeknesses InstantMirror could be used with
>> MirrorManager to do transparent caching/mirroring...
>> Take a system with enough HDD space, install instantmirror,
>> go to mirror manager admin page, create a new site, add your ips, and
>> the mirror.
>> The get the mirror reporting script and make it run with cron
>> It isn't perfect but it's much berrer than nothing
>>
>>
>
> I personally use squid in reverse proxy mode instead of InstantMirror. The
> main drawback of squid is the cache cannot be shared for other protocols
> (like rsync), but it is otherwise better because it handles cleanup and
> respects whatever maximum amount of storage you set. InstantMirror will keep
> growing and growing until it exhausts all space. InstantMirror also poorly
> handles concurrent clients.


I wanted to try InstantMirror, but was in a rush. I just used a basic
squid setup.

Are their any advantages of using it as a reverse mirror vs. regular
squid usage?

Arthur Pemberton

--
Fedora 7 : sipping some of that moonshine
( www.pembo13.com )

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 

Thread Tools




All times are GMT. The time now is 07:23 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org