http://fedorapeople.org/~wtogami/temp/InstantMirror-release/InstantMirror-0.2-0.fc8.noarch.rpm
http://fedorapeople.org/~wtogami/temp/InstantMirror-release/InstantMirror-0.2-0.fc8.src.rpm
http://fedorapeople.org/~wtogami/temp/InstantMirror-release/InstantMirror-0.2.tar.bz2
bzr branch http://fedorapeople.org/~wtogami/temp/InstantMirror/

Thanks to Ed Swierk's quick hacking, this theoretically is the first
somewhat working version of InstantMirror. See the TODO file for bug
warnings and the SELinux workaround.


We still don't have a hosted.fp.org project setup yet so the above is
only the temporary location. Until we have that permanent project
setup, please report bugs and make suggestions for improvement here in
this thread.


Warren Togami
wtogami@redhat.com

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

http://fedorapeople.org/~wtogami/temp/InstantMirror-release/
InstantMirror-0.2-0.fc8.src.rpm


Runs on F7 too.
Thank you for this, it works well in our small business environment
where conserving bandwidth to the internet is important.



We still don't have a hosted.fp.org project setup yet so the above is
only the temporary location. Until we have that permanent project
setup, please report bugs and make suggestions for improvement here in
this thread.


The included InstantMirror.conf file that goes into /etc/httpd/
conf.d/ stomps on any other configuration you may have set up.
Because the file name starts with an upper case "eye" it is loaded
first by the


