We (the KDE4-Solaris project) now have two dedicated build machines in the Sun lab at amersfoort. These are for KDE package building and testing, and are accessible to all who need it. But looking at the logs, they are used mostly by me and Luc^.
The one machine is called Dillon and is a 16-way opteron box. It's slightly older hardware, so it only supports paravirtualization; this means we can't run S10 virtualized on it. The other machine has no name yet - that is Gerard's prerogative, although I would choose "Bawb" or "Matt" myself under the circumstances - and is a T5220, I think that's an 8-way T2. This *does* do all the virtualization, so we could put S10 on it. We've gone over this before, about updating machines. This time I sat down with Gerard to plan specifics and a timeframe. The timeframe is "now", basically if dillon has a load of 0 and just me logged in, then it can be taken offline anytime and upgraded. Data on the machine will be preserved. We decided to install the machines pretty much equally: nv101 or nv103 for host OS virtualized nv93 (the "older nevada") virtualized nv107 (something trying to track the latest release) virtualized osol2008.11 (on dillon, as it's x86 only) virtualized s10 (on the other one, as it's sparc only) Zones will be used in the host OS to give people place to play / build / futz around without getting in each other's way; the virtualized ones won't necessarily have zones but be used for "release" builds. So this is how our build infrastructure will be upgraded fairly soon. Until then I'll be building stuff on dillon regularly for nv70 -- these also work on osol 2008.11 -- and on my home workstation, and avoiding S10. [ade] [ade]
