Distributed tinderboxing

[Ade Lovett]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Sep 14, 2005, at 01:12 , Pav Lucistnik wrote:
> Do you plan an affinity of bricks to the hosts, or migration of  
> packages
> between hosts of same arch/objtree/portstree?

Right now, I'm concentrating on the database pseudo-schema.  Brick  
affinity is something that will probably need some kind of additional  
table in the SQL, but I'm not sure yet whether it would require any  
changes in what I would call the core tables as currently shown in  
the README.txt

Similarly for package migration.  The basic premise of a cluster as  
it stands right now is a number of builder boxes (on a LAN) hooked to  
a central www/NFS server which houses the errorlogs/logs/packages,  
with an SQL server off to one side somewhere.

It would certainly be trivial to add a table of  
{objtree,portstree,package_uri,package_date} quads, and have the  
actual build scripts poke into that to pull packages in a more  
optimized manner, but again, I'm not sure this requires a core table  
change.

In particular, I haven't even begun to consider the full  
ramifications of geographically diverse co-operative clusters.  I  
don't believe I've made any design choices (yet) that would preclude  
that from happening; at the same time there is a danger of adding so  
many new features to a rebuild that it collapses under its own weight  
and never gets deployed.

In case I *am* putting in any assumptions, my setup here consists of  
the following:

     one box running postgresql, and my main local domain stuff
     one box running the webservers, which happens to have a small  
mysql server on it
     two boxes (one i386, one amd64) for building things

I plan on adding one more builder box (either i386 or amd64, doesn't  
really matter), just so I can more easily work on more than 1 machine  
with the same architecture, and distributed building.

- -aDe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFDKIoipXS8U0IvffwRArRBAKCeuwD+2JrU63U3PKk92hvw5JPEJgCdEazm
J8NmgyIgAgaN/eoea5XVoFI=
=ao8c
-----END PGP SIGNATURE-----