Adding builders without NFS access

[Josh Boyer]

Hi All,

I believe that currently any koji builder needs to have read-only access to
/mnt/koji, normally realized by NFS mounting.  I am wondering if there is a
way to add builders to a koji instance without requiring this.

In my thinking, this essentially means that all builders must be colocated in
the same lab.  That is a bit unfortunate, given that adding builders outside
of the local lab is one of the things that could really help a secondary arch.

Has any work gone into not requiring /mnt/koji to the builders?

Thanks,
josh

[Dan Horák]

Josh Boyer píše v Po 28. 09. 2009 v 12:39 -0400: 
>  Hi All,
>  
>  I believe that currently any koji builder needs to have read-only access to
>  /mnt/koji, normally realized by NFS mounting.  I am wondering if there is a
>  way to add builders to a koji instance without requiring this. 
Only HTTP connection is required between the hub and the builders.
That's how we have it set up for Fedora/s390x.

>  In my thinking, this essentially means that all builders must be
> colocated in
>  the same lab.  That is a bit unfortunate, given that adding builders outside
>  of the local lab is one of the things that could really help a secondary arch.
>  
>  Has any work gone into not requiring /mnt/koji to the builders? 

Dan

[Jesse Keating]

On Sep 28, 2009, at 9:39, Josh Boyer <jwboyer(a)gmail.com&gt; wrote:

>  Hi All,
>
>  I believe that currently any koji builder needs to have read-only  
>  access to
>  /mnt/koji, normally realized by NFS mounting.  I am wondering if  
>  there is a
>  way to add builders to a koji instance without requiring this.
>
>  In my thinking, this essentially means that all builders must be  
>  colocated in
>  the same lab.  That is a bit unfortunate, given that adding builders  
>  outside
>  of the local lab is one of the things that could really help a  
>  secondary arch.
>
>  Has any work gone into not requiring /mnt/koji to the builders?
>
>  Thanks,
>  josh
>
>  --
>  Fedora-buildsys-list mailing list
>  Fedora-buildsys-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-buildsys-list 
Should be fine if you take them out of the createrepo channel

--
Jes

[Josh Boyer]

On Mon, Sep 28, 2009 at 10:01:24AM -0700, Jesse Keating wrote:
>  On Sep 28, 2009, at 9:39, Josh Boyer <jwboyer(a)gmail.com&gt; wrote:
>
> > Hi All,
> >
> > I believe that currently any koji builder needs to have read-only  
> > access to
> > /mnt/koji, normally realized by NFS mounting.  I am wondering if there 
> > is a
> > way to add builders to a koji instance without requiring this.
> >
> > In my thinking, this essentially means that all builders must be  
> > colocated in
> > the same lab.  That is a bit unfortunate, given that adding builders  
> > outside
> > of the local lab is one of the things that could really help a  
> > secondary arch.
> >
> > Has any work gone into not requiring /mnt/koji to the builders?
> >
> > Thanks,
> > josh
> >
> > --
> > Fedora-buildsys-list mailing list
> > Fedora-buildsys-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
>
>  Should be fine if you take them out of the createrepo channel 
OK, I might have misunderstood then.  It just so happens that my builders
are the only creatrepo enabled hosts.  I find that to be good news.

josh

[Mike McLean]

On 09/28/2009 12:39 PM, Josh Boyer wrote:
>  I believe that currently any koji builder needs to have read-only
> access to
>  /mnt/koji, normally realized by NFS mounting.  I am wondering if there is a
>  way to add builders to a koji instance without requiring this. 
This is entirely possible and has been in place for years I think. As 
Jesse points out, you need to make sure any builders that lack the nfs 
mount are not in the createrepo channel.

Also, you need to make sure you have the builders configured for http 
access. That means you need to set topurl instead of topdir in the 
config as well as setting the pkgurl option. Of course that means your 
kojidir must be http accessible from somewhere.

I should also point out that the shared fs need not be accomplished by 
nfs (though this is arguably the easiest method). There are multiple 
ways of sharing a filesystem across machines.