On Sun, Apr 20, 2008 at 9:39 PM, Adriaan de Groot <groot at kde.org> wrote: > I think we reached a consensus on what we want on Dillon and how in order to > optimize our test and OS coverage with the x86 & amd64 packages for KDE's > dependencies (and mid-term KDE4 itself). But I'm starting this new thread in > order to double-check the consensus. Also because I'm not sure I got the > technical details right and we need to ask Gerard (a) nicely (b) clearly to > do what we want. > > Dillon should get Xen and Dom0 should be some recent flavor of Nevada. Not > 85, > though, because that breaks stuff. >
I think that in our case we need some pretty stable Nevada as Dom0. I don't expect from Dom0 nothing more then serve two DomU. I dont't have many experiences with Xen (xVM) on Solaris, but from my point of view is SXDE(79) in default quite enough for that. I hope that expert as Gerard could be helpful and recommend to us which build is enough for that. > We want at least an S10U4 -- the oldest Solaris we intend to support -- and > another nv in there as DomU. > first DomU > definitely S10U5 (most of customers which have S10 will be in upgrade process to U5 as soon as possible :D ) second DomU > Nevada latest buils as it possible. I have some idea, could we upgrade this Nevada i.e each 3 - 4 months ? > To conserve disk space (a little at least) we want one shared checkout of > Dude > and one of KDE4 SVN -- both anonsvn, read-only -- so that everyone can build > out of these if that's all that's needed. yes, we can use nfs share for all read only things (i.e from Dom0) > > For all the users of the machine, we want them to be able to log in to the nv > DomU and there should be a private zone for each of them in order to test, > install, deinstall etc. out of the way of everyone else. > ok, for both DomU. I think that users don't need log in to Dom0 and directly into global zones in DomU. Users needs full access directly into their zone. Could be very usefull direct log in from mulder into users zones. Example: Dom0 hostname: dillon DomU hostname: dillon10 >>> S10U5 DomU hostname: dillonNevada >>> latest Nevada my username: luc zone hostname on dillon10: luc10 zone hostname on dillonNevada: lucNevada Typical connection looks like : ssh kde at mulder pass: xxxx mulder:> ssh luc at luc10 for connection to my zone on Solaris10 DomU ssh luc at lucNevada for connection to my zone on Nevada DomU as a user I don't need any other connection. > There should be one shared compiler installaton -- Luc, what do you > recommend? > URLs please -- for everyone so that we are working with the same set of > tools. > Here is only one right way .... Sun Studio 12 + full set of patches. Nothing else. Using wide variety of Sun Studio Express from SXDE, SXCE is equal to nightmare, when we will obtain build issues from users with different builds. As Stefan said, we need exactly same environment between us everyone. I'm not sure if I understand good your statement 'shared'? What do you think with 'shared' ? Install SS12 in Dom0 as /opt/SS12 (in /opt/SUNWspro is SS Express) and export them over nfs to DomU as /opt/SUNWspro ? Do I understand right ? Same way we can use for KBE(CBE) install in /opt/ in Dom0 and export to DomU over nfs. > Anything else? > Yes ... I would better username, then I have now. I would like to have username : luc :D I hope that I'm not totally crazy if I would like to have those changes which I mentioned above. Last question, is it too crazy use some central service for maintain users accounts ? > [ade] I'm ready to help if I'll be able luc -- Lukas 'Luc' Oboril IRC nickname: luc^ at freenode When dealing with people, let us remember we are not dealing with creatures of logic. We are dealing with creatures of emotions, creatures bristling with prejudices and motivated by pride and vanity. Dale Carnegie