Include conf.d/*.conf

directive. It becomes the _default_ host for everything on port 80.
You can check how that works by

/usr/sbin/httpd -S
mv /etc/httpd/conf.d/InstantMirror.conf /etc/httpd/conf.d/
zInstantMirror.conf

/usr/sbin/httpd -S
( move it back if you prefer the stomping behavior )

From <http://httpd.apache.org/docs/2.2/vhosts/name-based.html>


Main host goes away

If you are adding virtual hosts to an existing web server, you must
also create a <VirtualHost> block for the existing host. The
ServerName and DocumentRoot included in this virtual host should be
the same as the global ServerName and DocumentRoot. List this
virtual host first in the configuration file so that it will act as
the default host.


This directive

NameVirtualHost *:80

should be uncommented in /etc/httpd/conf/httpd.conf
and a <VirtualHost> directive should be set up for the default web
content, and should be loaded before the InstantMirror.conf file.


I have something that works with my test system, but I'm still not in
a position to make a bomb-proof generalized config file
recommendation. It seems using VirtualHost is the best way to create
the Instant Mirror, but integrating that into an existing apache conf
needs to be handled with a bit more care. This could be communicated
with better comments or additional commented out directives in the
provided InstantMirror.conf file.


I use several files in conf.d to create aliases and WebDAV
collections for calendaring and file sharing on our main server. I
haven't tested yet with all those conf files mixed in.


Also, I think separating the logging is a good thing to do with
directives such as


ErrorLog logs/mirror-error_log
CustomLog logs/mirror-access_log

within the InstantMirror virtual host block.
That way when the python script throws a hissy fit about file
permissions, it is easier to find.


Thanks again for InstantMirror,


Charles Dostale

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

chasd wrote:
http://fedorapeople.org/~wtogami/temp/InstantMirror-release/InstantMirror-0.2-0.fc8.src.rpm



Runs on F7 too.
Thank you for this, it works well in our small business environment
where conserving bandwidth to the internet is important.



We still don't have a hosted.fp.org project setup yet so the above is
only the temporary location. Until we have that permanent project
setup, please report bugs and make suggestions for improvement here in
this thread.


The included InstantMirror.conf file that goes into /etc/httpd/conf.d/
stomps on any other configuration you may have set up.
Because the file name starts with an upper case "eye" it is loaded first
by the


Include conf.d/*.conf

directive. It becomes the _default_ host for everything on port 80.
You can check how that works by

/usr/sbin/httpd -S
mv /etc/httpd/conf.d/InstantMirror.conf
/etc/httpd/conf.d/zInstantMirror.conf

/usr/sbin/httpd -S
( move it back if you prefer the stomping behavior )

From <http://httpd.apache.org/docs/2.2/vhosts/name-based.html>


Main host goes away

If you are adding virtual hosts to an existing web server, you must
also create a <VirtualHost> block for the existing host. The
ServerName and DocumentRoot included in this virtual host should be
the same as the global ServerName and DocumentRoot. List this virtual
host first in the configuration file so that it will act as the
default host.


This directive

NameVirtualHost *:80

should be uncommented in /etc/httpd/conf/httpd.conf
and a <VirtualHost> directive should be set up for the default web
content, and should be loaded before the InstantMirror.conf file.


I have something that works with my test system, but I'm still not in a
position to make a bomb-proof generalized config file recommendation. It
seems using VirtualHost is the best way to create the Instant Mirror,
but integrating that into an existing apache conf needs to be handled
with a bit more care. This could be communicated with better comments or
additional commented out directives in the provided InstantMirror.conf
file.


I use several files in conf.d to create aliases and WebDAV collections
for calendaring and file sharing on our main server. I haven't tested
yet with all those conf files mixed in.


Also, I think separating the logging is a good thing to do with
directives such as


ErrorLog logs/mirror-error_log
CustomLog logs/mirror-access_log

within the InstantMirror virtual host block.
That way when the python script throws a hissy fit about file
permissions, it is easier to find.


Just recently I setup a new system, previously I had all my virtual
hosts in one virtual.conf that I included by doing a

include conf/virtual.conf

from the httpd.conf. I just switched it to multiple files, one for each
virtual host, they are now included by doing


include virtual.d/*conf

Perhaps if httpd were re-tooled to setup virtual hosts in that manner?
or should I have put my virtual hosts in the conf.d directory? I just
seemed cleaner to separate sites from what seemed like modular configs..


Anyway the point of this rambling is if we had something like that,
system that use httpd/apache could add a virtual host config to
httpd/virtual.d/ and not step on each others toes.


--
Nathanael D. Noblet

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

Perhaps if httpd were re-tooled to setup virtual hosts in that manner?
or should I have put my virtual hosts in the conf.d directory? I just
seemed cleaner to separate sites from what seemed like modular
configs..


Anyway the point of this rambling is if we had something like that,
system that use httpd/apache could add a virtual host config to
httpd/virtual.d/ and not step on each others toes.

--
Nathanael D. Noblet


If it was expected that InstantMirror was to be very popular, or
there was a large number of other packages that would make use of
<VirtualHost> directives, it might make sense to modify the default
apache configuration to be more "virtual host friendly." As it
stands, I think some prudent suggestions in the provided
InstantMirror.conf file ( and perhaps renaming it ) is the best plan.


"Persoanl File Sharing" aka gnome-user-share would be the only other
"popular" package that might benefit from a "virtual host friendly"
apache, but it spawns apache from a completely separate
configuration, so it shouldn't be considered here. However I might
not be aware of other packages in "Everything" that _should_ be
considered.


Anyway, I was able to test my suggestions on two different servers
with two different sets of configuration files in conf.d, and my
recommendations seem to work well in both cases. I guess that means
this package is thoroughly tested


If I could make one other suggestion about InstantMirror, it would be
to include a sample.repo file in /usr/share/doc/InstantMirror-x/ or
throw it into /etc/yum.repos.d/ with enabled=0.


Experienced admins should really know this config file stuff, but I
run into a lot of generally competent computer people that are new to
Linux and need a bit a of hand-holding -- hand-holding such as well
commented sample configuration files. Sensible defaults, right ?


BTW, InstantMirror is much simpler, lighter weight and easier to use
than WSUS. Although WSUS has other abilities, InstantMirror has a
good 50% of the functionality of WSUS. This package may seem
innocuous, if you mentioned WSUS in the same breath as InstantMirror,
it might warrant a mention as a feature, at least targeted at some
new-to-Linux admins.



Charles Dostale

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

On 12/4/07, chasd <chasd@silveroaks.com> wrote:
> If it was expected that InstantMirror was to be very popular, or
> there was a large number of other packages that would make use of
> <VirtualHost> directives, it might make sense to modify the default
> apache configuration to be more "virtual host friendly." As it
> stands, I think some prudent suggestions in the provided
> InstantMirror.conf file ( and perhaps renaming it ) is the best plan.

Actually InstantMirror should work just fine in a simple
non-VirtualHost configuration, so perhaps the default Apache
configuration file can leave out the VirtualHost directives and we can
bundle the fancier VirtualHost configuration as an example in the docs
directory.

> Anyway, I was able to test my suggestions on two different servers
> with two different sets of configuration files in conf.d, and my
> recommendations seem to work well in both cases. I guess that means
> this package is thoroughly tested

Well, Warren has done an excellent job finding stupid bugs in my
original implementation.

> If I could make one other suggestion about InstantMirror, it would be
> to include a sample.repo file in /usr/share/doc/InstantMirror-x/ or
> throw it into /etc/yum.repos.d/ with enabled=0.

Good idea.

> BTW, InstantMirror is much simpler, lighter weight and easier to use
> than WSUS. Although WSUS has other abilities, InstantMirror has a
> good 50% of the functionality of WSUS. This package may seem
> innocuous, if you mentioned WSUS in the same breath as InstantMirror,
> it might warrant a mention as a feature, at least targeted at some
> new-to-Linux admins.

I have no idea what WSUS does but my guess is the 80/20 rule applies.
Still, the fact that a useful admin tool can be implemented in less
than 100 lines of Python demonstrates the excellent design of Apache,
mod_python and Python.

--Ed

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

Ed Swierk wrote:

On 12/4/07, chasd <chasd@silveroaks.com> wrote:

If it was expected that InstantMirror was to be very popular, or
there was a large number of other packages that would make use of
<VirtualHost> directives, it might make sense to modify the default
apache configuration to be more "virtual host friendly." As it
stands, I think some prudent suggestions in the provided
InstantMirror.conf file ( and perhaps renaming it ) is the best plan.


Actually InstantMirror should work just fine in a simple
non-VirtualHost configuration, so perhaps the default Apache
configuration file can leave out the VirtualHost directives and we can
bundle the fancier VirtualHost configuration as an example in the docs
directory.


I personally dislike this idea. It is already fully commented out in
the default InstantMirror.conf. Why don't we:

1) Keep the contents as-is.
2) Add a note to other examples the doc directory.
3) Rename the file to zz-InstantMirror.conf so it never goes first.




If I could make one other suggestion about InstantMirror, it would be
to include a sample.repo file in /usr/share/doc/InstantMirror-x/ or
throw it into /etc/yum.repos.d/ with enabled=0.


Good idea.


I'm not sure about this. I might be okay with keeping a sample.repo in
docs, but not /etc/yum.respo.d/. This is because anybody should be able
to add their own mirror to MirrorManager itself and not need any
per-client configuration.


Also /etc/yum.repos.d/ included in InstantMirror would mean that you
need to install InstantMirror on each of your clients as well. How much
sense does this make? =)





BTW, InstantMirror is much simpler, lighter weight and easier to use
than WSUS. Although WSUS has other abilities, InstantMirror has a
good 50% of the functionality of WSUS. This package may seem
innocuous, if you mentioned WSUS in the same breath as InstantMirror,
it might warrant a mention as a feature, at least targeted at some
new-to-Linux admins.


I have no idea what WSUS does but my guess is the 80/20 rule applies.
Still, the fact that a useful admin tool can be implemented in less
than 100 lines of Python demonstrates the excellent design of Apache,
mod_python and Python.


Reportedly Debian has 3 implementations of a reverse proxy mirror, some
even handle apt metadata in an intelligent way to expire the repository
contents. Might be worth looking into to get ideas for future
improvement for InstantMirror.


Warren Togami
wtogami@redhat.com

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

From: "Ed Swierk" <eswierk@arastra.com>



Actually InstantMirror should work just fine in a simple
non-VirtualHost configuration, so perhaps the default Apache
configuration file can leave out the VirtualHost directives and we can
bundle the fancier VirtualHost configuration as an example in the docs
directory.


I didn't think a non-VirtualHost config might be more popular,
because it is not the way I do things



From: Warren Togami <wtogami@redhat.com>



I personally dislike this idea. It is already fully commented out in
the default InstantMirror.conf. Why don't we:
1) Keep the contents as-is.
2) Add a note to other examples the doc directory.
3) Rename the file to zz-InstantMirror.conf so it never goes first.


From my experience and usage, I agree with this.
However, we are getting into a territory like ordering in /etc/init.d/

What I did to make the InstantMirror.conf work :

1)
Uncomment

NameVirtualHost *:80

in /etc/httpd/conf/httpd.conf

2)
Create a "Default.conf" in conf.d that contains

<VirtualHost *:80>
ServerName your-hostname-here
DocumentRoot /var/www/html
</VirtualHost>

I named it with an upper case "D" so it loads first.
The name leaves something to be desired, but is indicative of
containing the config for the default host.


3)
Changes to the original InstantMirror.conf

#DocumentRoot /var/ftp/pub/linux/fedora
DocumentRoot /var/ftp

So I didn't get additional directory levels.
I added logging

ErrorLog logs/mirror-error_log
CustomLog logs/mirror-access_log combined

If I could make one other suggestion about InstantMirror, it
would be

to include a sample.repo file in /usr/share/doc/InstantMirror-x/ or
throw it into /etc/yum.repos.d/ with enabled=0.


Good idea.


I'm not sure about this. I might be okay with keeping a
sample.repo in

docs, but not /etc/yum.respo.d/.


After I wrote the suggestion for a sample.repo in docs, I couldn't
think of a reason not to put one in yum.repos.d.



Also /etc/yum.repos.d/ included in InstantMirror would mean that you
need to install InstantMirror on each of your clients as well. How
much

sense does this make? =)


That is a good reason to only provide a sample.repo in docs.

Reportedly Debian has 3 implementations of a reverse proxy mirror,
some
even handle apt metadata in an intelligent way to expire the
repository

contents. Might be worth looking into to get ideas for future
improvement for InstantMirror.


Names to save Google time ?


Charles Dostale

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

Am Donnerstag, den 06.12.2007, 18:13 -0800 schrieb Ed Swierk:
> On 12/4/07, chasd <chasd@silveroaks.com> wrote:
> > If it was expected that InstantMirror was to be very popular, or
> > there was a large number of other packages that would make use of
> > <VirtualHost> directives, it might make sense to modify the default
> > apache configuration to be more "virtual host friendly." As it
> > stands, I think some prudent suggestions in the provided
> > InstantMirror.conf file ( and perhaps renaming it ) is the best plan.
>
> Actually InstantMirror should work just fine in a simple
> non-VirtualHost configuration,

That's not very common though, is it?
Who has enough ips for that..?

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

On 12/10/07, nodata <lsof@nodata.co.uk> wrote:
> That's not very common though, is it?
> Who has enough ips for that..?

I was thinking users might want to set up an InstantMirror tree in a
subdirectory of an existing web host, but it sounds like that's not a
likely configuration. I use a VirtualHost myself, so I'm happy to
consider it the default :-)

--Ed

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