-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I couldn't decide where to send this, so here it is for all to see.
This is an idea I had last night, so don't expect anything too well thought out! Feedback - positive or negative, I don't care.
btw, I will be without a net connection for ~1 week from Sunday, though I will be watching ;)
Regards, Ian Leitch
Gentoo Linux Remote Package Building Service ============================================
The purpose of this system is to make Gentoo an option for those who had previously rejected Gentoo as a server grade OS. Reasons for rejection could have been the dislike for the presence of development tools on a production system, or use of CPU cycles to compile packages which could have been used to service web/ftp/whatever requests.
And for those already using Gentoo on a production server? They'll just love us even more :)
In a nutshell, emerge requests made on the production system are sent to a "build server", which compiles the package(s) and notifies the production server when the binary package is ready for download.
The build server would run a daemon which listens for requests, and are authenticated by client ID. Each client (production server) registers itself with the build server, at which point the system's CHOST, CFLAGS, USE etc are sent and stored on the build server.
When emerge is called on the production server; if 'remote-build' is in FEATURES then the build server is notified to build package foo and all its deps for client ID 123. An optional priority can also be set for security updates etc.
When the package is ready on the build server, it'll need to notify the production server somehow. Having a daemon running on the production server would be the easiest option, but probably the worst. Other options could be: Monitor an NFS mount (is this possible?), check the build server every n minutes (with a what's-ready request) then download from NFS/web server.
One requirement of this system is that the production server and build server will need to share the same portage tree. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFB39sNUxGWrFYv8KQRAqK/AKCiFDj7c+LGJDtFl0iDU7A2/mm8KwCeMfaU 3vY4/i9Q7D3N1tHKw1jA3Tk= =hmIn -----END PGP SIGNATURE-----
-- [email protected] mailing list
